[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

How should this issue be handled, should it be taken to the Technical Ctte?



I do not feel bug #181126 is being handled properly by the maintainer at
all. To make a short story even shorter: I have filed a bug on initrd-tools
since I believe there is room for improvements based on a slight review of
RedHat's mkinitrd package, so I ask the maintainer to check it out and see
if it's worth using instead of initrd-tools' mkinitrd.

An opening/closing/reopening/closing/reopening/closing sequence
ends with:

Hebert Xu wrote: 
> On Sat, Feb 15, 2003 at 07:48:02PM -0600, Debian Bug Tracking System wrote:
>> Processing commands for control@bugs.debian.org:
>>
>> > reopen 181126
>> Bug#181126: initrd-tools: Consider merging or using RedHat's mkinitrd
>> Bug reopened, originator not changed.
>
>The Developer's Reference is not the bible.

This is said in response to me asking him to not close the bug (again) but
tag it wontfix if the doesn't want to take care of it (since that is what 
the Developer's Reference asks maintainers to do for in this situations
in which the bug submitter believes its a bug but the maintainer does not). 

I do not want to get in another flame ware here, but I believe that the way
Herbert is acting is not at all reasonable. Then again, I might be wrong. 
So I would like to ask fellow DDs: is this a proper way to handle a bug?
What should the bug submitter (me) do in this case, just for the record.


	Javi

PS: Please don't start discussing the fact it might or might not be a
reasonable bug, Herbert hasn't done it (he closed it outright without any
explanation on the technical issue at hand).

Attachment: pgpK__xAlDeJ_.pgp
Description: PGP signature


Reply to: