[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

Axel Beckert abe at debian.org
Sat Jan 23 19:17:58 UTC 2016


Hi,

JFYI: I've already filed a bug for lynx and lynx-cur both FTBFS
against GnuTLS 3.4.x.

I've made up the following patch and will pushed it to the
renaming-back branch:

https://anonscm.debian.org/cgit/pkg-lynx/lynx.git/commit/?h=renaming-back

Debian's host at UBC are currently down due to local maintenance and I
assume that my bug report hasn't been recorded yet because of that.
Wrote it a few hours ago.

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!)

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.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe at debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



More information about the pkg-lynx-maint mailing list