Ubuntu Wiki

• Launchpad Entry: jaunty-cruftremover-improvements

• Created: MichaelVogt

• Contributors:

• Packages affected: update-manager, cruft-remover

Summary

This spec is about improvements to the cruft remover, most importantly sharing the quirks/anomalies fixup code between update-manager and cruft-remover.

Release Note

TBD

Rationale

Update-manager performs a cruft cleanup on upgrade, curft-remover is able to do this anytime. Currently they do not share the same code. This duplication of code should be unified.

Design

Both u-m and c-r need to perform two tasks:

• identify and cleanup cruft (obsolete packages, auto-removable packages etc)
• fix anomalies relative to a fresh install (missing relatime in /etc/fstab) and should share the code that performs those tasks.

There are some constrains in the release upgrader:

• must not hard depend on external python libraries (other than the stuff in ubuntu-minimal)
• must work on previous version/lts-version of the distro (intrepid,hardy)

The external dependencies can just be bundled inside the release upgrader so that is not a real problem (just something that makes it a bit more difficult). We should consider if we need some cruft/anomalies to be version specific (e.g. only if the current version in hardy). The release upgrades does that in a number of cases, but it could be argued that such checks are not required since a anomaly is a anomaly.

The cruft removal code in u-m needs to be able to be seeded with a blacklist (the list of packages obsolete before the upgrade and a explicit blacklist).

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

No UI changes needed.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release.

This need not be added or completed until the specification is nearing beta.

Unresolved issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.

CategorySpec