Processing of netlib-java_0.9.3-6_source.changes

[Debian FTP Masters]

netlib-java_0.9.3-6_source.changes uploaded successfully to localhost
along with the files:
  netlib-java_0.9.3-6.dsc
  netlib-java_0.9.3-6.debian.tar.xz

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.

netlib-java_0.9.3-6_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 27 Mar 2019 08:35:16 +0100
Source: netlib-java
Binary: libnetlib-java
Architecture: source
Version: 0.9.3-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Andreas Tille 
Description:
 libnetlib-java - collection of mission-critical software components for linear 
alg
Changes:
 netlib-java (0.9.3-6) unstable; urgency=medium
 .
   * Drop /build/netlib-java-0.9.3 from URLs
Checksums-Sha1:
 6fc50c3a151c3aa32ca90005ebce98ca52e1d175 2077 netlib-java_0.9.3-6.dsc
 e1d14263916ef0971e387feec95629556b095d9a 4632 netlib-java_0.9.3-6.debian.tar.xz
Checksums-Sha256:
 ab508d0574a352d3b1b1598c819ce2a47baa770d2a236bbcf8c16c276773729b 2077 
netlib-java_0.9.3-6.dsc
 3963c7fff8a570db0d7b196784ea043d88658440a3cfc86393455fed725ac3d7 4632 
netlib-java_0.9.3-6.debian.tar.xz
Files:
 e7b3b7884ba1d188ba1eeb113df791dd 2077 java optional netlib-java_0.9.3-6.dsc
 2fe8ff35f579931b747225e6c8f5874b 4632 java optional 
netlib-java_0.9.3-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlybLDsRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtE9Xw//SLXQhe2mE+EE0A7lFuiUwYq32LgY8+T9
6mSjoDUkWGdY+97PN44YhdmsuJlNjxslf25RZ4P+Jp0+f9s4jztuXonZo5k/7Nt1
JByGpRwVQ3baF3qxKxu+jEzd63j6VuPp1D778Jy7yPQKMkMF9KCDj5cztJuq+8zS
QpFgrx5H5SF8yvlvzF8/Sfy35ZqPC0qUCxSyZUp9zgpzk0HiUua2Ue+QHCv4suiR
YD2iio9j8WP1Lk37IGNUf/6NcX3JocC4X8FF00jlZesEKZUdaeqVFf4Rb+kM/tDY
Ya3nXDWWIYFUrsbuP7JgC39zerPdV6Q88aCuhzgz9ssaUsfS8BatCNoTxfAMYxu5
93JqyS80Fh1o74XaDvmCsg44HUnvEujgDLkuKUAimZSPDPytHqSLd6+gKPDnqnX4
dSOtAQWuHLkup4G5M/T13F+Db62+GTUPK10mysE4Td5YQYdwL18EnSqnoWwpshyI
qAnS0yP0iLcD9msts5p0X0U35mL+Cg1/dbJ1VxxodERBU11IoY1KEYLaWZXhlC2C
a2P7u3Cz6AMfmbIKsOtGsHs0jPGX7uDw6K/TUnVD5QaYG7MVG+TpYG13kYoIdr3X
YSk5n5be0qzvkmLXzwT2P9GS92mKXIqbCv4clhKds1QVCRZdfOKv4B6rLVodT8rM
T3xUscDPJ48=
=7ovZ
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

[Mattia Rizzolo]

On Tue, Mar 26, 2019 at 04:35:41PM -0700, tony mancill wrote:
> Are you sure about the upload of 4.3.22-2 changing the number of binary
> packages built?  If that is the case, it was completely unintentional.

Meh, apparently nope, I was tricked by that dpkg change in the Binary
field... I had only looked at the uploaded .changes, forgetting it
doesn't list anymore all the produced binaries…

Sorry for inappropriately pointing at you.


So, this was instead caused by Andrej's -3 upload, that has

--- libspring-java-4.3.22/debian/rules  2019-03-04 05:35:23.0 +0100
+++ libspring-java-4.3.22/debian/rules  2019-03-09 15:46:25.0 +0100
@@ -5,15 +5,18 @@

 JAVA_HOME   := /usr/lib/jvm/default-java

