[00:05] <Noldorin_> jelmer, well, it looks like you've been working hard, so i can scarcely complain... looking forward to it is all i can say :-)
[02:06] <poolie> jelmer: do you reckon i should add tests before landing this, after, or don't care?
[13:50] <vila> jelmer, maxb: Thanks in advance for giving  some love to bzr-2.4.2 and 2.5b2 in debian and our various PPAs :-)
[16:55] <jo-erlend> I use bzr-explorer. I don't know if it's ontopic for this channel or not, but one thing I really miss, is the ability to see line numbers in the diff view. Is that possible?
[16:56] <jelmer> jo-erlend: I think that's actually part of qbzr
[16:56] <jelmer> jo-erlend: it's on topic in this channel, though it's probably best to file a bug report against bzr-explorer/qbzr about that
[16:57] <jo-erlend> great. Thanks.
[19:42] <smacktoward> hey all
[19:43] <jelmer> hi smacktoward
[19:43] <smacktoward> got a question I could use some better minds' help with :-D
[19:44] <smacktoward> seeing a weird crash when i try to run bzr update
[19:44] <jelmer> smacktoward: can you pastebin the backtrace?
[19:44] <smacktoward> sure, 1sec
[19:44] <jelmer> I have to quickly run out for groceries, but back in 20 minutes or so
[19:44] <smacktoward> k
[19:46] <smacktoward> pastebin: http://pastebin.com/GwM57smq
[19:58] <jelmer> smacktoward: as far as I can tell this should be fixed in newer versions of bzr - 2.0 is fairly old
[19:58] <smacktoward> hm
[19:59] <jelmer> bug 279680 looks related
[19:59] <smacktoward> yeah, there's a few similar looking bugs in launchpad, but none with a clear resolution
[20:00] <smacktoward> bug 377261 for example
[20:01] <smacktoward> was hoping there was a fix short of upgrading b/c the box is running debian lenny and lenny-backports' bzr is only 2.0
[20:02] <jelmer> hmm
[20:02] <jelmer> jam: ^
[20:03] <jelmer> jam: you were the last to comment on that bug, do you hjave any idea what might be happening?
[20:13] <smacktoward> there is a duplicate bug of that one (bug 504836) that suggests that the branch is somehow irretrievably busted
[20:14] <smacktoward> but i dunno how it would have gotten busted
[20:14] <jam> jelmer: logging of to go give a session, ping me when I get back
[21:12] <Saviq> hi all, can I unstack a remote branch?
[22:02] <poolie> hi all
[22:25] <jelmer> hey poolie
[22:25] <poolie> hey there
[22:38] <jam> hi jelmer, can you link me what you linked earlier
[22:38] <jam> hi poolie
[22:38] <jelmer> hi jam
[22:38] <jelmer> jam: bug 377261
[22:41] <jam> jelmer: what was the question again?
[22:41] <jam> (I don't have any traceback at this point)
[22:42] <jelmer> jam: the reporter had this traceback: http://pastebin.com/GwM57smq
[22:42] <jelmer> jam: we already found a different bug report which was marked as fixreleased in 2009, but had a similar backtrace
[22:43] <jelmer> then later we found bug 377261
[22:44] <jam> jelmer: it certainly sounds like it could be the same bug
[22:44] <jelmer> jam: I was mainly just wondering whether you had a better idea of what was going on, and if we could help the reporter with a workaround
[22:46] <jam> jelmer: I don't think I dug into it enough to do workaround/reproduce the bug.
[22:46] <jam> Though from the comments, maybe 'bzr revert ??.moved' and then 'bzr remerge ??' might help