[pkg-lynx-maint] lynx and lynx-cur both FTBFS with GnuTLS 3.4.x (bug report sent, but not yet recorded) -> Upload of src:lynx to unstable ahead

[Andreas Metzler]

On 2016-01-23 Axel Beckert <abe at debian.org> wrote:
[...]
> I intend to upload src:lynx with the exchanged lynx and lynx-cur
> packages as well as the added lynx-common package to unstable soon. As
> far as I remember, only Andreas wasn't happy with the lynx-common
> packages and most other team members were in favour of it. (Andreas: I
> hope that won't make you quit the team since I value your SSL
> knowledge a lot!)

No worries.

> When choosing the version number for the experimental upload I didn't
> take into account that we might need another src:lynx-cur bug fix
> upload. And uploading an lynx-cur/2.8.9dev8-2 will probably fail
> because the resulting binary packages already exist in the archive,
> built from the src:lynx package of that version.

Is there a specific raason for not uploading lynx (i.e. the package
gone through NEW) to unstable?

BTW, thanks for taling care og GnuTLSFTBFS.

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'