/srv/irclogs.ubuntu.com/2008/03/17/#bzr.txt

moebius_(btw, the error is when doing a "bzr branch" using any bzr+http:// URL scheme)00:01
nxvlis someone already working on git2bzr convertion??00:01
poolienxvl: yes, there's a fastimport reader, see list00:03
pooliemoebius_: i don't recall it00:03
pooliecan i suggest trying 1.3rc1 though00:03
james_wmoebius_: it seems like a bug to me, so please file it with the full traceback. If you can test with 1.3rc1 that would be great.00:07
james_wnxvl: hi00:07
nxvljames_w: hi!00:08
james_wnxvl: how are you?00:08
nxvljames_w: fine, finishing with all my papers for attending to UDS and looking for a python project to work on :P00:08
nxvljames_w: also waiting for the mentors list for GSOC being published tomorrow :P00:09
james_wnxvl: you're going to UDS? Great!00:09
james_wyou know bzr is a python project?00:09
nxvljames_w: yep, that's why i'm here :D00:10
james_wah, great!00:10
nxvljust starting to read the documentation and browsing the code00:10
james_wnxvl: are you interested in git->bzr conversion?00:10
nxvljames_w: yep00:11
james_wI think it would make a great project.00:11
nxvljames_w: i find it a nice and not so hard feature to start with00:11
james_wwell, a few parts will be a bit tricky in terms of learning the bzr API.00:12
nxvlbtw, is bzr going to be part of GSCO?00:12
nxvljames_w: yep, but is easier that learn the bzr code ;)00:12
poolienxvl: no, we're going to do our own student projects through canonical00:12
nxvlthan*00:12
poolieare you interested00:12
james_wthe rest will just be coming up with ways to not store the 300MB source repository in memory as you go.00:12
nxvlpoolie: yes of course00:12
nxvlpoolie: is there already a wiki or web where i can look for those?00:13
james_wpoolie: nxvl is a cool Peruvian LoCo team member for Ubuntu.00:13
james_wHe's also involved in MOTU.00:13
james_wand loads of other stuff I'm sure :)00:13
* nxvl HUGS james_w 00:13
* james_w hugs nxvl back00:13
poolie:)00:14
moebius_james_w: I will test 1.3rc1 and fill the bug, thanks00:15
james_wmoebius_: great, thanks.00:15
james_wnxvl: I don't think there's any sort of list or anything yet, I'm not sure how far along the planning is.00:16
james_wnxvl: I'm sure there is a bunch of project ideas lurking around somewhere.00:16
nxvljames_w: on the bzr list there is some info, i have just found it, but is more on fastimport on windows :S00:16
james_wthat's just one problem someone bought up, we're keen to have it work on every platform.00:17
nxvljames_w: isn't so hard with python00:18
nxvl:P00:18
james_wthat's the idea.00:18
james_wI can't find a list of project ideas on the wiki, if you are keen for others I'm sure we can generate some.00:19
nxvlmm00:19
nxvli have just had it open00:19
nxvllet me check my history00:19
pooliethe SummerOfCode page is old, I just renamed it00:19
james_wthough I think the fast-import one is great, as it is a useful tool, not too involved with the core, but would possibly involve adding some changes to core code to make it more efficient.00:20
nxvljames_w: http://bazaar-vcs.org/SummerOfCode200700:20
james_wah, I only looked at the top, so I didn't realise the list was there.00:20
moebius_james_w: 1.3rc1 works for me doing exactly the same operation as before00:21
pooliemoebius_: meaning it reproduces the bug, or it works?00:21
moebius_it works00:21
pooliegreat00:21
moebius_no error with 1.3rc100:22
moebius_the branch op gets done ok00:22
james_wmoebius_: great, thanks for testing.00:22
lifelessdato: bzr-hookless-email is quite slow for me; I'll look at it in my copious spare time00:22
lifelessabentley: ping00:22
nxvljames_w: that happends here also, but when i was looking for what has been done last year i found the list :D00:22
moebius_no problem, i like to help with those things00:22
moebius_and bzr is so good it deserves some love :D00:22
james_wmoebius_: bzr loves you too :-)00:22
moebius_should I report the bug in the 1.2 series?00:23
james_wI don't think it's likely to get fixed as 1.3 is so close, so the only reason would be documentation in case anyone else fixes it.00:24
james_wmoebius_: if you want to report it I would be happy to mark it fixed in 1.3 with an explanation.00:24
pooliemoebius_: generally once we've made a new release we don't worry about older bugs00:24
poolieas james says00:24
moebius_ok, I will report it, just for documentation00:25
moebius_also, if someone hits the same bug, will know he can use 1.300:25
nxvlwhat is bzrk?00:27
james_wI think it means bzr-gtk00:28
nxvloh! ok00:28
lifelessbzrk is 'bzr viz'00:28
james_whi lifeless00:28
nxvljames_w: thx00:29
james_wlifeless: I have both the bzr and git emacs trees here and guess which is smaller?00:30
james_wyou rock!00:30
poolieway to go00:30
james_wapparently the git one has some merge information added, so I don't know how much that will have added00:31
james_walthough the git log >/dev/null time is pretty amazing.00:31
lifelessjames_w: which ?00:31
james_wlifeless: bzr of course :)00:31
nxvllifeless: thnx00:31
lifelessjames_w: thats pretty surprising00:32
lifelessnice, but suprising00:32
poolieif they've recorded merges from other branches and we have not that might be part of it00:32
james_w292M/333M00:32
lifelesswe are rather bad with merges today00:32
pooliewell, that may be down to the way the import was done00:33
james_walthough there are perhaps more branches in git, so I may not be being fair.00:33
james_wI didn't look properly last time, so I thought there was only one.00:34
awmcclainjames_w: Remember yesterday when I was asking you about bzr configuration values? Seems like branch.conf doesn't work for bzr-email either.00:34
james_wawmcclain: hmm, sorry about that.00:34
lifelessawmcclain: hum, I consider that a bug. Can you please file a bug on bzr-email about that00:35
awmcclainEither that or it DOES work and I'm don't have it configured somewhere else.00:35
awmcclains/I'm/I00:35
lifelesslets assume you've done it right00:35
awmcclainI'm going to try a conf var in a user directory next00:36
lifelessI'll gather debugging stuff as needed via the bug00:36
james_wpoolie: thanks for the tips on that debugging.00:36
awmcclainIs there any documentation about bzr configuration stuff?00:36
lifelessthe user guide00:36
james_wpoolie: did you see John's bug about upgrading bzr.dev to -subtree? It looks like it may be the same thing.00:36
poolienot yet00:36
james_wawmcclain: http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html#configuring-bazaar00:37
moebius_I believe the bug report should be ok: https://bugs.edge.launchpad.net/bzr/+bug/20303100:41
ubotuLaunchpad bug 203031 in bzr "Branching over bzr+http fails with AttributeError" [Undecided,New]00:41
moebius_haha, the bot catched me00:41
moebius_xD00:41
moebius_it is my first bug report, so please do not spank me if it is not well done00:42
pooliemoebius_: you can mark it fixreleased if you like00:49
james_wI'll do it.00:51
ubotuNew bug: #203031 in bzr "Branching over bzr+http fails with AttributeError" [Undecided,New] https://launchpad.net/bugs/20303100:51
james_wmoebius_: thanks00:52
james_wmoebius_: and it was a good bug report, make them all like that and you won't have any problems :-)00:52
moebius_james_w: great! now time to sleep... it's somewhat late here in europe :D00:53
james_wmoebius_: indeed it is. I must sleep too, thanks for the reminder.00:54
james_wnight all.00:54
moebius_i could say the same, good night and be happy.00:55
pooliejames_w, nxvl: i posted http://bazaar-vcs.org/StudentProjects00:59
=== poolie changed the topic of #bzr to: http://bazaar-vcs.org/ | Bazaar 1.3rc1 available for testing |
=== poolie changed the topic of #bzr to: http://bazaar-vcs.org/ | Bazaar 1.3rc1 available for testing | http://launchpad.net/bzr/1.3/1.3rc1
* poolie looks at bzr ssh locking bugs with jml01:22
lifelessin soviet russia ssh lock bugs you01:24
poolieit does bug me01:25
lifelessare you in soviet russia?01:27
lifelessknit proposal sent to list for rfc01:27
Odd_Blokejames_w: Could you push your branch implementing the workaround option for bug 172657 to LP and link it to the bug?01:28
ubotuLaunchpad bug 172657 in bzr "bzr status after merge slower with packs" [Medium,Fix committed] https://launchpad.net/bugs/17265701:28
lifelesspoolie: branch made01:35
pooliethank01:37
poolielifeless: i'm suggesting we should fix the bzr+ssh leftover locks bug by making the client control polling for the lock, rather than the server01:41
pooliewhat do you think?01:41
lifelesswhat happens today?01:42
lifelessDoes the smart server verb not disable polling ?01:42
lifelesshow often do we poll ?01:42
pooliei believe the server does the polling, from what jml tells me01:46
pooliewill check01:47
lifelessso01:48
lifelessif we poll 1/sec01:48
lifelessthen I think its ok for the client to do it, but not optimal resource wise01:48
lifelessif we poll 5/sec, then server load will be even more significant01:48
lifelessI don't see why the client should do network traffic to ask the server 'are we there yet'01:49
poolieit's less than once per second01:49
lifelessis the root problem 'client disconnections are not noticed' ?01:49
jmlno.01:49
jmlinterrupting a bazaar client that's waiting for a lock does not cause a client disconnection01:50
jmlbecause it doesn't interrupt the ssh process.01:50
lifelessjml: well, sounds like its the same thing at the top level - the bzr client has gone away, but the server doesn't know this01:51
lifelessjml: and the client has gone before the lock was acquired01:51
jmlyes, that's right.01:51
poolielifeless: it's partly that, and partly that at the moment the client gets no indication that anything is happening01:52
poolieso, we can't display progress to the user for example01:52
lifelessso the race condition is the window between 'rpc_send obtain_lock' and 'rpc_reply lock_obtained' being sufficient for the client to go away.01:52
poolienor can it cancel the request once it's sent for that matter01:52
poolielifeless: that's ok; it's comparable to a dangling lock over another protocol01:52
lifelesspoolie: sure, I'm just making sure I have a clear understanding01:53
lifelesspoolie: if I said what I think about some imaginary situation, it wouldn't help much :)01:53
jml(user runs bzr push, bzr push waits for lock, user hits control-c, bzr dies, ssh keeps running, user runs break-lock, stale ssh acquires the lock)01:53
lifelessjml: (user runs bzr push, push gets lock, user hits contorl-c, bzr dies, ssh keeps running ?) ?01:54
jmlthat's the use-case that I'm particularly interested in01:54
lifelessjml: I'm postulating that actually there is a significantly broader group hitting this than you realise01:54
jmllifeless: not sure what happens in that situation. easy to find out though.01:54
lifelessjml: e.g. what is special about lock waiting that stops bzr cleaning up ssh01:54
jmllifeless: maybe. what's the significance if that's so?01:55
lifelessjml: it means that the folk seeing the problem are not people waiting on lock contention01:55
lifelessjml: but rather folk seeing little/no progress on push, or interrupting push01:55
jmllifeless: that's not the reported bug.01:55
* jml does an experiment or two01:56
lifelessjml: I know its not the reported bug. But imagine for a second that everyone that reports the bug has actually hit it first on push on the branch, and then when they try to diagnose they have their own stale lock already present.01:56
lifelesspoolie: so, what do I think. I think several things.01:57
lifelesspoolie: I think that bzr's client code is already correct re: lock cleanup, so really fixing this ssh handling is the most important thing to do, as it smells like the end of a thread of related issues to me.01:58
lifelesspoolie: I think that repeated network round trips to poll is rather ugly, as event based operations are so much cleaner, requests to the server have a cost, and polling designs are well known to scale poorly.01:58
lifelesspoolie: I think the lack of UI feedback is fixable without restoring to network polling; just displaying the progress bar immediately with 'obtaining lock' would do it for instance.01:59
lifelessand only doing that on non-local urls seems reasonable to me.01:59
jmlhitting ctrl-c during push kills the ssh process01:59
jmlat least, it does when I hit it :)01:59
lifelessso, I consider the ssh not being killed during lock obtaining a severe bug02:00
lifelessits got all sorts of implications02:00
pooliekilling the ssh client is not a reliable way to avoid this02:00
lifelesspoolie: indeed; removing the network is the only way :)02:00
* jml starts hacking on the ansible02:01
jml(imagine the TF2 ping times!)02:01
lifelesspoolie: you could as an immediate quick fix just set the poll time to 0 on the smart server verb02:03
lifelesspoolie: I think this is not really a good idea, but it would stop the polling on the server side02:03
lifelesse.g. just doing this on launchpad, today, would prevent the situation probably02:03
lifelessI realise that this is roughly what you were suggesting.02:04
pooliefor me the ssh client being killed or not, while good to fix, is not essential, because the same bug can occur withotu it02:04
pooliethe problem is that the server is polling on its own account, and that should be controlled by the client02:05
lifelesspoolie: well, I disagree that it should be controlled by the client.02:06
poolieperhaps in the medium term we want to avoid lock operations going across the network at all?02:06
lifelesswe only lock branches today02:06
lifelessand locking a branch is a human level action, not a bzr level one02:06
lifelessif that makes sense02:07
lifelesswe could do some fancy nonce based stuff to detect collisions during a branch level operation02:13
lifelessyay loggerhead, you go greedy thing02:14
lifeless930M02:14
lifelessmwhudson: can we get some patch to loggerhead to dump objet allocation stats to the log once an hour or some such ?02:15
lifelessalso02:15
lifelessits running python2.402:15
lifelessIIRC 2.5 has the ability to free() memory02:16
lifelesswhich might be useful.02:16
pooliethat will probably cause some complaints from IS - it may need a distro upgrade02:17
poolieprobably worth it though02:17
lifelessthey would love not having to stab loggerhead routinely02:17
pooliesigacly02:17
lifelessits running 6.01.102:18
lifeless2.5 is not installed, we can likely get a backport though02:18
pooliethat's dapper?02:19
pooliethey say it is infeasibly hard to backport it02:19
lifelessoh02:19
lifelessmeh, we can surely get a > dapper VM, or a distro upgrade02:20
lifelessSEP :)02:20
pooliewill send mail02:27
lifelesslunching02:42
mwhudsonlifeless: that sounds like a good idea02:50
lifelessmwhudson: which, the patch or 2.5 ? ;)03:04
mwhudsonlifeless: the patch03:04
mwhudsoni'd be a little surprised if 2.5 made much difference03:04
lifelessmwhudson: when did python start calling free()?03:31
mwhudsonlifeless: probably 2.5, i don't really remember03:31
mwhudsonbut i don't think this will make much difference to the loggerhead situation03:32
mwhudsonif entire arenas are free, python <2.5 will still reuse them03:32
lifelessmwhudson: it will make peak/current memory usage clearer to the os03:32
mwhudsonand if they're not free, python >=2.5 will not free them03:32
lifelesshow big is an area ?03:32
lifelessarena03:33
mwhudsonwell, it's possible it will make things clearer, i guess03:33
mwhudsoni would offer money that it would not really help much though03:33
mwhudsoner, 256k i think, not sure though03:33
lifelessso03:33
lifelessI think it unlikely that in 930M of vss03:34
lifelessthat a majority of 256k regions are not empty, unless there is a genuine leak03:34
mwhudsoneh03:35
poolieiirc 2.5 had more allocator improvements beyond just using free03:35
mwhudsonif they are empty, then when loggerhead needs to allocate more objects, it will use an empty arena03:36
lifelessmwhudson: sure, I get that03:37
lifelessmwhudson: anyhow, 2.5 won't harm.03:37
mwhudsonthis is extremely likely03:37
poolielifeless: i got "Sender not authorised to commit to branch http://bazaar-vcs.org/bzr/bzr.1.3"03:39
lifelesspoolie: doh. one sec03:39
lifelesspoolie: fixed03:41
pooliethx03:59
lifelessyay nm borked04:09
lifelessnow have to run iwconfig04:09
lifelessremind me why we have a gui ?04:09
poolielifeless: just as you said that my network collapsed :/04:22
lifelessha!04:29
lifelesspoolie: I'm out; ciao.06:02
awilkinsjelmer: Did you manage to solve that pyrex issue you had? I had a go at building the branch you had on Win32 ; it's not fun (and I've not succeeded yet).09:33
awilkinsls09:34
Odd_Bloke.   ..   .bzr09:37
fullermdEek!  It's a nekkid branch!  Avert your eyes!09:46
awilkinsArse, our decent HTTP proxy is down (ie, the one that doesn't demand NTLM auth to get out)10:09
awilkinsMeh, you know when you've been using vi to much when you try to quit every text editor with :wq10:16
fullermdOh, that's nothing.  Wait 'till you get stuck in front of Word one day, and see how it reacts to Esc getting smacked all the time...10:22
bob2disturbingly deals ok ctrl-x ctrl-s every few seconds10:30
jelmerawilkins: I've just pushed the branch I'm currnetly using10:37
jelmerthat should at least build ok10:37
jelmeryou may have to fix the include dir detetion code in setup.py10:38
awilkinsjelmer: Judging by the fun I had on Friday with it, definitely10:41
awilkinsjelmer: Although I think I may have been overzealous with includes and libs, I might have been increasing my dependency nightmare10:42
awilkinsjelmer: Was trying with both MS 7.1 compiler and MinGW10:42
awilkinsBoth have different issues10:42
=== mwhudson__ is now known as mwhudson
jelmeryou11:11
jelmer'd need both the apr and svn libraries11:11
awilkinsI got the "deps pack" for svn 1.4.6 win3211:12
awilkinsBut I'm not sure it has enough .lib files in it :-)11:12
awilkinsAnyway, I think it wil lhave to wait until later, my build environment is at home11:12
awilkinsAPR builds easily on Win32, I wish SVN would take a leaf out of their book.11:13
awilkinsThe best help they had to offer in #svn-dev was "good luck with that"11:13
=== kiko-afk is now known as kiko
PengWait a minute.11:35
Pengbzr-svn creating thousands of packs and instantly repacking them on a mostly-full file system can't be healthy for it.11:36
jelmerre12:14
jelmerPeng: well, a part of the problem is that the API provides no way to indicate that you're going to write a bunch of revisions12:15
PengI wasn't complaining about the repacking, just thinking "augh, my poor hard drives".12:16
jelmerinstead of just one12:16
PengHow does something like "bzr pull" only write one pack then?12:16
james_wwell, that's pull not commit.12:16
james_wcurrently when you do a commit it writes one pack.12:17
PengYeah..12:20
james_wjelmer: we need to get bzr-svn in hardy sorted.12:21
PengSo what would be useful is being able to tell commit "don't save it yet, I'm about to commit again!"?12:21
james_wI don't know if bzr 1.3 will get in to hardy, so we may have to instead put some bzr-svn package in.12:22
=== mrevell is now known as mrevell-lunch
jelmerjames_w: ah, ouch12:24
jelmerjames_w: what is going to determine whether 1.3 will make it into hardy?12:24
james_wjelmer: whether the release team allow it.12:25
jelmerjames_w: ah, ok12:25
james_wthe general rule is bug fix only releases.12:25
jelmerbzr-svn 0.4.7 works with bzr 1.212:25
jelmerit just warns you12:25
james_wso we should just disable the warning?12:25
jelmerso I guess one option would be to simply upload a new ubuntu package that adds (1,2) to the list of supported bzr versions12:25
jelmeror I could release 0.4.8, which would also help debian12:26
james_wI thought 0.4.8 would be 1.3 compatible12:30
james_wor is it both?12:30
jelmerwell, I was planning on making 0.4.8 1.3 compatible12:30
james_wSolving it in Debian is obviously important as well, but hardy is a little more pressing.12:30
james_wI think for Debian dato will upload the 1.3rc1 soon, so a bzr-svn release for 1.3 would work fine.12:31
jelmerk12:31
jelmerjames_w: I guess just adding (1,2) to the list of supported bzr versions in the bzr-svn ubuntu package should fix things then12:32
jelmerafaik Martin Pitt already loosened the dependencies of the package itself12:32
james_wah, ok.12:33
james_wI'll try and do that this week.12:33
=== FreeNode_ is now known as herb
=== mrevell-lunch is now known as mrevell
=== mw|out is now known as mw
ubotuNew bug: #203152 in bzr ""bzr merge --pull" does not list changes" [Undecided,New] https://launchpad.net/bugs/20315213:11
datojames_w: uploaded13:14
james_wdato: great, thanks.13:15
james_wspiv: did you see that Toshio says he is at pycon? Maybe you guys should try and catch up with him.13:16
james_wI think good relationships with distro packagers are very beneficial13:16
james_wisn't that right dato :)13:16
datoheh13:17
ubotuNew bug: #119265 in trac-bzr "branch w/o commits produce traceback" [Medium,Fix released] https://launchpad.net/bugs/11926513:47
elmargolHi, is there a way to resume a svn branch import?14:06
igcmorning14:07
james_welmargol: with bzr-svn?14:18
elmargoljames_w: :( i try to import a 4000r svn repository14:18
james_welmargol: if you have a partial branch on disk then you can bzr pull, if not I think you may have to start over.14:19
james_welmargol: what error did it fail with?14:19
elmargolI retry it...14:23
elmargoldon't have the errormessage anymore14:23
spivelmargol: with bzr-svn, it's best to do the branch inside a repo made with "bzr init-repo --rich-root-pack", because then you can resume very easily.14:31
jetsaredimcan someone explain the following error??  http://dpaste.com/39805/14:37
jelmerjetsaredim: you didn't specify a branch name14:38
datojetsaredim: ~jetsaredim/mplayerplug-in is an area to put branches related to mplayerplug-in14:38
datoit can't itself be a branch14:38
jetsaredimahh14:38
spivThat message from Launchpad could be clearer.  I'll file a bug.14:38
jetsaredimso i need to call it something after that14:39
elmargolspiv: how do I resume?14:39
datojetsaredim: yes. e.g. ~jetsaredim/mplayerplug-in/bug-123 or ~jetsaredim/mplayerplug-in/mine, or whatever14:39
jetsaredimgotcha14:41
jetsaredimthanks14:41
jetsaredimand yes, that could be a little clearer14:41
spivjetsaredim: bug 203178 filed.  Thanks for the report.14:46
ubotuLaunchpad bug 203178 in launchpad-bazaar "Unclear error when pushing over bzr+ssh: "This method is only for creating branches:"" [Undecided,New] https://launchpad.net/bugs/20317814:46
spivelmargol: If the branch is inside a repo, then you can just delete the branch and re-run the bzr branch command.  The already converted revisions will be stored in the repo, so it won't need to convert them again.14:47
jetsaredimspiv: that was fast14:50
elmargolhttp://dpaste.com/39808/15:01
elmargoljames_w:15:02
james_welmargol: can you do "svn ls https://svn.participatoryculture.org/svn/dtv" ?15:09
elmargolhttp://dpaste.com/39811/15:10
ubotuNew bug: #203186 in bzr "authentication.conf isn't used with openssh" [Undecided,New] https://launchpad.net/bugs/20318615:10
james_wso yes.15:10
james_wI'm not sure I'm afraid.15:11
james_wjelmer: do you have any ideas about this.15:11
elmargolthis happened after 600-700 revisions15:11
james_wthese propfind errors seem familiar.15:11
spivI think it's probably an intermittent error.15:11
james_wmaybe that's just how a lot of errors manifest themselves15:11
spivi.e. a temporary network glitch causing a request to fail at random.15:11
james_welmargol: can you "bzr branch  https://svn.participatoryculture.org/svn/dtv/trunk" ?15:12
elmargolyes15:13
james_welmargol: is that sufficient for your needs, or do you need the whole import?15:25
elmargolits ok for me if it works...15:25
elmargoli think it will crash... after some time15:25
james_wah, sorry, I thought you were saying that you could.15:26
elmargolhttp://dpaste.com/39815/15:29
james_welmargol: I'm not sure I'm afraid.15:33
james_wwould you file a bug containing the trackebacks that you get please?15:33
elmargolsure15:33
elmargolhttps://bugs.launchpad.net/bzr/+bug/20319015:40
ubotuLaunchpad bug 203190 in bzr "bzr svn-import fails" [Undecided,New]15:40
=== thekorn_ is now known as thekorn
ubotuNew bug: #203203 in bzr-loom "bzr nick breaks loom" [Undecided,New] https://launchpad.net/bugs/20320316:35
james_wbeuno: you'll never guess what, I just successfully build sid's baz in an up to date sid chroot.17:24
beunojames_w, wha?  really?  how!?17:25
james_wbeuno: no idea. Just downloaded it and built it intending to get a shell with the failed build and it worked.17:26
james_wI'm going to try it on hardy now.17:26
beunojames_w, cool. Let me know if you want the files we worked on17:27
james_wbeuno: yeah, they would be useful.17:28
james_wbeuno: I think I can grab them from your PPA, let me look.17:28
james_wok, I can get the baz one.17:29
james_wDid we do anything to bazaar-doc or bzr?17:29
* beuno checks17:29
beunojames_w, we did bazaar-docs17:30
beunoI can zip that up and send it over17:31
james_wbeuno: yes please.17:31
beunojames_w, sent17:33
james_wbeuno: thanks.17:34
beunojames_w, good luck, and let me know if I can help you17:36
james_wthanks17:36
beunovila, you rock  ;)17:43
=== FreeNode_ is now known as herb
james_wbeuno: it fails in hardy still18:02
beunojames_w, that's odd. Can you pinpoint it to the same library that failed before?18:02
james_wbeuno: what do you mean?18:03
beunojames_w, there was a specific library that made it fail18:03
beunowhich we tried to track down what was the last version it built with18:04
beunolifeless pointed it out18:04
james_wbeuno: I thought that was just a hunch.18:06
beunohe seemed pretty sure that they broke their ABI18:06
james_woh yeah, they definitely did that.18:07
=== mrevell is now known as mrevell-dinner
jetsaredimis it possible to see the progress in % for a push?19:52
james_wigc: nice work with the fast-import fix19:53
igcjames_w: please test!!!! It was a **BAD** bug19:54
james_wigc: did you see that the memcached guy confirmed that it worked for him?19:56
igcno I hadn't - thanks for the update19:56
james_wI've looked at that HACK before, it appears to be what makes the changed files not show up as modified: after in the log.19:57
igcyep19:57
james_wis that fixed by this change as well?19:58
igcshould be19:58
james_wcool, I'll test that.20:00
jelmer'evening *20:03
jelmerigc: using RevisionLoader seems to definitely help bzr-svn20:03
igchi jelmer - what sort of difference?20:04
ubotuNew bug: #203287 in bzr-loom "unable to create a new bottom thread" [Undecided,New] https://launchpad.net/bugs/20328720:06
ubotuNew bug: #203285 in bzr-loom "unable to "de-loom" a branch" [Undecided,New] https://launchpad.net/bugs/20328520:07
jelmerigc: I haven't done any benchmarking yet20:18
spivjelmer: when's the 0.4.8 release btw?  People at PyCon keep asking :)20:20
lifelessjames_w: neon breaks that test; it was memory not a hunch21:16
james_wlifeless: ah, sorry for doubting you.21:17
james_wlifeless: however it works on sid now. I think the failure there was for a different reason originally though21:17
james_wlifeless: I'm talking to a couple of people about bzr-loom on #vcs-pkg/freenode at the moment.21:17
=== jetsaredim is now known as _jgreenwa
=== FreeNode is now known as herb
unenoughhi, I have a shared repo with some repos inside21:39
unenoughcan i somehow see the tree for the whole shared repo? that is showing merges between sub-repos21:40
unenoughooooooops21:40
unenoughi mean: repo (instead of shared repo) and branches (instead of "repos")21:40
james_wunenough: no, there's no tool to visualise a set of branches yet unfortunately.21:42
=== lamont` is now known as lamont
mptHi, I've installed bzr-loom and it shows up in "bzr plugins", but when I branch a branch that's in loom format, I still get "bzr: ERROR: Could not understand response from smart server: ('error', "Unknown branch format: 'Bazaar-NG Loom branch format 1\\n'")"22:11
mptIs there something else I need to do?22:11
james_wmpt: is loom installed on the server?22:11
james_whi mpt btw22:11
mpthi :-)22:11
mptI don't know whether loom is installed on the server, it's not my server22:12
mptHow would I find out?22:12
james_wah, the message seems be suggesting that it isn't22:12
james_wwhat protocol are you using to branch?22:12
mptOh, so it's the server that's giving that "Unknown branch format" error, not my copy of bzr22:13
mptI don't know what protocol I'm using to branch, I'm just using "bzr branch"22:13
* mpt is a bear of very little brain22:13
mptOk, so I SSHed to the server and its copy of bzr doesn't have bzr-loom installed22:14
mptthanks for the help22:16
james_wmpt: the protocol would bzr bzr+ssh:// or something.22:17
mptoh, right22:18
mptyes, bzr+ssh22:18
mptoh, I could use sftp:// instead?22:18
* mpt tries22:18
mptthen bzr on the server wouldn't need to get involved at all22:18
james_wmpt: good idea22:20
nxvljames_w: hi!22:20
james_wI was asking to know if you had ssh access to the server22:20
james_whi nxvl. how are you?22:20
nxvlgood, working on some packages, and at work22:21
james_wcool22:21
mpthurrah22:21
mptthanks james_w22:21
nxvlthis has been the first light day after a really hard week22:21
nxvljames_w: did you know something about the canonical summer of code poolie mention last time22:22
james_wmpt: glad it works22:22
nxvljames_w: i have ask to dendrobates and dholbach, and non of them seems to know anything22:22
james_wnxvl: I don't know anything, sorry.22:23
nxvlmm, it seems that no one know, so it mustn't going to run this year :S22:23
james_wnxvl: I don't know if Ubuntu is doing it as well, I just saw that they weren't on the GSoC list.22:24
james_wI think it's a pretty recent idea, so it might be because people haven't heard yet.22:24
nxvljames_w: yep, but last time i was here poolie mention something about a running a student program thru canonical22:25
james_wnxvl: that's what I mean22:25
james_wnxvl: I think that idea is quite new.22:25
nxvlmm22:26
nxvlok, i will give a try to gsoc this year on a debian project, and next year maybe on canonical program22:26
nxvl:P22:26
james_wnxvl: if you are interested you could send an email to the list to say that.22:27
nxvljames_w: the bzr list?22:27
james_wyep22:28
nxvlmm22:28
james_wunless you're more interested in Ubuntu22:28
nxvlactually yes22:28
nxvli'm more interested in ubuntu22:28
james_wok22:28
nxvlbut i'm also interested on bzr, but is still 2nd on my list22:29
nxvl:S22:29
lifelessjames_w: still on vcs-pkg  ?22:32
james_wlifeless: I am, but the discussion has petered out.22:36
lifelessjames_w: I dont see anyone in that channel22:38
lifelessjames_w: #vcs-pkg right ?22:38
lifelessdato: bzr-hookless-email seems to set From and Sender22:41
lifelessdato: is that deliberate?22:41
james_wlifeless: did I say freenode?22:42
james_wsorry, I meant OFTC.22:42
james_wHow do I force urllib?22:47
TFKylejames_w: to do what?22:48
james_wTo force bzr to use urllib for http connections?22:49
Penghttp+urllib, I think22:49
TFKyleah, the http+urllib:// protocol iirc22:49
PengI think I've been using pycurl recently. No problems so far.22:49
james_whttps+urllib://22:49
james_wI was trying to use my 0.14 client on my server to tell me, and wondered why it had so few help topics.22:50
TFKylePeng: used to be a problem with it branching from certain lighttpd instances, think it was related to lighttpd not doing certain range requests22:50
PengHuh.22:50
PengAlso, there's stuff like it being bad about getting Ctrl+Ced or something.22:50
Pengjames_w: Heh, oops.22:51
james_wIt doesn't like SSL certificates it can't verify as they are self signed or it is missing the CA cert.22:52
PengAh.22:52
PengWell, that's a good thing.22:52
PengPython will gain cert verification in 2.6.22:52
dwonI created a project in bzr, and now I'm trying to svn-push it into a new svn repository, but I get "These branches have diverged. Use the merge command to reconcile them.".  With some fiddling, it looks like I can get it to merge my entire tree in one svn revision, but I'd like to get the revision history into subversion.  Is it possible?22:52
TFKylePeng: really? bug/commit link?22:53
PengTFKyle: There's an "ssl" module, AFAIK.22:53
Pengdwon: Wait, what? Why not push it to, y'know, bzr?22:53
james_wPeng: that is a good thing, except when the user can't override it.22:54
dwonPeng: because everyone else at the company I work for uses svn22:54
Pengjames_w: Indeed.22:54
james_wdwon: it should be possible. I'm not sure why you get that error.22:54
TFKylePeng: ah22:55
james_wdwon: you could file a bug with as much information as you can.22:56
james_wdwon: in particular an "svn ls URL_you_are_trying_to_push_to" might provide a hint.22:56
james_wand svn log of that too.22:56
james_wyou can obscure filenames if that is a problem for you.22:57
TFKylePeng: hmm, from a quick look at the ssl module it looks like it's up to the person using it to validate the cert23:00
* TFKyle could be blind and wrong though23:00
PengTFKyle: Does urllib2 use it, though?23:00
TFKyleor httplib rather, not sure :)23:01
TFKyle(urllib uses httplib under the covers for http connections :))23:01
james_wurllib ignores certificates, I know that much23:02
lifelesspoolie: /win 5023:02
lifelessmeh sorry23:02
lifelesspoolie: I'm going to be chasing knits today23:02
TFKylelooks like httplib uses it if available, doesn't do checking itself though23:03
TFKyle(in current svn trunk anyway, might be a bug adding checking if nothing does already)23:04
lifelessdwon: for a new svn branch use 'svn-push'23:05
dwonlifeless: Did that23:05
TFKylehmm, actually I'm probably blind and ssl/_ssl actually do do it23:06
TFKyle(assuming you give it a proper ca_certs arg23:07
TFKyle(and cert_reqs)23:08
poolielifeless: did you see jml around yet?23:12
pooliehe said he was still jetlagged...23:12
Pengjelmer: Would your new svn Python bindings be useful to other projects?23:14
jelmerPeng: yep, they're more python than the original bindings23:15
jelmer*pythonic23:15
TFKylemm, they're in bzr-svn or?23:16
PengTFKyle: http://people.samba.org/bzr/jelmer/bzr-svn/pyrex/23:17
Pengjelmer: Cool.23:18
jmlyes, I'm around23:18
jmlpoolie: I said I was still very tired :)23:19
jmlI'm uncertain as to whether this constitutes jetlag.23:19
poolieme too23:25
pooliei want to go out to the vet23:25
poolie(doctors can't help me anymore :-)23:25
pooliebut did not want to leave you standing outside23:26
poolieif you were coming over23:26
jmlpoolie: that's ok. I'm waiting for thumper to get back23:27
dwonjames_w: https://bugs.launchpad.net/bzr/+bug/20336523:31
ubotuLaunchpad bug 203365 in bzr "Can't create new svn branch from a bzr branch" [Undecided,New]23:31
spivjelmer: "bzr svn-push" does weird things if the branch has no new history (e.g. bzr branch svn://.../trunk new-branch; cd new-branch; bzr svn-push svn://.../branches/new-branch)23:33
=== mwhudson_ is now known as mwhudson
ubotuNew bug: #203365 in bzr "Can't create new svn branch from a bzr branch" [Undecided,New] https://launchpad.net/bugs/20336523:41
lifelessman npviewer.bin must die23:45
lifelesskeeps using 99% cpu23:45
RAOFlifeless: I see you're another member of the x86-64 self-flageltion society :(23:49
lifelessRAOF: users -> bug reports -> fixed software23:52
lifelessor thats the theory23:52
lifelessRAOF: have you filed a bug ?23:52
jmlpoolie: so, when would be a good time to come over?23:53
slangasekjelmer: so if I'm getting backtraces with bzr-svn trying to merge into the grub branch that was 'bzr join'ed, is this a bzr-svn bug, or a grade-A Fail of the unsupported join functionality? :)23:53
pooliehm i still haven't left23:54
pooliebut if you plan to arrive at 12 that should be ifne23:54
pooliejml, or even a bit earlier23:54
jmlpoolie: ok.23:55
ubotuNew bug: #203368 in bzr-svn "svn-push a branch with no new history makes surprising commit to SVN repo" [Undecided,New] https://launchpad.net/bugs/20336823:55
RAOFlifeless: I've filed a number of bugs against nspluginwrapper.  Some have even been fixed!23:56
lifelessslangasek: file a bug with the backtrace ?23:56
lifelessRAOF: was one of them 'insane battery use' ?23:56
RAOFNo, I don't believe so.  The one I was particularly thinking of is "crashes when there's lots of flash"23:56
RAOFI should probably follow that up.  The debian package has it fixed (by actually initialising glib's thread support before using threads, IIRC).23:57
slangaseklifeless: if I'm not going to get glared at for using undocumented and unsupported features, ok ;)23:59
lifelessslangasek: we want to make it supported23:59
lifelessslangasek: as long as you don't expect it to be fixed, bug reports on this stuff are good23:59

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!