Need a script to compare launchpad 'superseded' packages with official releases
Bug #1021050 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Most of the infrastructure to delete librarian files that are 'waste' is already in place.
The primary friction that we have today, is that Colin Watson has requested that we don't delete any packages from the point at which an official .0 release has been cut. (So the package that is in maverick-10.10.10.0 should stay around, even if it has a rev superseding it as 10.10.10.1, etc.)
Colin says the requirement comes from groups like OEM that end up needing what should otherwise be an EOL series.
For cleaning up Karmic, we dumped the list of filenames to delete, and he ran a script to compare this to the official snapshot from http://
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
To post a comment you must log in.
In talking with Colin more, he doesn't want us to automate the full deletion, however, there are 2 places that we still want better Launchpad support.
1) Generating the list of files to be deleted. Essentially an supported script (or API or web page) that can generate the list of files that Launchpad feels is safe to delete. Something that can be dumped into a text file for futher validation by a person.
2) Rather than running SQL to actually mark the files obsoleted, a script that can have tests for it in the Launchpad suite, so that if someone changes one of the tables, the script can get updated right away, rather than debugging much later.