Barry Warsaw wrote: > On Nov 7, 2009, at 10:30 AM, Max Bowsher wrote: > >> The current situation means that EVERY TIME I try to start looking at a >> new project, I have to first check whether they are rich-root or not >> BEFORE I can run "bzr init-repo". Which is a hideous user experience. > > Not only that, but there's no clear way to know what the right > invocation of init-repo is. If you look at the branch on Launchpad, you > see something like > > Branch metadata > Branch format: Repository format: > Branch format 6 Packs containing knits without subtree support > > Hookay... but it says nothing about what option I should give to init-repo. > > Probably up at the top of the page, Launchpad should say: > > Get this branch: > bzr branch lp:launchpadlib > > Update this branch: > bzr push lp:launchpadlib > > Create a shared repository: > bzr init-repo --pack-0.92 launchpadlib (or whatever)
And not only is it rich-root that's the problem. I just got "different serializers" trying to push a branch of bzrtools. So not only do you need to check if it's rich-root, you also need to take into account 2a vs. knitpack rich-root, such that you create the right kind of repo that will actually allow you to create stackable revisions. Max.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
