Processed: bug 912297 is forwarded to https://github.com/ansible/ansible/pull/47436

[Debian Bug Tracking System]

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

> forwarded 912297 https://github.com/ansible/ansible/pull/47436
Bug #912297 {Done: Ivo De Decker } [ansible] ansible: 
CVE-2018-16837
Set Bug forwarded-to-address to 'https://github.com/ansible/ansible/pull/47436'.
> thanks
Stopping processing here.

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

Bug#912297: ansible: CVE-2018-16837

[Chris Lamb]

Hi Ivo,

> From the upstream changelog for 2.7.1+dfsg-1 (already in unstable):
[..]
> - user module - do not pass ssh_key_passphrase on cmdline
>   (CVE-2018-16837)

Thanks for providing this and no problem that this wasn't in the
changelog.

Security team: This still affects stretch and jessie as I unless
I'm missing something - would you like me to prepare an upload for
stable? I'm happy to take the LTS side of things.

(If so Ivo, can I push these to some VCS? I note it is in collab-
maint but I thought I might check...)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Processed: Re: pygame FTBFS on s390x, testsuite failure.

[Debian Bug Tracking System]

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

> found 902036 1.9.4.post1+dfsg-1
Bug #902036 {Done: Dominik George } [pygame] pygame 
FTBFS on s390x, testsuite failure.
There is no source info for the package 'pygame' at version 
'1.9.4.post1+dfsg-1' with architecture ''
Unable to make a source version for version '1.9.4.post1+dfsg-1'
Marked as found in versions 1.9.4.post1+dfsg-1; no longer marked as fixed in 
versions pygame/1.9.4.post1+dfsg-1 and reopened.
> tags 902036 +patch
Bug #902036 [pygame] pygame FTBFS on s390x, testsuite failure.
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#902036: pygame FTBFS on s390x, testsuite failure.

[peter green]

found 902036 1.9.4.post1+dfsg-1
tags 902036 +patch
thanks


On 30/10/18 02:03, peter green wrote:


Unfortunately while the 1.9.4.post1+dfsg-1 upload fixed the ppc64el failure, it 
did not fix the s390x failure.

I just took a look at this, turned out to be a typo in a #if causing a 32-bit 
value to be written to a 64-bit variable. The variable was initialized to zero 
earlier, so we got away with this on little endian 64-bit but on big endian 
64-bit it resulted in the value being 4294967296 times larger than it should be 
which resulted in an out of range error.

Debdiff attached, no immediate intent to NMU.
diff -Nru pygame-1.9.4.post1+dfsg/debian/changelog 
pygame-1.9.4.post1+dfsg/debian/changelog
--- pygame-1.9.4.post1+dfsg/debian/changelog2018-10-28 13:09:16.0 
+
+++ pygame-1.9.4.post1+dfsg/debian/changelog2018-10-30 03:03:07.0 
+
@@ -1,3 +1,10 @@
+pygame (1.9.4.post1+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix a typo that breaks bufferproxy on 64-bit big endian.
+
+ -- Peter Michael Green   Tue, 30 Oct 2018 03:03:07 +
+
 pygame (1.9.4.post1+dfsg-1) unstable; urgency=high
 
   [ Ondřej Nový ]
diff -Nru pygame-1.9.4.post1+dfsg/debian/patches/fix-bufferproxy-be64.patch 
pygame-1.9.4.post1+dfsg/debian/patches/fix-bufferproxy-be64.patch
--- pygame-1.9.4.post1+dfsg/debian/patches/fix-bufferproxy-be64.patch   
1970-01-01 00:00:00.0 +
+++ pygame-1.9.4.post1+dfsg/debian/patches/fix-bufferproxy-be64.patch   
2018-10-30 03:03:07.0 +
@@ -0,0 +1,22 @@
+Description: Fix a typo that breaks bufferproxy on 64-bit big endian.
+ A typo in a #if caused a wrong definition of ARG_FORMAT to be used
+ leading to reading a 32-bit value into a 64-bit variable on 64 bit
+ systems.
+ 
+ On little endian we got away with this because the 64-bit value is
+ initialised to zero. However on big endian this resulted in a value
+ 4294967296 times larger than it should be which resulted in an out
+ of range error.
+Author: Peter Michael Green 
+
+--- pygame-1.9.4.post1+dfsg.orig/src/bufferproxy.c
 pygame-1.9.4.post1+dfsg/src/bufferproxy.c
+@@ -479,7 +479,7 @@ proxy_write(PgBufproxyObject *self, PyOb
+ Py_ssize_t offset = 0;
+ char *keywords[] = {"buffer", "offset", 0};
+ 
+-#if Py_VERSION_HEX >= 0x0205
++#if PY_VERSION_HEX >= 0x0205
+ #define ARG_FORMAT "s#|n"
+ #else
+ #define ARG_FORMAT "s#|i"  /* In this case Py_ssize_t is an int */
diff -Nru pygame-1.9.4.post1+dfsg/debian/patches/series 
pygame-1.9.4.post1+dfsg/debian/patches/series
--- pygame-1.9.4.post1+dfsg/debian/patches/series   2018-10-28 
13:09:16.0 +
+++ pygame-1.9.4.post1+dfsg/debian/patches/series   2018-10-30 
03:03:07.0 +
@@ -5,3 +5,4 @@
 arithmetic_fixes.patch
 fix_sphinx_unicode.patch
 skip_flaky_tests_on_le.patch
+fix-bufferproxy-be64.patch

Bug#902036: pygame FTBFS on s390x, testsuite failure.

[peter green]

found 902036 1.9.4.post1+dfsg-1
thanks

Unfortunately while the 1.9.4.post1+dfsg-1 upload fixed the ppc64el failure, it 
did not fix the s390x failure.

Bug#912221: jabref: incompatible with openjdk 11

[Emmanuel Bourg]

Le 30/10/2018 à 00:41, gregor herrmann a écrit :

> I guess we need to make sure that we build with openjdk-8.
> (You know this better than me but I seem to remember that the plan
> was to keep openjdk-8 in buster for building packages?)

No please don't built with openjdk-8 if there is a workaround with
openjdk-11. Building with openjdk-8 is really a last resort solution,
and very few cases justify its use (see lombok for a good example).

Emmanuel Bourg

Bug#912153: marked as done (phpunit FTBFS with PHP 7.3)

[Debian Bug Tracking System]

Your message dated Tue, 30 Oct 2018 00:05:47 +
with message-id 
and subject line Bug#912153: fixed in phpunit 7.4.3-1
has caused the Debian Bug report #912153,
regarding phpunit FTBFS with PHP 7.3
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.)


-- 
912153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: phpunit
Version: 7.4.0-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/phpunit.html

...
There was 1 failure:

1) 
/build/1st/phpunit-7.4.0/tests/end-to-end/regression/GitHub/2591-separate-function-no-preserve-no-bootstrap-xdebug.phpt
Failed asserting that string matches format description.
--- Expected
+++ Actual
@@ @@
 There were 2 errors:
 
 1) Issue2591_SeparateFunctionNoPreserveTest::testChangedGlobalString
-PHPUnit\Framework\Exception:%sPHP Fatal error:  Class 
'PHPUnit\Framework\TestCase' not found %s
-%SPHP Stack trace:%S
+PHPUnit\Framework\Exception: PHP Fatal error:  Uncaught Error: Class 
'PHPUnit\Framework\TestCase' not found in 
/build/1st/phpunit-7.4.0/tests/end-to-end/regression/GitHub/2591/SeparateFunctionNoPreserveTest.php:16
+Stack trace:
 #0 Standard input code(31): require_once()
+#1 Standard input code(111): __phpunit_run_isolated_test()
+#2 {main}
+  thrown in 
/build/1st/phpunit-7.4.0/tests/end-to-end/regression/GitHub/2591/SeparateFunctionNoPreserveTest.php
 on line 16
+
 2) Issue2591_SeparateFunctionNoPreserveTest::testGlobalString
-PHPUnit\Framework\Exception:%sPHP Fatal error:  Class 
'PHPUnit\Framework\TestCase' not found %s
-%SPHP Stack trace:%S
-%a
+PHPUnit\Framework\Exception: PHP Fatal error:  Uncaught Error: Class 
'PHPUnit\Framework\TestCase' not found in 
/build/1st/phpunit-7.4.0/tests/end-to-end/regression/GitHub/2591/SeparateFunctionNoPreserveTest.php:16
+Stack trace:
+#0 Standard input code(31): require_once()
+#1 Standard input code(111): __phpunit_run_isolated_test()
+#2 {main}
+  thrown in 
/build/1st/phpunit-7.4.0/tests/end-to-end/regression/GitHub/2591/SeparateFunctionNoPreserveTest.php
 on line 16
+
 ERRORS!
 Tests: 2, Assertions: 0, Errors: 2.

/build/1st/phpunit-7.4.0/src/Framework/Constraint/Constraint.php:112
/build/1st/phpunit-7.4.0/src/Framework/Constraint/Constraint.php:60
/build/1st/phpunit-7.4.0/src/Framework/Assert.php:1855
/build/1st/phpunit-7.4.0/src/Framework/Assert.php:1555
/build/1st/phpunit-7.4.0/src/Runner/PhptTestCase.php:277
/build/1st/phpunit-7.4.0/src/Runner/PhptTestCase.php:166
/build/1st/phpunit-7.4.0/src/Framework/TestSuite.php:750
/build/1st/phpunit-7.4.0/src/Framework/TestSuite.php:750
/build/1st/phpunit-7.4.0/src/TextUI/TestRunner.php:613
/build/1st/phpunit-7.4.0/src/TextUI/Command.php:206
/build/1st/phpunit-7.4.0/src/TextUI/Command.php:162
...
Tests: 1989, Assertions: 3454, Failures: 1, Skipped: 4.
make[1]: *** [debian/rules:30: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: phpunit
Source-Version: 7.4.3-1

We believe that the bug you reported is fixed in the latest version of
phpunit, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated phpunit package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 29 Oct 2018 13:47:35 -1000
Source: phpunit
Binary: phpunit
Architecture: source
Version: 7.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Description:
 phpunit- Unit testing suite for PHP
Closes: 912153
Changes:
 phpunit (7.4.3-1) unstable; urgency=medium
 .
   * Team upload
 .
   [ Sebastian Bergmann ]
   * Allow sebastian/environment ^4.0
   * Prepare release
   * Skip failing test with PHP 7.3 (Closes: #912153)
Checksums-Sha1:
 afd741e3b6af06623a9d493c6db7bf45cd9f7abc 2042 phpunit_7.4.3-1.dsc
 a7f0188588c788bdcc03b9f6a2e2c204ca4ee10d 270276 phpunit_7.4.3.orig.tar.gz
 287acba0455a96e3c2494360bafc573c77075bf6 13300 phpunit_7.4.3-1.debian.tar.xz
 a8bbf172bfc695a41df77d931716b817d7640471 7089 phpunit_7.4.3-1_amd64.buildinfo

Bug#912052: marked as done (sslsplit: FTBFS: Failure in test -r session.pem)

[Debian Bug Tracking System]

Your message dated Mon, 29 Oct 2018 23:52:17 +
with message-id 
and subject line Bug#912052: fixed in sslsplit 0.5.4-1
has caused the Debian Bug report #912052,
regarding sslsplit: FTBFS: Failure in test -r session.pem
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.)


-- 
912052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912052
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sslsplit
Version: 0.5.3-1
Severity: serious
Tags: ftbfs

>From my pbuilder build log:

...
make -C extra/pki testreqs session
make[2]: Entering directory '/build/sslsplit-0.5.3/extra/pki'
openssl genrsa -out rsa.key 2048
openssl genrsa -out server.key 2048
Generating RSA private key, 2048 bit long modulus (2 primes)
Generating RSA private key, 2048 bit long modulus (2 primes)
.
+
+++
+.+
+.
.e is 65537 (0x010001)
openssl req -new -nodes -x509 -sha256 -out server.crt -key server.key \
   -config x509v3ca.cnf -extensions v3_crt \
   -subj '/C=CH/O=SSLsplit Test Certificate/CN=daniel.roe.ch/' \
   -set_serial 42 -days 365
cat server.crt server.key >server.pem
openssl s_server -accept 46143 -cert server.pem -quiet  & \
   pid=$! ; \
   sleep 1 ; \
   echo q | openssl s_client -connect localhost:46143 \
   -quiet -no_ign_eof -sess_out session.pem ; \
   kill $pid
+
e is 65537 (0x010001)
openssl req -new -nodes -x509 -sha256 -out rsa.crt -key rsa.key \
   -config x509v3ca.cnf -extensions v3_ca \
   -subj '/C=CH/O=SSLsplit Root CA/CN=SSLsplit Root CA/' \
   -set_serial 1 -days 3650
cat rsa.crt rsa.key >rsa.pem
mkdir -p targets
mkdir -p targets
openssl genrsa -out targets/daniel.roe.ch.key 2048
openssl genrsa -out targets/wildcard.roe.ch.key 2048
Generating RSA private key, 2048 bit long modulus (2 primes)
Generating RSA private key, 2048 bit long modulus (2 primes)
..++.++.+
..+.++.++
...++.++.+
e is 65537 (0x010001)
openssl req -new -sha256 -subj '/C=CH/CN=*.roe.ch/' \
   -key targets/wildcard.roe.ch.key \
   -out targets/wildcard.roe.ch.csr
..Can't load /nonexistent/.rnd into RNG
139907575923136:error:2406F079:random number
generator:RAND_load_file:Cannot open
file:../crypto/rand/randfile.c:88:Filename=/nonexistent/.rnd
...openssl x509 -req -sha256 -CAcreateserial -days 365 \
   -CA rsa.crt -CAkey rsa.key \
   -in targets/wildcard.roe.ch.csr \
   -out targets/wildcard.roe.ch.crt
..Signature ok
subject=C = CH, CN = *.roe.ch
Getting CA Private Key
..cat targets/wildcard.roe.ch.crt targets/wildcard.roe.ch.key rsa.crt \
   >targets/wildcard.roe.ch.pem
.rm -f targets/wildcard.roe.ch.key targets/wildcard.roe.ch.csr \
   targets/wildcard.roe.ch.crt
+
e is 65537 (0x010001)
openssl req -new -sha256 -subj '/C=CH/CN=daniel.roe.ch/' \
   -key targets/daniel.roe.ch.key \
   -out targets/daniel.roe.ch.csr
Can't load /nonexistent/.rnd into RNG
140554678874560:error:2406F079:random number
generator:RAND_load_file:Cannot open
file:../crypto/rand/randfile.c:88:Filename=/nonexistent/.rnd
openssl x509 -req -sha256 -CAcreateserial -days 365 \
   -CA rsa.crt -CAkey rsa.key \
   -in targets/daniel.roe.ch.csr \
   -out targets/daniel.roe.ch.crt
Signature ok
subject=C = CH, CN = daniel.roe.ch
Getting CA Private Key
cat targets/daniel.roe.ch.crt targets/daniel.roe.ch.key rsa.crt \
   >targets/daniel.roe.ch.pem
rm -f targets/daniel.roe.ch.key targets/daniel.roe.ch.csr \
   targets/daniel.roe.ch.crt
rm -f rsa.srl
depth=0 C = CH, O = SSLsplit Test Certificate, CN = daniel.roe.ch
verify error:num=18:self signed certificate
verify return:1
depth=0 C = CH, O = SSLsplit Test Certificate, CN = daniel.roe.ch
verify return:1
DONE
test -r session.pem
make[2]: *** [GNUmakefile:117: session.pem] Error 1
make[2]: Leaving directory '/build/sslsplit-0.5.3/extra/pki'
make[1]: *** [GNUmakefile:410: test] Error 2
make[1]: 

Bug#911258: marked as done (libopenhmd-dev: missing dependency on libhidapi-dev, required by pkg-config metadata)

[Debian Bug Tracking System]

Your message dated Mon, 29 Oct 2018 23:50:39 +
with message-id 
and subject line Bug#911258: fixed in libopenhmd 0.2.0-4
has caused the Debian Bug report #911258,
regarding libopenhmd-dev: missing dependency on libhidapi-dev, required by 
pkg-config metadata
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.)


-- 
911258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libopenhmd-dev
Version: 0.2.0-2
Severity: serious
Tags: patch
Justification: Policy 3.5

libopenhmd-dev contains openhmd.pc, which Requires hidapi-libusb.
hidapi-libusb.pc is provided by libhidapi-dev, which is a
build-dependency for libopenhmd but is not included in libopenhmd's
dependencies.

The pkg-config file also contains an incorrect includedir and libdir,
because it assumes that the .pc file is installed 2 directories below
${prefix} (typically ${prefix}/lib/pkgconfig), but this is not true in
Debian. I attach proposed patches to fix this. Note that they include a
non-upstreamed patch for the pkg-config metadata.

This class of bug is easy to detect with an autopkgtest that builds
and runs a simple program (also included in the attached patches).

Regards,
smcv
>From f89ce3e8b599cf7783fb5db23d95d15315c1186e Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Wed, 17 Oct 2018 17:14:57 +0100
Subject: [PATCH 1/3] d/tests/build: Add a simple compile/link/execute test

---
 debian/changelog |  6 ++
 debian/tests/build   | 23 +++
 debian/tests/control |  3 +++
 3 files changed, 32 insertions(+)
 create mode 100755 debian/tests/build
 create mode 100644 debian/tests/control

diff --git a/debian/changelog b/debian/changelog
index fdf402e..6d71daa 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+libopenhmd (0.2.0-3.1) UNRELEASED; urgency=medium
+
+  * d/tests/build: Add a simple compile/link/execute test
+
+ -- Simon McVittie   Wed, 17 Oct 2018 17:14:22 +0100
+
 libopenhmd (0.2.0-3) unstable; urgency=medium
 
   * Fix filename in debian/watch
diff --git a/debian/tests/build b/debian/tests/build
new file mode 100755
index 000..9bb6c12
--- /dev/null
+++ b/debian/tests/build
@@ -0,0 +1,23 @@
+#!/bin/sh
+
+set -e
+exec 2>&1
+set -u
+set -x
+
+cd "$AUTOPKGTEST_TMP"
+cat > example.c <<'EOF'
+/* A very much simplified version of examples/simple/simple.c */
+#include 
+
+int main(void)
+{
+ohmd_context *ctx = ohmd_ctx_create();
+ohmd_ctx_destroy(ctx);
+return 0;
+}
+EOF
+
+gcc -o example example.c $(pkg-config --cflags --libs openhmd)
+test -x ./example
+./example
diff --git a/debian/tests/control b/debian/tests/control
new file mode 100644
index 000..9140881
--- /dev/null
+++ b/debian/tests/control
@@ -0,0 +1,3 @@
+Tests: build
+Restrictions: superficial
+Depends: build-essential, libopenhmd-dev, pkg-config
-- 
2.19.1

>From 66b6c5645d4edadbb2d80121e78a2ef4e901b357 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Wed, 17 Oct 2018 17:44:39 +0100
Subject: [PATCH 2/3] Make libopenhmd-dev depend on libhidapi-dev so the
 pkg-config metadata will work

---
 debian/changelog | 2 ++
 debian/control   | 3 ++-
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/debian/changelog b/debian/changelog
index 6d71daa..b7423fd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,8 @@
 libopenhmd (0.2.0-3.1) UNRELEASED; urgency=medium
 
   * d/tests/build: Add a simple compile/link/execute test
+  * Make libopenhmd-dev depend on libhidapi-dev so the pkg-config
+metadata will work
 
  -- Simon McVittie   Wed, 17 Oct 2018 17:14:22 +0100
 
diff --git a/debian/control b/debian/control
index 00f2ef4..38d4813 100644
--- a/debian/control
+++ b/debian/control
@@ -27,7 +27,8 @@ Description: API and drivers for immersive technology (shared library)
 Package: libopenhmd-dev
 Architecture: any
 Section: libdevel
