© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
As doko (thx!) suggested, a simple rebuild with newer pycentral solves this. I'm subscribing motu-sru to request a go-ahead to fix this for the stable release:
1. Users upgrading to hardy will fail upgrade due to plucker failure to upgrade.
2. This is simply due to the package not having been rebuild with latest pycentral. The package in the development release has been rebuilt with last pycentral.
3. A minimal patch is attached.
4. TEST CASE: Install the gutsy (or dapper) version of the package (ie. 1.8-21ubuntu1). Upgrading to the hardy version (1.8-24) will fail. Upgrading to the hardy-proposed version (1.8-24build0.1) will succeed.
5. Its a simple rebuild, so no regression potential of the patch is foreseen. If no updates to the intrepid package will be made, users upgrading to intrepid will also be unaffected (intrepid version (1.8-24build1) is > hardy version (1.8-24build0.1) so the package will be upgraded successfully).