On Thu, Feb 01, 2018 at 09:42:13PM +0100, Ansgar Burchardt wrote:
> peter green writes:
> >> If you do reintroduce it, please note the extra steps (reopening bugs
> >> in particular)
> > On that note one thing that doesn't seem to be easy/well documented is
> > how to go about finding the bugs that affected a package at the time
> > of it's removal. If I go to the bugs page for the package and select
> > "archived and unarchived" I see a bunch of resolved bugs but other
> > than opening them up individually I don't see a good way to tell the
> > difference between ones that were actually fixed and ones that were
> > open at the time of the removal.
>
> dak logs which bug reports is closed when a source package was removed:
> see the "Also-Bugs" field in https://ftp-master.debian.org/removals.822
> (for the current year; removals-YYYY.822 or removals-full.822 are also
> available).
Also, bugs cloed by dak rm are closed with a version of 1.2.3-1+rm (with
1.2.3-1 the version of the source removed, I believe the highest when
multiple versions of the same source were removed at the same time). So
you query for bugs closed with a version containing '+rm'.
This is documented in devref.
DAK removal logs are usually more parsable, of course. :)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Attachment:
signature.asc
Description: PGP signature