[00:20] <lifeless> hmm, 25 failures to go
[00:20] <Peng_> 56/
[00:20] <Peng_> Um. :D Oops. irssi fail.
[00:32] <lifeless> Peng_: and here I thought you were prognosticating
[00:47] <Peng_> No, I just forgot that you put the / before the command.
[01:35] <mkanat> mwhudson: So, are you going to merge my fix, or are you waiting on additional reviews?
[01:36] <mkanat> Oh, wait, I mean Peng.
[01:37] <Peng_> I'm off-duty.
[01:37] <Peng_> Wait...why am I at the computer at all? I forgot.
[01:52] <mkanat> Peng: Haha, okay. :-)
[01:57] <Peng_> mkanat: Regarding your email, the current state of the history-db stuff is that it would not be optional.
[01:57] <mwhudson> mkanat: want to set a commit message on that merge proposal?
[01:58] <Peng_> (Still off-duty! I just check my email too much...)
[02:03] <mwhudson> mkanat: nm, merging anyway
[02:03] <mwhudson> done
[03:08] <Peng_> mwhudson: Ping?
[03:26] <lifeless> hmm, I needs review :P
[03:30] <mkanat> Peng_: Oh, okay.
[04:00] <rm200910> Hi . I cannot do a launchpad checkout. "bzr checkout lp:epics-base/3-14 base1" throws out these exceptions: http://pastebin.com/R96AFfJc Any suggestions?
[04:01]  * rm200910 uses Bazaar (bzr) 2.1.1
[04:02] <lifeless> wow thats fun
[04:02] <lifeless> mwhudson: can you have a peek at that ?
[04:02] <mwhudson> Peng_: hi?
[04:02] <mwhudson> lifeless: looking
[04:02] <lifeless> mwhudson: looks like we're not getting a header we need or something
[04:02] <lifeless> mwhudson: btu I can't see why that would be the case
[04:03] <mwhudson> lifeless: i think it's a ****ed proxy
[04:03] <rm200910> i'm using an http_proxy
[04:03] <rm200910> I must add
[04:03] <lifeless> rm200910: is it anonymising or something ?
[04:03] <TresEquis> hmm, I was just able to get it via 'bzr branch' on my machine using bzr 2.1.1
[04:03] <mwhudson> i don't understand the details though
[04:03] <lifeless> rm200910: try 3.14 rather than 3-14 ?
[04:04] <rm200910> lifeless: I don't know if it's anonymizing
[04:04] <lifeless> rm200910: try this command: bzr checkout lp:epics-base/3.14 base2
[04:04] <lifeless> TresEquis: using the exact command line, or did your subconscious fix the typo ?
[04:05] <rm200910> lifeless: bzr: ERROR: Connection error: while sending CONNECT xmlrpc.edge.launchpad.net:443: [Errno 111] Connection refused
[04:05] <Peng_> mwhudson: Eek. Too late. I was just going AFK again.
[04:05] <Peng_> Um.
[04:06] <lifeless> rm200910: figuring out what an lp: url refers to requires direct access to ssl at the moment
[04:06] <lifeless> rm200910: I think that that might be fixed in 2.2 (but I'm not sure)
[04:06] <Peng_> mwhudson: Are there any plans for when Loggerhead's next release will be?
[04:06] <lifeless> rm200910: you can use http://bazaar.launchpad.net/~epics-core/epics-base/3.14 as a workaround (or bzr+ssh instead of http if you have write access)
[04:06] <mwhudson> Peng_: not from my end, i guess "soon" would be nice
[04:06] <lifeless> actually, I mean
[04:06] <TresEquis> lifeless: yup, my fingers fixed it
[04:07] <lifeless> 'bzr+ssh instead of http if you have done bzr lp-login'
[04:07] <TresEquis> and I used 'bzr branch' rather than 'bzr checkout', too ;)
[04:07] <lifeless> TresEquis: :)
[04:07] <rm200910> lifeless: I will try "bzr checkout http://bazaar.launchpad.net/~epics-core/epics-base/3.14 base3"
[04:08] <rm200910> lifeless: yay! it's doing something
[04:08] <Peng_> mwhudson: Personally, I'd like there to be a release before we go killing backwards compatibility, so anyone who isn't going to be upgrading to 2.0 or 2.1 just yet will still be able to enjoy the other bug fixes and whatever, but...I'm not the release manager, so I'm not going to demand anything.
[04:08] <lifeless> Peng_: you could be
[04:09] <Peng_> Yeah, I'm aware of that. Never done it before, so I dunno.
[04:13] <rm200910> I don't seem to be able to do lp-login over a proxy either: "bzr: ERROR: Connection error: while sending CONNECT launchpad.net:443: [Errno 111] Connection refused"
[04:15] <rm200910> thanks for translating the lp: URL to an http url.
[04:15] <Peng_> IIRC the LP proxy issues should be fixed in 2.1.1?
[04:16] <lifeless> mwhudson: bug 558343
[04:17] <rm200910> I agree with the last comment on that bug: It's not low importance for me!
[04:17] <lifeless> rm200910: well its got two elements
[04:18] <lifeless> we can and will fix it in bzr independently of launchpad changing, as I read it
[04:18] <lifeless> however, medium for us is wrong
[04:18] <lifeless> rm200910: you should click on the 'does this bug affect you' bit
[04:18] <mwhudson> lifeless: looks like it indeed
[04:19] <mwhudson> i think the importance of low for launchpad is ok really, the problem on the server side is a strange response to a seriously bogus request
[04:20] <lifeless> its probably a simple losa thing to fix
[04:20] <lifeless> I'm looking at the bzr side of it now
[04:21] <mwhudson> yeah, i have an unfounded suspicion that the redirect is coming from apache or something
[04:21] <rm200910> Wow: it is of high importance now!
[04:22] <lifeless> rm200910: in bzr, yes I upped it
[04:22] <lifeless> rm200910: do you have pycurl installed ?
[04:24] <rm200910> lifeless: I checked the "rpm -qa" list and did not find it.
[04:29] <lifeless> rm200910: thanks
[04:30] <rm200910> lifeless: I found this pycurl "/tools/RHEL5/src/bzr-2.1.1/bzrlib/transport/http/_pycurl.py"
[04:30] <lifeless> yes, thats our adapter
[04:31] <lifeless> only used if you have pycurl installed (don't install it, I was just gathering data)
[04:31] <lifeless> rm200910: can you do some data gathering for me ?
[04:32] <lifeless> http://pastebin.com/4KcJTJru
[04:32] <lifeless> apply that patch to your bzrlib
[04:33] <lifeless> and show me what it prints (when you have your proxy set as normal)
[04:36] <rm200910> lifeless: sorry it's going to take a while. This is bazaar installed by my sysadmin
[04:37] <rm200910> i'll look at installing something in my home directory
[04:38] <lifeless> rm200910: it can run from source
[04:38] <rm200910> I suppose I could do "bzr checkout lp:bzr"
[04:39] <lifeless> rm200910: just grab our tarball, or branch http://bazaar.launchpad.net/bzr/~bzr-pqm/bzr.dev
[04:41] <rm200910> bzr: ERROR: Not a branch: "http://bazaar.launchpad.net/bzr/~bzr-pqm/bzr.dev/"
[04:43] <rm200910> http://wiki.bazaar.canonical.com/SourceDownloads doesn't give me the 2.1.1 sources.... i wonder where my sysadmin got it from
[04:44] <rm200910> lifeless: I got 2.1.0 and I'll put your patches in
[04:49] <rm200910> lifeless: it prints "xmlrpc.edge.launchpad.net"
[04:50] <lifeless> thanks, I'm looking deeper now
[04:51] <rm200910> It's doing a checkout when I substitute the "3-14" by "3.14" /home/rm200910/tools/bzr-2.1.0/bzr checkout lp:epics-base/3.14 base1
[04:52] <lifeless> interesting
[04:57] <parthm> in a pqm failure mail is an AssertionError in 'File ".../testtools/testcase.py", line 276, in expectFailure' a failure or is it expected failure?
[04:57] <rm200910> it takes for ever though. Still doing it 5 minutes on. The http checkout was almost immediate
[04:57] <parthm> i am trying to understand why https://code.launchpad.net/~parthm/bzr/181124-ls-short-opts/+merge/24414 is failing while tests pass locally
[05:03] <rm200910> thanks for your help. Good-bye
[05:03] <lifeless> rm200910: ok, bye
[05:05] <lifeless> parthm: expectFailure is an assertion that something should error
[05:07] <parthm> lifeless: thanks. so thats nothing to worry about. will look some more into the log.
[05:15] <parthm> aah. its was test_help which was failing. hmm.
[05:31] <parthm> i was thinking the huge pqm error log should be a text attachment rather than inmail content. made FF crash :(
[05:55] <lifeless> parthm: that would be good to; though its meant to filter and not be so hgue :(
[05:58] <parthm> lifeless: it was 3.1M for me as a mail (on gmail). FF takes a looong time for search and hangs when i copy. When I had gmail save, it saved as html :( .... had to run it through html2txt
[05:58] <parthm> then used vim with text ... and all was well :)
[05:59] <parthm> lifeless: i thought there might be some filtering ... but this is the first time i had to go through it so i wasn't sure.
[05:59] <parthm> filtering would be real neat.
[06:01] <parthm> is it possible to submit the same patch to pqm ... i know p1 is running and will fail. can i put in p2 without waiting for p1 to finish (with nothing between p1 and p2)?
[06:03] <parthm> p2 is p1 with some fixes.
[06:04] <lifeless> sure
[06:04] <parthm> lifeless: cool. thanks.
[06:05]  * parthm goes to resubmit ls-short-opts patch with fixes.
[06:14] <AfC> Someone in my office just said "Hudson doesn't directly support bzr" but I could have sworn I heard lifeless talking about how he'd been using Hudson of late for $something. Surely Hudson and Bazaar get along just fine, no?
[06:14] <lifeless> AfC: they lied
[06:15] <AfC> :)
[06:15] <AfC> ok
[06:15] <lifeless> AfC: it supports bzr as much as it supports CVS or svn
[06:15] <lifeless> install the plugin from the plugin admin page.
[06:15] <lifeless> Then Go Hit Them.
[06:15] <AfC> ouch
[06:15] <AfC> (the client just typed that)
[06:15] <AfC> lifeless: thank you very kindly Robert
[06:16] <lifeless> AfC: sorry :P
[06:16] <AfC> ha, no, he just typed "ouch" to convey his appreciation of your humour.
[06:16] <lifeless> oh phew :>
[06:16] <AfC> s'ok
[07:09] <sangi> while running serve-branches to install loggerhead,its throwing an error like No handlers could be found for logger "bzr"
[07:09] <Peng_> sangi: You said that earlier. It's not a problem.
[07:10] <Peng_> sangi: And serve-branches doesn't install Loggerhead, it just runs it.
[07:10] <sangi> Peng_, but it is not proceding
[07:10] <Peng_> sangi: What you pasted earlier looked fine.
[07:11] <sangi> Peng_, http://pastebin.com/ws0AwuGn
[07:11] <Peng_> sangi: Visit http://127.0.0.1:8080/ in a browser. It's not working?
[07:12] <sangi> Peng_, thanks, i am able to view it
[07:13] <Peng_> OK then.
[07:30] <parthm> really trivial docstring patch at https://code.launchpad.net/~parthm/bzr/trivial-doc-followup-549310-mandatory-whoami/+merge/24877
[07:30] <parthm> if someone can approve it i can land it. ... i don't want to approve myself as i am the one who proposed :)
[07:31]  * parthm looks at vila
[07:33] <parthm> vila: thanks.
[07:33] <lifeless> hi poolie
[07:35] <poolie> hi lifeless, parthm
[07:35] <parthm> poolie: hi
[07:48] <parthm> poolie, lifeless: i like the suggestion from lifeless to do 538868-message-for-heavy-checkout more broadly i.e. if revs to be pulled is > N.
[08:01] <vila> hi all
[08:10] <vila> parthm: what happened with your short-ls patch ? It landed in bzr.dev apparently...
[08:28] <GaryvdM> Hi vila
[08:29] <GungaDin> How do I un-add a file that hasn't been committed?
[08:30] <avu> GungaDin, bzr rm --keep <file>
[08:31] <GaryvdM> vila: Nudge for https://code.edge.launchpad.net/~jelmer/bzr/more-colo/+merge/23592
[08:32] <GaryvdM> vila: You reviwed it previously. Branch has been update since you last reviewed.
[09:14] <parthm> vila: hi. short-ls patch had test failures (test_help) ... i had a little difficulty (bug #576800) finding the test failure but its fixed and landed :)
[09:15] <vila> parthm: ok, thanks for the feedback
[09:15] <vila> GaryvdM: I'm looking into it
[11:37] <sangi> starting loggerhead throws an error like sudo: no passwd entry for loggerhead! Loggerhead is *not* running
[11:57] <Peng_> sangi: That sounds like an issue with however you're trying to start it, not Loggerhead itself.
[11:57] <Peng_> Err, um.
[11:58] <Peng_> I missed the "sudo".
[11:58] <Peng_> sangi: That has nothing to do with Loggerhead. From the error message, it sounds like you're trying to sudo to/from an account that either doesn't exist or doesn't have a password set.
[12:05] <sangi> Peng_, ok
[13:19] <bialix> hi
[13:24] <GaryvdM> Hi bialix
[13:24] <bialix> hi Gary
[13:24] <bialix> my last day online
[13:25] <GaryvdM> bialix: I'll try find you on Sunday
[13:25] <GaryvdM> I should be there by midday.
[13:27] <bialix> is somebody wants a souvenir from Ukraine -- shout
[13:30] <Tak> /Library/Python/2.5/site-packages/bzrlib/lockable_files.py:61: UserWarning: 'LockableFiles(<bzrlib.transport.local.LocalTransport url=file:///Users/levi/Code/mono-repo/monodevelop/.bzr/branch/>)' was gc'd while locked
[13:30] <Tak> problem? or no?
[13:30] <bialix> Tak: during selftest?
[13:30] <Tak> no, at runtime
[13:31] <bialix> not a critical problem, but it seems some code forgot to unlock
[13:31] <bialix> I'd say file a bug
[13:33] <Tak> meh, be nice if I had a stack trace
[13:34] <bialix> there is no stacj trace
[13:34] <bialix> it's a from garbage collector
[13:35] <bialix> some code locked the branch and then forgot to unlock
[13:35] <bialix> is it from regular bzr operations?>
[13:35] <bialix> or some plugin involved?
[13:42] <Tak> bzr-svn at least is involved
[13:43] <Tak> and bzrlib is being used, although I'm using the ui cmd classes as much as possible
[13:49] <lifeless_> Tak: so, its possibly a bug in bzrlib
[13:49] <lifeless_> Tak: or, and arguably more likely, a bug in your code. As bialix says, its happening from the object finaliser, so there isn't a stack to refer to to get a backtrace - or at least, not one related to the finalising code
[13:50] <Tak> oh, it definitely could be a bug in my code
[13:50] <Tak> I'm only locking manually in a few places, and I'm trying to always unlock in a finally block, but I could have missed something
[13:53] <Tak> I'm also manually deleting objects in a few places
[13:57] <lifeless> well, deleting won't unlock
[13:57] <lifeless> so be sure you've unlocked before you delete
[14:04] <Tak> yeah, I need to make sure I'm doing that
[14:38] <GaryvdM> bialix: Are you still here.
[14:38] <GaryvdM> bialix: If so, please check you email.
[14:38] <bialix> ack
[14:38] <bialix> which one?
[14:39] <GaryvdM> Re: Threads
[14:39] <bialix> guys, during the sprint, please use my gmail account
[14:39] <GaryvdM> bialix: Sent to ml
[14:39] <GaryvdM> Not sure where that goes to
[14:39] <bialix> I see the mail
[14:40] <bialix> GaryvdM: cool@
[14:40] <bialix> GaryvdM: cool!
[14:41] <bialix> I don't have time to read your code right now, sorry
[14:41] <GaryvdM> bialix: Ok np
[14:42] <bialix> but perhaps we have to carefully testing it on PyQt 4.4.x which is still default for windows
[14:42] <GaryvdM> Sure
[14:42] <GaryvdM> bialix: Did we not say we were going to upgrade that
[14:43] <bialix> we said, but 2.1 unlikely will be upgraded
[14:43] <bialix> only 2.2 and up
[14:43] <GaryvdM> bialix: Yes ok.
[14:43] <bialix> so I'd better double test
[14:44] <bialix> although based on your estimate we'll have 2.2 as defult
[14:44] <bialix> default
[14:44] <GaryvdM> bialix: Yes, Try for 2.3...
[14:44] <bialix> or rather target trunk2a of qbzr with threads to 2.2+
[14:45] <GaryvdM> Yes
[15:00]  * bialix has to go, hope will be online sometime tomorrow, or maybe not. see ya soon!
[15:09] <GaryvdM> luks: Hi. I sent a mail re threads in qbzr to the ml. I would really like it if you could take a look at that code. It is only 123 lines.
[15:10] <GaryvdM> luks: Any pit falls for picard would be valuable to.
[15:10] <GaryvdM> *from
[15:14] <GaryvdM> http://bazaar.launchpad.net/~garyvdm/+junk/thread-test/annotate/head:/main.py
[23:04] <javatexan> hey guys, I have totally messed up my local repos, is there a easy way to revert to the network version?  bzr pull is not doing it....
[23:33] <xnox> Is there bzr equivalent of git reflog?
[23:33] <xnox> i did a rebase of 10 commits and I did it wrong
[23:33] <xnox> I need to checkout the old head again but I don't know the revid.
[23:34] <xnox> Where can I look up all available revids in the repository?
[23:36] <fullermd> You can use 'heads' to try tracking it down, since it's presumably a dead head at this point.
[23:43] <lifeless> xnox: bzr heads --dead
[23:45] <xnox> fullermd, that gave me the current tip
[23:46] <xnox> lifeless, that worked
[23:46]  * xnox panic is over
[23:46] <xnox> thank you
[23:55] <a212901390231901> hmpf, sister has managed to forget her laptop again, so I have nothing to borrow to bring with me