Processed: Bug #923299 in tomcat9 marked as pending

Processing control commands: > tag -1 pending Bug #923299 [tomcat9] /lib/systemd/system/tomcat9.service: tomcat9 fails to run; "Failed to set up mount namespacing" in system log Added tag(s) pending. -- 923299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923299 Debian Bug Tracking System

Processing of tomcat9_9.0.16-3_source.changes

tomcat9_9.0.16-3_source.changes uploaded successfully to localhost along with the files: tomcat9_9.0.16-3.dsc tomcat9_9.0.16-3.debian.tar.xz tomcat9_9.0.16-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) __ This is the maintainer address

Bug#919638: solr-tomcat: Permission problems after update to tomcat9

Control: reopen -1 Control: notfixed -1 9.0.16-2 Le 17/02/2019 à 12:38, Markus Koschany a écrit : > Thank you for the confirmation. Then I think reassigning this issue to > src:tomcat9 and fixing it there is sensible. Unfortunately the modification broke tomcat9 installations when solr isn't

Bug#923299: marked as done (/lib/systemd/system/tomcat9.service: tomcat9 fails to run; "Failed to set up mount namespacing" in system log)

Your message dated Tue, 26 Feb 2019 08:49:47 + with message-id and subject line Bug#923299: fixed in tomcat9 9.0.16-3 has caused the Debian Bug report #923299, regarding /lib/systemd/system/tomcat9.service: tomcat9 fails to run; "Failed to set up mount namespacing" in system log to be marked

Processed: Re: solr-tomcat: Permission problems after update to tomcat9

Processing control commands: > reopen -1 Bug #919638 {Done: Markus Koschany } [src:tomcat9] solr-tomcat: Permission problems after update to tomcat9 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug

tomcat9_9.0.16-3_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 26 Feb 2019 09:31:13 +0100 Source: tomcat9 Architecture: source Version: 9.0.16-3 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Closes: 923299 Changes:

Bug#923284: Seemingly miscompiles with jdk-11

On Tue, 2019-02-26 at 11:35 +0100, Emmanuel Bourg wrote: > Le 26/02/2019 à 10:20, Sjoerd Simons a écrit : > > > I've atteched the output of running docker build on the DockerFile > > i > > attached to reproduce the issue; The relevant part in the gradle > > build > > seems to be: > > Thank you!

Bug#919638: solr-tomcat: Permission problems after update to tomcat9

Am 26.02.19 um 09:46 schrieb Emmanuel Bourg: > Control: reopen -1 > Control: notfixed -1 9.0.16-2 > > Le 17/02/2019 à 12:38, Markus Koschany a écrit : > >> Thank you for the confirmation. Then I think reassigning this issue to >> src:tomcat9 and fixing it there is sensible. > > Unfortunately

Processing of jruby-openssl_0.9.21-2_source.changes

jruby-openssl_0.9.21-2_source.changes uploaded successfully to localhost along with the files: jruby-openssl_0.9.21-2.dsc jruby-openssl_0.9.21-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) __ This is the maintainer address of Debian's Java

Bug#923284: Seemingly miscompiles with jdk-11

