Am Donnerstag, den 19.05.2005, 10:56 +0200 schrieb Thomas Glanzmann: > lftp on my debian sarge boxes does no longer contain SSL support for > lftp as of this morning. Will that change or should I build my own lftp > packages from now on?
Please read:
# zless /usr/share/doc/lftp/changelog.Debian.gz
lftp (3.1.3-1) unstable; urgency=medium
* new upstream from 2005-04-15
* disabled ssl support because of license problem. See:
http://bugs.debian.org/305160
http://www.mail-archive.com/lftp%40uniyar.ac.ru/msg02012.html
http://www.openssl.org/support/faq.html#LEGAL2
http://www.gnome.org/~markmc/openssl-and-the-gpl.html
If the author add the needed exception to allow to link
against openssl it will be enabled again.
Better a lftp without ssl than no lftp in sarge.
(closes: Bug#305160)
-- NoÃl KÃthe <noel debian.org> Thu, 28 Apr 2005 18:11:59 +0200
Because of the Debian release freeze sarge will be released without ssl
because of this license problem.
Alexander implemented gnutls in lftp 3.2.0 to fix the GPL/SSL problem
but the sarge freeze doesn't allow new upstream versions with such big
changes.
To answer your question: yes if you need ssl you have to build it
yourself.
You can use coming 3.2.x packages but I had some build problems which
were solve yesterday by upstream.
--
NoÃl KÃthe <noel debian.org>
Debian GNU/Linux, www.debian.org
signature.asc
Description: This is a digitally signed message part
