On 2008-01-04 Atsuhito Kohda <[EMAIL PROTECTED]> wrote: [...] > I'm very puzzled at present but I'd like to know how I can > fix the bug in a decent manner.
> Is there anyone who can enlighten me? Hello, the situation seems to be rather simple: Currently we have two versions of lynx in unstable. Debian-Security is not very happy about this. On top of that upstream tells us that the version shipped in the package "lynx" is outdated and that only lynx-cur should be shipped: ------------------------------------------------ | From: Thomas Dickey <[EMAIL PROTECTED]> | To: Moritz Muehlenhoff <[EMAIL PROTECTED]> | Cc: Atsuhito Kohda <[EMAIL PROTECTED]>, [EMAIL PROTECTED] | Subject: Re: Bug#369386: #369386 Separate lynx-cur package should probably | not be included in Etch | Date: Tue, 30 May 2006 05:58:17 -0400 (EDT) | | On Tue, 30 May 2006, Moritz Muehlenhoff wrote: | [...] | > The problem, is that two versions of lynx are about to be included in | > Etch, which doubles the work load for fixing security issues in lynx. | > Almost every package in Debian has an unstable developer version, yet | > only very few are packaged separately. I'd like to know why lynx needs | > special treatment and why an unstable developer version needs to be | > included in a stable release. | | The so-called stable version is the one to drop, then, since it hsn't been | recommended for more than a year. ------------------------------------------------ So we should not have a package lynx-cur in sid, and the package lynx should be at version 2.8.7dev.8. You'll need to arrange between you two how to get this done. 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]