-Depends: libopenhmd0 (= ${binary:Version}),
+Depends: libhidapi-dev,
+ libopenhmd0 (= ${binary:Version}),
  ${misc:Depends}
 Description: API and drivers for immersive technology (development files)
  OpenHMD aims to provide a Free and Open Source API and drivers for
-- 
2.19.1

>From 3bdd4fd30d4dda02dd101a6954379ad45d3d5832 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Wed, 17 Oct 2018 17:53:03 +0100
Subject: [PATCH 3/3] Further fixes to the pkg-config metadata

---
 debian/changelog  |  3 +
 ...code-the-hidapi-dependency-in-the-pk.patch | 70 +++
 ...titute-the-correct-libdir-includedir.patch | 27 +++
 

Processed: limit source to phpunit, tagging 912153

[Debian Bug Tracking System]

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

> limit source phpunit
Limiting to bugs with field 'source' containing at least one of 'phpunit'
Limit currently set to 'source':'phpunit'

> tags 912153 + pending
Bug #912153 [src:phpunit] phpunit FTBFS with PHP 7.3
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#912221: jabref: incompatible with openjdk 11

[gregor herrmann]

On Mon, 29 Oct 2018 16:33:54 -0700, tony mancill wrote:

> On Mon, Oct 29, 2018 at 11:44:36PM +0100, Emmanuel Bourg wrote:
> > jabref should no longer use the java.se.ee module, it was a temporary
> > module in Java 9 & 10 now removed in Java 11. jabref should add jaxb to
> > its classpath instead.
> Thanks Emmanuel.  Yes, I was able to get things working during the bus
> ride in this morning, 

:)
Great, thanks Tony.

> just need to finish up the wrapper script logic
> so it can start on Java 8, 9, 10, > 10 without the user having to worry
> with it...

Awesome.
 
> I'll look at the FTBFS as well.

I guess we need to make sure that we build with openjdk-8.
(You know this better than me but I seem to remember that the plan
was to keep openjdk-8 in buster for building packages?)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Janis Joplin: Cry Baby (live)


signature.asc
Description: Digital Signature

Bug#912221: jabref: incompatible with openjdk 11

[tony mancill]

On Mon, Oct 29, 2018 at 11:44:36PM +0100, Emmanuel Bourg wrote:
> Le 29/10/2018 à 13:54, gregor herrmann a écrit :
> 
> > Now that openjdk 11 is the default, jabref won't start without some
> > help:
> > 
> > % jabref
> > Error occurred during initialization of boot layer
> > java.lang.module.FindException: Module java.se.ee not found
> 
> jabref should no longer use the java.se.ee module, it was a temporary
> module in Java 9 & 10 now removed in Java 11. jabref should add jaxb to
> its classpath instead.

Thanks Emmanuel.  Yes, I was able to get things working during the bus
ride in this morning, just need to finish up the wrapper script logic
so it can start on Java 8, 9, 10, > 10 without the user having to worry
with it...

I'll look at the FTBFS as well.


signature.asc
Description: PGP signature

Bug#912232: marked as done (carrotsearch-hppc FTBFS with OpenJDK 11)

[Debian Bug Tracking System]

Your message dated Mon, 29 Oct 2018 23:13:48 +
with message-id 
and subject line Bug#912232: fixed in carrotsearch-hppc 0.6.1-6
has caused the Debian Bug report #912232,
regarding carrotsearch-hppc FTBFS with OpenJDK 11
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.)


-- 
912232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912232
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: carrotsearch-hppc
Version: 0.6.1-5
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/carrotsearch-hppc.html

...
[INFO] -
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] HPPC (parent POM) 0.6.1  SUCCESS [  0.007 s]
[INFO] HPPC Template Processor  SUCCESS [  3.539 s]
[INFO] HPPC Collections 0.6.1 . FAILURE [ 12.315 s]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 16.238 s
[INFO] Finished at: 2018-10-28T22:31:41-12:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) 
on project hppc: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/carrotsearch-hppc-0.6.1/hppc-core/target/generated-sources/main/java/com/carrotsearch/hppc/ShortContainer.java:[16,19]
 package javax.annotation does not exist
[ERROR] 
/build/1st/carrotsearch-hppc-0.6.1/hppc-core/target/generated-sources/main/java/com/carrotsearch/hppc/ShortCollection.java:[9,19]
 package javax.annotation does not exist
[ERROR] 
/build/1st/carrotsearch-hppc-0.6.1/hppc-core/target/generated-sources/main/java/com/carrotsearch/hppc/ShortSet.java:[9,19]
 package javax.annotation does not exist
[ERROR] 
/build/1st/carrotsearch-hppc-0.6.1/hppc-core/target/generated-sources/main/java/com/carrotsearch/hppc/cursors/ShortCursor.java:[6,19]
 package javax.annotation does not exist
[ERROR] 
/build/1st/carrotsearch-hppc-0.6.1/hppc-core/target/generated-sources/main/java/com/carrotsearch/hppc/ShortLookupContainer.java:[8,19]
 package javax.annotation does not exist
[ERROR] 
/build/1st/carrotsearch-hppc-0.6.1/hppc-core/target/generated-sources/main/java/com/carrotsearch/hppc/predicates/ShortPredicate.java:[6,19]
 package javax.annotation does not exist
[ERROR] 
/build/1st/carrotsearch-hppc-0.6.1/hppc-core/target/generated-sources/main/java/com/carrotsearch/hppc/procedures/ShortProcedure.java:[6,19]
 package javax.annotation does not exist
[ERROR] 
/build/1st/carrotsearch-hppc-0.6.1/hppc-core/target/generated-sources/main/java/com/carrotsearch/hppc/cursors/IntCursor.java:[6,19]
 package javax.annotation does not exist
...
--- End Message ---
--- Begin Message ---
Source: carrotsearch-hppc
Source-Version: 0.6.1-6

We believe that the bug you reported is fixed in the latest version of
carrotsearch-hppc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated carrotsearch-hppc 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Oct 2018 23:20:35 +0100
Source: carrotsearch-hppc
Binary: libcarrotsearch-hppc-java
Architecture: source
Version: 0.6.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Java maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libcarrotsearch-hppc-java - High Performance Primitive Collections for Java
Closes: 912232
Changes:
 carrotsearch-hppc (0.6.1-6) unstable; urgency=medium
 .
   * Team upload.
   * Removed the @Generated annotation in the template to fix the build
 failure with Java 11 (Closes: #912232)
   * Standards-Version updated to 4.2.1
   * Use salsa.debian.org Vcs-* URLs
Checksums-Sha1:
 59f9de4aa63b4a43bff5abb56b32d4d6130686bf 2137 carrotsearch-hppc_0.6.1-6.dsc
 

Bug#912234: marked as done (commons-httpclient FTBFS with OpenJDK 11)

[Debian Bug Tracking System]

Your message dated Mon, 29 Oct 2018 23:14:08 +
with message-id 
and subject line Bug#912234: fixed in commons-httpclient 3.1-15
has caused the Debian Bug report #912234,
regarding commons-httpclient FTBFS with OpenJDK 11
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.)


-- 
912234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: commons-httpclient
Version: 3.1-14
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/commons-httpclient.html

...
[ERROR] Tests run: 591, Failures: 0, Errors: 29, Skipped: 0, Time elapsed: 
24.172 s <<< FAILURE! - in org.apache.commons.httpclient.TestAll
[ERROR] 
testTunnellingParamsHostHTTP10AndMethodHTTP11(org.apache.commons.httpclient.params.TestSSLTunnelParams)
  Time elapsed: 0.45 s  <<< ERROR!
javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake
at 
java.base/sun.security.ssl.SSLSocketImpl.handleEOF(SSLSocketImpl.java:1321)
at 
java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1160)
at 
java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1063)
at 
java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:402)
at 
java.base/sun.security.ssl.SSLSocketImpl.ensureNegotiated(SSLSocketImpl.java:716)
at 
java.base/sun.security.ssl.SSLSocketImpl$AppOutputStream.write(SSLSocketImpl.java:970)
at 
java.base/java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:81)
at 
java.base/java.io.BufferedOutputStream.flush(BufferedOutputStream.java:142)
at 
org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:828)
at 
org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2116)
at 
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at 
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at 
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at 
org.apache.commons.httpclient.params.TestSSLTunnelParams.testTunnellingParamsHostHTTP10AndMethodHTTP11(TestSSLTunnelParams.java:182)
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at 
java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:167)
at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:108)
at 
java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1152)
... 41 more

...
--- End Message ---
--- Begin Message ---
Source: commons-httpclient
Source-Version: 3.1-15

We believe that the bug you reported is fixed in the latest version of
commons-httpclient, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated commons-httpclient 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Oct 2018 22:56:50 +0100
Source: commons-httpclient
Binary: libcommons-httpclient-java libcommons-httpclient-java-doc
Architecture: source
Version: 3.1-15
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libcommons-httpclient-java - Commons HTTPClient - Java library for creating 
HTTP clients
 libcommons-httpclient-java-doc - Documentation for libcommons-httpclient-java
