Ideally the BTS would have a better way (probably involving the version trees) to associate these bugs with source and or binary packages still in the archive. Where it couldn't do that the usual auto-archiving (but not closing since the package could be reintroduced) would be appropriate. This would also solve problems we currently have where all bugs are closed when a package is temporarily removed from the archive and need to be manually reopened when the package is reintroduced.
Until we live in an ideal world, people can and should triage these bugs to determine the appropriate package and location for them. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKTje6HOJ_9srTaGD0sd4JrfuEN9QVj0-eCGbc=UXjCa=60...@mail.gmail.com
