On Fri, 19 Dec 2008, Paul Wise wrote: > Though it might be better for dak to send a package removal/addition > notification to the bts and have the bts take the appropriate action > rather than doing it all in dak. Seems more 'correct' to have dak > close/reopen the bugs via an interface. This way the bts could have > a field 'closed-due-to-removal' (or similar) so that only bugs > closed by removal are reopened if the package is reintroduced.
They won't get reopened, but they will be marked as affecting unstable/testing, etc. so all of that is ok. [And they won't be archived as long as the bug affects testing or unstable or the package is in Debian.] There's really nothing special about bugs that are closed by removal and bugs that are closed, archived and then later end up affecting a package again. Don Armstrong -- Your village called. They want their idiot back. -- xkcd http://xkcd.com/c23.html http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