Closes: 889358 912234
Changes:
 commons-httpclient (3.1-15) unstable; urgency=medium
 .
   * Ignore the test failures with Java 11 (Closes: #912234)
   * Standards-Version updated to 4.2.1
   * Use salsa.debian.org Vcs-* URLs
   * Removed Damien Raude-Morvan from the uploaders (Closes: #889358)
Checksums-Sha1:
 4cd0211e60f8aeb0ce83155066ab96dabcdf0966 2346 commons-httpclient_3.1-15.dsc
 

Bug#908680: marked as done (erlang-erlware-commons: FTBFS in every architecture)

[Debian Bug Tracking System]

Your message dated Mon, 29 Oct 2018 23:14:36 +
with message-id 
and subject line Bug#908680: fixed in erlang-erlware-commons 1.2.0+dfsg-1
has caused the Debian Bug report #908680,
regarding erlang-erlware-commons: FTBFS in every architecture
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.)


-- 
908680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:erlang-erlware-commons
Version: 1.0.0+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

This package seems to fail to build everywhere:

https://buildd.debian.org/status/package.php?p=erlang%2derlware%2dcommons

Thanks.
--- End Message ---
--- Begin Message ---
Source: erlang-erlware-commons
Source-Version: 1.2.0+dfsg-1

We believe that the bug you reported is fixed in the latest version of
erlang-erlware-commons, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 908...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu  (supplier of updated 
erlang-erlware-commons package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 30 Oct 2018 07:45:24 +0900
Source: erlang-erlware-commons
Binary: erlang-erlware-commons
Architecture: source amd64
Version: 1.2.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Erlang Packagers 
Changed-By: Nobuhiro Iwamatsu 
Description:
 erlang-erlware-commons - Erlware common libraries
Closes: 908680
Changes:
 erlang-erlware-commons (1.2.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #908680)
Checksums-Sha1:
 f00e909061f3489d7483fa587242123233fadfed 2194 
erlang-erlware-commons_1.2.0+dfsg-1.dsc
 a60c8d39df67a08285e981a81f29681ee801f482 46368 
erlang-erlware-commons_1.2.0+dfsg.orig.tar.xz
 42bd34b4baf601a3e541f1855bddf43022fcdafd 3300 
erlang-erlware-commons_1.2.0+dfsg-1.debian.tar.xz
 9dadc36e681083ba8e423471c1657ac41a220049 9326 
erlang-erlware-commons_1.2.0+dfsg-1_amd64.buildinfo
 071b2ebaa245423c724729fc004bb56b02adb3f4 107880 
erlang-erlware-commons_1.2.0+dfsg-1_amd64.deb
Checksums-Sha256:
 99d053cf572aa05193fa4f0a58684f266fbbd7cb28e37851099d61398cb541e8 2194 
erlang-erlware-commons_1.2.0+dfsg-1.dsc
 ef48d5ead0f9350cbec003f52090007ee1ded70de31ed2980f124cd49f3120e4 46368 
erlang-erlware-commons_1.2.0+dfsg.orig.tar.xz
 c27d0010e1fc323584467220f7a7d48a61f38f23e952c3c33087685f406fc46b 3300 
erlang-erlware-commons_1.2.0+dfsg-1.debian.tar.xz
 f5257bbb191aba6308d26be81bd1e2b2c6054a9cd6dd3d6f0d9e982ac5be0d3d 9326 
erlang-erlware-commons_1.2.0+dfsg-1_amd64.buildinfo
 4f05dd45fcd285643d5e158e7e35ab861b9bd6ec41f38d511f94b539b55fc5d7 107880 
erlang-erlware-commons_1.2.0+dfsg-1_amd64.deb
Files:
 4066438dd94f28daa41db4ce8d50d188 2194 devel optional 
erlang-erlware-commons_1.2.0+dfsg-1.dsc
 140571b0a63cf38e2cf0221ed7ab7f6b 46368 devel optional 
erlang-erlware-commons_1.2.0+dfsg.orig.tar.xz
 0895808aca859efc01c761e06745be2c 3300 devel optional 
erlang-erlware-commons_1.2.0+dfsg-1.debian.tar.xz
 92f3c79cf60878efaa7a2ae37bfd297d 9326 devel optional 
erlang-erlware-commons_1.2.0+dfsg-1_amd64.buildinfo
 344d4251e4d3621d40b7d04d2c666068 107880 devel optional 
erlang-erlware-commons_1.2.0+dfsg-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXmKe5SMhlzV7hM9DMiR/u0CtH6YFAlvXj38ACgkQMiR/u0Ct
H6ZpRBAAgoIRJAocaH6/fMI6CYuiVrZHymcC0ddjC9kXsQtJejLg+wdNVZfNEjEu
MVdYAPL5ZmrsMiRdVzgJRr+x2ZIi4L68mOYc7hnm2jYOY2hZWOjydEc5FAEEr8Pc
bcLuRv++QWeTZ9M+oTaNjQQbbzIBS+RUABt/UPVdBHptUTResMFrXBLRwLv3kxIS
AqTnMcmuo5kR9mjyEVezYmnIAsW/HI9nP4px+d+VrQ3GYD1BRCico3wNuvri3KXA
6lVH1XFqTxxTWksTB0alkBOYGlylpP/14sng12AstJlFyX2hEiazIxGjfV6kjuGI
D865KXRB6EMP98F3TKnE3A7HBx5D9V5IAEkkh0aHZre5k/0ehHaoXi3GnpJw3zLI
Li06+QYBzdjgPcTzMGilgVjvQ7YsFK/ETG9Tju/RSyCJQ2OG8X5ZHznI3zwUYvBM
d4V9iRlsDqhQLkl86wP5vWcpE/p5d/bO2Eq9q4WuCQxRWVAWDY0lAx6rFNBJTPDa
ISAY5qv8r0UE8mk0E887SDcgcGlg+LkyG7b4lD+uNjgAdYreOijA1jpbCSoU47F3
I+M0hTaw8GzZKM/+Sy/4rvTEAugmLtOiAR235S73EhikbNarFoJvgtKcgB4M9Pfi
fA0swVvqYLdyNhYcF+Bk6S+sWwpoFfG0KONAlhIlP9QjZKeuYvY=
=8QAq
-END PGP SIGNATURE End Message ---

Bug#912221: jabref: incompatible with openjdk 11

[Emmanuel Bourg]

Le 29/10/2018 à 13:54, gregor herrmann a écrit :

> Now that openjdk 11 is the default, jabref won't start without some
> help:
> 
> % jabref
> Error occurred during initialization of boot layer
> java.lang.module.FindException: Module java.se.ee not found

jabref should no longer use the java.se.ee module, it was a temporary
module in Java 9 & 10 now removed in Java 11. jabref should add jaxb to
its classpath instead.

Emmanuel Bourg

Bug#912221: jabref: incompatible with openjdk 11

[gregor herrmann]

Control: tag -1 + ftbfs

On Mon, 29 Oct 2018 13:54:26 +0100, gregor herrmann wrote:

> Package: jabref
> Version: 3.8.2+ds-7
> Severity: important
> 
> Now that openjdk 11 is the default, jabref won't start without some
> help:
> 
> % jabref
> Error occurred during initialization of boot layer
> java.lang.module.FindException: Module java.se.ee not found

And it also FTBFS:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jabref.html

(Thanks to Adrian for already raising the severity.)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Simon and Garfunkel: American Tune


signature.asc
Description: Digital Signature

Processed: Re: Bug#912221: jabref: incompatible with openjdk 11

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + ftbfs
Bug #912221 [jabref] jabref: incompatible with openjdk 11
Added tag(s) ftbfs.

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

Bug#912231: bnd FTBFS with OpenJDK 11

[Markus Koschany]

The OpenJDK 11 issue is rather simple to fix, however the build fails
later on with this error message, a Gradle issue?

Patch is attached.

Cannot find pom file
/build/bnd-3.5.0/debian/.m2/repository/biz/aQute/bnd/aQute.libg/3.5.0/aQute.libg-3.5.0.pom
Oct 29, 2018 7:44:01 PM org.debian.maven.repo.POMCleaner cleanPom
SEVERE: null
java.io.FileNotFoundException:
debian/.m2/repository/biz/aQute/bnd/aQute.libg/3.5.0/aQute.libg-3.5.0.pom (No
such file or directory)
>---at java.base/java.io.FileInputStream.open0(Native Method)
>---at java.base/java.io.FileInputStream.open(FileInputStream.java:219)
>---at java.base/java.io.FileInputStream.(FileInputStream.java:157)
>---at org.debian.maven.util.Readers.read(Readers.java:50)
>---at org.debian.maven.repo.POMReader.readPom(POMReader.java:57)
>---at
org.debian.maven.repo.POMTransformer.transformPom(POMTransformer.java:226)
>---at
org.debian.maven.repo.POMTransformer.transformPom(POMTransformer.java:211)
>---at org.debian.maven.repo.POMCleaner.cleanPom(POMCleaner.java:75)
>---at org.debian.maven.repo.POMCleaner.main(POMCleaner.java:372)

Cannot find pom file
/build/bnd-3.5.0/debian/.m2/repository/biz/aQute/bnd/aQute.libg/3.5.0/aQute.libg-3.5.0.pom
Oct 29, 2018 7:44:02 PM org.debian.maven.repo.POMCleaner cleanPom
SEVERE: null
java.io.FileNotFoundException:
debian/.m2/repository/biz/aQute/bnd/aQute.libg/3.5.0/aQute.libg-3.5.0.pom (No
such file or directory)
>---at java.base/java.io.FileInputStream.open0(Native Method)
>---at java.base/java.io.FileInputStream.open(FileInputStream.java:219)
>---at java.base/java.io.FileInputStream.(FileInputStream.java:157)
>---at org.debian.maven.util.Readers.read(Readers.java:50)
>---at org.debian.maven.repo.POMReader.readPom(POMReader.java:57)
>---at
org.debian.maven.repo.POMTransformer.transformPom(POMTransformer.java:226)
>---at
org.debian.maven.repo.POMTransformer.transformPom(POMTransformer.java:211)
>---at org.debian.maven.repo.POMCleaner.cleanPom(POMCleaner.java:75)
>---at org.debian.maven.repo.POMCleaner.main(POMCleaner.java:372)

/usr/bin/mh_installpom: line 148: debian/.mh/pom.properties: No such
file or directory
make: *** [debian/rules:9: binary] Error 1
From: Markus Koschany 
Date: Mon, 29 Oct 2018 20:36:31 +0100
Subject: java11

Fix biz.aQute.remote/src/aQute/remote/agent/RedirectOutput.java:41: error:
nullOutputStream() in RedirectOutput cannot override nullOutputStream() in
OutputStream private static PrintStream nullOutputStream() { ^ attempting to
assign weaker access privileges; was public

Bug-Debian: https://bugs.debian.org/912231
Forwarded: no
---
 biz.aQute.remote/src/aQute/remote/agent/RedirectOutput.java | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/biz.aQute.remote/src/aQute/remote/agent/RedirectOutput.java b/biz.aQute.remote/src/aQute/remote/agent/RedirectOutput.java
index 28ee248..fde8e95 100644
--- a/biz.aQute.remote/src/aQute/remote/agent/RedirectOutput.java
+++ b/biz.aQute.remote/src/aQute/remote/agent/RedirectOutput.java
@@ -38,7 +38,7 @@ public class RedirectOutput extends PrintStream {
 		this.err = err;
 	}
 
-	private static PrintStream nullOutputStream() {
+	public static PrintStream nullOutputStream() {
 		return new PrintStream(new NullOutputStream());
 	}
 


signature.asc
Description: OpenPGP digital signature

Bug#912232: Bug #912232 in carrotsearch-hppc marked as pending

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #912232 in carrotsearch-hppc reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/java-team/carrotsearch-hppc/commit/47001231a0ba30c66c172b2ff519b3fdea7ce3b5


Removed the @Generated annotation in the template to fix the build failure with 
Java 11 (Closes: #912232)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912232

Processed: Bug #912232 in carrotsearch-hppc marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912232 [src:carrotsearch-hppc] carrotsearch-hppc FTBFS with OpenJDK 11
Added tag(s) pending.

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

Bug#912297: marked as done (ansible: CVE-2018-16837)

[Debian Bug Tracking System]

Your message dated Mon, 29 Oct 2018 23:08:59 +0100
with message-id <20181029220857.s2c3qbod6imko...@debian.org>
and subject line Re: ansible: CVE-2018-16837
has caused the Debian Bug report #912297,
regarding ansible: CVE-2018-16837
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.)


-- 
912297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ansible
Version: 1.7.2+dfsg-2
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for ansible.

CVE-2018-16837[0]:
| Ansible "User" module leaks any data which is passed on as a parameter
| to ssh-keygen. This could lean in undesirable situations such as
| passphrases credentials passed as a parameter for the ssh-keygen
| executable. Showing those credentials in clear text form for every
| user which have access just to the process list.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16837
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16837


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Version: 2.7.1+dfsg-1

Hi,

On Mon, Oct 29, 2018 at 05:50:54PM -0400, Chris Lamb wrote:
> The following vulnerability was published for ansible.
> 
> CVE-2018-16837[0]:
> | Ansible "User" module leaks any data which is passed on as a parameter
> | to ssh-keygen. This could lean in undesirable situations such as
> | passphrases credentials passed as a parameter for the ssh-keygen
> | executable. Showing those credentials in clear text form for every
> | user which have access just to the process list.
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

>From the upstream changelog for 2.7.1+dfsg-1 (already in unstable):

changelogs/CHANGELOG-v2.7.rst

- user module - do not pass ssh_key_passphrase on cmdline (CVE-2018-16837)

This wasn't mentioned in the debian changelog, however.

Closing.

Ivo--- End Message ---

Processed: Re: Bug#912266: tomcat7 FTBFS with OpenJDK 11

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + wontfix
Bug #912266 [src:tomcat7] tomcat7 FTBFS with OpenJDK 11
Added tag(s) wontfix.

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

Bug#912266: tomcat7 FTBFS with OpenJDK 11

[Emmanuel Bourg]

Control: tags -1 + wontfix

src:tomcat7 builds one package, libservlet3.0-java, which is only used
by eclipse. Once eclipse is removed tomcat7 will follow.

Bug#883731: marked as done (audacious: Debian packaging has incorrect license)

[Debian Bug Tracking System]

Your message dated Mon, 29 Oct 2018 22:05:17 +
with message-id 
and subject line Bug#883731: fixed in audacious 3.10-1
has caused the Debian Bug report #883731,
regarding audacious: Debian packaging has incorrect license
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.)


-- 
883731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: audacious
Version: 3.9-2
Severity: serious

Per Debian policy 2.3:

"Every package must be accompanied by a verbatim copy of its copyright
information and distribution license in the file 
/usr/share/doc/package/copyright
(see Copyright information for further details)."

The file /usr/share/doc/audacious/copyright shipped in the Debian package
is out of date and does not match the current Audacious license (GPL3 vs.
BSD 2-clause).

Worse, the Debian package patches out[1] the upstream license file which
is normally installed under /usr/share/audacious/COPYING and visible in
the "About" window when running Audacious.

You are currently distributing Audacious in violation both of our license
and of Debian's own policy.  Please include the original upstream license,
verbatim, in the Debian package, or stop distributing Audacious.

Thank you,

John Lindgren
Audacious maintainer

[1] 
https://sources.debian.org/patches/audacious/3.9-2/use-system-licenses.patch/
--- End Message ---
--- Begin Message ---
Source: audacious
Source-Version: 3.10-1

We believe that the bug you reported is fixed in the latest version of
audacious, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 883...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated audacious package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 28 Oct 2018 15:39:56 +0100
Source: audacious
Binary: audacious audacious-dev libaudcore5 libaudgui5 libaudtag3
Architecture: source
Version: 3.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Andrej Shadura 
Description:
 audacious  - small and fast audio player which supports lots of formats
 audacious-dev - audacious development files
 libaudcore5 - audacious core engine library
 libaudgui5 - audacious media player (libaudgui shared library)
 libaudtag3 - audacious media player (libaudtag shared library)
Closes: 883731
Changes:
 audacious (3.10-1) unstable; urgency=medium
 .
   * License review (Closes: #883731).
 - Drop use-system-licenses.patch.
 - Update debian/copyright.
 - Ship packaging under the same license as the upstream code.
Checksums-Sha1:
 ddf5464173de591419d3bda2781f1a071d77f010 2002 audacious_3.10-1.dsc
 451e5122f2042cc08798fb75a3ac14b1a155d21e 563531 audacious_3.10.orig.tar.bz2
 e251e589a990eac973f4e242b9087d3b7e997d72 15752 audacious_3.10-1.debian.tar.xz
 e1bbde05a2c92f0df576bb9e805b70d52aafdf33 12217 
audacious_3.10-1_source.buildinfo
Checksums-Sha256:
 db5a3753514894ecafa93b06aef2eed6e4acca4d98914b740fc1c69104cf48e2 2002 
audacious_3.10-1.dsc
 6e4d49ac48a373c4c47d605fe18fbd5854bc30af6fece11331069af40eaa3fb5 563531 
audacious_3.10.orig.tar.bz2
 be848d91bfb69e2fb1256f48740c47b127599328248f863dbd3d8044ce3c1726 15752 
audacious_3.10-1.debian.tar.xz
 23de2a4753e424315f8a9ba0dcc5eda7a3b022e69b6ec8d0514a466e81911adf 12217 
audacious_3.10-1_source.buildinfo
Files:
 91ad264b590aa2ea564200deb201baa5 2002 sound optional audacious_3.10-1.dsc
 95c79e14c412f274624c6979236a3840 563531 sound optional 
audacious_3.10.orig.tar.bz2
 f914572095b47004a015ee8da4262e7e 15752 sound optional 
audacious_3.10-1.debian.tar.xz
 db6b2a952c471a8a62850ccd4b24895e 12217 sound optional 
audacious_3.10-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAlvVy+MACgkQXkCM2RzY
OdIWKwf/d8tIk2VOU2Dd0b3bZXFiBWOBVHHbt5YfcLqiVIKQ7bKnb8c6But5ArjI
4HW3SMSIrGsYCKOPiHOwcPQcGmHYBcDRWV+sE8AByfubp+uJ7ImUiTFwhQVsY2tI
e6/gZXaeAsj7rE3za7cHCxuPa+2HQspd2lgXXInsGBNSoyamZMA1wmCbh0Xz6iKc
nso+5OOrGJH690ebDShTg+4aZ6PwHfHWx7FQ5qZpeyHcPvMrQLpvdHv3goK+kL2q
wWcjJZH5IK2Wr5zrmhPQVArcTpa9SjsQnqFW2XlgrxVLet8geMMSYwny3m3a21Eh

Bug#912234: Bug #912234 in commons-httpclient marked as pending

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #912234 in commons-httpclient reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/java-team/commons-httpclient/commit/5a9df164a82d1342847e7504b22d1b7bab10cc8f


Ignore the test failures with Java 11 (Closes: #912234)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912234

Processed: Bug #912234 in commons-httpclient marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912234 [src:commons-httpclient] commons-httpclient FTBFS with OpenJDK 11
Added tag(s) pending.

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

Bug#912297: ansible: CVE-2018-16837

[Chris Lamb]

Package: ansible
Version: 1.7.2+dfsg-2
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for ansible.

CVE-2018-16837[0]:
| Ansible "User" module leaks any data which is passed on as a parameter
| to ssh-keygen. This could lean in undesirable situations such as
| passphrases credentials passed as a parameter for the ssh-keygen
| executable. Showing those credentials in clear text form for every
| user which have access just to the process list.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16837
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16837


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#912295: jboss-jdeparser2 FTBFS with OpenJDK 11

[Adrian Bunk]

Source: jboss-jdeparser2
Version: 2.0.2-1
Severity: serious
Tags: ftbfs buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jboss-jdeparser2.html

...
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 3.884 s
[INFO] Finished at: 2018-10-29T07:13:06-12:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) 
on project jdeparser: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/jboss-jdeparser2-2.0.2/src/main/java/org/jboss/jdeparser/Assertions.java:[21,19]
 cannot find symbol
[ERROR]   symbol:   class Reflection
[ERROR]   location: package sun.reflect
[ERROR] 
/build/1st/jboss-jdeparser2-2.0.2/src/main/java/org/jboss/jdeparser/Assertions.java:[29,20]
 cannot find symbol
[ERROR]   symbol:   variable Reflection
[ERROR]   location: class org.jboss.jdeparser.Assertions
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/jboss-jdeparser2-2.0.2 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/jboss-jdeparser2-2.0.2/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/jboss-jdeparser2-2.0.2/debian 
-Dmaven.repo.local=/build/1st/jboss-jdeparser2-2.0.2/debian/maven-repo 
--batch-mode package javadoc:jar javadoc:aggregate -DskipTests 
-Dnotimestamp=true -Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build] Error 1

Bug#912296: jboss-modules FTBFS with OpenJDK 11

[Adrian Bunk]

Source: jboss-modules
Version: 1.8.6-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jboss-modules.html

...
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 4.708 s
[INFO] Finished at: 2019-12-01T14:56:10-12:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) 
on project jboss-modules: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/jboss-modules-1.8.6/src/main/java/org/jboss/modules/JDKSpecific.java:[37,19]
 cannot find symbol
[ERROR]   symbol:   class Reflection
[ERROR]   location: package sun.reflect
[ERROR] 
/build/1st/jboss-modules-1.8.6/src/main/java/org/jboss/modules/JDKSpecific.java:[85,22]
 cannot find symbol
[ERROR]   symbol:   variable Reflection
[ERROR]   location: class org.jboss.modules.JDKSpecific
[ERROR] 
/build/1st/jboss-modules-1.8.6/src/main/java/org/jboss/modules/JDKSpecific.java:[85,75]
 cannot find symbol
[ERROR]   symbol:   variable Reflection
[ERROR]   location: class org.jboss.modules.JDKSpecific
[ERROR] 
/build/1st/jboss-modules-1.8.6/src/main/java/org/jboss/modules/JDKSpecific.java:[87,22]
 cannot find symbol
[ERROR]   symbol:   variable Reflection
[ERROR]   location: class org.jboss.modules.JDKSpecific
[ERROR] 
/build/1st/jboss-modules-1.8.6/src/main/java/org/jboss/modules/JDKSpecific.java:[87,54]
 cannot find symbol
[ERROR]   symbol:   class Reflection
[ERROR]   location: class org.jboss.modules.JDKSpecific
[ERROR] 
/build/1st/jboss-modules-1.8.6/src/main/java/org/jboss/modules/JDKSpecific.java:[120,20]
 cannot find symbol
[ERROR]   symbol:   variable Reflection
[ERROR]   location: class org.jboss.modules.JDKSpecific
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/jboss-modules-1.8.6 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/jboss-modules-1.8.6/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/jboss-modules-1.8.6/debian 
-Dmaven.repo.local=/build/1st/jboss-modules-1.8.6/debian/maven-repo 
--batch-mode package javadoc:jar javadoc:aggregate -DskipTests 
-Dnotimestamp=true -Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build] Error 1

Bug#909218: Xmas Gift

[NOEL ANTOINE]

Donation to you, contact jleac...@outlook.com

Bug#912247: marked as done (starman FTBFS: ssl tests fail)

[Debian Bug Tracking System]

Your message dated Mon, 29 Oct 2018 21:39:33 +
with message-id 
and subject line Bug#912247: fixed in starman 0.4014-3
has caused the Debian Bug report #912247,
regarding starman FTBFS: ssl tests fail
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.)


-- 
912247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: starman
Version: 0.4014-2
Severity: serious
Tags: ftbfs

starman fails to build from source in unstable. Presumably openssl broke
it:

| t/ssl.t .. 
| Dubious, test returned 111 (wstat 28416, 0x6f00)
| No subtests run 
| 2018/10/29-15:24:42 Starman::Server (type Net::Server::PreFork) starting! 
pid(13247)
| Resolved [localhost]:46413 to [127.0.0.1]:46413, IPv4
| Binding to SSL port 46413 on host 127.0.0.1 with IPv4
| 2018/10/29-15:24:42 Cannot connect to SSL port 46413 on 127.0.0.1 [No such 
file or directory]
|   at line 105 in file /usr/share/perl5/Net/Server/Proto/SSL.pm
| 2018/10/29-15:24:42 Received QUIT. Running a graceful shutdown
| 2018/10/29-15:24:42 Worker processes cleaned up
| 2018/10/29-15:24:42 Server closing!
| cannot open port: 127.0.0.1:46413 at /usr/share/perl5/Test/TCP.pm line 53.
| t/ssl_largebody.t  
| Dubious, test returned 111 (wstat 28416, 0x6f00)
| No subtests run 
| 2018/10/29-15:24:59 Starman::Server (type Net::Server::PreFork) starting! 
pid(13283)
| Binding to TCP port 35767 on host 127.0.0.1 with IPv4
| Setting gid to "1000 1000 4 24 29 44 111 114 115 136 142 1000"
| 2018/10/29-15:24:59 Server closing!
...
| Test Summary Report
| ---
| t/ssl.t(Wstat: 28416 Tests: 0 Failed: 0)
|   Non-zero exit status: 111
|   Parse errors: No plan found in TAP output
| t/ssl_largebody.t  (Wstat: 28416 Tests: 0 Failed: 0)
|   Non-zero exit status: 111
|   Parse errors: No plan found in TAP output
| Files=13, Tests=111, 34 wallclock secs ( 0.04 usr  0.01 sys +  0.95 cusr  
0.22 csys =  1.22 CPU)
| Result: FAIL
| dh_auto_test: perl Build test --verbose 1 returned exit code 1
| make: *** [debian/rules:7: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut
--- End Message ---
--- Begin Message ---
Source: starman
Source-Version: 0.4014-3

We believe that the bug you reported is fixed in the latest version of
starman, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated starman package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 29 Oct 2018 20:57:51 +
Source: starman
Binary: starman
Architecture: source
Version: 0.4014-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Damyan Ivanov 
Closes: 912247
Description: 
 starman- high-performance preforking PSGI/Plack web server
Changes:
 starman (0.4014-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Xavier Guimard ]
   * Email change: Xavier Guimard -> y...@debian.org
 .
   [ Damyan Ivanov ]
   * replace test certificates with 2048-bit ones (Closes: #912247)
   * declare conformance with Policy 4.2.1 (no changes needed)
   * bump debhelper compatibility level to 11
Checksums-Sha1: 
 2da795ad45b29aa930d84cff1a9dc43d0c9911d7 2218 starman_0.4014-3.dsc
 cbb889db531bd6a2e4cc064aa0d8aae9408fb4d0 9064 starman_0.4014-3.debian.tar.xz
Checksums-Sha256: 
 cc94ba43ac08414ddcc5a3529a6b97977346df1327e1c9fea6455942270b6263 2218 
starman_0.4014-3.dsc
 2f6685a1e00ccb6961fcd0a2b8e4d834ac3bcc3ed969edf3bb29ffecc42604fa 9064 
starman_0.4014-3.debian.tar.xz
Files: 
 785f3bb0b3b19bc4629c5d732f4f64d1 2218 perl optional starman_0.4014-3.dsc
 155480fb8d2cbbb1c40d3b7a163a0ab4 9064 perl optional 
starman_0.4014-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErqDETssFbpNjDZ0z276dTZnSoAQFAlvXdSkACgkQ276dTZnS
oAQ0dQ//dgBPY95TuPJSsOPjkXwKLw9pw96ijhPmnFZePnfZNiMOi9hZc3bqCko/
rhBvk8f9yNalFJQTlNMJq/kOTYq8u/MYI84PVWu15OAh2myo66mzZZ/LJOhOUOqI
PyI+A64m2MhsoDuneKptoN8x2oQNru76HYbm98pKFK0Z1sv+pbwwbplU0XiJcBS7

Bug#912274: marked as done (ruby-clockwork FTBFS: Mocha::NotInitializedError: Mocha methods cannot be used outside the context of a test)

[Debian Bug Tracking System]

Your message dated Mon, 29 Oct 2018 23:09:16 +0200
with message-id <20181029210916.GB24921@localhost>
and subject line This seems to be already fixed in experimental
has caused the Debian Bug report #912274,
regarding ruby-clockwork FTBFS: Mocha::NotInitializedError: Mocha methods 
cannot be used outside the context of a test
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.)


-- 
912274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-clockwork
Version: 1.2.0-3
Severity: serious
Tags: ftbfs

ruby-clockwork fails to build from source in unstable.

|   1) Error:
| Clockwork::Event::#thread?::manager config thread option set to 
true#test_0001_is true:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/event_test.rb:12:in `block (4 levels) in '
| 
|   2) Error:
| Clockwork::Event::#thread?::manager config thread option set to 
true#test_0002_is false when event thread option set:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/event_test.rb:12:in `block (4 levels) in '
| 
|   3) Error:
| Clockwork::Manager#test_0013_exceptions still set the last timestamp to avoid 
spastic error loops:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/manager_test.rb:131:in `block (2 levels) in '
| 
|   4) Error:
| Clockwork#test_0006_support module re-open style:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/clockwork_test.rb:80:in `block (2 levels) in '
| 
|   5) Error:
| Clockwork#test_0001_should run events with configured logger:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/clockwork_test.rb:24:in `block (2 levels) in '
| 
|   6) Error:
| Clockwork#test_0002_should log event correctly:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/clockwork_test.rb:37:in `block (2 levels) in '
| 
|   7) Error:
| Clockwork#test_0004_should not run anything after reset:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/clockwork_test.rb:62:in `block (2 levels) in '
| 
|   8) Error:
| Clockwork#test_0003_should pass event without modification to handler:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/clockwork_test.rb:50:in `block (2 levels) in '
| 
|   9) Error:
| Clockwork#test_0005_should pass all arguments to every:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/clockwork_test.rb:69:in `block (2 levels) in '
| 
|  10) Error:
| Clockwork::Event::#thread?::manager config thread option not set#test_0001_is 
true if event thread option is true:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/event_test.rb:28:in `block (4 levels) in '
| 
|  11) Error:
| Clockwork::Manager::max_threads#test_0001_should warn when an event tries to 
generate threads more than max_threads:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/manager_test.rb:276:in `block (3 levels) in '
| 
|  12) Error:
| Clockwork::Manager::max_threads#test_0002_should not warn when thread is 
managed by others:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/manager_test.rb:291:in `block (3 levels) in '
| 
| 85 runs, 139 assertions, 0 failures, 12 errors, 0 skips
| rake aborted!
| Command failed with status (1): [ruby -w -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/at_test.rb" 
"test/clockwork_test.rb" "test/database_events/sync_performer_test.rb" 
"test/event_test.rb" "test/manager_test.rb" 
"test/database_events/test_helpers.rb" -v]
| 
| Tasks: TOP => default
| (See full trace by running task with --trace)
| ERROR: Test "ruby2.5" failed. Exiting.
| dh_auto_install: dh_ruby --install /<>/debian/ruby-clockwork 
returned exit code 1
| make: *** [debian/rules:6: binary] Error 1
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

Helmut
--- End Message ---
--- Begin Message ---
Version: 2.0.3-1

This seems to be already fixed in experimental:
https://tests.reproducible-builds.org/debian/rb-pkg/experimental/amd64/ruby-clockwork.html

cu
Adrian

-- 

   "Is 

Processed: Bug #912247 in starman marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912247 [src:starman] starman FTBFS: ssl tests fail
Added tag(s) pending.

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

Processed: bug 912247 is forwarded to https://github.com/miyagawa/Starman/pull/130

[Debian Bug Tracking System]

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

> forwarded 912247 https://github.com/miyagawa/Starman/pull/130
Bug #912247 [src:starman] starman FTBFS: ssl tests fail
Set Bug forwarded-to-address to 'https://github.com/miyagawa/Starman/pull/130'.
> thanks
Stopping processing here.

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

Bug#912247: Bug #912247 in starman marked as pending

[Damyan Ivanov]

Control: tag -1 pending

Hello,

Bug #912247 in starman reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/perl-team/modules/packages/starman/commit/8b7c67b63ea4c55cb21ad61342ee5b6fc7884d85


replace test certificates with 2048-bit ones

Closes: #912247 - FTBFS with openssl 1.1.1



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912247

Bug#912288: zeroc-ice FTBFS with OpenJDK 11

[Adrian Bunk]

Source: zeroc-ice
Version: 3.7.1-3
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zeroc-ice.html

...
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':test:compileJava'.
> error: invalid source release: 1.11

Bug#912286: libgzstream FTBFS on 32bit: symbol differences

[Adrian Bunk]

Source: libgzstream
Version: 1.5+dfsg-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=libgzstream=sid

...
   dh_makeshlibs -a -O--no-parallel
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libgzstream0/DEBIAN/symbols doesn't match 
completely debian/libgzstream0.symbols
--- debian/libgzstream0.symbols (libgzstream0_1.5+dfsg-3_i386)
+++ dpkg-gensymbolsguhOdo   2018-10-29 01:05:56.585746020 +
@@ -22,5 +22,7 @@
  _ZTT12gzstreambase@Base 1.5+dfsg
  _ZTV11gzstreambuf@Base 1.5+dfsg
  _ZTV12gzstreambase@Base 1.5+dfsg
- _ZTv0_n24_N12gzstreambaseD0Ev@Base 1.5+dfsg
- _ZTv0_n24_N12gzstreambaseD1Ev@Base 1.5+dfsg
+ _ZTv0_n12_N12gzstreambaseD0Ev@Base 1.5+dfsg-3
+ _ZTv0_n12_N12gzstreambaseD1Ev@Base 1.5+dfsg-3
+#MISSING: 1.5+dfsg-3# _ZTv0_n24_N12gzstreambaseD0Ev@Base 1.5+dfsg
+#MISSING: 1.5+dfsg-3# _ZTv0_n24_N12gzstreambaseD1Ev@Base 1.5+dfsg
dh_makeshlibs: failing due to earlier errors
make: *** [debian/rules:14: binary-arch] Error 2

Bug#912272: staden-io-lib FTBFS: dh_installdocs: Cannot find (any matches for) "README" (tried in .)

[Niels Thykier]

Helmut Grohne:
> Source: staden-io-lib
> Version: 1.14.9-4
> Severity: serious
> Tags: ftbfs
> 
> staden-io-lib fails to build from source in unstable. This smells a bit
> like a debhelper regression, but I'm not sure actually. In any case, it
> fails to build reliably.
> 
> |dh_installdocs -O--no-parallel
> | dh_installdocs: Cannot find (any matches for) "README" (tried in .)
> | 
> | make: *** [debian/rules:11: binary] Error 2
> | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
> exit status 2
> 
> Helmut
> 

That is a real issue in staden-io-lib.  The
debian/staden-io-lib-utils.docs file lists "README" but there is no
"README" in the source root.

Note that there was a regression in debhelper's reporting of such issues
which was fixed in debhelper/11.3.5 (#902355).  This can explain why
this issue was not noticed until now.

Thanks,
~Niels

Bug#897846: HELP needed for uploading a new debianisation of the Rheolef package

[Pierre Saramito]

Hi Andreas, 

I just commit with git a new release 7.0-2 of the debianisation 
of the rheolef package: it fixes a FTBS bug #897846 (see d/changelog). 

The upstream version is unchanged (7.0). 

Could you please upload it in debian ? 

Many thanks for your help. 

Best regards, 

Pierre 
-- 
Laboratoire Jean Kuntzmann, Grenoble, France 
http://ljk.imag.fr/membres/Pierre.Saramito 

Processed: tagging 912274

[Debian Bug Tracking System]

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

> tags 912274 + buster sid experimental
Bug #912274 [src:ruby-clockwork] ruby-clockwork FTBFS: 
Mocha::NotInitializedError: Mocha methods cannot be used outside the context of 
a test
Added tag(s) experimental, buster, and sid.
> thanks
Stopping processing here.

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

Bug#912272: staden-io-lib FTBFS: dh_installdocs: Cannot find (any matches for) "README" (tried in .)

[Andreas Tille]

Control: tags -1 pending

Hi Helmut,

On Mon, Oct 29, 2018 at 08:09:25PM +0100, Helmut Grohne wrote:
> staden-io-lib fails to build from source in unstable. This smells a bit
> like a debhelper regression, but I'm not sure actually. In any case, it
> fails to build reliably.
> 
> |dh_installdocs -O--no-parallel
> | dh_installdocs: Cannot find (any matches for) "README" (tried in .)

Strange since the file was renamed to README.md - no idea why this
has built in pbuilder before.

Anyway, fix is under way but needs to pass new since the new upstream
version has a soversion bump.

Thanks for all your QA work

  Andreas.

-- 
http://fam-tille.de

Processed: Re: Bug#912272: staden-io-lib FTBFS: dh_installdocs: Cannot find (any matches for) "README" (tried in .)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #912272 [src:staden-io-lib] staden-io-lib FTBFS: dh_installdocs: Cannot 
find (any matches for) "README" (tried in .)
Added tag(s) pending.

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

Bug#912255: marked as done (python-asdf FTBFS if some webserver is listening to localhost:80)

[Debian Bug Tracking System]

Your message dated Mon, 29 Oct 2018 19:49:22 +
with message-id 
and subject line Bug#912255: fixed in python-asdf 2.1.0-2
has caused the Debian Bug report #912255,
regarding python-asdf FTBFS if some webserver is listening to localhost:80
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.)


-- 
912255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-asdf
Version: 2.1.0-1
Severity: serious
Tags: ftbfs

python-asdf fails to build from source if some webserver is listening to
localhost:80. The Debian policy prohibits doing so in section 4.9. The
access is only legitimate if python-asdf starts the web server.

| === FAILURES 
===
| _ test_invalid_source 
__
| 
| small_tree = {'not_shared': array([10,  9,  8,  7,  6,  5,  4,  3,  2,  1], 
dtype=uint8), 'science_data': array([0., 1., 2., 3., 4., 5., 6., 7., 8., 9.]), 
'skipping': array([0., 2., 4., 6., 8.]), 'subset': array([3., 4., 5., 6.])}
| 
| def test_invalid_source(small_tree):
| buff = io.BytesIO()
| 
| ff = asdf.AsdfFile(small_tree)
| ff.write_to(buff)
| 
| buff.seek(0)
| with asdf.AsdfFile.open(buff) as ff2:
| ff2.blocks.get_block(0)
| 
| with pytest.raises(ValueError):
| ff2.blocks.get_block(2)
| 
| with pytest.raises(IOError):
| >   ff2.blocks.get_block("http://127.0.0.1/;)
| 
| asdf/tests/test_low_level.py:141: 
| _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
| asdf/block.py:643: in get_block
| source, do_not_fill_defaults=True)
| asdf/asdf.py:364: in open_external
| do_not_fill_defaults=do_not_fill_defaults)
| asdf/asdf.py:778: in open
| ignore_missing_extensions=ignore_missing_extensions)
| _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
| 
| cls = 
| self = , fd = 'http://127.0.0.1/'
| uri = None, mode = 'r', validate_checksums = False, do_not_fill_defaults = 
True
| _get_yaml_content = False, _force_raw_types = False
| strict_extension_check = False, ignore_missing_extensions = False
| 
| @classmethod
| def _open_impl(cls, self, fd, uri=None, mode='r',
|validate_checksums=False,
|do_not_fill_defaults=False,
|_get_yaml_content=False,
|_force_raw_types=False,
|strict_extension_check=False,
|ignore_missing_extensions=False):
| """Attempt to open file-like object as either AsdfFile or 
AsdfInFits"""
| if not is_asdf_file(fd):
| try:
| # TODO: this feels a bit circular, try to clean up. Also
| # this introduces another dependency on astropy which may
| # not be desireable.
| from . import fits_embed
| return fits_embed.AsdfInFits._open_impl(fd, uri=uri,
| validate_checksums=validate_checksums,
| 
ignore_version_mismatch=self._ignore_version_mismatch,
| extensions=self._extensions,
| strict_extension_check=strict_extension_check,
| 
ignore_missing_extensions=ignore_missing_extensions,
| _extension_metadata=self._extension_metadata)
| except ValueError:
| pass
| raise ValueError(
| >   "Input object does not appear to be ASDF file or FITS with " +
| "ASDF extension")
| E   ValueError: Input object does not appear to be ASDF file or FITS 
with ASDF extension
| 
| asdf/asdf.py:682: ValueError
| - Captured stdout call 
-
| Downloading http://127.0.0.1/ [Done]
| === warnings summary 
===
| 
.pybuild/cpython3_3.7_asdf/build/asdf/tests/test_suite.py::test_reference_file[reference_files/1.0.0/complex.asdf]
|   /usr/lib/python3/dist-packages/numpy/core/numeric.py:2321: RuntimeWarning: 
overflow encountered in absolute
| return less_equal(abs(x-y), atol + rtol * abs(y))
| 
| -- Docs: http://doc.pytest.org/en/latest/warnings.html
| === 1 failed, 319 passed, 12 skipped, 4 xfailed, 1 warnings in 4.60 seconds 

| E: pybuild pybuild:338: test: plugin distutils failed 

Bug#912265: marked as done (trove3 FTBFS with OpenJDK 11)

[Debian Bug Tracking System]

Your message dated Mon, 29 Oct 2018 19:34:36 +
with message-id 
and subject line Bug#912265: fixed in trove3 3.0.3-5
has caused the Debian Bug report #912265,
regarding trove3 FTBFS with OpenJDK 11
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.)


-- 
912265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trove3
Version: 3.0.3-4
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/trove3.html

...
-build_tests:
[javac] /build/1st/trove3-3.0.3/build.xml:350: warning: 'includeantruntime' 
was not set, defaulting to build.sysclasspath=last; set to false for repeatable 
builds
[javac] Using javac -source 1.5 is no longer supported, switching to 6
[javac] Using javac -target 1.5 is no longer supported, switching to 6
[javac] Compiling 28 source files to 
/build/1st/trove3-3.0.3/output/test_classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 6
[javac] warning: [options] source value 6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/trove3-3.0.3/test/gnu/trove/set/hash/TLinkedHashSetTest.java:25: 
error: package org.omg.CORBA.portable does not exist
[javac] import org.omg.CORBA.portable.Streamable;
[javac]  ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 1 error
[javac] 4 warnings

BUILD FAILED
/build/1st/trove3-3.0.3/build.xml:63: The following error occurred while 
executing this line:
/build/1st/trove3-3.0.3/build.xml:350: Compile failed; see the compiler error 
output for details.

Total time: 18 seconds
dh_auto_build: ant -Duser.name debian -Dversion.number=3.0.3 release javadoc 
returned exit code 1
make[1]: *** [debian/rules:13: override_dh_auto_build-indep] Error 2
--- End Message ---
--- Begin Message ---
Source: trove3
Source-Version: 3.0.3-5

We believe that the bug you reported is fixed in the latest version of
trove3, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 912...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated trove3 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Oct 2018 20:02:06 +0100
Source: trove3
Binary: libtrove3-java libtrove3-java-doc
Architecture: source
Version: 3.0.3-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libtrove3-java - high performance collections for java
 libtrove3-java-doc - high performance collections for java
Closes: 912265
Changes:
 trove3 (3.0.3-5) unstable; urgency=medium
 .
   [ Steffen Möller ]
   * Team upload.
   * Update watch - project moved to bitbucket
   * Using Files-Excluded in d/copyright, formatting.
 .
   [ Markus Koschany ]
   * Declare compliance with Debian Policy 4.2.1.
   * Add no-CORBA-JDK11.patch. Remove the test failing with OpenJDK 11.
 (Closes: #912265)
Checksums-Sha1:
 0ed60053172c2f946acfb046eb736804b09a0f5a 2235 trove3_3.0.3-5.dsc
 fe4ef6c253ca1e01ab3dfba00ff26ee2d582c0bb 9300 trove3_3.0.3-5.debian.tar.xz
 e83bca1badaa7815e323ce884e875ecfbbc4538f 13081 trove3_3.0.3-5_amd64.buildinfo
Checksums-Sha256:
 c011a4dab2a374a63ce0f523030f4ab77371f92ea84c3b132d4be4243c79f006 2235 
trove3_3.0.3-5.dsc
 11472c1bb7eb1152ce588e7cce48a64a6b26022402bb3a826eb0cd8d8a8ad88c 9300 
trove3_3.0.3-5.debian.tar.xz
 17c9a2bf1bd8aa180e087be8531f7ff78e5c07061a93a21fff4de286409d85d7 13081 
trove3_3.0.3-5_amd64.buildinfo
Files:
 0af3425332ab3f240c1dfa0e12bde806 2235 java optional trove3_3.0.3-5.dsc
 c8d225e6e2b4382ae50a49e40611c5c7 9300 java optional 

Bug#912278: wala FTBFS with OpenJDK 11

[Adrian Bunk]

Source: wala
Version: 1.3.9-2
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/wala.html

...
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':util:compileJava'.
> error: invalid source release: 1.11

Bug#912275: uncommons-watchmaker FTBFS with OpenJDK 11

[Adrian Bunk]

Source: uncommons-watchmaker
Version: 0.7.1-1
Severity: serious
Tags: ftbfs buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/uncommons-watchmaker.html

...
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':framework:compileJava'.
> error: invalid source release: 1.11

Processed: tagging 890075

[Debian Bug Tracking System]

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

> tags 890075 + ftbfs
Bug #890075 [src:ruby-http] ruby-http ftbfs (test failures with 2.5)
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#912274: ruby-clockwork FTBFS: Mocha::NotInitializedError: Mocha methods cannot be used outside the context of a test

[Helmut Grohne]

Source: ruby-clockwork
Version: 1.2.0-3
Severity: serious
Tags: ftbfs

ruby-clockwork fails to build from source in unstable.

|   1) Error:
| Clockwork::Event::#thread?::manager config thread option set to 
true#test_0001_is true:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/event_test.rb:12:in `block (4 levels) in '
| 
|   2) Error:
| Clockwork::Event::#thread?::manager config thread option set to 
true#test_0002_is false when event thread option set:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/event_test.rb:12:in `block (4 levels) in '
| 
|   3) Error:
| Clockwork::Manager#test_0013_exceptions still set the last timestamp to avoid 
spastic error loops:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/manager_test.rb:131:in `block (2 levels) in '
| 
|   4) Error:
| Clockwork#test_0006_support module re-open style:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/clockwork_test.rb:80:in `block (2 levels) in '
| 
|   5) Error:
| Clockwork#test_0001_should run events with configured logger:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/clockwork_test.rb:24:in `block (2 levels) in '
| 
|   6) Error:
| Clockwork#test_0002_should log event correctly:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/clockwork_test.rb:37:in `block (2 levels) in '
| 
|   7) Error:
| Clockwork#test_0004_should not run anything after reset:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/clockwork_test.rb:62:in `block (2 levels) in '
| 
|   8) Error:
| Clockwork#test_0003_should pass event without modification to handler:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/clockwork_test.rb:50:in `block (2 levels) in '
| 
|   9) Error:
| Clockwork#test_0005_should pass all arguments to every:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/clockwork_test.rb:69:in `block (2 levels) in '
| 
|  10) Error:
| Clockwork::Event::#thread?::manager config thread option not set#test_0001_is 
true if event thread option is true:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/event_test.rb:28:in `block (4 levels) in '
| 
|  11) Error:
| Clockwork::Manager::max_threads#test_0001_should warn when an event tries to 
generate threads more than max_threads:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/manager_test.rb:276:in `block (3 levels) in '
| 
|  12) Error:
| Clockwork::Manager::max_threads#test_0002_should not warn when thread is 
managed by others:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/manager_test.rb:291:in `block (3 levels) in '
| 
| 85 runs, 139 assertions, 0 failures, 12 errors, 0 skips
| rake aborted!
| Command failed with status (1): [ruby -w -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/at_test.rb" 
"test/clockwork_test.rb" "test/database_events/sync_performer_test.rb" 
"test/event_test.rb" "test/manager_test.rb" 
"test/database_events/test_helpers.rb" -v]
| 
| Tasks: TOP => default
| (See full trace by running task with --trace)
| ERROR: Test "ruby2.5" failed. Exiting.
| dh_auto_install: dh_ruby --install /<>/debian/ruby-clockwork 
returned exit code 1
| make: *** [debian/rules:6: binary] Error 1
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

Helmut

Bug#912235: Bug#912235: figtree FTBFS with OpenJDK 11

[Andreas Tille]

Hi Fabian,

On Mon, Oct 29, 2018 at 04:41:56PM +0100, Fabian Klötzl wrote:
> Thank you for reporting. I added a fix to the repo. Will get resolved with
> the next upload.

I've seen your patch to enforce Java 8.  I'm not sure whether this is a
sustainable solution.  Did you pointed upstream to the issue and asked
for upgrading to Java 11?

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#912273: unsafe-mock FTBFS with OpenJDK 11

[Adrian Bunk]

Source: unsafe-mock
Version: 8.0-2
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/unsafe-mock.html

...
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 1.499 s
[INFO] Finished at: 2018-10-29T06:59:56-12:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) 
on project unsafe-mock: Compilation failure
[ERROR] /build/1st/unsafe-mock-8.0/src/main/java/sun/misc/Unsafe.java:[83,34] 
cannot find symbol
[ERROR]   symbol:   class Reflection
[ERROR]   location: package sun.reflect
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/unsafe-mock-8.0 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/unsafe-mock-8.0/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/unsafe-mock-8.0/debian 
-Dmaven.repo.local=/build/1st/unsafe-mock-8.0/debian/maven-repo --batch-mode 
package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build] Error 2

Bug#912272: staden-io-lib FTBFS: dh_installdocs: Cannot find (any matches for) "README" (tried in .)

[Helmut Grohne]

Source: staden-io-lib
Version: 1.14.9-4
Severity: serious
Tags: ftbfs

staden-io-lib fails to build from source in unstable. This smells a bit
like a debhelper regression, but I'm not sure actually. In any case, it
fails to build reliably.

|dh_installdocs -O--no-parallel
| dh_installdocs: Cannot find (any matches for) "README" (tried in .)
| 
| make: *** [debian/rules:11: binary] Error 2
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

Helmut

Bug#910485: Confirm issue with libpsm2-2/11.2.68-1

[Mehdi Dogguy]

Sure, but it is still an improvement over the current situation and is simple 
enough to minimize its impact. Of course, it should be considered as a 
wrkaround, until upstream releases a fixed version.


Le 29 octobre 2018 19:41:06 GMT+01:00, Brian Smith 
 a écrit :
>Hi Mehdi,
>
>
>On Mon, Oct 29, 2018 at 4:48 AM Mehdi Dogguy  wrote:
>>
>> Sorry for not replying sooner.
>>
>> On 2018-10-20 17:54, Brian Smith wrote:
>> > The change is in psm2_hal.c. It is a brand new file. Reference the
>> > initialization loop at line 246.
>> >
>>
>> Indeed. The solution described in the github issue looks very fine.
>> Why not uploading it in Debian? It will solve a real issue for users
>> (and reverse dependencies) while giving upstream more time to
>> investigate it.
>>
>> --
>> Mehdi
>
>Thank you for looking it over. I'm still working with upstream to get
>an approved patch. The proposed patch corrects the symptom that
>resulted in this issue, but I can't guarantee it won't cause some
>other aberrant behavior.

-- 
Mehdi

Bug#910485: Confirm issue with libpsm2-2/11.2.68-1

[Brian Smith]

Hi Mehdi,


On Mon, Oct 29, 2018 at 4:48 AM Mehdi Dogguy  wrote:
>
> Sorry for not replying sooner.
>
> On 2018-10-20 17:54, Brian Smith wrote:
> > The change is in psm2_hal.c. It is a brand new file. Reference the
> > initialization loop at line 246.
> >
>
> Indeed. The solution described in the github issue looks very fine.
> Why not uploading it in Debian? It will solve a real issue for users
> (and reverse dependencies) while giving upstream more time to
> investigate it.
>
> --
> Mehdi

Thank you for looking it over. I'm still working with upstream to get
an approved patch. The proposed patch corrects the symptom that
resulted in this issue, but I can't guarantee it won't cause some
other aberrant behavior.

-- 
Brian T. Smith
System Fabric Works
Senior Technical Staff
bsm...@systemfabricworks.com
GPG Key: 0xB3C2C7B73BA3CD7F

Bug#912270: writer2latex FTBFS with OpenJDK 11

[Adrian Bunk]

Source: writer2latex
Version: 1.4-5
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/writer2latex.html

...
compile:
[mkdir] Created dir: /build/1st/writer2latex-1.4/target/classes
[javac] Compiling 203 source files to 
/build/1st/writer2latex-1.4/target/classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 6
[javac] warning: [options] source value 6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/writer2latex-1.4/source/java/writer2latex/base/ImageConverter.java:37:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.DatatypeConverter;
[javac]  ^
[javac] 
/build/1st/writer2latex-1.4/source/java/writer2latex/base/ImageConverter.java:351:
 error: cannot find symbol
[javac] return DatatypeConverter.printHexBinary(md.digest(blob))
[javac]^
[javac]   symbol:   variable DatatypeConverter
[javac]   location: class ImageConverter
[javac] 
/build/1st/writer2latex-1.4/source/java/writer2latex/base/ImageConverter.java:352:
 error: cannot find symbol
[javac] 
+DatatypeConverter.printHexBinary(Arrays.copyOf(blob, 10));
[javac]  ^
[javac]   symbol:   variable DatatypeConverter
[javac]   location: class ImageConverter
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] 3 errors
[javac] 4 warnings

BUILD FAILED
/build/1st/writer2latex-1.4/build.xml:78: Compile failed; see the compiler 
error output for details.

Total time: 5 seconds
make: *** [debian/rules:37: build-indep-stamp] Error 1

Bug#897496: marked as done (python-pathlib: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Mon, 29 Oct 2018 18:37:51 +
with message-id 
and subject line Bug#897496: fixed in python-pathlib 1.0.1-2.1
has caused the Debian Bug report #897496,
regarding python-pathlib: FTBFS: dh_auto_test: pybuild --test -i 
python{version} -p 2.7 returned exit code 13
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.)


-- 
897496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pathlib
Version: 1.0.1-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYBUILD_TEST_ARGS="-s /<>" dh_auto_test
> I: pybuild base:217: cd /<>/.pybuild/cpython2_2.7_pathlib/build; 
> python2.7 -m unittest discover -v -s /<>
> test_parse_parts (test_pathlib.NTFlavourTest) ... ok
> test_parse_parts_common (test_pathlib.NTFlavourTest) ... ok
> test_splitroot (test_pathlib.NTFlavourTest) ... ok
> test_chmod (test_pathlib.PathTest) ... ok
> test_complex_symlinks_absolute (test_pathlib.PathTest) ... ok
> test_complex_symlinks_relative (test_pathlib.PathTest) ... ok
> test_complex_symlinks_relative_dot_dot (test_pathlib.PathTest) ... ok
> test_concrete_class (test_pathlib.PathTest) ... ok
> test_cwd (test_pathlib.PathTest) ... ok
> test_empty_path (test_pathlib.PathTest) ... ok
> test_exists (test_pathlib.PathTest) ... ok
> test_glob_common (test_pathlib.PathTest) ... ok
> test_glob_dotdot (test_pathlib.PathTest) ... ok
> test_group (test_pathlib.PathTest) ... ok
> test_is_block_device_false (test_pathlib.PathTest) ... ok
> test_is_char_device_false (test_pathlib.PathTest) ... ok
> test_is_char_device_true (test_pathlib.PathTest) ... ok
> test_is_dir (test_pathlib.PathTest) ... ok
> test_is_fifo_false (test_pathlib.PathTest) ... ok
> test_is_fifo_true (test_pathlib.PathTest) ... ok
> test_is_file (test_pathlib.PathTest) ... ok
> test_is_socket_false (test_pathlib.PathTest) ... ok
> test_is_socket_true (test_pathlib.PathTest) ... ERROR
> test_is_symlink (test_pathlib.PathTest) ... ok
> test_iterdir (test_pathlib.PathTest) ... ok
> test_iterdir_nodir (test_pathlib.PathTest) ... ok
> test_iterdir_symlink (test_pathlib.PathTest) ... ok
> test_lstat (test_pathlib.PathTest) ... ok
> test_lstat_nosymlink (test_pathlib.PathTest) ... ok
> test_mkdir (test_pathlib.PathTest) ... ok
> test_mkdir_parents (test_pathlib.PathTest) ... ok
> test_open_common (test_pathlib.PathTest) ... ok
> test_owner (test_pathlib.PathTest) ... ok
> test_parts_interning (test_pathlib.PathTest) ... ok
> test_pickling_common (test_pathlib.PathTest) ... ok
> test_rename (test_pathlib.PathTest) ... ok
> test_replace (test_pathlib.PathTest) ... ok
> test_resolve_common (test_pathlib.PathTest) ... ok
> test_resolve_dot (test_pathlib.PathTest) ... ok
> test_rglob_common (test_pathlib.PathTest) ... ok
> test_rmdir (test_pathlib.PathTest) ... ok
> test_stat (test_pathlib.PathTest) ... ok
> test_symlink_to (test_pathlib.PathTest) ... ok
> test_touch_common (test_pathlib.PathTest) ... ok
> test_touch_nochange (test_pathlib.PathTest) ... ok
> test_unlink (test_pathlib.PathTest) ... ok
> test_unsupported_flavour (test_pathlib.PathTest) ... ok
> test_parse_parts (test_pathlib.PosixFlavourTest) ... ok
> test_parse_parts_common (test_pathlib.PosixFlavourTest) ... ok
> test_splitroot (test_pathlib.PosixFlavourTest) ... ok
> test_anchor_common (test_pathlib.PosixPathAsPureTest) ... ok
> test_as_bytes_common (test_pathlib.PosixPathAsPureTest) ... skipped 
> 'os.fsencode has been introduced in version 3.2'
> test_as_posix_common (test_pathlib.PosixPathAsPureTest) ... ok
> test_as_uri (test_pathlib.PosixPathAsPureTest) ... ok
> test_as_uri_common (test_pathlib.PosixPathAsPureTest) ... ok
> test_as_uri_non_ascii (test_pathlib.PosixPathAsPureTest) ... skipped 
> 'os.fsencode has been introduced in version 3.2'
> test_constructor_common (test_pathlib.PosixPathAsPureTest) ... ok
> test_div (test_pathlib.PosixPathAsPureTest) ... ok
> test_div_common (test_pathlib.PosixPathAsPureTest) ... ok
> test_drive_common (test_pathlib.PosixPathAsPureTest) ... ok
> test_eq (test_pathlib.PosixPathAsPureTest) ... ok
> test_eq_common (test_pathlib.PosixPathAsPureTest) ... ok
> test_equivalences (test_pathlib.PosixPathAsPureTest) ... ok
> test_is_absolute (test_pathlib.PosixPathAsPureTest) ... ok
> test_is_reserved (test_pathlib.PosixPathAsPureTest) ... ok
> test_join 

Bug#899804: marked as done (fcitx-hangul: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Mon, 29 Oct 2018 18:34:17 +
with message-id 
and subject line Bug#899804: fixed in fcitx-hangul 0.3.1-2
has caused the Debian Bug report #899804,
regarding fcitx-hangul: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
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.)


-- 
899804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fcitx-hangul
Version: 0.3.1-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of fcitx-hangul,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package fcitx-hangul since the list address
pkg-ime-de...@lists.alioth.debian.org used in the Maintainer: field was
not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-ime-de...@lists.alioth.debian.org is 68.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: fcitx-hangul
Source-Version: 0.3.1-2

We believe that the bug you reported is fixed in the latest version of
fcitx-hangul, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated fcitx-hangul package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 25 Oct 2018 15:11:36 -0400
Source: fcitx-hangul
Binary: fcitx-hangul
Architecture: source amd64
Version: 0.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Description:
 fcitx-hangul - Free Chinese Input Toy of X - hangul module
Closes: 899804
Changes:
 fcitx-hangul (0.3.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Rebuild against gcc 8.2.
   * Modernize packaging.
 + Bump Standards-Version to 4.2.1.
 + Bump debhelper compat to 11.
 + Update uploaders' email address and use the @debian.org one.
 + Update Vcs-* fields and use the git repo under Salsa input-method-team
   group.
 + Update maintainer information and use Debian Input Method Team.
   (Closes: #899804).
 + Use "dh_missing --fail-missing". in debian/rules.
Checksums-Sha1:
 27be1067d9143250637a2dd00a39ced1272a5239 2090 fcitx-hangul_0.3.1-2.dsc
 f2ae6b8636991a4e1bca16528a327fae8cdc81c3 26612 fcitx-hangul_0.3.1.orig.tar.xz
 b13d169784c76d9630d173f1dc2f9038abf50b5d 2720 
fcitx-hangul_0.3.1-2.debian.tar.xz
 e930fa0faf72f7f78130b1d54c6af1785d7f5614 67940 
fcitx-hangul-dbgsym_0.3.1-2_amd64.deb
 960c8ad48a0577be4f2b123e216e6b108a0e4867 8875 

Bug#912268: uimaj FTBFS with OpenJDK 11

[Adrian Bunk]

Source: uimaj
Version: 2.10.1-2
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/uimaj.html

...
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 18.376 s
[INFO] Finished at: 2018-10-29T06:16:31-12:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) 
on project uimaj-adapter-soap: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/uimaj-2.10.1/uimaj-adapter-soap/src/main/java/org/apache/uima/adapter/soap/axis11/BinarySerializer_Axis11.java:[25,24]
 package javax.activation does not exist
[ERROR] 
/build/1st/uimaj-2.10.1/uimaj-adapter-soap/src/main/java/org/apache/uima/adapter/soap/BinarySerializer.java:[25,24]
 package javax.activation does not exist
[ERROR] 
/build/1st/uimaj-2.10.1/uimaj-adapter-soap/src/main/java/org/apache/uima/adapter/soap/BinaryDeserializer.java:[26,24]
 package javax.activation does not exist
[ERROR] 
/build/1st/uimaj-2.10.1/uimaj-adapter-soap/src/main/java/org/apache/uima/adapter/soap/axis11/BinaryDeserializer_Axis11.java:[26,24]
 package javax.activation does not exist
[ERROR] 
/build/1st/uimaj-2.10.1/uimaj-adapter-soap/src/main/java/org/apache/uima/adapter/soap/axis11/BinarySerializer_Axis11.java:[100,9]
 cannot find symbol
[ERROR]   symbol:   class DataHandler
[ERROR]   location: class 
org.apache.uima.adapter.soap.axis11.BinarySerializer_Axis11
[ERROR] 
/build/1st/uimaj-2.10.1/uimaj-adapter-soap/src/main/java/org/apache/uima/adapter/soap/axis11/BinarySerializer_Axis11.java:[100,39]
 cannot find symbol
[ERROR]   symbol:   class DataHandler
[ERROR]   location: class 
org.apache.uima.adapter.soap.axis11.BinarySerializer_Axis11
[ERROR] 
/build/1st/uimaj-2.10.1/uimaj-adapter-soap/src/main/java/org/apache/uima/adapter/soap/BinarySerializer.java:[99,9]
 cannot find symbol
[ERROR]   symbol:   class DataHandler
[ERROR]   location: class org.apache.uima.adapter.soap.BinarySerializer
[ERROR] 
/build/1st/uimaj-2.10.1/uimaj-adapter-soap/src/main/java/org/apache/uima/adapter/soap/BinarySerializer.java:[99,39]
 cannot find symbol
[ERROR]   symbol:   class DataHandler
[ERROR]   location: class org.apache.uima.adapter.soap.BinarySerializer
[ERROR] 
/build/1st/uimaj-2.10.1/uimaj-adapter-soap/src/main/java/org/apache/uima/adapter/soap/BinaryDeserializer.java:[91,11]
 cannot find symbol
[ERROR]   symbol:   class DataHandler
[ERROR]   location: class org.apache.uima.adapter.soap.BinaryDeserializer
[ERROR] 
/build/1st/uimaj-2.10.1/uimaj-adapter-soap/src/main/java/org/apache/uima/adapter/soap/axis11/BinaryDeserializer_Axis11.java:[91,11]
 cannot find symbol
[ERROR]   symbol:   class DataHandler
[ERROR]   location: class 
org.apache.uima.adapter.soap.axis11.BinaryDeserializer_Axis11
[ERROR] 
/build/1st/uimaj-2.10.1/uimaj-adapter-soap/src/main/java/org/apache/uima/adapter/soap/AxisAnalysisEngineServiceStub.java:[129,11]
 cannot find symbol
[ERROR]   symbol:   class DataHandler
[ERROR]   location: class 
org.apache.uima.adapter.soap.AxisAnalysisEngineServiceStub
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :uimaj-adapter-soap
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/uimaj-2.10.1 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/uimaj-2.10.1/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/uimaj-2.10.1/debian 
-Dmaven.repo.local=/build/1st/uimaj-2.10.1/debian/maven-repo --batch-mode 
install -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
make[1]: *** [debian/rules:7: override_dh_auto_build] Error 2

Bug#912266: tomcat7 FTBFS with OpenJDK 11

[Adrian Bunk]

Source: tomcat7
Version: 7.0.78-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/tomcat7.html

...
compile-java6:
[javac] Compiling 1307 source files to 
/build/1st/tomcat7-7.0.78/output/classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 6
[javac] warning: [options] source value 6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/tomcat7-7.0.78/java/org/apache/catalina/util/Base64.java:20: error: 
package javax.xml.bind does not exist
[javac] import javax.xml.bind.DatatypeConverter;
[javac]  ^
[javac] 
/build/1st/tomcat7-7.0.78/java/javax/el/ResourceBundleELResolver.java:109: 
warning: [unchecked] getFeatureDescriptors(ELContext,Object) in 
ResourceBundleELResolver overrides getFeatureDescriptors(ELContext,Object) in 
ELResolver
[javac] public Iterator getFeatureDescriptors(
[javac] ^
[javac]   return type requires unchecked conversion from Iterator to 
Iterator
[javac] 
/build/1st/tomcat7-7.0.78/java/org/apache/catalina/util/Base64.java:93: error: 
cannot find symbol
[javac] return DatatypeConverter.printBase64Binary(binaryData);
[javac]^
[javac]   symbol:   variable DatatypeConverter
[javac]   location: class Base64
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] 2 errors
[javac] 5 warnings

BUILD FAILED
/build/1st/tomcat7-7.0.78/build.xml:652: Compile failed; see the compiler error 
output for details.

Total time: 13 seconds
make[1]: *** [debian/rules:21: override_dh_auto_build] Error 1

Bug#912267: uddi4j FTBFS with OpenJDK 11

[Adrian Bunk]

Source: uddi4j
Version: 2.0.5-4
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/uddi4j.html

...
compile:
[mkdir] Created dir: /build/1st/uddi4j-2.0.5/build/classes
[javac] /build/1st/uddi4j-2.0.5/build.xml:158: warning: 'includeantruntime' 
was not set, defaulting to build.sysclasspath=last; set to false for repeatable 
builds
[javac] Compiling 106 source files to /build/1st/uddi4j-2.0.5/build/classes
[javac] error: module not found: java.xml.ws
[javac] 1 error

BUILD FAILED
/build/1st/uddi4j-2.0.5/build.xml:158: Compile failed; see the compiler error 
output for details.

Total time: 2 seconds
dh_auto_build: ant -propertyfile ./debian/ant.properties -Duser.name debian 
dist returned exit code 1
make[1]: *** [debian/rules:9: override_dh_auto_build] Error 2

Bug#912265: trove3 FTBFS with OpenJDK 11

[Adrian Bunk]

Source: trove3
Version: 3.0.3-4
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/trove3.html

...
-build_tests:
[javac] /build/1st/trove3-3.0.3/build.xml:350: warning: 'includeantruntime' 
was not set, defaulting to build.sysclasspath=last; set to false for repeatable 
builds
[javac] Using javac -source 1.5 is no longer supported, switching to 6
[javac] Using javac -target 1.5 is no longer supported, switching to 6
[javac] Compiling 28 source files to 
/build/1st/trove3-3.0.3/output/test_classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 6
[javac] warning: [options] source value 6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/trove3-3.0.3/test/gnu/trove/set/hash/TLinkedHashSetTest.java:25: 
error: package org.omg.CORBA.portable does not exist
[javac] import org.omg.CORBA.portable.Streamable;
[javac]  ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 1 error
[javac] 4 warnings

BUILD FAILED
/build/1st/trove3-3.0.3/build.xml:63: The following error occurred while 
executing this line:
/build/1st/trove3-3.0.3/build.xml:350: Compile failed; see the compiler error 
output for details.

Total time: 18 seconds
dh_auto_build: ant -Duser.name debian -Dversion.number=3.0.3 release javadoc 
returned exit code 1
make[1]: *** [debian/rules:13: override_dh_auto_build-indep] Error 2

Processed: tagging 912249

[Debian Bug Tracking System]

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

> tags 912249 + buster sid
Bug #912249 [src:ruby-file-tail] ruby-file-tail FTBFS: 
test_tail_change2(FileTailTest) fails
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: tagging 912253

[Debian Bug Tracking System]

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

> tags 912253 + buster sid
Bug #912253 [src:ruby-protected-attributes] ruby-protected-attributes: FTBFS 
reliably (failing tests)
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#912263: android-sdk-helper FTBFS with OpenJDK 11

[Adrian Bunk]

Source: android-sdk-helper
Version: 0.1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/android-sdk-helper.html

...
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':gradle-debian-android-plugin:compileJava'.
> error: invalid source release: 1.11

Bug#912262: android-platform-frameworks-data-binding FTBFS with OpenJDK 11

[Adrian Bunk]

Source: android-platform-frameworks-data-binding
Version: 2.2.2-3
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/android-platform-frameworks-data-binding.html

...
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':dataBinding:compilerCommon:compileJava'.
> error: invalid source release: 1.11

Bug#912261: clojure FTBFS with OpenJDK 11

[Adrian Bunk]

Source: clojure
Version: 1.9.0-5
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/clojure.html

...
compile-clojure:
 [java] Exception in thread "main" java.lang.ExceptionInInitializerError
 [java] at clojure.lang.Compile.(Compile.java:29)
 [java] Caused by: java.lang.IllegalArgumentException: Must hint overloaded 
method: toArray, compiling:(clojure/gvec.clj:131:1)
 [java] at clojure.lang.Compiler.analyzeSeq(Compiler.java:7010)
 [java] at clojure.lang.Compiler.analyze(Compiler.java:6773)
 [java] at clojure.lang.Compiler.analyze(Compiler.java:6729)
 [java] at 
clojure.lang.Compiler$BodyExpr$Parser.parse(Compiler.java:6102)
 [java] at 
clojure.lang.Compiler$LetExpr$Parser.parse(Compiler.java:6420)
 [java] at clojure.lang.Compiler.analyzeSeq(Compiler.java:7003)
 [java] at clojure.lang.Compiler.analyze(Compiler.java:6773)
 [java] at clojure.lang.Compiler.analyze(Compiler.java:6729)
 [java] at 
clojure.lang.Compiler$BodyExpr$Parser.parse(Compiler.java:6104)
 [java] at clojure.lang.Compiler$FnMethod.parse(Compiler.java:5460)
 [java] at clojure.lang.Compiler$FnExpr.parse(Compiler.java:4022)
 [java] at clojure.lang.Compiler.analyzeSeq(Compiler.java:7001)
 [java] at clojure.lang.Compiler.analyze(Compiler.java:6773)
 [java] at clojure.lang.Compiler.eval(Compiler.java:7059)
 [java] at clojure.lang.Compiler.load(Compiler.java:7514)
 [java] at clojure.lang.RT.loadResourceScript(RT.java:379)
 [java] at clojure.lang.RT.loadResourceScript(RT.java:370)
 [java] at clojure.lang.RT.load(RT.java:460)
 [java] at clojure.lang.RT.load(RT.java:426)
 [java] at clojure.core$load$fn__1725.invoke(core.clj:6046)
 [java] at clojure.core$load.invokeStatic(core.clj:6045)
 [java] at clojure.core$load.doInvoke(core.clj:6029)
 [java] at clojure.lang.RestFn.invoke(RestFn.java:408)
 [java] at clojure.core$eval3444.invokeStatic(core.clj:6689)
 [java] at clojure.core$eval3444.invoke(core.clj:6689)
 [java] at clojure.lang.Compiler.eval(Compiler.java:7062)
 [java] at clojure.lang.Compiler.load(Compiler.java:7514)
 [java] at clojure.lang.RT.loadResourceScript(RT.java:379)
 [java] at clojure.lang.RT.loadResourceScript(RT.java:370)
 [java] at clojure.lang.RT.load(RT.java:460)
 [java] at clojure.lang.RT.load(RT.java:426)
 [java] at clojure.lang.RT.doInit(RT.java:468)
 [java] at clojure.lang.RT.(RT.java:336)
 [java] ... 1 more
 [java] Caused by: java.lang.IllegalArgumentException: Must hint overloaded 
method: toArray
 [java] at 
clojure.lang.Compiler$NewInstanceMethod.parse(Compiler.java:8375)
 [java] at 
clojure.lang.Compiler$NewInstanceExpr.build(Compiler.java:7937)
 [java] at 
clojure.lang.Compiler$NewInstanceExpr$DeftypeParser.parse(Compiler.java:7813)
 [java] at clojure.lang.Compiler.analyzeSeq(Compiler.java:7003)
 [java] ... 33 more

BUILD FAILED
/build/1st/clojure-1.9.0/build.xml:52: Java returned: 1

Total time: 12 seconds
dh_auto_build: ant -Duser.name debian jar returned exit code 1
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 2

Bug#912260: android-platform-tools-analytics-library FTBFS with OpenJDK 11

[Adrian Bunk]

Source: android-platform-tools-analytics-library
Version: 2.2.2-2
Severity: serious
Tags: ftbfs buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/android-platform-tools-analytics-library.html

...
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':analytics-library:protos:compileJava'.
> error: invalid source release: 1.11

Bug#911403: Please always include a copyright notice in 'LicenseWithSummary::summary_or_text'

[Felix Lechner]

Hi Dominique,

I am fine with your suggestion. We will wait for your implementation.
Thank you for providing this package!

Kind regards,
Felix

On Mon, Oct 29, 2018 at 9:44 AM Dominique Dumont  wrote:
>
> On Monday, 29 October 2018 16:51:45 CET you wrote:
> > I am happy to provide patches and merge requests that implement your
> > idea,
>
> Thanks. But the change is trivial. I can do it on my side.
>
> We just need to find a common ground that allow fixing #905614
>
> > but are you sure there are other meaningful consumers of the
> > summary_or_text method?
>
> Absolutely not. But keeping backward compat with already published modules is
> one of the best values of the Perl community. I intend to keep that promise as
> much as possible
>
> > Your posting [1] restricts uses to Debian
>
> Debian and its 100+ derivates.
>
> > , and
> > a search on codesearch.debian.net shows no other packages that rely on
> > the current implementation that produces a copyright notice with a
> > full text but not with a summary. Why is the current implementation
> > worth keeping?
>
> Because we can't be sure that nobody will be impacted. A user may be relying
> on summary_or_text but has not (or will not) publish her or his code.
>
> > Please forgive me if I appear insistent. It's the only
> > question I have.
>
> No problem. You're right to challenge what is not clear :-)
>
> All the best
>
>
>
>

Bug#905614: Patch invalid

[Felix Lechner]

Control: tags 905614 - patch

The owner of libsoftware-licensemoreutils would like to resolve the
issue differently. (For details, please see #911403.) The patch I
submitted earlier is outdated. Thank you!

Kind regards,
Felix

Processed: Patch invalid

[Debian Bug Tracking System]

Processing control commands:

> tags 905614 - patch
Bug #905614 [src:license-reconcile] FTBFS: Failed test 'no warnings' with 
libsoftware-license-perl 0.103013-2
Ignoring request to alter tags of bug #905614 to the same tags previously set

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

Bug#910888: marked as done (imagemagick: CVE-2018-16644)

[Debian Bug Tracking System]

Your message dated Mon, 29 Oct 2018 16:50:36 +
with message-id 
and subject line Bug#910888: fixed in imagemagick 8:6.9.10.14+dfsg-1
has caused the Debian Bug report #910888,
regarding imagemagick: CVE-2018-16644
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.)


-- 
910888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910888
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imagemagick
Version: 8:6.9.7.4+dfsg-1
Severity: grave
Tags: patch security upstream
Forwarded: https://github.com/ImageMagick/ImageMagick/issues/1269
Control: fixed -1 8:6.9.7.4+dfsg-11+deb9u6

[adding already the fixed version for the already pending
stretch-security DSA version]

Hi,

The following vulnerability was published for imagemagick.

CVE-2018-16644[0]:
| There is a missing check for length in the functions ReadDCMImage of
| coders/dcm.c and ReadPICTImage of coders/pict.c in ImageMagick
| 7.0.8-11, which allows remote attackers to cause a denial of service
| via a crafted image.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16644
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16644
[1] https://github.com/ImageMagick/ImageMagick/issues/1269

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.9.10.14+dfsg-1

We believe that the bug you reported is fixed in the latest version of
imagemagick, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 910...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated imagemagick package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Oct 2018 13:13:38 +0100
Source: imagemagick
Binary: imagemagick-6-common imagemagick-6-doc libmagickcore-6-headers 
libmagickwand-6-headers libmagick++-6-headers libimage-magick-perl 
libmagickcore-6-arch-config imagemagick-6.q16 libmagickcore-6.q16-6 
libmagickcore-6.q16-6-extra libmagickcore-6.q16-dev libmagickwand-6.q16-6 
libmagickwand-6.q16-dev libmagick++-6.q16-8 libmagick++-6.q16-dev 
libimage-magick-q16-perl imagemagick-6.q16hdri libmagickcore-6.q16hdri-6 
libmagickcore-6.q16hdri-6-extra libmagickcore-6.q16hdri-dev 
libmagickwand-6.q16hdri-6 libmagickwand-6.q16hdri-dev libmagick++-6.q16hdri-8 
libmagick++-6.q16hdri-dev libimage-magick-q16hdri-perl imagemagick-common 
imagemagick-doc perlmagick libmagickcore-dev libmagickwand-dev libmagick++-dev 
imagemagick
Architecture: source
Version: 8:6.9.10.14+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: ImageMagick Packaging Team 

Changed-By: Bastien Roucariès 
Description:
 imagemagick - image manipulation programs -- binaries
 imagemagick-6-common - image manipulation programs -- infrastructure
 imagemagick-6-doc - document files of ImageMagick
 imagemagick-6.q16 - image manipulation programs -- quantum depth Q16
 imagemagick-6.q16hdri - image manipulation programs -- quantum depth Q16HDRI
 imagemagick-common - image manipulation programs -- infrastructure dummy 
package
 imagemagick-doc - document files of ImageMagick -- dummy package
 libimage-magick-perl - Perl interface to the ImageMagick graphics routines
 libimage-magick-q16-perl - Perl interface to the ImageMagick graphics routines 
-- Q16 versio
 libimage-magick-q16hdri-perl - Perl interface to the ImageMagick graphics 
routines -- Q16HDRI ve
 libmagick++-6-headers - object-oriented C++ interface to ImageMagick - header 
files
 libmagick++-6.q16-8 - C++ interface to ImageMagick -- quantum depth Q16
 libmagick++-6.q16-dev - C++ interface to ImageMagick - development files (Q16)
 libmagick++-6.q16hdri-8 - C++ interface to ImageMagick -- quantum depth Q16HDRI
 libmagick++-6.q16hdri-dev - C++ interface to ImageMagick - development files 
(Q16HDRI)
 libmagick++-dev - object-oriented C++ interface to ImageMagick -- dummy package
 libmagickcore-6-arch-config - low-level image manipulation library - 
architecture header files
 libmagickcore-6-headers - low-level 

Bug#910889: marked as done (imagemagick: CVE-2018-16645)

[Debian Bug Tracking System]

Your message dated Mon, 29 Oct 2018 16:50:36 +
with message-id 
and subject line Bug#910889: fixed in imagemagick 8:6.9.10.14+dfsg-1
has caused the Debian Bug report #910889,
regarding imagemagick: CVE-2018-16645
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.)


-- 
910889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imagemagick
Version: 8:6.9.7.4+dfsg-1
Severity: grave
Tags: patch security upstream
Forwarded: https://github.com/ImageMagick/ImageMagick/issues/1268
Control: fixed -1 8:6.9.7.4+dfsg-11+deb9u6

[adding already the fixed version for the pending stretch-security DSA
version]

Hi,

The following vulnerability was published for imagemagick.

CVE-2018-16645[0]:
| There is an excessive memory allocation issue in the functions
| ReadBMPImage of coders/bmp.c and ReadDIBImage of coders/dib.c in
| ImageMagick 7.0.8-11, which allows remote attackers to cause a denial
| of service via a crafted image file.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16645
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16645
[1] https://github.com/ImageMagick/ImageMagick/issues/1268

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.9.10.14+dfsg-1

We believe that the bug you reported is fixed in the latest version of
imagemagick, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 910...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated imagemagick package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Oct 2018 13:13:38 +0100
Source: imagemagick
Binary: imagemagick-6-common imagemagick-6-doc libmagickcore-6-headers 
libmagickwand-6-headers libmagick++-6-headers libimage-magick-perl 
libmagickcore-6-arch-config imagemagick-6.q16 libmagickcore-6.q16-6 
libmagickcore-6.q16-6-extra libmagickcore-6.q16-dev libmagickwand-6.q16-6 
libmagickwand-6.q16-dev libmagick++-6.q16-8 libmagick++-6.q16-dev 
libimage-magick-q16-perl imagemagick-6.q16hdri libmagickcore-6.q16hdri-6 
libmagickcore-6.q16hdri-6-extra libmagickcore-6.q16hdri-dev 
libmagickwand-6.q16hdri-6 libmagickwand-6.q16hdri-dev libmagick++-6.q16hdri-8 
libmagick++-6.q16hdri-dev libimage-magick-q16hdri-perl imagemagick-common 
imagemagick-doc perlmagick libmagickcore-dev libmagickwand-dev libmagick++-dev 
imagemagick
Architecture: source
Version: 8:6.9.10.14+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: ImageMagick Packaging Team 

Changed-By: Bastien Roucariès 
Description:
 imagemagick - image manipulation programs -- binaries
 imagemagick-6-common - image manipulation programs -- infrastructure
 imagemagick-6-doc - document files of ImageMagick
 imagemagick-6.q16 - image manipulation programs -- quantum depth Q16
 imagemagick-6.q16hdri - image manipulation programs -- quantum depth Q16HDRI
 imagemagick-common - image manipulation programs -- infrastructure dummy 
package
 imagemagick-doc - document files of ImageMagick -- dummy package
 libimage-magick-perl - Perl interface to the ImageMagick graphics routines
 libimage-magick-q16-perl - Perl interface to the ImageMagick graphics routines 
-- Q16 versio
 libimage-magick-q16hdri-perl - Perl interface to the ImageMagick graphics 
routines -- Q16HDRI ve
 libmagick++-6-headers - object-oriented C++ interface to ImageMagick - header 
files
 libmagick++-6.q16-8 - C++ interface to ImageMagick -- quantum depth Q16
 libmagick++-6.q16-dev - C++ interface to ImageMagick - development files (Q16)
 libmagick++-6.q16hdri-8 - C++ interface to ImageMagick -- quantum depth Q16HDRI
 libmagick++-6.q16hdri-dev - C++ interface to ImageMagick - development files 
(Q16HDRI)
 libmagick++-dev - object-oriented C++ interface to ImageMagick -- dummy package
 libmagickcore-6-arch-config - low-level image manipulation library - 
architecture header files
 libmagickcore-6-headers - 

Bug#910887: marked as done (imagemagick: CVE-2018-16412 CVE-2018-16413)

[Debian Bug Tracking System]

Your message dated Mon, 29 Oct 2018 16:50:36 +
with message-id 
and subject line Bug#910887: fixed in imagemagick 8:6.9.10.14+dfsg-1
has caused the Debian Bug report #910887,
regarding imagemagick: CVE-2018-16412 CVE-2018-16413
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.)


-- 
910887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imagemagick
Version: 8:6.9.7.4+dfsg-11
Severity: grave
Tags: patch security upstream
Forwarded: https://github.com/ImageMagick/ImageMagick/issues/1250
Control: fixed -1 8:6.9.7.4+dfsg-11+deb9u6

[adding already the fixed version for strech-security as DSA pending]

Hi,

The following vulnerability was published for imagemagick.

CVE-2018-16412[0]:
| ImageMagick 7.0.8-11 Q16 has a heap-based buffer over-read in the
| coders/psd.c ParseImageResourceBlocks function.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16412
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16412
[1] https://github.com/ImageMagick/ImageMagick/issues/1250

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.9.10.14+dfsg-1

We believe that the bug you reported is fixed in the latest version of
imagemagick, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 910...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated imagemagick package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 29 Oct 2018 13:13:38 +0100
Source: imagemagick
Binary: imagemagick-6-common imagemagick-6-doc libmagickcore-6-headers 
libmagickwand-6-headers libmagick++-6-headers libimage-magick-perl 
libmagickcore-6-arch-config imagemagick-6.q16 libmagickcore-6.q16-6 
libmagickcore-6.q16-6-extra libmagickcore-6.q16-dev libmagickwand-6.q16-6 
libmagickwand-6.q16-dev libmagick++-6.q16-8 libmagick++-6.q16-dev 
libimage-magick-q16-perl imagemagick-6.q16hdri libmagickcore-6.q16hdri-6 
libmagickcore-6.q16hdri-6-extra libmagickcore-6.q16hdri-dev 
libmagickwand-6.q16hdri-6 libmagickwand-6.q16hdri-dev libmagick++-6.q16hdri-8 
libmagick++-6.q16hdri-dev libimage-magick-q16hdri-perl imagemagick-common 
imagemagick-doc perlmagick libmagickcore-dev libmagickwand-dev libmagick++-dev 
imagemagick
Architecture: source
Version: 8:6.9.10.14+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: ImageMagick Packaging Team 

Changed-By: Bastien Roucariès 
Description:
 imagemagick - image manipulation programs -- binaries
 imagemagick-6-common - image manipulation programs -- infrastructure
 imagemagick-6-doc - document files of ImageMagick
 imagemagick-6.q16 - image manipulation programs -- quantum depth Q16
 imagemagick-6.q16hdri - image manipulation programs -- quantum depth Q16HDRI
 imagemagick-common - image manipulation programs -- infrastructure dummy 
package
 imagemagick-doc - document files of ImageMagick -- dummy package
 libimage-magick-perl - Perl interface to the ImageMagick graphics routines
 libimage-magick-q16-perl - Perl interface to the ImageMagick graphics routines 
-- Q16 versio
 libimage-magick-q16hdri-perl - Perl interface to the ImageMagick graphics 
routines -- Q16HDRI ve
 libmagick++-6-headers - object-oriented C++ interface to ImageMagick - header 
files
 libmagick++-6.q16-8 - C++ interface to ImageMagick -- quantum depth Q16
 libmagick++-6.q16-dev - C++ interface to ImageMagick - development files (Q16)
 libmagick++-6.q16hdri-8 - C++ interface to ImageMagick -- quantum depth Q16HDRI
 libmagick++-6.q16hdri-dev - C++ interface to ImageMagick - development files 
(Q16HDRI)
 libmagick++-dev - object-oriented C++ interface to ImageMagick -- dummy package
 libmagickcore-6-arch-config - low-level image manipulation library - 
architecture header files
 libmagickcore-6-headers - low-level image manipulation library - header files
 libmagickcore-6.q16-6 - low-level image manipulation library -- 

Bug#911403: Please always include a copyright notice in 'LicenseWithSummary::summary_or_text'

[Dominique Dumont]

On Monday, 29 October 2018 16:51:45 CET you wrote:
> I am happy to provide patches and merge requests that implement your
> idea, 

Thanks. But the change is trivial. I can do it on my side. 

We just need to find a common ground that allow fixing #905614 

> but are you sure there are other meaningful consumers of the
> summary_or_text method? 

Absolutely not. But keeping backward compat with already published modules is 
one of the best values of the Perl community. I intend to keep that promise as 
much as possible

> Your posting [1] restricts uses to Debian

Debian and its 100+ derivates. 

> , and
> a search on codesearch.debian.net shows no other packages that rely on
> the current implementation that produces a copyright notice with a
> full text but not with a summary. Why is the current implementation
> worth keeping? 

Because we can't be sure that nobody will be impacted. A user may be relying 
on summary_or_text but has not (or will not) publish her or his code.

> Please forgive me if I appear insistent. It's the only
> question I have.

No problem. You're right to challenge what is not clear :-)

All the best

Bug#911403: Please always include a copyright notice in 'LicenseWithSummary::summary_or_text'

[Dominique Dumont]

On Monday, 29 October 2018 15:21:25 CET you wrote:
> I'm not thrilled at the idea of changing the behavior of summary_or_text
> method because the implementation would no longer match its behavior.

Oops, this sentence does not make sense.

I meant that "the function name would no longer match its behavior."

All the best

Processed: tagging 912245

[Debian Bug Tracking System]

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

> tags 912245 + buster sid experimental
Bug #912245 [src:ruby-nio4r] ruby-nio4r FTBFS: SSL_CTX_use_certificate: ee key 
too small
Added tag(s) sid, experimental, and buster.
> thanks
Stopping processing here.

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

Bug#912255: python-asdf FTBFS if some webserver is listening to localhost:80

[Helmut Grohne]

Source: python-asdf
Version: 2.1.0-1
Severity: serious
Tags: ftbfs

python-asdf fails to build from source if some webserver is listening to
localhost:80. The Debian policy prohibits doing so in section 4.9. The
access is only legitimate if python-asdf starts the web server.

| === FAILURES 
===
| _ test_invalid_source 
__
| 
| small_tree = {'not_shared': array([10,  9,  8,  7,  6,  5,  4,  3,  2,  1], 
dtype=uint8), 'science_data': array([0., 1., 2., 3., 4., 5., 6., 7., 8., 9.]), 
'skipping': array([0., 2., 4., 6., 8.]), 'subset': array([3., 4., 5., 6.])}
| 
| def test_invalid_source(small_tree):
| buff = io.BytesIO()
| 
| ff = asdf.AsdfFile(small_tree)
| ff.write_to(buff)
| 
| buff.seek(0)
| with asdf.AsdfFile.open(buff) as ff2:
| ff2.blocks.get_block(0)
| 
| with pytest.raises(ValueError):
| ff2.blocks.get_block(2)
| 
| with pytest.raises(IOError):
| >   ff2.blocks.get_block("http://127.0.0.1/;)
| 
| asdf/tests/test_low_level.py:141: 
| _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
| asdf/block.py:643: in get_block
| source, do_not_fill_defaults=True)
| asdf/asdf.py:364: in open_external
| do_not_fill_defaults=do_not_fill_defaults)
| asdf/asdf.py:778: in open
| ignore_missing_extensions=ignore_missing_extensions)
| _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ 
| 
| cls = 
| self = , fd = 'http://127.0.0.1/'
| uri = None, mode = 'r', validate_checksums = False, do_not_fill_defaults = 
True
| _get_yaml_content = False, _force_raw_types = False
| strict_extension_check = False, ignore_missing_extensions = False
| 
| @classmethod
| def _open_impl(cls, self, fd, uri=None, mode='r',
|validate_checksums=False,
|do_not_fill_defaults=False,
|_get_yaml_content=False,
|_force_raw_types=False,
|strict_extension_check=False,
|ignore_missing_extensions=False):
| """Attempt to open file-like object as either AsdfFile or 
AsdfInFits"""
| if not is_asdf_file(fd):
| try:
| # TODO: this feels a bit circular, try to clean up. Also
| # this introduces another dependency on astropy which may
| # not be desireable.
| from . import fits_embed
| return fits_embed.AsdfInFits._open_impl(fd, uri=uri,
| validate_checksums=validate_checksums,
| 
ignore_version_mismatch=self._ignore_version_mismatch,
| extensions=self._extensions,
| strict_extension_check=strict_extension_check,
| 
ignore_missing_extensions=ignore_missing_extensions,
| _extension_metadata=self._extension_metadata)
| except ValueError:
| pass
| raise ValueError(
| >   "Input object does not appear to be ASDF file or FITS with " +
| "ASDF extension")
| E   ValueError: Input object does not appear to be ASDF file or FITS 
with ASDF extension
| 
| asdf/asdf.py:682: ValueError
| - Captured stdout call 
-
| Downloading http://127.0.0.1/ [Done]
| === warnings summary 
===
| 
.pybuild/cpython3_3.7_asdf/build/asdf/tests/test_suite.py::test_reference_file[reference_files/1.0.0/complex.asdf]
|   /usr/lib/python3/dist-packages/numpy/core/numeric.py:2321: RuntimeWarning: 
overflow encountered in absolute
| return less_equal(abs(x-y), atol + rtol * abs(y))
| 
| -- Docs: http://doc.pytest.org/en/latest/warnings.html
| === 1 failed, 319 passed, 12 skipped, 4 xfailed, 1 warnings in 4.60 seconds 

| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.7_asdf/build; python3.7 -m pytest 
| dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.7 3.6" 
returned exit code 13
| make: *** [debian/rules:8: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut

Bug#912252: android-platform-dalvik FTBFS with OpenJDK 11

[Adrian Bunk]

Source: android-platform-dalvik
Version: 8.1.0+r23-2
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/android-platform-dalvik.html

...
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileJava'.
> error: invalid source release: 1.11

Bug#912253: ruby-protected-attributes: FTBFS reliably (failing tests)

[Helmut Grohne]

Source: ruby-protected-attributes
Version: 1.1.3-2
Severity: serious
Tags: ftbfs

ruby-protected-attributes fails to build from source reliably now. On my
system as well as on reproducible builds, I consistently see the very
same three failures:

| Finished in 0.447334s, 453.7994 runs/s, 1629.6540 assertions/s.
| 
|   1) Error:
| AccessibleParamsWrapperTest#test_accessible_wrapped_keys_from_matching_model:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/accessible_params_wrapper_test.rb:67:in 
`test_accessible_wrapped_keys_from_matching_model'
| 
|   2) Error:
| AccessibleParamsWrapperTest#test_derived_wrapped_keys_from_matching_model:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/accessible_params_wrapper_test.rb:41:in 
`test_derived_wrapped_keys_from_matching_model'
| 
|   3) Error:
| AccessibleParamsWrapperTest#test_derived_wrapped_keys_from_specified_model:
| Mocha::NotInitializedError: Mocha methods cannot be used outside the context 
of a test
| /<>/test/accessible_params_wrapper_test.rb:54:in `block in 
test_derived_wrapped_keys_from_specified_model'
| /<>/test/accessible_params_wrapper_test.rb:9:in 
`with_default_wrapper_options'
| /<>/test/accessible_params_wrapper_test.rb:53:in 
`test_derived_wrapped_keys_from_specified_model'
| 
| 203 runs, 729 assertions, 0 failures, 3 errors, 0 skips
| rake aborted!
| Command failed with status (1): [ruby -w -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/accessible_params_wrapper_test.rb" "test/attribute_sanitization_test.rb" 
"test/mass_assignment_security/black_list_test.rb" 
"test/mass_assignment_security/permission_set_test.rb" 
"test/mass_assignment_security/sanitizer_test.rb" 
"test/mass_assignment_security/strong_parameters_fallback_test.rb" 
"test/mass_assignment_security/white_list_test.rb" 
"test/mass_assignment_security_test.rb" "test/test_helper.rb" -v]
| 
| Tasks: TOP => default
| (See full trace by running task with --trace)
| ERROR: Test "ruby2.5" failed. Exiting.
| dh_auto_install: dh_ruby --install 
/<>/debian/ruby-protected-attributes returned exit code 1
| make: *** [debian/rules:6: binary] Error 1
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