-MODULES = aop beans context context-support core expression instrument jdbc 
jms messaging orm oxm test tx web webmvc webmvc-portlet
+# MODULES = aop beans context context-support core expression instrument jdbc 
jms messaging orm oxm test tx web webmvc webmvc-portlet
+MODULES = aop beans context context-support core expression instrument jdbc 
orm oxm test tx web webmvc webmvc-portlet

 %:
-   dh $@ --buildsystem=gradle
+   dh $@ --buildsystem=gradle -Nlibspring-messaging-java 
-Nlibspring-jms-java

 override_dh_auto_build:
dh_auto_build -- jar -x test -x check \
 -x :spring-orm-hibernate4:compileJava \
 -x :spring-orm-hibernate5:compileJava \
+-x :spring-jms:compileJava \
+-x :spring-messaging:compileJava \
 -x :spring-instrument-tomcat:compileJava \
 -x :spring-webmvc-tiles2:compileJava \
 -x :spring-websocket:compileJava


(srly?  Using dh -N instead of removing the packages from d/control?!…).


Anyway, this also wasn't mentioned in the changelog...


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

[Andrej Shadura]

On Wed, 27 Mar 2019 12:01:40 +0100 Mattia Rizzolo  wrote:
> On Tue, Mar 26, 2019 at 04:35:41PM -0700, tony mancill wrote:
> > Are you sure about the upload of 4.3.22-2 changing the number of binary
> > packages built?  If that is the case, it was completely unintentional.
> 
> Meh, apparently nope, I was tricked by that dpkg change in the Binary
> field... I had only looked at the uploaded .changes, forgetting it
> doesn't list anymore all the produced binaries…
> 
> Sorry for inappropriately pointing at you.
> 
> So, this was instead caused by Andrej's -3 upload, that has
> 
> --- libspring-java-4.3.22/debian/rules  2019-03-04 05:35:23.0 +0100
> +++ libspring-java-4.3.22/debian/rules  2019-03-09 15:46:25.0 +0100
> @@ -5,15 +5,18 @@
> 
>  JAVA_HOME   := /usr/lib/jvm/default-java
> 
> -MODULES = aop beans context context-support core expression instrument jdbc 
> jms messaging orm oxm test tx web webmvc webmvc-portlet
> +# MODULES = aop beans context context-support core expression instrument 
> jdbc jms messaging orm oxm test tx web webmvc webmvc-portlet
> +MODULES = aop beans context context-support core expression instrument jdbc 
> orm oxm test tx web webmvc webmvc-portlet
> 
>  %:
> -   dh $@ --buildsystem=gradle
> +   dh $@ --buildsystem=gradle -Nlibspring-messaging-java 
> -Nlibspring-jms-java
> 
>  override_dh_auto_build:
> dh_auto_build -- jar -x test -x check \
>  -x :spring-orm-hibernate4:compileJava \
>  -x :spring-orm-hibernate5:compileJava \
> +-x :spring-jms:compileJava \
> +-x :spring-messaging:compileJava \
>  -x :spring-instrument-tomcat:compileJava \
>  -x :spring-webmvc-tiles2:compileJava \
>  -x :spring-websocket:compileJava
> 
> 
> (srly?  Using dh -N instead of removing the packages from d/control?!…).

Yes, so that it’s easier to bring them back when they’re unbroken.

> Anyway, this also wasn't mentioned in the changelog...

It was, indirectly:

  * Disable jasperreports support since it is RC-buggy.
  * Don’t build against libreactor-core-java since it depends on RC-
buggy openhft.


-- 
Cheers,
  Andrej

__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

[Andrej Shadura]

