severity 488219 wishlist done
I may not have had the time to give this package even close to the attention I should be giving it. But I dislike seeing fixes delayed for reasons like this. Zephaniah E. Hull. On Sat, Jun 28, 2008 at 08:31:07AM +0200, Andreas Metzler wrote: > On 2008-06-27 Mario 'BitKoenig' Holbe <[EMAIL PROTECTED]> wrote: > > On Fri, Jun 27, 2008 at 07:57:46PM +0200, Andreas Metzler wrote: > >> (currently shipped in package lynx-cur) the only thing to "fix" this > >> bug is to stop providing lynx-ssl. > > > Yes. > > >> Why should this bug be severity "serious"? > > > Because the package claims things it cannot hold. It's just as formal as > > stopping to build against OpenSSL(wrapper). However, it's easy to fix, > > so this should not be a big issue at all. > > Hello, > Sorry, looks like my question was to unspecific. We have got rather > clear guidelines what makes a bug serious: > > http://www.debian.org/Bugs/Developer.en.html#severities > serious > is a severe violation of Debian policy (roughly, it violates a must > or required directive), or, in the package maintainer's or release > manager's opinion, makes the package unsuitable for release. > > http://release.debian.org/lenny/rc_policy.txt > > Afaict this bug does not match either of them. > > I care about this because stopping linkage against gnutls OpenSSL > compat layer really fixed a serious bug in the packages, and this fix > needs to propagate to testing. "Your" bug prevents this or is going to > delay the propagation for at least another week. So I would appreciate > if you could either back up the severity claim or downgrade the bug. > > thanks for considering, cu andreas > -- > `What a good friend you are to him, Dr. Maturin. His other friends are > so grateful to you.' > `I sew his ears on from time to time, sure' > > -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
