Custom Query (1145 matches)
Results (298 - 300 of 1145)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #406 | fixed | athena-auto-update does not retry configuring unconfigured packages | geofft | |
| Description |
athena-auto-update checks aptitude --simulate --assume-yes full-upgrade for the string "0 packages upgraded, 0 newly installed, 0 to remove", and assumes that means that there's nothing to do. This fails to check for the string "The following partially installed packages will be configured:", which often occurs when everything's installed but there are unconfigured things. Importantly, this can cause machines to fall out of -cluster or -workstation if there's a transient upgrade problem that could be fixed with aptitude install by hand. |
|||
| #407 | fixed | athena-auto-update should dpkg --configure -a | jdreed | geofft |
| Description |
A handful of machines in clusters have stopped updating with E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. E: Couldn't rebuild package cache update.log is missing a record of the last upgrade finishing, indicating the system was probably rebooted. I reported this as a theoretical bug five months ago in comment:ticket:217:1 after running into it on my -cluster laptop; as I predicted, it's happening in practice. |
|||
| #408 | wontfix | athena-auto-update should deal with upstream's anjuta/libgbf fail | geofft | |
| Description |
Ubuntu released a version of the anjuta package that is supposed to Conflict with libgbf-1-2, for it replaces a file in that package, but doesn't. This was previously inhibiting upgrades on ozok, and is currently inhibiting upgrades on m66-080-4; we should add code to athena-auto-update to work around this. cf. LP:338464 |
|||
