[01:26] jelmer: ping [01:41] markh, pong [01:42] hi jelmer - a couple of things - the 0.4 branch is still what I should be using for windows 1.7 builds? [01:43] markh, yep [01:43] and have you seen the thread on the mailing list talking about the crash? [01:43] identifying the env var etc [01:43] the DLL mess you mean? [01:43] well - its not that bad as it turns out [01:44] "As it happens, on my system APR_ICONV_PATH was set to c:\program files\subversion\iconv (perhaps created by a SVN installer)" [01:44] from the most recent mail in the thread on the mailing list [01:44] which leads to question 2 1/2 :) he suggests using svn 1.5 libs would be a good option [01:45] using 1.5 instead of 1.4 would always be a good idea [01:46] and I believe he is suggesting we just ensure to clobber that env var before loading svn [01:46] bb in 20 mins... [01:47] I'm not sure that's going to work in all situations [01:47] I'm getting some sleep in a few minutes [01:48] markh, Will be back tomorrow CET time === mw is now known as mw|out [03:51] poolie: i don't want to be a pest, but are you going to land http://bundlebuggy.aaronbentley.com/project/bzr/request/%3Ce01316480809050416r72b3f857h4a664a2cc4e157b0%40mail.gmail.com%3E ? [03:52] !! [03:52] i did send it [03:52] hm that kind of sucks [03:53] i don't think it's in bzr.dev, it's possble bb is out of date [03:57] doesn't seem to have landed [03:59] it may have bounced [03:59] we'll need to get that into 1.7 [04:00] thanks for reminding me [04:00] yes please :) [05:03] Hm. http://live.gnome.org/Bazaar says "For best performance, install 1.6b2." [05:10] what do I need to do to serve bzr+http files from my apache? [05:11] or is there a bzr plugin that will create a mini-server that will do the same? [05:12] jml, i think there is documentation on how to hook it up in mod_python [05:12] but also tim will know about the mini-codehost project [05:12] which may help [05:13] well, it's mostly for testing purposes. [05:13] so even something launched a toy web server with support would be fine for me. [05:19] poolie: how do you spell NULL_REVISION for weave repos? [05:20] it should be the same, but old code might use None [05:20] thanks. [05:30] jml: bzr+http is very simple to set up. Take the script from the documentation, put it somewhere, then use mod_rewrite or something to point "foo/.bzr/smart" to it. [05:30] It just uses WSGI, so you can use CGI or FastCGI or mod_wsgi or whatever you want. [05:31] Peng_: the docs are in the bzr source tree? [05:31] jml: http://doc.bazaar-vcs.org/bzr.dev/en/user-guide/index.html#serving-bazaar-with-fastcgi [05:32] Peng_: thanks. [05:53] hi bazaarmens [05:53] please a question [05:53] Evening. Does bzr support 'forests' well. ie, I have a dozen projects that I want to maintain individual revisions/logs for, but be able to update/check them all out en masse if I work on a different terminal for instance. [05:54] i make a copy of brach, and in copy i make a new file. I use "bzr merge" to update the parent branch, but merge not copy new file [05:55] MolePrince: the bzrtools plugin has 'multi-pull', which may be close to what you want. [05:55] jml: Thanks, I'll look into that. [05:55] seyacat: did you do 'bzr add ' and then 'bzr commit' in the copy? [05:56] yes i make "add" and "commit" [05:56] seyacat: hmm. can you pastebin the exact commands you used, starting with the copy? [05:59] where is pastebin? [06:00] F:\bzrtest\copia>bzr status [06:00] unknown: [06:00] prueba/newfile.txt [06:00] F:\bzrtest\copia>bzr add prueba [06:00] added prueba/newfile.txt [06:00] F:\bzrtest\copia>bzr commit [06:00] Committing to: F:/bzrtest/copia/ [06:00] added prueba/newfile.txt [06:00] Committed revision 4. [06:00] F:\bzrtest\copia>bzr merge [06:00] Merging from remembered parent location F:/bzrtest/repo1/ [06:00] Nothing to do. [06:00] MolePrince: You're looking for "nested trees". In-progress feature. [06:01] it can be a windows bzr problem? [06:02] seyacat: No, you're doing it backward. That bzr merge is trying to merge new stuff FROM repo1 INTO copia. If you want to merge new stuff FROM copia INTO repo1, you need to cd ../repo1 ; bzr merge ../copia [06:04] yes i can see ita work... and what is difference with pull command? [06:05] Roughly speaking, 'pull' updates your copy of another branch. 'merge' merges in changes from the other branch into yours. [06:11] aaa i cant make chain checkouts branches [06:13] * fullermd doesn't know what that means... [06:13] im very very happy, i understand bzr at last, its nicer than i think [06:14] ty fullermd , you are a good suppot [06:14] np :) [06:16] well done [06:29] the links to modpywsgi are broken :( [06:39] ok, now I'm getting this error when I try to branch via bzr+http: http://paste.ubuntu.com/45643/ [06:41] jml: I think it's 1.6b4 problem [06:41] * jml updates that branch [06:41] it's fixed in 1.6.1 [06:43] ok, now I'm just getting 'not a branch', which makes me happier. [06:52] markh, re bug 251701 do you know if paramiko is sure to be in the windows binaries now? [06:52] Launchpad bug 251701 in bzr "windows stand alone v1.6 does not include parmiko - seriosly breaking expectaions." [Undecided,New] https://launchpad.net/bugs/251701 [06:53] hrm [06:55] poolie: that surprises me. it was in the first few builds I made, and it seems be in the last 1.6 build I made [06:56] it may be invalide [06:56] or user erro [06:56] i'd appreciate if you could look [06:56] Good morning Bazaar [06:59] vila: Good morning. [06:59] why do the http smartserver instruction say to do: Alias /srv/example.com/scripts/bzr-smart.fcgi /srv/example.com/scripts/bzr-smart.fcgi [06:59] that seems... redundant. [07:02] poolie: it is also certainly there in 1.6.1 and 1.7 builds [07:03] I suspect that bug was user error, but just marking it as "fixed" would work. [07:14] small doc patch on the list. [07:14] massive review karma going for cheap [07:15] * markh just had the brain-wave he could close it, so did... [07:17] jml: because I suck at configuring apache [07:17] jml: I twiddle until it works, and then I twiddle some more to tidy up, and things mysteriously break, so I undo that and just go with messy-but-working and get on with more important things. [07:18] oh right. [07:18] spiv: well, my patch makes things a little better. [07:39] Peng: so, I'm looking at a development copy of Launchpad, mirroring branches from a bzr+http server on my own laptop. it makes a lot of posts to .bzr/smart (as well as a few GETs of control and format files) -- I'm guessing that's bzr+http mirroring. [07:45] jml: What? [07:45] Peng_: you know about bug https://bugs.edge.launchpad.net/launchpad-bazaar/+bug/245918? [07:45] Launchpad bug 245918 in launchpad-bazaar "Puller should use bzr+http when it can" [Medium,In progress] [07:45] Right. You got it working? [07:45] Could someone do me a favor? Try to 'bzr branch http://bzr.mattnordhoff.com/bzr/imports/lighttpd/trunk/' outside of a shared repo with 1.7rc1 or bzr.dev. I get a format error (it's a rich-root-pack branch). nosmart+http works fine though, and so does branching locally. [07:46] Peng_: well, I *think* it's working, but what I want to know is "how do I know when it's working" [07:46] I think I found a bug in bzr-svn: Can someone try to branch svn://uclibc.org/trunk/buildroot ? [07:46] POSTs to .bzr/smart is smart-over-http, yes. [07:47] Peng_: I get http://paste.ubuntu.com/45655/ [07:47] spiv: thanks. [07:51] jml: Yeah, that's what I get. That would be a bug, then. [07:53] Actually, I have the same issue in 1.6.1. [07:54] And "bzr info" says it's an unnamed format, so now I'm totally confused. [07:55] "bzr info -v" is helpful when it says unnamed. [07:56] It's often just format 5 branch with pack-0.92 repo. [07:58] I have a format 7 branch in a rich-root-pack repo. [07:58] Is that not how rich-root-pack is supposed to be? [07:58] Which is branch 7? [07:58] 'supports stacking' [07:58] It allows stacking, IIRC. [07:59] Oh, really? How did I get that? [08:00] Hmm, my local copy is Branch6 as it should be. [08:01] So...when does bzr decide to upgrade remote branches to support stacking? [08:02] And then not upgrade the repo? [08:02] I would have assumed when --stacked is used. [08:02] But that doesn't explain your situation. [08:02] spiv: It tries to upgrade the source branch? [08:02] Check your ~/.bzr.log? [08:02] I may have tried to branch --stacked from it as a test, but I don't even remember doing that. [08:02] I'm not very familiar with this end of things. [08:03] spiv: What do I grep for? "Upgrading random branch for fun"? [08:03] AFAIK bzr never silently tries to upgrade anything. [08:03] Right. [08:03] Maybe search your bzr.log for --stacked? [08:03] Oh, good idea. [08:03] I am not in the mood for figuring out weird bzr issues. Hmph. [08:04] So far I'm guessing it's a weird user issue ;) [08:04] Grep says I have never used --stacked in my life. [08:05] At least in the history of my .bzr.log [08:06] OK, here we go. According to .bzr.log.old, I twice tried to "bzr branch --stacked" that branch locally. [08:06] But it upgrades the source branch? That makes no sense. [08:06] I doubt it. [08:07] Maybe you simply pushed the local --stacked branch up? [08:07] And bzr push then preserved the format (but not the stacking)? [08:07] Both times I tried to "bzr branch --stacked", it yelled at me about IncompatibleRepositories. [08:07] In that case, no idea. [08:07] Is the bzr-svn stable, or should I expect vital bugs? [08:07] :) [08:08] I scared poolie away. :( [08:08] Maybe check .bzr.log on the server in case someone is did something strange on that end? [08:08] Peng_: nah, he just hopped on his bike and went home. [08:08] spiv: I did check .bzr.log on the server. [08:08] speakman: it's been stable for me [08:08] Peng_: dang. There goes another idea. [08:08] On my PC, I have never once used --stacked in the history of .bzr.log and .bzr.log.old. [08:08] spiv: could you please try to branch svn://uclibc.org/trunk/buildroot ? [08:08] On the server, I twice tried to locally "bzr branch --stacked" that branch, and both times it failed. [08:09] * Peng_ blames poolie since he's not here. :) [08:09] speakman: I don't have the spare bandwidth for that atm, unfortunately :( [08:10] How big is that branch? I have spare bandwidth, but not spare RAM. :) [08:10] speakman: are you getting an error? [08:10] Peng_: the current bzr-svn release is much friendlier RAM-wise. [08:11] (compared to early this year) [08:13] True [08:13] beuno: ping? [08:14] UnicodeDecodeError: 'utf8' codec can't decode bytes in position 85-87: invalid data [08:15] can I make bzr run under ipython, and use ipython's more informative traceback? [08:17] it seems to crash in the "insert_revprop" function in logwalker.py [08:17] self.cachedb.execute("replace into revprop (rev, name, value) values (?, ?, ?)", (rev, name.decode("utf-8"), value.decode("utf-8"))) [08:19] Verterok: everyting fine - just tested it. [08:19] a7p: great! :) [08:19] should I confirm the bug fixed on lp? [08:20] Verterok: thanks a fixing it. [08:20] a7p: no, I marked it as "Fix committed", but if you encounter any problem, just reopen it :) [08:21] a7p: np, this new build also comes with some extra goodies ;) [08:21] Verterok: I saw that, that's why I asked if futher confirment is needed. [08:22] Verterok: I am going to check it out as soon as I finished this (ugly) flash project I am suffering from at the moment. [08:22] beuno: Never mind about the ping. I just filed bug 268867. [08:22] Launchpad bug 268867 in loggerhead "Breadcrumbs ignore PrefixMiddleware" [Undecided,New] https://launchpad.net/bugs/268867 [08:22] a7p: ok, just let me know if you hit that bug again [08:23] Verterok: I will. [08:30] * Verterok is off to bed, g'night all [08:35] Peng_: i guess the breadcrumbs should key off SCRIPT_NAME somehow [08:36] mwhudson: Oh, hi. :) [08:37] mwhudson: They should do it the same way every other link does, cuz they get it right. [08:39] I came to the computer to do one thing, decided to read the mailing list and pull new changes out of boredom, and here I am an hour later. Oops. [08:41] OK, so how do I upgrade from branch7 to branch6? [08:41] "bzr upgrade" doesn't know how. Should I init/pull (I hate that hack). [08:41] ? [08:42] bzr upgrade --packs should do it i think [08:43] "bzr upgrade --rich-root-pack errored out with "No converter". [08:44] speakman: file a bug on bzr-svn in launchpad, jelmer is pretty good at fixing those sorts of things [09:12] Whew. Over 1 hour, 2355 bytes of IRC conversation, 1 bug and 1 long mailing list post later, I can get back to watching my depressing anime. Why did I decide to pull bzr.dev and get into all this? :( [09:12] (Also, why did I spend 10 minutes counting my IRC conversation?) [09:12] Anyway, good night everyone. [09:15] Peng_: good night :) [09:15] Peng_: thanks for the bug hunting! [10:20] Hmm : bug: bzr rocks does not respect "-q" argument [10:21] I'm looking for quiet optimism [10:21] :-P [10:37] hi [10:37] all of a sudden bzr seems unwilling to play with bzr-playground [10:37] the error message is "bzr: ERROR: exceptions.AttributeError: 'ProtocolThreeDecoder' object has no attribute '_in_buffer'" [10:38] Bazaar (bzr) 1.6.1, from the ppa [10:40] can i go after this problem somehow? [10:53] hi [10:53] bzr-svn has some problem today [10:53] bzr-svn/ra.c:919: undefined reference to `py_svn_log_entry_receiver' [10:53] what is it ? [10:54] robsta: ttry 1.7 perhaps, that looks likea local error, bt will tell you [10:54] visik7: no idea sorry, jelmer: may know [10:54] * lifeless waves bye [10:54] ok solved [10:55] sorry [10:55] lifeless: it may be related to the problem Jc2k just pinged you about, in #gnome-bzr [10:57] I've this error using latest svn-bzr and latest svn http://dpaste.com/77418/ [10:57] sorry [10:57] latest svn-bzr and latest bzr [10:58] visik7: That message is pretty clear, isn't it? [10:59] I've the latest version [10:59] visik7: The bzr-svn you have is not compatible with the bzr version you have. you're running development code. stick to bzr 1.6 [10:59] visik7: "the latest version" is 1.6.1 [10:59] not 1.8dev [10:59] does anyone have the address for canonicals rt? [11:00] uws: my bzr is bzr.dev http://bazaar-vcs.org/bzr/bzr.dev/ [11:01] Jc2k: #canonical-sysadmin should [11:01] *really* gone now, sorry [11:01] visik7: What's the problem? [11:02] uws: I dunno I think I was on the devel branch of both bzr and bzr-svn [11:02] visik7: perhaps bzr-svn lags behind a bit? [11:03] visik7: it's called "devel branch" for a reason, namely that it is NOT stable or 'guaranteed' to work [11:03] oh [11:03] I misunderstood the error [11:03] nevermind :P [11:03] visik7: ok === mvo__ is now known as mvo [12:00] vila, hi [12:00] poolie: hi ! [12:24] night! [12:27] I need register my RSA key fingerprint, where i do this? [12:27] i dont remeber [12:28] hersonls: Is this a Launchpad question? [12:28] yes [12:28] hersonls: There are instructions on the website, and you should ask in #launchpad anyway [12:29] sorry :] [12:30] hersonls: https://help.launchpad.net/YourAccount/ImportingYourPGPKey [12:35] Huh, if I branch an old knit branch over "http", with the bzr+http smart server available, it does most things over plain http and is very quick. If I explicitly use "bzr+http", it's extremely slow, makes a huge number of requests, and doesn't use plain http. [12:36] God, you guys *really* killed knits. [12:37] I'm vaguely tempted to see what happens if I access a weave branch over bzr+ssh... [12:37] Just out of sick, sick curiosity. [12:38] Hahaha. [12:41] Hey, it's done! It only took 7 minutes and made 1085 requests! That's not excessive, right? [12:42] Heck, that's not even 3 a second. What a yawner. [12:42] You know, for a 2 MB branch with about 200 revisions? [12:43] That's 5 per revision... a fifth of 2 megabytes is about 400k... who'd want to do more than 400k a request either? [12:44] (I realize the math may not SEEM right, but...) [12:45] fullermd: You're actually right. ...Wait, no you're not. The responses were 435 *bytes*, not 435 KB. [12:45] So, see how awesome bzr is? It's giving you 1000:1 compression! [12:46] Imagine how much slower it would be if it did more per request. [12:46] Say I file a bug, everyone ignores it for 4 months (ahem), and then when someone finally notices it, it's not reproducable anymore. How should it be resolved? Fixed or invalid? [12:47] Ideally, the third choice. [12:47] * fullermd drags his "dammit, I need to write a BTS" out of the closet. [12:50] It took precisely 128 days for someone to notice the bug. Nice coincidence. :) [12:52] I wonder what Bazaar's average bug response time is? [12:54] I'll bet the standard deviation is huge. === beuno_ is now known as beuno [13:51] Ranges from people who filed bugs so they have something to put a patch in, to bugs that were filed early on and never touched, I'll wager === beuno_ is now known as beuno === kiko-afk is now known as kiko [15:00] hoia [15:00] anyone knows if it's possible to export just a directory of a repo? [15:01] I have a directory in my git repo which I want to export and import to bzr [15:03] Can anyone help me with an error I get when trying to branch a branch from LP: Permission denied (publickey). [15:03] bzr: ERROR: Connection closed: please check connectivity and permissions (and try -Dhpss if further diagnosis is required) [15:04] I can branch (bzr branch lp:peekabot) from my desktop, but not from my laptop [15:04] and they use the same bzr version (1.3.1, Ubuntu 8.04) [15:06] gimaker: Are you using public-key authentication? [15:06] ericvw, I have my pubkey uploaded to LP, yes [15:07] but it never even asks for the passphrase on my private key [15:07] (it does on my desktop, though - where it works) [15:07] how are you branching from your laptop? [15:07] "bzr branch lp:peekabot trunk" [15:08] Sorry, i am a bit unfamiliar with lp:peekabot syntax; could you clarify that for me? [15:09] lp:peekabot is the same as lp:///~peekabot-devs/peekabot/trunk [15:09] e.g. it's the "main branch of development" [15:11] I don't `lp` is a URL identifier that bazaar supports [15:11] it's supported if you have the Launchpad plugin, which is bundled with bazaar [15:13] the only thing I can think of is maybe you have two different private keys going on for some reason. [15:13] ericvw: yeah, that was it... I just figured it out too [15:13] Uploaded my 2nd one and now it works ok! [15:13] gimaker: Sorry, I am a bit new to Bazaar, but I know public-key quite well :D [15:14] I still think it's lame that a valid key is needed to branch from a public branch, though :) [15:15] is the lp:blah syntax just for the launch pad plugin? [15:15] gimaker: It shouldn't be. [15:16] Odd_Bloke: What should be? That I needed a pubkey to branch? [15:16] ericvw: yes [15:17] gimaker: Thanks, I should read up on that! [15:17] A valid key shouldn't be needed to branch from a public branch. [15:17] Though I suspect that's a known bug once you've launchpad-login'd. [15:18] Odd_Bloke: exactly... [15:19] If you remove 'launchpad_username' from ~/.bazaar/bazaar.conf, it should no longer be needed. [15:20] Odd_Bloke: well, now that I uploaded a second pubkey it should be ok anyway :) [15:21] Though it's still being annonying and demand that I type my passphrase twice after spewing ut an annoying "Server is too old for streaming pull, reconnecting. (Upgrade the server to Bazaar 1.2 to avoid this)" message :) [15:21] gimaker: You should upgrade your client. [15:21] ...which is obviously wrong, seeing as LP runs 1.6rc3 :) [15:22] Or...I don't know. I think upgrading the client is the right solution. [15:22] Peng_: I prefer to stick with what's in Ubuntu [15:22] gimaker: What's in Ubuntu? [15:22] 1.3.1 [15:22] gimaker: Well, I'm 99% sure upgrading the client will fix that [15:23] Either way, it's no biggie and I should stop whining already [15:23] You can add the Bazaar repository into sources for apt-get to have it get the latest and greatest! [15:23] Yeah. See https://launchpad.net/~bzr/+archive if you want to do that. [15:24] ericvw: does that work with all plugins as well? I use bzrtools, bzr-svn and rebase on a regular basis [15:25] s/all plugins/all plugins available in stock ubuntu/ [15:25] gimaker: A couple plugins are available in the PPA, but not that many. [15:25] I believe bzrtools is [15:25] gimaker: I think it's just bzrtools and bzr-gtk now. bzr-svn used to be. [15:25] John uploads bzr-svn to PPA now as well [15:26] Ah. [15:26] That's good. :) [15:27] maybe when I have some more time on my hands (I'm leaving for the first field-test of our robot in half an hour... a bit stressed atm :) [15:32] jelmer: does using the new dpush mean I won't have rebase as soon as someone else does a (non-conflicting) commit on the SVN-repository? [15:33] gimaker, No, you will still have to rebase or pull [15:33] hey all [15:34] I need help configuring bzr-eclipse [15:34] * beuno pokes awilkins [15:35] jelmer: ok. bummer :) rebase everytime someone else commits it is then! [15:35] gimaker, That's not specific to bzr-svn though, you would have to do the same thing if you were using a native bzr branch that other people committed to as well [15:37] I need help configuring bzr-eclipse someone help me ? [15:38] I should put lp:~gmazzurco89/mastro/work in branch location ? [15:38] jelmer: hmm? surely you must jest. native bzr branches I can just pull/merge. [15:39] gimaker, there shouldn't be anything preventing you from pulling/merging in the current situation either [15:40] some one can help em ? [15:41] jelmer: merging was fine, but I couldn't push without rebasing - since I had local commits "in between" the two latest revisions in the SVN repos. I thought maybe there was some fancy new feature that automated that for me. [15:41] gimaker: You would have to rebase or merge again too if you were in a native bzr branch [15:43] jelmer: yeah, I'd have to merge (or rebase, but that hardly seems necessary). But for svn-branches rebase is the only option, right? [15:44] jam, friendly reminder about TWiB today. I've got alerts going everywhere to make sure I don't forget. [15:45] statik can you help me please ? [15:45] statik someone tell me you use eclipse [15:45] rockstar, Hi! [15:45] jelmer, hello [15:46] gimaker, No, merge should work too for bzr-svn but not if you use dpush [15:47] gimaker, well, it would work but it would do strange (though correct) things to your history [15:47] can some body help em please ??' [15:47] rockstar: were you looking into creating a mirror of the KDE svn repo? [15:47] Gioacchino, sorry, none of the bzr-eclipse folks appear to be around [15:48] Gioacchino, Verterok is the person you'd want to talk to [15:48] ok [15:49] jelmer: really? What I did was: branch from svn, local commit, local commit, someone else commits to svn, local commit, bzr push. bzr push failed saying the branches had diverged, so I merged from the SVN-repo and then push failed with some error message about "changing the order of commits already in the SVN repository" [15:49] jelmer, I was, but we put it off because it was looking like it would be a while before they started the process of choosing a new VCS. [15:49] It also suggested rebase to solve the problem [15:49] gimaker: Ah, you're committing directly to the repository root? [15:50] jelmer: yeah. does that make a difference? [15:50] gimaker, Yep, that means you can not change the order of revisions on the mainline [15:50] gimaker, and if you "bzr merge" and then push that means the mainline changes [15:50] jelmer: which makes sense :) [15:50] gimaker, since some revisions from upstream that you merged will disappear from mainline [15:50] rockstar, Ah, ok [15:51] rockstar, bzr-svn now supports branching KDE branches pretty quickly fwiw [15:51] jelmer, I think we could probably set it up easily if we had a box. [15:51] jelmer, I saw that actually. [15:52] jelmer: gotta run, but thanks for the help [15:52] rockstar, some of the Kubuntu folks were asking about mirrors earlier so I think there's some interest in it [15:52] gimaker, you're welcome [15:52] jelmer, well, then let's find a box. [16:13] hello [16:14] Hi! Does bzr join --reference actually works somewhere? [16:14] is there a way to "export" some local commits, as in diff+commit log? [16:14] (like git am does) [16:14] * pinotree is not a git fan [16:15] pinotree: What do you want to do with said exported commits? [16:16] emailing them to another bzr user [16:16] pinotree: 'bzr send'. [16:17] i saw that; i was wondering if there was a way to just get the "result", instead of being sent directly [16:18] pinotree, "bzr send -o " [16:19] d'oh, i misread the documentation... you're right, jelmer, thanks [16:19] i understood like not specifying -o would give the result to stdout, stupid me [16:19] * pinotree headdesks [16:23] Anyone is using bzr join --reference and can confirm it works? [16:29] hmm but bzr send does not include the commit log, does it? [16:30] pinotree, it does [16:31] oh? [16:31] Pieter, it includes all revision metadata [16:31] s/pieter/pinotree/ [16:31] hah! [16:31] Pieter, sorry! [16:31] :) [16:31] ree: It does work, but is experimental [16:31] jelmer: is it the bundle? [16:32] pinotree, It's the base64-encoded data at the bottom of the genreated file [16:32] oh i see [16:32] * pinotree is a bzr noob === mw|out is now known as mw [17:02] quickie -- how do I upgrade a branch with subtrees? 1.6.1 doesn't know the old format, 1.5 doesn't know the new format [17:03] jelmer: another question.. if i ask for a diff of a revno range (eg revno:x..revno:x+4), does the bundle include the commit logs for all of the commits? [17:03] pinotree, yes [17:04] or is there a way to discard the information that the branch has subtrees? I don't mind losing that info, the sub-branch only has one revision which I can replicate [17:04] lalo: 1.6.1 doesn't k now the old format? === BZ|nortune is now known as jfroy [17:05] bzr: ERROR: Unknown repository format: 'Bazaar development format 0 with subtree support (needs bzr.dev from before 1.3)\n' [17:06] lalo: Ah, a development format... I guess you could upgrade to "pack-0.92-subtree" with bzr 1.5 [17:06] or maybe there's another format that supports subtrees and that's what I'm missing... but I think I tried all formats that 1.5 supports [17:07] aha, succeeds [17:07] yeah and 1.6 can read it :-D awesome, thanks [17:07] guess I assumed 0.92 had to be older than development? [17:07] yes, it is older [17:08] you'd never want to use development unless you're interested in hacking on bzr [17:08] and losing data once in a while [17:09] so pack-0.92-subtree is the current "supported" format with subtrees? [17:10] Gioacchino: hi [17:14] lalo, yep [17:15]