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)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876298 Title: [MASTER] We need to better handle external payloads (Flash, msttcorefonts) not being available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/876298/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
