[01:41] <mtaylor> jelmer: how hard is it to use the rewrite plugin to go through and replace the committer on a bunch of revs? (as in, retroactively fix someones commits who had never done bzr whoami...) ?
[03:00] <jelmer> mtaylor: you'd have to patch it to do something like that
[03:00] <jelmer> mtaylor: it shouldn't be too hard to do using a patch, but it's not possible using the current UI
[03:02] <mtaylor> jelmer: ok. good to know
[03:02] <mtaylor> jelmer: I may poke at that at some point - I think I'd like to make a pass on our tree to clean up a bunch of revs that have bogus people having committed them
[03:09] <jelmer> mtaylor: this will affect the revision ids of all revisions since the first that is changed, of course.
[04:32] <echo-area> Hello, I upgraded to bzr-2.2.0 on my Windows machine, and then get this error every time I execute bzr: "Unable to load plugin u'rebase'. It requested API version (2, 1, 0) of module <module 'bzrlib' from 'C:\Program Files\Bazaar\lib\library.zip\bzrlib\__init__.pyo'> but the minimum exported version is (2, 2, 0), and the maximum is (2, 2, 0)"  How to resolve this?
[04:38] <echo-area> I see that rebase is now renamed to ``rewrite''.  Could I simply remove the subdir `rebase' in plugins?
[04:39] <echo-area> I've done that and don't see problems.  I think it works
[04:39] <fullermd> Yes, the plugin was renamed.
[19:08] <nprasath002> Does netbeans has a bzr plugin? is the developement still active?? where can i get it??
[19:44] <lifeless> nprasath002: I'm not aware of one; it would be awesome to have one.
[21:51] <snowdrop> I did a "checkout --lightweight" but can't commit to it, get the followin error msg: "bzr: ERROR: Cannot lock LockDir(http://bazaar.launchpad.net/~wtdevs/wtactics/trunk/.bzr/branch/lock): Transport operation not possible: http does not support mkdir() "
[21:52] <snowdrop> any pointers? (And yeah, I'm new to bzr... only had some experience with SVN before.)
[21:53] <mgz> checkout from a branch you can write to, which means not over http.
[21:54] <mgz> if you used a lp: shortcut, this means running `bzr launchpad-login` and setting up ssh, then doing the same thing again.
[21:56] <snowdrop> mgz:  i see....  is there a way to change the http:// stuff in the branch I already checked out?
[21:56] <snowdrop> mgz: So i don't have to check it out once again?
[21:56] <mgz> `bzr pull --remember lp:<sameasbefore>` should work I think.
[21:57] <snowdrop> mgz:  thanks.. on it.
[21:58] <snowdrop> mgz: Hrm.. "bzr pull --remember lp:~wtdevs/wtactics/trunk/" gave me same error.
[21:59] <mgz> did you do `bzr launchpad-login <yourid>` first?
[21:59] <mgz> you need the ssh access rather than the http, is our aim here.
[22:00] <snowdrop> mgz: Should I use my personal ID, or the groups id? Cause " lp:~wtdevs"  = the group (wtdevs), while my personal ID is "snowdrop".
[22:00] <mgz> your personal id.
[22:00] <snowdrop> mgz: snowdrop@snowdrop:~/WTactics$ bzr launchpad-login snowdrop
[22:00] <snowdrop> snowdrop@snowdrop:~/WTactics$ bzr pull --remember lp:~wtdevs/wtactics/trunk/
[22:00] <snowdrop> bzr: ERROR: Cannot lock LockDir(http://bazaar.launchpad.net/~wtdevs/wtactics/trunk/.bzr/branch/lock): Transport operation not possible: http does not support mkdir()
[22:01] <mgz> okay, try... `bzr switch lp:~wtdevs/wtactics/trunk/` instead
[22:01]  * mgz doesn't use checkouts much
[22:02] <snowdrop> mgz: Ah.. success!
[22:02] <snowdrop> snowdrop@snowdrop:~/WTactics$ bzr switch lp:~wtdevs/wtactics/trunk/
[22:02] <snowdrop> Tree is up to date at revision 13.
[22:02] <snowdrop> Switched to branch: bzr+ssh://bazaar.launchpad.net/~wtdevs/wtactics/trunk/
[22:02] <mgz> good good, and now, if you've made changes, and run `bzr diff` you should still see them
[22:04] <snowdrop> mgz: Since I did a "checkout --lightweight"... all my "commits" directly upload to launchpad, right? (kind of SVN)? In contrast to when I used "branch" and they were done locally?
[22:05] <mgz> yup. you should think about changing how you work, but this preserves the svn style for now
[22:09] <snowdrop> mgz: Thanks a bunch. =)
[22:09] <snowdrop> mgz: If you take paypal I'd happily buy you a coffe... have been wasting 7h on this... = P
[22:11] <mgz> I'm good for coffee but feel free to email "Martin Pool <mbp@canonical.com>" and say how helpful I was :)
[22:11] <snowdrop> = ) will do.
[22:15] <snowdrop> done.
[22:26] <vila> mgz: ping, just passing around, were did you end up with garyvdm on the windows installers ?
[22:26] <thumper> I wish windows would sort out the ssh support
[22:27] <thumper> https://answers.edge.launchpad.net/launchpad-code/+question/125565 for anyone who knows putty
[22:27] <mgz> vila: he's got one built that looked solid, but he hit another issue that I couldn't reproduce here
[22:27] <vila> thumper: hey ! Feeling really optimistic for a monday morning... windows and sort out in the same sentence... :D
[22:27] <mgz> I'll try and catch up with him on it when I see him in the channel next
[22:28] <vila> mgz: Thanks. I'll try to read the log tomorrow so use my nick when you think I should double-read ;)
[22:29] <mgz> I've got another testtools change babune will want, to deal with the log oddness we were seeing on maverick
[22:30] <mgz> might see if I can track down the timings thing as well tonight.
[22:30] <vila> I don't quite get what happened here and whether there is a way to address this kind of issue that delay the official announce for a single installer... but we should definitely think about it ;)
[22:30] <vila> mgz: you mean the leaks ?
[22:30] <vila> the log leaks that is ?
[22:31] <mgz> yup, that jam was nibbling at the other end of.
[22:32] <vila> ha, I wish there was an option to keep the log for successful tests, pqm is one thing, babune is another and even if hudson doesn't provide access to this yet...it's a shame to not collect it anymore ;-/
[22:33] <mgz> yeah, I think we can back out the hacks but keep the tests for that change when we fix some other things in future
[22:33] <vila> I didn't have the time to follow more closely and I
[22:34] <vila> 'm wondering which object is responsible for or can introduce a variation in the way such test attributes are handled...