Bug#898821: maven-plugin-tools: FTBFS with Java 10 due to com.sun.tools.doclets removal
Le 22/11/2018 à 15:45, Emmanuel Bourg a écrit : > This issue has been "solved" upstream in the version 3.6 by dropping > support for javadoc annotations. This means we have to convert the > plugins still using these javadoc annotations to use the Java > annotations instead [2]. I misanalysed the issue, it's the Javadoc taglets which were removed in the version 3.6, not the support for defining plugins with javadoc tags (this is implemented using doxia and doesn't rely on internal JDK classes anyway). The taglets are only used when generating the javadoc of a plugin and this never happens in Debian. So no need to update all the plugins still using javadoc tags.
Bug#914566: RM: pleiades -- ROM; No longer used
Package: ftp.debian.org Severity: normal Hi, Please remove the pleiades package. It contains a Japanese translation plug-in for Eclipse but it's about to be removed (#914448). Thank you, Emmanuel Bourg
Bug#914503: RM: plexus-cdc -- ROM; No longer used, replaced by plexus-component-metadata
Package: ftp.debian.org Severity: normal Hi, Please remove the plexus-cdc package. It is no longer used and along plexus-maven-plugin it has been replaced by libplexus-component-metadata-java. Thank you, Emmanuel Bourg
Bug#914502: RM: plexus-maven-plugin -- ROM; No longer used, replaced by plexus-component-metadata
Package: ftp.debian.org Severity: normal Hi, Please remove the plexus-maven-plugin package. It's no longer used and has been replaced by libplexus-component-metadata-java from src:plexus-containers. Thank you, Emmanuel Bourg
Bug#914497: RM: tomcat7 -- ROM; No longer used
Package: ftp.debian.org Severity: normal Hi, Please remove the src:tomcat7 package. It only builds the libservlet3.0-java package but it is no longer used, it has been replaced by libservlet3.1-java. Thank you, Emmanuel Bourg
Bug#914467: RM: swt-gtk -- ROM; No longer used, superseded by swt4-gtk
Package: ftp.debian.org Severity: normal Hi, Please remove the swt-gtk package. It's an old version of SWT that was only used for the needs of src:eclipse, and it's about to be removed (#914448). swt4-gtk should now be used instead. Thank you, Emmanuel Bourg
Bug#914466: RM: icu4j-49 -- ROM; Obsolete, no longer used
Package: ftp.debian.org Severity: normal Hi, Please remove the icu4j-49 package. It's an old version of ICU4J that was only used for the needs of src:eclipse, and it's about to be removed (#914448). Thank you, Emmanuel Bourg
Bug#914463: RM: icu4j-4.2 -- ROM; Obsolete, no longer used
Package: ftp.debian.org Severity: normal Hi, Please remove the src:icu4j-4.2 package. It's an old version of ICU4J that was only used for the needs of lucene2, and it's about to be removed (#914450). Thank you, Emmanuel Bourg
Bug#914452: RM: asm3 -- ROM; Obsolete, no longer used
Package: ftp.debian.org Severity: normal Hi, Please remove the src:asm3 package. It's an old version of ASM that was only used for the needs of src:eclipse, and it's about to be removed (#914448). Thank you, Emmanuel Bourg
Bug#914450: RM: lucene2 -- ROM; Obsolete, no longer used
Package: ftp.debian.org Severity: normal Hi, Please remove the src:lucene2 package. It's an old version of Lucene that was only used for the needs of src:eclipse, and it's about to be removed (#914448). Thank you, Emmanuel Bourg
Bug#914448: RM: eclipse -- ROM; Old and unmaintained, replaced by finer-grained libraries
Package: ftp.debian.org Severity: normal Hi, Please remove the src:eclipse package. This package contains an old version of the Eclipse IDE that hasn't been updated since 2012. The package fails to build and the IDE is no longer suitable for the version of Java shipped in Debian (OpenJDK 11). Smaller library packages have been uploaded to replace the big monolithic eclipse package, and the eclipse reverse dependencies have all been updated to use these new packages. The Eclipse IDE may return in Debian under a different form if motivated and skilled developpers step forward for maintaining it. Just contact the Java Team: debian-j...@lists.debian.org Thank you, Emmanuel Bourg
Bug#898821: maven-plugin-tools: FTBFS with Java 10 due to com.sun.tools.doclets removal
Control: tags -1 + fixed-upstream This issue has been "solved" upstream in the version 3.6 by dropping support for javadoc annotations. This means we have to convert the plugins still using these javadoc annotations to use the Java annotations instead [2]. [1] https://issues.apache.org/jira/browse/MPLUGIN-336 [2] https://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/using-annotations.html
Bug#914291: jaxrs-api: copyright file wrong
Le 21/11/2018 à 19:57, Thorsten Glaser a écrit : > Why don’t you just change the copyright file and upload a > fix instead of trying to weasel out causing a lengthy > discussion? That would save time. I will when I have to update the package. But I disagree with the severity and the urgency. I have more pressing issues on my todo list and this bug is just a distraction. Emmanuel Bourg
Bug#914291: jaxrs-api: copyright file wrong
Control: severity -1 normal The license changed in the version 2.1.1 because the project was donated to the Eclipse Foundation. There is no code change between the version 2.1 under the CDDL+GPL and the version 2.1.1 under the EPL+GPL. So it's still correct to state that the code is licensed under the CDDL.
Bug#783938: openjdk-11: Reproducible timestamp in javadoc files
Control: tags -1 + patch
Here is a patch adding SOURCE_DATE_EPOCH support to the javadoc tool.
Description: Makes the timestamp in the javadoc files reproducible when
SOURCE_DATE_EPOCH is specified
Author: Emmanuel Bourg
Forwarded: no
---
a/src/jdk.javadoc/share/classes/jdk/javadoc/internal/doclets/formats/html/markup/Head.java
+++
b/src/jdk.javadoc/share/classes/jdk/javadoc/internal/doclets/formats/html/markup/Head.java
@@ -256,6 +256,9 @@
*/
public Content toContent() {
Date now = showTimestamp ? calendar.getTime() : null;
+if (now != null && System.getenv("SOURCE_DATE_EPOCH") != null) {
+now = new Date(1000 *
Long.parseLong(System.getenv("SOURCE_DATE_EPOCH")));
+}
HtmlTree tree = new HtmlTree(HtmlTag.HEAD);
if (showGeneratedBy) {
@@ -269,6 +272,9 @@
if (showMetaCreated) {
SimpleDateFormat dateFormat = new SimpleDateFormat("-MM-dd");
+if (System.getenv("SOURCE_DATE_EPOCH") != null) {
+dateFormat.setTimeZone(TimeZone.getTimeZone("UTC"));
+}
tree.addContent(HtmlTree.META(
(htmlVersion == HtmlVersion.HTML5) ? "dc.created" : "date",
dateFormat.format(now)));
@@ -298,7 +304,14 @@
private Comment getGeneratedBy(boolean timestamp, Date now) {
String text = "Generated by javadoc"; // marker string, deliberately
not localized
if (timestamp) {
-text += " ("+ docletVersion + ") on " + now;
+text += " ("+ docletVersion + ") on ";
+if (System.getenv("SOURCE_DATE_EPOCH") == null) {
+text += now;
+} else {
+SimpleDateFormat fmt = new SimpleDateFormat("-MM-dd
HH:mm:ss z");
+fmt.setTimeZone(TimeZone.getTimeZone("UTC"));
+text += fmt.format(now);
+}
}
return new Comment(text);
}
Bug#914278: openjdk-11: Reproducible properties file header when SOURCE_DATE_EPOCH is specified
Source: openjdk-11
Severity: normal
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps toolchain
When writing a properties file using the java.util.Properties class, a header
containing the current date is automatically added. This renders the output non
reproducible.
Here is a patch for java.util.Properties checking if the SOURCE_DATE_EPOCH
environment variable is specified and using it instead of the current date
for the timestamp.
Description: Makes the timestamp in the properties files header reproducible
when SOURCE_DATE_EPOCH is specified
Author: Emmanuel Bourg
Forwarded: no
--- a/src/java.base/share/classes/java/util/Properties.java
+++ b/src/java.base/share/classes/java/util/Properties.java
@@ -905,7 +905,7 @@
if (comments != null) {
writeComments(bw, comments);
}
-bw.write("#" + new Date().toString());
+bw.write("#" + getFormattedTimestamp());
bw.newLine();
synchronized (this) {
for (Map.Entry e : entrySet()) {
@@ -1555,4 +1555,22 @@
}
this.map = map;
}
+
+/**
+ * Returns a formatted timestamp to be used in the properties file header.
+ * The date used is the current date, unless the SOURCE_DATE_EPOCH
+ * environment variable is specified. In this case the format used is
+ * locale and timezone insensitive to ensure the output is reproducible.
+ */
+private String getFormattedTimestamp() {
+if (System.getenv("SOURCE_DATE_EPOCH") == null) {
+return new Date().toString();
+} else {
+// Use the SOURCE_DATE_EPOCH timestamp and make the format
locale/timezone insensitive
+java.text.SimpleDateFormat fmt = new
java.text.SimpleDateFormat("-MM-dd HH:mm:ss z", java.util.Locale.ENGLISH);
+fmt.setTimeZone(java.util.TimeZone.getTimeZone("UTC"));
+Date date = new Date(1000 *
Long.parseLong(System.getenv("SOURCE_DATE_EPOCH")));
+return fmt.format(date);
+}
+}
}
Bug#914098: RM: plexus-utils -- ROM; Replaced by plexus-utils2
Package: ftp.debian.org Severity: normal Hi, Please remove the src:plexus-utils, it has been replaced by src:plexus-utils2. Starting with the version 3.1.0-1 libplexus-utils2-java now provides the same artifacts installed by libplexus-utils-java. The libplexus-utils2-java package now declares a Breaks, Replaces and Provides for libplexus-utils-java. Thank you, Emmanuel Bourg
Bug#800998: wagon: depends on obsolete libcommons-httpclient-java library
Control: fixed -1 3.0.0-1 Control: close -1 This issue has been fixed when the package was upgraded from the version 1.x to 3.x.
Bug#897566: freeplane freezes while entering text node under OpenJDK 10
Hi Ben, Could you try again with OpenJDK 11 please? This is the new default Java runtime now. Emmanuel Bourg On Sun, 6 May 2018 11:03:42 +1200 Ben Caradoc-Davies wrote: > On 05/05/18 20:01, Felix Natter wrote: > > Freeplane upstream has made me aware that this is an OpenJDK issue: > > https://bugs.openjdk.java.net/browse/JDK-8202580 > > This very well fits your logs: > >at > >sun.java2d.pipe.ShapeSpanIterator.lineTo(java.desktop@10.0.1/Native > >Method) > > So I think we can close this bug since it's not something fixable in > > Freeplane? Please use OpenJDK-9 meanwhile. > > Thanks, Felix. That looks convincing. I agree that this is an OpenJDK > issue, so I will reassign this to openjdk-10 and set forwarded to the > OpenJDK issue. I will test again when OpenJDK 10 is fixed. Until then I > am using a wrapper script to set OpenJDK 8. > > Kind regards, > > -- > Ben Caradoc-Davies > Director > Transient Software Limited <https://transient.nz/> > New Zealand > >
Bug#894359: Help needed to port beast2-mcmc to Java 9
On Mon, 9 Apr 2018 13:24:51 +0200 Andreas Tille wrote: > [javac] import com.sun.org.apache.xerces.internal.dom.CoreDocumentImpl; > [javac] ^ > [javac] > /build/beast2-mcmc-2.4.8+dfsg/src/beast/util/XMLParserUtils.java:120: > warning: CoreDocumentImpl is internal proprietary API and may be removed in a > future release > [javac] ((CoreDocumentImpl) doc).putIdentifier(id, > (Element) node); > [javac] ^ > [javac] /build/beast2-mcmc-2.4.8+dfsg/src/beast/util/TreeParser.java:353: > error: cannot find symbol > [javac] CharStream charStream = CharStreams.fromString(newick); > [javac] ^ > [javac] symbol: variable CharStreams > [javac] location: class TreeParser > [javac] > /build/beast2-mcmc-2.4.8+dfsg/src/beast/util/treeparser/NewickLexer.java:98: > error: method does not override or implement a method from a supertype > [javac] @Override > [javac] ^ Hi Andreas, I've pushed a fix for this issue and now beast2-mcmc builds fine with antlr 4.6. Could you give it a try? If it works that would allow us to move forward without waiting for antlr 4.7. Emmanuel Bourg
Bug#894353: ikvm build depends on openjdk-8-jdk
IKVM has been abandoned upstream [1] and it looks unlikely to be ported to Java 11+ in the near future. ikvm has no reverse dependencies and a low popcon, maybe the package should be removed? [1] http://weblog.ikvm.net/#a33ea525f-a291-418a-bd6a-abdf22d0662b
Bug#913575: SEVERE: Cannot resolve dependencies in ./fop-servlet/pom.xml: Dependency not found org.apache.xmlgraphics:batik-all:jar:debian
Le 12/11/2018 à 13:54, Mathieu Malaterre a écrit : > It should be possible to tweak the package to remove the following > from mh_make on user side: Hi Mathieu, Looking at the log I fail to understand the issue. Could you be more specific on the behavior you expect and why? Emmanuel Bourg
Bug#912392: scilab FTBFS with OpenJDK 11
Control: tags -1 + patch I sent a merge request on Salsa [1]. It's only build tested, please check if it's also ok at runtime. [1] https://salsa.debian.org/science-team/scilab/merge_requests/2
Bug#912392: scilab FTBFS with OpenJDK 11
Later the build fails when generating the javadoc, because the "--add-modules=java.activation,java.xml.bind" option was specified to build with Java 9, but these modules have been removed in Java 11.
Bug#908884: i2p: FTBFS (autobuilder hangs)
severity 908884 important fixed 908884 8.5.35-1 close 908884
Bug#912392: scilab FTBFS with OpenJDK 11
With javax.activation.jar added to the classpath the build now fails due to the removal of JAXB: [javac] import javax.xml.bind.JAXBContext; [javac] ^ [javac] /build/scilab-6.0.1/modules/xcos/src/java/org/scilab/modules/xcos/palette/PaletteManager.java:27: error: package javax.xml.bind does not exist [javac] import javax.xml.bind.JAXBException; [javac] ^ [javac] /build/scilab-6.0.1/modules/xcos/src/java/org/scilab/modules/xcos/palette/PaletteManager.java:28: error: package javax.xml.bind does not exist [javac] import javax.xml.bind.Marshaller; [javac] ^ So a new dependency on libjaxb-java is also needed.
Bug#912392: scilab FTBFS with OpenJDK 11
The @Generated annotations can be safely removed, they only have a documentation purpose at the source level. But after removing them there is another issue related to the removal of the javax.activation API in Java 11: [javac] /build/scilab-6.0.1/modules/helptools/src/java/org/scilab/modules/helptools/image/ImageConverter.java:33: error: package javax.activation does not exist [javac] import javax.activation.MimetypesFileTypeMap; [javac]^ [javac] /build/scilab-6.0.1/modules/helptools/src/java/org/scilab/modules/helptools/image/ImageConverter.java:50: error: cannot find symbol [javac] private MimetypesFileTypeMap mimeMap = new MimetypesFileTypeMap(); [javac] ^ [javac] symbol: class MimetypesFileTypeMap [javac] location: class ImageConverter [javac] 2 errors [javac] 3 warnings
Bug#913193: buildd.debian.org: Assign a mipsel/mips64el builder to *-backports
Package: buildd.debian.org Severity: normal Hi, The mipsel/mips64el build queues for stretch-backports currently have a backlog of 97 packages, the last package was built 38 days ago. The builders have been busy with the sid/experimental uploads for over a month. It would be nice if at least one mipsel builder prioritize the backports over experimental (and maybe sid) to avoid blocking the queue for such a long time. Thank you, Emmanuel Bourg
Bug#913190: bash-completion: Update 'java' completion to support '.java' files
Package: bash-completion Version: 1:2.8-2 Severity: wishlist User: debian-j...@lists.debian.org Usertags: default-java11 .java files used to be compiled into .class files with 'javac' and then executed with 'java', but starting with Java 11 the explicit compilation can be skipped and the file executed directly. For example: java Test.java It would be nice if the bash completion could handle this case. Currently the completion works only for the .class files.
Bug#912516: libcommons-lang3-java FTBFS with OpenJDK 11
Control: retitle -1 libcommons-lang3-java FTBFS with easymock 4.0 Control: user debian-j...@lists.debian.org Control: usertag -1 - default-java11 This is actually a regression caused by easymock 4.0 which was recently uploaded. The package builds fine with OpenJDK 11 and easymock 3.6
Bug#913132: libfile-stripnondeterminism-perl: Java 11 javadoc support
Here is the related merge request: https://salsa.debian.org/reproducible-builds/strip-nondeterminism/merge_requests/2
Bug#913132: libfile-stripnondeterminism-perl: Java 11 javadoc support
Package: libfile-stripnondeterminism-perl Version: 0.043-2 Severity: normal Tags: patch Hi, The output of the javadoc tool changed in Java 11, the timestamp in the HTML header is now in a element named 'dc.created' instead of 'date'. For example: I'll open a merge request on Salsa with a fix. Emmanuel Bourg
Bug#912221: jabref: incompatible with openjdk 11
Hi Tony, Le 06/11/2018 à 21:12, tony mancill a écrit : > XJC="java -cp > /usr/share/java/xml-resolver.jar:/usr/share/java/jaxb-api.jar:/usr/share/java/jaxb-core.jar:/usr/share/java/jaxb-impl.jar:/usr/share/java/jaxb-jxc.jar:/usr/share/java/jaxb-xjc.jar > -jar /usr/share/java/jaxb-xjc.jar" > > And it dies with this exception stack, despite the xml-resolver being on > the classpath: The -cp parameter doesn't work with -jar, that's why you keep getting the ClassNotFoundException. Either all the jar files are specified behind -cp and the main class is specified on the command line (i.e. com.sun.tools.xjc.XJCFacade for xjc), or the jar executed has a proper Class-Path attribute in its manifest (and indeed xml-resolver.jar isn't listed in jaxb-xjc.jar). > Can you help me understand why this patch > (https://salsa.debian.org/java-team/jaxb/blob/master/debian/patches/04-xml-resolver-compatibility.patch) > was necessary? Perhaps it's related to the failure I'm seeing? I don't think it's related. We simply use a different version of xml-resolver. There is this rule in debian/maven.rules: s/com.sun.org.apache.xml.internal/xml-resolver/ s/resolver/xml-resolver/ Sun/Oracle had to change the namespace of the libraries they embedded in the JDK to avoid conflicts. But now that JAXB is no longer in the JDK it's not needed, and we can directly use the original library instead. > I've also started looking at updating jaxb 2.3.1, but it will > take me a bit of time. I've also started digging into jaxb to address the compatibility with Java 11. I've considered upgrading to the version 2.3.1 but it didn't look that straightforward despite the minor version increment. I'm not sure the upgrade is still compatible with Java 8 for example. So I think I'll rather aim at a minor update simply adding the dependency on libactivation-java, and later look at an upgrade. Emmanuel Bourg
Bug#838356: fixed in jboss-annotations-1.2-api 1.0.0-1
Hi Timo, We already have the javax.annotation API in the geronimo-annotation-1.3-spec package. Is it really necessary to duplicate it? Emmanuel Bourg
Bug#912221: jabref: incompatible with openjdk 11
On 01/11/2018 01:54, tony mancill wrote: > I am definitely open to (and appreciative of) your suggestions. Hi Tony, even if the jaxb package doesn't yet provide the xjc executable (#905357), you can invoke it with: java -jar /usr/share/java/jaxb-xjc.jar Emmanuel Bourg
Bug#641880: Please create default-jdk-source
Le 30/10/2018 à 13:10, Thorsten Glaser a écrit : > As the GCJ stuff is now gone, nothing should block this any more. > Can this please be added now (if for nothing else then for consistency)? Patches or pull requests on Salsa are welcome :)
Bug#912233: checkstyle FTBFS with OpenJDK 11
Control: retitle: checkstyle: FTBFS with saxonhe 9.9.0 Control: user debian-j...@lists.debian.org Control: usertag -1 - default-java11 This issue is actually caused by the upload of saxonhe 9.9.0 last week.
Bug#912221: jabref: incompatible with openjdk 11
Le 30/10/2018 à 00:41, gregor herrmann a écrit : > I guess we need to make sure that we build with openjdk-8. > (You know this better than me but I seem to remember that the plan > was to keep openjdk-8 in buster for building packages?) No please don't built with openjdk-8 if there is a workaround with openjdk-11. Building with openjdk-8 is really a last resort solution, and very few cases justify its use (see lombok for a good example). Emmanuel Bourg
Bug#912221: jabref: incompatible with openjdk 11
Le 29/10/2018 à 13:54, gregor herrmann a écrit : > Now that openjdk 11 is the default, jabref won't start without some > help: > > % jabref > Error occurred during initialization of boot layer > java.lang.module.FindException: Module java.se.ee not found jabref should no longer use the java.se.ee module, it was a temporary module in Java 9 & 10 now removed in Java 11. jabref should add jaxb to its classpath instead. Emmanuel Bourg
Bug#912266: tomcat7 FTBFS with OpenJDK 11
Control: tags -1 + wontfix src:tomcat7 builds one package, libservlet3.0-java, which is only used by eclipse. Once eclipse is removed tomcat7 will follow.
Bug#912257: ITP: eclipse-jdt-ui -- User interface for the Eclipse Java IDE
Package: wnpp Severity: wishlist Owner: Emmanuel Bourg * Package name: eclipse-jdt-ui Version : 3.7.3 Upstream Author : Eclipse Foundation, Inc. * URL : https://www.eclipse.org/jdt/ui/ * License : EPL-1.0 Programming Lang: Java Description : User interface for the Eclipse Java IDE Eclipse JDT UI implements the user interface for the Java IDE. It provides several workbench contributions for viewing and manipulating Java code: * Package Explorer View - shows the Java element tree as defined by a project's build class path * Type Hierarchy View - shows the sub- and supertype hierarchies * Java Outline View - shows the structure of a Java compilation unit or class file * Java Browsing Perspecitve - allows navigating the Java model using separate views for projects, packages, types and memebers. * Wizards for creating Java elements - Java project, package, class, interface * Java Editor - syntax coloring, content specific code assist, code resolve, method level edit, import assistance, quick fix and quick assist In addition to these workbench elements the following functions are provided: * Refactoring support - Extract Method, Safe Rename and Moving with reference updates, Self Encapsulate Field etc. * Java searching - find declarations of and/or references to packages, types, methods, and fields, scoped to the workspace, a working set, or the current selection. * Java aware structured compare - determine and present changes to individual Java methods. It supports to replace individual Java elements with a version of an element from the local history. This package will be maintained by the Java Team. It's required to transition away from the old src:eclipse package.
Bug#912217: elki: Build with default-jdk instead of openjdk-8
Source: elki Version: 0.7.1-7 Severity: serious Tags: sid buster User: debian-j...@lists.debian.org Usertags: default-java11 Please change the build dependency to use default-jdk instead of openjdk-8. OpenJDK 11 is the default JDK for Buster and we'd like to ship only one JDK per release. Thank you, Emmanuel Bourg
Bug#895695: elki FTBFS: java.base/jdk.internal.loader.ClassLoaders$AppClassLoader cannot be cast to java.base/java.net.URLClassLoader
Le 29/10/2018 à 13:08, Erich Schubert a écrit : > This precise bug has been fixed, as can be seen from the changelog and > this patch: > > https://sources.debian.org/src/elki/0.7.1-9/debian/patches/java9-classloader.patch/ Thank you for the reference, I should have checked the patches, sorry. I'll file another bug for the build dependency. Emmanuel Bourg
Bug#895695: elki FTBFS: java.base/jdk.internal.loader.ClassLoaders$AppClassLoader cannot be cast to java.base/java.net.URLClassLoader
Control: reopen -1 Control: notfixed -1 0.7.1-7 Control: user debian-j...@lists.debian.org Control: usertag -1 + default-java9 Control: tags -1 + sid buster fixed-upstream I'm reopening the bug because the compatibility with Java 9 and later wasn't really fixed, the JDK was just reverted to openjdk-8. openjdk-11 will be the default JDK in Buster, the upstream fix should be applied instead, and the build dependency changed back to default-jdk.
Bug#912211: openjdk-11: Add support for DEB_BUILD_OPTIONS=terse
Source: openjdk-11 Severity: wishlist Tags: patch Since the Debian Policy 4.2.0 the new "terse" build option can be used to have less verbose build logs. I suggested supporting it in openjdk-11 with the following change to debian/rules: --- a/debian/rules +++ b/debian/rules @@ -328,7 +328,9 @@ ifeq (,$(filter $(DEB_HOST_ARCH), $(hotspot_archs))) CONFIGURE_ARGS += --enable-zero endif -EXTRA_BUILD_ENV += MAKE_VERBOSE=y QUIETLY= LOG=debug +ifneq (,$(filter $(DEB_BUILD_OPTIONS), terse)) + EXTRA_BUILD_ENV += MAKE_VERBOSE=y QUIETLY= LOG=debug +endif # timestamp skew on kFreeBSD EXTRA_BUILD_ENV += IGNORE_OLD_CONFIG=true
Bug#909063: apacheds: package installation fails due to incorrect apacheds.service unit
Le 27/10/2018 à 15:44, Dominik George a écrit : > Patch against git master is attached. This happened during the BSP in > Karlsruhe, so I will NMU to DELAYED/5 tomorrow before the BSP ends if you do > not object, and also ask the release team about inclusion in the next point > release. Thank you for the fix Dominik. Could you commit the changes to the Salsa repository and do a team upload instead of a NMU please?
Bug#911936: ITP: eclipse-jdt-debug -- Java debugging support for the Eclipse Platform
Package: wnpp Severity: wishlist Owner: Emmanuel Bourg * Package name: eclipse-jdt-debug Version : 4.7.3 Upstream Author : Eclipse Foundation, Inc. * URL : https://projects.eclipse.org/projects/eclipse.jdt.debug * License : EPL-1.0 Programming Lang: Java Description : Java debugging support for the Eclipse Platform Eclipse JDT Debug implements Java debugging support and works with any JDPA-compliant target Java VM. It is implemented on top of the language independent "debug model" provided by the platform debugger. This package will be maintained by the Java Team. It's required to transition away from the old src:eclipse package.
Bug#894359: Now we have antlr 4.6 - any chance to get 4.7 soon (Was: beast-mcmc2: Cannot find symbol CharStreams.fromString(newick))
Control: tags 911286 + pending Control: tags 911302 + pending Le 19/10/2018 à 16:42, Andrius Merkys a écrit : > updating antlr4 to 4.7 requires two new Debian packages, > libmojo-executor-java (ITP #911286) and libstring-template-maven-plugin-java > (ITP #911302). I have pushed their packaging to Salsa: > > * https://salsa.debian.org/merkys-guest/mojo-executor > * https://salsa.debian.org/merkys-guest/string-template-maven-plugin > (build-depends on libmojo-executor-java) > > It would be great if you could review and, if possible, sponsor them. I've uploaded mojo-executor and string-template-maven-plugin, they are awaiting in the NEW queue for the FTP masters approval. Thanks a lot Andrius. Emmanuel Bourg
Bug#911694: openjdk-11: Tighten the dependency on debhelper (requires 10.3 or higher)
Source: src:openjdk-11 Severity: normal openjdk-11 build-depends on debhelper (>= 9.20141010), but it uses dh_missing which was only introduced in debhelper 10.3.
Bug#911681: RM: libconcurrentlinkedhashmap-java -- ROM; Never used, deprecated
Package: ftp.debian.org Severity: normal Hi, Please remove the libconcurrentlinkedhashmap-java, it was packaged as part of an effort 8 years ago to bring Grails (#473213) and Cassandra (#585905) to Debian but the packagings were never completed. Now noth Grails and Cassandra have moved to the successor of concurrentlinkedhashmap, Caffeine Cache [1][2]. The library has been deprecated upstream and it's unlikely this package will be ever used. Thank you, Emmanuel Bourg [1] https://github.com/grails/grails-core/issues/624 [2] https://issues.apache.org/jira/browse/CASSANDRA-10855
Bug#911547: debhelper gradle build system could cat hs_err_pid*.log on failure
Le 23/10/2018 à 15:44, Helmut Grohne a écrit : > "output" as in "make it recoverable from the build log". Essentially > that means printing to stdout or stderr, yes. > > So do you agree with the idea? The idea is interesting, it could be useful for maven-debian-helper too. The log can be quite long, so maybe displaying a message stating that the JVM crashed and left a hs_err_pid file would be enough, or just printing the header of the file which usually contains the main reason of the crash. Do you want to provide an implementation? Emmanuel Bourg
Bug#911679: RM: libswingx1-java -- ROM; No longer used, replaced by libswingx-java
Package: ftp.debian.org Severity: normal Hi, Please remove the libswingx1-java package. It'll no longer be used once pirl is removed (#911677) and it has been replaced by libswingx-java. Thank you, Emmanuel Bourg
Bug#911677: RM: pirl -- ROM; Orphaned, low popcon, dead upstream
Package: ftp.debian.org Severity: normal Hi, Please removed the pirl package, it has been orphaned for a year, has a very low popcon and is no longer active upstream (6 years old). Thank you, Emmanuel Bourg
Bug#911547: debhelper gradle build system could cat hs_err_pid*.log on failure
Le 21/10/2018 à 20:33, Helmut Grohne a écrit : > So what do you think about outputting hs_err_pid*.log when gradle fails? You mean printing hs_err_pid*.log on stderr if the build fails?
Bug#894359: Now we have antlr 4.6 - any chance to get 4.7 soon (Was: beast-mcmc2: Cannot find symbol CharStreams.fromString(newick))
Le 19/10/2018 à 17:14, Andreas Tille a écrit : > I have cloned > >https://salsa.debian.org/merkys-guest/mojo-executor > > to > >https://salsa.debian.org/java-team/mojo-executor > > where it should reside when maintained in Java Team. :-) @Andreas: We have a script [1] to create the repositories on Salsa. It's important to use it because it configures the IRC/BTS/mail hooks properly. [1] https://salsa.debian.org/java-team/pkg-java-scripts/blob/master/setup-salsa-repository
Bug#894359: Now we have antlr 4.6 - any chance to get 4.7 soon (Was: beast-mcmc2: Cannot find symbol CharStreams.fromString(newick))
Le 19/10/2018 à 17:14, Andreas Tille a écrit : > Moreover there are some lintian issues: > > I: mojo-executor-parent source: quilt-patch-missing-description > sonatype-to-eclipse.patch > W: libmojo-executor-java-doc: embedded-javascript-library > usr/share/doc/libmojo-executor-java/mojo-executor-maven-plugin/jquery/jquery-ui.structure.css > please use libjs-jquery-ui Thanks a lot for the packages Andrius, I'll review them. Two things: * We don't build the javadoc for the Maven plugins, because nobody calls the plugin API directly. * The jquery warnings can be ignored, this is a javadoc issue to be fixed at the openjdk level (if ever fixed). Emmanuel Bourg
Bug#911390: RM: openjdk-7-jre-dcevm/experimental -- ROM; Obsolete, no longer updated upstream
Package: ftp.debian.org Severity: normal Hi, Please remove the openjdk-7-jre-dcevm in experimental. I used it to prepare backports but it's now obsolete and I don't plan to use it again. Thank you, Emmanuel Bourg
Bug#911371: antlr4: package v4.7.1 and include Cpp libraries/headers
Hi Andrius, Le 19/10/2018 à 10:55, Andrius Merkys a écrit : > I have started packaging antlr4 v4.7.1. Apart from updating the existing > binary packages, I have packaged antlr4 Cpp libraries/headers, what seems to > be required at least by #902798 [1]. > > My packaging efforts are pushed to a fork on Salsa [2]. Thanks a lot for helping with antlr4! In the past we had an antlr package supporting several languages and it became difficult to maintain because the Java Team didn't have the skill to properly support the other runtimes. If possible I think the non Java stuff should be moved to another source packages maintained by the proper language team, such that the Java Team can freely upgrade antlr without affecting packages outside its scope. Here for example the version embedded in the name of new libantlr4-runtime4.7.1 package suggests that any update of antlr will have to go through the NEW queue, which is rather inconvenient. And if a Java maintainer wants to upgrade antlr he'll now have to manage a transition, sending bug reports, waiting for package updates, etc. Multiply this by the number of languages supported and it quickly turns in to a nightmare :) Emmanuel Bourg
Bug#911350: RM: eclipse-wtp -- ROM; FTBFS, outdated and unmaintained
Package: ftp.debian.org Severity: normal Hi, Please remove the eclipse-wtp package. It depends on the outdated and unmaintained src:eclipse package (last updated in 2013) which the Java Team plans to retire before the Buster release. Thank you, Emmanuel Bourg
Bug#911348: RM: eclipse-rse -- ROM; FTBFS, outdated and unmaintained
Package: ftp.debian.org Severity: normal Hi, Please remove the eclipse-rse package. It depends on the outdated and unmaintained src:eclipse package (last updated in 2013) which the Java Team plans to retire before the Buster release. Thank you, Emmanuel Bourg
Bug#911351: RM: eclipse-xsd -- ROM; FTBFS, outdated and unmaintained
Package: ftp.debian.org Severity: normal Hi, Please remove the eclipse-xsd package. It depends on the outdated and unmaintained src:eclipse package (last updated in 2013) which the Java Team plans to retire before the Buster release. Thank you, Emmanuel Bourg
Bug#911349: RM: eclipse-subclipse -- ROM; FTBFS, outdated and unmaintained
Package: ftp.debian.org Severity: normal Hi, Please remove the eclipse-subclipse package. It depends on the outdated and unmaintained src:eclipse package (last updated in 2013) which the Java Team plans to retire before the Buster release. Thank you, Emmanuel Bourg
Bug#911346: RM: eclipse-remote-services-api -- ROM; FTBFS, outdated and unmaintained
Package: ftp.debian.org Severity: normal Hi, Please remove the eclipse-remote-services-api package. It depends on the outdated and unmaintained src:eclipse package (last updated in 2013) which the Java Team plans to retire before the Buster release. Thank you, Emmanuel Bourg
Bug#911319: RM: eclipse-pydev -- ROM; FTBFS, outdated and unmaintained
Package: ftp.debian.org Severity: normal Hi, Please remove the eclipse-pydev package. It depends on the outdated and unmaintained src:eclipse package (last updated in 2013) which the Java Team plans to retire before the Buster release. Thank you, Emmanuel Bourg
Bug#911318: RM: eclipse-ptp -- ROM; FTBFS, outdated and unmaintained
Package: ftp.debian.org Severity: normal Hi, Please remove the eclipse-ptp package. It depends on the outdated and unmaintained src:eclipse package (last updated in 2013) which the Java Team plans to retire before the Buster release. Thank you, Emmanuel Bourg
Bug#911317: RM: eclipse-mylyn-tasks-github -- ROM; FTBFS, outdated and unmaintained
Package: ftp.debian.org Severity: normal Hi, Please remove the eclipse-mylyn-tasks-github package. It depends on the outdated and unmaintained src:eclipse package (last updated in 2013) which the Java Team plans to retire before the Buster release. Thank you, Emmanuel Bourg
Bug#911316: RM: eclipse-mylyn -- ROM; FTBFS, outdated and unmaintained
Package: ftp.debian.org Severity: normal Hi, Please remove the eclipse-mylyn package. It depends on the outdated and unmaintained src:eclipse package (last updated in 2013) which the Java Team plans to retire before the Buster release. Thank you, Emmanuel Bourg
Bug#911314: RM: eclipse-linuxtools -- ROM; FTBFS, outdated and unmaintained
Package: ftp.debian.org Severity: normal Hi, Please remove the eclipse-linuxtools package. It depends on the outdated and unmaintained src:eclipse package (last updated in 2013) which the Java Team plans to retire before the Buster release. Thank you, Emmanuel Bourg
Bug#911315: RM: eclipse-mercurialeclipse -- ROM; FTBFS, outdated and unmaintained
Package: ftp.debian.org Severity: normal Hi, Please remove the eclipse-mercurialeclipse package. It depends on the outdated and unmaintained src:eclipse package (last updated in 2013) which the Java Team plans to retire before the Buster release. Thank you, Emmanuel Bourg
Bug#911309: RM: eclipse-gef -- ROM; FTBFS, outdated and unmaintained
Package: ftp.debian.org Severity: normal Hi, Please remove the eclipse-gef package. It depends on the outdated and unmaintained src:eclipse package (last updated in 2013) which the Java Team plans to retire before the Buster release. Thank you, Emmanuel Bourg
Bug#911308: RM: eclipse-egit -- ROM; FTBFS, outdated and unmaintained
Package: ftp.debian.org Severity: normal Hi, Please remove the eclipse-egit package. It depends on the outdated and unmaintained src:eclipse package (last updated in 2013) which the Java Team plans to retire before the Buster release. Thank you, Emmanuel Bourg
Bug#911306: RM: eclipse-cdt-pkg-config -- ROM; FTBFS, outdated and unmaintained
Package: ftp.debian.org Severity: normal Hi, Please remove the eclipse-cdt-pkg-config package. It depends on the outdated and unmaintained src:eclipse package (last updated in 2013) which the Java Team plans to retire before the Buster release. Thank you, Emmanuel Bourg
Bug#911307: RM: eclipse-eclox -- ROM; FTBFS, outdated and unmaintained
Package: ftp.debian.org Severity: normal Hi, Please remove the eclipse-eclox package. It depends on the outdated and unmaintained src:eclipse package (last updated in 2013) which the Java Team plans to retire before the Buster release. Thank you, Emmanuel Bourg
Bug#911305: RM: eclipse-cdt -- ROM; FTBFS, outdated and unmaintained
Package: ftp.debian.org Severity: normal Hi, Please remove the eclipse-cdt package. It depends on the outdated and unmaintained src:eclipse package (last updated in 2013) which the Java Team plans to retire before the Buster release. Thank you, Emmanuel Bourg
Bug#911304: RM: eclipse-anyedit -- ROM; FTBFS, outdated and unmaintained
Package: ftp.debian.org Severity: normal Hi, Please remove the eclipse-anyedit package. It depends on the outdated and unmaintained src:eclipse package (last updated in 2013) which the Java Team plans to retire before the Buster release. Thank you, Emmanuel Bourg
Bug#910698: dogtag-pki needs jdk8
Le 17/10/2018 à 07:11, Timo Aaltonen a écrit : > ldapjdk is built against jdk8 because jss/dogtag-pki still need it that > way or things will break. Though now I realized maybe it might still > work with -Dant.build.javac.target=1.8 (or whatever jdk8 uses). What errors do you get if you use the Java 11 compiled ldapjdk with jss/dogtag-pki?
Bug#911194: libbtm-java: FTBFS with Java 11 due to javax.rmi removal
Package: src:libbtm-java Severity: important Tags: sid buster User: debian-j...@lists.debian.org Usertags: default-java11 libbtm-java fails to build with Java 11, it's affected by the removal of the CORBA related classes which include the javax.rmi package: [javac] /build/libbtm-java-2.1.4/build.xml:45: warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to false for repeatable builds [javac] Using javac -source 1.5 is no longer supported, switching to 6 [javac] Using javac -target 1.5 is no longer supported, switching to 6 [javac] Compiling 136 source files to /build/libbtm-java-2.1.4/dist/classes [javac] warning: [options] bootstrap class path not set in conjunction with -source 6 [javac] warning: [options] source value 6 is obsolete and will be removed in a future release [javac] warning: [options] target value 1.6 is obsolete and will be removed in a future release [javac] warning: [options] To suppress warnings about obsolete options, use -Xlint:-options. [javac] /build/libbtm-java-2.1.4/src/bitronix/tm/resource/jms/JndiXAConnectionFactory.java:29: error: package javax.rmi does not exist [javac] import javax.rmi.PortableRemoteObject; [javac] ^ [javac] /build/libbtm-java-2.1.4/src/bitronix/tm/resource/jms/JndiXAConnectionFactory.java:216: error: cannot find symbol [javac] wrappedFactory = (XAConnectionFactory) PortableRemoteObject.narrow(lookedUpObject, XAConnectionFactory.class); [javac]^ [javac] symbol: variable PortableRemoteObject [javac] location: class JndiXAConnectionFactory [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. [javac] 2 errors [javac] 4 warnings
Bug#911193: eclipselink: FTBFS with Java 11 due to Java EE APIs removal
Source: eclipselink Severity: important Tags: sid buster User: debian-j...@lists.debian.org Usertags: default-java11 eclipselink fails to build with Java 11 due to the removal of several Java EE APIs (javax.xml.soap, javax.xml.ws, javax.rmi and CORBA) [javac] Compiling 3151 source files to /build/eclipselink-2.6.5/target/classes [javac] warning: [options] bootstrap class path not set in conjunction with -source 7 [javac] /build/eclipselink-2.6.5/org/eclipse/persistence/internal/dbws/ProviderHelper.java:16: error: package javax.xml.soap does not exist [javac] import static javax.xml.soap.SOAPConstants.SOAP_1_2_PROTOCOL; [javac] ^ [javac] /build/eclipselink-2.6.5/org/eclipse/persistence/internal/dbws/ProviderHelper.java:16: error: static import only from classes and interfaces [javac] import static javax.xml.soap.SOAPConstants.SOAP_1_2_PROTOCOL; [javac] ^ [javac] /build/eclipselink-2.6.5/org/eclipse/persistence/internal/dbws/ProviderHelper.java:17: error: package javax.xml.soap does not exist [javac] import static javax.xml.soap.SOAPConstants.URI_NS_SOAP_1_1_ENVELOPE; [javac] ^ [javac] /build/eclipselink-2.6.5/org/eclipse/persistence/internal/dbws/ProviderHelper.java:17: error: static import only from classes and interfaces [javac] import static javax.xml.soap.SOAPConstants.URI_NS_SOAP_1_1_ENVELOPE; [javac] ^ [javac] /build/eclipselink-2.6.5/org/eclipse/persistence/internal/dbws/ProviderHelper.java:18: error: package javax.xml.soap does not exist [javac] import static javax.xml.soap.SOAPConstants.URI_NS_SOAP_1_2_ENVELOPE; [javac] ^ [javac] /build/eclipselink-2.6.5/org/eclipse/persistence/internal/dbws/ProviderHelper.java:18: error: static import only from classes and interfaces [javac] import static javax.xml.soap.SOAPConstants.URI_NS_SOAP_1_2_ENVELOPE; [javac] ^ [javac] /build/eclipselink-2.6.5/org/eclipse/persistence/internal/dbws/ProviderHelper.java:19: error: package javax.xml.ws.handler does not exist [javac] import static javax.xml.ws.handler.MessageContext.INBOUND_MESSAGE_ATTACHMENTS; [javac] ^ [javac] /build/eclipselink-2.6.5/org/eclipse/persistence/internal/dbws/ProviderHelper.java:19: error: static import only from classes and interfaces [javac] import static javax.xml.ws.handler.MessageContext.INBOUND_MESSAGE_ATTACHMENTS; [javac] ^ [javac] /build/eclipselink-2.6.5/org/eclipse/persistence/internal/dbws/SOAPResponseWriter.java:19: error: package javax.xml.soap does not exist [javac] import static javax.xml.soap.SOAPConstants.SOAP_1_2_PROTOCOL; [javac] ^ [javac] /build/eclipselink-2.6.5/org/eclipse/persistence/internal/dbws/SOAPResponseWriter.java:19: error: static import only from classes and interfaces [javac] import static javax.xml.soap.SOAPConstants.SOAP_1_2_PROTOCOL; [javac] ^ [javac] /build/eclipselink-2.6.5/org/eclipse/persistence/internal/dbws/SOAPResponseWriter.java:20: error: package javax.xml.soap does not exist [javac] import static javax.xml.soap.SOAPConstants.URI_NS_SOAP_1_1_ENVELOPE; [javac] ^ [javac] /build/eclipselink-2.6.5/org/eclipse/persistence/internal/dbws/SOAPResponseWriter.java:20: error: static import only from classes and interfaces [javac] import static javax.xml.soap.SOAPConstants.URI_NS_SOAP_1_1_ENVELOPE; [javac] ^ [javac] /build/eclipselink-2.6.5/org/eclipse/persistence/internal/dbws/SOAPResponseWriter.java:21: error: package javax.xml.soap does not exist [javac] import static javax.xml.soap.SOAPConstants.URI_NS_SOAP_1_2_ENVELOPE; [javac] ^ [javac] /build/eclipselink-2.6.5/org/eclipse/persistence/internal/dbws/SOAPResponseWriter.java:21: error: static import only from classes and interfaces [javac] import static javax.xml.soap.SOAPConstants.URI_NS_SOAP_1_2_ENVELOPE; [javac] ^ [javac] /build/eclipselink-2.6.5/org/eclipse/persistence/internal/dbws/SOAPResponseWriter.java:34: error: package javax.xml.soap does not exist [javac] import javax.xml.soap.AttachmentPart; [javac] ^ [javac] /build/eclipselink-2.6.5/org/eclipse/persistence/internal/dbws/SOAPResponseWriter.java:35: error: package javax.xml.soap does not exist [javac] import javax.xml.soap.MessageFactory; [javac] ^ [javac] /build/eclipselink-2.6.5/org/eclipse/persistence/internal/dbws/SOAPResponseWriter.java:36: error: package javax.xml.soap does not exist [javac] import javax.xml.soap.SOAPBody; [javac] ^ [javac] /build/eclipselink-2.6.5/org/eclipse/persistence/internal/dbws/SOAPResponseWriter.java:37: error: package javax.xml.soap does not exist [javac] import javax.xml.soap.SOAPException; [java
Bug#911190: openjpa: FTBFS with Java 11 due to JAXB removal
Source: openjpa Severity: important Tags: sid buster User: debian-j...@lists.debian.org Usertags: default-java11 openjpa fails to build with Java 11 due to the removal of JAXB: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project openjpa-jdbc: Compilation failure: Compilation failure: [ERROR] /build/openjpa-2.4.2/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/meta/strats/XMLValueHandler.java:[25,22] package javax.xml.bind does not exist [ERROR] /build/openjpa-2.4.2/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/meta/strats/XMLValueHandler.java:[26,22] package javax.xml.bind does not exist [ERROR] /build/openjpa-2.4.2/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/meta/strats/XMLValueHandler.java:[27,22] package javax.xml.bind does not exist [ERROR] /build/openjpa-2.4.2/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/meta/strats/XMLValueHandler.java:[28,22] package javax.xml.bind does not exist [ERROR] /build/openjpa-2.4.2/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/meta/strats/XMLValueHandler.java:[78,13] cannot find symbol [ERROR] symbol: class JAXBContext [ERROR] location: class org.apache.openjpa.jdbc.meta.strats.XMLValueHandler [ERROR] /build/openjpa-2.4.2/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/meta/strats/XMLValueHandler.java:[78,30] cannot find symbol [ERROR] symbol: variable JAXBContext [ERROR] location: class org.apache.openjpa.jdbc.meta.strats.XMLValueHandler [ERROR] /build/openjpa-2.4.2/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/meta/strats/XMLValueHandler.java:[84,13] cannot find symbol [ERROR] symbol: class Marshaller [ERROR] location: class org.apache.openjpa.jdbc.meta.strats.XMLValueHandler [ERROR] /build/openjpa-2.4.2/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/meta/strats/XMLValueHandler.java:[91,16] cannot find symbol [ERROR] symbol: class JAXBException [ERROR] location: class org.apache.openjpa.jdbc.meta.strats.XMLValueHandler [ERROR] /build/openjpa-2.4.2/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/meta/strats/XMLValueHandler.java:[107,13] cannot find symbol [ERROR] symbol: class JAXBContext [ERROR] location: class org.apache.openjpa.jdbc.meta.strats.XMLValueHandler [ERROR] /build/openjpa-2.4.2/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/meta/strats/XMLValueHandler.java:[107,30] cannot find symbol [ERROR] symbol: variable JAXBContext [ERROR] location: class org.apache.openjpa.jdbc.meta.strats.XMLValueHandler [ERROR] /build/openjpa-2.4.2/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/meta/strats/XMLValueHandler.java:[108,13] cannot find symbol [ERROR] symbol: class Unmarshaller [ERROR] location: class org.apache.openjpa.jdbc.meta.strats.XMLValueHandler [ERROR] /build/openjpa-2.4.2/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/meta/strats/XMLValueHandler.java:[112,16] cannot find symbol [ERROR] symbol: class JAXBException [ERROR] location: class org.apache.openjpa.jdbc.meta.strats.XMLValueHandler
Bug#911188: libjdo-api-java: FTBFS with Java 11 due to javax.rmi removal
Package: src:libjdo-api-java Version: 3.1-2 Severity: important Tags: sid buster User: debian-j...@lists.debian.org Usertags: default-java11 libjdo-api-java fails to build with Java 11, it's affected by the removal of the CORBA related classes which include the javax.rmi package: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project jdo-api: Compilation failure: Compilation failure: [ERROR] /build/libjdo-api-java-3.1/api/src/java/javax/jdo/JDOHelper.java:[58,16] error: package javax.rmi does not exist [ERROR] /build/libjdo-api-java-3.1/api/src/java/javax/jdo/JDOHelper.java:[1785,47] error: cannot find symbol [ERROR] symbol: variable PortableRemoteObject [ERROR] location: class JDOHelper
Bug#911187: axis: FTBFS with Java 11 due to javax.rmi and CORBA removal
Source: axis
Severity: important
Tags: sid buster
User: debian-j...@lists.debian.org
Usertags: default-java11
axis fails to build with Java 11 due to the removal of the javax.rmi
and org.omg.CORBA packages:
[javac]
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:25:
error: package org.omg.CORBA does not exist
[javac] import org.omg.CORBA.ORB;
[javac] ^
[javac]
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:26:
error: package org.omg.CosNaming does not exist
[javac] import org.omg.CosNaming.NameComponent;
[javac] ^
[javac]
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:27:
error: package org.omg.CosNaming does not exist
[javac] import org.omg.CosNaming.NamingContext;
[javac] ^
[javac]
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:28:
error: package org.omg.CosNaming does not exist
[javac] import org.omg.CosNaming.NamingContextHelper;
[javac] ^
[javac]
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:85:
error: cannot find symbol
[javac] ORB orb = ORB.init(new String[0], orbProps);
[javac] ^
[javac] symbol: class ORB
[javac] location: class CORBAProvider
[javac]
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:85:
error: cannot find symbol
[javac] ORB orb = ORB.init(new String[0], orbProps);
[javac] ^
[javac] symbol: variable ORB
[javac] location: class CORBAProvider
[javac]
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:88:
error: cannot find symbol
[javac] NamingContext root =
NamingContextHelper.narrow(orb.resolve_initial_references("NameService"));
[javac] ^
[javac] symbol: class NamingContext
[javac] location: class CORBAProvider
[javac]
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:88:
error: cannot find symbol
[javac] NamingContext root =
NamingContextHelper.narrow(orb.resolve_initial_references("NameService"));
[javac] ^
[javac] symbol: variable NamingContextHelper
[javac] location: class CORBAProvider
[javac]
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:89:
error: cannot find symbol
[javac] NameComponent nc = new NameComponent(nameId, nameKind);
[javac] ^
[javac] symbol: class NameComponent
[javac] location: class CORBAProvider
[javac]
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:89:
error: cannot find symbol
[javac] NameComponent nc = new NameComponent(nameId, nameKind);
[javac]^
[javac] symbol: class NameComponent
[javac] location: class CORBAProvider
[javac]
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:90:
error: cannot find symbol
[javac] NameComponent[] ncs = {nc};
[javac] ^
[javac] symbol: class NameComponent
[javac] location: class CORBAProvider
[javac]
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:91:
error: package org.omg.CORBA does not exist
[javac] org.omg.CORBA.Object corbaObject = root.resolve(ncs);
[javac] ^
[javac]
/build/axis-1.4/src/org/apache/axis/providers/java/CORBAProvider.java:101:
error: package org.omg.CORBA does not exist
[javac] private static final Class[] CORBA_OBJECT_CLASS = new Class[]
{org.omg.CORBA.Object.class};
[javac]
^
[javac]
/build/axis-1.4/src/org/apache/axis/providers/java/EJBProvider.java:129: error:
package javax.rmi does not exist
[javac] Object ehome = javax.rmi.PortableRemoteObject.narrow(ejbHome,
homeClass);
[javac] ^
[javac]
/build/axis-1.4/src/org/apache/axis/providers/java/EJBProvider.java:254: error:
package javax.rmi does not exist
[javac] Object ehome = javax.rmi.PortableRemoteObject.narrow(ejbHome,
homeClass);
[javac] ^
Bug#911183: logback: FTBFS with Java 11 due to sun.reflect.Reflection removal
Source: logback Severity: important Tags: sid buster User: debian-j...@lists.debian.org Usertags: default-java11 logback fails to build with Java due to the removal of the sun.reflect package: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project logback-classic: Compilation failure: Compilation failure: [ERROR] /build/logback-1.2.3/logback-classic/src/main/java/ch/qos/logback/classic/spi/PackagingDataCalculator.java:[20,19] cannot find symbol [ERROR] symbol: class Reflection [ERROR] location: package sun.reflect [ERROR] /build/logback-1.2.3/logback-classic/src/main/java/ch/qos/logback/classic/spi/PackagingDataCalculator.java:[45,13] cannot find symbol [ERROR] symbol: variable Reflection [ERROR] location: class ch.qos.logback.classic.spi.PackagingDataCalculator [ERROR] /build/logback-1.2.3/logback-classic/src/main/java/ch/qos/logback/classic/spi/PackagingDataCalculator.java:[85,31] cannot find symbol [ERROR] symbol: variable Reflection [ERROR] location: class ch.qos.logback.classic.spi.PackagingDataCalculator
Bug#911182: libquartz-java: FTBFS with Java 11 due to javax.rmi removal
Package: src:libquartz-java Severity: important Tags: sid buster User: debian-j...@lists.debian.org Usertags: default-java11 libquartz-java fails to build with Java 11, it's affected by the removal of the CORBA related classes which include the javax.rmi package: [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /build/libquartz-java-1.8.6/quartz/src/main/java/org/quartz/jobs/ee/ejb/EJBInvokerJob.java:[31,17] package javax.rmi does not exist [ERROR] /build/libquartz-java-1.8.6/quartz/src/main/java/org/quartz/jobs/ee/ejb/EJBInvokerJob.java:[163,41] cannot find symbol symbol: variable PortableRemoteObject location: class org.quartz.jobs.ee.ejb.EJBInvokerJob [ERROR] /build/libquartz-java-1.8.6/quartz/src/main/java/org/quartz/jobs/ee/ejb/EJBInvokerJob.java:[182,33] cannot find symbol symbol: variable PortableRemoteObject location: class org.quartz.jobs.ee.ejb.EJBInvokerJob
Bug#911181: sitemesh: FTBFS with Java 11 due to javax.rmi removal
Source: sitemesh Severity: important Tags: sid buster User: debian-j...@lists.debian.org Usertags: default-java11 sitemesh fails to build with Java 11, it's affected by the removal of the CORBA related classes which include the javax.rmi package: [javac] /build/sitemesh-2.4.1+dfsg/src/java/com/opensymphony/module/sitemesh/Factory.java:17: error: package javax.rmi does not exist [javac] import javax.rmi.PortableRemoteObject; [javac] ^ [javac] /build/sitemesh-2.4.1+dfsg/src/java/com/opensymphony/module/sitemesh/Factory.java:94: error: cannot find symbol [javac] result = (String)PortableRemoteObject.narrow(o, String.class); // rmi-iiop friendly. [javac] ^ [javac] symbol: variable PortableRemoteObject [javac] location: class Factory
Bug#890624: RM? Outdated, no rdeps, broken deps
Control: unblock 888255 by 890624 Control: tags -1 + wontfix Control: close -1 apache-curator doesn't depend on netty-3.9.
Bug#880359: Still happening in 11+26-4
Le 16/10/2018 à 12:51, Frédéric Bonnard a écrit :
> That worked fine and the packages were created.
> I checked the diff between ppc64el debc and mips debc and there
> wasn't anything noticeable to me.
Thanks a lot for investigating this issue Frédéric! I checked the
src:icu package and there is only an icudt62l.dat file in the source
tree. Maybe adding icudt51{b,e}.zip symlinks to icudt51l.zip would also
work.
Do you want to upload the fix as a team upload.
Emmanuel Bourg
Bug#911142: cofoja: FTBFS with Java 11 due to UnsupportedOperationException in ClassVisitor.visitNestHostExperimental()
Source: cofoja Severity: important Tags: sid buster User: debian-j...@lists.debian.org Usertags: default-java11 cofoja fails to build with Java 11 with the following error: /build/cofoja-1.3/build.xml:269: The following error occurred while executing this line: /build/cofoja-1.3/build.xml:179: java.lang.instrument.IllegalClassFormatException at com.google.java.contract.core.agent.ContractClassFileTransformer.transformWithContracts(ContractClassFileTransformer.java:302) at com.google.java.contract.core.agent.PreMain.instrument(PreMain.java:190) at PreAgentAntTask.execute(PreAgentAntTask.java:73) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99) at org.apache.tools.ant.Task.perform(Task.java:350) at java.base/java.util.Vector.forEach(Vector.java:1387) at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:67) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99) at org.apache.tools.ant.Task.perform(Task.java:350) at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.java:391) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99) at org.apache.tools.ant.Task.perform(Task.java:350) at org.apache.tools.ant.Target.execute(Target.java:449) at org.apache.tools.ant.Target.performTasks(Target.java:470) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1388) at org.apache.tools.ant.Project.executeTarget(Project.java:1361) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1251) at org.apache.tools.ant.Main.runBuild(Main.java:834) at org.apache.tools.ant.Main.startAnt(Main.java:223) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101) Caused by: java.lang.UnsupportedOperationException at org.objectweb.asm.ClassVisitor.visitNestHostExperimental(ClassVisitor.java:158) at org.objectweb.asm.ClassReader.accept(ClassReader.java:541) at org.objectweb.asm.ClassReader.accept(ClassReader.java:391) at com.google.java.contract.core.agent.ContractClassFileTransformer.extractContracts(ContractClassFileTransformer.java:363) at com.google.java.contract.core.agent.ContractClassFileTransformer.transformWithContracts(ContractClassFileTransformer.java:298) ... 33 more It probably needs an updated version of libasm-java.
Bug#911139: jaxrs-api: FTBFS with Java 11 due to missing Maven dependencies
Source: jaxrs-api Version: 2.1.2-1 Severity: important Tags: sid buster newcomer User: debian-j...@lists.debian.org Usertags: default-java11 jaxrs-api fails to build with Java 11 due to missing Maven dependencies activated in a JDK 11 profile: [ERROR] Failed to execute goal on project jakarta.ws.rs-api: Could not resolve dependencies for project jakarta.ws.rs:jakarta.ws.rs-api:bundle:2.1.2: The following artifacts could not be resolved: javax.xml.bind:jaxb-api:jar:debian, javax.activation:javax.activation-api:jar:debian, org.glassfish.jaxb:jaxb-runtime:jar:debian: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact javax.xml.bind:jaxb-api:jar:debian has not been downloaded from it before. -> [Help 1] Adding the corresponding build dependencies to the package should fix this issue.
Bug#911138: libhibernate-validator-java: FTBFS with Java 11 due to JAXB removal
Package: src:libhibernate-validator-java Version: 4.3.3-5 Severity: important Tags: sid buster User: debian-j...@lists.debian.org Usertags: default-java11 libhibernate-validator-java still fails to build with Java 11 due to the removal of JAXB: [ERROR] diagnostic: /<>/engine/src/main/java/org/hibernate/validator/internal/xml/XmlMappingParser.java:40: error: package javax.xml.bind does not exist import javax.xml.bind.JAXBContext; ^ [ERROR] diagnostic: /<>/engine/src/main/java/org/hibernate/validator/internal/xml/XmlMappingParser.java:41: error: package javax.xml.bind does not exist import javax.xml.bind.JAXBElement; ^ [ERROR] diagnostic: /<>/engine/src/main/java/org/hibernate/validator/internal/xml/XmlMappingParser.java:42: error: package javax.xml.bind does not exist import javax.xml.bind.JAXBException; ^ [ERROR] diagnostic: /<>/engine/src/main/java/org/hibernate/validator/internal/xml/XmlMappingParser.java:43: error: package javax.xml.bind does not exist import javax.xml.bind.Unmarshaller; ^ [ERROR] diagnostic: /<>/engine/target/generated-sources/jaxb/org/hibernate/validator/internal/xml/ConstraintDefinitionType.java:11: error: package javax.xml.bind.annotation does not exist import javax.xml.bind.annotation.XmlAccessType; ^ [ERROR] diagnostic: /<>/engine/target/generated-sources/jaxb/org/hibernate/validator/internal/xml/ConstraintDefinitionType.java:12: error: package javax.xml.bind.annotation does not exist import javax.xml.bind.annotation.XmlAccessorType; ^ [ERROR] diagnostic: /<>/engine/target/generated-sources/jaxb/org/hibernate/validator/internal/xml/ConstraintDefinitionType.java:13: error: package javax.xml.bind.annotation does not exist import javax.xml.bind.annotation.XmlAttribute; ^ [ERROR] diagnostic: /<>/engine/target/generated-sources/jaxb/org/hibernate/validator/internal/xml/ConstraintDefinitionType.java:14: error: package javax.xml.bind.annotation does not exist import javax.xml.bind.annotation.XmlElement; ^ ...
Bug#911136: javatools: FTBFS with Java 11 due to MANIFEST.MF wrapping change
Source: javatools Severity: important Tags: sid buster User: debian-j...@lists.debian.org Usertags: default-java11 javatools has a test failing with Java 11. It looks like Java 11 now wraps the attributes in MANIFEST.MF after 72 characters instead of 70 in the previous versions: prove -Ilib t t/critic.t ... skipped: Only UNRELEASED versions are criticised t/minimum-version.t .. ok t/strict.t ... ok All tests successful. Files=3, Tests=50, 3 wallclock secs ( 0.03 usr 0.00 sys + 2.88 cusr 0.13 csys = 3.04 CPU) Result: PASS cd tests && ./tests.sh Running: perl -I./lib ./jh_manifest "/build/javatools-0.70/tests/test.jar" Running: perl -I./lib ./jh_manifest "/build/javatools-0.70/tests/test.jar" ERROR: difference detected: --- long-out2014-09-10 19:33:53.0 + +++ META-INF/MANIFEST.MF2018-10-16 09:21:38.0 + @@ -1,11 +1,10 @@ Manifest-Version: 1.0 -Class-Path: /usr/share/java/hexdump.jar /usr/share/java/hexdump.jar /u - sr/share/java/hexdump.jar /usr/share/java/hexdump.jar /usr/share/java - /hexdump.jar /usr/share/java/hexdump.jar /usr/share/java/hexdump.jar - /usr/share/java/hexdump.jar /usr/share/java/hexdump.jar /usr/share/ja - va/hexdump.jar /usr/share/java/hexdump.jar /usr/share/java/hexdump.ja - r /usr/share/java/hexdump.jar /usr/share/java/hexdump.jar /usr/share/ - java/hexdump.jar /usr/share/java/hexdump.jar /usr/share/java/hexdump. - jar +Class-Path: /usr/share/java/hexdump.jar /usr/share/java/hexdump.jar /usr + /share/java/hexdump.jar /usr/share/java/hexdump.jar /usr/share/java/hex + dump.jar /usr/share/java/hexdump.jar /usr/share/java/hexdump.jar /usr/s + hare/java/hexdump.jar /usr/share/java/hexdump.jar /usr/share/java/hexdu + mp.jar /usr/share/java/hexdump.jar /usr/share/java/hexdump.jar /usr/sha + re/java/hexdump.jar /usr/share/java/hexdump.jar /usr/share/java/hexdump + .jar /usr/share/java/hexdump.jar /usr/share/java/hexdump.jar Created-By: 1.6.0_06 (Sun Microsystems Inc.)
Bug#872885: netty-tcnative-1.1: Please migrate to openssl1.1 in Buster
Le 13/10/2018 à 00:32, Emmanuel Bourg a écrit : > - tycho (through aether again), I'm working on an upgrade no longer > depending on it The tycho update is ready but requires equinox-p2 which is still in NEW. > - libgpars-groovy-java which is used by groovy. I don't have a solution > for this one yet. I've uploaded libgpars-groovy-java/1.2.1-10 with the Netty part removed, it was never used in Debian.
Bug#872885: netty-tcnative-1.1: Please migrate to openssl1.1 in Buster
Le 12/10/2018 à 22:33, Moritz Mühlenhoff a écrit : > src:tcnetty has been fixed wrt OpenSSL 1.1 and netty-tcnative-1.1 has no > reverse dependencies in the archive. Shall we remove it from the archive? Actually netty-tcnative-1.1 is still needed by netty-3.9. There are 3 rdeps left for netty-3.9: - maven-indexer (through aether), but it isn't used and could be removed - tycho (through aether again), I'm working on an upgrade no longer depending on it - libgpars-groovy-java which is used by groovy. I don't have a solution for this one yet. Emmanuel Bourg
Bug#910843: jaxb: Rebuilding from source gives broken dependencies
Le 12/10/2018 à 18:49, Daniel Schepler a écrit : > Unfortunately, I didn't save logs of the manual builds I did in the > pbuilder login session. I could probably repeat the process later > today and send you the logs then - along with possibly the rebuilt > packages from dtd-parser and jaxb for comparison with the current > versions in the Debian archive, if that would be useful. I get it, that's because you rebuilt dtd-parser with a more recent version of maven-debian-helper than originally. Before maven-debian-helper/2.2 a bug rendered the --has-package-version option ineffective.
Bug#910843: jaxb: Rebuilding from source gives broken dependencies
I'm unable to reproduce the issue. libjaxb-java doesn't get a versioned dependency on libdtd-parser-java. Do you still have the full pbuilder log please? Emmanuel Bourg
Bug#894284: android-platform-tools-base FTBFS with openjdk-9
The javax.xml.bind errors can be simply fixed by adding a dependency
on jaxb-api:
--- a/repository/build.gradle
+++ b/repository/build.gradle
@@ -9,6 +9,7 @@
compile project(':base:common')
compile 'org.apache.commons:commons-compress:1.8.1'
compile 'com.google.jimfs:jimfs:1.1'
+compile 'javax.xml.bind:jaxb-api:debian'
testCompile 'junit:junit:4.12'
}
There is another error with Java 10 caused by a change in the return
type of javax.xml.namespace.NamespaceContext.getPrefixes().
It's easily fixed with:
--- a/common/src/main/java/com/android/xml/AndroidXPathFactory.java
+++ b/common/src/main/java/com/android/xml/AndroidXPathFactory.java
@@ -81,7 +81,7 @@
}
@Override
-public Iterator getPrefixes(String namespaceURI) {
+public Iterator getPrefixes(String namespaceURI) {
if (SdkConstants.NS_RESOURCES.equals(namespaceURI)) {
return mAndroidPrefixes.iterator();
}
Unfortunately there is another issue with SignedJarBuilder:
/build/android-platform-tools-base-2.2.2/sdklib/src/main/java/com/android/sdklib/internal/build/SignedJarBuilder.java:23:
error: package sun.security.pkcs is not visible
import sun.security.pkcs.ContentInfo;
^
(package sun.security.pkcs is declared in module java.base, which does not
export it to the unnamed module)
/build/android-platform-tools-base-2.2.2/sdklib/src/main/java/com/android/sdklib/internal/build/SignedJarBuilder.java:24:
error: package sun.security.pkcs is not visible
import sun.security.pkcs.PKCS7;
^
(package sun.security.pkcs is declared in module java.base, which does not
export it to the unnamed module)
/build/android-platform-tools-base-2.2.2/sdklib/src/main/java/com/android/sdklib/internal/build/SignedJarBuilder.java:25:
error: package sun.security.pkcs is not visible
import sun.security.pkcs.SignerInfo;
^
(package sun.security.pkcs is declared in module java.base, which does not
export it to the unnamed module)
/build/android-platform-tools-base-2.2.2/sdklib/src/main/java/com/android/sdklib/internal/build/SignedJarBuilder.java:26:
error: package sun.security.x509 is not visible
import sun.security.x509.AlgorithmId;
^
(package sun.security.x509 is declared in module java.base, which does not
export it to the unnamed module)
/build/android-platform-tools-base-2.2.2/sdklib/src/main/java/com/android/sdklib/internal/build/SignedJarBuilder.java:27:
error: package sun.security.x509 is not visible
import sun.security.x509.X500Name;
^
(package sun.security.x509 is declared in module java.base, which does not
export it to the unnamed module)
Bug#880359: openjfx FTBFS on big endian: ../lib/icupkg: No such file or directory
Control: severity -1 important Control: tags -1 + help Downgrading the severity, upstream doesn't support non x86 architectures and the packages are only provided as a best effort.
Bug#842535: mark npapi-sdk-dev Multi-Arch: foreig and move pkg-config files out of /usr/lib/pkgconfig
Control: affects -1 - src:icedtea-web The NPAPI plugin is being removed from src:icedtea-web, I'm therefore removing the 'affects' tag.
Bug#647706: libwebkitgtk-1.0-0: Can't open Banco do Brasil's login page with icedtea-plugin
Control: tags -1 + wontfix Control: close -1 NPAPI support has been removed from all major browsers (Firefox 52, Chrome 45, Safari 12, Edge), the Java plugin can no longer work and applets are fading away from the web. For this reason the src:icedtea-web package will no longer build the plugin in the next update, and all related issues are tagged as wontfix and closed.
Bug#855686: icedtea-web: FTBFS: configure: error: Package requirements (mozilla-plugin) were not met
Control: tags -1 + pending The plugin is being removed
Bug#605458: icedtea-web plugin removal
Control: tags -1 + wontfix Control: close -1 NPAPI support has been removed from all major browsers (Firefox 52, Chrome 45, Safari 12, Edge), the Java plugin can no longer work and applets are fading away from the web. For this reason the src:icedtea-web package will no longer build the plugin in the next update, and all related issues are tagged as wontfix and closed.