Helmut

Bug#912250: gkl FTBFS with OpenJDK 11

[Adrian Bunk]

Source: gkl
Version: 0.8.5+dfsg-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gkl.html

...
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileJava'.
> error: invalid source release: 1.11

Bug#912249: ruby-file-tail FTBFS: test_tail_change2(FileTailTest) fails

[Helmut Grohne]

Source: ruby-file-tail
Version: 1.1.1-2
Severity: serious
Tags: ftbfs

ruby-file-tail fails to build from source in unstable.

| Failure: test_tail_change2(FileTailTest)
| /<>/tests/file_tail_test.rb:353:in `test_tail_change2'
|  350: end
|  351: appender.join
|  352: logger.join
|   => 353: assert_equal(110, lines.size)
|  354: assert reopened
|  355: assert_equal 10, @in.lineno
|  356:   end
| <110> expected but was
| <20>
| 
| diff:
| ? 110
| ? 2
| 
===
| 
| Finished in 24.813629151 seconds.
| 
---
| 20 tests, 70 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
| 95% passed
| 
---
| 0.81 tests/s, 2.82 assertions/s
| ERROR: Test "ruby2.5" failed. Exiting.
| dh_auto_install: dh_ruby --install /<>/debian/ruby-file-tail 
returned exit code 1
| make: *** [debian/rules:16: binary] Error 1
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

Helmut

Bug#912248: gatk-native-bindings FTBFS with OpenJDK 11

[Adrian Bunk]

Source: gatk-native-bindings
Version: 1.0.0-2
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gatk-native-bindings.html

...
All input files are considered out-of-date for incremental task ':compileJava'.
Compiling with JDK Java compiler API.
:compileJava FAILED
:compileJava (Thread[Task worker for ':' Thread 2,5,main]) completed. Took 
0.301 secs.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileJava'.
> error: invalid source release: 1.11

Bug#912247: starman FTBFS: ssl tests fail

[Helmut Grohne]

Source: starman
Version: 0.4014-2
Severity: serious
Tags: ftbfs

starman fails to build from source in unstable. Presumably openssl broke
it:

| t/ssl.t .. 
| Dubious, test returned 111 (wstat 28416, 0x6f00)
| No subtests run 
| 2018/10/29-15:24:42 Starman::Server (type Net::Server::PreFork) starting! 
pid(13247)
| Resolved [localhost]:46413 to [127.0.0.1]:46413, IPv4
| Binding to SSL port 46413 on host 127.0.0.1 with IPv4
| 2018/10/29-15:24:42 Cannot connect to SSL port 46413 on 127.0.0.1 [No such 
file or directory]
|   at line 105 in file /usr/share/perl5/Net/Server/Proto/SSL.pm
| 2018/10/29-15:24:42 Received QUIT. Running a graceful shutdown
| 2018/10/29-15:24:42 Worker processes cleaned up
| 2018/10/29-15:24:42 Server closing!
| cannot open port: 127.0.0.1:46413 at /usr/share/perl5/Test/TCP.pm line 53.
| t/ssl_largebody.t  
| Dubious, test returned 111 (wstat 28416, 0x6f00)
| No subtests run 
| 2018/10/29-15:24:59 Starman::Server (type Net::Server::PreFork) starting! 
pid(13283)
| Binding to TCP port 35767 on host 127.0.0.1 with IPv4
| Setting gid to "1000 1000 4 24 29 44 111 114 115 136 142 1000"
| 2018/10/29-15:24:59 Server closing!
...
| Test Summary Report
| ---
| t/ssl.t(Wstat: 28416 Tests: 0 Failed: 0)
|   Non-zero exit status: 111
|   Parse errors: No plan found in TAP output
| t/ssl_largebody.t  (Wstat: 28416 Tests: 0 Failed: 0)
|   Non-zero exit status: 111
|   Parse errors: No plan found in TAP output
| Files=13, Tests=111, 34 wallclock secs ( 0.04 usr  0.01 sys +  0.95 cusr  
0.22 csys =  1.22 CPU)
| Result: FAIL
| dh_auto_test: perl Build test --verbose 1 returned exit code 1
| make: *** [debian/rules:7: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut

Bug#912246: ruby-cheffish FTBFS: uses unavailable default cipher DES-EDE3-CBC

[Helmut Grohne]

Source: ruby-cheffish
Version: 13.1.0-1
Severity: serious
Tags: ftbfs

ruby-cheffish fails to build from source in unstable:

| An error occurred while loading ./spec/unit/recipe_run_wrapper_spec.rb.
| Failure/Error: property :cipher, OpenSSL::Cipher.ciphers, default: 
"DES-EDE3-CBC"
| 
| Chef::Exceptions::ValidationFailed:
|   Property cipher must be one of: "aes-128-cbc", "aes-128-cbc-hmac-sha1", 
"aes-128-cbc-hmac-sha256", "aes-128-ccm", "aes-128-cfb", "aes-128-cfb1", 
"aes-128-cfb8", "aes-128-ctr", "aes-128-ecb", "aes-128-gcm", "aes-128-ocb", 
"aes-128-ofb", "aes-128-xts", "aes-192-cbc", "aes-192-ccm", "aes-192-cfb", 
"aes-192-cfb1", "aes-192-cfb8", "aes-192-ctr", "aes-192-ecb", "aes-192-gcm", 
"aes-192-ocb", "aes-192-ofb", "aes-256-cbc", "aes-256-cbc-hmac-sha1", 
"aes-256-cbc-hmac-sha256", "aes-256-ccm", "aes-256-cfb", "aes-256-cfb1", 
"aes-256-cfb8", "aes-256-ctr", "aes-256-ecb", "aes-256-gcm", "aes-256-ocb", 
"aes-256-ofb", "aes-256-xts", "aes128", "aes128-wrap", "aes192", "aes192-wrap", 
"aes256", "aes256-wrap", "aria-128-cbc", "aria-128-ccm", "aria-128-cfb", 
"aria-128-cfb1", "aria-128-cfb8", "aria-128-ctr", "aria-128-ecb", 
"aria-128-gcm", "aria-128-ofb", "aria-192-cbc", "aria-192-ccm", "aria-192-cfb", 
"aria-192-cfb1", "aria-192-cfb8", "aria-192-ctr", "aria-192-ecb", 
"aria-192-gcm", "aria-192-ofb", "aria-256-cbc", "aria-256-ccm", "aria-256-cfb", 
"aria-256-cfb1", "aria-256-cfb8", "aria-256-ctr", "aria-256-ecb", 
"aria-256-gcm", "aria-256-ofb", "aria128", "aria192", "aria256", "bf", 
"bf-cbc", "bf-cfb", "bf-ecb", "bf-ofb", "blowfish", "camellia-128-cbc", 
"camellia-128-cfb", "camellia-128-cfb1", "camellia-128-cfb8", 
"camellia-128-ctr", "camellia-128-ecb", "camellia-128-ofb", "camellia-192-cbc", 
"camellia-192-cfb", "camellia-192-cfb1", "camellia-192-cfb8", 
"camellia-192-ctr", "camellia-192-ecb", "camellia-192-ofb", "camellia-256-cbc", 
"camellia-256-cfb", "camellia-256-cfb1", "camellia-256-cfb8", 
"camellia-256-ctr", "camellia-256-ecb", "camellia-256-ofb", "camellia128", 
"camellia192", "camellia256", "cast", "cast-cbc", "cast5-cbc", "cast5-cfb", 
"cast5-ecb", "cast5-ofb", "chacha20", "chacha20-poly1305", "des", "des-cbc", 
"des-cfb", "des-cfb1", "des-cfb8", "des-ecb", "des-ede", "des-ede-cbc", 
"des-ede-cfb", "des-ede-ecb", "des-ede-ofb", "des-ede3", "des-ede3-cbc", 
"des-ede3-cfb", "des-ede3-cfb1", "des-ede3-cfb8", "des-ede3-ecb", 
"des-ede3-ofb", "des-ofb", "des3", "des3-wrap", "desx", "desx-cbc", 
"id-aes128-CCM", "id-aes128-GCM", "id-aes128-wrap", "id-aes128-wrap-pad", 
"id-aes192-CCM", "id-aes192-GCM", "id-aes192-wrap", "id-aes192-wrap-pad", 
"id-aes256-CCM", "id-aes256-GCM", "id-aes256-wrap", "id-aes256-wrap-pad", 
"id-smime-alg-CMS3DESwrap", "rc2", "rc2-128", "rc2-40", "rc2-40-cbc", "rc2-64", 
"rc2-64-cbc", "rc2-cbc", "rc2-cfb", "rc2-ecb", "rc2-ofb", "rc4", "rc4-40", 
"rc4-hmac-md5", "seed", "seed-cbc", "seed-cfb", "seed-ecb", "seed-ofb", "sm4", 
"sm4-cbc", "sm4-cfb", "sm4-ctr", "sm4-ecb", "sm4-ofb"!  You passed 
"DES-EDE3-CBC".
| # ./lib/chef/resource/private_key.rb:34:in `'
| # ./lib/chef/resource/private_key.rb:8:in `'
| # ./lib/chef/resource/private_key.rb:7:in `'
| # ./lib/chef/resource/private_key.rb:6:in `'
| # ./lib/cheffish/recipe_dsl.rb:25:in `'
| # ./lib/cheffish.rb:130:in `'
| # ./spec/support/spec_support.rb:3:in `'
| # ./spec/unit/recipe_run_wrapper_spec.rb:1:in `'
| 
| Finished in 0.00014 seconds (files took 0.78209 seconds to load)
| 0 examples, 0 failures, 16 errors occurred outside of examples
| 
| /usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
| ERROR: Test "ruby2.5" failed. Exiting.
| dh_auto_install: dh_ruby --install /<>/debian/ruby-cheffish 
returned exit code 1
| make[1]: *** [debian/rules:11: override_dh_auto_install] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:7: binary] Error 2
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

