txw2 REMOVED from testing

FYI: The status of the txw2 source package in Debian's testing distribution has changed. Previous version: 0.1+20110809-1 Current version: (not in testing) Hint: (no removal hint found) The script that generates this mail tries to extract removal reasons from comments in the britney hint

lombok-patcher 0.22-2 MIGRATED to testing

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

jaxb 2.3.0-1 MIGRATED to testing

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

rngom REMOVED from testing

FYI: The status of the rngom source package in Debian's testing distribution has changed. Previous version: 0+201103+svn20110406-1 Current version: (not in testing) Hint: (no removal hint found) The script that generates this mail tries to extract removal reasons from comments in the

xsom REMOVED from testing

FYI: The status of the xsom source package in Debian's testing distribution has changed. Previous version: 0+20110809-1 Current version: (not in testing) Hint: (no removal hint found) The script that generates this mail tries to extract removal reasons from comments in the britney hint

geronimo-validation-1.0-spec 1.1-3 MIGRATED to testing

FYI: The status of the geronimo-validation-1.0-spec source package in Debian's testing distribution has changed. Previous version: 1.1-2 Current version: 1.1-3 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a

reproducible.debian.net status changes for libfreemarker-java

2017-10-03 16:36 https://tests.reproducible-builds.org/debian/unstable/amd64/libfreemarker-java changed from FTBFS -> reproducible __ This is the maintainer address of Debian's Java team . Please use

reproducible.debian.net status changes for gluegen2

2017-10-04 00:34 https://tests.reproducible-builds.org/debian/unstable/amd64/gluegen2 changed from reproducible -> FTBFS __ This is the maintainer address of Debian's Java team . Please use

Processed: your mail

Processing commands for cont...@bugs.debian.org: > user m...@qa.debian.org Setting user to m...@qa.debian.org (was mat...@debian.org). > usertags 675779 mia-teammaint There were no usertags set. Usertags are now: mia-teammaint. > clone 675779 -1 Bug #675779 [libjazzy-java] libjazzy-java: please

Processed: Re: Bug#857464: openjfx: FTBFS - Execution failed for task ':web:compileNativeLinux'

Processing control commands: > severity -1 important Bug #857464 [src:openjfx] openjfx: FTBFS - Execution failed for task ':web:compileNativeLinux' Severity set to 'important' from 'serious' -- 857464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857464 Debian Bug Tracking System Contact

Bug#857464: openjfx: FTBFS - Execution failed for task ':web:compileNativeLinux'

Control: severity -1 important The build fails because the machine used lacks memory. I have been struggling with this issue since openjfx 8u121. On amd64 and i386 I managed to build the package with 16GB of RAM (the binaries for the other architectures are provided as a convenience as long as

Processed: Re: Bug#877626: netbeans: Does not recognize Maven projects

Processing control commands: > severity -1 wishlist Bug #877626 [netbeans] netbeans: Does not recognize Maven projects Severity set to 'wishlist' from 'normal' > retitle -1 netbeans: Support Maven projects out-of-the-box Bug #877626 [netbeans] netbeans: Does not recognize Maven projects Changed

Bug#877626: netbeans: Does not recognize Maven projects

Control: severity -1 wishlist Control: retitle -1 netbeans: Support Maven projects out-of-the-box Hello Mark, Am 03.10.2017 um 16:57 schrieb Mark Carroll: > Package: netbeans > Severity: normal > > Dear Maintainer, > > With jessie's netbeans I used to be able to use "open project" and see the

freeplane_1.6.6-2_i386.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA384 Format: 1.8 Date: Tue, 03 Oct 2017 14:33:17 +0200 Source: freeplane Binary: freeplane freeplane-scripting-api Architecture: source all Version: 1.6.6-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers

Bug#877626: netbeans: Does not recognize Maven projects

Package: netbeans Severity: normal Dear Maintainer, With jessie's netbeans I used to be able to use "open project" and see the "m" marking by some folders and netbeans handled them just fine as maven projects. With the current stretch 8.1 netbeans I cannot find any sign at all of

Processing of freeplane_1.6.6-2_i386.changes

freeplane_1.6.6-2_i386.changes uploaded successfully to localhost along with the files: freeplane_1.6.6-2.dsc freeplane_1.6.6-2.debian.tar.xz freeplane-scripting-api_1.6.6-2_all.deb freeplane_1.6.6-2_all.deb freeplane_1.6.6-2_i386.buildinfo Greetings, Your Debian queue daemon

libfreemarker-java_2.3.23-7_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 03 Oct 2017 09:54:57 +0200 Source: libfreemarker-java Binary: libfreemarker-java libfreemarker-java-doc Architecture: source Version: 2.3.23-7 Distribution: unstable Urgency: medium Maintainer: Debian Java

Processing of libfreemarker-java_2.3.23-7_source.changes

libfreemarker-java_2.3.23-7_source.changes uploaded successfully to localhost along with the files: libfreemarker-java_2.3.23-7.dsc libfreemarker-java_2.3.23-7.debian.tar.xz libfreemarker-java_2.3.23-7_source.buildinfo Greetings, Your Debian queue daemon (running on host

Bug#876426: Patches for JDK9 EA & GA support

Below are the local changes I have been using during Early Access, and which also work for the current GA release. Note: only for JDK & docs; I haven't needed JRE packages. But I would assume that the JRE setup is basically a subset of SDK and could be easily adapted. The Early Access builds