Re: RFS: bluecove, bluecove-gpl
Hi Chris, Sorry for the huge wait. [...] If these files completely lack copyright information, it might not even be legal to distribute them. The proper approach would definitely be to track down where they come from and fix the copyrightlicense information. Maybe they are part of some larger source package which has its license stated in a separate file!? Best regards, Michael I have contacted the developer but am quite confused with his response. You can see the thread here http://groups.google.com/group/bluecove-developers/browse_thread/thread/f28c13ae5a3e9d46 . If they created the files, they should also take their copyright. This would at least clarify who created them. Licensing might be free of choice as well; and with a copyright it would at least be clear with whom this is to be discussed, if debate is necessary. If you could get that fixed I'd offer to do another round of reviews. Thanks a lot, Michael pgplRvEiSZcvE.pgp Description: PGP signature
Re: RFS: bluecove, bluecove-gpl
On Sat, 2010-12-04 at 22:43 +0100, Michael Tautschnig wrote: [...] - There is missing/incomplete license information in three source files: ./src/main/java/com/sun/cdc/io/ConnectionBaseInterface.java: *No copyright* UNKNOWN ./src/main/java/com/ibm/oti/connection/CreateConnection.java: UNKNOWN ./src/main/java/com/ibm/oti/vm/VM.java: UNKNOWN All of them carry a marker Not in distributed bluecove jar, but this doesn't make the source of those files distributable. I guess you will have to repack the tarball to produce a DFSG-free version. [...] If these files completely lack copyright information, it might not even be legal to distribute them. The proper approach would definitely be to track down where they come from and fix the copyrightlicense information. Maybe they are part of some larger source package which has its license stated in a separate file!? Best regards, Michael I have contacted the developer but am quite confused with his response. You can see the thread here http://groups.google.com/group/bluecove-developers/browse_thread/thread/f28c13ae5a3e9d46 . Thanks, Chris signature.asc Description: This is a digitally signed message part
Re: RFS: bluecove, bluecove-gpl
Hi Chris, I have nearly completed these changes now. However I am having problems with the three files listed below. All files are required to build, even thought they are not part of the release jar. I guess that rules out just removing them? What is the best way to proceed now? The options I can think of are, find out where these files come from and what licences and copyright apply, then if possible upload the bluecove package to unstable and bluecove-gpl to contrib, or, package the source of these files seperately and if possible add to non-free, then upload both packages to contrib. [...] - There is missing/incomplete license information in three source files: ./src/main/java/com/sun/cdc/io/ConnectionBaseInterface.java: *No copyright* UNKNOWN ./src/main/java/com/ibm/oti/connection/CreateConnection.java: UNKNOWN ./src/main/java/com/ibm/oti/vm/VM.java: UNKNOWN All of them carry a marker Not in distributed bluecove jar, but this doesn't make the source of those files distributable. I guess you will have to repack the tarball to produce a DFSG-free version. [...] If these files completely lack copyright information, it might not even be legal to distribute them. The proper approach would definitely be to track down where they come from and fix the copyrightlicense information. Maybe they are part of some larger source package which has its license stated in a separate file!? Best regards, Michael pgpljQs67omCX.pgp Description: PGP signature
Re: RFS: bluecove, bluecove-gpl
I have nearly completed these changes now. However I am having problems with the three files listed below. All files are required to build, even thought they are not part of the release jar. I guess that rules out just removing them? What is the best way to proceed now? The options I can think of are, find out where these files come from and what licences and copyright apply, then if possible upload the bluecove package to unstable and bluecove-gpl to contrib, or, package the source of these files seperately and if possible add to non-free, then upload both packages to contrib. Thanks, Chris On Mon, 2010-11-15 at 20:52 +0100, Michael Tautschnig wrote: You might want to take a look at http://markmail.org/message/u7qajey4e2dxbj2r (in the quoted part towards the end). I can confirm that this makes lintian happy :-) There are a number of other remarks I'd like to add. First for bluecove: - There is missing/incomplete license information in three source files: ./src/main/java/com/sun/cdc/io/ConnectionBaseInterface.java: *No copyright* UNKNOWN ./src/main/java/com/ibm/oti/connection/CreateConnection.java: UNKNOWN ./src/main/java/com/ibm/oti/vm/VM.java: UNKNOWN All of them carry a marker Not in distributed bluecove jar, but this doesn't make the source of those files distributable. I guess you will have to repack the tarball to produce a DFSG-free version. - Apropos repacking: both bluecove and bluecove-gpl tarballs produce a warning with tar, please check. - Please review your debian/copyright, License: stanza and fix it (no, you'll have to spot the error yourself). A DEP-5 formatted copyright file would still be nice to have. - Your README.Debian should probably be README.source - this information isn't really useful for users of the binary package (they won't see LICENSE.txt anyway). - debian/watch doesn't work. bluecove-gpl: - See above for tarball and DEP-5 for debian/copyright. - It's not only GPL 3 - use licensecheck `find src/ -type f` to find out for yourself. - After acting according to the markmail.org post referenced above you'll have to updated debian/control as lintian is going to tell you. - Package doesn't build on non-i386 architectures because of a library_suffix that is added. Use libbluecove*.so instead of libbluecove.so in your debian/rules file (both in clean and for the mv command). - debian/watch doesn't work. I hope I'm not leaving too much open to find out for yourself, but I strongly believe that this is way more educative :-) Hope this helps, Michael signature.asc Description: This is a digitally signed message part
Re: RFS: bluecove, bluecove-gpl
I have now fixed the licencing issues (see README.Debian) and updated the packages. I am still getting the library-not-linked-against-libc warning from lintian but I am reasonably sure the library is linked against libc as you can see below. ch...@chris-desktop:~$ ldd /usr/lib/jni/libbluecove-2.1.0.so linux-gate.so.1 = (0xb78da000) libbluetooth.so.3 = /usr/lib/libbluetooth.so.3 (0xb7894000) libc.so.6 = /lib/i686/cmov/libc.so.6 (0xb774e000) /lib/ld-linux.so.2 (0xb78db000) Does anyone know why this is happening? Thanks, Chris On Sat, 2010-11-13 at 16:30 +0100, Michael Tautschnig wrote: Hi Chris, Dear mentors, I am looking for a sponsor for my packages bluecove and bluecove-gpl. Package name: bluecove Version : 2.1.0-1 Upstream Author : Many URL : http://bluecove.org License : LGPL and GPL Section : java and libs Bluecove builds these binary packages: libbluecove-2.1.0-java - Java library for Bluetooth (JSR-82 implementation) I briefly reviewed the copyright information of libbluecove and was kind of irritated by README and LICENSE saying it is LGPL while *all* (well, a few even missing license/copyright information) the source files say it is Apache 2.0 licensed!? Could you please get some clarifification from upstream? Please get this fixed first as BlueCove-GPL relies on this one and cannot be built without it. BlueCove-GPL builds these binary packages: libbluecove-gpl-2.1.0 - additional module for BlueCove support on Linux (native library) libbluecove-gpl-2.1.0-java - additional module for BlueCove support on Linux (java library) BlueCove is lintian clean however BlueCove-GPL has two warnings: E: libbluecove-gpl-2.1.0: sharedobject-in-library-directory-missing-soname usr/lib/libbluecove-2.1.0.so W: libbluecove-gpl-2.1.0: library-not-linked-against-libc ./usr/lib/libbluecove-2.1.0.so I would appreciate help with these as I have run out of ideas. Run lintian with the additional flag -i to get a more detailed description, which can also be found here: http://lintian.debian.org/tags/sharedobject-in-library-directory-missing-soname.html http://lintian.debian.org/tags/library-not-linked-against-libc.html The other small issue with the packages is the Maintainer, I created a Java package recently (ant-contrib-cpptasks), for which the Maintainer is the Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org, should this package (as its a java package) have this Maintainer also? [...] I guess this is up to you, whether you prefer future team maintenance or would like to stay the lone maintainer of these packages. Hope this helps, Michael signature.asc Description: This is a digitally signed message part
Re: RFS: bluecove, bluecove-gpl
Hi Chris, I have now fixed the licencing issues (see README.Debian) and updated the packages. I am still getting the library-not-linked-against-libc warning from lintian but I am reasonably sure the library is linked against libc as you can see below. [...] You might want to take a look at http://markmail.org/message/u7qajey4e2dxbj2r (in the quoted part towards the end). I can confirm that this makes lintian happy :-) There are a number of other remarks I'd like to add. First for bluecove: - There is missing/incomplete license information in three source files: ./src/main/java/com/sun/cdc/io/ConnectionBaseInterface.java: *No copyright* UNKNOWN ./src/main/java/com/ibm/oti/connection/CreateConnection.java: UNKNOWN ./src/main/java/com/ibm/oti/vm/VM.java: UNKNOWN All of them carry a marker Not in distributed bluecove jar, but this doesn't make the source of those files distributable. I guess you will have to repack the tarball to produce a DFSG-free version. - Apropos repacking: both bluecove and bluecove-gpl tarballs produce a warning with tar, please check. - Please review your debian/copyright, License: stanza and fix it (no, you'll have to spot the error yourself). A DEP-5 formatted copyright file would still be nice to have. - Your README.Debian should probably be README.source - this information isn't really useful for users of the binary package (they won't see LICENSE.txt anyway). - debian/watch doesn't work. bluecove-gpl: - See above for tarball and DEP-5 for debian/copyright. - It's not only GPL 3 - use licensecheck `find src/ -type f` to find out for yourself. - After acting according to the markmail.org post referenced above you'll have to updated debian/control as lintian is going to tell you. - Package doesn't build on non-i386 architectures because of a library_suffix that is added. Use libbluecove*.so instead of libbluecove.so in your debian/rules file (both in clean and for the mv command). - debian/watch doesn't work. I hope I'm not leaving too much open to find out for yourself, but I strongly believe that this is way more educative :-) Hope this helps, Michael pgpknT3Ig081h.pgp Description: PGP signature
Re: RFS: bluecove, bluecove-gpl
Hi Chris, Dear mentors, I am looking for a sponsor for my packages bluecove and bluecove-gpl. Package name: bluecove Version : 2.1.0-1 Upstream Author : Many URL : http://bluecove.org License : LGPL and GPL Section : java and libs Bluecove builds these binary packages: libbluecove-2.1.0-java - Java library for Bluetooth (JSR-82 implementation) I briefly reviewed the copyright information of libbluecove and was kind of irritated by README and LICENSE saying it is LGPL while *all* (well, a few even missing license/copyright information) the source files say it is Apache 2.0 licensed!? Could you please get some clarifification from upstream? Please get this fixed first as BlueCove-GPL relies on this one and cannot be built without it. BlueCove-GPL builds these binary packages: libbluecove-gpl-2.1.0 - additional module for BlueCove support on Linux (native library) libbluecove-gpl-2.1.0-java - additional module for BlueCove support on Linux (java library) BlueCove is lintian clean however BlueCove-GPL has two warnings: E: libbluecove-gpl-2.1.0: sharedobject-in-library-directory-missing-soname usr/lib/libbluecove-2.1.0.so W: libbluecove-gpl-2.1.0: library-not-linked-against-libc ./usr/lib/libbluecove-2.1.0.so I would appreciate help with these as I have run out of ideas. Run lintian with the additional flag -i to get a more detailed description, which can also be found here: http://lintian.debian.org/tags/sharedobject-in-library-directory-missing-soname.html http://lintian.debian.org/tags/library-not-linked-against-libc.html The other small issue with the packages is the Maintainer, I created a Java package recently (ant-contrib-cpptasks), for which the Maintainer is the Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org, should this package (as its a java package) have this Maintainer also? [...] I guess this is up to you, whether you prefer future team maintenance or would like to stay the lone maintainer of these packages. Hope this helps, Michael pgpYSVR1VlqxE.pgp Description: PGP signature
