severity 487104 important
kthxbye

On Fri, Aug 15, 2008 at 05:12:43PM +0100, Jonathan H N Chin wrote:

> The problem causes data loss, so it is "grave" at minumum:

>     http://www.debian.org/Bugs/Developer#severities

> (At my site at least, the data loss is serious, as I explained in my
> previous message, but I grant that this may not be the case elsewhere.)

Please don't drop people from the CC list if you're going to make a
major change like this to the status of a bug.  The first time I found
out that this was upgraded to RC severity was when I noticed that my
closure message went to the release critical bugs list.

As previously discussed while I do think this should be fixed for lenny
I really don't think this is a severe enough problem to warrant removing
the package from the distribution; the definition of data loss is being
stretched a bit here (the data is still present and accessible via
interfaces other than ypcat) and the package continues to function well
in the overwhelming majority of use cases.

Like I say, I appreciate that this is something which is very important
in your system and do think this is something that should be fixed for
the next release but given the choice between having this bug and not
shipping at all it seems much more constructive to ship with the bug.

Incidentally, my testing also seemed to indicate that it was quite hard
to get a Debian system to generate UTF-8 data which had this problem - I
ended up using a hex editor to get the encoding that you had, other
encodings worked fine.

-- 
"You grabbed my hand and we fell into it, like a daydream - or a fever."



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to