Bug#1013324: Upgrade package to latest upstream version
Le 2022-06-29 à 01 h 47, tony mancill a écrit : On Thu, Jun 23, 2022 at 08:52:53PM -0700, tony mancill wrote: On Tue, Jun 21, 2022 at 01:59:00PM -0400, Jérôme Charaoui wrote: Package: lz4-java Version: 1.5.1-3 Severity: wishlist Dear maintainer, Please upgrade lz4-java to the latest version, 1.8.0. It includes several API and performance improvements, and a package I would like to upload to Debian, nippy-clojure, depends on version 1.7.1 and above of this package. Hello Jerome, Thank you for the bug report. I am working on this now. I have updated the patches and am working through an issue with the mvel templating. I will update the bug if it looks like it's going to take much longer. Hi Jérôme, I have just uploaded to experimental because I have have a few open questions about the update before uploading to unstable. First, lz4-java now supports a "lz4-pure-java" build that results in only a jar file with no need for the JNI package or the lz4 library. It is easy to build this, but I think we would want this in a separate binary package that doesn't depend on the JNI binary package. That will necessitate the package going through NEW, so I am asking the team first. (IMO, a pure Java implementation is a nice improvement.) Second, the build of 1.8.0 results in a lintian warning that I'm trying to understand, because when I run ldd against the library, it definitely appears to be linked against libc (and against the same libraries that the liblz4-java.so file in the 1.5.1 packaging is, yet that package doesn't trigger the lintian error). E: liblz4-jni: library-not-linked-against-libc [usr/lib/x86_64-linux-gnu/jni/liblz4-java.so] All of the r-deps that build against 1.5.1 are building against 1.8.0. Please let me know if you have any issues with the new package. Hi Tony, I've tested nippy-clojure with the latest lz4-java binaries and the testsuite is running fine. Thanks for working on this! -- Jérôme
Bug#1013324: Upgrade package to latest upstream version
On Tue, 28 Jun 2022 22:47:42 -0700, tony mancill wrote: > Second, the build of 1.8.0 results in a lintian warning that I'm trying > to understand, because when I run ldd against the library, it definitely > appears to be linked against libc (and against the same libraries that > the liblz4-java.so file in the 1.5.1 packaging is, yet that package > doesn't trigger the lintian error). > > E: liblz4-jni: library-not-linked-against-libc > [usr/lib/x86_64-linux-gnu/jni/liblz4-java.so] That's probably a lintian false positive, we are also seeing this in perl (arch:any) packages. I forgot the details but looking at lintian bugs, https://bugs.debian.org/896012 came up. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- BOFH excuse #160: non-redundant fan failure
Bug#1013324: Upgrade package to latest upstream version
On Thu, Jun 23, 2022 at 08:52:53PM -0700, tony mancill wrote: > On Tue, Jun 21, 2022 at 01:59:00PM -0400, Jérôme Charaoui wrote: > > Package: lz4-java > > Version: 1.5.1-3 > > Severity: wishlist > > > > Dear maintainer, > > > > Please upgrade lz4-java to the latest version, 1.8.0. > > > > It includes several API and performance improvements, and a package I would > > like to upload to Debian, nippy-clojure, depends on version 1.7.1 and above > > of this package. > > Hello Jerome, > > Thank you for the bug report. I am working on this now. I have updated > the patches and am working through an issue with the mvel templating. I > will update the bug if it looks like it's going to take much longer. Hi Jérôme, I have just uploaded to experimental because I have have a few open questions about the update before uploading to unstable. First, lz4-java now supports a "lz4-pure-java" build that results in only a jar file with no need for the JNI package or the lz4 library. It is easy to build this, but I think we would want this in a separate binary package that doesn't depend on the JNI binary package. That will necessitate the package going through NEW, so I am asking the team first. (IMO, a pure Java implementation is a nice improvement.) Second, the build of 1.8.0 results in a lintian warning that I'm trying to understand, because when I run ldd against the library, it definitely appears to be linked against libc (and against the same libraries that the liblz4-java.so file in the 1.5.1 packaging is, yet that package doesn't trigger the lintian error). E: liblz4-jni: library-not-linked-against-libc [usr/lib/x86_64-linux-gnu/jni/liblz4-java.so] All of the r-deps that build against 1.5.1 are building against 1.8.0. Please let me know if you have any issues with the new package. Thank you, tony
Bug#1013324: Upgrade package to latest upstream version
On Tue, Jun 21, 2022 at 01:59:00PM -0400, Jérôme Charaoui wrote: > Package: lz4-java > Version: 1.5.1-3 > Severity: wishlist > > Dear maintainer, > > Please upgrade lz4-java to the latest version, 1.8.0. > > It includes several API and performance improvements, and a package I would > like to upload to Debian, nippy-clojure, depends on version 1.7.1 and above > of this package. Hello Jerome, Thank you for the bug report. I am working on this now. I have updated the patches and am working through an issue with the mvel templating. I will update the bug if it looks like it's going to take much longer. Cheers, tony
Bug#1013324: Upgrade package to latest upstream version
Package: lz4-java Version: 1.5.1-3 Severity: wishlist Dear maintainer, Please upgrade lz4-java to the latest version, 1.8.0. It includes several API and performance improvements, and a package I would like to upload to Debian, nippy-clojure, depends on version 1.7.1 and above of this package. Thank you! -- Jerome
