-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/17/2011 03:55 PM, Brendan Donegan wrote: > Hi Marc, > > Do you have some steps for getting a repository into this state from > scratch? Would be handy for reproducing the problem. So far I can't seem > to. > > Thanks,
I'm pretty sure the issue is that the URL canonicalization changed. If you try doing "bzr info" I think you'll see that a URL might have "~" and another has "%2E". Or something along those lines. Just doing "bzr bind lp:..." should fix the master branch to match the update branch, and then it won't block anymore. This is also a dupe, but I don't know the other bug number. John =:-> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk37Xz8ACgkQJdeBCYSNAAMJ/ACdG3eLVeSfuPm5TgfX8h/RK/Vw XyQAnAgDiVDCYyfnUQvCGgezKh5gmRW1 =WINC -----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/798688 Title: possible regression in natty-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/798688/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
