/srv/irclogs.ubuntu.com/2012/08/08/#bzr.txt

mgzmorning08:10
vilahi08:11
=== zyga is now known as zyga-food
=== zyga-food is now known as zyga
vilajames_w: ping, around ?14:39
james_wvila, yep14:50
vilajames_w: I'd like to have a ppa on ~udd to replace ~vila/+archive/pkgimport but I'm not an udd admin :)14:51
james_wvila, you are now14:52
vilathanks14:52
vilajames_w: wow, and jam too, you're reading my mind or was that from someone else ?14:53
james_wvila, i saw your comment elsechannel14:57
vilayou rock ;)14:57
hallynhi - when i do 'bzr merge someothertree' it quilt pops all patches.  then doesn't re-push them.  is there any reason not to simply quilt push -a again before checking in?15:59
hallyn(i was surprised it didn't do it autmoatcially, figured ther emight be a reason :)16:00
weigonI'm trying to find a (performant) way to find all the heads in a repo. I'm actually looking for loose ends after a "uncommit" or "pull --overwrite"16:08
weigonI went with repo.get_graph().heads(repo.all_revisions()) ... but that takes quite some time to complete16:09
jelmerweigon: there is something slightly faster I think16:22
weigonjelmer: I wonder how the revisions are indexed and if that can be utilized16:31
jelmerweigon: any access to the revision graph should already use just the indexes afaik16:32
weigonjelmer: any idea how to speed it up?16:43
jelmerweigon: check out what 'bzr heads' does16:56
weigonjelmer: *doh* it is all there ...17:16
weigonjelmer: thx17:16
=== r0bby is now known as robbyoconnor
jelmermaxb: you're still occasionally contributing to the bzr package, should I consider you one of its maintainers?20:07
=== mbarnett` is now known as mbarnett
jimisCan I convert a branch of an lp:project in a local repo, to a stacked one so I can save space, but without re-branching?23:20
thumperare you using shared repositories?23:21
jimisthumper: I think so, yes23:21
jimisyou mean if the branch is in a directory where init-repo has run?23:22
jimisif so then yes23:22
thumperthen stacking will make no difference at all23:22
thumperas it is already sharing revisions23:22
jimisthumper: as it is now I have locally all metadata from the lp:project, which is too much23:23
jimisby converting to stacked I was hoping to rid this space and have only local changes23:23
jimislocal branches etc23:23
thumperyou really don't want to stack on a remote branch23:24
thumperever23:24
jimisI know, bad past experience :-)23:24
jimisso it's not possible23:24
jimis?23:24
thumperoh  it is possible, but every action will include network which will be very slow23:25
thumperlifeless: care to comment?23:25
jimisthumper: I hope I'll not do *any* action after converting to stacked. My plan is to do it in a dup copy of the original repo: 1)convert to stacked 2)back it up 3)rm -rf stacked-repo   :-)23:27
jimisanyway just playing here to find the best backup method, I'll let you know after experimenting :-)23:27
thumperjimis: how about push to launchpad?23:28
thumperthat is a pretty good backup23:28
thumperand saves you 100% disk space23:28
jimisthumper: I push what I want to be seen, but too many junk branches I don't want to push23:28
* thumper shrugs23:29
thumperok23:29
lifelessjimis: it will performance very poorly.23:42
lifelessjimis: whats the actual problem you are trying to solve ?23:42
jimislaunchpad answer 20531823:43
jimishttps://answers.launchpad.net/bzr/+question/20531823:43
jimisjust trying various ways other then the obvious, to incrementally backup everything.23:44
jimislifeless: Ideally when I'll have to restore from backup, I'll be able to re-convert to non-stacked.23:45
jimisthis will possibly be slow but it will only happen once, hopefully never :-p23:46
lifelessjimis: I think you have a flawed model about how stacked works.23:47
lifelessjimis: if you want to run efficient backups of the whole repo to another site, push the whole repo there; a small python script can push all the heads in one network transaction.23:48
lifelesssomething like bzrlib.repository.Repository.open('remotepath').fetch(bzrlib.repository.Repository.open('localpath'))23:48
lifelessstacking won't give you the ability to restore reliably, because one missing revision can render a branch unusable; and it will incur a per-branch overhead of 10 or so network round trips.23:49
lifelessyou can seed the back up repository by cloning lp:gcc from Launchpad directly to your backup server.23:50
jimisah that would be ideal23:50
lifelessif you have 400MB of local branch commits, I'd be amazed. I suspect you actually have 20 or 30MB tops23:50
lifelessits just not compacted.23:50
jimiseven less probably of raw text data, that's why I was hoping to generate minimum traffic23:51
lifelessbzr will be reasonably efficient at incremental backups.23:51
lifelessWhat I'm describing will get all the revisions23:51
lifelessyou can use your rsync of the per-branch directories to grab them and their metadata.23:52
jimisso I'll clone lp:gcc on my backup server, and then only rsync my branch subdirs, ignoring root .bzr.23:54
jimisRight?23:54

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