Le 26/02/2019 à 12:22, Sjoerd Simons a écrit : > ASM7 mode seems to have been introduced in the gradle v5.x series. Not > sure if it makes sense for buster to upgrade to that (I really don't > know much about java, so no idea about the impact)? We can't upgrade to Gradle 5 unfortunately, not

Processed: reassign 923284 to gradle, merging 923284 923317 ...

Processing commands for cont...@bugs.debian.org: > reassign 923284 gradle Bug #923284 [src:bsh] Seemingly miscompiles with jdk-11 Bug reassigned from package 'src:bsh' to 'gradle'. No longer marked as found in versions bsh/2.0b4-19. Ignoring request to alter fixed versions of bug #923284 to the

Bug#912545: marked as done (jruby-openssl: FTBFS with Java 11 due to javax.annotation removal)

Your message dated Tue, 26 Feb 2019 10:34:47 + with message-id and subject line Bug#912545: fixed in jruby-openssl 0.9.21-2 has caused the Debian Bug report #912545, regarding jruby-openssl: FTBFS with Java 11 due to javax.annotation removal to be marked as done. This means that you claim

Bug#923284: Seemingly miscompiles with jdk-11

Le 26/02/2019 à 10:20, Sjoerd Simons a écrit : > I've atteched the output of running docker build on the DockerFile i > attached to reproduce the issue; The relevant part in the gradle build > seems to be: Thank you! The "Malformed jar" message is just a warning. The actual issue is: > Caused

tomcat9_9.0.16-1~bpo9+1_source.changes ACCEPTED into stretch-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 26 Feb 2019 09:17:32 +0100 Source: tomcat9 Binary: tomcat9-common tomcat9 tomcat9-user libtomcat9-java libtomcat9-embed-java tomcat9-admin tomcat9-examples tomcat9-docs Architecture: source Version:

jruby-openssl_0.9.21-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 26 Feb 2019 11:26:24 +0100 Source: jruby-openssl Binary: jruby-openssl Architecture: source Version: 0.9.21-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Andrej Shadura

Bug#923317: FTBS: fails to build after libjaxp1.3-java is rebuild on buster

Le 26/02/2019 à 11:23, Sjoerd Simons a écrit : > This may or may not be related to 923284 This is the same issue. Gradle breaks when its dependencies use Java 11 bytecode. Emmanuel Bourg __ This is the maintainer address of Debian's Java team

Bug#923364: FTBS: Can't build against bouncy-castle build with newer jdk

Package: libitext-java Version: 2.1.7-12 Severity: serious Tags: patch Hey, When rebuilding bouncy-castle the jar doesn't seem to have the same classpath built-in as older builds did; specifically comparing a rebuild with an old debian build the MANIFEST.MF has the following diff (among other

Bug#923330: jajuk: Fails to start with Java Runtime Environment 1.7 minimum required. You use a JVM ext.JVM@23fc625e

Package: jajuk Version: 1:1.10.9+dfsg2-4 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Just trying to start jajuk. From the menu just nothing happens, from commandline I get the

Bug#923284: Seemingly miscompiles with jdk-11

On Tue, 2019-02-26 at 12:40 +0100, Emmanuel Bourg wrote: > Le 26/02/2019 à 12:22, Sjoerd Simons a écrit : > > > ASM7 mode seems to have been introduced in the gradle v5.x series. > > Not > > sure if it makes sense for buster to upgrade to that (I really > > don't > > know much about java, so no

Processing of morfologik-stemming_1.9.0+dfsg-1_source.changes

morfologik-stemming_1.9.0+dfsg-1_source.changes uploaded successfully to localhost along with the files: morfologik-stemming_1.9.0+dfsg-1.dsc morfologik-stemming_1.9.0+dfsg-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) __ This is the

Bug#917702: jruby FTBFS with openjdk-9

Le 26/02/2019 à 15:05, Markus Koschany a écrit : > The FTBFS bug got fixed yesterday. I should complain more often. Andrej > uploaded version 9.1.17 to unstable. This is not the latest one but I > guess better than nothing? The original bug has not been closed yet. > Andrej, can we close it now

Bug#917702: jruby FTBFS with openjdk-9

Hi, On Tue, 26 Feb 2019 at 15:20, Emmanuel Bourg wrote: > Le 26/02/2019 à 15:05, Markus Koschany a écrit : > > The FTBFS bug got fixed yesterday. I should complain more often. Andrej > > uploaded version 9.1.17 to unstable. This is not the latest one but I > > guess better than nothing? The

Bug#917702: jruby FTBFS with openjdk-9

Hi, Am 25.02.19 um 19:40 schrieb Miguel Landaeta: > Hi Markus, > > On Sun, Feb 24, 2019 at 08:39:48PM +0100, Markus Koschany wrote: >> JRuby is a mess. I guess we "just" need to package the latest upstream >> release to fix the FTBFS bugs. Nobody felt like doing that in the past >> twelve

Processed: Bug #920707 in netbeans marked as pending

Processing control commands: > tag -1 pending Bug #920707 [src:netbeans] netbeans: Unexpected Exception sealing violation related to nb-javac Added tag(s) pending. -- 920707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920707 Debian Bug Tracking System Contact ow...@bugs.debian.org with

morfologik-stemming_1.9.0+dfsg-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 26 Feb 2019 14:38:04 +0100 Source: morfologik-stemming Binary: libmorfologik-stemming-java Architecture: source Version: 1.9.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Java maintainers

openjdk-11-jre-dcevm is marked for autoremoval from testing

openjdk-11-jre-dcevm 11.0.1+7-1 is marked for autoremoval from testing on 2019-03-20 It is affected by these RC bugs: 922678: openjdk-11-jre-dcevm: openjdk-11-dcevm ftbfs on i386 __ This is the maintainer address of Debian's Java team

Processing of jruby_9.1.17.0-2_source.changes

jruby_9.1.17.0-2_source.changes uploaded successfully to localhost along with the files: jruby_9.1.17.0-2.dsc jruby_9.1.17.0-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) __ This is the maintainer address of Debian's Java team

Processing of tomcat9_9.0.16-1~bpo9+1_source.changes

tomcat9_9.0.16-1~bpo9+1_source.changes uploaded successfully to localhost along with the files: tomcat9_9.0.16-1~bpo9+1.dsc tomcat9_9.0.16-1~bpo9+1.debian.tar.xz tomcat9_9.0.16-1~bpo9+1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) __ This

Bug#923284: marked as done (FTBS: Doesn't handle depencencies that were build using openjdk 11)

Your message dated Tue, 26 Feb 2019 19:19:59 + with message-id and subject line Bug#923284: fixed in gradle 4.4.1-5 has caused the Debian Bug report #923284, regarding FTBS: Doesn't handle depencencies that were build using openjdk 11 to be marked as done. This means that you claim that the

Processing of gradle_4.4.1-5_source.changes

gradle_4.4.1-5_source.changes uploaded successfully to localhost along with the files: gradle_4.4.1-5.dsc gradle_4.4.1-5.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) __ This is the maintainer address of Debian's Java team

