/srv/irclogs.ubuntu.com/2013/01/11/#bzr.txt

=== slank_away is now known as slank
=== slank is now known as slank_away
MerwinHi ! Can I get a shelf as a patch I could apply ?08:30
=== yofel_ is now known as yofel
vilaMerwin: From a clean tree: bzr unshelve ; bzr diff >my.patch08:55
MerwinOk, that's what I thought but I hoped for a way without unshelving ;)08:59
MerwinThanks08:59
Merwinvila: How to do on windows ? ">my.patché doesn't work09:45
vila>-/09:45
vilaI can't imagine why...09:45
vilaanything more specific than "doesn't work" ?09:46
Merwinvila: Forget, I'm stupid. Thanks ;)09:56
vilanever thought you were stupid ;)09:57
=== mmrazik is now known as mmrazik|otp
=== mmrazik|otp is now known as mmrazik
xnoxvila: wasn't there like --preview?10:44
xnoxbzr unshelve --preview10:44
vilaxnox: doh ! indeed10:45
vilaMerwin: better ^10:45
* jelmer waves to Vila and xnox10:47
* mgz waves to jelmer10:52
jelmerhi mgz10:56
Merwinthx vila :)10:57
* vila waves to mgz and jelmer ;)10:58
vilaMerwin: np and sorry, see who's the idiot now ? ;-)10:58
=== mmrazik is now known as mmrazik|lunch
Merwinvila: :-)11:03
vilajelmer: got a sec ?11:16
=== mmrazik|lunch is now known as mmrazik
jelmervila: I'm boarding a plane in 40 min, but should be around until then12:36
jelmerwhat's upm12:36
jelmer?12:36
vilajelmer: I think I found a bug in svn_canonicalize_path (deprecated by svn_uri_canonicalize still buggy): it can return an url where ( and ) are not quoted :-/12:42
vilathat triggers in a parameterized test..12:43
jelmervila: yeah, unfortunately svn doesn't expect them to be quoted12:48
jelmerwe hit other bugs where bzr was escaping them and svn expected them not to be escaped :-(12:48
vilajelmer: quite amazing considering it *unquotes* them...12:48
jelmervila: it returns its canonical version of the URL, and that means parentheses aren't quoted12:49
jelmerat least, that's my understanding of it.12:49
vilajelmer: ok, so there are precedents, I was wondering if I was wrongly doing something, at least I know it's not me (and I ended up in svn_path_canon... after digging from bzr-svn, hence my first ping)12:49
vilajelmer: huh ?12:49
vilaparens should be quoted according to ... (whatever, closed the page ;)12:50
jelmervila: not according to svn ;-)12:50
vilaha, ok, makes sense ;-D12:50
vilajelmer: enjoy your flight ;)12:53
jelmervila: thanks (-:12:53
jelmervila: anyway, so I think bzr-svn in general could use some work to make it consistently translate between svn URLs and bzr URLs - at the moment we sort of assume that they're interchangable12:54
jelmerapart from the base, that is12:54
vilaright, so the full story is that there is an assertion checking with startswith but the compared urls are not coherent (one is quoted, not the other, so fail), commenting out that assertion leads to a failure later, so it *seems* bzr-svn can't work around it :-/12:56
jelmerwell, one is bzr-quoted, the other is svn-quoted presumably?12:56
vilastarting with a bzr quoted one, one stays correct, the other is unquoted in _ra.RemoteAccess by svn_path_canonicalize12:57
jelmervila: that's not really "unquoted". that's svn-quoted12:58
jelmertomato, tomato I guess :)12:59
vilaha right, sorry, not accustoomed yet ;)12:59
jelmeri.e. this only really matters for parentheses I think12:59
vilaha found the page back http://en.wikipedia.org/wiki/Percent-encoding, haven't looked in detail at svn sources but there is more than parens (see url)13:01
vilabut well, you can hardly fix that in bzr-svn right ?13:02
jelmervila: sure, it can be fixed in bzr-svn13:02
jelmerwe just need to make sure to correctly re-quote stuff that comes back from svn13:03
vilaha, right, but whack-a-mole may take more time than I want to spend here :-/ I came across it while refreshing my memory in bzr-gardener running the test suite there...13:04
jelmerah, yeah - I remember that test failure13:04
jelmerthat said, you should have hit a fair number of other issues if you ran the bzr-svn testsuite13:05
vilano, only the gardener one but since it's parametrized it grabs some svn stuff via the formats13:05
jelmersvn 1.7 breaks it fairly badly; it's probably useless as-is in raring :-(13:05
vilaouch13:05
vila...and compiling subvertpy mention svn_pacth_canonicalize is deprecated13:06
vilabut I'm still in quantal here13:06
jelmerhmm, it looks like quantal actually has 1.7 too13:08
jelmerI guess it might be okay if you are just running some of the code that happens to be using bzr-svn13:08
jelmerthe bzr-svn testsuite itself triggers an abort IIRC13:09
vilayeah, that's what I'm doing13:09
=== slank_away is now known as slank
=== slank is now known as slank_away
=== slank_away is now known as slank
Luke-JrIf I have a bzr repository, and I want to add revisions prior to its initial commit, how can I do that?16:45
Luke-JrI'm aware it will likely break compatibility with the pre-rebased branches, so I've avoided publishing them so far16:46
LeoNerdLuke-Jr: Make a new branch with the new initial commit, then  bzr replay  the original branch on top of it..?18:28
mgzyeah, new branch, make changes there, then replay or `bzr merge -r0..-1` the original branch on top18:29
paultag(sorry for the phrasing, I'm a git user) -- anyone know how I can use bzr to branch a repo similar to git's "bare" mode (but have it branched from a remote location)18:45
mgzexplain what that does, so I don't have to google "git bare"?18:46
paultagit's a mode similar to bzr repo-init18:46
paultagbasically, server bits for hosting, rather then a working tree18:46
paultagsorry, init-repo18:47
mgz`bzr branch --no-tree`?18:47
mgzor just push to a remote location, which doesn't create a working tree18:47
paultagah, --no-tree might be good18:52
paultagmgz: I'm using bzr-git :)18:52
paultagI had to patch it, because Launchpad chokes on signed git tags18:52
paultagso I'm just going to mirror on a cron18:52
paultaglet's see here18:52
paultagahha! Nice, thanks mgz18:53
mgzupstreaming any bzr-git patches would be nice18:53
paultagACK, it's been orphaned by jelme[r], and my patches do the wrong thing (ignore it, rather then handle it with grace)18:53
paultagbut I'll see if I can't find a better long-term solution and see if it'll get upstream'd18:54
mgzthat would be ace.18:54
paultagruddy brilliant, thanks mgz.18:54
paultageverything works nicely18:54
qenghoI seem to run into "different rich-root support" more than most people. I think something might be wrong.19:04
qenghoSo, I have two local branches.  Both say "Standalone tree (format: unnamed)" with "bzr info" on bzr 2.6b2, but they have d r-r s. I'm not sure what to do.19:06
mgzqengho: use `bzr info -v` in both?19:08
qenghohttp://pastebin.ubuntu.com/1520703/    mgz, I see.  Different branch and repo formats.19:11
qenghomgz: that higher version is the odd man out, so I think I want to downgrade its format.19:12
mgzright, either upgrade everything, or make sure you use the same old format19:13
mgzthe thought of chromium not using 2a is somewhat terrifying19:13
qenghoIt's just packaging.  They use Svn and some wrappers and some git thing somehow for the code.19:14
mgzall those nice performance fixes to large-branches going unused...19:14
qenghoas the "bzr info" says, 71 files, in 800 revisions.19:15
mgzah, it's literally just the packaging?19:16
qenghomgz: Yes.19:16
qenghomgz: "bzr upgrade" takes an argument, but "bzr info" doesn't actually name a format.19:17
qenghoOr, it names four.19:17
qenghoif a numberis a name.19:17
mgzqengho: you probably want to look on the bazaar mailing list for threads about this back from when the 2a switch was done :)19:18
qenghoEw, email.19:19
fullermdThere isn't a way to backgrade to poor roots.19:19
mgzfullermd: but you can bring the changes over to a old-format branch via one hack or another19:19
fullermdPotentially, yeah, but the hacks get real grody real fast.  Gonna be simpler to just pile up some diff|patch-ery unless you're talking about hundreds of revs or something.19:22
jelmerpaultag: ignoring sigtag will almost certainly cause checksum errors at some point in the future19:22
fullermdAnd if you are, it's time to catch up to 2009 and just move everything to non-ancient formats anyway   :p19:22
paultagjelmer: erm, hurm.19:22
paultagcrap.19:22
jelmerpaultag: basically, whenever git has a delta base that is a commit object with gpgsig19:23
paultagOhhh, I see it now.19:23
paultagHurm, OK19:23
paultagwell I'll be sure not to do that ;)19:23
jelmerpaultag: as bzr-git won't be able to generate the right git object from the bzr data19:23
paultagACK19:23
paultagjelmer: is this something I could patch around sanely if I spent some time on it, or is it a lost cause to fight that19:23
paultag(and end up stripping git tags for the bzr branch import)19:23
paultag(and here I thought I was being clever with a 2 line patch)19:25
jelmerpaultag: one sec, let me grab my laptop19:25
paultagjelmer: don't spend too much time, on me it's a silly silly thing, I was just trying to get dput-ng nightlies, I can totally work around it19:25
jelmerpaultag: ok, back19:25
paultagthanks jelmer, sorry!19:26
jelmer(phones are terrible for non-trivial IRC conversations..)19:26
paultagyeah, sorry, sorry19:26
paultagI didn't mean to bug you19:26
paultag(tried to avoid a ping)19:26
jelmerpaultag: I don't think there really is a way to fix this properly without spending a day or two on it19:26
jelmerpaultag: that's quite alright :) it would be nice if somebody fixed this, as it's going to be hitting more and more bzr-git users19:26
jelmerpaultag: but I don't think there is an easy fix like a two-liner :-/19:27
jelmerpaultag: another alternative is to actively strip the gpgsig data from the git repository involved (so the git sha1s change appropriately)19:27
paultagI'd not mind fixing it, I know dulwich fairly well (used it for $WORK a few times to track DB changes), but is it going to involve going wrist-deep into bzr internals?19:27
paultag(I'd also be happy to fold it into a QA upload against your package, which I see is now O'd)19:28
jelmerit is going to involve a fair amount of bzr-git internals. you'll have to chuck the gpgsig data in a bzr revision property, and possibly deal with older bzr-git versions that handle that data well.19:28
jelmers/that handle/that don't handle/19:29
paultagack19:29
paultagoh, I see.19:29
paultaghurm.19:29
paultagright, and trying to trick it into convering a signed → unsigned should (rightly) blow it up19:31
paultagOh, OK, I see where this would break.19:31
paultagyikes.19:31
jelmerpaultag: yes, because that changes the commit SHA119:31
paultagright, ack19:31
paultagok, so the fact this is working now means I'm really, really, really lucky :)19:32
jelmerwell, bzr-git only generates the old git object text from the bzr data when it receives a delta with that data as base19:32
paultagand since commits are based on the thing the git tag ref's, that's not been the case19:33
paultagI see, I see.19:33
paultag(still think it's more luck then anything else now ;) )19:34
jelmeryes, luck is a big part of it (-:19:34
paultagthanks jelmer, you've been a huge help :)19:34
paultagsorry to keep bugging you with this!19:34
jelmerpaultag: sure, not a problem. sorry I couldn't give you better news on your 2-liner...19:35
paultagnah, it's fine, I was shocked I could just drop an if / exception and not have everything blow up, so I was kinda expecting this19:35
iamvshalhi I am trying to get this branch22:13
iamvshalbzr branch lp:openobject-addons/6.122:13
iamvshalhowever it always gives and error after some time22:13
iamvshalWrite failed: Broken pipehing revisions:Inserting stream:Estimate22:14
iamvshal182361/18248722:14
iamvshalbzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and22:14
iamvshalpermissions, and report a bug if problems persist.22:14
iamvshalI did search but did not find anything usefull22:14

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