Looks like ruby-cheffish expects openssl to provide DES-EDE3-CBC, but
that one is only available in lower case.

Helmut

Bug#912235: [Debian-med-packaging] Bug#912235: figtree FTBFS with OpenJDK 11

[Fabian Klötzl]

Thank you for reporting. I added a fix to the repo. Will get resolved 
with the next upload.


Best
Fabian

Bug#911403: Please always include a copyright notice in 'LicenseWithSummary::summary_or_text'

[Felix Lechner]

Hi Dominique,

I am happy to provide patches and merge requests that implement your
idea, but are you sure there are other meaningful consumers of the
summary_or_text method? Your posting [1] restricts uses to Debian, and
a search on codesearch.debian.net shows no other packages that rely on
the current implementation that produces a copyright notice with a
full text but not with a summary. Why is the current implementation
worth keeping? Please forgive me if I appear insistent. It's the only
question I have. Thank you!

Kind regards,
Felix

[1] 
https://ddumont.wordpress.com/2018/07/07/new-softwarelicensemoreutils-perl-module/


On Mon, Oct 29, 2018 at 7:22 AM Dominique Dumont  wrote:
>
> On Sat, 27 Oct 2018 15:57:56 +0200 gregor herrmann  wrote:
> > Dominique, could you look into this patch, please?
>
> yes, sorry for the delay.
>
> I'm not thrilled at the idea of changing the behavior of summary_or_text
> method because the implementation would no longer match its behavior.
>
> Felix, how about un-deprecating debian_text method and putting your code there
> ?
>
> All the best
>
>

