[00:04] <lifeless> vila: TestCompare is a level higher than TestIterChanges
[00:05] <lifeless> look at TestIterChanges
[00:10] <vila> lifeless, Yup, I'm on IterChanges, does test_file_rename suits you ?
[00:10] <lifeless> ok
[00:13] <lifeless> jml: ping
[00:13] <jml> lifeless: pong.
[00:14] <lifeless> is launchpad-bazaar 'just the server side code' or 'stuff for launchpad-bazaar'?
[00:14] <lifeless> (I'm asking because IMO launchpad plugin bugs belong in launchpad-bazaar; I think poolie has been treating it that way too)
[00:15] <jml> lifeless: I think it should be just the server side code.
[00:16] <jml> lifeless: and I *thought* I'd already said so to both you & poolie
[00:16] <lifeless> jml: Ok. Can you make this more clear on project pages etc
[00:16] <jml> although maybe not as clearly / officially / permanently as I ought
[00:16] <jml> lifeless: will do.
[00:17] <lifeless> jml: e.g. https://edge.launchpad.net/launchpad-bazaar it entirely unclear, though it is a wonderful mission statement
[00:18] <lifeless> it just doesn't help me understand what bugs/questions are relevant there :)
[00:21]  * jml sends an email to a person
[00:22]  * thumper feels like he needs a PR person sometimes
[00:34] <poolie> hello thumper
[00:34] <lifeless> bam bam
[00:34] <thumper> hi poolie
[00:37] <lifeless> vila: how are you going?
[00:37] <vila> trying to understand what is *in* the heap in CHKMap,iter_changes
[00:38] <lifeless> vila: ok; do you suspect a bug in that later?
[00:39] <lifeless> *layer*
[00:39] <vila> so far, yes.
[00:39] <lifeless> vila: it should be trivial to examine whitebox style - left = dict(map1.iteritems()), right = dict(map2.iteritems())
[00:40] <lifeless> then you can say deleted_keys = set(left) - set(right)
[00:40] <lifeless> and new_keys = set(right) - set(left)
[00:40] <lifeless> and (a little more work needed)
[00:41] <lifeless> unchanged = set([key for key in set(left).intersection(set(right)) if left[key] == right[key]])
[00:41] <lifeless> changed = set(right).intersection(set(left)) - unchanged
[00:42] <lifeless> and you can do this from within a debugger in CHKInventory.iter_changes, before the loop
[00:42] <lifeless> and compare it to
[00:42] <lifeless> list(self.id_to_entry.iter_changes(basis.id_to_entry))
[00:42] <lifeless> vila: ^
[00:43] <vila> ack
[00:51] <lifeless> poolie: http://www.google.com.au/search?q=launchpad+bazaar+password+authentication&ie=utf-8&oe=utf-8&aq=t&rls=com.ubuntu:en-US:unofficial&client=firefox-a
[00:51] <lifeless> my google-fu is strong
[00:51] <vila> right, so since the tests is about renaming a single file unchanged shouldn't be empty
[00:51] <vila> right, so since the test is about renaming a single file unchanged shouldn't be empty
[00:52] <lifeless> vila: 'changed should not be empty'
[00:52] <lifeless> ?
[00:52] <vila> changed is empty too
[00:53] <lifeless> vila: keep poking it for a little bit, I'll just flush my cache
[00:53] <vila> I really meant unchanged shouldn't be empty, there is a directory and a file inside it that are used in the test but not concerned by the rename itself
[00:54] <lifeless> vila: ok
[00:54] <vila> so may be the bug occured before, when the map were built
[00:54] <lifeless> vila: note that unchanged is not reported by iter_changes
[00:54] <vila> so may be the bug occured before, when the maps were built
[00:55] <lifeless> vila: so its the dict comparison that would show them as unchanged
[00:55] <vila> lifeless, sure, I used it as the simplest communication vector, eye-grepping left and right told me that before
[00:55] <lifeless> vila: you can also do self[self.path2id['dir'] etc to check
[00:56] <vila> in left: (('b-id',), 'dir: b-id\x00root-id\x00b\x00vila@scythe-20081114004115-p86lzmmfsqqie2a3')
[00:56] <vila> in right: (('b-id',), 'dir: b-id\x00root-id\x00b\x00vila@scythe-20081114004115-oh1ijsqf60ht5rzs')
[00:57] <vila> is the latest part a rev-id ?
[00:59] <vila> that's the crux of the problem, there is no difference between the twosm yet iter_changes saw them as different
[01:03] <lifeless> vila: yes, the end is the revision_id
[01:03] <lifeless> they are different
[01:03] <lifeless> but perhaps inv.iter_changes is not meant to report these differences
[01:03] <lifeless> ah yes
[01:04] <lifeless> in CHKInventory.iter_changes
[01:04] <lifeless> if there is no change at all, but the revision is different, just continue
[01:04] <lifeless> rather than yielding
[01:07] <lifeless> so
[01:08] <lifeless> if not changed_content and parent[0] == parent[1] and name[0] == name[1] and executable[0] == executable[1]:
[01:08] <lifeless>     continue
[01:12] <jfroy|work> jelmer: I'm getting a weird failure trying to branch a bzr branch whose parent is a Subversion branch
[01:12] <jelmer> jfroy|work, what's the error?
[01:13] <jfroy|work> bzr: ERROR: Revision {svn-v4:be02940b-5f7b-422b-ba6c-1eb93f4884eb:<path>:7882} not present in "6604@be02940b-5f7b-422b-ba6c-1eb93f4884eb:<path>".
[01:14] <jfroy|work> It's strange not because it is happening per se, but it's happening if I try to branch the the branch in a different repository
[01:14] <jelmer> jfroy|work, this is what the warning in bzr-svn trunk is about..
[01:14] <vila> lifeless, that fixed some failures 17 failures out of 36 :)
[01:14] <jfroy|work> The source branch is in shared repository A, and I can branch it in that repository fine. But if I try to branch in repository B, it fails with that error.
[01:14] <jelmer> jfroy|work, the output of bzr-svn trunk can change, breaking some core assumptions made in bzr
[01:15] <jfroy|work> Right, I used trunk for a brief while some time ago.
[01:15] <jfroy|work> But I am not right now.
[01:15] <jelmer> the same key refers to slightly different contents in bzr apparently
[01:16] <jelmer> jfroy|work, one of the revisions you're fetching was apparently imported using trunk
[01:28] <vila> lifeless, so, out of the 19 remaining failures, most need either specific_files filter  or include_unchanged or want_unversioned implemented
[01:29] <vila> 3 sounds like bugs in CHKInventory.inter_changes about missing/renamed files. I'll look into them first
[01:29] <lifeless> ok
[01:29] <lifeless> commit and push first
[01:29] <lifeless> small steps
[01:34] <jfroy|work> jelmer: OK sorry, had to take care of something
[01:35] <jfroy|work> I checked out the svn branch in repository B just fine.
[01:35] <jfroy|work> So basically, I should re-branch the svn branch in repository A
[01:35] <jfroy|work> And indeed, I might have done the initial checkout in repository A using bzr-svn trunk.
[01:35] <poolie> ok i'm going back to 288751 now
[01:36] <poolie> i might push my bzr branch of that and get some user testing
[01:44] <funkychicken818> hey i am running bzr on my windows box and i created a project on my linux box and i am getting the error Not a branch
[01:44] <funkychicken818> i a connecting via ftp
[02:08] <lamalex> is there any documentation on setting up a server to be able to push to and pull from?
[02:09] <lifeless> lamalex: yes, in the users guide
[02:11] <lamalex> yah, i just found it
[02:11] <lamalex> my google-fu was failing me, but now i got it
[02:13] <lifeless> vila: how are you progressing?
[02:14] <vila> lifeless, :) You always ping just when I want to ask you a question :)
[02:14] <lifeless> its the chip implanted in your brain
[02:14] <lifeless> I get a flashing red LED here
[02:14] <vila> lifeless, haaa, I thought it was tobacco craving...
[02:15] <vila> so, for bzrlib.tests.intertree_implementations.test_compare.TestIterChanges.test_missing_and_renamed
[02:16] <vila> CHKMap,iter_changes knows nothing about the missing file renamed and transformed into a directory and I don't understand if that's the bug
[02:17] <lifeless> so
[02:17] <lifeless> this may need special casing in the test
[02:17] <lifeless> RevisionTree.iter_changes(RevisionTree) can never have 'missing' files :)
[02:19] <vila> you mean something like in test_only_in_source_and_missing (just below) ?
[02:20] <lifeless> vila: yes
[02:20] <lifeless> only on tree2
[02:20] <lifeless> erm
[02:20] <vila> sure
[02:20] <lifeless> *thinks*
[02:20] <lifeless> yes
[02:20] <lifeless> tree12
[02:20] <lifeless> *2*
[02:22] <vila> well, in the permutation we added, we want only the tests that use two revision trees and we don't want tests that need one or two working treees (as tests about missing files are)
[02:22] <vila> do you agree ?
[02:22] <spiv> ~.
[02:24] <lifeless> vila: one working tree will be fine
[02:24] <lifeless> vila: because the existing dirstate<->workingtree needs one revision tree
[02:24] <lifeless> vila: so the new if block should be tree2 only
[02:25] <vila> I added         if not tree2.path2id('directory'): for test_missing_and_renamed
[02:25] <lifeless> cool
[02:26] <vila> my question was more about why we encounter these failing tests and a general rule I can apply for the other ones :)
[02:26] <lifeless> vila: yes, I agree
[02:27] <vila> test_only_in_target_and_missing for example needs kind of the same test for the same root cause, the change ends up being a 'missing' one that can be represented in our case
[02:29] <vila> and instead of duplicating that block, I'll do a helper named file_id_is_missing(path) that will raise TestNotApplicable, agree ?
[02:30] <vila> file_id_cannot_be_missing_in(path, tree)
[02:31] <lifeless> how about
[02:31] <lifeless> not_applicable_if_missing_in(path, tree)
[02:31] <vila> deal
[02:32] <lifeless> self, path, tree actually :P
[02:32] <lifeless> hmm, unless it needs to be a function, then path, tree is fine :>
[02:32] <vila> yeah, yeah, don't worry :)
[02:37] <lifeless> jam: spiv: - there are two cases I think, xml->chk, and chk->chk
[02:37] <lifeless> the former hits interdiffering
[02:38] <lifeless> so fetch.py should just find the nodes only-in the interesting inventory maps
[02:38] <lifeless> I suggest a new method on chk_map to support this; similar to the iter_changes one
[02:38] <lifeless> because it has the same problems with when-are-duplicate-keys-encountered
[02:39] <lifeless> it probably wants to take two sets though, not two objects
[02:39] <jam> right
[02:40] <lifeless> a naive implementation (use iterchanges, discard some data) is probably easy to get going, and will let the interface be settled
[02:43] <lifeless> in terms of layering
[02:43] <lifeless> hmm, actually, I'll comment later
[02:43] <lifeless> other than to say I agree its not a CHKMap method
[02:46] <a_c_m> how can i run bzr as the nobody user ("bzr commit" is being spawned by a exec() command from php)
[02:47] <lifeless> a_c_m: bzr doesn't particularly care
[02:47] <lifeless> a_c_m: just make sure your permissions etc allow it to do what it needs :>
[02:47] <a_c_m> lifeless: i think they are, but i think bzr is expecting a .bzr directory in the users home folder
[02:47] <a_c_m> which being the nobody user, it doesn't have
[02:47] <a_c_m> anyway to bypass that check?
[02:48] <lifeless> a_c_m: it needs a ~/.bazaar, and a ~/.bzr.log it can write too
[02:48] <lifeless> you'll need them available in whatever account it is running as
[02:48] <a_c_m> right, so how do i create / fake that, as a the nobody user ?
[02:49] <a_c_m> who doesnt have a home directory ?
[02:49] <bob2> 'nobody' shouldn't own any files
[02:49] <lifeless> a_c_m: well, my advice would be to not run bzr as 'nobody'
[02:50] <a_c_m> right, but i dont have that option really
[02:50] <lifeless> nobody isn't meant to have write access anywhere, so asking bzr to do something your system is almost certainly setup to prevent won't end well
[02:53] <lifeless> a_c_m: why don't you have an option?
[02:53] <bob2> use sudo to run a trivial shell script that can only commit the required stuff
[02:54] <a_c_m> the bzr statement is being kicked off by apache
[02:54] <lifeless> a_c_m: so? tell apache what user to use
[02:54] <a_c_m> i think i've worked out a way around it
[02:54] <a_c_m> apache user == nobody
[03:39] <lifeless> awesome
[03:40] <lifeless> some one just mailed me asking how to login in  latin on intrepid
[03:40] <bob2> haha
[03:40] <lifeless> I'll need to fix it again I suspect :P
[03:44] <lifeless> perf testing this children thunk
[03:44] <lifeless> I expect satisfactory results, because the design makes sense to me :)
[03:44]  * lifeless has no ego, really
[03:54] <flacoste> is there a bzr-svn ppa?
[03:54] <flacoste> or any way to get a bzr-svn to go with bzr 1.9 package?
[03:54] <flacoste> i'm on hardy, btw
[03:58] <lifeless> ugh
[03:58] <lifeless> Inventory.apply_delta mutates the inventory entries it is passed
[03:58]  * lifeless fixes
[03:58] <lifeless> flacoste: not sure
[03:59]  * flacoste thinks i might be better to use bzr-svn as a branch
[04:22] <Peng_> Woah why is Loggerhead using half my RAM?
[04:23] <Peng_> (That would be more dramatic if I wasn't running it on a $20 VPS. :P )
[04:24] <poolie> lifeless: so at the moment "_fetch_uses_delta" determines "include_delta_closure" but they're not really the same thing
[04:35] <jml> Peng_: *probably* a bug in Bazaar's logging. The Launchpad Code team are looking at it.
[04:35] <jml> (it's one of our dozen #1 priorities)
[04:36] <Peng_> It was only 200 MB. I was surprised because it almost doubled in 6 hours.
[04:36] <Peng_> (doubled *to* 200 MB, I mean)
[04:37] <Peng_> jml: Logging leaks RAM?
[04:38] <jml> Peng_: uhh, I meant "something in getting a revision log". I haven't been following the details of the discussion.
[04:39] <lifeless> spiv: jam: just pushing a tweak to allow inv._make_delta(inv), which unsurprisingly improves fetching from dev3 to dev4 dramatically
[04:42] <Peng_> jml: Oh!
[04:43] <Peng_> Hey look, it dropped 4 MB of RAM.
[04:43] <Peng_> Anyway..
[04:48] <cafuego> How do I increment the version no of a repo to an arbitrary integer?
[04:49] <Peng_> You, uh, don't?
[04:49] <AfC> cafuego: while `/bin/true` ; do bzr commit --unchanged ; done
[04:49] <Peng_> Or that.
[04:49] <AfC> cafuego: that outta do ti. :|
[04:50] <cafuego> AfC: ta
[04:50] <lifeless> cafuego: <why>?
[04:50] <AfC> [notice the subtle "ti" mimicking the reversed "fi" that ends a shell if block, clearly I was playing on that instead of just saying "outta do it". Yup. Uh huh]
[04:50] <cafuego> Peng_: I'm setting up bzr for a piece of software that's at rev 12. I'm missing v1 and 2, but would like the commits match the version number (it's a single php file)
[04:51] <cafuego> AfC: if you 'sudo rmmod sjh' the problem should go away ;-)
[04:51] <AfC> cafuego: uh, Peter, can I politely suggest that you're on completely the wrong track?
[04:51] <cafuego> Yes, you can.
[04:51] <AfC> cafuego: as for your task at hand, why not just use tags?
[04:52] <cafuego> That sounds like more work ;-)
[04:52] <AfC> [sooner or later you're going to have more than one commit : "version" and you'll be screwed anyway, hence my suggestion expressed a moment ago]
[04:52] <cafuego> AfC: No, that work would be done ona  dev branch, not on trunk.
[04:52] <AfC> cafuego: or, do what everyone else does, and have the version embedded in a file somewhere and ignore it from there.
[04:52] <cafuego> AfC: I'll merge those into trunk and a single revision, thus keeping it in sync.
[04:53] <mlh> while true; do something; done
[04:53] <mlh> no need - in fact you shouldn't backtick it
[04:53] <AfC> mlh: I was in a channel the other day where someone had the nick 'something'. The conversation went to Who's On First" in a real hurry.
[04:54] <mlh> hah
[04:54] <AfC> mlh: Ah yes. I knew that. In fact, that's what my fingers typed, and then I second guessed myself. Thanks
[04:55] <mlh> while I'm on a roll ... :-)
[04:55] <mlh> true is faster than /bin/true, being a builtin (I think) and : might be even faster
[04:58] <AfC> mlh: it is a builtin, yes
[04:58] <AfC> $ help true
[04:58] <lifeless> I don't knows on third
[05:01] <vila> lifeless, just pushed handling specific files for iter_changes
[05:02] <lifeless> sweet
[05:02] <cafuego> right, done, excellent.
[05:08] <poolie> lifeless: like http://pastebin.ubuntu.com/71665/
[05:09] <poolie> unfortunately now i understand it i can't think of a better way to explain it :)
[05:11] <jml> spiv: want some sad news?
[05:12] <jml> Using saved push location: bzr+ssh://bazaar.launchpad.net/...
[05:12] <jml> No new revisions to push.
[05:12] <jml> HPSS calls: 19 <bzrlib.smart.medium.SmartSSHClientMedium object at 0x12aeed0>
[05:12] <jml> HPSS calls: 6 <bzrlib.smart.medium.SmartSSHClientMedium object at 0x142e550>
[05:12] <jml> HPSS calls: 7 <bzrlib.smart.medium.SmartSSHClientMedium object at 0x1444090>
[05:12] <lifeless> poolie: why line 23/24 ?
[05:24] <lifeless> http://paste.ubuntu.com/71472/
[05:25] <spiv> jml: not as bad as I'd fear ;)
[05:26] <jml> spiv: if I had to call Tim 32 times to find out I had nothing to do, I'd be upset. :)
[05:28] <jml> hmm. you could probably make a parlour game out of protocol design.
[05:28] <poolie> jml :-)
[05:28] <spiv> jml: I noticed recently how many times waiters at restaurants come up to your table to find out that everything is fine.
[05:29] <poolie> varies per country and restaurant
[05:29] <jml> spiv: polling sucks
[05:29] <poolie> lifeless: it's not a big deal, it just seems like it's a class property not an instance one
[05:29] <jml> poolie: I'm semi-serious though.
[05:30] <lifeless> poolie: formats are instances :)
[05:32] <lifeless> how does lh want patches? branches? bb? lp merge-proposals
[05:32] <lifeless> ?
[05:32] <poolie> jml, i know
[05:36] <cafuego> spiv: i noticed they all did that in adelaide, not so much in melbourne.
[05:46] <poolie> lifeless:  i think through lp
[05:47] <lifeless> jml: ^^ lh above is loggerhead
[05:48] <jml> lifeless: I don't know for sure. I think bb.
[05:48] <jml> lifeless: I merely hang out with a bunch of people who care about loggerhead :)
[05:51] <vila> lifeless, yeah for getting rid of make_inv_delta !!
[05:52] <rockstar> lifeless, did you happen to hack on that profiling for loggerhead.
[05:52] <lifeless> rockstar: thats why I'm asking
[05:53] <rockstar> lifeless, oh, I hadn't read backlog.
[05:53] <rockstar> Submit a merge proposal.
[05:53] <lifeless> ok
[05:53] <lifeless> I've only just started now
[05:53] <lifeless> but the day is close to halt() so getting the facts straight
[05:54] <lifeless> rockstar: I was planning on writing the profile to request_serial.callgrind in the working dir
[05:54] <rockstar> lifeless, there's something going on with stderr.  I couldn't capture it properly.
[05:57] <rockstar> I wanted to put the profiling data into the HTTPResponse, but it never really worked right.
[05:57] <lifeless> rockstar: ok, well I don't :)
[05:57] <lifeless> rockstar: should I preserve yours, or just alter it to suit?
[05:58] <rockstar> lifeless, alter to suit.
[06:02] <lifeless> rockstar: the reason I don't, is that it would force buffering and be a race condition,FWIW
[06:03] <rockstar> lifeless, oh, I'm fine with that.  In fact, if I could get more detail in a log, then I'd rather have that.
[06:03] <lifeless> what is the getattr('close' thing all about ?
[06:04] <rockstar> lifeless, no idea.  I haven't touched that branch in two weeks.  I was probably in the middle of scheming something.
[06:05] <lifeless> ok
[06:05] <lifeless> and self.lock?
[06:06] <rockstar> lifeless, threading thing.
[06:06] <lifeless> yah, just climbed into the base class
[06:07] <lifeless> fugly
[06:07] <rockstar> lifeless, indeed!
[06:08] <lifeless> most of it has to do with buffering.
[06:08] <lifeless> overly clever fools.
[06:09] <rockstar> Yea, I figured I could have removed much of that code.
[06:11] <lifeless> also,  it will buffer badly; list.extend is not the fastest thing in the world
[06:11] <lifeless> I particularly like their use of inline methods
[06:13] <poolie> lifeless: this is the basic approach to instert_records:
[06:13] <poolie>                 # We can insert the knit record literally if either we already
[06:13] <poolie>                 # have its basis OR the basis is not present even in the
[06:13] <poolie>                 # fallbacks.  In the latter case it will either turn up later
[06:13] <poolie>                 # in the stream and all will be well, or it won't turn up at
[06:13] <poolie>                 # all and we'll raise an error at the end.
[06:14] <lifeless> rockstar: just adding save to disk, then will be done
[06:16] <lifeless> poolie: not quite right. I think:
[06:16] <lifeless> poolie: ah, never mind me, thats fine
[06:17] <lifeless> poolie: I was thinking that it may make fulltext things it doesn't need to; that we could (should?) insert it literally always, if we dno't have its basis then at the end, copy the basis in as a full text.
[06:17] <lifeless> (from the fallback repo)
[06:17] <lifeless> poolie: butperhaps this is over complicated
[06:19] <poolie> i thought about that too
[06:19] <poolie> however, it seems like you may end up with more data
[06:20] <poolie> because you'll get a fulltext plus a delta rather than just one (perhaps larger) fulltext
[06:20] <poolie> there are various possibilities, like if you get a lot of direct children of a fulltext that's in the fallback repo
[06:20] <lifeless> thats true; OTOH we won't ever turn a ft into a delta, so perhaps more data here is better for when its merged to the trunk repo.
[06:20] <poolie> it would have been better to just copy it
[06:21] <poolie> true
[06:21] <poolie> so it does seem more complicated because you have to recurse back in to the fallback repo to get the delta closure...
[06:21] <lifeless> (that's kindof a flaw itself, but we're working with what we have today ;P)
[06:21] <lifeless> poolie: so, your text is fine; we both thought about and discarded the same thing
[06:23] <poolie> ok
[06:23] <poolie> so i have that approach working
[06:23] <poolie> insert_records is a bit complex i'm going to see if i can refactor that
[06:23] <poolie> but it is passing now
[06:31] <lifeless> rockstar: I can has kcachegrind love
[06:32] <lifeless> 26% in simpletal
[06:32] <lifeless> expandInline
[06:32] <lifeless> ok, not bzrlib. yay
[06:33] <lifeless> something silly is logging gif content to stdout
[06:33] <lifeless> oh, thats me
[06:33] <lifeless> whats all this /static stuff ?
[06:34]  * lifeless thinks loggerhead trunk is broken
[06:34] <lifeless> (assuming this is close to trunk)
[06:34] <lifeless> anyho
[06:34] <lifeless> w
[06:35] <lifeless> rockstar: its done
[07:09] <vila> lifeless, only 2 failures left for ./bzr selftest --no-plugins -s bt.intertree IterChange.*CHK
[07:10] <lifeless> vila: congrats
[07:17] <pygi> morning folks
[07:27] <poolie> hello pygi
[07:28] <poolie> lifeless: so now some of the effort tests in test_knit are failing
[07:28] <pygi> hey poolie, how's it going? :)
[07:32] <lifeless> poolie: push one in, the other pops out
[07:34] <poolie> ?
[07:35] <lifeless> commenting on bug fixing in general
[07:36] <poolie> oh, right
[07:47] <lifeless> rockstar: around?
[07:52] <poolie> woo!
[07:52] <poolie> bug 288751 is dead, i think
[07:52] <poolie> and probably all its brothers
[07:55] <lifeless> poolie: congrats!
[08:17] <vila> lifeless, no more failures :)
[08:17] <vila> lifeless, pushed to bbc
[08:19] <lifeless> vila: vcool
[08:20] <vila> lifeless, I kept all the hacks in the same place so there will be a single place to de-hack :)
[08:35] <vila> lifeless, TestCompare tests passing too
[08:40] <igc> night all
[08:43] <poolie> night
[09:59] <visik7> hi
[09:59] <visik7> good morning
[09:59] <visik7> at least here :P
[10:04] <visik7> I need to remove some files that lives in my history that are HUGE and when I mean huge I mean 600mb  that is not anymore in the tree and they are present only for 1 revision
[10:04] <visik7> is there a way ?
[10:08] <visik7> jquery
[10:08] <visik7> ops
[10:10] <eleftherios> :-)
[10:22] <splodge> Is there a command akin to 'switch' for branches - i.e. created with 'branch' not 'switch'?
[10:24] <splodge> I haven't found anything so far and wonder if the only way is to delete my local branch and issue the branch command again for the one I want?
[10:25] <hmeland> Maybe "pull --overwrite", depending on exactly what you mean by "akin to".
[10:25] <splodge> Which is a bit of a shame because the branches contain lots of similar code
[10:26] <splodge> Maybe overwrite will work. I'll take a look
[10:27] <splodge> Perfect! Thanks.
[10:28] <hmeland> Also, you could create a shared repository above the branch, and "bzr reconfigure" the currently --standalone branch into a --use-shared branch.
[10:33] <splodge> I'll take a look into it, thanks.
[10:38] <jbl1> I'm using bzr v1.3.1 from Ubuntu 8.04 LTS right now.  I planning on sticking with the latest bzr available in ubuntu for production use, because it gives me a good indication of how stable that version of bzr is, and how backward compatible it might be in the event of an upgrade.  Does anyone see any problems with this, or should I be trying to stick to the latest version of bzr off the website?
[10:58] <AfC> Sorry, what gives you an indication of "stable for production use"?
[10:58] <AfC> You should most certainly be using the latest release of Bazaar if you are able. That's where the bug fixes are.
[11:44] <awilkins> Yes, the enormous test suite is far more reassuring than a slow creep of revision numbers
[12:17] <ikarus2k> hello everyone. I was wondering, could Bazaar be used within a design department? That would mean large files (10-300MB), autoversioning would be nice...
[12:17] <awilkins> It wouldn't be advisable
[12:17] <awilkins> It's not suited to large files
[12:17] <awilkins> Have you considered ZFS?
[12:19] <awilkins> It wouldn't provide iron-clad-forever versioning but it would give you a considerable cusion
[12:19] <awilkins> *cushion
[12:21] <ikarus2k> ... ZFS -> the file system? does it store previews (1-step) versions?
[12:31] <ikarus2k> ah, the copy-on-write feature, thnx alott
[12:37] <ikarus2k> k , thnx bye
[12:50] <visik7> I need to remove some files that lives in my history that are HUGE and when I mean huge I mean 600mb  that is not anymore in the tree and they are present only for 1 revision
[12:51] <hiperlink> Hi all, I'm in linux and tried to install the vimdiff plugin (copy to ~/.bazaar/plugins/vimdiff (there are README and __init__.py)), making the .py executeable, but when I do 'bzr plugins' it's not listed.
[12:51] <hiperlink> what am I missing?
[12:55] <Odd_Bloke> hiperlink: Look in ~/.bzr.log, it might tell you.
[13:02] <hiperlink> @Odd_bloke as I'm not a python programmer, I'm not good at interpreting this: http://gist.github.com/24890
[13:03] <Odd_Bloke> hiperlink: If you 'cd ~/.bazaar/plugins', 'python -c "import vimdiff"', what happens?
[13:06] <hiperlink> ImportError: "No module named vimdiff"
[13:07] <hiperlink> oh I got it, accidentally I moved the __init__.py to plugins/ not into plugins/vimdiff/.
[13:07] <hiperlink> Anyway: thanks for your help
[13:07] <Odd_Bloke> Yeah, that'll do it.
[13:07] <hiperlink> now it works.
[14:07] <hmeland> visik7: Your best bet is probably to branch the revision just before the giant file was introduced (revision N), and then use the "rebase" plugin to re-create revisions N+2... on top of revision N (i.e. skipping revision N+1).
[14:08] <visik7> :/
[14:08] <hmeland> This means that the revisions N+2... will have their revision-id change, so any branches off the un-rebased revision will become stale/still include the giant file.
[14:35] <beuno> lifeless, you filed to merge proposals with the same commits, except for a last one. Any reason for that?  to land them separetly?
[14:54] <cr3> if I pushed a commit but then I want to revert that commit in order to make little commits, how can I revert without removing those files that were added?
[14:57] <cr3> maybe I could do a bzr revert -r1; bzr diff -r1..2 | patch?
[14:59] <cr3> err, 2..1
[15:05] <cr3> nevermind, all figured out now
[15:42] <army> hi ,bzr-svn do not wok , i installed bzr-svn with macports,
[15:43] <army> bzr checkout svn+http://www.prestashop.com/publicsvn/trunk/ shop-trunk The svn+ syntax is deprecated, use http://www.prestashop.com/publicsvn/trunk/ instead. - [                                                        ] copying revision    0/4815
[15:44] <army> stay in this screen about five minute,
[15:57] <Odd_Bloke> army: Are you sure it's not doing anything?
[15:58] <Odd_Bloke> Just because it's not reporting progress doesn't mean it's not doing anything (unfortunately).
[15:58] <army> ? yes ,no reporting progress,
[16:01] <army> Initialising Subversion metadata cache in /Users/army/.bazaar/svn-cache/6e0da8f0-d90d-0410-b14f-823b0ad1652c   bzr: ERROR: plugins is already versioned
[16:52] <davidstrauss> If you have a checkout with local commits, how can one commit, say, a single file to the bound branch? We get "ERROR: Selected-file commit of merges is not supported yet" right now.
[20:48] <vadi21> Hi, I have a question about the bzr notification - it's only giving me notifications when I commit. Is that it's supposed behaviour? I thought it would notify me when others committed.
[20:49] <LarstiQ> vadi21: which notification and which others?
[20:49] <vadi21> LarstiQ: when I commit locally, it pops up a notification. But not when someone else commits to a repository I'm involved with.
[20:49] <LarstiQ> vadi21: if you're in a lan setting with others using bzr, they'd have to send out notifications, and you listening to that, to be notified.
[20:50] <vadi21> Oh.
[20:50] <vadi21> Can I make it notify me of launchpad notifications?
[20:50] <LarstiQ> I'm not aware of launchpad notifications?
[20:51] <LarstiQ> could be some feature got introduced without me noticing
[20:51] <vadi21> Ah nevermind then, just thought that would be more useful. Thanks for your explanation
[20:52] <LarstiQ> vadi21: for launchpad branches, you could hook it up to rss of course
[20:55] <vadi21> Yeah
[20:58] <LarstiQ> vadi21: but if we're talking about the same notification thing, that is not what it was originally written for
[21:00] <dobey> yeah i don't really get why bzr-gtk does notifications anyway
[21:04] <LarstiQ> dobey: how so?
[21:04] <Odd_Bloke> dobey: It's intended to tie into the bzr-dbus stuff, so you can get notifications whenever someone on the network commits.
[21:04] <dobey> LarstiQ: i don't really need to see a notification of when i commit, or when i pull new revisions
[21:05] <LarstiQ> dobey: right, that's not the primary usecase
[21:05] <dobey> Odd_Bloke: that makes sense, but notifying for local commits/pulls is rather annoying
[21:29] <abentley> spiv: ping
[21:31] <davidstrauss> If you have a checkout with local commits, how can one commit, say, a single file to the bound branch? We get "ERROR: Selected-file commit of merges is not supported yet" right now.
[22:02]  * beuno realizes he's committed random messages to Loggerhead