Merge lp:~mwhudson/ubuntu-archive-scripts/find-rcbuggy-problem-packages into lp:ubuntu-archive-scripts
Status: | Merged |
---|---|
Merged at revision: | 239 |
Proposed branch: | lp:~mwhudson/ubuntu-archive-scripts/find-rcbuggy-problem-packages |
Merge into: | lp:ubuntu-archive-scripts |
Diff against target: |
358 lines (+340/-0) 3 files modified
find-rcbuggy-problem-packages (+244/-0) run-proposed-migration (+6/-0) templates/rcbuggy-problem-packages.html (+90/-0) |
To merge this branch: | bzr merge lp:~mwhudson/ubuntu-archive-scripts/find-rcbuggy-problem-packages |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ubuntu Package Archive Administrators | Pending | ||
Review via email:
|
Commit message
Generate a report of packages that have been removed from testing whose removal from Ubuntu would aid other packages though proposed migration.
Description of the change
This branch implements this idea:
Packages that have been removed from Debian testing should not automatically be removed from Ubuntu devel, because a package may be buggy in Debian but not in Ubuntu (or vice-versa). However, packages that have been removed from Debian testing for bugs, and which are also blocking things in the proposed-migration queue, are candidates for fast-tracking for removal from devel + devel-proposed.
Currently we waste too much time identifying packages in this category.
Create a report that shows packages that are in this situation, so that they can be more quickly identified. Report should provide recommended commands for their removal. Iterate until the report is correct and a simple button-pushing exercise for the archive admins, then automate.
Should be added to lp:ubuntu-archive-scripts
Example of a package removed from testing that we then manually removed from devel:
https:/
The output looks like this fwiw: https:/ /paste. ubuntu. com/p/6NC4VPMJT w/