[00:17] <jelmer> lifeless, subunit was accepted into sid
[13:40] <TheJosh1337> Hi I have a quick question about bazaar. How can I set up access control for my bazaar repository? I am running the repo on a server, and I want control on who can commit to what branches.
[13:43] <mwhudson> TheJosh1337: bazaar doesn't get into that business itself
[13:43] <mwhudson> TheJosh1337: one option is using unix accounts and ssh
[13:44] <TheJosh1337> can I write a plugin?
[13:45] <TheJosh1337> it's currently going through bzr://
[13:46] <mwhudson> yes, you can
[13:46] <mwhudson> it's probably not super easy though
[13:47] <TheJosh1337> All I want is for each user to have as many branches as they want
[13:47] <TheJosh1337> but they can only commit to their branches.
[13:48] <TheJosh1337> with the branch name containing the user name (e.g., /TheJosh/sandbox for TheJosh's 'sandbox' branch
[13:49] <mwhudson> but you don't want to create a unix account for each user?
[13:51] <TheJosh1337> I could do that
[13:51] <mwhudson> it's a bit sucky, but that's easiest for now
[13:51] <TheJosh1337> although the plan is that the users will only be able to commit to their branch(es)
[13:51] <mwhudson> well sure
[13:51] <TheJosh1337> then a web tool will allow merging of branches into trunk
[13:52] <mwhudson> so use unix permissions
[13:52] <TheJosh1337> so the user accounts are only on the web tool.
[13:52] <mwhudson> i.e. create /code/Bob that's owned by bob anx rwxr--r--
[13:52] <mwhudson> there are bits and pieces in launchpad we should probably factor out and open source to make this easier
[13:52] <TheJosh1337> so my web tool has to create a unix account on the server for every user account created, and set the correct permissions as well, correct
[13:53] <mwhudson> but, well, that takes time
[13:53] <mwhudson> ah i see
[13:53] <TheJosh1337> see I want to do something slightly radical. I want to allow anyone with an account commit access to trunk straight away
[13:53] <TheJosh1337> as long as they go through a branch, and as long as the code compiles
[13:54] <mwhudson> you can play tricks with ~/.ssh/authorized_keys to avoid creating an actual account for each user
[13:54] <TheJosh1337> kinda like wikipedia - it doesn't make sense, but it works
[13:54] <mwhudson> TheJosh1337: have you seen pqm?
[13:54] <TheJosh1337> Yeah
[13:54] <mwhudson> that allows an email driven way of doing what you want
[13:54] <TheJosh1337> but I couldn't find any useful docs
[13:54] <TheJosh1337> like how to install or set up or anything like that
[13:55] <TheJosh1337> and for a anyone-can-commit system to work it has to be easy to use - really easy to use
[13:55] <TheJosh1337> wikipedia wouldn't work if it wasn't brain-dead easy to use
[13:57] <TheJosh1337> mwhudson, ill look into hooks, to begin with I only have to prevent commits to trunk, that should be fairly easy I hope.
[14:05] <TheJosh1337> thanks
[17:42] <nekohayo> anyone has a recording or slides of "Plans for Bazaar after 2.0" from UDS 2009?
[20:59] <cellofellow> I have a Bazaar branch I just made that has an Audacity project with nearly 2:30 hours of audio in it. It's about 2.6 GB and has 2679 files in it. I've already put it in a regular branch but was thinking it would be better to put it into a repository, though I'm not sure the best route to go with that.
[21:00] <cellofellow> Should I use the --no-trees option?
[21:00] <cellofellow> can I move the already existing branch into a shared repo or do I have to branch it in?
[21:06] <nekohayo> hey there, is it me or the bzr-gtk packages are broken with bazaar 1.15?
[21:16] <pygi> nekohayo: define broken?
[21:17] <nekohayo> pygi: bzr viz doesn't start, neither does olive
[21:17] <pygi> nekohayo: what's the traceback?
[21:17] <nekohayo> Unable to load plugin 'gtk'. It requested API version (1, 13, 0) of module <module 'bzrlib' from '/usr/lib/python2.6/dist-packages/bzrlib/__init__.pyc'> but the minimum exported version is (1, 15, 0), and the maximum is (1, 15, 0)
[21:17] <pygi> pastie pls
[21:17] <nekohayo> that's all of it
[21:17] <pygi> nekohayo: moment :P
[21:18] <pygi> bzr-gtk comaintainer is in the next room
[21:18] <pygi> but he's busy :-/
[21:18] <pygi> hmmm
[21:18] <nekohayo> seems like there's a version mismatch
[21:18] <pygi> nekohayo: are you using bzr checkout of bzr-gtk?
[21:18] <nekohayo> nah, just the PPA
[21:18] <pygi> nekohayo: could you try the bzr checkout pls?
[21:19] <pygi> we'll get better at keeping it up to date, I know :p
[21:19] <nekohayo> don't quite know how to do that :)
[21:19] <nekohayo> well if it's just a matter of the bzr-gtk package not being yet updated in the archive..
[21:19] <nekohayo> I guess I can simply wait for it to appear?
[21:31] <pygi> nekohayo: yes :)
[21:31] <pygi> nekohayo: I think the thing is that there isn't yet a new release :P
[21:31] <pygi> I'll bug szi tomorrow
[21:33] <pygi> nekohayo: I think we'll get a bit more better at bzr-gtk after this week
[21:33] <pygi> :)
[21:49] <nekohayo> pygi: ah, why is that? :)
[21:50] <pygi> nekohayo: we had some discussions about bzr-gtk specifically during bazaar sprint
[21:50] <nekohayo> at UDS?
[21:51] <nekohayo> any way for a simple user like me to have access to stuff that was discussed, or presentations such as "Plans for Bazaar after 2.0" ?
[21:51] <pygi> nekohayo: yes
[21:51] <pygi> uhm, there are some notes, but unfortunately its just a list of things for discussion from monday
[21:51] <pygi> some updates were sent during UDS to the mailing list
[21:51] <pygi> but I guess most are still expected
[21:52] <nekohayo> I vaguely heard someone raving about that "Plans for Bazaar after 2.0" talk on planet gnome, but couldn't find it
[21:52] <pygi> uh? Not sure, I didn't follow planet gnome  really
[21:53] <pygi> I was busy with windows stuff :-/
[21:54] <nekohayo> :]
[21:54] <nekohayo> it was quite hard to spot
[21:54] <nekohayo> in the middle of a list of bullet points
[22:01] <LarstiQ> nekohayo: not featured in planet.bazaar-vcs.org?
[22:02] <nekohayo> LarstiQ: nope, haven't seen that there
[22:02] <nekohayo> and the post in question on p.g.o. is http://bloc.eurion.net/archives/2009/uds-2009/
[22:02] <nekohayo> which briefly mentions 2.0, but no details
[22:03] <LarstiQ> hah
[22:03] <LarstiQ> nekohayo: that is just a reference to the `bzr rocks` command
[22:04] <nekohayo> well with a session title like that, I'm still interested in those "plans after 2.0"
[22:04] <LarstiQ> nekohayo: http://doc.bazaar-vcs.org/devnotes/wishlist.html is a brief list
[22:05] <LarstiQ> nekohayo: you can look at other documents in that dir for more of an idea
[22:05] <nekohayo> cool
[22:08] <pygi> nekohayo: I think there will be a lot work on UI
[22:08] <pygi> and the plan is to have one stable and one development format in the entire 2.0 cycle
[22:09] <nekohayo> you mean, olive/nautilus will be usable? :P
[22:09] <pygi> some of the plans also include merging qt/gtk logic behind GUIs
[22:09] <pygi> nekohayo: I meant UI of the "bzr"
[22:09] <nekohayo> oh
[22:10] <pygi> nekohayo: why is say olive not usable?
[22:11] <nekohayo> well my general impression from having used it a while ago is that it's not feature-complete, and not much attention/love is given to it because the devs are busy with other things?
[22:11] <pygi> nekohayo: specifics specifics
[22:12]  * nekohayo finds his bug list
[22:12] <pygi> if you could write a detailed mail to the mailing list, that would be great for example
[22:13] <nekohayo> well I think this is part of it: https://bugs.launchpad.net/bzr-gtk/+bugs
[22:15] <nekohayo> the bugs don't seem to be fixed much or the app doesn't "feel" maintained, but this is just a subjective, personal perception
[22:16] <pygi> nekohayo: that's true, I admit it
[22:16] <nekohayo> but I do understand the time/workforce constraints
[22:17] <nekohayo> over time I just got accustomed to using bzr on the command line and not hoping for olive or nautilus integration, basically :|
[22:17] <pygi> nekohayo: I really really really hope that will change
[22:17] <nekohayo> me too :)
[22:17] <nekohayo> but I have no idea when it will happen?
[22:18] <pygi> nekohayo: this year :p
[22:18] <nekohayo> I remember about 5-10 bug reports I did back 1-2 years ago on olive AND bzr-gtk (because there was some kind of mess regarding their status in launchpad)
[22:18] <nekohayo> and I even provided patches which sat there for months
[22:18] <nekohayo> (for basic 1-2 lines stuff)
[22:18] <pygi> nekohayo: ok, if you'll have patches now I'll process them in like a week at most :p
[22:18] <nekohayo> that kinda depressed me ;)
[22:19] <nekohayo> nice
[22:19] <pygi> unless they're 10000lines :P
[22:25] <pygi> nekohayo: so when can I expect patches? :D
[22:37] <ronny> whats the 1.14 format and whats the relation to brisbane-core?
[22:41] <fullermd> None, 1.14 adds a WT format for the IO filters.
[22:41] <pygi> ronny: and 1.14 release added a brisbane core as --development-rich-root
[22:46] <ronny> pygi: does that mean the on-disk structures will be stable now?
[22:47] <pygi> ronny: if you're thinking of 2.x having a stable format, then yes