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
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
Package: lynx
Version: 2.8.6-2.1
Severity: serious
Hello,
with 2.8.6-2.1 lynx stopped linking against a SSL library and thus lynx
complains when it is requested to open a https:// URL:
Alert!: This client does not contain support for HTTPS URLs.
However, the package still claims to
On Fri, Jun 27, 2008 at 09:40:13AM +0200, Mario 'BitKoenig' Holbe wrote:
Package: lynx
Version: 2.8.6-2.1
Severity: serious
Hello,
with 2.8.6-2.1 lynx stopped linking against a SSL library and thus lynx
complains when it is requested to open a https:// URL:
Alert!: This client
On 2008-06-27 Mario 'BitKoenig' Holbe [EMAIL PROTECTED] wrote:
Package: lynx
Version: 2.8.6-2.1
Severity: serious
Hello,
with 2.8.6-2.1 lynx stopped linking against a SSL library and thus lynx
complains when it is requested to open a https:// URL:
Alert!: This client does not
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
6 matches
Mail list logo
