maximilian attems wrote: > On Fri, May 16, 2008 at 04:39:58PM +0000, Debian Bug Tracking System > wrote: > > Processing commands for [EMAIL PROTECTED]: > > > > > found 242866 2.6.24-6 > > Bug#242866: drivers containing firmware blobs > > Bug#243022: ymfpci_image.h: Sourceless microcode without permission > > to redistribute Bug#383403: linux-2.6: includes nondistributable > > and non-free binary firmware Bug#412950: linux-2.6: [legal] the > > current kernel tarball doesn't respect the GR 2006-007 Bug marked > > as found in version 2.6.24-6 and reopened. > > > > > found 242866 2.6.25-3 > > Bug#242866: drivers containing firmware blobs > > Bug#243022: ymfpci_image.h: Sourceless microcode without permission > > to redistribute Bug#383403: linux-2.6: includes nondistributable > > and non-free binary firmware Bug#412950: linux-2.6: [legal] the > > current kernel tarball doesn't respect the GR 2006-007 Bug marked > > as found in version 2.6.25-3. > > > > > thanks > > Stopping processing here. > > stop this game or i get you blacklisted on debian bug tracking system.
I do not like such threats when I havn't done anything wrong (according to my knowledge). I was acting exactly as you requested. IMHO you said that reopening should be done only by maintainer or by someone with info that bug had not been dealt with. I'm not a maintainer, but I did have info that bug had not been dealt with, so I reopened the bug with that info. I fail to see any reason to threaten me with blacklisting. IMHO it is you who should've been threatened with blacklisting if anyone, since you have insisted on closing bugs which clearly havn't been fixed. If I did something wrong, IMHO the right response would've been to point out my mistake to me, and not to threaten with blacklisting without giving any reason for it. > it is up to the maintainer to decide if that is closed or not. If maintainer decides that bug must not be reopened anymore, that should be mentioned in the bug-report. -- Markus Laire -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
