Below I have included the text rejecting my httperf package. I am taking over as maintainer and uploaded a new version that also closed a couple of bugs and moved it from non-US to main. If linking with libssl is not permissible, should the version that is currently in Sarge be slated for removal when 3.1r1 comes out? If so, what do I need to do ensure that it happens?
Also, I have emailed the upstream author and asked for him to relicense or add an exception for linking to OpenSSL. If that happens, then what happens to the version in Sarge? Does it need updating in 3.1r1 so the the new license becomes part of the package in Sarge? -Roberto ----- Forwarded message from Joerg Jaspert <[EMAIL PROTECTED]> ----- From: Joerg Jaspert <[EMAIL PROTECTED]> To: "Roberto C. Sanchez" <[EMAIL PROTECTED]> Cc: Debian Installer <[EMAIL PROTECTED]> Subject: httperf_0.8-3_i386.changes REJECTED X-Katie: lisa $Revision: 1.30 $ Hi Maintainer, while looking at your package in NEW I discovered that it is linking against openssl, itself beeing GPL licensed. Sorry, but this doesnt work, the OpenSSL license and the GPL are incompatible. For more information, and a link to give to your upstream please visit http://www.openssl.org/support/faq.html#LEGAL2 or/and http://www.gnome.org/~markmc/openssl-and-the-gpl.html After this is fixed feel free to upload your package again. -- bye Joerg === If you don't understand why your files were rejected, or if the override file requires editing, reply to this email. ----- End forwarded message ----- -- Roberto C. Sanchez http://familiasanchez.net/~sanchezr
pgpwa1gjuQj1p.pgp
Description: PGP signature
