Re: maven 3.6.3, please?
Le 15/01/2021 à 10:26, Sudip Mukherjee a écrit : > I think we will also need to update libmodello-maven-plugin-java, > libmodello-java and libplexus-utils2-java in backport to update maven. > Do you see any problem with that? Hi Sudip, I don't remember but I think the versioned dependencies are properly set to ensure a smooth backporting. Go ahead, if it breaks I'll look into it. Emmanuel Bourg
Re: Help with removing the Jruby build-dependency in mustache-java (#979845)
Le 12/01/2021 à 19:59, Louis-Philippe Véronneau a écrit : > I spent an hour looking at the changes 0.9.7 introduces, and I feel it > would be more than a "small, targeted fixes" (the Soft-Freeze has > started!). Maybe someone with more Java skills than I would be confident > the update wouldn't break things right and left, as I'm not. Hi Louis-Philippe, I've updated mustache-java to the version 0.9.1, it no longer depends on jruby. Emmanuel Bourg
Re: gs-collections vs eclipse-collections
Hi Vincent, libgs-collections-java is still used to build libreactor-core-java. eclipse-collections is incompatible with gs-collections because the package name was changed to org.eclipse.collections. For these reasons I suggest to keep the gs-collections package for now, and create a new eclipse-collections source package building libeclipse-collections-java. The gs-collections repository on Salsa can be cloned and used as a starting point for the new package. Emmanuel Bourg Le 07/01/2021 à 01:56, Vincent Prat a écrit : > Dear all, > > The latest version of NatTable (2.0.0) depends on Eclipse Collections > (https://www.eclipse.org/collections/). > Originally, it was called GS Collections, and was renamed when it > migrated to the Eclipse Foundation. > GS Collections is present in Debian (as gs-collections: > https://tracker.debian.org/pkg/gs-collections), but not Eclipse Collections. > > Should we package Eclipse Collections as a separate project (in which > case I will submit an ITP bug), or update and rename the existing package? > For your information, the package gs-collections has no reverse > dependency and has not been updated since September 2017. > > Best wishes for the new year > Vincent >
Re: openjdk segfault with latest jni library from swt4-gtk
Hi All, On Sat, Jan 2, 2021 at 12:44 AM Sudip Mukherjee wrote: > > Hi All, > > I am seeing segfault in openjdk with a coredump when I am using the > updated JNI libraries of swt4-gtk on ppc64el. Its happening every time > > Also, this will be a bug on swt4-gtk or openjdk ? I have opened #979609 on swt4-gtk. And, as mentioned in the bug report this segfault is seen with all the 3 packages (syndie, stegosuite and eclipse-tracecompass) which are using libswt-cairo-gtk-4-jni. -- Regards Sudip
Help with libjsonp-java needed
Hi, I'm not sure whether this is the right moment to update libjsonp-java but I just stumbled upon it on the "stinks" page[1] and I'd love to make those packages I'm responsible for non-stinky. ;-) Thus I refreshed the packaging in Git[2] but the build time test issue I observed some time ago remains and I simply have no idea how to fix it: ... [INFO] JSR 374 (JSON Processing) Default Provider . FAILURE [ 0.012 s] [INFO] JSR 374 (JSON Processing) Media for JAX-RS 1.1 . SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.806 s [INFO] Finished at: 2021-01-16T17:36:28Z [INFO] [ERROR] Failed to execute goal on project javax.json: Could not resolve dependencies for project org.glassfish:javax.json:bundle:1.1.2: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact javax.json:javax.json-api:jar:debian has not been downloaded from it before. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :javax.json dh_auto_build: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/build/libjsonp-java-1.1.2 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/build/libjsonp-java-1.1.2/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/build/libjsonp-java-1.1.2/debian -Dmaven.repo.local=/build/libjsonp-java-1.1.2/debian/maven-repo install javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1 I wonder whether somebody might have some clue. Kind regards Andreas. [1] https://trends.debian.net/packages-with-smells-sorted-by-maintainer.txt [2] https://salsa.debian.org/java-team/libjsonp-java -- http://fam-tille.de
Re: Help with libjsonp-java needed
Hi Andreas, Le 16/01/2021 à 20:31, Andreas Tille a écrit : Hi, I'm not sure whether this is the right moment to update libjsonp-java but I just stumbled upon it on the "stinks" page[1] and I'd love to make those packages I'm responsible for non-stinky. ;-) Thus I refreshed the packaging in Git[2] but the build time test issue I observed some time ago remains and I simply have no idea how to fix it: ... [INFO] JSR 374 (JSON Processing) Default Provider . FAILURE [ 0.012 s] [INFO] JSR 374 (JSON Processing) Media for JAX-RS 1.1 . SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.806 s [INFO] Finished at: 2021-01-16T17:36:28Z [INFO] [ERROR] Failed to execute goal on project javax.json: Could not resolve dependencies for project org.glassfish:javax.json:bundle:1.1.2: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact javax.json:javax.json-api:jar:debian has not been downloaded from it before. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :javax.json dh_auto_build: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/build/libjsonp-java-1.1.2 -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/build/libjsonp-java-1.1.2/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/build/libjsonp-java-1.1.2/debian -Dmaven.repo.local=/build/libjsonp-java-1.1.2/debian/maven-repo install javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1 I wonder whether somebody might have some clue. Yes, the issue is the version number of the dependency javax.json-api was hardcoded in the patch 03-bundle-dependencies -- this thus broke when the last upstream version was adopted. I have pushed a correction to Salsa. To have the package build, I also ignored the module jaxrs-1x in d/libjsonp-java.poms (pushed to Salsa as well). I think this is safe because you already ignored the jaxrs module, which is very close. If you need it, just revert my last commit, but then you will need to add a dependency on libjsr311-api-java and to modify some lines in jaxrs-1x/pom.xml. Kind regards Andreas. All the best, Pierre
