jaxb 2.3.0.1-8 MIGRATED to testing

FYI: The status of the jaxb source package in Debian's testing distribution has changed. Previous version: 2.3.0.1-7 Current version: 2.3.0.1-8 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

libjsr166y-java: status change on tests.reproducible-builds.org/debian

2019-04-06 09:34 https://tests.reproducible-builds.org/debian/unstable/amd64/libjsr166y-java changed from FTBFS -> reproducible __ This is the maintainer address of Debian's Java team . Please use

jmock: status change on tests.reproducible-builds.org/debian

2019-04-06 08:25 https://tests.reproducible-builds.org/debian/unstable/amd64/jmock changed from FTBFS -> reproducible __ This is the maintainer address of Debian's Java team . Please use debian-j...@lists.debian.org

sdo-api-java: status change on tests.reproducible-builds.org/debian

2019-04-07 00:08 https://tests.reproducible-builds.org/debian/unstable/amd64/sdo-api-java changed from FTBFS -> reproducible __ This is the maintainer address of Debian's Java team . Please use

jaxb_2.3.0.1-7.1_source.changes REJECTED

Version check failed: Your upload included the source package jaxb, version 2.3.0.1-7.1, however testing already has version 2.3.0.1-8. Uploads to unstable must have a higher version than present in testing. === Please feel free to respond to this email if you don't understand why your files

Bug#926088: marked as done (robocode: CVE-2019-10648)

Your message dated Sun, 07 Apr 2019 22:33:37 + with message-id and subject line Bug#926088: fixed in robocode 1.9.3.3-2 has caused the Debian Bug report #926088, regarding robocode: CVE-2019-10648 to be marked as done. This means that you claim that the problem has been dealt with. If this

robocode_1.9.3.3-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 08 Apr 2019 00:13:19 +0200 Source: robocode Architecture: source Version: 1.9.3.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Closes: 926088 Changes:

Processing of robocode_1.9.3.3-2_source.changes

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

Bug#916145: closure-compiler: Not working with recent JS code

Am 07.04.19 um 20:36 schrieb Adrian Bunk: > On Sun, Apr 07, 2019 at 11:12:30AM -0700, tony mancill wrote: >> ... >> Somewhat related, given that closure-compiler upstream releases about >> once a month on average, perhaps it is a candidate for doing Something >> Different. > > That's pretty

Bug#916145: closure-compiler: Not working with recent JS code

On Sun, Apr 07, 2019 at 11:12:30AM -0700, tony mancill wrote: >... > Somewhat related, given that closure-compiler upstream releases about > once a month on average, perhaps it is a candidate for doing Something > Different. That's pretty normal for a package, and we aren't even close to the

Bug#916145: closure-compiler: Not working with recent JS code

On Sun, Apr 07, 2019 at 11:16:53AM +0300, Adrian Bunk wrote: > On Sat, Apr 06, 2019 at 06:13:05PM +0200, Chris Hofstaedtler wrote: > > * Roland Gruber [190406 16:07]: > > > the current version is so old that it got incompatible with recent JS > > > code. > > > E.g. jQuery 3.3.1 cannot be

Processed: Re: CVE-2018-1000073

Processing commands for cont...@bugs.debian.org: > retitle 925986 CVE-2018-173: directory Traversal vulnerability in > install_location Bug #925986 [jruby] CVE-2018-173 Changed Bug title to 'CVE-2018-173: directory Traversal vulnerability in install_location' from

Processed: your mail

Processing commands for cont...@bugs.debian.org: > retitle 888547 CVE-2017-1000190: XXE vulnerability resulting in SSRF, > information disclosure, DoS, etc. Bug #888547 [src:simple-xml] CVE-2017-1000190 Changed Bug title to 'CVE-2017-1000190: XXE vulnerability resulting in SSRF, information

Bug#925507: marked as done (jh_build fails when source files are specified)

Your message dated Sun, 07 Apr 2019 13:34:12 + with message-id and subject line Bug#925507: fixed in javatools 0.72.8 has caused the Debian Bug report #925507, regarding jh_build fails when source files are specified to be marked as done. This means that you claim that the problem has been

Bug#926542: marked as done (javatools: jh_build -N has undefined behaviour (--no-package vs. --no-javadoc))