Bug#912245: ruby-nio4r FTBFS: SSL_CTX_use_certificate: ee key too small

[Helmut Grohne]

Source: ruby-nio4r
Version: 1.2.1-1
Severity: serious
Tags: ftbfs

ruby-nio4r fails to build in unstable with the current openssl:

| Failures:
| 
|   1) OpenSSL::SSL::SSLSocket behaves like an NIO selectable selects readable 
objects
|  Failure/Error: ssl_peer = OpenSSL::SSL::SSLSocket.new(peer, 
ssl_server_context)
| 
|  OpenSSL::SSL::SSLError:
|SSL_CTX_use_certificate: ee key too small
|  Shared Example Group: "an NIO selectable" called from 
./spec/nio/selectables/ssl_socket_spec.rb:160
|  # ./spec/nio/selectables/ssl_socket_spec.rb:36:in `initialize'
|  # ./spec/nio/selectables/ssl_socket_spec.rb:36:in `new'
|  # ./spec/nio/selectables/ssl_socket_spec.rb:36:in `block (2 levels) in 
'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:298:in `block 
(2 levels) in let'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:157:in `block 
(3 levels) in fetch_or_store'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:157:in `fetch'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:157:in `block 
(2 levels) in fetch_or_store'
|  # /usr/lib/ruby/vendor_ruby/rspec/support/reentrant_mutex.rb:23:in 
`synchronize'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:156:in `block 
in fetch_or_store'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:155:in `fetch'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:155:in 
`fetch_or_store'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:298:in `block 
in let'
|  # ./spec/support/selectable_examples.rb:5:in `block (2 levels) in '
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in `instance_exec'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in `block in run'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:500:in `block in 
with_around_and_singleton_context_hooks'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:457:in `block in 
with_around_example_hooks'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `block in run'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:602:in 
`run_around_example_hooks_for'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `run'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:457:in 
`with_around_example_hooks'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:500:in 
`with_around_and_singleton_context_hooks'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:251:in `run'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:629:in `block in 
run_examples'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:625:in `map'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:625:in 
`run_examples'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:591:in `run'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:592:in `block in 
run'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:592:in `map'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:592:in `run'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:116:in `block (3 
levels) in run_specs'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:116:in `map'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:116:in `block (2 
levels) in run_specs'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1989:in 
`with_suite_hooks'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:111:in `block in 
run_specs'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:74:in `report'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:110:in `run_specs'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:87:in `run'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
|  # /usr/bin/rspec:4:in `'
| 
|   2) OpenSSL::SSL::SSLSocket behaves like an NIO selectable does not select 
unwritable objects
|  Failure/Error: ssl_peer = OpenSSL::SSL::SSLSocket.new(peer, 
ssl_server_context)
| 
|  OpenSSL::SSL::SSLError:
|SSL_CTX_use_certificate: ee key too small
|  Shared Example Group: "an NIO selectable" called from 
./spec/nio/selectables/ssl_socket_spec.rb:160
|  # ./spec/nio/selectables/ssl_socket_spec.rb:99:in `initialize'
|  # ./spec/nio/selectables/ssl_socket_spec.rb:99:in `new'
|  # ./spec/nio/selectables/ssl_socket_spec.rb:99:in `block (2 levels) in 
'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:298:in `block 
(2 levels) in let'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:157:in `block 
(3 levels) in fetch_or_store'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:157:in `fetch'
|  # /usr/lib/ruby/vendor_ruby/rspec/core/memoized_helpers.rb:157:in `block 
(2 levels) in fetch_or_store'
|  # 