Processed: Bug #923284 in gradle marked as pending

Processing control commands: > tag -1 pending Bug #923284 [gradle] FTBS: Doesn't handle depencencies that were build using openjdk 11 Bug #923317 [gradle] FTBS: Doesn't handle depencencies that were build using openjdk 11 Added tag(s) pending. Added tag(s) pending. -- 923284:

gradle_4.4.1-5_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 26 Feb 2019 20:02:13 +0100 Source: gradle Binary: gradle libgradle-core-java libgradle-plugins-java gradle-doc Architecture: source Version: 4.4.1-5 Distribution: unstable Urgency: medium Maintainer: Debian Java

Bug#917702: jruby FTBFS with openjdk-9

On Tue, Feb 26, 2019 at 03:05:48PM +0100, Markus Koschany wrote: > > [...] > > The FTBFS bug got fixed yesterday. I should complain more often. Andrej > uploaded version 9.1.17 to unstable. This is not the latest one but I > guess better than nothing? The original bug has not been closed yet. >

Bug#923330: jajuk: Fails to start with Java Runtime Environment 1.7 minimum required. You use a JVM ext.JVM@23fc625e

Control: severity -1 grave Hello Bertrand, hello Werner Am 26.02.19 um 21:13 schrieb Bertrand Florat: > Hi, > > Current develop branch fixes that : > https://github.com/jajuk-team/jajuk/blob/develop/src/main/java/org/jajuk/Main.java > > We now just throw an error if JVM is < 1.8. > [...] >

Processed: Re: Bug#923330: jajuk: Fails to start with Java Runtime Environment 1.7 minimum required. You use a JVM ext.JVM@23fc625e

Processing control commands: > severity -1 grave Bug #923330 [jajuk] jajuk: Fails to start with Java Runtime Environment 1.7 minimum required. You use a JVM ext.JVM@23fc625e Severity set to 'grave' from 'important' -- 923330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923330 Debian Bug

Processed (with 1 error): coming…

Processing commands for cont...@bugs.debian.org: > tags 922863 = pending Bug #922863 [tomcat8] tomcat8: post-installation script subprocess failed during upgrade Added tag(s) pending; removed tag(s) moreinfo and unreproducible. > owner 922863 t...@debian.org Bug #922863 [tomcat8] tomcat8:

Processed: coming…

Processing commands for cont...@bugs.debian.org: > outlook 922863 patch coming Really Soon Now Outlook recorded from message bug 922863 message > thanks Stopping processing here. Please contact me if you need assistance. -- 922863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922863

Bug#893244: marked as done (jruby FTBFS with openjdk-9)

Your message dated Tue, 26 Feb 2019 21:45:16 +0100 with message-id <730ddbaf-b7c0-4541-cee9-925980416...@debian.org> and subject line Re: jruby FTBFS with openjdk-9 has caused the Debian Bug report #893244, regarding jruby FTBFS with openjdk-9 to be marked as done. This means that you claim that

Processed: your mail

Processing commands for cont...@bugs.debian.org: > outlook 922863 fixed package team-uploaded, thanks Dominik George for > debugging this together and his massive investment of time Outlook replaced with message bug 922863 message > End of message, stopping processing here. Please contact me

tomcat8_8.5.38-2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA384 Format: 1.8 Date: Tue, 26 Feb 2019 21:37:51 +0100 Source: tomcat8 Binary: libtomcat8-embed-java libtomcat8-java tomcat8 tomcat8-admin tomcat8-common tomcat8-docs tomcat8-examples tomcat8-user Architecture: source all Version: 8.5.38-2

Processing of tomcat8_8.5.38-2_amd64.changes

tomcat8_8.5.38-2_amd64.changes uploaded successfully to localhost along with the files: tomcat8_8.5.38-2.dsc tomcat8_8.5.38-2.debian.tar.xz libtomcat8-embed-java_8.5.38-2_all.deb libtomcat8-java_8.5.38-2_all.deb tomcat8-admin_8.5.38-2_all.deb tomcat8-common_8.5.38-2_all.deb

Bug#922863: marked as done (tomcat8: post-installation script subprocess failed during upgrade)

Your message dated Tue, 26 Feb 2019 23:07:14 + with message-id and subject line Bug#922863: fixed in tomcat8 8.5.38-2 has caused the Debian Bug report #922863, regarding tomcat8: post-installation script subprocess failed during upgrade to be marked as done. This means that you claim that

Bug#923330: jajuk: Fails to start with Java Runtime Environment 1.7 minimum required. You use a JVM ext.JVM@23fc625e

Am 26.02.19 um 21:34 schrieb Markus Koschany: > Thanks for reporting and the hint how to fix this problem. I'll take a > closer look soon. Unfortunately there is another issue that prevents jajuk from starting. This appears to be the same one which affects triplea as well.

Processed: Bug #923330 in jajuk marked as pending

Processing control commands: > tag -1 pending Bug #923330 [jajuk] jajuk: Fails to start with Java Runtime Environment 1.7 minimum required. You use a JVM ext.JVM@23fc625e Added tag(s) pending. -- 923330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923330 Debian Bug Tracking System