Call for testing of colocated branch support in bzr.dev

[John Arbash Meinel]

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

...

>> I'm pretty sure it is a known bug that an interrupted push
>> creates a .bzr directory, but no branch, such that a second push
>> creates a full branch without stacking.
> 
> Yes, there is that bug, but I'm pretty sure that's not what I'm
> hitting here.
> 
> My bug is:
> 
> 1- bzr init LP_URL   # no interruption or error 2-
> b.get_stacked_on_url() --> None, but it should be the trunk
> 

Confirmed.

$ bzr init lp:~jameinel/bzr/my-special-test
Using default stacking branch /+branch-id/241735 at
bzr+ssh://bazaar.launchpad.net/~jameinel/bzr/
Created a standalone branch (format: unnamed)

$ wget
http://bazaar.launchpad.net/~jameinel/bzr/my-special-test/.bzr/branch.conf

Empty file

Contrasted with

$ bzr push lp:~jameinel/bzr/my-test-2
Created new stacked branch referring to /+branch-id/241735.
$ wget
http://bazaar.launchpad.net/~jameinel/bzr/my-test-2/.bzr/branch/branch.conf
stacked_on_location = /+branch-id/241735
parent_location = ../../../%2Bbranch/bzr/


Note that the messages are different. And IMO, is part of the issue
with having multiple ways of creating stuff. (vs always running the
same init code, and then fetching into it as orthogonal steps.)

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

iEYEARECAAYFAk9C0bAACgkQJdeBCYSNAAOTbwCfTalSFlKQ1u9BBUpxgD5KlMEF
vKUAn0ednQ08E6oDxRetc+hoFAaijFIt
=ILXy
-----END PGP SIGNATURE-----