Bug#912243: libsmali-1-java FTBFS with OpenJDK 11

[Adrian Bunk]

Source: libsmali-1-java
Version: 1.4.2-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libsmali-1-java.html

...
All input files are considered out-of-date for incremental task 
':dexlib:compileJava'.
Compiling with JDK Java compiler API.
:dexlib:compileJava FAILED
:dexlib:compileJava (Thread[Task worker for ':',5,main]) completed. Took 1.207 
secs.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':dexlib:compileJava'.
> error: invalid source release: 1.11

* Try:
Run with --debug option to get more log output. Run with --scan to get full 
insights.

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task 
':dexlib:compileJava'.
at 
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:100)
at 
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:70)
at 
org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51)
at 
org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:62)
at 
org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54)
at 
org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:60)
at 
org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:97)
at 
org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:87)
at 
org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:52)
at 
org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)
at 
org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
at 
org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at 
org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.run(DefaultTaskGraphExecuter.java:248)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:241)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:230)
at 
org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.processTask(DefaultTaskPlanExecutor.java:123)
at 
org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.access$200(DefaultTaskPlanExecutor.java:79)
at 
org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:104)
at 
org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:98)
at 
org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.execute(DefaultTaskExecutionPlan.java:626)
at 
org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.executeWithTask(DefaultTaskExecutionPlan.java:581)
at 
org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.run(DefaultTaskPlanExecutor.java:98)
at 
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at 
org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
at 
org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
Caused by: java.lang.IllegalArgumentException: error: invalid source release: 
1.11
at 
jdk.compiler/com.sun.tools.javac.main.Arguments.error(Arguments.java:907)
at 
jdk.compiler/com.sun.tools.javac.main.Arguments.doProcessArgs(Arguments.java:383)
at 
jdk.compiler/com.sun.tools.javac.main.Arguments.processArgs(Arguments.java:347)
at 

