-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 8/9/2011 10:57 AM, Scott Moser wrote: > On Fri, 5 Aug 2011, John A Meinel wrote: > >> 3) Because of the ^C and re-push, the branch did not end up stacked >> on the development focus: >> http://bazaar.launchpad.net/~ubuntu-on-ec2/live-build/cloud-images/.bzr/branch/branch.conf >> >> (there should be a 'stacked_on_location' there.) > > There was no control-C . At least, if I reported that there was, I > am uncertain of that. Instead, the initial push just fails with the > message above. > > So at very least there is a bug there. >
Your initial push doesn't say anything about failing, just taking a while. Your symptoms match the case when a bzr meta-directory exists, but the branch directory does not. (a .bzr/ dir exists, but .bzr/branch/ is missing.) That can happen if someone starts pushing to a branch and interrupts it. The *next* push would show the symptoms you describe. (it would fail to notice that the branch should be stacked, so create a complete new copy of the history in the target location.) John =:-> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5BKzkACgkQJdeBCYSNAAPaMwCgmeyZz95O+/FFsGswMZbwVb2/ 35cAn3n88lBJfjKdfsRUxxFTGspUEW5N =0BgU -----END PGP SIGNATURE----- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/818138 Title: branch not stacked if first push is interrupted To manage notifications about this bug go to: https://bugs.launchpad.net/bzr/+bug/818138/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
