In the past couple of weeks I’ve been writing a needs-packaging bug reviewer that creates a report regarding possible actions for bugs tagged needs-packaging. I’ve gone through quite a few of these myself and tagged them as ‘auto-search’ if the report led me to act on the bug.

The script looks at bugs without a package that are tagged needs-packaging and parses the bug’s title, ‘[needs-packaging] software …’, extracting the first word after ‘[needs-packaging]’. This word is then searched for using rmadison (for Ubuntu and Debian) and Debian wnpp (Work-Needing and Prospective Package) bug reports. The searches used and possible actions follow:

1) Search – ‘rmadison software’ – Ubuntu’s repositories are searched for a package name matching software. Action to take – In the event that the software is the same as the one described in the bug report the bug should be closed as “Fix Released” and information given about in which release of Ubuntu the software can be found.

2) Search – ‘rmadison -u debian software’ – Debian’s repositories are searched for a package name matching software. Action to take – In the event the software is the same as the one described in the bug report the bug should become a sync request, or a new bug submitted using the sync request format. Generally speaking, the package will be available in the next release of Ubuntu when packages are synced with Debian.

3) Search – Debian ITP (intent to package) bug reports are searched. Action to take – In the event a match for the same piece of software is found an upstream bug watch for the particular Debian bug should be added. This will inform potential packagers that Debian is also looking for this software so they could try and have the package also included in Debian.

4) Search – Debian requested package bug reports are searched. Action to take – In the event a match for the same piece of software is found an upstream bug watch for the particular Debian bug should be added. This will inform potential packagers that Debian is also looking for this software so they could try and have the package also included in Debian.

Additionally, in the event that there is not a clear package name for a piece of software – like ‘[needs-packaging] Ruby Nmap::Parser Library’ it is possible to tag the bug as ‘np-reviewed’. The script will ignore any bugs with that tag. While you are welcome to run this report locally I’ve setup a cronjob on people.ubuntu.com to run it weekly. In the event that you do take any actions on needs-packaging bugs because of the hints provided by this report please tag them as ‘auto-search’.