Your message dated Sun, 07 Apr 2019 13:34:12 + with message-id and subject line Bug#926542: fixed in javatools 0.72.8 has caused the Debian Bug report #926542, regarding javatools: jh_build -N has undefined behaviour (--no-package vs. --no-javadoc) to be marked as done. This means that you

javatools_0.72.8_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 Apr 2019 13:18:04 + Source: javatools Architecture: source Version: 0.72.8 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Niels Thykier Closes: 925507 926542

Bug#925473: tomcat9: sysvinit script missing (Policy §9.11¶2 “must”)

On Sun, 7 Apr 2019, Ivo De Decker wrote: > Also, I'm not sure adding an init script now is an approriate change > for the freeze. It is, it only touches systems on which it previously did not work. > Some other changes suggested in this bug (like changes in systemd) > certainly are not. This

Processing of javatools_0.72.8_source.changes

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

Bug#925473: tomcat9: sysvinit script missing (Policy §9.11¶2 “must”)

Control: tags -1 buster-ignore Hi, On Wed, Apr 03, 2019 at 02:33:47PM +0200, Thorsten Glaser wrote: > On Wed, 3 Apr 2019, Emmanuel Bourg wrote: > > > > I really insist on being able to install tomcat9 without having to > > > install a whole other init system, even if it is not used. > > > >

Processed: Re: Bug#925473: tomcat9: sysvinit script missing (Policy §9.11¶2 “must”)

Processing control commands: > tags -1 buster-ignore Bug #925473 [tomcat9] tomcat9: sysvinit script missing (Policy §9.11¶2 “must”) Added tag(s) buster-ignore. -- 925473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925473 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: severity of 926542 is serious ...

Processing commands for cont...@bugs.debian.org: > severity 926542 serious Bug #926542 [javahelper] jh_build: randomly fails with DH_OPTIONS="-N..." Severity set to 'serious' from 'normal' > retitle 926542 javatools: jh_build -N has undefined behaviour (--no-package > vs. --no-javadoc) Bug

Processed: Re: Bug#916145: closure-compiler: Not working with recent JS code

Processing control commands: > severity -1 important Bug #916145 [closure-compiler] closure-compiler: Not working with recent JS code Severity set to 'important' from 'serious' -- 916145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916145 Debian Bug Tracking System Contact

Bug#916145: closure-compiler: Not working with recent JS code

Control: severity -1 important Hi, On Sun, Apr 07, 2019 at 11:16:53AM +0300, Adrian Bunk wrote: > > Adrian: you raised the severity, care to lower it until buster is > > out (or say some words on why)? > > IMHO the release team adding a buster-ignore tag would be the best way > forward here -

Bug#924635: marked as done (libactivemq-java depends on the removed libspring-jms-java)

Your message dated Sun, 7 Apr 2019 12:17:36 +0200 with message-id <20190407101735.ct5b3qjwbxe2e...@debian.org> and subject line Re: Update has caused the Debian Bug report #924635, regarding libactivemq-java depends on the removed libspring-jms-java to be marked as done. This means that you claim

Bug#924634: marked as done (libuima-as-java depends on the removed libspring-jms-java)

Your message dated Sun, 7 Apr 2019 11:52:38 +0200 with message-id <20190407095236.wivmwod6272aq...@debian.org> and subject line Re: Update has caused the Debian Bug report #924634, regarding libuima-as-java depends on the removed libspring-jms-java to be marked as done. This means that you claim

Bug#916145: closure-compiler: Not working with recent JS code

On Sat, Apr 06, 2019 at 06:13:05PM +0200, Chris Hofstaedtler wrote: > * Roland Gruber [190406 16:07]: > > the current version is so old that it got incompatible with recent JS code. > > E.g. jQuery 3.3.1 cannot be minified as the tool reports parsing errors. > > > > Please either update the tool

libspring-java_4.3.22-4_source.changes REJECTED

Signature for changes file was already seen at 2019-04-07 00:04:20.602427. Please refresh the signature of the changes file if you want to upload it again. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which

Processing of libspring-java_4.3.22-4_source.changes

libspring-java_4.3.22-4_source.changes uploaded successfully to localhost along with the files: libspring-java_4.3.22-4.dsc libspring-java_4.3.22-4.debian.tar.xz libspring-java_4.3.22-4_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) __ This