Ticket #1026 (closed enhancement: fixed)
athena-auto-update needs a full rewrite
| Reported by: | jdreed | Owned by: | |
|---|---|---|---|
| Priority: | high | Milestone: | Precise Release |
| Component: | -- | Keywords: | |
| Cc: | Fixed in version: | debathena-auto-update 1.38 | |
| Upstream bug: |
Description (last modified by jdreed) (diff)
Given #1020, #1145, and #840, we need to re-write auto-update, because it's now full of hacks. The consensus is that we should switch to apt-get, which has better multi-arch support. But, we need to preserve the check for not removing metapackages. Perhaps this can be accomplished with apt-get -s?
OTOH, if we don't set autoremove (and it's not set by default), apt-get would only remove the actual metapackages, and not their dependencies, which is less catastrophic. So you'd have a functional machine, but machtype -L and possibly the greeter would yell at you.
Change History
comment:1 Changed 13 years ago by jdreed
- Description modified (diff)
- Summary changed from athena-auto-update sucks to athena-auto-update needs a full rewrite
comment:3 Changed 12 years ago by jdreed
I've actually gone ahead and committed this, since aptitude is also (on Precise, at least) chewing up CPU while it sits there spinning, and my inhibiting all pre and post hooks did not work.
comment:5 Changed 12 years ago by jdreed
- Status changed from committed to development
- Fixed in version set to debathena-auto-update 1.37
comment:6 Changed 12 years ago by jdreed
Thanks to VMware snapshotting, I just successfully used auto-update 1.37 to update a Natty machine from June. Nothing terrible happened.
comment:7 Changed 12 years ago by jdreed
- Status changed from development to proposed
- Fixed in version changed from debathena-auto-update 1.37 to debathena-auto-update 1.38
