expire_archive_files.py doesn't expire enough cruft
Bug #844945 reported by
Julian Edwards
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug Description
It currently expires files for sources and binaries that were superseded or deleted. It should also expire files for obsoleted publications, at least for Ubuntu, as the files are moved to old-releases.
In addition, we need to expire files for rejected PackageUploads.
(any more William?)
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: tech-debt |
Changed in launchpad: | |
assignee: | nobody → William Grant (wgrant) |
status: | Triaged → In Progress |
Changed in launchpad: | |
assignee: | William Grant (wgrant) → nobody |
status: | In Progress → Triaged |
To post a comment you must log in.
Here are notes I had:
* Find all unexpired BPRs.
* Remove any where datecreated > (now - stay of execution)
* Remove any from a build which is referenced by a PackageUpload that
is not DONE or REJECTED.
* Remove any with publications where any of these hold:
+ dateremoved is NULL
+ dateremoved > (now - stay of execution)
+ archive is private
+ archive is a PPA and blacklisted
+ archive is primary and any of these hold:
- series is not expirable
(expirable series are currently: warty, hoary, breezy, dapper,
edgy, feisty, gutsy, intrepid, jaunty)
- status is PUBLISHED or OBSOLETE (the final packages in a
release are kept forever)
* Expire all BPRs that remain.
What about copy archives? They are not published, so their
PackageUploads never leave ACCEPTED. We probably want a separate thing
to reject them, making them eligible for expiration?