On Fri, 19 Dec 2008, Sven Joachim wrote: > There are several packages in Debian that come in different flavors > (GCC, Python, Emacs), and if an old flavor is removed the bugs need > to be examined and reassigned to a newer flavor if necessary, rather > than being closed automatically.
These bugs should actually be cloned and assigned to all of the affected packages at the time they're filed (or the new package(s) come into existance) rather than at the time the old package is removed. Furthermore, the number of packages that do this kind of multi-flavor thing is fairly small, and the automatic closure and even archiving doesn't make the examination and reassignment of these bugs much more difficult. [It would even be reasonable to have a usertag or possibly a tag that tracked bugs closed in this manner to assist maintainers of multiflavor packages who had gotten behind.] > The same reasoning applies whenever a library changes its soname. The only time this would matter is if the source package name changes; that shouldn't happen in the case of library soname changes. [The only exception is the few libraries for which we maintain different APIs, but in this case, it's the API version, not the soname.] (In case it wasn't clear, the automatic closure procedure should only affect source package removals, not binary package removals.) Don Armstrong -- It seems intuitively obvious to me, which means that it might be wrong -- Chris Torek http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
