poor documentation/broken link on how to use split

Bug #220067 reported by Martin Pool on 2008-04-21
2
Affects Status Importance Assigned to Milestone
Bazaar
Medium
Unassigned

Bug Description

Hi Martin,

I'm currently using bzr 1.3 and now need to re-organize a project in
that I need to split out a few sub-projects. I should use 'bzr split',
right? Well, almost... except for this error message:

"bzr: ERROR: To use this feature you must upgrade your branch at ..."

Of course, upgrading the branch requires using a well-hidden option
(either --development or --development-subtree), but first, I'd liked
to heed the warning: "Please read
http://doc.bazaar-vcs.org/latest/developers/development-repo.html
before use."

Unfortunately, this page is not too revealing: "This page does not
exist yet. You can create a new empty page, or use one of the page
templates."

FWIW, searching the website for 'split' yields almost no useful
information, either...

I dimly remember having read something about this at an earlier date,
but I only found it after perusing Google and/or Gmane quite a bit.

Martin Pool (mbp) on 2008-04-21
Changed in bzr:
assignee: nobody → mbp
importance: Undecided → Medium
status: New → Confirmed

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
> "bzr: ERROR: To use this feature you must upgrade your branch at ..."
>
> Of course, upgrading the branch requires using a well-hidden option
> (either --development or --development-subtree),

This is false. You need rich-root-pack, which is in no way hidden.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIC/bx0F+nu1YWqI0RArBiAJ9nU7R373AmCmI9oSkBSnJqMF0MKACfRmwo
TLLdNI0eCScp8TuZa4EAcq8=
=lARI
-----END PGP SIGNATURE-----

ToniMueller (support-oeko) wrote :

Well... being the naive user, I do this (being in /home/project/somewhere, with a subdirectory 'webimport', and /home/project being the root of the tree):

$ bzr split webimport
bzr: ERROR: To use this feature you must upgrade your branch at file:///home/project/.
$ cd ..
$ bzr upgrade
bzr: ERROR: The branch format Bazaar-NG meta directory, format 1 is already at the most recent format.
$ bzr upgrade -h
[ lots of stuff, then: ]
    --development-subtree
                        Current development format, subtree variant. Can
                        convert data to and from pack-0.92 (and anything
                        compatible with pack-0.92) format repositories.
                        Repositories in this format can only be read by
                        bzr.dev. Please read http://doc.bazaar-
                        vcs.org/latest/developers/development-repo.html before
                        use.
[ lots more stuff ]
    --rich-root-pack New in 1.0: Pack-based format with data compatible
                        with rich-root format repositories. Incompatible with
                        bzr < 1.0
...

$ bzr info
Standalone tree (format: pack-0.92)
Location:
  branch root: .

You may be right that --rich-root-pack is required, and that it's not hidden (I just verified this), but at least the documentation doesn't point this out, but instead points in a different direction, imho. Unless one already knows what a 'rich-root-pack' might be (I don't), one would not know where to go, and instead be misguided by the description under --development-subtree'.

Martin Pool (mbp) on 2009-07-23
Changed in bzr:
assignee: Martin Pool (mbp) → nobody
John C Barstow (jbowtie) wrote :

The page mentioned in this bug report now exists and contains information on upgrading a branch.

Changed in bzr:
status: Confirmed → Fix Released
milestone: none → 2.2.0
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers