2009/01/14/#bzr.txt

[00:01] <Jc2k> jelmer: its not without its problems - it can only handle revisions that came from git as it stands for example.
[00:02] <Jc2k> anyway, i think im going to sleep at this point :]
=== sdboyer_ is now known as sdboyer
[00:33] <jml> :( :( :( :(
[00:33] <jml> I hit Ctrl-C during an up-thread --auto and now everything is screwed :(
[00:35] <jml> switching down to trunk and doing up-thread manually all the way to the top seems to work ok.
[00:35] <jml> (i.e. fix the problem of pending merges without working tree changes)
[00:36] <jml> I hope I haven't actually screwed up the loom though
[00:36] <lifeless> jml: interesting
[00:36] <lifeless> jml: up-thread --auto probably wnats a KeyBoardInterrupt catch-and-rollback
[00:36] <jml> it all started when I accidentally hit "bzr up-thread --auto" when I had uncommitted changes
[00:36] <jml> and so hit C-c
[00:38] <jml> hmm. bzr di -r branch:../trunk/ looks about right.
[00:38] <lifeless> jml: bottom: might be easier :)
[00:39] <jml> lifeless: but less reliable, given that the loom itself is now suspect.
[00:40] <lifeless> jml: current-thread writes are atomic, and up-thread doesn't modify the bottom thread, so I don't see bottom: being faulty
=== rocky1 is now known as rocky
[00:47] <jelmer> rocky, hi
[00:47] <jelmer> rocky, any chance you can confirm that bug in bzr-svn you were hitting is fixed now?
[00:49] <rocky> ohh...
[00:49] <rocky> unfortunately i'm away from my workstation atm, but i'll certainly try it as soon as i can
[01:02] <lifeless> jam: still around?
=== joshuabl1unt is now known as jblount
[02:23] <igc> hi all
[02:28] <thumper> igc: hi
[02:28] <thumper> igc: are you up for a quick skype call?
[02:28] <igc> thumper: sure
[02:45] <igc> thumper: http://arstechnica.com/news.ars/post/20090107-dvcs-adoption-is-soaring-among-open-source-projects.html
[02:53] <lifeless> I need to pop out for a minute to the chemist
[02:53] <lifeless> brb
[02:56] <thumper> Tree transform is malformed [('versioning no contents', 'new-4')]???
[02:56] <thumper> what does that mean?
[03:12] <emmajane> hi all!
[03:12] <emmajane> I'm trying to understand using launchpad for merging branches.
[03:12] <poolie> thumper: it's either a bug in bzr, or in code that's calling in to bzrlib
[03:12] <emmajane> Should there be a big "MERGE" button that I'm looking for?
[03:13] <thumper> poolie: ta
[03:13] <thumper> emmajane: launchpad doesn't merge branches for you yet
[03:13] <thumper> emmajane: we have some kinda future plans, but it just isn't there yet
[03:13] <emmajane> thumper, ah! probably why I can't find a button. :)
[03:13] <thumper> emmajane: exactly
[03:14] <emmajane> thumper, I'm glad to know I'm just a futurist instead of plain ol' daft. ;)
[03:14] <thumper> heh
[03:15] <thumper> emmajane: lets just say I have a loom with about 8 threads dealing with this topic
[03:15] <thumper> that I haven't had time to get to
[03:15] <emmajane> awww.
[03:15] <thumper> ('cause I'm a manager now)
[03:15] <emmajane> So I guess I shouldn't wait for the button to appear tonight? ;)
[03:15] <thumper> and I don't get as much time to code as I'd like
[03:15] <emmajane> (congrats on your promotion)
[03:15] <thumper> emmajane: sorry, no
[03:16] <thumper> emmajane: promotion was quite some time ago
[03:16] <thumper> but thanks
[03:16] <emmajane> thumper, heh. so you're only just coming to grips with never being able to code again. ;)
[03:16] <thumper> well, I hope not never
[03:16] <thumper> just not as often as I'd like
[03:17]  * emmajane nods
[03:17] <emmajane> so to merge I need to pull down the branch I want to merge into; merge; and then push back up?
[03:17]  * emmajane has never done this before.
[03:17] <thumper> emmajane: can you give me a concrete example?
[03:18] <emmajane> https://code.edge.launchpad.net/~emmajane/ubuntu-desktop-course/udc-804/+merge/2799
[03:18] <emmajane> that's sort of concrete, eh? :)
[03:18]  * thumper looks
[03:18] <thumper> right
[03:18] <emmajane> I'm very happy to RTFM if there's anything specific for launchpad.
[03:19] <emmajane> -beta needs to go into main.
[03:19] <poolie> lifeless: can we catch up before you finish today, maybe at 4?
[03:19] <thumper> emmajane: ok, so you are a member of the team that owns the target branch, so that means you can do it
[03:20] <thumper> emmajane: did you want to move this to #launchpad?
[03:20] <emmajane> thumper, can do. :)
[03:24] <lifeless> poolie: shortly before owould be fine
[03:24] <lifeless> and migod its hot out there
=== Mario__ is now known as pygi
[03:26] <poolie> isn't it just
[03:32] <lifeless> anyone know of stats modules in the stdlib ?
[03:33] <lifeless> e.g. to get stddev, IQR etc
[03:41] <lifeless> can someone look at bzrlib.check.Check._check_one_revision
[03:41] <poolie> thumper: hi
[03:41] <poolie> lifeless: i'm pretty sure there is an SD function
[03:41] <poolie> in math?
[03:41] <thumper> poolie: hi, just helping emmajane on #launchpad
[03:42] <poolie> thumper: whenever you like
[03:42] <poolie> lifeless: in scipy according to google
[03:42] <poolie> it's not in math
[03:43] <lifeless> yeah, I knew scipy would have everything I'd need
[03:50] <lifeless> but its not stdlib :(
[03:52] <poolie> copy & paste?
[03:52] <poolie> lifeless: what about that function?
[03:52] <poolie> check_one
[03:53] <lifeless> poolie: well several things
[03:53] <lifeless> it calls check revision tree
[03:53] <lifeless> which means we're extracting the inventory for every revision 3 times I think, maybe more
[03:54] <lifeless> once there, once to generate the text key references, and once in check_weaves
[03:55] <lifeless> check_revision_tree seems to check that the fileid iteration of the inventory only yields each id once; which seems rather redundant to me - its checking using too high an API pehaps
[03:58] <lifeless> and then InventoryFile._check seems to double-check the sha1, which means we're extracting every file text twice (or more)
[03:58] <thumper> poolie: call?
[03:58] <lifeless> so I'm saying it seems like check can be halved in time without huge effort
[04:10] <jml> how hard would it be to add a debug option to bzr that shows bytes transferred? is there one already?
[04:10] <jml> (or can I trick linux into doing this for me somehow?)
[04:10] <lifeless> jml: -Dtransport possibly, also see vila's transport debugging plugin
[04:12] <jml> lifeless: thanks
[04:12] <bob2> ethereal could, too
[04:13] <lifeless> bob2: ELOWTECH
[04:13] <bob2> hehe
[04:17] <poolie> lifeless: yes that's all true
[04:17] <poolie> about check
[04:17] <lifeless> poolie: thanks, useful confirmation
[04:18] <lifeless> you want that call now?
[04:18] <lifeless> poolie: ^
[04:19] <poolie> lifeless: talking to thumper at the moment but straight after that would be good
[04:19] <lifeless> ok
[04:19] <lifeless> I want to finish sharp at 4
[04:21] <poolie> k
[04:54]  * emmajane chuckles at poolie. I assure you it's mostly photos of knitting and looms. 
[04:54] <poolie> i was seriously impressed by the looms
[04:54] <emmajane> Thanks. :)
[04:55]  * emmajane is pretty hardcore into the fibre arts.
[04:55] <emmajane> That's only because I'm a recovering bookbinder though.
[05:04] <fullermd> Aren't photos of knits deprecated?   :p
[05:09]  * emmajane chuckles.
[05:14] <poolie> emmajane: what was it that made you chuckle anyhow?
[05:15] <emmajane> poolie, knitting and looms and bzr. It amuses me more than it should.
[05:16] <emmajane> poolie, a friend of mine also runs a craft show called http://www.bazaarbizarre.org/cleveland.html
=== sdboyer_ is now known as sdboyer
[05:58] <emmajane> Alright. On that happy note. I'm going to give up on the idea of eating supper (it's 1AM) and trundle off to sleep. http://emmajane.net/node/884 <-- thanks for the help (although it happened over yonder, it all started here).
[07:08] <vila> hi all
[07:09] <Peng_> Good morning. :)
[07:54] <poolie> hello vila, Peng
[07:54] <poolie> sleepy
[08:44] <igc> night
=== thekorn_ is now known as thekorn
[11:02] <LarstiQ> siretart: heya! In bug 317001 you say an unwriteable dir to watch cause bzr-hookless-email to traceback, I haven't yet managed to reproduce that (then again, I'm still sleepy)
[11:02] <ubottu> Launchpad bug 317001 in bzr-hookless-email "ugly traceback when directory to watch is not writeable" [Undecided,New] https://launchpad.net/bugs/317001
[11:06] <siretart> LarstiQ: yes. testcase: chown -R the branch to root:root and try as user
[11:07] <siretart> silly use case, I know, but we have system configuration managed in a bzr branch, and wondered if I can setup the monitoring (bzr-hookless-mail) as non-priviledged user
[11:07] <siretart> LarstiQ: btw, did you query me before?
[11:08] <LarstiQ> siretart: not in a looong time
[11:08] <siretart> ok. then it was someone else :)
[11:09] <LarstiQ> ah, there needs to be a branch in place *doh*
[11:09] <siretart> yes. I assume the plugin doesn't work else anyways..
[11:10] <LarstiQ> siretart: it does, it notices branches that get created after it starts watching
[11:10] <LarstiQ> (not branches that get mv'ed in the hierarchy, but I've almost fixed that)
[11:10] <LarstiQ> siretart: and of course it needs to open a branch to trigger that traceback, I was just being stupid
[11:12] <LarstiQ> siretart: I'll push your changes up in a sec, thanks for the patch!
[11:13] <siretart> you're welcome!
[14:15] <vila> guilhembi: ping
=== montabeau is now known as abeaumont
[16:30] <ericvw> How do I have a branch un-ignore a file extension is ignored globally?
[16:30] <ericvw> that is*
[16:31] <jelmer> ericvw: I don't think there's a way to do that, but you can explicitly override the ignore by "bzr add <filename>"
[16:32] <LarstiQ> it will version the file of course
[16:32] <ericvw> jelmer: Okay, I will do that for now.  Thanks!
=== mvo_ is now known as mvo
=== asac_ is now known as asac
[18:11] <Kobaz> how come sometimes i get: These branches have diverged.  Try using "merge" and then "push".
[18:11] <Kobaz> and sometimes i don't
[18:11] <Kobaz> sometimes it will merge for me, and it's auto
[18:11] <Kobaz> here's an example
[18:11] <fullermd> It will never merge for you.
[18:12] <fullermd> The snarky answer is of course "because sometimes they're diverged, and sometimes they haven't"   :p
[18:12] <Kobaz> files 1,2,3 exist in the repo, user A makes changes to file 1 and does a push, user B makes a change to file 2 and does a push
[18:12] <Kobaz> and bzr will complain branches have diverged
[18:12] <Kobaz> so now i have to do a merge
[18:12] <Kobaz> even though nothing is in conflict
[18:12] <fullermd> It's a question of what revisions are where.
[18:13] <fullermd> If all the revisions on the far side are in your local history, they're not diverged, and push can Just Run.
[18:13] <Kobaz> and then other times, person A will modify file 1, and person B will modify file 2, and then a pull is down, and the files are brought down and merged in
[18:13] <fullermd> If there are revisions there that you don't have, though, you have divergeance.
[18:13] <Kobaz> mmm
[18:13] <Kobaz> so it has nothing to do with conflicts then
[18:13] <LarstiQ> Kobaz: correct
[18:14] <fullermd> Yah.  Push doesn't do merges, or create new revisions; it just moved around revs that are already created.
[18:14] <LarstiQ> Kobaz: the divergence is about wether both branches have different revisions from a certain point
[18:14] <LarstiQ> Kobaz: do you know the `bzr missing` command?
[18:15] <Kobaz> yeah
[18:16] <Kobaz> so if there are missing revs, then you need a merge?
[18:16] <LarstiQ> sorry, phone call interrupted
[18:16] <LarstiQ> Kobaz: no
[18:17] <LarstiQ> Kobaz: if missing reports extra revisions for one side only, yours, or theirs, then you can pull/push and do not need a merge.
[18:17] <LarstiQ> Kobaz: but if missing shows extra revisions for _two_ sides, that is when divergence has occurred and you would need a merge
[18:17] <fullermd> If the other side has revs you don't, you're out of date and can pull.  If you have revs the other side doesn't, then it's out of date and you can push.
[18:18] <fullermd> If you both have revs the other doesn't, then you have divergeance, and have to merge them.
[18:18]  * LarstiQ nods
[18:18] <fullermd> (that's a rather simplified way of looking at it, but it works)
[18:18] <LarstiQ> Kobaz: does that make sense?
[18:19] <Kobaz> sec
[18:19] <LarstiQ> lifeless: oh oh, I got an Acer Aspire One, so now I have a laptop with working wireless ;)
[18:22] <Kobaz> okay, i see
=== thekorn_ is now known as thekorn
[18:38] <beuno> jam, second day using yout log alias, and it's 100 times more comfortable to use. Speed and presentation-wise
=== lamont` is now known as lamont
=== andreas__ is now known as ahasenack
[19:27] <maco> hi um, bzr just told me that a file i have on launchpad.net has been locked for 900+ hours, and the error said to use " bzr break-lock lp-46717904:///~maco.m/5-a-day-data/main/.bzr/branch/lock
[19:28] <maco> but when i do that, bzr then tells me that it's an unsupported protocol
[19:28] <maco> why's it telling me to do something it can't do?
[19:28] <jelmer> maco, try running bzr break-lock on the branch location
[19:28] <jelmer> maco, that's a bug in the launchpad plugin
[19:29] <maco> so remove the -##### stuff so it just says lp: like it normally does?
[19:29] <jam> beuno: yeah, I like it a lot, too
[19:30] <jam> a *long* time ago I proposed it as the default for "bzr log", but I think at that time we decided to be compatible with other systems
[19:30] <jam> maco: yeah
[19:30] <jelmer> maco, yeah
[19:30] <maco> ok, thanks
[19:30] <jam> bzr break-lock lp:~maco.m/5-a-day-data/main
=== nevans1 is now known as nevans
[20:00] <Lo-lan-do> jelmer: A thought occurred to me while I was eating my lasagna tonight.
[20:01] <Lo-lan-do> The bzr-svn logs show that there are lots of "get-dir" requests going back and forth to the SVN server, but they all seem to concern past revisions.
[20:01] <Lo-lan-do> Shouldn't their results be cached?  Surely that data is not expected to change over time, is it?
=== fta_ is now known as fta
[20:23] <jelmer> Lo-lan-do: Those results specifically are not cached but some of the data that is inferred from them are
[20:27] <guilhembi_> vila: ping
=== kiko is now known as kiko-afk
[20:28] <dereine> hi is it possible to follow symlinks?
[20:30] <Lo-lan-do> jelmer: So... why not cache the rest and do without the round-trips?  Or am I talking complete nonsense?
[20:30] <jelmer> Lo-lan-do: Too much caching takes up too much disk space
[20:30] <jelmer> Lo-lan-do: Also, I'm not sure why it's looking at those older revisions at all
[20:35] <Lo-lan-do> Well, I'd be willing to sacrifice some more disk space if it means a commit to SVN takes significantly less than half an hour.
[20:37] <jelmer> Lo-lan-do, let's figure out first why it's looking at those older revisions
[20:37] <jelmer> also, a single get-dir call isn't supposed to be as slow as it appears to be for you
[20:37] <Lo-lan-do> Sounds like a plan.  How can I help?
[20:38] <jelmer> should just be a single round-trip with about a kb of data
[20:38] <Lo-lan-do> I guess the remote server is slow...
[20:38] <dereine> anyone?
[20:38] <LarstiQ> dereine: your question doesn't make sense to me as-is, could you elaborate?
[20:39] <Lo-lan-do> But even if it weren't, there's a scalability problem: the number of requests is O(number of revisions committed through bzr-svn)
[20:39] <fullermd> If they catch you, they might call the cops...
[20:39] <dereine> i have a repo called config
[20:39] <dereine> where i link all my config files
[20:39] <dereine> but bzr only diffs the links itself and not the file behind it
[20:40] <Lo-lan-do> dereine: Store the files under bzr and do the symlinks the other way round?
[20:40] <dereine> no other way?
[20:41] <jelmer> Lo-lan-do, It shouldn't be of that order though
[20:42] <LarstiQ> dereine: no other way
[20:42] <dereine> ok thx! btw bzr is awesome!
[20:42] <Lo-lan-do> Hardlinks maybe.
[20:43] <LarstiQ> Lo-lan-do: I doubt they won't be broken by bzr though.
[20:43] <Lo-lan-do> LarstiQ: If you just use bzr as a backup mechanism and only do the restores by hand, myabe you can afford that.
[20:44] <LarstiQ> Lo-lan-do: possibly
[20:45] <LarstiQ> dereine: how are you using bzr that this becomes an issue?
[20:45] <dereine> i have ~/.config
[20:46] <dereine> no
[20:46] <dereine> ~/config, there i would like to collect all config files for example ~/.bashrc
[20:46] <dereine> and ~/.vimrc ...
[20:46] <dereine> but i don't want to have my home folder as repo
[20:47] <lifeless> jelmer: git pack delta compression
[20:49] <LarstiQ> dereine: ah, right
[20:49] <LarstiQ> dereine: I do that with a ~/dotfiles branch, and then I symlink ~/.zshrc to ~/dotfiles/.zshrc etc
[20:50] <dereine> its still ok
[21:34] <dereine> what is the difference between init-repo and init?
[21:35] <Lo-lan-do> One initialises a repository, the other initialises a branch.
[21:35] <dereine> mh i did not used init-repo
[21:37] <Lo-lan-do> That's not strictly necessary.
[21:37] <Lo-lan-do> A repo is just a way of storing data that saves disk space when several branches share some revisions.
[21:39] <dereine> for my config i only need one branch
[21:39]  * dereine still has to learn
[21:39] <Lo-lan-do> Then no repo is needed.
[21:39] <dereine> so i pushed my current branch to a webspace
[21:39] <dereine> removed my local one
[21:40] <dereine> bzr branch the webspace one
[21:40] <dereine> so now i change a file locally
[21:40] <dereine> how can i get them to the server?, so how can i commit on the server
[21:41] <Lo-lan-do> Either you commit locally then push, or you bind your local branch to the remote one and every commit you do locally will automatically be pushed.
[21:41] <dereine> what happens if i have no internet connection if i bind?
[21:42] <Lo-lan-do> Then you can do bzr commit --local, and push only when you get back on the net.
[21:42] <dereine> ah nice
[21:42] <Lo-lan-do> Or bzr unbind, work, commit, bzr push, bzr bind
[21:42] <dereine> wow
[21:43] <dereine> thats much better than any cvs stuff
[21:43] <Lo-lan-do> You know, I think that kinda was the point :-)
[21:43] <Lo-lan-do> Note that a bound branch is also known as a "checkout".
[21:44] <Lo-lan-do> So when you do "bzr checkout $remotebranch", it behaves the same as a CVS or SVN checkout.  Except you can do diff and log and annotate and whatnot even when you're not on the net.
[21:45] <dereine> the idea of working locally is just much better!
[21:46] <dereine> can you explain what https://launchpad.net/bzr-push-and-update does exactly?
[21:47] <Lo-lan-do> Yeah.
[21:47] <Lo-lan-do> When you're in a branch, you've got your files, and your .bzr dir.
[21:48] <Lo-lan-do> That .bzr dir contains the history of the revisions so far.
[21:48] <dereine> exact
[21:48] <dereine> yes?
[21:48] <Lo-lan-do> When you commit or log or diff, the command operates on that .bzr dir.
[21:49] <Lo-lan-do> When you push to a branch, bzr mostly updates the stored revisions, ie the .bzr dir of that branch.
[21:49] <Lo-lan-do> The actual (plaintext) files need to be updated separately.
[21:50] <Lo-lan-do> If the branch is local, then they are updated automatically, but if the branch is remote then they're not.
[21:50] <dereine> they are only updated if someone merges them from the repo?
[21:50] <Lo-lan-do> Yup, or if the branch is local.
[21:51] <dereine> a personal question, do you have your whole homefolder in a repo?
[21:51] <Lo-lan-do> That plugin does the update for remote branches accessible through ssh.
[21:52] <dereine> nice
[21:52] <Lo-lan-do> No.  I have my ~/bin in a repo, and most of my ~/debian/* stuff, but I not the whole home dir.
[21:53] <dereine> just wonders. because i wait for 5 minutes for a push a branch with files(not .bzr) of one mb
[22:02] <igc> jam: w.r.t. log --short FILE not working ...
[22:03] <igc> I think we need to always include_merges inside calculate_view_revisions if there's a fileid given
[22:03] <igc> sound right?
[22:04] <igc> that should give us the correct projection onto the mainline
[22:09] <jelmer> 'morning Ian
[22:11] <dereine> how can i save the repo , so that i only have to write bzr push?
[22:12] <Lo-lan-do> bzr push --remember $remotelocation
[22:12] <dereine> wow incredible
[22:12] <Lo-lan-do> Although I think it remembers automatically the first time you push
[22:12] <LarstiQ> it does
[22:13] <jelmer> hmm
[22:13] <jelmer> *somebody* should fix progress indication
[22:14] <Lo-lan-do> ...or make stuff so fast that it's unneeded :-)
[22:14]  * LarstiQ quickly goes to sleep
[22:32] <jelmer> poolie, thanks for sending the standup notes again
[22:32] <mwhudson> beuno: apropos of not much, the directory listing for serve-branches should probably paginated
[22:32] <mwhudson> -d
[22:33] <fullermd> Uh oh.
[22:33] <fullermd> "mbp: several calls; today will bzrtools into ppa"
[22:33] <Haffi___> Hi, I've pushed a few python files onto a ssh server I'm running, and me and a few others will be working on these files on separate machines. I've read the user guide but I'm not quite I understand fully the difference between using branch and merge or checkout and update
[22:33] <fullermd> He ran out of verbs already   :(
[22:34] <fullermd> Haffi___: Checkout gives you a [n additional] working tree on a branch.  Branch gives you a new independent branch.
[22:34] <jml> "There should be a newer version of Bzrtools available, e.g. 1.12."
[22:34] <jml> abentley: is this true?
[22:34] <fullermd> Haffi___: Update is how you bring a working tree up to date with its branch.  Merge is how you integrate changes from 2 branches together.
[22:35] <Haffi___> fullermd: So if we're trying to keep things centralized, then we should use checkout and update?
[22:35] <fullermd> (also, rain causes rainbows, and babies come from good home-cookin')
[22:36] <fullermd> Haffi___: That way you'd have everybody working in lockstep on one branch (CVS/SVN style).
[22:36] <fullermd> Now, that doesn't stop people from making their OWN branches and working in them locally, then later merging them into the checkout of trunk.
[22:38] <abentley> jml: No, it's a little early for 1.12.
[22:38] <jml> hmm.
[22:38] <abentley> bzrtools 1.11 won't emit that for a dev version of 1.12.
[22:39] <Haffi___> But regarding concurrency, is it as safe? If I checkout the "latest" branch and work on a file, but in the meantime someone else has made changes to a file and pushed it to the branch when I send my changes in, does it matter shich method I use?
[22:39] <jml> abentley: I somehow have 1.10...
[22:39] <jml> I wonder how that got there
[22:39] <fullermd> Haffi___: If you try to commit in a checkout and it's out of date, it won't let you; you'll have to 'update' first.
[22:40] <jml> ahh ok. running from a branch.
[22:40]  * jml pulls to get the happiness
[22:40] <abentley> jml: So bzrtools 1.11 will work with it.
[22:40] <jml> abentley: yeah, that works. thanks.
[22:41] <abentley> jml: np
[22:41] <fullermd> Hm.  I think it complained for me after bzr.dev changed...
[22:41] <fullermd> I had to pull it before I could multi-pull my plugins.
[22:42] <poolie> jelmer: oh, thanks for saying so
[22:42] <poolie> glad you liked them
[22:42] <Haffi___> I lost the connection for a bit there...
[22:42]  * fullermd likes them too.
[22:42] <abentley> fullermd: What version were you on when you did that?
[22:43] <fullermd> A rev or two back.  Last pulled in Dec sometime.
[22:43] <fullermd> r688 probably.
[22:44] <abentley> fullermd: Well, the version number would be 1.11 then, and that was compatible with 1.12dev
[22:45] <fullermd> Hm.  Well, I can't reproduce it.
[22:45] <Haffi___> Are the IRC logs kept public somewhere?
[22:47] <fullermd> Oh well.  I'll worry about it next time it happens, when I've forgotten about it   ;)
[22:48] <fullermd> jam used to have them somewhere.  Dunno if he still does.
[22:48] <fullermd> Only thing I said after your last was
[22:48] <fullermd> Haffi___: If you try to commit in a checkout and it's out of date, it won't let you; you'll have to 'update' first.
[22:49] <Haffi___> and update is just merging your working tree with the parent branch?
[22:49] <fullermd> Pretty much, yah.
[22:49] <jam> fullermd, Haffi___: If you look in the topic, you can see: http://irclogs.ubuntu.com/
[22:49] <jam> http://irclogs.ubuntu.com/2009/01/14/%23bzr.html
[22:49] <Haffi___> right, thanks... :)
[22:50] <fullermd> Topic?  Well, shoot, why hide the info where nobody will ever look?   :p
[22:50] <jam> That only seems to update every-hour or so
[22:51] <Haffi___> I try to look at documentation and such before asking stupid questions, but sometimes you forget looking at the most obvious places
[23:11]  * ToyKeeper tries to remember how to explicitly set branches URLs for :parent and :submit
[23:11] <ToyKeeper> s/branches/branch/
[23:16] <NfNitLoop> toytoy: --remember
[23:16] <NfNitLoop> er, ToyKeeper
[23:17] <ToyKeeper> Some commands have a --remember option, but the option name and the branch label don't match and the commands I want to use don't have --remember.
[23:18] <fullermd> Parent would be pull, and submit...   mmm...   merge, I think?
[23:18] <NfNitLoop> yep.
[23:18] <NfNitLoop> Yeah, I've been confused by that before too.
[23:18] <NfNitLoop> why aren't they just called the "pull branch" and the "merge branch".
[23:19] <ToyKeeper> I'm still used to the way hg handles branch URLs...  it'll use 'default-CMD' for the 'CMD' command, if it exists, or fall back to 'default' otherwise.  It's simple and intuitive.
[23:20] <ToyKeeper> To set one, edit .hg/hgrc
[23:21] <ToyKeeper> Ah, found it.  .bzr/branch/branch.conf ; '%s_location = URL'
[23:22] <ToyKeeper> I guess it doesn't allow arbitrary labels though, and 'submit_location' isn't the variable for the :submit branch.
[23:24] <ToyKeeper> Odd.  :parent uses 'parent_location = ../trunk/' but :submit uses 'submit_branch = file:///full/path/to/trunk/'
[23:26] <NfNitLoop> as you said, it's not meant for arbitrary aliases. :)
[23:26] <ToyKeeper> If I have both 'submit_branch' and 'submit_location' set, bzr dies on commands like diff, even though 'submit_location' doesn't actually seem to get used for anything.
[23:27] <NfNitLoop> so don't set submit_location?  :)
[23:28] <ToyKeeper> Well, yeah.  It's just odd that it would be ignored when it's alone (since it's the wrong name), but cause a collision when the correct name is set.
[23:28] <ToyKeeper> I resolved the original issue I was having, and now am just looking to see what's fragile or internally inconsistent.
[23:32] <lifeless> jelmer: around?
[23:32] <jelmer> lifeless, somewhat
[23:33] <jelmer> lifeless, what's up?
[23:33] <lifeless> pack delta compression - how did you implement that
[23:33] <lifeless> its xdelta right?
[23:34] <jelmer> I'm not sure it's xdelta completely, but it sure did look like it
[23:35] <jelmer> it's apply_delta() in dulwich/pack.py in dulwich fwiw
[23:35] <lifeless> how fast is your implementation? does it need C bindings to libxdelta? where is it?
[23:35] <jelmer> no, it's implemented in Python
[23:35] <jelmer> lp:dulwich
[23:35] <jelmer> dulwich/pack.py
[23:35] <jelmer> the function is called apply_delta()
[23:36] <lifeless> did you write a compressor?
[23:36] <jelmer> there's a create_delta() as well, but I didn't write that - Jc2k did
[23:36] <lifeless> AIUI xdelta has a turing complete [or nearly] component
[23:36] <lifeless> is that used?
[23:36] <poolie> lifeless: i really don't think it's turing complete
[23:37] <poolie> imbw
[23:37] <poolie> but i don't think it can switch based on the content
[23:37] <poolie> written out by the delta
[23:37] <lifeless> poolie: I have no idea, haven't read the specs, just going on memorys of jams comments
[23:37] <poolie> i guess it would be turing complete if you ran xdelta repeatedly on its own output
[23:37] <poolie> but that would be weird
[23:38] <jelmer> lifeless, I don't think that's used
[23:40] <lifeless> jelmer: thanks
[23:41] <jelmer> lifeless, but speed is an issue with the current in-python implementation
[23:42] <jelmer> I'm looking at ways to improve it at the moment
[23:42] <lifeless> jelmer: I'm putting together a compressbench tool
[23:42] <lifeless> jelmer: it needs a VersionedFile interfface
[23:43] <jelmer> it's ok for small repositories (loudmouth, ~500 revs, takes a few minutes)
[23:43] <lifeless> or rather a subset of it
[23:43] <jelmer> but for e.g. Samba just figuring out what objects to fetch takes a loooong time
[23:43] <lifeless> is it byte orientated?
[23:44] <jelmer> lifeless, is what?
[23:44] <lifeless> and do you string join?
[23:44] <lifeless> the deltas
[23:44] <jelmer> lifeless, the git deltas are byte-based, yes
[23:44] <lifeless> do they work in bits bytes lines
[23:44] <jelmer> bytes
[23:44] <lifeless> do you string join in your decompressor?
[23:45] <jelmer> string concatenate, yes
[23:45] <lifeless> do you know the length of the output when you start decompression?
[23:47] <jelmer> lifeless, sorry, the delta-applyer does string concatenate
[23:47] <jelmer> the decompressor is a simple zlib decompresser
[23:47] <jelmer> and the output length is not known beforehand
[23:47] <lifeless> jelmer: well, I meant the delta applier
[23:47] <lifeless> which is a form of decompression :P
[23:48] <jelmer> lifeless, sure, but it makes the terminology a bit confusing
[23:48] <lifeless> well
[23:48] <jelmer> as all objects (whether they're deltas or plaintexts) are stored zlib-compressed
[23:48] <jelmer> in the packs
[23:48] <lifeless> k, well ignore the zlib step for this discussion
[23:49] <poolie> the length is still not known
[23:49] <poolie> it's an instruction stream
[23:50] <lifeless> poolie: it may be wrapped
[23:50] <poolie> i guess you *could* run over it once as a dummy to work out the eventual length
[23:50] <poolie> if you mean you could have a statement of the eventual length
[23:50] <lifeless> poolie: and as jelmer has been coding this I'm asking him rather than digging up the pack spec to check
[23:50] <poolie> sure
[23:51] <lifeless> jelmer: so, do you know the output length of the object?
[23:51] <jelmer> lifeless, so fwiw, the delta unpack algorithm does not use the delta length
[23:51] <jelmer> lifeless, in dulwich' case we do know the delta length since we always do a complete decompress before applying a delta
[23:52] <lifeless> jelmer: Its not the delta length; what I was getting at was that if you know the objec tlength you could mmap a region of the right size and decompress into place
[23:52] <damijit> Hello, I am wondering if it is save to move the top level directory for a bzr project (i.e., the  one that contains the .bzr directory). Will this cause any problems?
[23:52] <damijit> *safe
[23:55] <jelmer> lifeless, ah, sorry
[23:55] <jelmer> lifeless, the result size *is* known beforehand
[23:55] <jelmer> it's one of the two variable-size headers of the delta
[23:57] <RAOF> damijit: Yes, it's safe.
[23:58] <RAOF> damijit: As long as the contents of that directory stay the same, bzr is (almost) entirely oblivious to where it is.
[23:58] <damijit> RAOF: Thanks, that's good to  know
[23:59] <jelmer> lifeless, we don't use the result size, just for verification purposes