bzr-1.7rc1 bzr branch --stacked problem/question

[John Arbash Meinel]

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

Aaron Bentley wrote:
> David Ingamells wrote:
>> On closer examination of the bzr messages, it looks like the problem is
>> that bzr branch --stacked has not been updated to use format 1.6.1
>> instead of the killed format 1.6:
> 
> 1.6 was not killed.  1.6-rich-root was killed, and replaced with
> 1.6.1-rich-root.
> 
>>> since bzr is MAKING the named branch why does it then complain that
>>> the format is no good?
> 
> The repository you're creating it in is no good.
> 
>>> Do I need to upgrade the repos to use --stacked now?
> 
> Yes, specifically to format 1.6.  Since this would affect all your other
> branches, and be incompatible with older clients, we do not do this
> automatically.
> 
> It's also a bit strange to use --stacked if you already have a shared
> repo.  They're two different ways of accomplishing the same thing.
> 
> Aaron

At a minimum, I think it is strange that we are telling the user we are
upgrading the repository format, and then *not* using it because of the shared
repository. So we need to fix the UI output, and there is certainly a bug
here. I would guess it doesn't have to go into 1.7, though.

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

iD8DBQFIyAY5JdeBCYSNAAMRAmwWAJwLO6KZMn8V3SPkebjxOuWo6MuJMACfQi6R
VAxXgqFSCqv4/wuxSxq9rVE=
=YUsr
-----END PGP SIGNATURE-----