Comment 23 for bug 876298
Revision history for this message
| Michael Vogt (mvo) wrote Re: [MASTER] We need to better handle external payloads (Flash, msttcorefonts) not being available. | #23 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
The update-alternatives warning was mostly a precaution measure as I'm not sure if that is doing proper locking. If it does thats fine, but there is a race otherwise that a package may call it on something when the cron job runs and tries to modify it too. If that is a non-issue even better :)
About the failed downloads> Without knowing the implementation (yet) I would assume we define states like:
needs-downloading, fetched, failed-permanently
and a way to list the state of the current queue for the user. The failed-permanently one is tricky as it may be that its
a system that is very rarely connected to the net (so ifup-down integration would be good) so a fixed number of days
is not ideal (if the system goes online only every week). But at the same time daily retries on a resource that is no longer
available forever is equally bad. So maybe a combination of both? Say 14 days or 10 retries (when there was a working
network connect)?