Hello, lftp was removed from sarge because of #305160 "linked against libssl". I uploaded a ssl disabled version (3.1.3-1) to get it fixed because upstream will not add the needed GPL/openssl exeption: http://www.mail-archive.com/lftp%40uniyar.ac.ru/msg02022.html Debian package changelog: 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) Its a new upstream version with the follow changelog: some bugs fixed. * added mirror --loop option to re-mirror until no changes found. * fixed mirror creating too many children mirrors. * fixed cls and mirror with http backend, when PROPFIND returns 404 error. * fixed mirror --use-cache with sftp backend. * fixed a rare hang in sftp. It should have make it into sarge but the arm and sparc built packages weren't uploaded (but built: http://buildd.debian.org/build.php?pkg=lftp) and this missed the yesterday freeze status. Now I have the following question to this status: - Will you hint the lftp 3.1.3-1 package when the missing archs will be there (ssl disabled and upstream minor fixes)? - If not will you allow 3.1.2-2 (same as 3.1.2-1 but ssl disabled)? Thanks. -- Noèl Köthe <noel debian.org> Debian GNU/Linux, www.debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part