Bug#1023237: openjdk-11: Keep out of testing and stable
Le 17/04/2024 à 09:54, Timo Röhling a écrit : FastDDSGen currently depends on OpenJDK 11 (or more precisely, any OpenJDK before 15) because it needs the Nashorn JavaScript engine, so could OpenJDK 11 be kept in trixie for the time being? That's a dead end, if OpenJDK 11 is kept there will be no incentive to update softwares to follow the evolution of Java, and the old JDK will just hang there forever. Alternatively, someone could help me package the standalone version: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038142 Packaging Nashorn is the way to go in this case. You can post to the debian-java mailing list to get some help with the packaging. Emmanuel Bourg
Bug#1068463: marked as pending in procyon
Control: tag -1 pending Hello, Bug #1068463 in procyon reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/procyon/-/commit/5d917ba977596412dd3b207a9195c78390cadc7b Prevent untrusted code execution from the command line (Closes: #1068463) (this message was generated automatically) -- Greetings https://bugs.debian.org/1068463
Bug#1052733: marked as pending in groovy
Control: tag -1 pending Hello, Bug #1052733 in groovy reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/groovy/-/commit/3ee4fa2a6f97acae2e09da42290ecb30d825e80f Fixed the type inference errors when building with source/target level 8 (Closes: #1052733) (this message was generated automatically) -- Greetings https://bugs.debian.org/1052733
Bug#1052743: marked as pending in libhamcrest-java
Control: tag -1 pending Hello, Bug #1052743 in libhamcrest-java reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/libhamcrest-java/-/commit/775c0fe4447d6cfe654ed27b8a925f9dddbf4eb9 Fixed the type inference errors when building with source/target level 8 (Closes: #1052743) (this message was generated automatically) -- Greetings https://bugs.debian.org/1052743
Bug#1052758: marked as pending in gradle
Control: tag -1 pending Hello, Bug #1052758 in gradle reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/gradle/-/commit/eec89b31a252685e65f19edcbbdad190ea7e4031 Fixed the type inference errors when building with source/target level 8 (Closes: #1052758) (this message was generated automatically) -- Greetings https://bugs.debian.org/1052758
Bug#1034824: tomcat9 should not be released with Bookworm
Le 2023-05-26 21:14, Paul Gevers a écrit : I have just added removal hints for tomcatjss and dogtag-pki. As mentioned in my previous message, I want the changes in logback reverted. You can do the reduced upload of tomcat9. Markus, can you please revert you logback change by tomorrow at the latest? The changes to jetty9 have to be reverted too, the package is broken (#1036798). Sadly we can't do without tomcat9. The path forward implies packaging Jetty 11 or 12 first and migrating all the reverse dependencies, but that's a task for Trixie. Thanks again to Oracle for forcing the javax to jakarta transition on the community, what a waste of energy just to please a couple of lawyers in an office. Emmanuel Bourg
Bug#1036798: jetty9: Failed startup of context: JettyJasperInitializer not a subtype of javax.servlet.ServletContainerInitializer
Package: jetty9 Version: 9.4.50-3 Severity: grave Justification: renders package unusable The jetty9 package can no longer run web applications after switching to libtomcat10-java for the JSP compiler. The following error appears in the log: java.util.ServiceConfigurationError: javax.servlet.ServletContainerInitializer: org.eclipse.jetty.apache.jsp.JettyJasperInitializer not a subtype at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:593) at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1244) at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(ServiceLoader.java:1273) at java.base/java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1309) at java.base/java.util.ServiceLoader$3.hasNext(ServiceLoader.java:1393) at org.eclipse.jetty.annotations.AnnotationConfiguration.getNonExcludedInitializers(AnnotationConfiguration.java:829) at org.eclipse.jetty.annotations.AnnotationConfiguration.configure(AnnotationConfiguration.java:343) at org.eclipse.jetty.webapp.WebAppContext.configure(WebAppContext.java:498) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1409) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:916) at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:288) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:524) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) at org.eclipse.jetty.deploy.bindings.StandardStarter.processBinding(StandardStarter.java:46) at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:188) at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:517) at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:157) at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:173) at org.eclipse.jetty.deploy.providers.WebAppProvider.fileAdded(WebAppProvider.java:428) at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:66) at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:785) at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:754) at org.eclipse.jetty.util.Scanner.scan(Scanner.java:641) at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:540) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) at org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:146) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) at org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:605) at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:252) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169) at org.eclipse.jetty.server.Server.start(Server.java:423) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97) at org.eclipse.jetty.server.Server.doStart(Server.java:387) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) at org.eclipse.jetty.xml.XmlConfiguration.lambda$main$3(XmlConfiguration.java:1907) at java.base/java.security.AccessController.doPrivileged(AccessController.java:569) at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1857) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:568) at org.eclipse.jetty.start.Main.invokeMain(Main.java:218) at org.eclipse.jetty.start.Main.start(Main.java:491) at org.eclipse.jetty.start.Main.main(Main.java:77) Reverting back to libtomcat9-java fixes the issue. Using the Jasper compiler from Tomcat 10 with Jetty 9 is unlikely to work properly since the source files generated will use the servlet classes from the jakarta namespace and Jetty 9 doesn't implement them. Emmmanuel Bourg
Bug#1034855: trapperkeeper-webserver-jetty9-clojure: FTBFS in testing:
Le 22/05/2023 à 18:27, Markus Koschany a écrit : Can you think of a simpler solution for this problem? I'll get a look. Intuitively I think that if no Tomcat internals are used, the javax.servlet classes should still be used since Tomcat 10 works with both javax and jakarta namespaces. If necessary we may also consider using the tomcat-jakartaee-migration tool at build time instead of patching the source files. Emmanuel
Bug#1034824: tomcat9 should not be released with Bookworm
Le 26/05/2023 à 10:58, Moritz Muehlenhoff a écrit : Can't we just do the pragmatic fix of updating src:tomcat9 to only ship libtomcat9-java and libtomcat9-embed-java? The maintenance burden for security updates lies within the server stack, the percentage of issues affecting the libtomcat9-java binary packages as used by rdeps will be small to none? dogtag-pki has a popcon of 4, do we really want to keep that package and tomcat9 for so few users? It could come back later in Bookworm as a backport once it supports Tomcat 10. If tomcat9 is kept in Bookworm most users won't realize it's no longer supported. I think we should add a prominent warning in the NEWS file that it's not supported. I'd even suggest disabling the tomcat9 service when upgrading to force the users to act (either migrate to tomcat10, or re-enabling it willingly). Emmanuel Bourg
Bug#1034982: marked as pending in android-platform-tools
Control: tag -1 pending Hello, Bug #1034982 in android-platform-tools reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/android-tools-team/android-platform-tools/-/commit/4e44148cf0129f468a1f4530b5bd4c4ae0e5d4fb Added the missing Replaces field for android-libnativehelper (Closes: #1034982) (this message was generated automatically) -- Greetings https://bugs.debian.org/1034982
Bug#1034824: tomcat9 should not be released with Bookworm
Le 2023-05-13 22:38, Markus Koschany a écrit : The question is: If we ship libtomcat9-java in Bookworm and change the dependency from tomcat9-user to tomcat10-user, will a web application like dogtag-pki, which is designed for Tomcat 9, continue to work with Tomcat 10? I'm pretty sure it won't work. dogtag-pki depends on tomcatjss which is tightly coupled with Tomcat's internal code. Unfortunately tomcatjss upstream is lagging with the Tomcat 10 adoption [1], and we can't hold back Tomcat 10 in Debian indefinitely just for that (for the reminder, Tomcat 10 is a very important release implementing the new Jakarta EE specification, not having it in Bookworm would be a real disservice to our users). The thing I don't understand is why a CA webapp needs a custom Tomcat connector (tomcatjss), maybe it could be patched to work without it? Emmanuel Bourg [1] https://github.com/dogtagpki/tomcatjss/issues/68
Bug#1035995: bazel-bootstrap: Depend on libgeronimo-annotation-1.3-spec-java instead of libtomcat9-java
Package: bazel-bootstrap Version: 4.2.3+ds-8 Severity: serious bazel-bootstrap depends on libtomcat9-java, only to use tomcat9-annotations-api.jar which provides the javax.annotations package. Since libtomcat9-java is about to be removed this needs to be replaced. libtomcat10-java provides a new version of the annotations API but under the jakarta.annotation package. It would involve patching bazel-bootstrap heavily. The javax.annotations package is also provided by libgeronimo-annotation-1.3-spec-java, it could be used as a replacement.
Bug#1035992: apache-log4j-extras1.2: Error while generating Javadoc: Unable to write 'options' temporary file
Source: apache-log4j-extras1.2 Version: 1.2.17-2 Severity: serious Tags: ftbfs apache-log4j-extras1.2 fails to build with the following error: [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 3.437 s [INFO] Finished at: 2023-05-12T10:19:16Z [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.4.1:jar (default-cli) on project apache-log4j-extras: MavenReportException: Error while generating Javadoc: Unable to write 'options' temporary file for command execution: Input length = 1 -> [Help 1] [ERROR]
Bug#1011597: marked as pending in tiles
Control: tag -1 pending Hello, Bug #1011597 in tiles reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/tiles/-/commit/30d709f2a8c99607e4376671491fa5a1117bcc4d Fixed the build failure with Java 17 (Closes: #1011597) (this message was generated automatically) -- Greetings https://bugs.debian.org/1011597
Bug#1034824: tomcat9 should not be released with Bookworm
Hi Paul, Le 2023-05-11 21:44, Paul Gevers a écrit : From a quick look at the key packages: It seems you didn't follow up (86 days) on libcommons-dbcp-java which can't migrate to bookworm because it would make libbiojava-java-doc uninstallable (no fix there, no bug report filed). I have to apology for this one, I forgot to check the transition of libcommons-dbcp-java. Is it still possible to remove libbiojava-java-doc to fix this (very low popcon and unused like the other -java-doc package)? src:tiles also build-depends on libtomcat9-java, with no bug filed for the migration to tomcat10 *and* it having it's own FTBFS bug. (It's key because of src:libspring-java) I remember pulling my hair on src:tiles to make it build with OpenJDK 17, without success unfortunately (#1011597). The project is dead upstream, that doesn't help. Patching src:libspring-java and removing src:tiles is likely the next step. On IRC carnil and jmm_ suggested that src:tomcat9 could be left in bookworm but have it's server component stripped. Would that help the situation? I agree, this is a good compromise. Emmanuel Bourg
Bug#1033170: libitext-rups-java: Does not work at all
Le 2023-03-28 05:28, tony mancill a écrit : The upload is ready. Any concerns? $ reverse-depends libitext-rups-java No reverse dependencies found $ reverse-depends -b libitext-rups-java No reverse dependencies found +1 for removing libitext-rups-java, and maybe libitext-rtf-java too.
Bug#1026713: marked as pending in apache-directory-server
Control: tag -1 pending Hello, Bug #1026713 in apache-directory-server reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/apache-directory-server/-/commit/c5a8619821dddb48a057eeef3101a7feafeb28c5 Fixed the build failure with mina 2.2 (Closes: #1026713) (this message was generated automatically) -- Greetings https://bugs.debian.org/1026713
Bug#1026639: rhino FTBFS
I don't think this should be assigned to rhino. ckeditor should open the internal packages it touches.
Bug#1011172: marked as pending in segment
Control: tag -1 pending Hello, Bug #1011172 in segment reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/segment/-/commit/4529ccc8200ae98fcd94474a1b9974c751ba86ec Fixed the build failure with Java 17 (Closes: #1011172) (this message was generated automatically) -- Greetings https://bugs.debian.org/1011172
Bug#1012102: marked as pending in groovycsv
Control: tag -1 pending Hello, Bug #1012102 in groovycsv reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/groovycsv/-/commit/c258c208a62e0bbf13c38db68323f70aa6667d50 Fixed the build failure with Java 17 (Closes: #1012102) (this message was generated automatically) -- Greetings https://bugs.debian.org/1012102
Bug#1028838: marked as pending in maven-remote-resources-plugin
Control: tag -1 pending Hello, Bug #1028838 in maven-remote-resources-plugin reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/maven-remote-resources-plugin/-/commit/05988dc05cea5e4d81583ad1fde73b0b9eb0145d Depend on libmaven-parent-java (Closes: #1028838) (this message was generated automatically) -- Greetings https://bugs.debian.org/1028838
Bug#986070: closing 986070
close 986070 thanks Green light for Kotlin and its dependencies in testing
Bug#1028866: marked as pending in maven-ejb-plugin
Control: tag -1 pending Hello, Bug #1028866 in maven-ejb-plugin reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/maven-ejb-plugin/-/commit/cb565ded72904def11c38bdfc1e36ff12c75cb59 Depend on libmaven-parent-java (Closes: #1028866) (this message was generated automatically) -- Greetings https://bugs.debian.org/1028866
Bug#1028851: marked as pending in maven-war-plugin
Control: tag -1 pending Hello, Bug #1028851 in maven-war-plugin reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/maven-war-plugin/-/commit/862b85817ef9df1a27909e47a749e715b018bee5 Depend on libmaven-parent-java (Closes: #1028851) (this message was generated automatically) -- Greetings https://bugs.debian.org/1028851
Bug#1028831: marked as pending in maven-source-plugin
Control: tag -1 pending Hello, Bug #1028831 in maven-source-plugin reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/maven-source-plugin/-/commit/d708a543e6cde3b79f2df31436cdb50ce6d05daa Depend on libmaven-parent-java (Closes: #1028831) (this message was generated automatically) -- Greetings https://bugs.debian.org/1028831
Bug#1021549: marked as pending in maven-artifact-transfer
Control: tag -1 pending Hello, Bug #1021549 in maven-artifact-transfer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/maven-artifact-transfer/-/commit/5c4e3c07c5ad2e1e3d6b4a756a3fdacf9795021a Fixed the build failure with Maven 3.8 (Closes: #1021549) (this message was generated automatically) -- Greetings https://bugs.debian.org/1021549
Bug#1026665: marked as pending in doxia-sitetools
Control: tag -1 pending Hello, Bug #1026665 in doxia-sitetools reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/doxia-sitetools/-/commit/a55fc0f4a22c90cfaa4d5084dc40a44213ee47ae Explicit dependency on libeclipse-sisu-maven-plugin-java (Closes: #1026665) (this message was generated automatically) -- Greetings https://bugs.debian.org/1026665
Bug#1026689: marked as pending in doxia
Control: tag -1 pending Hello, Bug #1026689 in doxia reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/doxia/-/commit/2f9ebc943436711e261205370a167bb20552248f Added the missing dependency on sisu-maven-plugin (Closes: #1026689) (this message was generated automatically) -- Greetings https://bugs.debian.org/1026689
Bug#1027643: marked as pending in tycho
Control: tag -1 pending Hello, Bug #1027643 in tycho reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/tycho/-/commit/565f4a674e51ee26607814d5e9ac044e4e911620 Explicit dependency on osgi-compendium in the Maven pom (Closes: #1027643) (this message was generated automatically) -- Greetings https://bugs.debian.org/1027643
Bug#1019488: bouncycastle: incomplete information in the manifest files
Le 30/10/2022 à 01:31, Sudip Mukherjee a écrit : The attached patch is the minimum required to unblock eclipse-tracecompass. But Emmanuel Bourg did not agree so I am not doing an upload but keeping the patch here for record. Ref: https://lists.debian.org/debian-java/2022/09/msg2.html My objection was about patching the Eclipse manifests, not Bouncy Castle. Regarding BC, the question is why the build system doesn't generate the same OSGi metadata than the ones in Maven Central. Is there a missing build step on our side? Emmanuel Bourg
Bug#1027558: marked as pending in wagon
Control: tag -1 pending Hello, Bug #1027558 in wagon reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/wagon/-/commit/f43786cd4abd57d579b173ee6a24f5538f0723d6 Set the target release to Java 8 (Closes: #1027558) (this message was generated automatically) -- Greetings https://bugs.debian.org/1027558
Bug#1026679: marked as pending in maven-ejb-plugin
Control: tag -1 pending Hello, Bug #1026679 in maven-ejb-plugin reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/maven-ejb-plugin/-/commit/247573e018aef623c2993cec77f60dd11f15c182 Fixed the compatibility with maven-filtering 3.3.0 (Closes: #1026679) (this message was generated automatically) -- Greetings https://bugs.debian.org/1026679
Bug#1026726: marked as pending in apache-directory-api
Control: tag -1 pending Hello, Bug #1026726 in apache-directory-api reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/apache-directory-api/-/commit/59f67f6e59ebe7aa65e77473ffc60e0687367789 Depend on libmina2-java (>= 2.2.1) (Closes: #1026726) (this message was generated automatically) -- Greetings https://bugs.debian.org/1026726
Bug#1026656: marked as pending in maven-war-plugin
Control: tag -1 pending Hello, Bug #1026656 in maven-war-plugin reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/maven-war-plugin/-/commit/0516f362df65bcd8a931cd6b32697d955133c1fd Fixed the build failure with maven-filtering 3.3 (Closes: #1026656) (this message was generated automatically) -- Greetings https://bugs.debian.org/1026656
Bug#1020298: marked as pending in eclipse-platform-runtime
Control: tag -1 pending Hello, Bug #1020298 in eclipse-platform-runtime reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/eclipse-platform-runtime/-/commit/eda98fc8cc2389db86f00ef21a088da1dcdd177b Fixed the javax.annotation version range in the OSGi metadata (Closes: #1020298) (this message was generated automatically) -- Greetings https://bugs.debian.org/1020298
Bug#1011532: marked as pending in icedtea-web
Control: tag -1 pending Hello, Bug #1011532 in icedtea-web reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/icedtea-web/-/commit/184c05ab121ad4f71a1ad7bd1d1de4fbc62cd2d0 Removed pack200 support to build with Java 17 (Closes: #1011532) (this message was generated automatically) -- Greetings https://bugs.debian.org/1011532
Bug#1023237: openjdk-11: Keep out of testing and stable
Source: openjdk-11 Version: 11.0.4+11-1 Severity: serious Justification: should not migrate to testing or stable any more openjdk-17 is now the default JDK, but openjdk-11 is still required for bootstrapping JVM-based languages like Kotlin or Scala in unstable. Therefore the package should no longer migrate to testing or stable anymore.
Bug#1022293: marked as pending in localizer
Control: tag -1 pending Hello, Bug #1022293 in localizer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/localizer/-/commit/7a0b4c03f90833350f568996d6cbe08790a645c4 Fixed the build failure with maven-archiver 3.6 (Closes: #1022293) (this message was generated automatically) -- Greetings https://bugs.debian.org/1022293
Bug#1004638: openjfx: diff for NMU version 11.0.11+0-1.1
Le 26/10/2022 à 01:27, Sebastian Ramacher a écrit : Dear maintainer, I've prepared an NMU for openjfx (versioned as 11.0.11+0-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Hi Sebastian, Thank you for the update, but could you send a PR on Salsa instead of uploading NMUs please? Emmanuel Bourg
Bug#1004638: Bug#1013009: Bug#1004638: openjfx: FTBFS with ffmpeg 5.0
Le 16/10/2022 à 17:10, Philipp Kern a écrit : While arm64/armhf remains unfixed (and could have its own t-p-u upload based on the +0 version plus Ubuntu's patch), there's also a question if a newer version would actually fix the issue. I talked to Sebastian on IRC and we agreed that I'd upload the Ubuntu patch for now. It doesn't make anything worse and will allow building on amd64 again. Hi Philipp, Thank you for taking the time to look into the openjfx package. Do you know how difficult porting to ffmpeg 5.0 would be? The video support is a major feature of OpenJFX, removing it isn't ideal. Emmanuel Bourg
Bug#1013355: groovy: FTBFS with jansi 2.4.0-1
Le 2022-06-22 17:54, Markus Koschany a écrit : groovy FTBFS with jansi 2.4.0. I intend to either prepare a patch or upgrade to a newer upstream release in the future. Please hold the upload, this is going to blow up Maven and Gradle. I've introduced jansi1 to try to work around the issue but I haven't completed the transition yet. Emmanuel Bourg
Bug#1012215: gradle-debian-helper: unknown option --add-opens breaks OpenJDK 11 packages
gradle-debian-helper/2.2 already checks if the JDK supports modules before adding the --add-opens options, but it checks the default JDK and not the one specified by JAVA_HOME, that's why it fails when OpenJDK 8 is used.
Bug#1012215: marked as pending in gradle-debian-helper
Control: tag -1 pending Hello, Bug #1012215 in gradle-debian-helper reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/gradle-debian-helper/-/commit/5a3769b9bda5a581a38be6bdd694676bc24b83ed Check the JDK specified by JAVA_HOME before adding --add-opens to the gradle command line (Closes: #1012215) (this message was generated automatically) -- Greetings https://bugs.debian.org/1012215
Bug#1012215: gradle-debian-helper: unknown option --add-opens breaks OpenJDK 11 packages
The --add-opens option was introduced in Java 9, so this shouldn't cause an issue with Java 11. What error did you get?
Bug#1011131: josm: FTBFS with JavaCC 6
Le 17/05/2022 à 17:37, Sebastiaan Couwenberg a écrit : In the upstream issue it's noted that javacc 6.1.3 was never released: " This tagged release may or may not be released, but is tagged here so that we maintain a history prior to merging in Francis' substantial changes. " https://github.com/javacc/javacc/releases/tag/release_6_1_3 Good catch, and the tag has now been removed. Would you consider downgrading to 6.1.2? No I'll instead upgrade to the latest 7.x release, that's the version expected by javaparser. Emmanuel Bourg
Bug#1011131: josm: FTBFS with JavaCC 6
Source: josm Version: 0.0.svn18427+dfsg-1 Severity: serious Tags: ftbfs Justification: FTBFS josm fails to build with JavaCC 6: [javac] /<>/src/ch/poole/openinghoursparser/OpeningHoursParserTokenManager.java:1182: error: incompatible types: possible lossy conversion from int to char [javac] throw new TokenMgrError(EOFSeen, curLexState, error_line, error_column, error_after, curChar, TokenMgrError.LEXICAL_ERROR); [javac] ^ This can be fixed by building with the javacc5 package instead of javacc
Bug#1010558: jetty9: FTBFS An API incompatibility was encountered while executing org.apache.maven.plugins:maven-assembly-plugin
Le 04/05/2022 à 13:10, Markus Koschany a écrit : I have just discovered that jetty9 fails to build from source. An API incompatibility was encountered while executing org.apache.maven.plugins:maven-assembly-plugin Probably some recently upgraded reverse-dependency is to blame here. Thank you for reporting the issue Markus, this is caused by an incompatibility in plexus-archiver/4.2.7-1. The fix will be uploaded soon. Emmanuel Bourg
Bug#1004482: liblog4j1.2-java: CVE-2022-23307 CVE-2022-23305 CVE-2022-23302
Le 31/01/2022 à 00:47, Markus Koschany a écrit : Thanks tony! I'm currently rebuilding all reverse-dependencies of log4j1.2. So far it looks like I was right and there is no package that actually requires one of the affected classes to build. None of the affected features are enabled by default hence why I would rather prefer the sledgehammer approach and just remove them. What doesn't exist can't be exploited. At least this makes sense for stable and oldstable distributions right now. +1 I suggest to file bugs against all those packages with severity normal and ask to migrate to log4j2. If we don't make a lot of progress within the next six months then we could consider packaging reload4j, although I would rather avoid to package (and maintain) a fork of an obsolete project. We may also pick the reload4j changes and apply them on top of log4j1.2, that should induce less work (no extra package, no dependency change, no migration to a new API). Emmanuel Bourg
Bug#991006: marked as pending in openjdk-11-jre-dcevm
Control: tag -1 pending Hello, Bug #991006 in openjdk-11-jre-dcevm reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/openjdk-11-jre-dcevm/-/commit/9ccd8295c4e900c467dd8ec48bad0b678705c886 New upstream release (Closes: #991006) (this message was generated automatically) -- Greetings https://bugs.debian.org/991006
Bug#986518: marked as pending in ant
Control: tag -1 pending Hello, Bug #986518 in ant reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/ant/-/commit/2bb010ec62b3f93a093fad405db13fa60c9aee22 Disable doclint only with the default doclet (Closes: #986518) (this message was generated automatically) -- Greetings https://bugs.debian.org/986518
Bug#958499: eclipse: fails to launch
Control: tags -1 + wontfix Control: done -1 Eclipse is no longer in Debian
Bug#982727: marked as pending in libbtm-java
Control: tag -1 pending Hello, Bug #982727 in libbtm-java reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/libbtm-java/-/commit/74b0b0d14c8af8881b1c0ca9bd4c98ae64c2decd Depend on the version-less jar of geronimo-jms (Closes: #982727) (this message was generated automatically) -- Greetings https://bugs.debian.org/982727
Bug#982710: marked as pending in maven-reporting-exec
Control: tag -1 pending Hello, Bug #982710 in maven-reporting-exec reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/maven-reporting-exec/-/commit/92bb314f697862c1639ba8a7628bb3646ffea8bf Depend on eclipse-sisu instead of sonatype-sisu (Closes: #982710) (this message was generated automatically) -- Greetings https://bugs.debian.org/982710
Bug#982708: marked as pending in maven-resolver
Control: tag -1 pending Hello, Bug #982708 in maven-resolver reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/maven-resolver/-/commit/9b592443a7111695d2e1a398b5cfb14d3a5cbe16 Depend on guice instead of sisu-guice (Closes: #982708) (this message was generated automatically) -- Greetings https://bugs.debian.org/982708
Bug#982568: marked as pending in ehcache
Control: tag -1 pending Hello, Bug #982568 in ehcache reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/ehcache/-/commit/6d001ab9b7b708a623dcad74493b254c43336c9f Depend on libgeronimo-jta-1.2-spec-java instead of libgeronimo-jta-1.0.1b-spec-java (Closes: #982568) (this message was generated automatically) -- Greetings https://bugs.debian.org/982568
Bug#963444: marked as pending in epubcheck
Control: tag -1 pending Hello, Bug #963444 in epubcheck reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/epubcheck/-/commit/603ba4044057cb99815ef5b45eac21d1728a07a1 Fixed the build failure with the latest version of Guava (Closes: #963444) (this message was generated automatically) -- Greetings https://bugs.debian.org/963444
Bug#981886: intellij-community-idea build depends on openjdk-8-jdk-headless that will not be in bullseye
Le 2021-02-04 20:45, Adrian Bunk a écrit : Migration status: Blocked. Can't migrate due to a non-migratable dependency. Check status below. Build-Depends(-Arch): intellij-community-idea openjdk-8 (not considered) Invalidated by build-dependency intellij-community-idea was introduced to build kotlin but it isn't ready yet. It doesn't matter if it isn't in testing at this stage. Emmanuel Bourg
Bug#979058: marked as pending in geronimo-j2ee-connector-1.5-spec
Control: tag -1 pending Hello, Bug #979058 in geronimo-j2ee-connector-1.5-spec reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/geronimo-j2ee-connector-1.5-spec/-/commit/73faee1b2803b7a9be97d8e430b15ec795cbc576 Package adopted by the Java Team (Closes: #979058) (this message was generated automatically) -- Greetings https://bugs.debian.org/979058
Bug#979056: marked as pending in geronimo-jms-1.1-spec
Control: tag -1 pending Hello, Bug #979056 in geronimo-jms-1.1-spec reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/geronimo-jms-1.1-spec/-/commit/65f3683626e44242422a10c4d4cde45a241a0a03 Package adopted by the Java Team (Closes: #979056) (this message was generated automatically) -- Greetings https://bugs.debian.org/979056
Bug#980526: marked as pending in maven
Control: tag -1 pending Hello, Bug #980526 in maven reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/maven/-/commit/6dcafed3cd4deaacd5a491e3ffc6bab96c003457 Fixed the mh_resolve_dependencies error truncating the package dependencies (Closes: #980526) (this message was generated automatically) -- Greetings https://bugs.debian.org/980526
Bug#975197: marked as pending in jmock2
Control: tag -1 pending Hello, Bug #975197 in jmock2 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/jmock2/-/commit/cf2ba58b50572bda7dc688bf77e258bd620bc4d0 Fixed the build failure with junit 4.13 (Closes: #975197) (this message was generated automatically) -- Greetings https://bugs.debian.org/975197
Bug#957576: nagios4: ftbfs with GCC-10
Control: severity -1 important nagios4/4.4.6-2 currently in unstable seems to build fine with gcc-10/10.2.0-18 on the builders [1], so I guess this was fixed? I'm downgrading the severity to let nagios4 migrate to testing. Emmanuel Bourg [1] https://buildd.debian.org/status/package.php?p=nagios4=unstable
Bug#976915: service-wrapper-java: FTBFS on ppc64el: [exec] wrapper.c:(.text+0x3598): undefined reference to `pow'
Le 13/12/2020 à 00:38, Markus Koschany a écrit : > In this case I believe the RC severity is correct because the arch:any or jni > version of the package FTBFS on ppc64el. We should try to fix the problem on > ppc64el or, if upstream doesn't support ppc64el, remove the architecture from > the list of supported architectures in debian/control. As a side note, if we keep getting issues with service-wrapper-java I wonder if we could scrap it, systemd is now able to provide similar auto-restart features for services. Emmanuel Bourg
Bug#975842: google-api-client-java: FTBFS: Could not resolve dependencies for project com.google.api-client:google-api-client:jar:1.27.1
On 29/11/2020 06:37, tony mancill wrote: > Apologies for the earlier noise on this bug - I mistakenly closed it > during an upload of google-oauth-client-java - but I am not able to > reproduce this build failure, neither in a clean sid chroot nor during a > ratt rebuild of build-r-deps of google-oauth-client-java. I've fixed this issue yesterday, libopencensus-java was missing a dependency on libgrpc-java. Emmanuel Bourg
Bug#942814: libhibernate-validator-java: update to 5.3.6 breaks reverse-dependencies
On 25/09/2020 13:50, Markus Koschany wrote: > Why did you upgrade hibernate-validator to version 5.x when > no other package in Debian requires it? Wouldn't it have been > simpler to revert the upgrade instead of creating a separate > hibernate-validator4 package? The version 5.x is a prerequisite to upgrade Spring to the next major release. Also the version 4.x is no longer supported and security issues are frequently reported. The idea is to use libhibernate-validator4-java as a transitional package until all reverse dependencies are updated to use the version 5.x. Emmanuel Bourg
Bug#942814: libhibernate-validator-java: update to 5.3.6 breaks reverse-dependencies
On 24/09/2020 11:20, Paul Gevers wrote: > Ping. This bug is blocking the migration of libhibernate-validator-java > to testing (bug #953338). > > If no solution to this issue can be found, I think we should revert to > the previous version of libhibernate-validator-java. Hi Paul, The version 4.x has been packaged separately as libhibernate-validator4-java. libspring-java has been updated to use it but not the other reverse dependencies. Emmanuel Bourg
Bug#963979: marked as pending in libhibernate-validator4-java
Control: tag -1 pending Hello, Bug #963979 in libhibernate-validator4-java reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/libhibernate-validator4-java/-/commit/84b4d5684a00b71bb563fb64e3e2acd8e30cd0a6 Removed the Maven artifacts with the upstream version (Closes: #963979) (this message was generated automatically) -- Greetings https://bugs.debian.org/963979
Bug#941685: marked as pending in libspring-java
Control: tag -1 pending Hello, Bug #941685 in libspring-java reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/libspring-java/-/commit/fc4d5693031df4dd2e0f76c4e1f75ec5f88a0edc Depend on libhibernate-validator4-java instead of libhibernate-validator-java (Closes: #941685) (this message was generated automatically) -- Greetings https://bugs.debian.org/941685
Bug#963979: marked as pending in libhibernate-validator4-java
Control: tag -1 pending Hello, Bug #963979 in libhibernate-validator4-java reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/libhibernate-validator4-java/-/commit/c297582b72c1c04c18f5cc100617c029da584bd3 Renamed the /usr/share/java jar (Closes: #963979) (this message was generated automatically) -- Greetings https://bugs.debian.org/963979
Bug#963396: jimfs: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project jimfs: Compilation failure
On 06/08/2020 11:05, Andreas Tille wrote: > [INFO] - > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] > /build/jimfs-1.1/jimfs/src/main/java/com/google/common/jimfs/PathService.java:[290,30] > error: is not abstract and > does not override abstract method test(Object) in Predicate Have you tried setting the source/target level to Java 8? Just add this to debian/maven.properties: maven.compiler.source=8 maven.compiler.target=8 Emmanuel Bourg
Bug#963443: marked as pending in apache-curator
Control: tag -1 pending Hello, Bug #963443 in apache-curator reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/apache-curator/-/commit/18d45d4cbf3c5f55de16233657761c770f1c3a9d Set the source/target level to Java 8 (Closes: #963443) (this message was generated automatically) -- Greetings https://bugs.debian.org/963443
Bug#963385: marked as pending in airlift-airline
Control: tag -1 pending Hello, Bug #963385 in airlift-airline reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/airlift-airline/-/commit/9149b0dba8c982c4bb93f8d462c4b1a99cc026e8 Set the source/target level to Java 8 (Closes: #963385) (this message was generated automatically) -- Greetings https://bugs.debian.org/963385
Bug#954684: marked as pending in ant-contrib
Control: tag -1 pending Hello, Bug #954684 in ant-contrib reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/ant-contrib/-/commit/fe0d18fe4822c2db6fcd5b1b11b1a50a93e3a7cc Disabled the broken verifydesign tests (Closes: #954684) (this message was generated automatically) -- Greetings https://bugs.debian.org/954684
Bug#963362: marked as pending in guice
Control: tag -1 pending Hello, Bug #963362 in guice reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/guice/-/commit/3217752ffaaf7c573313a27e4029c94e16aa15b9 Generate Java 8 compatible bytecode (Closes: #963362) (this message was generated automatically) -- Greetings https://bugs.debian.org/963362
Bug#964908:
On 17/07/2020 16:04, Thomas Kotzian wrote: > i have narrowed to problem down to an old version of the bnd tool. > > bnd in the debian repos is 3.5.0 - which seemed to work for tomcat9 up to > 9.0.36. > > tomcat9 9.0.37 changed the format of the bnd-file > res/bnd/tomcat-coyote.jar.tmp.bnd to use the instruction "-includepackage:" > which is only found in bnd 4.x and newer. > > the solution to the problem seems an update to bnd debian package or using > tomcat bnd 5.1.1 which gets downloaded in the official builds. Thank you for spotting the issue. Upgrading bnd isn't straightforward, I'll try to modify the bnd configuration instead. Emmanuel Bourg
Bug#952370: marked as pending in javatools
Control: tag -1 pending Hello, Bug #952370 in javatools reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/javatools/-/commit/73afb66e2f9ff2b07c32d7518367b0998285bc06 jh_manifest: Fix the error when the jar processed doesn't have a manifest (Closes: #952370) (this message was generated automatically) -- Greetings https://bugs.debian.org/952370
Bug#952370: #952370 not fixed yet
Le 28/06/2020 à 10:47, Niko Tyni a écrit : > The actual fix for #952370 seems to be missing, I only see a changelog > entry in the debdiff. > > At least cronometer_0.9.9+dfsg-3 still fails to build. > > Reopening. Thank you for spotting this mistake Niko, it looks like I've erased the fix just before uploading. I'll upload it again. Emmanuel Bourg
Bug#932749: marked as pending in eclipselink
Control: tag -1 pending Hello, Bug #932749 in eclipselink reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/eclipselink/-/commit/4e33fe7d9d6504251a9d9cf713e93da0856cff40 Include the embedded libraries in eclipselink.jar (Closes: #932749) (this message was generated automatically) -- Greetings https://bugs.debian.org/932749
Bug#952370: marked as pending in javatools
Control: tag -1 pending Hello, Bug #952370 in javatools reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/javatools/-/commit/d0ad9d7da3c3d9c6355e762309c4509535fcbab6 jh_manifest: Fix the error when the jar processed doesn't have a manifest (Closes: #952370) (this message was generated automatically) -- Greetings https://bugs.debian.org/952370
Bug#942876: openjdk-11-jre-dcevm: Doesn't start up anymore after updating openjdk-11-jre
Le 14/05/2020 à 17:10, Ruedi Steinmann a écrit : > According to upstream the issue is fixed now. Just tried the version 11.0.7+1 and it looks good now. Uploading soon. Emmanuel Bourg
Bug#961839: closure-compiler: FTBFS: is not abstract and does not override abstract method test(Object) in Predicate
Le 31/05/2020 à 19:36, tony mancill a écrit : > Thank you for the bug report. This is due to the recent Guava update > from 19.0 -> 29.0. test() was introduced in version 21. Somewhat > ironically, test() appears to lack any Javadoc [1] because it was added > to more closely emulate java.util.function.Predicate [2] and use of the > Guava Predicate is discouraged by its authors anyway [3]. If that helps, building closure-compiler with source/target=8 should fix this issue. I did that for Gradle this week to fix the same issue. Emmanuel Bourg
Bug#961298: jodd: CVE-2018-21234: Potential vulnerability in JSON deserialization
Control: severity -1 important Le 22/05/2020 à 22:51, Salvatore Bonaccorso a écrit : > The following vulnerability was published for jodd. I'm filling it as > RC severity since altough one might dispute the severity for the issue > itself, it looks that in Debian there was ever only one upload of > jodd, there are no reverse (build) dependencies neither. > > Is the package acutally of some use or planned use? Thank you for the report Salvatore. jodd is a new dependency of JMeter 3, I haven't finished the packaging yet. Note that the fix for CVE-2018-21234 merely adds an optional whitelisting feature to check the classes being deserialized. But the default behavior is still the same (no check), so the charge of addressing the vulnerability is actually shifted to the applications using jodd. Emmanuel Bourg
Bug#952292: marked as pending in groovycsv
Control: tag -1 pending Hello, Bug #952292 in groovycsv reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/groovycsv/-/commit/0cea0e079f09240a98099224ebfd70382ee155cf Updated the opencsv groupId in the pom (Closes: #952292) (this message was generated automatically) -- Greetings https://bugs.debian.org/952292
Bug#960828: marked as pending in eclipse-jdt-debug
Control: tag -1 pending Hello, Bug #960828 in eclipse-jdt-debug reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/eclipse-jdt-debug/-/commit/57553b94f695ade292e3caa2afbdbdbb4b0b20de Fixed the version of libeclipse-jdt-debug-ui-java (Closes: #960828) (this message was generated automatically) -- Greetings https://bugs.debian.org/960828
Bug#959565: libjdom2-intellij-java: FTBFS: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configuration ':contrib:co
Control: reassign -1 libxalan2-java Control: found -1 2.7.2-3 Control: severity -1 important Control: affects -1 + libjdom2-intellij-java Control: retitle -1 libxalan2-java: xml-apis dependency left in the xalan:serializer pom The actual issue is with libxalan2-java, because the xalan:serializer pom depends on xml-apis but the package doesn't depend on libjaxp1.3-java.
Bug#959567: marked as done (dom4j: FTBFS: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configuration ':testCompile
> Caused by: org.gradle.internal.resolve.ModuleVersionResolveException: Could > not resolve xml-apis:xml-apis:debian. > Required by: > project : > xalan:xalan:debian > xalan:serializer:debian The actual issue is with libxalan2-java, because the xalan:serializer pom depends on xml-apis but the package doesn't depend on libjaxp1.3-java. Any package depending on xalan is likely to fail similarly. The xml-apis artifact contains the javax.xml classes now integrated in the JDK. In most cases this dependency can be dropped (from the poms and the packages dependencies). Emmanuel Bourg
Bug#956585: openjfx: FTBFS on all making openjfx uninstallable
Le 19/04/2020 à 20:57, Sebastiaan Couwenberg a écrit : > 11.0.7+0-2 still FTBFS on arm64 & mips*, will you still file the RM bugs > for openjfx & zeroc-ice to unblock the testing migration or shall I? Yes go ahead with the RM, thank you for the help. Emmanuel Bourg
Bug#956585: openjfx: FTBFS on all making openjfx uninstallable
Le 13/04/2020 à 19:34, Sebastiaan Couwenberg a écrit : > It looks like the changes in openjfx (11.0.7+0-2) won't be enough to fix > the FTBFS on mips* as well. I've noticed a segfault in the build log on mips64el. I have no idea how to address this, this sounds like a compiler bug. > Will openjfx & zeroc-ice be removed from those architectures to allow it > to migrate to testing if that's the case? I'll request the mips binaries to be removed if it still doesn't work. Emmanuel Bourg
Bug#956585: marked as pending in openjfx
Control: tag -1 pending Hello, Bug #956585 in openjfx reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/openjfx/-/commit/4eea096659d3b386ad8ded4b28e73ad09e7a6c7d Disable the Gradle version check when building only the arch all package (Closes: #956585) (this message was generated automatically) -- Greetings https://bugs.debian.org/956585
Bug#942876: openjdk-11-jre-dcevm: Doesn't start up anymore after updating openjdk-11-jre
Le 22/10/2019 à 19:20, Michael Meier a écrit : > java -dvecm can't be executed anymore: > > java -dcevm > java: relocation error: /usr/lib/jvm/java-11-openjdk-amd64/lib/libjava.so: > symbol JVM_InitializeFromArchive version SUNWprivate_1.1 not defined in file > libjvm.so with link time reference > > This seems to be the case since yesterday my system updated openjdk-11-jre to > version 11.0.5 from the security repository I've updated openjdk-11-jre-dcevm to the version 11.0.5+5 but it's still broken: $ java -dcevm -version [0.009s][error][class] Invalid layout of java.lang.StackFrameInfo field: bci type: S Error occurred during initialization of VM Invalid layout of preloaded class: use -Xlog:class+load=info to see the origin of the problem class The issue has been forwarded upstream: https://github.com/HotswapProjects/openjdk-jdk11u-dcevm/issues/6
Bug#952351: marked as pending in plexus-build-api
Control: tag -1 pending Hello, Bug #952351 in plexus-build-api reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/plexus-build-api/commit/5a5212d965505bc8fd1861b04bcc5110b2695bb3 Fixed the compatibility with plexus-utils 3.3 (Closes: #952351) (this message was generated automatically) -- Greetings https://bugs.debian.org/952351
Bug#938892: marked as pending in zookeeper
Control: tag -1 pending Hello, Bug #938892 in zookeeper reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/zookeeper/commit/46462122ff90ca7758f87100d9cdd129920aa0a2 Build the Python bindings with Python 3 (Closes: #938892) (this message was generated automatically) -- Greetings https://bugs.debian.org/938892
Bug#925473: tomcat9: sysvinit script missing (Policy §9.11¶2 “must”)
Hi Thorsten, The issue I reported that prevented systemd-sysusers from being used without systemd as the init system has just been fixed (#926316). So in theory we should be able to use it with other init systems. But the fact that elogind conflicts with systemd creates another hurdle. If the conflict can't be lifted I can see two solutions, either elogind provides its own version of systemd-sysusers, or systemd-sysusers is extracted into an independent package that doesn't conflict with elogind (I've filed #946456 for that). Emmanuel Bourg
Bug#940723: java-package requires libgtk-3-0 and libcairo-gobject2 to build java8 221
Control: severity -1 normal
Bug#866704: guacamole-client FTBFS: guacamole-common-js failure
Control: reassign -1 libmaven-assembly-plugin-java Control: found -1 2.4.1-2 Control: fixed -1 2.4.1-3 Control: close -1 On Sat, 01 Jul 2017 09:04:00 +0300 Adrian Bunk wrote: > [[1;31mERROR[m] Failed to execute goal > [32morg.apache.maven.plugins:maven-assembly-plugin:2.4.1:attached[m > [1m(make-zip)[m on project [36mguacamole-common-js[m: [1;31mExecution > make-zip of goal > org.apache.maven.plugins:maven-assembly-plugin:2.4.1:attached failed: An API > incompatibility was encountered while executing > org.apache.maven.plugins:maven-assembly-plugin:2.4.1:attached: > java.lang.NoSuchMethodError: > org.codehaus.plexus.interpolation.object.FieldBasedObjectInterpolator.interpolate(Ljava/lang/Object;Lorg/codehaus/plexus/interpolation/Interpolator;Lorg/codehaus/plexus/interpolation/RecursionInterceptor;)V[m This is a duplicate of #866855 which was fixed two years ago.
Bug#910423: guacamole: broken symlink: /usr/share/guacamole/guacamole/WEB-INF/lib/stax-api.jar -> ../../../../java/stax-api.jar
Control: severity -1 normal On Sat, 06 Oct 2018 08:07:40 +0200 Andreas Beckmann wrote: > Is guacamole missing a dependency on libstax-java ? The StAX API is a standard API of the JDK since Java 6, so the missing stax-api.jar link has no effect at runtime. Emmanuel Bourg
Bug#940108: nexus: FTBFS with GCC 9: dereferencing pointer to incomplete type 'mxml_node_t' error
Control: retitle -1 nexus: FTBFS with mxml 3 Le 12/09/2019 à 15:32, Emmanuel Bourg a écrit : > With the Java 9 fix applied (#893383) nexus still fails to build, > I assume due to more strict checks by GCC 9: Actually the build failure was caused by the upgrade of mxml to the version 3 last month. With the version 2 from Buster it builds fine. @Alastair: any hint how to fix this? Is this due to the _mxml_index_s struct being moved to mxml-private.h and thus no longer exposed by libmxml-dev? Emmanuel Bourg
Bug#873992: marked as pending in libusb-java
Control: tag -1 pending Hello, Bug #873992 in libusb-java reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/libusb-java/commit/84c374ea97b3c3c1d18be903f27586e94238afe8 Update java-compat.patch and fix FTBFS with Java 9 (Closes: #873992) (this message was generated automatically) -- Greetings https://bugs.debian.org/873992
Bug#912538: marked as pending in libjaba-client-java
Control: tag -1 pending Hello, Bug #912538 in libjaba-client-java reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/libjaba-client-java/commit/787624c0f3f43c8abf44547a355c678acc3fb72c Fixed the build failure with Java 11 (Closes: #912538) (this message was generated automatically) -- Greetings https://bugs.debian.org/912538
Bug#917759: marked as pending in openhft-chronicle-wire
Control: tag -1 pending Hello, Bug #917759 in openhft-chronicle-wire reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/openhft-chronicle-wire/commit/5a9a0ff828511d6f6e4a0c3e3619f7f0d3d37dfc Added the missing build dependency on libeasymock-java (Closes: #917759) (this message was generated automatically) -- Greetings https://bugs.debian.org/917759
