© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Re comment #6:
"I wonder if it could be a bug related to the crash reporting software instead. What looks strange (but maybe I'm not reading it correctly) is that the publishing history indicates it was brought back to 0% even before it was put at 10% : https:/
It seems to me it should at least collect some data before phasing out, so maybe the bug is somewhere else or it has been blocked manually..."
The phased-updater, which sets the phased-update percentage, currently runs every 6 hours and does not consider how the long the package has been in -updates. I've submitted an MP fixing this now so that there will be an opportunity for more data to be collected. Thanks for discovering this!