Bug#912116: nuitka FTBFS: test failures

[Kay Hayen]

Hello Adrian,

> +simpleFunction21: FAILED 125836 125872 leaked 36

The reference counting in 3.7.0 was broken, as reported in
https://bugs.python.org/issue34042 which is reported fixed.

For current releases, I have had disabled it for 3.7.0 therefore, and
couldn't see what 3.7.1 will be. These now might be actual bugs become
visible only with 3.7.1, which I need to look at, and fix it.

Yours,
Kay

Processed: severity of 912221 is serious

[Debian Bug Tracking System]

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

> severity 912221 serious
Bug #912221 [jabref] jabref: incompatible with openjdk 11
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#912241: uuagc FTBFS: error: Repeated declaration of synthesized attribute copy of nonterminal Pattern.

[Helmut Grohne]

Source: uuagc
Version: 0.9.52.1-2
Severity: serious
Tags: ftbfs

uuagc fails to build from source in unstable on the official buildds for
any arch tried thus far:

https://buildd.debian.org/status/fetch.php?pkg=uuagc=amd64=0.9.52.1-2=1538622922=0

| src-ag/Patterns.ag:22:23: error: Repeated declaration of synthesized 
attribute copy of nonterminal Pattern.
|  First definition: "src-ag/Patterns.ag"(line 
22, column 23).
|  Other definition: "src-ag/Patterns.ag"(line 
22, column 23).
| src-ag/Patterns.ag:22:23: error: Repeated declaration of synthesized 
attribute copy of nonterminal Patterns.
|  First definition: "src-ag/Patterns.ag"(line 
22, column 23).
|  Other definition: "src-ag/Patterns.ag"(line 
22, column 23).
...
| make: *** [/usr/share/cdbs/1/class/hlibrary.mk:147: build-ghc-stamp] Error 1
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

Helmut

Bug#912239: ruby-httparty FTBFS: SSL_CTX_use_certificate: ee key too small

[Helmut Grohne]

Source: ruby-httparty
Version: 0.16.2+dfsg1-1
Severity: serious
Tags: ftbfs

ruby-httparty fails to build from source in unstable:


| 
GEM_PATH=debian/ruby-httparty/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -e gem\ \"httparty\"
| 
| 
┌──┐
| │ Run tests for ruby2.5 from debian/ruby-tests.rake   
 │
| 
└──┘
| 
| RUBYLIB=/<>/debian/ruby-httparty/usr/lib/ruby/vendor_ruby:. 
GEM_PATH=debian/ruby-httparty/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
| /usr/bin/ruby2.5 /usr/bin/rspec --pattern spec/\*\*/\*_spec.rb
| /<>/spec/httparty/request/body_spec.rb:3: warning: setting 
Encoding.default_external
| Run options: include {:focus=>true}
| 
| All examples were filtered out; ignoring {:focus=>true}
| 
| Randomized with seed 46039
| 
*.#>/spec/support/ssl_test_server.rb:34
 run> terminated with exception (report_on_exception is true):
| /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `initialize': 
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)
|   from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `new'
|   from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `accept'
|   from /<>/spec/support/ssl_test_server.rb:56:in 
`thread_main'
|   from /<>/spec/support/ssl_test_server.rb:34:in `block (2 
levels) in start'
| 
.#>/spec/support/ssl_test_server.rb:34
 run> terminated with exception (report_on_exception is true):
| /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `initialize': 
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)
|   from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `new'
|   from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `accept'
|   from /<>/spec/support/ssl_test_server.rb:56:in 
`thread_main'
|   from /<>/spec/support/ssl_test_server.rb:34:in `block (2 
levels) in start'
| 
.#>/spec/support/ssl_test_server.rb:34
 run> terminated with exception (report_on_exception is true):
| /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `initialize': 
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)
|   from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `new'
|   from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `accept'
|   from /<>/spec/support/ssl_test_server.rb:56:in 
`thread_main'
|   from /<>/spec/support/ssl_test_server.rb:34:in `block (2 
levels) in start'
| 
F#>/spec/support/ssl_test_server.rb:34
 run> terminated with exception (report_on_exception is true):
| /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `initialize': 
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)
|   from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `new'
|   from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `accept'
|   from /<>/spec/support/ssl_test_server.rb:56:in 
`thread_main'
|   from /<>/spec/support/ssl_test_server.rb:34:in `block (2 
levels) in start'
| 
F#>/spec/support/ssl_test_server.rb:34
 run> terminated with exception (report_on_exception is true):
| /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `initialize': 
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)
|   from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `new'
|   from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `accept'
|   from /<>/spec/support/ssl_test_server.rb:56:in 
`thread_main'
|   from /<>/spec/support/ssl_test_server.rb:34:in `block (2 
levels) in start'
| 
.#>/spec/support/ssl_test_server.rb:34
 run> terminated with exception (report_on_exception is true):
| /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `initialize': 
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)
|   from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `new'
|   from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `accept'
|   from /<>/spec/support/ssl_test_server.rb:56:in 
`thread_main'
|   from /<>/spec/support/ssl_test_server.rb:34:in `block (2 
levels) in start'
| 
F#>/spec/support/ssl_test_server.rb:34
 run> terminated with exception (report_on_exception is true):
| /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `initialize': 
SSL_CTX_use_certificate: ee key too small (OpenSSL::SSL::SSLError)
|   from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `new'
|   from /usr/lib/ruby/2.5.0/openssl/ssl.rb:483:in `accept'

Bug#912240: gentlyweb-utils FTBFS with OpenJDK 11

[Adrian Bunk]

Source: gentlyweb-utils
Version: 1.5-1
Severity: serious
Tags: ftbfs buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gentlyweb-utils.html

...
   jh_linkjars
   jh_build
find src -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp 
/usr/share/java/jdom1.jar:debian/_jh_build.gentlyweb-utils -d 
debian/_jh_build.gentlyweb-utils -source 1.7 -target 1.7 -encoding ISO8859-1
warning: [options] bootstrap class path not set in conjunction with -source 7
src/utils/com/gentlyweb/utils/URLDataSource.java:22: error: package 
javax.activation does not exist
import javax.activation.DataSource;
   ^
src/utils/com/gentlyweb/utils/URLDataSource.java:26: error: cannot find symbol
public class URLDataSource implements DataSource
  ^
  symbol: class DataSource
src/utils/com/gentlyweb/utils/HTMLDataSource.java:23: error: package 
javax.activation does not exist
import javax.activation.DataSource;
   ^
src/utils/com/gentlyweb/utils/HTMLDataSource.java:25: error: cannot find symbol
public class HTMLDataSource implements DataSource
   ^
  symbol: class DataSource
src/utils/com/gentlyweb/utils/GZIPFileDataSource.java:29: error: package 
javax.activation does not exist
import javax.activation.DataSource;
   ^
src/utils/com/gentlyweb/utils/GZIPFileDataSource.java:137: error: cannot find 
symbol
public class GZIPFileDataSource implements DataSource
   ^
  symbol: class DataSource
src/utils/com/gentlyweb/utils/Getter.java:384: warning: non-varargs call of 
varargs method with inexact argument type for last parameter;
 null);
 ^
  cast to Class for a varargs call
  cast to Class[] for a non-varargs call and to suppress this warning
src/utils/com/gentlyweb/utils/Getter.java:413: warning: non-varargs call of 
varargs method with inexact argument type for last parameter;
 null);
 ^
  cast to Class for a varargs call
  cast to Class[] for a non-varargs call and to suppress this warning
src/utils/com/gentlyweb/utils/Getter.java:432: warning: non-varargs call of 
varargs method with inexact argument type for last parameter;
null);
^
  cast to Class for a varargs call
  cast to Class[] for a non-varargs call and to suppress this warning
Note: src/utils/com/gentlyweb/utils/GeneralFilter.java uses or overrides a 
deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
6 errors
4 warnings
make: *** [debian/rules:14: build] Error 123

Bug#912238: android-platform-libnativehelper FTBFS: ScopedPthreadMutexLock.h: No such file or directory

[Adrian Bunk]

Source: android-platform-libnativehelper
Version: 7.0.0+r33-1
Severity: serious
Tags: ftbfs buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/android-platform-libnativehelper.html

...
g++ JNIHelp.cpp JniConstants.cpp toStringArray.cpp JniInvocation.cpp 
AsynchronousCloseMonitor.cpp -o libnativehelper.so.0 -g -O2 
-ffile-prefix-map=/build/1st/android-platform-libnativehelper-7.0.0+r33=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-fvisibility=protected -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG 
-I/usr/include/android -Iinclude/nativehelper -I/usr/include/android/libcore 
-Wl,-z,relro -fPIC -shared -Wl,-soname,libnativehelper.so.0 -ldl -lpthread 
-Wl,-rpath=/usr/lib/x86_64-linux-gnu/android 
-L/usr/lib/x86_64-linux-gnu/android -llog
In file included from AsynchronousCloseMonitor.cpp:19:
include/nativehelper/AsynchronousCloseMonitor.h:20:10: fatal error: 
ScopedPthreadMutexLock.h: No such file or directory
 #include "ScopedPthreadMutexLock.h"
  ^~
compilation terminated.
make[2]: *** [debian/Makefile:14: build] Error 1

Bug#912075: [Pkg-ayatana-devel] Bug#912075: ayatana-indicator-power FTBFS with googletest 1.8.1-1

[Adrian Bunk]

On Mon, Oct 29, 2018 at 02:09:15PM +, Mike Gabriel wrote:
>...
> Hi Adrian,

Hi Mike,

>...
> Can you retry with -4. Please reopen this bug, if you see the issue re-occur.

confirmed that it is fixed now.

> Mike

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#912236: ruby-ffi-rzmq FTBFS: SSL_CTX_use_certificate: ee key too small

[Helmut Grohne]

Source: ruby-ffi-rzmq
Version: 2.0.6-1
Severity: serious
Tags: ftbfs

ruby-ffi-rzmq fails to build from source in unstable (but not in
testing):

| Failures:
| 
|   1) ZMQ::Poller poll works with SSLSocket
|  Failure/Error: server = OpenSSL::SSL::SSLSocket.new(s, ctx)
| 
|  OpenSSL::SSL::SSLError:
|SSL_CTX_use_certificate: ee key too small
|  # ./spec/poll_spec.rb:254:in `initialize'
|  # ./spec/poll_spec.rb:254:in `new'
|  # ./spec/poll_spec.rb:254:in `block (3 levels) in '
| 
| Finished in 2.72 seconds (files took 0.12738 seconds to load)
| 443 examples, 1 failure
| 
| Failed examples:
| 
| rspec ./spec/poll_spec.rb:240 # ZMQ::Poller poll works with SSLSocket
| 
| ERROR: Test "ruby2.5" failed. Exiting.
| dh_auto_install: dh_ruby --install /<>/debian/ruby-ffi-rzmq 
returned exit code 1
| make: *** [debian/rules:15: binary] Error 1
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

Looks like more openssl fallout.

Helmut

Bug#912206: freerdp2-x11: ERRCONNECT_TLS_CONNECT_FAILED with libssl1.1 1.1.1-1

[Kevin Locke]

On Mon, 2018-10-29 at 14:13 +, Mike Gabriel wrote:
> Bernhard from FreeRDP upstream has started working on this and we will
> likely provide patches next week.
> 
> So, please stay tuned + thanks for reporting this. The problem is caused by
> system-wide openssl default settings that have changed between those two
> referenced openssl versions. We will try to pin things down in FreeRDP, so
> that system-wide defaults don't apply anymore for FreeRDP.

Sounds great.  Will do.  Let me know if there is anything else I can
do to help.

Thanks,
Kevin

Bug#912234: commons-httpclient FTBFS with OpenJDK 11

[Adrian Bunk]

Source: commons-httpclient
Version: 3.1-14
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/commons-httpclient.html

...
[ERROR] Tests run: 591, Failures: 0, Errors: 29, Skipped: 0, Time elapsed: 
24.172 s <<< FAILURE! - in org.apache.commons.httpclient.TestAll
[ERROR] 
testTunnellingParamsHostHTTP10AndMethodHTTP11(org.apache.commons.httpclient.params.TestSSLTunnelParams)
  Time elapsed: 0.45 s  <<< ERROR!
javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake
at 
java.base/sun.security.ssl.SSLSocketImpl.handleEOF(SSLSocketImpl.java:1321)
at 
java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1160)
at 
java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(SSLSocketImpl.java:1063)
at 
java.base/sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:402)
at 
java.base/sun.security.ssl.SSLSocketImpl.ensureNegotiated(SSLSocketImpl.java:716)
at 
java.base/sun.security.ssl.SSLSocketImpl$AppOutputStream.write(SSLSocketImpl.java:970)
at 
java.base/java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:81)
at 
java.base/java.io.BufferedOutputStream.flush(BufferedOutputStream.java:142)
at 
org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:828)
at 
org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2116)
at 
org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
at 
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at 
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at 
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at 
org.apache.commons.httpclient.params.TestSSLTunnelParams.testTunnellingParamsHostHTTP10AndMethodHTTP11(TestSSLTunnelParams.java:182)
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at 
java.base/sun.security.ssl.SSLSocketInputRecord.decode(SSLSocketInputRecord.java:167)
at java.base/sun.security.ssl.SSLTransport.decode(SSLTransport.java:108)
at 
java.base/sun.security.ssl.SSLSocketImpl.decode(SSLSocketImpl.java:1152)
... 41 more

...

Bug#912235: figtree FTBFS with OpenJDK 11

[Adrian Bunk]

Source: figtree
Version: 1.4.3+dfsg-6
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/figtree.html

...
compile:
[javac] /build/1st/figtree-1.4.3+dfsg/build.xml:40: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Compiling 127 source files to /build/1st/figtree-1.4.3+dfsg/build
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 6
[javac] warning: [options] source value 6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/figtree-1.4.3+dfsg/src/figtree/treeviewer/painters/LabelPainter.java:23:
 error: package com.sun.tools.corba.se.idl does not exist
[javac] import com.sun.tools.corba.se.idl.InterfaceEntry;
[javac]  ^
[javac] 
/build/1st/figtree-1.4.3+dfsg/src/figtree/treeviewer/DiscreteColourScaleDialog.java:27:
 error: package javax.activation does not exist
[javac] import javax.activation.DataHandler;
[javac]^
[javac] 2 errors
[javac] 4 warnings

BUILD FAILED
/build/1st/figtree-1.4.3+dfsg/build.xml:40: Compile failed; see the compiler 
error output for details.

Total time: 3 seconds
dh_auto_build: ant -Duser.name debian returned exit code 1
make: *** [debian/rules:12: binary] Error 2

Bug#912233: checkstyle FTBFS with OpenJDK 11

[Adrian Bunk]

Source: checkstyle
Version: 8.8-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/checkstyle.html

...
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 14.597 s
[INFO] Finished at: 2018-10-28T22:50:53-12:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) 
on project checkstyle: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/checkstyle-8.8/src/main/java/com/puppycrawl/tools/checkstyle/xpath/AbstractNode.java:[292,35]
 iterate() in com.puppycrawl.tools.checkstyle.xpath.AbstractNode cannot 
implement iterate() in net.sf.saxon.om.Item
[ERROR]   return type net.sf.saxon.om.SequenceIterator is not compatible with 
net.sf.saxon.tree.iter.UnfailingIterator
[ERROR] 
/build/1st/checkstyle-8.8/src/main/java/com/puppycrawl/tools/checkstyle/xpath/AbstractNode.java:[271,5]
 method does not override or implement a method from a supertype
[ERROR] 
/build/1st/checkstyle-8.8/src/main/java/com/puppycrawl/tools/checkstyle/xpath/AttributeNode.java:[32,8]
 com.puppycrawl.tools.checkstyle.xpath.AttributeNode is not abstract and does 
not override abstract method iterate() in net.sf.saxon.om.GroundedValue
[ERROR] 
/build/1st/checkstyle-8.8/src/main/java/com/puppycrawl/tools/checkstyle/xpath/ElementNode.java:[39,8]
 com.puppycrawl.tools.checkstyle.xpath.ElementNode is not abstract and does not 
override abstract method iterate() in net.sf.saxon.om.GroundedValue
[ERROR] 
/build/1st/checkstyle-8.8/src/main/java/com/puppycrawl/tools/checkstyle/xpath/RootNode.java:[38,8]
 com.puppycrawl.tools.checkstyle.xpath.RootNode is not abstract and does not 
override abstract method iterate() in net.sf.saxon.om.GroundedValue
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/checkstyle-8.8 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/checkstyle-8.8/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/checkstyle-8.8/debian 
-Dmaven.repo.local=/build/1st/checkstyle-8.8/debian/maven-repo --batch-mode 
package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true 
-Dlocale=en_US returned exit code 1
make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1