RFS: ncrypt
Dear mentors, I am looking for a sponsor for my package ncrypt. * Package name: ncrypt Version : 0.6.4-1 Upstream Author : Tachyon Technologies Pvt. Ltd. * URL : http://tachyon.in/ncrypt/ * License : MIT Section : python It builds these binary packages: python-ncrypt - Python wrapper for OpenSSL The package appears to be lintian clean. The upload would fix these bugs: 528358, 614051 My motivation for maintaining this package is: Dropbox, another package which I plan to upload, depends on this package. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/n/ncrypt - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/n/ncrypt/ncrypt_0.6.4-1.dsc I would be glad if someone uploaded this package for me. Kind regards Vincent Cheng
Re: RFS: ncrypt
Hi! * Vincent Cheng vincentc1...@gmail.com [110219 12:50]: * Package name: ncrypt [..] python-ncrypt - Python wrapper for OpenSSL [..] My motivation for maintaining this package is: Dropbox, another package which I plan to upload, depends on this package. Uhm... AFAIK dropbox used some lgpl libraries, and now we add openssl stuff? Did anyone checked, if that's okay license wise? Best Regards, Alexander -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110219150340.gp11...@melusine.alphascorpii.net
Re: RFS: ncrypt
In 20110219150340.gp11...@melusine.alphascorpii.net, Alexander Reichle- Schmehl wrote: python-ncrypt - Python wrapper for OpenSSL [..] My motivation for maintaining this package is: Dropbox, another package which I plan to upload, depends on this package. Uhm... AFAIK dropbox used some lgpl libraries, and now we add openssl stuff? Did anyone checked, if that's okay license wise? LGPL + OpenSSL should be fine. It's GPL + OpenSSL that is a problem, since GPL required the combined work be available under the terms of the GPL and those are incompatible with one or two clauses in the OpenSSL license. LGPL makes fewer requirements on the programs that link with it with can be satisfied at the same time as the OpenSSL license. Basically, you have to take the minimum steps to allow your software to be linked against a compatible version of the LGPL code. NB: IANADD; TINASOODP. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: RFS: ncrypt
On Sat, Feb 19, 2011 at 10:09 AM, Boyd Stephen Smith Jr. b...@iguanasuicide.net wrote: In 20110219150340.gp11...@melusine.alphascorpii.net, Alexander Reichle- Schmehl wrote: python-ncrypt - Python wrapper for OpenSSL [..] My motivation for maintaining this package is: Dropbox, another package which I plan to upload, depends on this package. Uhm... AFAIK dropbox used some lgpl libraries, and now we add openssl stuff? Did anyone checked, if that's okay license wise? LGPL + OpenSSL should be fine. It's GPL + OpenSSL that is a problem, since GPL required the combined work be available under the terms of the GPL and those are incompatible with one or two clauses in the OpenSSL license. LGPL makes fewer requirements on the programs that link with it with can be satisfied at the same time as the OpenSSL license. Basically, you have to take the minimum steps to allow your software to be linked against a compatible version of the LGPL code. NB: IANADD; TINASOODP. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ AFAIK, the libraries that Dropbox uses are all licensed either under the MIT (Expat) license, the LGPL, or the OpenSSL license. The only thing in the Dropbox package that is licensed under the GPL is my actual packaging (the contents of debian/), but I can also change this if necessary. Anyways, are there any problems/anything I've overlooked with my ncrypt packaging? Vincent
