[02:12] <milleja46> Can someone help me? I run the commands after setting bazaar up so i can push just to see if it works and i get: "Key 'Bazaar-NG branch, format 5\\n' already registered";Unable to load plugin 'weave_fmt' from 'C:\\Python27\\lib\\site-packages\\bzrlib\\plugins';bzr: ERROR: Don't know how to handle SSH connections. Please set BZR_SSH environment variable." how do i fix it?
[02:15] <milleja46> i set up bzr pagent and everything else and still it reports the no bzr_ssh var error
[02:15] <lifeless> how did you install bzr?
[02:16] <milleja46> i used the installer since i'm on windows
[02:33] <milleja46> then installed the rest as well, generated the keys, put the public key in launchpad, ran the commands and ran almost completly fine until i had to push/commit and now it reports those errors listed above
[02:34] <milleja46> would a restart help at all with this?
[02:37] <lifeless> I don't know :(
[02:37] <lifeless> spiv: ^ any ideas?
[02:58] <milleja46> anyone?
[03:00] <lifeless> milleja46: I don't use windows at all sorry, I'm very poorly placed to help :(
[03:00] <milleja46> lifeless: i can tell, i'm just trying to get my comp ready so i can help out with a project called openlp
[03:01] <milleja46> i guess i'll be back in the morning i gotta go to bed i've got school in the morning :(
[08:42] <poolie> hi all
[08:46] <vila> hello all !
[08:47] <vila> And to start the day with some food for thought, let it be said that I will probably stop to listen to you all because you're biasing my judgement : http://arstechnica.com/science/news/2011/05/following-the-crowd-undermines-its-wisdom.ars
[08:47] <vila> :-D
[08:51] <fullermd> So, if I ignore you while you ignore me, we both get smarter in an infinite recursion?
[08:59] <jam> morning all
[09:12] <poolie> hi jam
[09:12] <jam> hi
[10:01] <fullermd> Hey, neat, selftest actually runs through.  With some apparently spurious errors, but it finishes.
[10:18] <poolie> fullermd: on bsd?
[10:18] <fullermd> Yah.
[10:19] <fullermd> Stack of "ValueError: filedescriptor out of range in select()
[10:20] <fullermd> Spot-checked a few individually, and they ran fine.  So probably just something leaking in the whole run.
[10:24] <LarstiQ> fullermd: what was happening previously?
[10:25] <fullermd> Previous to what?
[10:25] <LarstiQ> fullermd: before it got to run through
[10:26] <fullermd> Oh.  Last time I tried (which was a long time ago; year or so?) a full selftest would never finish.  Deadlock threads partway through.
[10:27] <LarstiQ> ok
[10:27] <poolie> aoueaou
[10:28] <poolie> oops
[10:28] <fullermd> You forgot 'i' and sometimes 'y'.
[10:29] <Lo-lan-do> Hi all.  I understand there's a Bazaar sprint going on these days… could a few minutes be set apart to upload a newer bzr-svn to Debian so we can upgrade to 2.4 goodness?
[10:56] <spiv> Lo-lan-do: we just poked jelmer, he'll take a look
[10:57] <Lo-lan-do> Thanks :-)
[11:07] <jelmer_> hi Lo-lan-do
[11:08] <Lo-lan-do> Hi jelmer_ :-)
[11:10] <Lo-lan-do> I'm seeing a lot of commits in bzr-git too these days, I'm jumping up and down with impatience :-)
[11:13] <jelmer_> :)
[11:13] <jelmer_> I'm trying to get the whole bzr testsuite to pass against the foreign plugins - that should also help enormously with 'bzr serve --git'
[11:13] <milleja46> ok over the past several days after installing everything i should when i went to push i got the follwoing errors: ""Key 'Bazaar-NG branch, format 5\\n' already registered";Unable to load plugin 'weave_fmt' from 'C:\\Python27\\lib\\site-packages\\bzrlib\\plugins';bzr: ERROR: Don't know how to handle SSH connections. Please set BZR_SSH environment variable." how do i fix that?
[11:13] <milleja46> (i'm on windows)
[11:16] <milleja46> and i get it after running the command "bzr push --use-existing lp:~milleja46/openlp/milleja46"
[11:17] <jelmer_> milleja46, hi
[11:17] <milleja46> jelmer_: hi
[11:17] <jelmer_> milleja46, did you downgrade bzr recently perhaps?
[11:17] <jelmer_> milleja46, it looks like you are using a part of the a new bzr with an older version of bzr
[11:17] <milleja46> jelmer_: no i have version 2.3 or whatever the latest version is
[11:18] <milleja46> should i just try un-installing and reinstalling?
[11:19] <jelmer_> milleja46: it seems like you have at least something that comes from a newer version - weave_fmt was added in bzr 2.4 only
[11:20] <milleja46> well why does it reference that in 2.3.1?
[11:21] <milleja46> (that's the version i have since that was the latest version i saw on site
[11:25] <milleja46> well if weave_fmt is only in 2.4 i sure see it in 2.3.1 when i go to the plugins folder under bzrlib in the site-packages folder in lib
[11:26] <jelmer_> milleja46, How did you install bzr?
[11:26] <milleja46> by going to the site, and downloading the py2.7 installer for bzr 2.3.1
[11:27] <LarstiQ> mgz: I don't know what the policy is on discussing things on a merge proposal
[11:28] <LarstiQ> mgz: so, pypy -c "import codecs; codecs.lookup('EUC-JP')" gives LookupError: unknown encoding: EUC-J
[11:28] <LarstiQ> ah, but not under pypy-nightly
[11:28] <LarstiQ> progress!
[11:29] <milleja46> jelmer_: though oddly enough i could do everything else to get it set up just not this for what reason i have no clue
[11:31] <jelmer_> milleja46, you could try removing the weave_fmt directory, but I'm still not sure where it could come from
[11:33] <LarstiQ> jelmer_: though that doesn't seem to be he reason the ssh connection won't work?
[11:33] <LarstiQ> milleja46: does http://howto.praqma.net/bazaar/bazaar-on-windows help with setting up ssh?
[11:35] <jelmer_> LarstiQ: I hadn't even looked at that yet :) Yeah, it won't help with the ssh issue.
[11:35] <jelmer_> Lo-lan-do, a new bzr-svn is planned, with matching debian upload
[11:41] <milleja46> funny thing is i have putty set up and my private key linked to it and everything yet it doesn't work like it should.....
[11:43] <LarstiQ> milleja46: ok, so why not?
[11:43] <milleja46> it just keeps reporting the the bzr_ssh var needs to be set
[11:43]  * LarstiQ nods
[11:43] <LarstiQ> milleja46: what does .bzr.log say about this?
[11:44] <LarstiQ> milleja46: `bzr version` reports its location
[11:44] <LarstiQ> milleja46: "Bazaar log file: /home/larstiq/.bzr.log" in my case, don't know where it will be on Windows, but bzr knows :)
[11:45]  * Lo-lan-do hugs jelmer_ 
[11:47] <milleja46> as soon as pastebin loads it i'll paste the link to it so you can see there are quite a bit of errors aparently
[12:01] <LarstiQ> milleja46: how's that going?
[12:01] <milleja46> not very well i think pastebin is down....
[12:02] <mgz> there are many pastebins, try another one.
[12:02] <LarstiQ> milleja46: paste.pocoo.org for example
[12:04] <mgz> larstiq: so, if your remaining os lock unexpected success just a platform detection issue?
[12:05] <mgz> or is there actually something incorrect in the locking code?
[12:09] <LarstiQ> mgz: good question. It works under python, but not under pypy.
[12:11]  * LarstiQ has a look at the test code
[12:13] <LarstiQ> I so do not like locking code
[12:15] <mgz> hm, if you just comment out that check in assertCheckoutStatusOutput, what does the test do?
[12:15] <mgz> doesn't look like a sys.platform issue, but likewise I'd expect *lots* more failures if the locking semantics really were different under pypy
[12:18] <LarstiQ> unexpected return code, hmm
[12:19] <LarstiQ> time to break out pdb
[12:19] <milleja46> dang all of thse paste sites are taking a long time to load the page after i click the paste button i'm on the ocoo.org one righ tnow
[12:20] <LarstiQ> how big is the thing you're trying to paste?
[12:21] <LarstiQ> milleja46: we only need the output of one run
[12:23] <milleja46> like 1.96 mb
[12:30] <milleja46> but after i enter the captcha it just takes me to a new paste
[12:30] <LarstiQ> milleja46: strip that down
[12:32] <LarstiQ> milleja46: if you don't want to manually figure out which part to paste, move the file out of the way, do one bzr run so you get the BZR_SSH message, and then paste the file
[12:32] <LarstiQ> mgz: which at that point should contain less than, say, a 100 lines
[12:32] <LarstiQ> ehm
[12:32] <LarstiQ> well know
[12:32] <LarstiQ> now
[12:33] <LarstiQ> mgz: back to you then, it is failing in the L L L case
[12:39] <mgz> hm.
[12:41] <LarstiQ> mgz: specifically, under pypy `bzr info -v lightcheckout` returns info output, while without it complains it couldn't acquire a lock
[12:41] <LarstiQ> so then retcode = 0 instead of the expected 3
[12:42] <LarstiQ> which trips up the self.assertEquals(retcode, result, message='Unexpected return code') in _run_bzr_core()
[12:43] <LarstiQ> although I don't quite get that
[12:45]  * LarstiQ detaches from irc for a while
[12:49] <santagada> LarstiQ, hi
[12:51] <LarstiQ> santagada: hey
[12:58] <LarstiQ> santagada: how did the run go?
[13:01] <santagada> LarstiQ, not good, just commented on the ticket
[13:01] <santagada> http://paste.pocoo.org/show/391764/
[13:01] <santagada> and it was using 1.9gb of ram so my machine was unusable
[13:03] <LarstiQ> santagada: ouch, that needs to be resolved
[13:04] <mgz> so, I've got a branch that may help that side as well
[13:04] <santagada> LarstiQ, I think there is a leak on bzr testsuite because pypy has been used with very big projects without signs of leaking memory
[13:05] <mgz> currently we keep testcases alive for the whole run
[13:05] <santagada> ah
[13:05] <mgz> which is pypy uses a lot of memory for various things might... getbig
[13:05] <mgz> if you try a run on <lp:~gz/bzr/cleanup_testcases_by_collection_613247> which I updated to bzr.dev yesterday, you may have more luck
[13:06] <santagada> pypy should be using less memory than cpython unless you were using __slots__ in cpython
[13:06] <mgz> it uses more memory for jit
[13:06] <mgz> and if we're keeping lots of test methods alive...
[13:06] <spiv> santagada: it depends
[13:07] <santagada> python objects are smaller, as if they were all using __slots__
[13:07] <mgz> it may not be smart enough to free generated code when it's not needed any more
[13:07] <santagada> pypy jit uses some memory, but it is a more or less fixed amount and it does release unused compiled loops
[13:07] <santagada> mgz, it does... well there could always be a bug somewhere :)
[13:07] <santagada> but it should be releasing unused memory
[13:08] <santagada> I think there is cases where if you mutate your __dict__ then the objects get as big as cpython ones
[13:08] <LarstiQ> santagada: I did a cpython run under memusage.py yesterday, and it got up to 500Mb
[13:08] <santagada> because it has to actually create a dict for it
[13:09] <LarstiQ> https://codespeak.net/svn/user/arigo/hack/misc/memusage.py
[13:09] <LarstiQ> that is
[13:09] <santagada> maybe it is a mixture of a bug/missing feature on pypy that bzr testsuite is using
[13:10] <santagada> LarstiQ, also if you want me to run the tests again I should do it on your branch
[13:10] <LarstiQ> santagada: my branch got merged into bzr.dev
[13:10] <santagada> ahh
[13:10] <santagada> so lp:bzr should have it right?
[13:11] <santagada> I don't know what bzr.dev is
[13:11] <LarstiQ> santagada: yeah, lp:bzr
[13:11] <LarstiQ> santagada: sorry, I'm stuck in my terminology
[13:12] <santagada> mgz, you are going to land your changes on lp:bzr today? because I can rerun the tests later if you are
[13:12] <LarstiQ> santagada: r5893 to be precise
[13:12]  * LarstiQ is going to give mgz's branch a spin
[13:13] <LarstiQ> if it works, I can actually run the testsuite to completion under pypy
[13:14] <santagada> wish I knew why it ran so slowly on my machine
[13:14] <santagada> its a core 2 duo with 4gb ram so it should be faster
[13:15] <LarstiQ> santagada: iirc subprocess is slow on pypy, so that would explain why the blackbox tests take long
[13:15]  * LarstiQ is now at 958/1388 blackbox tests in 100 minutes
[13:15] <LarstiQ> on a 1.5gb ram Atom N270
[13:16] <santagada> uhmm that is true
[13:16] <santagada> I don't remember why it is slow
[13:20]  * LarstiQ merges bzr.dev into cleanup_testcases_by_collection_631247 and gives it another go
[13:30] <LarstiQ> hi abentley
[13:31] <abentley> LarstiQ: Hi.
[13:31] <LarstiQ> mgz: I'll wait till this run is done before crying victory, but at this point pypy has run 600 blackbox tests in under 10 minutes. That is incredibly much faster than without your branch.
[13:43] <LarstiQ> mgz: so, the previous pypy run did 958 blackbox tests in 100 minutes, with your branch it is 1388 in 19. Consider me in favour of merging it.
[13:44] <Lo-lan-do> Hear, hear.
[13:54] <abentley> It's nice that we're getting to a place where we can support pypy, but isn't pypy supposed to be fast?
[13:54] <mgz> larstiq: that's great post-lunch news
[13:57] <mgz> abentley: you'd need his numbers for those tests on cpython without extensions compiled for a sane comparison
[13:58] <abentley> mgz: Ah, unfair comparison, then.
[13:58] <santagada> and pypy is not very fast in unittests
[13:58] <santagada> I think the biggest advantage for bzr would be startup time in most cases
[13:59] <santagada> and then for long merges the jit would help also
[14:00] <santagada> s/long merges/any slow operation that is somewhat cpu bound/
[14:00] <LarstiQ> abentley: benchmarks to see how pypy without extensions compares with cpython with extensions have yet to be done
[14:00] <santagada> benchmarking before making the tests pass also don't make much sense
[14:01] <santagada> a broken bzr could be easily faster than a working bzr :)
[14:02] <LarstiQ> santagada: although it wouldn't hurt to already set the environment up so it can roll when we get there
[14:05] <santagada> LarstiQ, that would be great
[14:06] <jam> santagada, abentley, LarstiQ: And we'd have to rewrite the GroupCompress code to actually do the same thing in pure python
[14:06] <jam> at the moment it runs an entirely different algorithm that just generates compatible streams
[14:07] <LarstiQ> right
[14:08] <santagada> when everything is working there are many venues to go to get more performance on pypy
[14:20] <spiv> Also, we've spent a considerable amount of time and effort tuning bzr for CPython.  So a completely fair comparison would involve doing the same for pypy.
[14:23] <LarstiQ> if we're lucky pypy will be faster without doing anything, but I'm not holding my breath
[14:25] <poolie> jlemer can you answer https://answers.launchpad.net/bzr/+question/158196
[14:33] <LarstiQ> poolie: did you manage to find ianc's old homedir btw? https://launchpad.net/bzr-usertest still points to a non-existing link
[14:36] <poolie> ah ok
[14:38] <poolie> LarstiQ: can't you getto https://code.launchpad.net/~bzr/bzr-usertest/trunk ?
[14:39] <poolie> i mean can you?
[14:39] <poolie> oh, you mean just the link in the description
[14:39] <poolie> i'll see about that
[14:39] <LarstiQ> poolie: sorry, yes
[14:40] <poolie> no you were clear
[14:40] <poolie> i thought someone else asked me about access to one of his branches
[14:41] <poolie> are you going to run it?
[14:41] <poolie> http://people.canonical.com/~mbp/ianc-plugins/usertest/doc/
[14:44] <poolie> and i updated the page too
[14:44] <LarstiQ> poolie: I would like to have a go at benchmarking with pypy, yes
[14:46] <LarstiQ> poolie: thanks!
[14:50] <poolie> np, thanks
[14:52] <poolie> ?
[14:52] <LarstiQ> abentley: fwiw, doing the same blackbox test run but now with cpython instead of pypy takes 14.5 minutes instead of 19
[14:52] <LarstiQ> poolie: hmm?
[14:54] <poolie> oh, john was saying "yay" that his delta-update patch is finished
[14:54] <poolie> i wonder if we can make usertest draw graphs through R
[14:54] <jam> poolie: if someone wants to go through the diff with me, I do realize 1400 lines is a bit long
[15:03] <abentley> LarstiQ: Cool!
[17:25] <spiv> vila: lp:~spiv/bzr/import-tariff-test-subprocess-deadlock should fix that deadlock
[17:27] <vila> spiv: thanks
[17:27] <vila> spiv: ... but no :-/
[17:34] <spiv> vila: drat
[17:52] <LarstiQ> mgz: what should be done to get cleanup_testcases_by_collection_613247 moving?
[18:08] <mgz> larstiq: vila suggested last night that I try and split it up into smaller bits
[18:11] <mgz> larstiq: the main complication is ensuring we don't regress is hard
[18:11] <mgz> okay, we're heading off globewards nowish
[19:06] <arnetheduck> hi, I'm playing around with the log -m option and was thinking about extending it to also match committer and author(s)
[19:07] <arnetheduck> the other option would be to add another option that only matches committer, one for author etc etc...
[19:08] <arnetheduck> does anyone have any opinion?
[19:08] <jam> arnetheduck: offhand, I think it would be ok to just make -m match it. I don't think you'll get spurious matches
[19:13] <arnetheduck> indeed, it seems more simple both to implement and above all for the user
[19:13] <jam> arnetheduck: right.
[19:13] <jam> the only question is if it should match the *email* which can cause more spurious matches because of domain names. But I'd probably still say go for it
[19:15] <arnetheduck> the other option I considered was maybe to use some sort of property specifiers to only match a certain field (-m message=xxx or -m committer=abc) and match all fields if none are specified
[19:15] <arnetheduck> but that of course complicates matters...
[19:16] <jam> yeah
[19:16] <jam> not worth the mental overhead
[19:16] <arnetheduck> in any case, do you think a patch in this direction would be interesting for upstream?
[19:16] <jam> yes
[19:18] <arnetheduck> also, I tried looking for an existing bug but the obvious keywords (log, author etc) yield a massive list - does anyone maybe recall seeing a bug for this? (I recall a posting on the bzr mailing list where I lurk =)
[19:32] <jam> arnetheduck: I don't know of a specific bug about that.
[19:39] <arnetheduck> jam: thanks for the input
[19:45] <arnetheduck> is it normal that the self test takes close to an hour? also, is there any (simple) way of knowing which tests pass through a particular function except guessing by test name?
[20:00] <jam> arnetheduck: that is about right. I've seen it go faster on better hardware, and we have "bzr selftest --parallel=fork" if you have multiple cpus
[20:07] <jam> LarstiQ, mgz: my attempt at helping you out: https://code.launchpad.net/~jameinel/bzr/2.4-exc-info/+merge/61630 https://code.launchpad.net/~jameinel/bzr/2.4-613247-cleanup-tests/+merge/61636 https://code.launchpad.net/~jameinel/bzr/2.4-613247-test-cases/+merge/61637
[20:07] <jam> I'm guessing that isn't the #1 important bits, which is the changes to TestUtil and some of the other helper functions
[20:08] <jam> but it was the bits I felt I understood.
[20:08] <jam> and it should at least reduce your divergence vs bzr.dev
[20:42] <jam> arnetheduck: most tests are grouped by the module they effect, so "bzr selftest -s bt.test_log -s bb.test_log" is going to handle most of the 'test_log' cases
[20:42] <jam> they correspond to "bzrlib/tests/test_log.py" and "bzrlib/tests/blackbox/test_log.py"
[20:42] <jam> bt => bzrlib.tests bb=>bzrlib.tests.blackbox
[21:01] <LarstiQ> jam: thanks!
[21:01] <LarstiQ> jam: and oooh, I didn't realise you could specify -s multiple times
[21:21] <milleja46> Ok can someone help me? when i run the push command on windows i get the following error: ""Key 'Bazaar-NG branch, format 5\\n' already registered";Unable to load plugin 'weave_fmt' from 'C:\\Python27\\lib\\site-packages\\bzrlib\\plugins';bzr: ERROR: Don't know how to handle SSH connections. Please set BZR_SSH environment variable."
[21:21] <milleja46> and here's the log: http://paste.pocoo.org/show/392030/
[21:28] <LarstiQ> ooh, a log
[21:28] <LarstiQ> milleja46: you went offline unexpectedly earlier
[21:28] <milleja46> LarstiQ: i didn't randomly go off i had to go to school i'm still a high school junior :P
[21:29] <LarstiQ> milleja46: a note would have saved me the line I was typing to you ;P
[21:29] <LarstiQ> anyway
[21:29]  * LarstiQ looks at the log
[21:29] <milleja46> did i mention that i'm using the python 2.7 installer for bzr?
[21:30] <LarstiQ> milleja46: I think so
[21:31] <milleja46> LarstiQ: i'd take it there has to be some kind of issue for it to be 1.96 mb in size
[21:31] <LarstiQ> milleja46: as I was saying then, we only need the last bit of it
[21:32] <LarstiQ> milleja46: it is a debug log all bzr operations write to
[21:32] <LarstiQ> milleja46: so posting the entire log is a bit overkill
[21:32] <LarstiQ> milleja46: but if you want, you could move it out of the way, run bzr, and upload the new log formed that way with only 1 run
[21:33]  * LarstiQ needs to look up what the regular setup on windows with putty is
[21:33] <milleja46> LarstiQ: ok i'll try that just let me close out all my bzr stuff :)
[21:33] <LarstiQ> milleja46: for next time, I've got the info I was after now
[21:34] <milleja46> LarstiQ: good and sorry about that...ohand the specific command i ran was "bzr push --use-existing lp:~milleja46/openlp/milleja46" if i didn't mention it earlier
[21:34] <LarstiQ> milleja46: can you set BZR_SSH=paramiko ?
[21:35] <milleja46> LarstiQ: where would i set that and do i have to get paramiko? i don't recall anything called paramiko
[21:35] <LarstiQ> milleja46: paramiko should be bundled with the installer
[21:35] <milleja46> ahh
[21:36] <LarstiQ> milleja46: hmm, iirc there is an environment variable setting in System somewhere
[21:36] <LarstiQ> milleja46: or to test, on a commadline, 'set BZR_SSH=paramiko' I think
[21:36] <LarstiQ> and then run bzr
[21:37] <milleja46> bzr: ERROR: Unrecognised value for BZR_SSH environment variable: paramiko
[21:37] <LarstiQ> really, hrmf
[21:37] <milleja46> LarstiQ: so i guess i need to figure out why paramiko isn't known
[21:39] <LarstiQ> milleja46: try BZR_SSH=plink?
[21:39] <milleja46> ok next error: bzr: ERROR: Unable to connect to SSH host bazaar.launchpad.net; [Error 2] The sy
[21:39] <milleja46> stem cannot find the file specified
[21:40] <milleja46> i've got the keypair and gave launchpad the public one and have both saved on my system
[21:41] <milleja46> LarstiQ: would i happen to possibly be missing the private one being set somewhere?
[21:42] <milleja46> i've got putty on my computer
[21:42] <milleja46> as well as that pagent stuff
[21:43] <LarstiQ> milleja46: can you paste the traceback corresponding to that bazaar.launchpad.net error?
[21:43] <milleja46> LarstiQ: yea hold on
[21:43] <LarstiQ> it _sounds_ like a dns problem
[21:44] <milleja46> http://paste.pocoo.org/show/392050/
[21:46] <LarstiQ> right
[21:46] <LarstiQ> milleja46: does ping bazaar.launchpad.net work?
[21:47] <milleja46> yes
[21:47] <LarstiQ> hmm
[21:48] <LarstiQ> milleja46: how about, 'plink bazaar.launchpad.net' ?
[21:49] <milleja46> LarstiQ: umm, how would i do that one?
[21:50] <LarstiQ> milleja46: from commandline too
[21:50]  * LarstiQ is looking at http://the.earth.li/~sgtatham/putty/0.58/htmldoc/Chapter7.html
[21:54] <milleja46> ahh now that i added it to the path variable it works...but i get this error after giving it my login as stuff: FATAL ERROR: Disconnected: No supported authentication methods available
[21:54] <LarstiQ> milleja46: that sounds like it isn't trying your key
[21:56] <milleja46> maybe this is why i opened up the keys Pagent knows and there is nothing on the list
[21:56] <LarstiQ> milleja46: that would not help, no :)
[21:57] <milleja46> LarstiQ: well i add the key then it says: "No shells on this server"
[21:58] <milleja46> when i re-run the plink command on bazaar.launchpad.net
[21:58] <milleja46> i mean
[21:59] <LarstiQ> milleja46: that's good!
[21:59] <LarstiQ> milleja46: now try bzr again
[22:00] <LarstiQ> milleja46: (bazaar.launchpad.net doesn't let you log in to a shell, but trying to is useful to see if keys etc are all set up)
[22:01] <milleja46> LarstiQ:well so close->"Key 'Bazaar-NG branch, format 5\\n' already registered";Unable to load plugin 'weave_fmt' from 'C:\\Python27\\lib\\site-packages\\bzrlib\\plugins';Using default stacking branch /+branch-id/40441 at lp-85209680:///~milleja46/openlp;bzr: ERROR: KnitPackRepository('lp-85209680:///+branch-id/40441/.bzr/repository')is not compatible with CHKInventoryRepository('lp-85209680:///~milleja46/openlp/milleja46/.bzr/repos
[22:01] <LarstiQ> aha
[22:03] <milleja46> http://paste.pocoo.org/show/392060/
[22:04] <LarstiQ> milleja46: you're not pasting the relevant things, but in this case I know what is going on
[22:04] <LarstiQ> milleja46: so, the problem is that your branch is in a newer, unfortunately incompatible format
[22:04] <milleja46> well it's the last bit of what pops up after sending it
[22:04] <milleja46> LarstiQ: just ran it again it's working i think!
[22:04] <LarstiQ> really?
[22:05] <milleja46> it looks like there's some transfer rates popping up on screen
[22:05]  * LarstiQ wouldn't expect that to work with either 1) lp:openlp being upgraded 2) not stacking on it
[22:05] <LarstiQ> milleja46: you'll note that in the the log it also mentions what command you ran
[22:06] <milleja46> LartsiQ: well i haven't updated my branch in a few days...
[22:06] <LarstiQ> and above that a timestamp
[22:06] <mwhudson> spiv: btw, i get an email every day with the list of bzrlib docstrings that aren't valid reST :)
[22:06] <LarstiQ> milleja46: for example, 0.585  bzr arguments: [u'info', u'lp:~milleja46/openlp/milleja46']
[22:06] <mwhudson> i guess that should be 'got' now
[22:07] <milleja46> this is what i see:   6690kB    34kB/s \ Fetching revisions:Inserting stream:Estimate 38703/68556
[22:07] <LarstiQ> milleja46: so everything from the timestamp (Thu 2011-05-19 23:03:20 +0200 in that case) to the next blank line; timestamp is the relevant bit
[22:08] <LarstiQ> milleja46: on a push?
[22:08] <milleja46> LarstiQ: yea
[22:08] <LarstiQ> milleja46: ok, let's wait and see then :)
[22:09] <milleja46> yea this is gonna take awhile the branch is 24.6 mb
[22:10] <milleja46> and i've really and truly made no revisions yet
[22:17] <LarstiQ> milleja46: ah, that sounds like it fell back to not using stacking then
[22:17] <LarstiQ> milleja46: maybe you should ask the openlp people to upgrade lp:openlp
[22:18] <milleja46> LarstiQ: what do you mean upgrade it?
[22:19] <LarstiQ> milleja46: `bzr upgrade lp:openlp` should do the trick, with any bzr 2.0 or higher
[22:29]  * LarstiQ goes to sleep
[22:30]  * milleja46 hopes this works
[23:16]  * milleja464 almost had it...then lost connection.....
[23:56] <milleja46> LarstiQ: thanks it finally worked, now just to start learning some PyQt and hopefully i can make a change that i need to soon