© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Well, if the fix was supposed to solve the unpropagated tags, I am sorry to report that it still affects my 2.3.0 I am using on my systems...
I know for a fact it used to work a few versions ago (I have a tag I know a did on 14/07/2010 that has propagated to the "central repository" via merge from a branch into a checkout + commit (binded to the bzr smart server url). Not really sure what stable release was then, but I am on a Lucid, which I believe it already was back then (at least, up-to-date every week)
Is there any tests I can try? Log files to send? May a plugin be affecting my systems? Must I rebuild my repository from scratch for the fix to work? (I hope not) Is there a new META format for a repository upgrade that could mitigate the behavior? Must I get my bzr from a PPA instead?