On Tue, 26 Mar 2019 16:35:41 -0700 tony mancill  wrote:
> Regarding the OpenHFT, I tried to help the overall situation by
> uploading new versions to experimental several months back but as was
> discussed on the list (I'd have to find the link), was requested to
> hold-off on transitioning them into unstable.

I tried completing that work, but unfortunately I ran into a compiler
bug in openhft-chronicle-wire:

[INFO] Compiling 107 source files to
/tmp/openhft-chronicle-wire/openhft-chronicle-wire/target/classes
compiler message file broken: key=compiler.misc.msg.bug
arguments=11.0.2, {1}, {2}, {3}, {4}, {5}, {6}, {7}
java.lang.AssertionError: exception_index is not set
at jdk.compiler/com.sun.tools.javac.util.Assert.error(Assert.java:162)
at jdk.compiler/com.sun.tools.javac.util.Assert.check(Assert.java:95)
at
jdk.compiler/com.sun.tools.javac.code.TypeAnnotationPosition.getExceptionIndex(TypeAnnotationPosition.java:307)
at
jdk.compiler/com.sun.tools.javac.jvm.ClassWriter.writePosition(ClassWriter.java:908)
at
jdk.compiler/com.sun.tools.javac.jvm.ClassWriter.writeTypeAnnotation(ClassWriter.java:879)
at
jdk.compiler/com.sun.tools.javac.jvm.ClassWriter.writeTypeAnnotations(ClassWriter.java:793)
at
jdk.compiler/com.sun.tools.javac.jvm.ClassWriter.writeCode(ClassWriter.java:1352)
at
jdk.compiler/com.sun.tools.javac.jvm.ClassWriter.writeMethod(ClassWriter.java:1220)
at
jdk.compiler/com.sun.tools.javac.jvm.ClassWriter.writeMethods(ClassWriter.java:1715)
at
jdk.compiler/com.sun.tools.javac.jvm.ClassWriter.writeClassFile(ClassWriter.java:1825)
at
jdk.compiler/com.sun.tools.javac.jvm.ClassWriter.writeClass(ClassWriter.java:1741)
at
jdk.compiler/com.sun.tools.javac.main.JavaCompiler.genCode(JavaCompiler.java:757)
at
jdk.compiler/com.sun.tools.javac.main.JavaCompiler.generate(JavaCompiler.java:1635)
at
jdk.compiler/com.sun.tools.javac.main.JavaCompiler.generate(JavaCompiler.java:1603)
at
jdk.compiler/com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:973)
at
jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.lambda$doCall$0(JavacTaskImpl.java:104)
at
jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.handleExceptions(JavacTaskImpl.java:147)
at
jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:100)
at
jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:94)
at
org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126)
at
org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:176)
at
org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:1129)
at
org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:188)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:192)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:181)
at org.debian.maven.Wrapper.main(Wrapper.java:89)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launch

Bug#925509: netbeans: Netbeans not usable with java in Buster

[Markus Koschany]

Control: forcemerge 925509 925510
Control: severity -1 serious

Am 25.03.19 um 23:26 schrieb Wouter Wijsman:
[...]
> A java.lang.NoSuchMethodError exception has occurred.
> Please report this at 
> https://issues.apache.org/jira/projects/NETBEANS/issues,
> including a copy of your messages.log file as an attachment.
> The messages.log file is located in your
> /home/wouter/.netbeans/10.0/var/log folder.
> 
> The full log can be found here: https://pastebin.com/0wgJNt15
> 
> I hope that helps. I can provide more information if needed.

Hello and thanks for reporting!

java.lang.NoSuchMethodError:
com.sun.tools.javadoc.main.JavadocClassFinder: method
(Lcom/sun/tools/javac/util/Context;)V not found

This look like an incompatibility with Java 11.

Jaroslav and Jan, might this be related to nb-javac again? Here is the
full log.

https://pastebin.com/0wgJNt15

and the link to the full bug report.

https://bugs.debian.org/925509

Regards,

Markus



signature.asc
Description: OpenPGP digital signature
__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.

Processed: Re: Bug#925509: netbeans: Netbeans not usable with java in Buster

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 925509 925510
Bug #925509 [netbeans] netbeans: Netbeans not usable with java in Buster
Bug #925510 [netbeans] netbeans: Netbeans not usable with java in Buster
Merged 925509 925510
> severity -1 serious
Bug #925509 [netbeans] netbeans: Netbeans not usable with java in Buster
Bug #925510 [netbeans] netbeans: Netbeans not usable with java in Buster
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'

-- 
925509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925509
925510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

[Andrej Shadura]

