Custom Query (1145 matches)
Results (97 - 99 of 1145)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #832 | fixed | auto-updater should conditionally display progress on stdout | jdreed | |
| Description |
There are times (recovery mode, for example) where running athena-auto-update from the terminal is desirable. If there are a ton of updates, it can take a while and look like nothing is happening (because the output is going to a log). We should conditionally (either conditionalize on the "cron" argument, or take a "-v" argument or something) display output on stdout. The case could be made for a progress bar, or all output, or even to _not_ log to the normal place, since that should always be the log from the automatic invocation. |
|||
| #543 | fixed | auto-updater should resolve conffile conflicts on -workstation | jdreed | |
| Description |
This was originally the second half of #483: Right now, if anything triggers a dpkg conffile conflict, auto-update will hang indefinitely. Cluster machines invoke apttiude with "-o Dpkg::Options::=--force-confnew" On not-cluster machines, it's less clear. It sounds like Athena 9 used rpm's default behavior, which was the equivalent of --force-confold. I think ideally the update should fail and e-mail root (which may or may not go anywhere useful), leaving them to fix the upgrade, but I don't know if there's a way to make dpkg error out on conffile conflicts. |
|||
| #987 | fixed | auto-update's check for metapackages being removed results in false positive on natty | jdreed | |
| Description |
Some natty machines have suddenly started logging that metapackages would be removed, even when they clearly won't be. |
|||
