As an aside, the Opinion status is for when there's a dispute as to whether the issue is actually a bug. It is treated as a closed bug in launchpad, making it not show up in the default bug listing for a project.
In discussing it with the security team, something like this would probably be reasonable. I assume the QRT-Deprecated flag would take a release version in which the test became deprecated? We may have a weird issue where for some reason a package gets removed for a release or more and then comes back into the archive; netbeans is an example of a package doing this, though we don't have a test script for it.
Hi Max,
As an aside, the Opinion status is for when there's a dispute as to whether the issue is actually a bug. It is treated as a closed bug in launchpad, making it not show up in the default bug listing for a project.
In discussing it with the security team, something like this would probably be reasonable. I assume the QRT-Deprecated flag would take a release version in which the test became deprecated? We may have a weird issue where for some reason a package gets removed for a release or more and then comes back into the archive; netbeans is an example of a package doing this, though we don't have a test script for it.
Thanks!