/srv/irclogs.ubuntu.com/2007/09/24/#bzr.txt

lapthrickhrmpf12:04
lapthrickit seems that a push didn't, in fact, include the nested tree :(12:04
lifelesshad you committed?12:05
lapthrickyes12:05
lifelessdoes 'bzr branch mytree mynewtree' include the upstream subtree ?12:05
lifelessand did you use bzr push, or bzr svn-push?12:05
lapthricklifeless: when I do svn log on that branch, there's a missing revno corresponding to when I merged12:05
lapthricklifeless: svn-push12:06
=== jelmer_ [n=jelmer@157pc196.sshunet.nl] has joined #bzr
lapthrickactually, it might be due to another thing12:06
lifelessjelmer_: good timing12:06
=== jelmer_ is now known as jelmer
lifelessassuming you are here :)12:06
lapthrickthat SVN repo uses a two-level branch structure12:06
lapthrickso branches/owner/branchname12:06
jelmerhey lifeless12:07
lifeless08:04 < lapthrick> hrmpf12:07
lifeless08:04 < lapthrick> it seems that a push didn't, in fact, include the nested tree :(12:07
lifeless08:05 < lifeless> had you committed?12:07
lifeless08:05 < lapthrick> yes12:07
lifeless08:05 < lifeless> does 'bzr branch mytree mynewtree' include the upstream subtree ?12:07
jelmerit's actually evening here (-:12:07
lifeless08:05 < lifeless> and did you use bzr push, or bzr svn-push?12:07
lifeless08:05 < lapthrick> lifeless: when I do svn log on that branch, there's a missing revno corresponding to when I merged12:07
lifeless08:06 -!- jelmer [n=jelmer@157pc196.sshunet.nl]  has quit [Remote closed the connection] 12:07
lifeless08:06 < lapthrick> lifeless: svn-push12:07
lapthrickand it did bail out with "not a valid SVN branch" during that push12:07
lapthrickso I assume it was trying to push that sub-tree after pushing the parent tree and then it died12:07
lapthrickjelmer: so, I need support for two-level branch scheme for the repo I'm using12:08
lapthrickthough it's actually optional, some branches we have are directly unders branches/, some live in branches/owner/12:09
jelmerlifeless: Thanks12:09
lapthrickjelmer: I also submitted a bug report and have a scenario where merge-into manages to kill bzr-svn for you :)12:10
jelmerlapthrick: 'bzr svn-branching-scheme' should be able to tell you what branching scheme is being used for a repository atm12:10
lapthrickbzr pokerolymp:2090/> svn-branching-scheme svn+https://beta.aimido.de/svn/src2/12:11
lapthricktrunk12:11
lapthrickbranches/*12:11
lapthricktags/*12:11
jelmeryou'd probably want to add 'branches/*/*' there as well12:12
lapthrickjelmer: how can I do that?12:12
jelmerbzr.dev svn-branching-scheme --set12:13
lapthrickjelmer: so just svn-branching-scheme --set branches/*/* ?12:13
jelmerlapthrick: just bzr svn-branching-scheme --set <url>12:15
jelmerthat should put you into an editor allowing you to edit that list12:15
lapthrickahh12:15
jelmerthe branches/*/* should probably be the first line12:15
lapthrickbzr pokerolymp:2090/> svn-push svn+https://beta.aimido.de/svn/src2/branches/mathrick/pokersource/12:17
lapthrickUnhandled error:12:17
lapthrickhmm12:17
lapthrickI suspect that branch might be broken by the previous botched push12:17
lapthrickno, actually it happens for every branch I try to push to12:18
lapthrickjelmer: any idea where I should poke it?12:18
jelmerlapthrick: what unhandled error exactly?12:19
lapthrickjelmer: that's exactly what it says. Unhandled error and then nothing12:19
jelmercan you try running with BZR_PDB=1 set and seeing what line it bails out on?12:20
lapthrickjelmer: http://pastebin.com/m68ba42d812:21
lifelessigc: I have all tests passing in packs12:23
jelmerah, looks like ListBranchingScheme still needs a is_parent_branch() implementation12:23
igcthat's great lifeless12:23
lifelessigc: about to send a patch that cleans up weave stuff - and makes the tests pass ;)12:24
igcok - I'll have a look12:24
lapthrickjelmer: is there an easy fix for that?12:25
jelmerlapthrick: looking at it atm12:26
jelmerlapthrick: btw, I don't think I've seen any bugreport on the merge-into/bzr-svn problem12:29
lifelessigc: mail sent12:32
igccool12:32
igcbtw, up early because it's school holidays here now - best to get as much done as early as possible :-)12:33
lifelessheh12:34
lifelessI got 7 hours solid sleep.... and then woke up at 043012:34
lapthrickjelmer: no, I didn't submit a bugreport, as it wasn't entirely clear what's happening12:35
jelmerlapthrick: If you can still reproduce it, a bug report would be very useful. merge-into and bzr-svn should be able to work ok together12:37
lapthrickjelmer: sure12:39
lapthrickjelmer: actually it seems I'm able to trigger two separate errors12:45
lapthrickmathrick@hatsumi:/tmp/merge$ bzr merge-into file://$PWD/../test/trunk test12:45
lapthrickbzr: ERROR: Repository KnitRepository('file:///tmp/merge/.bzr/') is not compatible with repository SvnRepository('file:///tmp/merge/../test')12:45
lapthrickjelmer: that's on a local test repo12:45
lapthrickjelmer: http://pastebin.com/m6302280512:46
lapthrickthis one is on the actual repos I wanted to merge-into12:46
jelmerlapthrick: that first error should be fixable by upgrading the bzr repository12:47
jelmerlapthrick: see the FAQ in bzr-svn's 0.4 branch12:47
jelmerlapthrick: I'll fix the other one12:48
lapthrickjelmer: great, thanks12:48
=== Verterok [n=ggonzale@184-220-114-200.fibertel.com.ar] has joined #bzr
lifelessigc: repository branch that passes all tests pushed01:11
igccool. Did you want me to run any tests here?01:11
lifelessnot as such01:13
lifelessjust letting you know01:13
igcsure - thanks01:14
=== jml [n=jml@ppp121-44-213-76.lns1.hba1.internode.on.net] has joined #bzr
=== asabil [n=asabil@ti0035a340-0469.bb.online.no] has joined #bzr
PengPulling from the repository branch: bzr: ERROR: Revision {robertc@robertcollins.net-20070923224332-qy28l0g345rcyein} not present in "rev_storage.py-20051111201905-119e9401e46257e3".01:34
PengIs it in the middle of a push or something?01:35
lifelessno01:39
lifelessrevert back a couple of revisions01:39
lifelessthen pull again01:39
lifelesstermporary bokrage01:39
=== mssever [n=mssever@75-106-9-198.cust.wildblue.net] has joined #bzr
=== michelp [n=michelp@69-30-72-119.dq1sf.easystreet.com] has joined #bzr
PengWhat, uncommit back a few revisions?01:43
=== mssever [n=mssever@75-106-9-198.cust.wildblue.net] has left #bzr []
lifelessyes01:44
lifelessbbiab01:44
lifelessbefore the 'fix test X' one, that broke it01:44
lifelessuncommit + revert01:45
lifelessok, ciao, -> poolies01:45
PengOh, revert too.01:45
PengYeah, that worked.01:48
PengThanks.01:48
=== jml [n=jml@ppp121-44-213-76.lns1.hba1.internode.on.net] has joined #bzr
=== poolie [n=mbp@ppp112-44.static.internode.on.net] has joined #bzr
abentleylifeless: The branch: and ancestor: revision specs do a fetch.02:11
=== arjenAU [n=arjen@ppp215-29.static.internode.on.net] has joined #bzr
pooliehi02:15
poolieabentley, i think lifeless is on a train02:16
abentleypoolie: Okay.  No big rush.02:16
poolie(rebooting)02:16
=== AnMaster [n=AnMaster@unaffiliated/anmaster] has joined #bzr
=== jamesh [n=james@canonical/launchpad/jamesh] has joined #bzr
=== jrydberg_ [n=johan@213.115.45.46] has joined #bzr
=== poolie [n=mbp@ppp112-44.static.internode.on.net] has joined #bzr
=== BasicMac [n=BasicOSX@216.243.156.81.real-time.com] has joined #bzr
=== BasicMac [n=BasicOSX@216.243.156.81.real-time.com] has joined #bzr
=== BasicMac is now known as Basic
=== AfC [i=andrew@office.syd.operationaldynamics.com] has joined #bzr
=== Bambi_BOFH [n=kgoetz@gnewsense/friend/kgoetz] has joined #bzr
=== schierbeck [n=daniel@dasch.egmont-kol.dk] has joined #bzr
=== Bambi_BOFH is now known as kgoetz
=== orospakr [n=orospakr@bas4-ottawa23-1177770446.dsl.bell.ca] has joined #bzr
lifelessPeng: cool03:42
PengSo what was wrong with it?03:47
=== poolie [n=mbp@ppp112-44.static.internode.on.net] has joined #bzr
lifelessI broke it03:56
lifelessthen I unbroke it03:56
lifelessyou had the broken copy03:56
=== igc food
PengOkay.04:00
=== BasicMac [n=BasicOSX@216.243.156.81.real-time.com] has joined #bzr
=== BasicMac is now known as Basic
lifelessPeng: the details are pretty boring really; there was a failing test that was more important than I realised; and two variables being tested for equality that were of different types04:19
lifelessPeng: but all tests pass now; so should all be good04:19
=== fullermd blinks.
fullermdUnderrating the importance of a failing test??  Who are you, and what have you done with lifeless?04:26
lifelessits an experimental branch04:28
lifelessI don't have a zero-tests failing policy for things that I'm doing open heart surgery on; I try for zero but its not always feasible.04:29
fullermdHrmph.  Excuses, excuses.  Getting soft in your old age...04:29
=== jml_ [n=jml@203-113-250-169-static.TAS.netspace.net.au] has joined #bzr
Penglifeless: Oh, okay.04:39
=== rml [n=Skippy@78.32.35.169] has joined #bzr
=== dous_ [n=dous@124.104.0.255] has joined #bzr
=== jamesh [n=james@canonical/launchpad/jamesh] has joined #bzr
=== bigdog [n=scmikes@72-197-8-8-arpa.cust.cinci.current.net] has left #bzr []
=== jml_ is now known as jml
=== kgoetz [n=kgoetz@gnewsense/friend/kgoetz] has joined #bzr
=== bigdo1 [n=scmikes@72-197-8-8-arpa.cust.cinci.current.net] has joined #bzr
=== NamNguyen [n=namnt@203.162.163.50] has joined #bzr
=== bigdo1 [n=scmikes@72-197-8-8-arpa.cust.cinci.current.net] has left #bzr []
=== bigdo1 [n=scmikes@72-197-8-8-arpa.cust.cinci.current.net] has joined #bzr
=== BasicMac [n=BasicOSX@216.243.156.81.real-time.com] has joined #bzr
lifelessigc: ping05:47
igchi lifeless05:47
lifelesswant a quick call ?05:48
igcsure05:48
igcyou at poolies?05:48
lifelessup05:48
igcor you can call me05:48
lifelessyup05:48
lifelessnah, call poolies05:48
igcnp05:48
igc2 minutes05:49
ubotuNew bug: #144352 in bzr "tag should refuse to tag null:" [Undecided,New]  https://launchpad.net/bugs/14435206:15
=== BasicOSX [n=BasicOSX@warden.real-time.com] has joined #bzr
jelmerlapthrick: ok, the bug you posted to pastebin should be fixed now06:52
=== rml [n=Skippy@78.32.35.169] has joined #bzr
=== Starting logfile irclogs/bzr.log
=== ubuntulog [i=ubuntulo@ubuntu/bot/ubuntulog] has joined #bzr
=== Topic for #bzr: The Bazaar Version Control System | http://bazaar-vcs.org/ | Bazaar 0.90 and 0.91rc2 are out - http://bazaar-vcs.org/Download | Please complete the Bazaar User Survey - http://www.surveymonkey.com/s.aspx?sm=L94RvLswhKdktrxiHWiX3g_3d_3d
=== Topic (#bzr): set by poolie at Wed Sep 12 03:35:03 2007
=== mlh [n=mlh@c211-30-211-232.belrs1.nsw.optusnet.com.au] has joined #bzr
=== Mez [n=Mez@ubuntu/member/mez] has joined #bzr
=== jml [n=jml@ppp121-44-213-76.lns1.hba1.internode.on.net] has joined #bzr
=== poolie [n=mbp@ppp112-44.static.internode.on.net] has joined #bzr
pooliejelmer: hi?07:18
jelmerpoolie, hi07:19
=== Verterok [n=ggonzale@184-220-114-200.fibertel.com.ar] has joined #bzr
lapthrickjelmer: the one with merge-into svn://, or the one with push svn:// ?07:29
jelmerlapthrick: merge-into07:29
jelmerpoolie: ping?07:29
lapthrickokay, lemme try07:29
jelmerbtw, I've only fixed the issue you reported, not actually tested merge-into with bzr-svn..07:29
lapthrickjelmer: it seems to work fine07:32
jelmercool, great :-)07:32
lapthrickjelmer: do you have that push bug recorded somewhere, or should I put it in launchpad?07:33
jelmerlapthrick: I just filed a bug report on launchpad, with you subscribed07:34
lapthrickgood, thanks07:34
fullermdpoolie: Hi dere.07:34
fullermdpoolie: Is 0.91 blocked on something?07:35
=== kgoetz [n=kgoetz@gnewsense/friend/kgoetz] has left #bzr []
=== jelmer gets some sleep
=== AfC [i=andrew@office.syd.operationaldynamics.com] has joined #bzr
=== liw [n=liw@a91-154-119-10.elisa-laajakaista.fi] has joined #bzr
pooliefullermd: no, just other work keeps getting ahead of it08:02
poolieliw, hi08:02
liwpoolie, greetingses08:03
fullermdCoolies.  Just making sure I didn't miss something on the list   :)08:03
=== abentley [n=abentley@bas8-toronto63-1088754407.dsl.bell.ca] has joined #bzr
=== bigdo2 [n=scmikes@72-197-8-8-arpa.cust.cinci.current.net] has joined #bzr
=== bigdo1 [n=scmikes@72-197-8-8-arpa.cust.cinci.current.net] has joined #bzr
=== jamesh [n=james@canonical/launchpad/jamesh] has joined #bzr
=== pmezard [n=pmezard@nor75-4-81-56-59-92.fbx.proxad.net] has joined #bzr
=== hdima [n=hdima@idealer.cust.smartspb.net] has joined #bzr
=== Lo-lan-do [n=roland@mirexpress.internal.placard.fr.eu.org] has joined #bzr
=== vila [n=vila@lec67-4-82-230-53-244.fbx.proxad.net] has joined #bzr
=== CardinalFang [n=c@217.194.71.122] has joined #bzr
=== Zindar [n=erik@h188n1fls12o803.telia.com] has joined #bzr
=== hdima [n=hdima@idealer.cust.smartspb.net] has joined #bzr
=== GaryvdM [n=chatzill@mtngprs2.mtn.co.za] has joined #bzr
lapthrickI have a branch in which I removed some files present in upstream, now it turns out I need them. What's the best way to restore them?09:24
=== jamesh_ [n=james@canonical/launchpad/jamesh] has joined #bzr
GaryvdMlapthrick: revert09:27
GaryvdMI think09:27
AfClapthrick: revert is correct if it's simply current uncommitted work.09:29
AfClapthrick: if numerous revisions have gone by since then, you'll have to do something more elaborate09:29
lapthrickthe latter09:30
liwwould a reverse merge work? "bzr merge -r 42..41"09:30
lapthrickit suggests merge -r foo09:30
=== mvo [n=egon@p54A640B8.dip.t-dialin.net] has joined #bzr
AfC... a kludgy way to do it would be to just copy the files [back]  in, and `bzr add` them [again]  [potentially using  --file-ids or whatever to make sure it knows what you're up to] 09:30
AfCliw: [that would assume the file removal was the only thing in that revision, although you could do that and then revert the parts you didn't want to, er, revert :)] 09:31
lapthrickit seems that revert takes revision argument, but it also seems that I didn't, in fact , remove the dir I needed, I was just looking in the wrong place :)09:33
lapthrickaye, revert -r foo bar restores bar just fine09:36
lifelessciao for now, be back in a bit09:36
lapthrickAfC: we need to beat some sense into desrt09:37
lapthrickwhat with his silly delusions about git09:37
lifelesslapthrick: are you a gnomer ?09:37
lapthricklifeless: indeed09:37
lifelesscool09:37
lapthrickindeed :)09:37
lifelessAfC: btw, did I mention I have local initial commit faster than hg now ?09:37
lifelessAfC: (not that hg are *my* benchmark, but they seem to be some folks' benchmark)09:38
lifelessheading home, be back in a bit09:38
lapthricksee ya09:38
=== vila [n=vila@lec67-4-82-230-53-244.fbx.proxad.net] has joined #bzr
vilahi all09:39
lapthrickhi vila09:39
lapthrickvila: looked into that curl bug perhaps?09:40
vilalapthrick: 1) not yet, 2) I thought you found it was more on the bzr-svn front ?09:40
lapthrickvila: no, quite the opposite, I found it's a general libcurl-gnutls compat issue09:41
vilalapthrick: more precisely ? Is that a problem in curl or a problem in the way we interact with it ?09:41
vilalifeless: regarding my corrupted repo, I found that gutsy have changed the way nfs interacts with OSX09:42
lapthrickvila: I dunno, but last time you said it looked like an API compat bug and you need to look into it, since there was no error 77 as far as you knew09:42
vilalapthrick: That point I didn't have time to check yet09:43
lapthrickok09:43
lapthrickI'm not in a big hurry, I can use https+urllib for now, that repo isn't very likely to haxx me for not checking the cert properly09:43
vilalapthrick: ok09:44
vilalifeless: as I update gutsy as soon as the update-manager warn me, I can't know exactly if/what/when something went wrong, *but* this morning, the nfs mount from OSX failed at boot (but worked from command line...) until I add proto=tcp in /etc/fstab (using mount-v revealed that the mount succeeded with proto=udp)09:46
vilaas I can't reproduce the corruption by committing in the same conditions (to the best of my knowledge), I will consider that NFS was the cause (I don't really like leaving a possible corruption bug lying around, but I really can't see what to do to get a better diagnosis)09:48
vilalifeless: I am currently reorganizing around a new repo and will keep the corrupted one for some weeks anyway as it looks as a perfect candidate to better understand many details (why 'bzr send -o -' needs to refer to a revision outside of the branches it should care of, for one :)09:50
=== pmezard [n=pmezard@dhcp26-226.enst.fr] has joined #bzr
=== mwh [n=mwh@62-31-157-102.cable.ubr01.azte.blueyonder.co.uk] has joined #bzr
=== jamesh_ is now known as jamesh
=== Mez [n=Mez@ubuntu/member/mez] has joined #bzr
=== asabil [n=asabil@62.70.2.252] has joined #bzr
lifelessvila: ok10:18
lifelessoh, and I'm back :)10:18
vilalifeless: :) I still feel bad about that corruption though... What is *your* feeling ?10:19
lifelessvila: One of the lp developers has had similar corruption twice now; they use nfs.10:20
vilalifeless: haaaa, what a relief, same symptoms ? zeroed revision ?10:20
lifelessdunno exactly10:21
vilalifeless: ok, will keep an open eye then (but I rarely commit from OSX these days anyway)10:23
=== mrevell [n=matthew@canonical/launchpad/mrevell] has joined #bzr
vilalifeless: is there same way to check against this corruption from another data path or do we rely on the gzip crc ?10:24
lifelessfile sha will find it10:25
vilaok, I'll try to look into that (if only to understand if bzr may have been tricked by nfs telling him, yes, the content have been written to disk, when in fact it has not)10:26
vilathat's one of the reason I didn't want to touch that repo if I was able to rebuild everything (which I'm close to have achieved)10:27
vilalifeless: errr, scratch that, the commit was from the NFS server10:29
=== Mez_ [n=Mez@ubuntu/member/mez] has joined #bzr
=== igc food
=== asabil_ [n=asabil@62.70.2.252] has joined #bzr
ubotuNew bug: #144388 in bzr "Cannot do svn checkouts in a repository" [Undecided,New]  https://launchpad.net/bugs/14438811:05
=== allenap [i=allenap@nat/canonical/x-3037a206c251a099] has joined #bzr
=== sverrej [n=sverrej@pat-tdc.opera.com] has joined #bzr
=== Mez [n=Mez@ubuntu/member/mez] has joined #bzr
=== matkor [n=matkor@85.14.91.175] has joined #bzr
=== sabdfl [i=sabdfl@ubuntu/member/pdpc.silver.sabdfl] has joined #bzr
=== silwol [n=silberma@wosi02.synserver.de] has joined #bzr
=== CardinalFang [n=c@217.194.71.122] has joined #bzr
=== cfbolz [n=cfbolz@p54ABBA2D.dip0.t-ipconnect.de] has joined #bzr
=== dewd [n=dewd@201.9.147.182] has joined #bzr
ubotuNew bug: #144394 in bzr "stderr from a bzr+ssh smart server process should not be sent to the client" [Undecided,New]  https://launchpad.net/bugs/14439411:55
=== jnair [n=jayesh@203.123.188.10] has joined #bzr
=== zyga [n=zyga@ubuntu/member/zyga] has joined #bzr
=== mvo_ [n=egon@p54A65FC9.dip.t-dialin.net] has joined #bzr
=== mvo__ [n=egon@p54A65FC9.dip.t-dialin.net] has joined #bzr
=== mvo__ is now known as mvo
=== gabe [n=gabriel@91.84.56.254] has joined #bzr
=== NamNguyen [n=NamNguye@cm38.delta196.maxonline.com.sg] has joined #bzr
=== Mez [n=Mez@ubuntu/member/mez] has joined #bzr
=== dous_ is now known as dous
=== asabil [n=asabil@62.70.2.252] has joined #bzr
=== mvo [n=egon@p54A66696.dip.t-dialin.net] has joined #bzr
=== hsn_ [n=radim@234.114.broadband5.iol.cz] has joined #bzr
=== mrevell is now known as mrevell-lunch
=== herzel [i=herzel@gateway/tor/x-257cc1dfc7f708d5] has joined #bzr
=== bigdo2 is now known as bigdog
=== niemeyer [n=niemeyer@200.140.230.150] has joined #bzr
=== corporate_cookie [n=richie@seraphim.asbury.edu] has joined #bzr
=== cprov [n=cprov@canonical/launchpad/cprov] has joined #bzr
=== schierbeck [n=daniel@dasch.egmont-kol.dk] has joined #bzr
=== Mez [n=Mez@ubuntu/member/mez] has joined #bzr
=== AfC [i=andrew@office.syd.operationaldynamics.com] has joined #bzr
=== silwol [n=silberma@wosi02.synserver.de] has left #bzr []
=== Govan [n=Govan@62.254.178.211] has joined #bzr
=== matkor [n=matkor@EUROCZESCI.wbs.ssh.gliwice.pl] has joined #bzr
=== CardinalFang [n=c@217.194.71.122] has joined #bzr
=== RichardL [n=Skippy@78.32.35.169] has joined #bzr
=== mrevell-lunch is now known as mrevell
=== marianom [n=marianom@ubuntu/member/marianom] has joined #bzr
=== mw|out [n=mw@189.146.13.202] has joined #bzr
=== mw|out is now known as mw
ubotuNew bug: #144421 in bzr "Using branch: revspec in stat blows up" [Undecided,New]  https://launchpad.net/bugs/14442102:50
=== asabil [n=asabil@62.70.2.252] has joined #bzr
=== allenap [i=allenap@nat/canonical/x-a744796f36af6bfd] has joined #bzr
=== mvo_ [n=egon@p54A652B1.dip.t-dialin.net] has joined #bzr
=== mvo__ [n=egon@p54A67253.dip.t-dialin.net] has joined #bzr
=== bwinton [n=bwinton@mail.phantomfiber.com] has joined #bzr
=== mvo__ is now known as mvo
=== asak [n=alexis@200-171-75-98.dsl.telesp.net.br] has joined #bzr
=== asabil_ [n=asabil@62.70.2.252] has joined #bzr
=== asabil [n=asabil@62.70.2.252] has joined #bzr
=== asabil_ [n=asabil@62.70.2.252] has joined #bzr
=== NamNguyen [n=NamNguye@cm38.delta196.maxonline.com.sg] has joined #bzr
=== keir [n=keir@206-248-134-7.dsl.teksavvy.com] has joined #bzr
=== herzel [i=herzel@gateway/tor/x-f068b8419f4e0198] has joined #bzr
=== corporate_cookie [n=richie@seraphim.asbury.edu] has joined #bzr
=== p4tux [n=p4tux@189.169.63.63] has joined #bzr
=== schierbeck [n=daniel@192.38.109.188] has joined #bzr
=== schierbeck [n=daniel@192.38.109.188] has joined #bzr
=== asabil [n=asabil@62.70.2.252] has joined #bzr
=== asabil_ [n=asabil@62.70.2.252] has joined #bzr
=== asabil_ is now known as asabil
=== Mez [n=Mez@ubuntu/member/mez] has joined #bzr
=== asabil [n=asabil@62.70.2.252] has joined #bzr
=== BasicMac [n=BasicOSX@warden.real-time.com] has joined #bzr
=== Sigma [n=yann@pdpc/supporter/active/Sigma] has joined #bzr
=== asabil [n=asabil@62.70.2.252] has joined #bzr
=== cfbolz [n=cfbolz@p54AB8FCB.dip0.t-ipconnect.de] has joined #bzr
=== orospakr [n=orospakr@132.213.238.4] has joined #bzr
=== quicksilver [n=jules@212.69.38.59] has joined #bzr
=== schierbeck [n=daniel@192.38.109.188] has joined #bzr
=== asabil [n=asabil@62.70.2.252] has joined #bzr
=== AnMaster_ [n=AnMaster@unaffiliated/anmaster] has joined #bzr
=== AnMaster_ is now known as AnMaster
=== CardinalFang [n=c@217.194.71.122] has left #bzr ["Leaving"]
=== Govan [n=Govan@62.254.178.211] has left #bzr []
=== abadger1999 [n=abadger1@65.78.187.68] has joined #bzr
=== asabil [n=asabil@62.70.2.252] has joined #bzr
=== zyga [n=zyga@ubuntu/member/zyga] has joined #bzr
=== asabil [n=asabil@62.70.2.252] has joined #bzr
=== BasicOSX [n=BasicOSX@errant.real-time.com] has joined #bzr
=== schierbeck [n=daniel@192.38.109.188] has joined #bzr
=== asabil [n=asabil@62.70.2.252] has joined #bzr
=== asabil [n=asabil@62.70.2.252] has joined #bzr
=== cprov is now known as cprov-lunch
=== herzel [i=herzel@gateway/tor/x-5b7127646a9012da] has joined #bzr
=== jrydberg [n=Johan@c80-216-246-123.bredband.comhem.se] has joined #bzr
=== juliank [n=juliank@f049170213.adsl.alicedsl.de] has joined #bzr
abadger1999Does launchpad support the smart server?05:56
PengYes.05:56
PengIt's even recommended now105:56
Peng!05:56
PengNot sure about bzr+http.05:56
abadger1999Cool.05:56
abadger1999Oh.05:56
abadger1999Does that mean I would need an account of some sort to have ssh?05:56
PengYes.05:57
fullermdI didn't think it did, only the +ssh variant.05:57
=== abadger1999 is not an ubuntu dev
PengI tried to set up a bzr+http server once. It didn't work. Someone else had the same experience too.05:57
=== Peng wanders off.
abadger1999I'm making some speed tests for a blog post and wanted to include smart server times to lp.05:57
abadger1999Guess I'll just include times to a server I have ssh on and note any discrepancy between doing a plain branch operation and smart server branch operation compared to lp.05:58
fullermdI don't think bzr+http is in general significantly faster than http.  It'll gain a little, and the special case of initial mirror may be a good bit faster from the tarball sending thing, but that's pretty fringe...05:58
abadger1999Good to know.  Is http in general faster than bzr+ssh?05:59
abadger1999err.. as fast as.05:59
fullermdWell, theoretically (mod protocol setup overhead), bzr+ssh should be the same speed as bzr+http06:00
fullermdSomewhat axiomatically, http should be slower than bzr+http by some non-zero factor; I think that factor is pretty small outside of very specific cases, though.06:00
=== Zindar_ [n=erik@h188n1fls12o803.telia.com] has joined #bzr
abadger1999Okay.  Sometime when I'm less busy I'll have to run some more in-depth tests.06:01
fullermdNow, bzr+ssh is noticeably faster than sftp.  But that's mostly on writes (and the specific limitations of sftp in that realm), not reads, so that doesn't translate over to http.06:01
abadger1999Okay.  And the initial checkout? (because of the tarball sending)06:02
fullermdToo, there are the currently in-progress (and vaguely hoped for in 0.92) smart server improvements that should make a drastic improvement there, by making the smart server actually smart.  It's pretty dumb overall...06:03
=== dpm [n=dpm@p54A13C3D.dip0.t-ipconnect.de] has joined #bzr
fullermdWell, when it kicks in, that should make the transfer bandwidth limited at the size of the repository.06:04
abadger1999heh, my quick blog post is just to address someone who claimed that bzr branch awn (a project on lp) took 10 minutes.  So the smart server will definitely add another interesting number to the mix.06:04
=== Zindar__ [n=erik@h188n1fls12o803.telia.com] has joined #bzr
=== p4tux [n=p4tux@189.169.63.63] has joined #bzr
=== Lo-lan-do gently pokes jelmer
abadger1999Does anyone know what the scope of this warning in http_smart_server.txt is?06:18
abadger1999**This feature is EXPERIMENTAL and is NOT SECURE.  It will allow access to06:18
abadger1999arbitrary files on your server.**06:18
abadger1999Does it refer to the particular configuration in the file or to limitations of running bzr+http at all?06:19
=== fog [n=fog@debian/developer/fog] has joined #bzr
=== liw [n=liw@a91-154-119-10.elisa-laajakaista.fi] has joined #bzr
Pengabadger1999: It's out-of-date.06:28
abadger1999Even better :-)06:29
=== Zindar [n=erik@h188n1fls12o803.telia.com] has joined #bzr
=== herzel [i=herzel@gateway/tor/x-aaa07f19bb697f08] has joined #bzr
Pengabadger1999: Personally, I'd like to know one of the developers went through the bzr+http code, but I'd be willing to use it.06:30
Pengabadger1999: Tell me if you get it to work!06:30
abadger1999Peng: Cool.  I'll be sure to mention it if I get it running!06:31
=== liw [n=liw@a91-154-119-10.elisa-laajakaista.fi] has left #bzr ["The]
=== phanatic [n=phanatic@dsl5402BA1B.pool.t-online.hu] has joined #bzr
=== jrydberg__ [n=Johan@c80-216-246-123.bredband.comhem.se] has joined #bzr
=== herzel [i=herzel@gateway/tor/x-cd2c1bf736ecab5c] has joined #bzr
=== jrydberg [n=Johan@c80-216-246-123.bredband.comhem.se] has joined #bzr
=== p4tux [n=p4tux@189.169.63.63] has joined #bzr
=== p4tux [n=p4tux@189.169.63.63] has joined #bzr
=== et_ [n=et@ip111.215.dsl-acs2.sea.iinet.com] has joined #bzr
=== et_ [n=et@ip111.215.dsl-acs2.sea.iinet.com] has left #bzr ["Leaving"]
=== bac is now known as bac_afk
sabdflfullermd, abadger1999: there's also the history-horizon stuff, which should make "bzr branch" take about the same time as a tarball download of source snapshot without history07:19
sabdfli think that's post-1.0, though, so December+07:19
abadger1999Nifty.  I didn't realize history horizon would improve performance.07:20
abadger1999Does that mean that it doesn't download history unless it's necessary?07:20
fullermdWell, in the degenerate case, it drops you to a equivalent 'checkout --lightweight' time.  Which doesn't really crank up spiffiness until the smart server gets rather smart.07:20
sabdflabadger1999: the idea is to make it do "asm much as it can" with the history it has availble07:25
sabdflso, bzr log would show the revisions it has07:25
sabdflyou could fetch more revisions to do more07:25
sabdflmerge would bring in just the revisions needed to do the merge07:26
=== allenap [i=allenap@nat/canonical/x-74fb1088cbecdc20] has joined #bzr
abadger1999Thanks for the explanation.07:36
=== GaryvdM [n=chatzill@dsl-241-254-221.telkomadsl.co.za] has joined #bzr
=== cprov-lunch is now known as cprov
=== bwinton [n=bwinton@mail.phantomfiber.com] has joined #bzr
=== hsn_ [n=radim@234.114.broadband5.iol.cz] has joined #bzr
=== schierbeck [n=daniel@disko.egmont-kol.dk] has joined #bzr
schierbeckphanatic: hi08:04
phanatichey schierbeck08:05
phanatici've just rolled out 0.91.008:05
schierbeckcool08:05
schierbeckhave you taken a look at the remove-date-column branch?08:06
=== jamesh_ [n=james@canonical/launchpad/jamesh] has joined #bzr
datophanatic: cool, thanks08:08
=== pmezard [n=pmezard@nor75-4-81-56-59-92.fbx.proxad.net] has joined #bzr
=== jrydberg__ [n=Johan@c80-216-246-123.bredband.comhem.se] has joined #bzr
phanaticschierbeck: yep, but i think we should go with what GaryvdM suggested (allowing the user the select which columns s/he wants to see)08:10
=== grimboy [n=grimboy@85-211-248-46.dsl.pipex.com] has joined #bzr
phanaticdato: yw :)08:11
schierbeckphanatic: okay, is someone working on that atm?08:12
phanatici don't know if GaryvdM does, i hope he can answer that when he returns08:12
schierbeckokay, i was just hoping we could've merged my branch first, and then worked on a more advanced solution later on08:15
jelmerphanatic, congrats on your first release (-:08:16
schierbeckphanatic: should i create a separate branch for the removal of the email part of the committer column?08:17
phanaticjelmer: thanks :) i hope i haven't f'd up anything...08:17
=== Lo-lan-do spots jelmer
Lo-lan-doAha!08:17
phanaticschierbeck: it's up to you08:17
jelmerhey Lo-lan-do08:18
Lo-lan-dojelmer: I'm sorry I was not online during the weekend, hope you weren't waiting for me08:18
schierbeckphanatic: okay, i'll do that -- you'll merge it to trunk?08:18
=== jelmer [n=jelmer@132.207.221.82] has joined #bzr
jelmerhey Lo-lan-do08:19
phanaticschierbeck: sure, just send a mail about that to the list, so we can track them. and don't forget the NEWS entry. i had to hunt down at least 5 missing items before the release :)08:19
jelmerbad timing for a client crash :-)08:19
Lo-lan-doAs I was saying: <Lo-lan-do> jelmer: I'm sorry I was not online during the weekend, hope you weren't waiting for me08:19
Lo-lan-do(Hope you're not fleeing away from me :-)08:20
ubotuNew bug: #144522 in bzr "test suite fails" [Undecided,Fix committed]  https://launchpad.net/bugs/14452208:21
jelmerNah, was travelling08:21
Lo-lan-do'kay.  Did you have time to have a look at my pushing problem?08:23
schierbeckphanatic: btw, do you want me to sign the commits?08:23
jelmerLo-lan-do: working on it atm08:27
Lo-lan-doThat's great!08:27
phanaticschierbeck: it's not neccessary08:31
=== jrydberg [n=Johan@c80-216-246-123.bredband.comhem.se] has joined #bzr
schierbeckphanatic: screw it, i already did it08:32
schierbeck:)08:32
phanatichehe :)08:32
phanaticno problem08:32
phanatici hope it won't break anything08:32
=== bwinton [n=bwinton@mail.phantomfiber.com] has left #bzr []
phanaticjelmer: could you update gnomefiles and freshmeat? i don't have access to those bzr-gtk pages08:32
schierbeckphanatic: i'm thinking of adding some ui for displaying whether a commit has been signed, so i'm planting some data08:33
jelmerphanatic, I'll add you to the list of maintainers of both08:33
phanaticjelmer: thanks!08:33
phanaticschierbeck: sounds cool :)08:33
schierbeckokay, i've got to get something to eat now, see you guys later08:33
abadger1999abentley: When you're around I have some trac-bzr patches.08:35
GaryvdMphanatic, schierbeck: Hi08:37
GaryvdMI'm not working on the columns selector currently.08:37
phanaticGaryvdM: hey, thanks for the update08:37
jelmerphanatic: I've added you on freshmeat08:37
=== Mez_ [n=Mez@ubuntu/member/mez] has joined #bzr
GaryvdMHow is the release going?08:37
=== kiko [n=kiko@canonical/launchpad/pdpc.supporter.active.kiko] has joined #bzr
jelmerphanatic, and you're now owner of bzr-gtk on gnomefiles.org08:39
phanaticGaryvdM: 0.91.0 is out :)08:40
phanaticjelmer: thank, updating those sites now...08:40
phanaticthanks08:40
GaryvdMCool!08:40
phanaticjelmer: freshmeat and gnomefiles updated08:48
lapthrickoooh, jelmer, my favourite bzr-svn maintainer08:48
phanaticschierbeck: subscribe to the list :P08:49
=== cprov [n=cprov@canonical/launchpad/cprov] has joined #bzr
jelmerhey lapthrick08:56
jelmerphanatic, thanks!08:56
lapthrickjelmer: did you have the time for bugfixing love perhaps?08:57
=== Mez [n=Mez@ubuntu/member/mez] has joined #bzr
jelmerlapthrick, I'm working on bzr-svn atm though on a different bug..09:00
lapthrickI see09:00
=== herzel [i=herzel@gateway/tor/x-460c31d9e3cb0b91] has joined #bzr
=== dewd [n=dewd@201009147182.user.veloxzone.com.br] has joined #bzr
jelmerLo-lan-do: can you try the pushing again09:08
jelmer?09:08
Lo-lan-doSure09:09
Lo-lan-dohttp://paste.debian.net/3789609:13
=== jamesh_ [n=james@canonical/launchpad/jamesh] has joined #bzr
=== grimeboy [n=grimboy@85.211.241.150] has joined #bzr
=== Mez [n=Mez@ubuntu/member/mez] has joined #bzr
lifelessabadger1999: the warning is out of date, I believe it is less scary in bzr.dev09:27
abadger1999lifeless: Great.09:28
corporate_cookiedose anyone have a bzr RPM for RHEL4 ?09:28
lifelesscorporate_cookie: I'm not sure, however its really easy to run from source - just unpack it somewhere and add the dir to your path09:30
lifelesscorporate_cookie: as long as you have pythn2.4 or newer, the very core will simply work09:30
corporate_cookielifeless: I need an entry in my RPM database for some dependancy checking09:30
=== duckx [n=Duck@tox.dyndns.org] has joined #bzr
corporate_cookieI've tried to roll my own ..but i'm getting some fun errors ...and I have no clue what they mean09:31
lifelesscorporate_cookie: oh09:31
abadger1999corporate_cookie: Which python version is in RHEL4?09:31
lifelesscorporate_cookie: what sort of errors, ones from rpm ?09:31
abadger1999corporate_cookie: python -c 'import sys; print sys.version'09:33
abadger1999I was pretty sure it was 2.3 :-(09:34
jelmerLo-lan-do: thanks09:34
corporate_cookieabadger1999: its 2.309:34
corporate_cookiehowever ..i have a parallel install of 2.409:34
abadger1999corporate_cookie: Ah.  Then I might be able to help (I build the Fedora and EPEL-5 bzr rpms)09:36
abadger1999corporate_cookie: if you pastebin your errors and spec file I can take a look.09:36
schierbeckphanatic: i thought i already was :) i've done it now09:41
phanaticschierbeck: thanks. your previous mail will appear on the list as soon as we get moderation fixed :)09:41
schierbeckphanatic: cool09:42
corporate_cookieabadger1999: (managers always pick the best times to stop by and check in; pardon my slow responce)09:44
corporate_cookieabadger1999:  im generating the spec ..and rpm with python2.4 setup.py bdist_rpm09:46
abadger1999corporate_cookie: k.09:48
corporate_cookieim pasting the full output09:48
corporate_cookiehttp://pastebin.com/d3738370709:48
abadger1999Hmm... it's unable to find generate_docs.py even though it's in the toplevel directory.09:51
corporate_cookieabadger1999: is this a problem with the python install ?09:55
abadger1999corporate_cookie: I don't think so.  I'm able to replicate it here with the vendor py2.5 install.09:56
=== Lo-lan-do starts hacking his DSL gateway
Lo-lan-doI'll probably blink for a while, but I'll definitely be back :-)09:59
=== grimeboy [n=grimboy@85-211-244-198.dsl.pipex.com] has joined #bzr
abadger1999corporate_cookie: Looks like it's a problem with distutils.10:00
lifelessLo-lan-do: good luck :)10:00
=== bac_afk is now known as bac
=== jamesh_ [n=james@canonical/launchpad/jamesh] has joined #bzr
abadger1999corporate_cookie: Let me see if I can get an old enough version of the bzr spec from Fedora that might work for you.10:01
corporate_cookiethanks : )10:01
ubotuNew bug: #144300 in bzr "bzr log dies on more fancy revisionspecs with bzr-svn branches" [Medium,Triaged]  https://launchpad.net/bugs/14430010:02
=== juliank [n=juliank@f049170213.adsl.alicedsl.de] has joined #bzr
Lo-lan-doBack (yay for TCP timeouts being longer than the reboot time of a Soekris box)10:09
abadger1999corporate_cookie: http://toshio.fedorapeople.org/bzr.spec10:09
corporate_cookiewoo hoo10:09
corporate_cookiethanks abadger199910:09
lifelessbubg 14430010:09
abadger1999corporate_cookie: Have you built an rpm from scratch before?10:09
lifelessbug 14430010:09
ubotuLaunchpad bug 144300 in bzr-svn "bzr log dies on more fancy revisionspecs with bzr-svn branches" [Medium,Triaged]  https://launchpad.net/bugs/14430010:09
jelmerlooks like the ancestor: one is a bzr-svn related bug10:10
corporate_cookieabadger1999:  I have ...but i must admit i've only done it aa few times10:10
jelmerlifeless: but the branch: one is valid for bzr itself too10:10
lifelessyah noticing that10:10
abadger1999corporate_cookie: Okay.  If you have troubles using rpmbuild with that spec let me know and I'll try to work out what's going wrong.10:11
abadger1999corporate_cookie: I don't have a rhel 4 box with python2.4 so I can't test it easily :-(10:11
fullermdThat kinda ties in with but 144421 I filed earlier.10:11
jelmerlifeless: There's no "split" option for bugs in lp yet, right? I'll make a copy10:11
lifelessbug 14430010:12
ubotuLaunchpad bug 144300 in bzr "bzr log -r branch|ancestor attempt to fetch data in a read only transaction" [High,Triaged]  https://launchpad.net/bugs/14430010:12
fullermdNote that my testing was on stat, which fails with branch:.  Using 'diff' instead works, though.10:13
=== ipkiss [i=ipkiss@nat/ecp/x-21648748d30e93c8] has joined #bzr
=== BasicOSX [n=BasicOSX@errant.real-time.com] has joined #bzr
lifelessanother patch up :)10:15
lifelessso jelmer, I'm curious why the new list10:16
AnMasterhttp://pastebin.ca/70960710:17
AnMastershouldn't both report no such command?10:17
AnMasterbzr should handle utf8 everywhere IMO10:18
jelmerlifeless: doesn't require contributors to be on the high-volume bzr list, makes it easier to set up separate bundlebuggy, doesn't clutter the main list with bzr-gtk merge requests10:18
=== hsn_ [n=radim@234.114.broadband5.iol.cz] has joined #bzr
fullermdAnMaster: Are you using a UTF-8 locale?10:18
AnMasterfullermd, I am10:18
lifelessjelmer: OTOH if most of our users use bzr-gtk as well, then until they get used to the other list your contributors won't see their questions10:19
AnMastersv_SE.UTF810:19
lifelessalso slack folk like me with $ too many lists, will be lazy about joining the new list10:19
AnMastersv_SE.UTF-8 even10:19
fullermdAnMaster: It DTRT's for me.  en_US.UTF-8.10:19
AnMasterbzr 0.9010:20
jelmerlifeless: There'll still be bzr-gtk folks like Szilveszter and me around to help with the occasional question on the main bzr list10:20
fullermdbzr.dev and 0.91rc2.  I don't have 0.90 handy at the mom...  wait, maybe I do.10:20
fullermdYeah, works on 0.90 too.10:20
AnMasterfullermd, system is freebsd10:20
fullermdSo're all mine.  I've got taste, after all   ;>10:21
AnMasterit also fails on gentoo10:21
AnMasterhm10:21
AnMasterit fails on my 64-bit gentoo but not my 32-bit gentoo10:21
AnMasteras for freebsd, it is 32-bit10:21
AnMasterweird10:21
fullermdAre you setting LANG, or some of the LC_*'s individually?10:22
AnMasterfullermd, I'm setting LC_ALL10:22
AnMasterLANG is set to C10:22
AnMasterbut, it is same on each10:22
AnMasterfullermd, actually no it isn't10:22
jelmerlifeless: also, two bundlebuggy's on one list doesn't work - at least not with the standard bundlebuggy and standard 'bzr send'10:23
AnMasterfullermd, but well both gentoo got LC_COLLATE set to C as well10:23
AnMasterand one of those worked10:23
AnMasterso makes no sense10:23
fullermdI've never tried mixing and matching.  I just have LANG=en_US.UTF-8 on my systems, LC_ALL stays blank, and the other LC_*'s follow it.10:23
fullermdI get a headache every time I try to figure out more intricate setups and precedence   :|10:24
AnMasterfullermd heh10:24
fullermdBut that's where I'd guess the problem is; it ends up seeing a 7-b ASCII encoding rather than a UTF-8 because of whatever vagary of interpretation of the mixing, on those systems.10:26
AnMasterbtw who should I complain to about trac-bzr?10:26
AnMasterthe trac ppl or you here?10:26
fullermdProbably someone here.  Not sure who, though...   I think abentley did some work on it, but I don't know if he's currently looking at it.10:27
AnMasterhttp://kuonet.org/~anmaster/envbot/trac/timeline <-- see two weird changesets at top10:27
lifelessjelmer: re BB thats really just a bug :)10:27
AnMasteralso I get messages like:10:27
AnMaster/usr/local/lib/python2.5/site-packages/TracBzr-0.2-py2.5.egg/tracbzr/backend.py:674: DeprecationWarning: bzrlib.revisiontree.RevisionTree.get_weave was deprecated in version 0.90.10:27
AnMaster  weave = self.tree.get_weave(self.entry.file_id)10:27
lifelessI don't like the idea that folk have to have a list to use BB properly.10:27
AnMaster:/10:27
AnMasterfullermd, ^10:28
AnMasterbzr is 0.9010:28
AnMastertrac and trac-bzr are last from ports on freebsd10:28
fullermdYeah, that would be a 'bzr API moving ahead, trac not keeping up' thing.10:28
AnMasterfullermd, same for the broken changesets ?10:28
fullermdOh, I don't know trac or trac-bzr well enough to say, but it could be a suspicious coincidence.10:29
AnMasterfullermd, also did bzr do a version jump, it seemd to be around 0.15 just some months ago then I turned my back for a few months and it is suddenly at 0.9010:29
AnMaster?10:29
lifelessjelmer: for instance, one could give BB a submission address, rather than the list. Then BB mails the list as things come into it10:29
jelmerlifeless: Yup, I agree. I don't think it's likely that support for determining whether a revision is relevant for a particular project is going to be added soon though and working with a separate list is much easier than adding such support.10:29
fullermdbzr port is up to date.  trac-bzr is from March, though, so I dunno.  I don't have any involvement with the trac side...10:29
fullermdAnMaster: Yes, it jumped from 0.18 to 0.90.10:29
AnMasterfullermd, reason?10:29
lifelessjelmer: This would be trivial, all you need is BB to forward the message rather than just linking to it.10:30
lifelessmuch simpler than what you're talking about10:30
fullermdAnMaster: Well, _I_ stick by the belief that it's a bit error in memory somewhere...     :p10:30
jelmerlifeless: so you have to send merge requests to both the list /and/ bundlebuggy?10:30
lifelessjelmer: no10:30
AnMasterfullermd, and the official reason?10:30
jelmerlifeless, that sounds more complicated than joining an additional mailing list10:30
fullermdAnMaster: The theory behind it was to express some sense of progress toward 1.0.10:31
AnMasterfullermd, anyway, I need to know who to complain to really about trac-bzr10:31
lifelessjelmer: rather than --mail-to bazaar-at-blah, its --mail-to bundle-buggy10:31
jelmerlifeless: that means the development process for bazaar would have to change as well10:31
jelmerlifeless: otherwise bzr's bundlebuggy would pick up the bzr-gtk merge requests10:31
lifelessjelmer: its a trivial change10:32
lifelessand its not like we're static, we change what, monthly?10:32
fullermdAnMaster: Well, you may have to bug Radim about it.  I'm not sure there are any 'official' releases; it looks like a snapshot that he rolled and hosts himself for the port.10:32
jelmerlifeless, it requires all contributers to change how they work, docs on submitting merge requests to change, etc10:32
AnMasterfullermd, who? *confused, just a user*10:32
fullermdAnMaster: I'm not sure where the 'official' upstream is, to check if there are catchup changes.10:32
fullermdAnMaster: The port maintainer.10:32
AnMasterah10:32
lifelessjelmer: yes, I understand that.10:32
lifelessAnMaster: we jumped to 0.90 because some people judge 'progress' by 'how close to MAJOR.0'10:33
AnMasterfullermd, /usr/ports/www/trac-bzr/pkg-descr says http://bazaar-vcs.org/TracBzr10:33
lifelessAnMaster: and while we were happy moving point release by point release, it wasn't clear to folk casually perusing, how mature a project this is.10:34
AnMasterlifeless, ah10:34
lifelessAnMaster: (we think its pretty mature)10:34
AnMasterI always find a project that jumps versions like this suspect10:34
jelmerlifeless: I think getting that changed would take a lot more time than setting up an additional list10:34
jelmerlifeless: if you really feel having an additional list is a problem, please bring it up on the bazaar list10:35
lifelessjelmer: I wasn't claiming it was a problem, I was asking why.10:35
fullermdAnMaster: Well, there aren't any fixed for that sort of problem on Aaron's branch; there's hardly anything recently.  I'm not sure if someone else's is the "main" branch now.  You could try asking on the list.10:35
lifelessit surprised me is all, and it makes more work for me10:35
fullermd(fixes)10:35
AnMasterfullermd, what list? not mailing list I hope, I hate mailing lists10:35
lifelessjelmer: so enough said, nothing to see here, moving right along10:36
fullermdAnMaster: Oh.  Well, forget I said anything, and poke Radim them   :] 10:36
AnMasterfullermd, and where do I get hold of him?10:36
fullermdcd /usr/ports/www/trac-bzr/ && make -V MAINTAINER10:36
AnMasterah10:37
lifelessphanatic: good to see you around again ;)10:39
abadger1999AnMaster: I have patches to make those changesets slightly less wierd.10:40
=== jelmer [n=jelmer@132.207.221.82] has joined #bzr
AnMasterabadger1999, oh?10:40
abadger1999AnMaster: Let me dig up the launchpad bug10:40
AnMaster:)10:40
fullermdOh good!10:41
abadger1999AnMaster: https://bugs.launchpad.net/trac-bzr/+bug/11665910:41
ubotuLaunchpad bug 116659 in trac-bzr "Phantom changesets in timeline" [Undecided,Confirmed] 10:41
=== fullermd pawns off the trac issues on abadger1999 and runs away while he can.
abadger1999I've been working on the assumption that abentley's branch is canonical.10:41
=== Mez [n=Mez@ubuntu/member/mez] has joined #bzr
AnMasterabadger1999, hm10:41
phanaticlifeless: thanks, but actually reviewing patches and managing a release takes more time than just hacking :)10:41
AnMasterI think I will mail ports maintainer either way10:42
AnMasterso everyone can make use of it10:42
abadger1999yeah.  It would be good.10:42
fullermdHm.10:42
fullermdhsn_: Around?10:42
lifelessphanatic: indeed it does10:42
hsn_fullermd: yes10:43
fullermdhsn_: Oh good.  See above discussion about trac-bzr port compatibility with current bzr.10:43
fullermdQuicker than email   :] 10:44
=== lapthrick [n=mathrick@users.kollegienet.dk] has joined #bzr
jelmerlifeless: Sorry, you said it takes more time for you, that's why I figured you considered it a problem. Anyhow, I'll let it rest.10:45
AnMasterabadger1999, sent mail to trac-bzr maintainer10:48
abadger1999AnMaster: Cool -- I think hsn_ is that maintainer :-)10:49
AnMasterabadger1999, sent it to output of that command fullermd gave me10:49
AnMasterbut yes hsn was in the mail10:49
hsn_abadger1999: you think right10:50
AnMasterhsn_, got my mail right?10:50
lifelessjelmer: it does, but I patch bzr-gtk what, once a month? If that? So I'll ignore it until my next patch, if its more convenient for the folk doing the coding that is the important thing.10:50
AnMasteryet*10:50
=== Mez [n=Mez@ubuntu/member/mez] has joined #bzr
AnMasterbtw, does source forge support bzr? I don't really like launchpad, it is slower than sourceforge even (and that is pretty slow) and it looks ubuntu-ish, and is confusing10:51
fullermdIn theory, you could just host the bzr files in project webspace.  I suspect it's probably at least moderately frowned on, though.10:52
datoAnMaster: bzr can be served over a normal http server, so there you go10:52
abadger1999hsn_: Cool. I'm packaging trac-bzr for fedora so if we need to work on standardizing on someone's branch as canonical or cooperating on getting bugs fixed feel free to ping me.10:52
AnMasterdato, hm true10:52
AnMasterdato, but does pycurl fail at bzr branch http://kuonet.org/~anmaster/bzr/envbot for anyone but me10:53
AnMastersome users reported problems10:53
AnMasterlighttpd on freebsd10:53
fullermdSF is probably better connected (depending on where you are).  A lot of the slowness may be just bzr, though...10:53
AnMasterit works with urllib10:53
AnMasterfullermd, yes pushing almost half a minute to my current web server10:54
jelmerlifeless: But why is it more work? subscribing takes less than a minute10:54
AnMasterbut anyway, why is pycurl broken for that site10:54
=== jamesh_ [n=james@canonical/launchpad/jamesh] has joined #bzr
lifelessjelmer: subscribing, managing the mail to a new folder, remembering to check that folder, remembering to send to a different list, moving discussion cross-list as needed10:55
fullermdAnMaster: Hard to say, probably.  pycurl will probably have somewhat different characteristics (request rate and accel, number pipelined, number keepalive'd, blah blah) than urllib.  What about it is significant, though..10:56
=== asabil [n=asabil@ti0035a340-0469.bb.online.no] has joined #bzr
AnMasterfullermd, a user who did some debugging said it somehow borked with certain range requests10:57
lifelesshmm10:58
lifelessperhaps we should make disabling pycurl easy without uninstalling it10:58
lifelessvila: ^ ?10:59
fullermdI thought we had a discussion just last month-ish about turning off default-enable-if-found on it, and just saving it for explicit http+pycurl10:59
lifelessAnMaster: we've had a bunch of issues with lighthttpd IIRC10:59
lifelessfullermd: sounds vaguely familiar10:59
lifelessAnMaster: or some http server, sending bad range responses11:00
lifelessfailing to serve our requests ok11:00
lifelessand this forces us to fallback to slower means11:00
lifelessor error11:00
lifelessbbiab11:00
=== fullermd also passes the buck to vila.
AnMasterlifeless, ah11:01
AnMasterlifeless, for now I tell my users to use http+urllib://...11:01
fullermdI think in the current state, urllib is generally preferable anyway, so you don't lose much that way.11:02
AnMasterhsn_, so, how long can it take to get a fixed version into ports? :)11:02
hsn_AnMaster: if you submit patch, it can be quite fast11:03
AnMasterhsn_, I sent a link to the patch yes in my mail to the maintainer11:04
AnMaster:)11:04
AnMasterand that was you11:04
hsn_did you tested patch?11:04
AnMasterhsn_, not yet I sent a link to the bug report to be exact11:05
AnMasterbut I will test in a bit11:05
AnMasteronce I find out how to patch this in the correct way to test it11:05
hsn_ok. test it and report it back to me11:05
AnMasterI don't know, should I edit the port?11:05
hsn_yes, edit port11:06
AnMasterhsn_, or how to do it without making package manager loose track?11:06
AnMasterhsn_, um, and what with portsnap do then?11:06
hsn_put patch in files/ directory11:06
fullermdAnMaster: Copy the port dir somewhere else (in /tmp, say) and work on it there.  It doesn't have to be under /usr/ports to work.11:06
hsn_recompile port, test, install porttools and do port submit11:06
AnMasterfullermd, oh? cool11:06
fullermdThen you can diff against the 'main' one to gen the patch.11:06
AnMasterhsn_, hm11:06
fullermd's how I do it (actually, I cvs co from my local CVS mirror in /tmp, but 6 of one, half a dozen of the other...  either way)11:07
AnMasterhsn_, um, I got to sleep now, it is late here11:08
=== zyga [n=zyga@ubuntu/member/zyga] has joined #bzr
AnMasterI will do it tomorrow11:08
=== zyga [n=zyga@ubuntu/member/zyga] has joined #bzr
=== mgedmin [n=mg@c-24-218-183-144.hsd1.ma.comcast.net] has joined #bzr
mgedminI can't use bzr diff to look at my changes while I'm editing the commit message for bzr ci?11:37
jelmerphanastic: ok, pqm is up at http://145.97.196.157:8089/11:38
=== bac is now known as bac_afk
=== orospakr [n=orospakr@132.213.238.4] has joined #bzr
james_wmgedmin: no you can't I'm afraid. With 0.91 you can use bzr ci --show-diff to get the diff in the message editor.11:57
=== mgedmin weeps

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