=== 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
[02:22] <dchilton> I'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?
[03:06] <quiznilo> ssh-copy-id appears to have locked up!
[03:06] <quiznilo> is that typically a long-running command?
=== psynaptic is now known as psynaptic|away
[03:11] <wizonesolutions> I 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:24] <wizonesolutions> Oh, and the repository was on a different box, so this was a checkout. I restored just the checkout.
[03:25] <wizonesolutions> Hopefully 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:26] <lifeless> wizonesolutions: bzr info -v ?
[03:32] <wizonesolutions> lifeless: http://pastebin.com/YE7vuyyj
[03:35] <lifeless> thanks, trying to bring that up (having some issue, may be local internet)
[03:36] <wizonesolutions> lifeless: If it expires let me know...I set it to 10 mins
[03:39] <lifeless> I can't seem to grab any new tcp connections
[03:39] <lifeless> outside of nz
[04:02] <wizonesolutions> lifeless: pm?
[04:11] <lifeless> sure
[04:11] <lifeless> that should work
[04:23] <lifeless> wizonesolutions: what about 'bzr revision-info'
[04:25] <wizonesolutions> 0 null:
[04:30] <lifeless> hm
[04:31] <lifeless> if you have bzrtools you should be able to run 'bzr heads --all' to find out if the history is locally available
[04:36] <wizonesolutions> "No heads found"
[04:42] <wizonesolutions> It is truly hosed, doctor?
[04:43] <lifeless> sounds like it
[04:43] <lifeless> uhm
[04:43] <lifeless> bzr dump-btree .bzr/repository/pack-names
[04:43] <lifeless> might be a non trivial final check
[04:44] <wizonesolutions> Yep 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:45] <wizonesolutions> This 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] <wizonesolutions> No pain no gain, eh
[04:45] <wizonesolutions> Good thing for backups
[04:45] <wizonesolutions> Maybe I will be able to recover it on the new HD, fingers crossed
[04:46] <wizonesolutions> It's an old pack that's unreadable so I don't think it's been changed for quite some time...
[04:49] <lifeless> good luck
=== psynaptic|away is now known as psynaptic
[17:29] <sobersabre> hi guys.
[17:29] <sobersabre> Is there a diagram/table describing time/size complexity of bzr operations - like adding, checkout, update, etc. ?
[21:04] <lifeless> sobersabre: add should be near instance
[21:04] <lifeless> operations that extract text from the repo need about twice the size of the largest file they extract in memory
[23:14] <poolie> hi all
[23:22] <jelmer> hi poolie
[23:23] <poolie> hi jelmer