Bug#493583: Display bugs that affect this package even when assigned to another
Package: bugs.debian.org Severity: wishlist It would be really neat if you could designate that a bug that is assigned to another package, affects this one. It's quite common as a maintainer to assign bugs to another package especially libraries but visitors to your package's bugs page then won't know about the other bug and may file duplicates/be confused. A solution to this is to have new functionality that declares that a bug affects a certain package. I guess I see it working something like: * Have a command that lets you say that this bug affects this package and gives a short description of how with a severity e.g. affects 123456 baz serious baz is currently broken by the new upload of libfoobar which fails to include /usr/lib/libfoobar* * Store these somehow. I imagine it's easy to store in the buglog for the particular bug but you would also want a per-package-it-affects index so that you can... * Display them. Have the web interface trawl the per-package-it-affects index for itself/its source package name and display the severity and reason with a link to the bugs on other packages that affect this one. * Update the storage When a bug is closed it should be removed from the per-package-it-affects index. Optionally you could notify people on the [EMAIL PROTECTED] alias that you had done so. I included the severity to give a human indication of how bad it is but also because you could potentially feed things back into testing migration. I see the severity being the severity this bug has for the affected package not necessary the same as that of the bug that has been reassigned. I was thinking about this today because of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493407 and its effect on netbase but in general lots of the xfce stuff is based on common libraries (e.g. libvte, libxine etc) and it'd be nice to keep track of those bugs on the index page for our packages in the BTS. It is similar in concept to blocks but not the same. I wouldn't file a bug on netbase about that issue and if I did I'd expect it to get merged to the existing bug on lsb. This encourages more users to file more bugs and then they all get merged onto a package noone is looking at when reporting the bug. Currently a maintainer could file a placeholder bug on a package and set it blocking on the other bug and then manually close it at the same time the other one gets closed but that seems like a lot of work that the BTS could just do for us. Anyway, hope this makes some sense. Simon. -- But Granny had spent a lifetime bending recalcitrant creatures to her bidding and, while Esk was a surprisingly strong opponent, it was obvious that she would give in before the end of the paragraph. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493583: Display bugs that affect this package even when assigned to another
reassign 493583 debbugs thanks On Sun, 03 Aug 2008, Simon Huggins wrote: It would be really neat if you could designate that a bug that is assigned to another package, affects this one. The right way to do this is to file a bug against this package, which explains what the problem is, which is blocked by the bug against the other package. * Update the storage When a bug is closed it should be removed from the per-package-it-affects index. Optionally you could notify people on the [EMAIL PROTECTED] alias that you had done so. This is the only thing that blocking bugs currently do not do. There is some argument that we should allow a feature to allow specific bugs to be automatically closed when a blocker is closed, but that's not something that we do currently. Don Armstrong -- Leukocyte... I am your father. -- R. Stevens http://www.dieselsweeties.com/archive.php?s=1546 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493583: Display bugs that affect this package even when assigned to another
On Sun, Aug 03, 2008 at 04:46:35AM -0700, Don Armstrong wrote: On Sun, 03 Aug 2008, Simon Huggins wrote: It would be really neat if you could designate that a bug that is assigned to another package, affects this one. The right way to do this is to file a bug against this package, which explains what the problem is, which is blocked by the bug against the other package. This is incredibly clumsy though. That means that for every bug you reassign to a library, ideally you would: * file another bug * explain the problem fully in the other bug (potentially you just clone the first bug to the other package but you would need to add more explanation in either case) * set the second bug to be blocked by the first bug you've reassigned. * manually track when the first bug goes away and close the second bug. * Update the storage When a bug is closed it should be removed from the per-package-it-affects index. Optionally you could notify people on the [EMAIL PROTECTED] alias that you had done so. This is the only thing that blocking bugs currently do not do. There is some argument that we should allow a feature to allow specific bugs to be automatically closed when a blocker is closed, but that's not something that we do currently. You also don't get the severity of the bug on the dependent package. I think to be honest, whilst technically you can do some of this by being fastidious with blockers, this is a sane feature request that would make the lives of Debian developers and other users of the BTS easier. Simon. -- oOoOo - You have saved our lives. We are eternally grateful.oOoOo oOoOo- Yeah, yeah, yeah whatever.oOoOo oOoOo oOoOo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
