/srv/irclogs.ubuntu.com/2011/04/17/#bzr.txt

=== psynaptic is now known as psynaptic|away
=== psynaptic|away is now known as psynaptic
=== psynaptic is now known as psynaptic|away
=== psynaptic|away is now known as psynaptic
=== psynaptic is now known as psynaptic|away
=== psynaptic|away is now known as psynaptic
dchiltonI've a bzr-managed tree that's got years of history.  I'd like to ideally clear out all history before a specific revision # ~ 1 month ago.  Is there a way to do that?  Another option is just to start 'from zero history', with a new/immediate revision.  Is that a (better) option?02:22
quiznilossh-copy-id appears to have locked up!03:06
quiznilois that typically a long-running command?03:06
=== psynaptic is now known as psynaptic|away
wizonesolutionsI just restored a branch from backup that was a bound branch. The repository got corrupted cuz of a bad disk, so I unbound it. However, bzr status shows all files as new and it doesn't appear to have any revision history. I thought that branches should be able to stand alone? Where are the revisions stored? Maybe I didn't restore something...03:11
wizonesolutionsOh, and the repository was on a different box, so this was a checkout. I restored just the checkout.03:24
wizonesolutionsHopefully once I put the new HD in the offending box I'll be able to restore the bad pack to that too and then maybe I can rebind it and reconcile it. I mean, if I was still able to commit (I was) then perhaps I'm OK. But yeah...if anyone has any ideas on what could cause a checkout that is later unbound to be unaware of its own history (it was a heavy checkout)...all ears.03:25
lifelesswizonesolutions: bzr info -v ?03:26
wizonesolutionslifeless: http://pastebin.com/YE7vuyyj03:32
lifelessthanks, trying to bring that up (having some issue, may be local internet)03:35
wizonesolutionslifeless: If it expires let me know...I set it to 10 mins03:36
lifelessI can't seem to grab any new tcp connections03:39
lifelessoutside of nz03:39
wizonesolutionslifeless: pm?04:02
lifelesssure04:11
lifelessthat should work04:11
lifelesswizonesolutions: what about 'bzr revision-info'04:23
wizonesolutions0 null:04:25
lifelesshm04:30
lifelessif you have bzrtools you should be able to run 'bzr heads --all' to find out if the history is locally available04:31
wizonesolutions"No heads found"04:36
wizonesolutionsIt is truly hosed, doctor?04:42
lifelesssounds like it04:43
lifelessuhm04:43
lifelessbzr dump-btree .bzr/repository/pack-names04:43
lifelessmight be a non trivial final check04:43
wizonesolutionsYep it's empty. Strange. I guess that checkouts aren't as full as I thought when a shared repo is in the mix. Good to know.04:44
wizonesolutionsThis taught that me that I should only use shared repos if I plan to put stuff in them that actually will have shared revisions. Otherwise it's a rather undesirable point of failure for several unrelated branches!04:45
wizonesolutionsNo pain no gain, eh04:45
wizonesolutionsGood thing for backups04:45
wizonesolutionsMaybe I will be able to recover it on the new HD, fingers crossed04:45
wizonesolutionsIt's an old pack that's unreadable so I don't think it's been changed for quite some time...04:46
lifelessgood luck04:49
=== psynaptic|away is now known as psynaptic
sobersabrehi guys.17:29
sobersabreIs there a diagram/table describing time/size complexity of bzr operations - like adding, checkout, update, etc. ?17:29
lifelesssobersabre: add should be near instance21:04
lifelessoperations that extract text from the repo need about twice the size of the largest file they extract in memory21:04
pooliehi all23:14
jelmerhi poolie23:22
pooliehi jelmer23:23

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