[00:52] oh ok thanks [00:52] jelmer, of course we don't need to verify every bug, just make sure it's not broken [01:07] can i do conditional commits ? [01:07] or a patch commit you might call it [03:18] meth, what do you mean? [03:21] git add -p [03:21] would like that [03:23] try bzr-interactive [03:27] https://launchpad.net/bzr-interactive [03:31] cool [04:11] anyone alive in here? [04:14] Often! [04:16] hi spiv! [04:16] your name looks familiar :-) [04:16] do you have time to field a bazaar question for me? [04:19] BlindWolf8: depends on how hard it is ;) [04:20] BlindWolf8: in general it's best to just ask your question, lots of folks are usually quiet but check the scrollback periodically and might answer [04:20] spiv: well, I always try and be polite [04:21] people giving fre support and all [04:21] This channel is here to talk about bzr :) [04:21] *free [04:21] OK, so...here's the deal... [04:21] You're quite welcome to just pop in and say "hi, I'm having X problem..." :) [04:21] I have a server...running Ubuntu 11.10 [04:21] bzr is installed on it via the PPA [04:21] bzr 2.4.2 is on all the clients and the server [04:22] putty 0.61 is installed on all clients [04:22] clients are all windows boxes [04:22] clients gave me public keys to pop on the server and use pagent to authenticate [04:23] I have the command for bzr_ssh_path_limiter listed in the auithorized_keys file [04:24] on the first line of the keys file, it goes [04:24] all other lines are simply public keys [04:24] first, I am assuming that just the first line is supposed to have the bzr_ssh_path_limiter command? [04:27] I have done various tests on my end and I am able to pull files from the server no problem, but none of the other people I work with can [04:27] If you only want the first key to use the bzr_ssh_path_limiter [04:27] Each line is independent of the others, read the authorized_keys man page that comes with OpenSSH for the exact details. [04:28] ah........ [04:29] I thought it was executed on the user's profile, not per key.... [04:29] No, it's per key [04:30] that solves that problem, thanks! [04:30] I have another slight issue though [04:30] So some people use it as a relatively cheap way to have per-user repos hosted by a single user account. [04:31] some clients get a temp file error that deals with pagent...but I'm using 0.61 with no isseus, even though the issue is supposed to be with 0.61 [04:31] I don't know much about pageant. [04:31] relavent bug report: https://bugs.launchpad.net/bzr/+bug/820805 [04:31] Ubuntu bug 820805 in Bazaar "access denied on Pageant .pag file" [Undecided,Confirmed] [04:38] o/ spiv [04:38] Hey poolie === Merwin_ is now known as Merwin === gerard_1 is now known as gerard_ [09:03] morning all. [09:26] hi mgz === Merwin_ is now known as Merwin [10:27] what's the way of finding out what versions of packages PQM has installed? [10:30] mgz: checking with a losa, probably [10:31] okay, what's the way of changing the PQM code so it displays the versions it has installed? [10:32] mgz: you'd have to modify the script that is used to verify bzr submissions, I'm not sure if that's publicly available somewhere === Noldorin__ is now known as Noldorin [10:34] mgz: change Makefile [10:34] mgz: in the bzr tree [10:35] mgz: PQM is -extremely- simple. Thats why everyone gets so confused by it. [10:35] that only works if it's running a test I think lifeless [10:36] mgz: yes... that was the context of your question right ? [10:36] '23:31 < mgz> okay, what's the way of changing the PQM code so it displays the versions it has installed? [10:36] ' [10:36] but lp:pqm doesn't look too hard to poke, though actually deploying a change is probably impossible [10:36] pretty easy - get the losa to pull in the branch [10:37] and yes, lp:pqm should be fairly straight forward, though I'm horribly confused about what you're trying to do. [10:37] okay, I will poke this. [10:37] lifeless: I want to look at pqm.bazaar-vcs.org and know what version of testtools is being used [10:37] mgz: I don't think that question makes sense unless a test is runnig. [10:38] meh, maybe not. [10:39] there's not a sensible way of getting ther versions of python packages unless they're being used [10:40] debian packages would kind of work, but I imagine that would also be a harder sell. [10:41] there is that, and that the place to check is in a chroot, of which there can be multiple versions at once (especially when bzr is transitioning) [10:41] having the web UI go off and probe arbitrary chroots which may or may not be active or even usable at the time ... seems odd [10:41] vs having Makefile report it for you. [10:42] adding more output to the Makefile doesn't actually solve my problem though [10:42] what is your problem ? [10:42] you'd still have to push a branch to see any relevent information [10:43] ^as stated above [10:43] mgz: I don't follow :) [10:44] I, right now, want to know something, and right now, the page just says "0 scripts" and the time [10:45] ah. [10:45] so in general, to know this, I ask a losa [10:45] there's no change I can do in lp:bzr to remedy that, and it seems the same goes for lp:pqm [10:46] mgz: you could send a patch through that will print out the versions and return 1 [10:46] so my ping saving idea is no good. [10:46] mgz: making the test suite fail and thus not landing anything. [10:46] mgz: you could even just have that sitting around ready to go at a moments notice [10:48] that only helps me, which is much the same as just asking an admin. [10:49] I must be really tied [10:49] but it's okay, sometimes there's not an easy way of adding code to save work, [10:49] *tired* [10:49] because I thought you said you wanted to know [10:50] I do, and when the answer was "ask someone" I wondered if I could avoid that by fixing the web display. [10:50] The answer to the second question is "no" [10:50] its more yes-but-its-not-as-simple-as-all-that :( [10:51] So, I will go back to the initial issue and forget the generalisation. [10:51] :) [12:54] ah, vila is still suffering [12:54] all I really have left today is the impressive cough [13:21] dammit, last change somehow hasn't fixed the random failure on babune natty [13:22] what were the chances of even hitting it again right after... === yofel_ is now known as yofel [16:20] heh, bialix and I having the same idea in these bugs at the same time === daveb__ is now known as croepha [17:20] I'm sure Gordan or someone fixed an issue related to unquoting paths from config [17:20] but I now can't find it [17:54] Hello o/ [17:54] I'm sure it's somewhere in the documentation but I can't find how exactly create a new branch in a shared repository. Any help? [17:57] Amis: just `bzr init` as normal. [17:58] bzr init "remote shared rep location" project? [17:58] oh wait [17:58] eg, `bzr init-repo repo; bzr init repo/branch` [17:59] you can also branch into the shared repo and it will do the right thing [18:05] yeah, right, thanks === spiv_ is now known as spiv === wallyworld___ is now known as wallyworld