On Tue, 26 Mar 2019 15:27:38 +0100 Emmanuel Bourg 
wrote:> I think this was done to remove the openhft packages that are
> incompatible with Java 11. But maybe the affected Spring modules could
> be salvaged by disabling the code using openhft (if it's optional).

I’m not entirely sure it is possible. But maybe someone else is going to
have better luck removing openhft dependencies.

-- 
Cheers,
  Andrej

__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

[Mattia Rizzolo]

On Wed, Mar 27, 2019 at 12:37:17PM +0100, Andrej Shadura wrote:
> > (srly?  Using dh -N instead of removing the packages from d/control?!…).
> 
> Yes, so that it’s easier to bring them back when they’re unbroken.

But that doesn't help anything.

You removed two packages because a dependency of them was RC buggy,
making other packages uninstallable because of this.

> > Anyway, this also wasn't mentioned in the changelog...
> 
> It was, indirectly:
> 
>   * Disable jasperreports support since it is RC-buggy.
>   * Don’t build against libreactor-core-java since it depends on RC-
> buggy openhft.

We are in freeze, changelogs are read by people who don't always know
what this thing is.  Reading that I would never suspect that binaries
packages have been removed; please try to be more explicit and lengthy
in your changelogs.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#925533: libspring-java: stopped building libspring-jms-java and libspring-messaging-java

[Emmanuel Bourg]

Le 27/03/2019 à 12:41, Andrej Shadura a écrit :

> I’m not entirely sure it is possible. But maybe someone else is going to
> have better luck removing openhft dependencies.

I'll get a look during the Paris BSP on sunday.

Emmanuel Bourg

__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#925617: jh_build initializes javac_opts with javadoc_opts, discard javac options

[Matthias Klose]

Package: src:javatools
Version: 0.72.6
Severity: serious
Tags: sid buster patch

jh_build initializes javac_opts with javadoc_opts, discard javac options,
apparently a typo.

patch at
http://launchpadlibrarian.net/416705136/javatools_0.72.6_0.72.6ubuntu1.diff.gz

__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#839173: marked as done (javahelper: jh_installjavadoc fails to parse -P option)

[Debian Bug Tracking System]

Your message dated Wed, 27 Mar 2019 19:41:00 +
with message-id <07d2005a-030a-9136-d4ca-2d60df0f5...@thykier.net>
and subject line Re: javahelper: jh_installjavadoc fails to parse -P option
has caused the Debian Bug report #839173,
regarding javahelper: jh_installjavadoc fails to parse -P option
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
839173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839173
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: javahelper
Version: 0.58
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,

I am attempting to use jh_installjavadoc on a manually compiled javadoc.
The package uses tmpdirs in the form debian/tmp/$package. I therefore
passed the -P option exactly as requested by the man page, but it had no
effect: the javadoc was copied to
debian/libprocessing3-java-doc/usr/share/doc/libprocessing3-java-doc/api/.
The command line I used was

jh_installjavadoc -plibprocessing3-java-doc 
-Pdebian/tmp/libprocessing3-java-doc $OUTDIR 
/usr/share/doc/libprocessing3-java-doc/api/

where $OUTDIR is the temporary folder the javadocs were built to.

The debian/$package notation appears to be hardcoded into
jh_installjavadocs. Please could this be fixed?

Many thanks,
George Bateman.

- -- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages javahelper depends on:
ii  bsdmainutils 9.0.10
ii  dctrl-tools  2.24-2
ii  debhelper10
ii  devscripts   2.16.7
ii  dpkg-dev 1.18.10
ii  libarchive-zip-perl  1.59-1
ii  perl 5.22.2-5

javahelper recommends no packages.

Versions of packages javahelper suggests:
pn  cvs   
ii  gawk  1:4.1.3+dfsg-0.1
pn  tofrodos  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQE4BAEBCAAiBQJX7WQ5GxxnZW9yZ2UuYmF0ZW1hbjE2QGdtYWlsLmNvbQAKCRDE
F6qcQDnvz7NfB/4vWQMpJ3Qzrspp1CB9vU5G5W6Ooi2d6v0bFYv4WP3HHyvEOzwR
SV6kPH7TgUzYEdrh3OvwkCTgn3fUza5zfqV/r3O2bdKK731bPVcxi1DpzJQ/W1mK
3NsxlAbsePS/W766F2NoUolk01OZvn6SKjySXwhPUvUDgm8lLw7iztu8o9ogFcob
IKG3Dq2EQyEcdpxnITahZ+ZEqZUGXGPmncXBuX2Qv4DIRJx33aKAVcvDTCnRlkEn
/h+JteObdTbw3cYri8AJpfDd8Pi5eu5/GRTJi2zgM3G8HMi98a3oOHIsjZRHTfEJ
PgejjNWLzOEUxgLoEucH2tK/uxOo+yCO6Aa3
=2kx6
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: javatools
Source-Version: 0.71

On Thu, 29 Sep 2016 19:58:09 +0100 George Bateman
 wrote:
> Package: javahelper
> Version: 0.58
> Severity: important
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Dear Maintainer,
> 
> I am attempting to use jh_installjavadoc on a manually compiled javadoc.
> The package uses tmpdirs in the form debian/tmp/$package. I therefore
> passed the -P option exactly as requested by the man page, but it had no
> effect: the javadoc was copied to
> debian/libprocessing3-java-doc/usr/share/doc/libprocessing3-java-doc/api/.
> The command line I used was
> 
> jh_installjavadoc -plibprocessing3-java-doc 
> -Pdebian/tmp/libprocessing3-java-doc $OUTDIR 
> /usr/share/doc/libprocessing3-java-doc/api/
> 
> where $OUTDIR is the temporary folder the javadocs were built to.
> 
> The debian/$package notation appears to be hardcoded into
> jh_installjavadocs. Please could this be fixed?
> 
> Many thanks,
> George Bateman.
> 
> [...]
This was fixed as a part of the jh_installjavadocs rewrite.  It happened
before 0.71, but 0.71 contains the last (at the time of writing known)
regression fix for jh_installjavadocs.

Thanks,
~Niels--- End Message ---
__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#925869: zookeeper: ftbfs with GCC-9

[Matthias Klose]

Package: src:zookeeper
Version: 3.4.13-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/zookeeper_3.4.13-1_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
checking netdb.h presence... yes
checking for netdb.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for unistd.h... (cached) yes
checking sys/utsname.h usability... yes
checking sys/utsname.h presence... yes
checking for sys/utsname.h... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking whether time.h and sys/time.h may both be included... yes
checking for nfds_t... yes
checking whether to enable ipv6... yes
checking for getcwd... yes
checking for gethostbyname... yes
checking for gethostname... yes
checking for getlogin... yes
checking for getpwuid_r... yes
checking for gettimeofday... yes
checking for getuid... yes
checking for memmove... yes
checking for memset... yes
checking for poll... yes
checking for socket... yes
checking for strchr... yes
checking for strdup... yes
checking for strerror... yes
checking for strtol... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
/usr/bin/make -C src/c
make[2]: Entering directory '/<>/src/c'
(CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash /<>/src/c/missing 
autoheader)
rm -f stamp-h1
touch config.h.in
cd . && /bin/bash ./config.status config.h
config.status: creating config.h
config.status: config.h is unchanged
/usr/bin/make  all-am
make[3]: Entering directory '/<>/src/c'
gcc -DHAVE_CONFIG_H -I.  -I./include -I./tests -I./generated  -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Werror  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -MT cli.o -MD -MP -MF 
.deps/cli.Tpo -c -o cli.o `test -f 'src/cli.c' || echo './'`src/cli.c
In file included from /usr/include/string.h:494,
 from src/cli.c:31:
In function 'strncpy',
inlined from 'main' at src/cli.c:559:9:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: error: 
'__builtin_strncpy' specified bound 1024 equals destination size 
[-Werror=stringop-truncation]
  106 |   return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest));
  |  ^~
cc1: all warnings being treated as errors
make[3]: *** [Makefile:1057: cli.o] Error 1
make[3]: Leaving directory '/<>/src/c'
make[2]: *** [Makefile:671: all] Error 2
make[2]: Leaving directory '/<>/src/c'
make[1]: *** [debian/rules:30: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:20: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.

Processed (with 1 error): forcibly merging 924328 925617

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 924328 925617
Bug #924328 [javahelper] javahelper: jh_build regressed for -doc packages
Bug #924339 [javahelper] javahelper: jh_build regressed for -doc packages
Unable to merge bugs because:
package of #925617 is 'src:javatools' not 'javahelper'
Failed to forcibly merge 924328: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
924328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924328
924339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924339
925617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.

jajuk is marked for autoremoval from testing

[Debian testing autoremoval watch]

jajuk 1:1.10.9+dfsg2-4 is marked for autoremoval from testing on 2019-04-08

It is affected by these RC bugs:
923330: jajuk: Fails to start with Java Runtime Environment 1.7 minimum 
required. You use a JVM ext.JVM@23fc625e


__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.