Bug#859001: libbrowserlauncher-java: No jar file without version number

Am 29.03.2017 um 15:30 schrieb Ole Streicher: > Hi Markus, > > Am 29.03.2017 um 15:15 schrieb Markus Koschany: >>> There is no jar without a version number. This makes it impossible to >>> add the jar to the CLASSPATH of other packages, >> >> This is not true. You can add such jar files to your

Bug#859001: libbrowserlauncher-java: No jar file without version number

Hi Markus, Am 29.03.2017 um 15:15 schrieb Markus Koschany: >> There is no jar without a version number. This makes it impossible to >> add the jar to the CLASSPATH of other packages, > > This is not true. You can add such jar files to your CLASSPATH. >> since the file name will change silently

Bug#859001: libbrowserlauncher-java: No jar file without version number

Hi Markus, Am 29.03.2017 um 15:46 schrieb Markus Koschany: > In the case of backports you would probably backport jmodeltest as well, > so both could be easily kept in sync. AFAICT both packages seem to work > well together and librowserlauncher-java was only packaged to build > jmodeltest from

Bug#859005: libbrowserlauncher-java: properties file not included

The properties file also contains a bug the prevents from using IceWeasel even when it would be included. So, when fixing this, the attached patch should be applied as well. I can't do this myself since I just realized that I am not in the java-maintainers group. Cheers Ole >From

Bug#859012: maven-debian-helper: unnecessarily gendered pronoun in prompt

Package: maven-debian-helper Version: 2.1.3 Severity: normal Dear Maintainer, In this source file you will find a prompt... http://sources.debian.net/src/maven-debian-helper/2.1.3/maven-packager-utils/src/main/java/org/debian/maven/packager/GenerateDebianFilesMojo.java/?hl=249#L249 ... which

Bug#859005: libbrowserlauncher-java: properties file not included

Am 29.03.2017 um 15:50 schrieb Ole Streicher: > The properties file also contains a bug the prevents from using > IceWeasel even when it would be included. So, when fixing this, the > attached patch should be applied as well. > > I can't do this myself since I just realized that I am not in the >

Bug#859005: libbrowserlauncher-java: properties file not included

Package: libbrowserlauncher-java Version: 1.3+dfsg-1 Severity: serious When using the package, I get the following exception: edu.stanford.ejalbert.exception.BrowserLaunchingInitializingException: unable to find config file: /edu/stanford/ejalbert/launching/misc/linuxUnixConfig.properties at

Bug#859004: Pending fixes for bugs in the libbrowserlauncher-java package

tag 859004 + pending thanks Some bugs in the libbrowserlauncher-java package are closed in revision 329d907fc3ad2095d5a3e07b9027ef376d41c44c in branch 'master' by Ole Streicher The full diff can be seen at https://anonscm.debian.org/cgit/pkg-java/libbrowserlauncher-java.git/commit/?id=329d907

Processed: Pending fixes for bugs in the libbrowserlauncher-java package

Processing commands for cont...@bugs.debian.org: > tag 859001 + pending Bug #859001 [libbrowserlauncher-java] libbrowserlauncher-java: No jar file without version number Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 859001:

Processed: Pending fixes for bugs in the libbrowserlauncher-java package

Processing commands for cont...@bugs.debian.org: > tag 859004 + pending Bug #859004 [libbrowserlauncher-java] libbrowserlauncher-java has the wrong architecture Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 859004:

Bug#859001: Pending fixes for bugs in the libbrowserlauncher-java package

tag 859001 + pending thanks Some bugs in the libbrowserlauncher-java package are closed in revision e8e93af065fad9135162bcb18f57d03861d49f91 in branch 'master' by Ole Streicher The full diff can be seen at https://anonscm.debian.org/cgit/pkg-java/libbrowserlauncher-java.git/commit/?id=e8e93af

Bug#859001: libbrowserlauncher-java: No jar file without version number

Hi Ole, Am 29.03.2017 um 14:56 schrieb Ole Streicher: > Package: libbrowserlauncher-java > Version: 1.3+dfsg-1 > Severity: serious > > The package contents are (mainly): > > /usr/share/java/BrowserLauncher2-1_3-1.3.jar > /usr/share/java/BrowserLauncher2-1_3.jar -> BrowserLauncher2-1_3-1.3.jar >

Processing of headius-options_1.4-1_source.changes

headius-options_1.4-1_source.changes uploaded successfully to localhost along with the files: headius-options_1.4-1.dsc headius-options_1.4.orig.tar.gz headius-options_1.4-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) __ This is the

headius-options_1.4-1_source.changes ACCEPTED into experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 29 Mar 2017 23:13:33 +0100 Source: headius-options Binary: libheadius-options-java libheadius-options-java-doc Architecture: source Version: 1.4-1 Distribution: experimental Urgency: medium Maintainer: Debian Java

commons-daemon_1.0.15-6+deb8u1_ppc64el.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 03 Mar 2017 13:47:51 -0500 Source: commons-daemon Binary: libcommons-daemon-java jsvc Architecture: source all ppc64el Version: 1.0.15-6+deb8u1 Distribution: jessie Urgency: medium Maintainer: Debian Java

Bug#856560: marked as done (ppc64el: "Cannot find any VM in Java Home" issue)

Your message dated Wed, 29 Mar 2017 19:47:08 + with message-id and subject line Bug#856560: fixed in commons-daemon 1.0.15-6+deb8u1 has caused the Debian Bug report #856560, regarding ppc64el: "Cannot find any VM in Java Home" issue to be marked as done.

Bug#859001: libbrowserlauncher-java: No jar file without version number

Package: libbrowserlauncher-java Version: 1.3+dfsg-1 Severity: serious The package contents are (mainly): /usr/share/java/BrowserLauncher2-1_3-1.3.jar /usr/share/java/BrowserLauncher2-1_3.jar -> BrowserLauncher2-1_3-1.3.jar There is no jar without a version number. This makes it impossible to

Bug#859004: libbrowserlauncher-java has the wrong architecture

Package: libbrowserlauncher-java Version: 1.3+dfsg-1 Severity: important The package is Arch: any, but since it is pure Java, it should be Arch:all. __ This is the maintainer address of Debian's Java team . Please use

Bug#857343: closed by Markus Koschany <a...@debian.org> (Bug#857343: fixed in logback 1:1.1.9-2)

Thank you for your upload. But i think that the issue is not completely solved, upstream made it in several commits (https://github.com/qos-ch/logback/commits/v_1.2.0). The comment is not meaningful but this one is related to the vulnerability :

Bug#857343: closed by Markus Koschany <a...@debian.org> (Bug#857343: fixed in logback 1:1.1.9-2)

Control: reopen -1 Am 29.03.2017 um 08:11 schrieb Fabrice Dagorn: > Thank you for your upload. > > But i think that the issue is not completely solved, upstream made it in > several commits (https://github.com/qos-ch/logback/commits/v_1.2.0). > > The comment is not meaningful but this one is

Processed: Re: Bug#857343: closed by Markus Koschany <a...@debian.org> (Bug#857343: fixed in logback 1:1.1.9-2)

Processing control commands: > reopen -1 Bug #857343 {Done: Markus Koschany } [liblogback-java] logback: CVE-2017-5929: serialization vulnerability affecting the SocketServer and ServerSocketReceiver components Bug #858914 {Done: Markus Koschany }