Bug#880886: maven-bundle-plugin FTBFS with libmaven-dependency-tree-java

[殷啟聰 | Kai-Chung Yan]

I removed the javadoc package now and it builds find in Sid. Shall I upload it 
right now?

(I still need the upload permission)



signature.asc
Description: OpenPGP digital signature

Bug#893547: ant: please do not emit --ignore-source-errors on Java 9

[tony mancill]

On Tue, Mar 20, 2018 at 08:51:32AM +0100, Ole Streicher wrote:

Hello Ole,

> On 20.03.2018 05:20, tony mancill wrote:
> > I'm in the midst of preparing an update for ant.  Is there any context
> > in which we want to add "--ignore-source-errors" to the ant javadoc
> > task, or should this patch [1] be removed entirely?
> >
> 
> I am not familar with ant, so I can't recommend here. The failure seems
> to not generally appear, but only on specific targets.
> 
> This is the snippet that produces the error:
> 
>       docletpathref="classpath"
>  failonerror="true"
>  public="true"
>  additionalparam="-headings"
>  destdir="${build.javadocs}"
>  sourcepath="${java.dir}"
>  packagenames="uk.ac.starlink.ttools.func"
>  classpathref="classpath"
>  encoding="cp1252"/>
> 
> while this one (from another package, starjava-pal) works fine:
> 
>       destdir="${dist.javadocs}"
>  author="true"
>  version="true"
>  locale="en"
>  windowtitle="${Name} API"
>  doctitle="${Name}"
>  defaultexcludes="yes"
>  source="${source.version}"
>  classpathref="classpath">
> 
> So, it may have something to do with the doclet.

You're definitely onto something here - thank you for the research.  I
enabled debug logging for maven and built checkstyle to get the full
invocation of javadoc command that fails, and it also uses doclet.

If I run those same command arguments sans the options related to doclet
(-doclet, -docletpath, and -destfile), but still including
--ignore-source-errors, and the javadoc invocation is successful.

So, the bug seems to belong to the JDK and not to ant, very possibly in
here [1].  I haven't tracked it down entirely yet, but I can reproduce
the same behavior with --dump-on-error, which is another "HIDDEN"
option.  I think ToolOption.get() [2] probably returns null (because the
option is hidden) and so we end up here [3], passing false for
isToolOption to handleDocletOptions() when we need for it to be true.
Perhaps the developer who added --ignore-source-errors and
--dump-on-error didn't realize that the parser can't handle hidden
options that don't start with '-XD'?

In any event, that's all based on static analysis of the code.  It'll
take me a bit of time to verify and come up with a patch for the JDK.

In the meantime, I don't know how many FTBFS problems it might cause if
we reverted the --ignore-source-errors patch from ant, so I'm not sure
whether we should change the current behavior or not.

Cheers,
tony

[1] 
https://github.com/dmlloyd/openjdk/blob/zlib-bytebuffer-v9/src/jdk.javadoc/share/classes/jdk/javadoc/internal/tool/Start.java#L795-L820

[2] 
https://github.com/dmlloyd/openjdk/blob/zlib-bytebuffer-v9/src/jdk.javadoc/share/classes/jdk/javadoc/internal/tool/Start.java#L795-L796

[3] 
https://github.com/dmlloyd/openjdk/blob/zlib-bytebuffer-v9/src/jdk.javadoc/share/classes/jdk/javadoc/internal/tool/Start.java#L819-L820


signature.asc
Description: PGP signature

Bug#893673: clirr: missing binary wrapper

[nkiesel]

Package: clirr
Version: 0.6-6
Severity: grave
Justification: renders package unusable

Dear Maintainer,

the actual binary (or shell script wrapper) for running `clirr` is missing from
the package, and a naive `java -jar /usr/share/java/clirr.jar` does not work
either.



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages clirr depends on:
ii  default-jre [java7-runtime]2:1.8-59
ii  java-wrappers  0.2
ii  libbcel-java   6.2-1
ii  libcommons-cli-java1.4-1
ii  libcommons-lang-java   2.6-7
ii  openjdk-8-jre [java7-runtime]  8u162-b12-1
ii  openjdk-9-jre [java7-runtime]  9.0.4+12-2

clirr recommends no packages.

clirr suggests no packages.

-- no debconf information

Bug#893668: adminer: CVE-2018-7667

[Chris Lamb]

Package: adminer
Version: 4.2.5-3
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

the following vulnerability was published for adminer.

CVE-2018-7667[0]:
| Adminer through 4.3.1 has SSRF via the server parameter.

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-7667


Regards,

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

Bug#893653: marked as done (petsc4py FTBFS)

[Debian Bug Tracking System]

Your message dated Wed, 21 Mar 2018 01:49:31 +
with message-id 
and subject line Bug#893653: fixed in petsc4py 3.8.1-3
has caused the Debian Bug report #893653,
regarding petsc4py FTBFS
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.)


-- 
893653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: petsc4py
Version: 3.8.1-2
Severity: serious

Some recent change in unstable makes petsc4py FTBFS:

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

...
# petsc4py embeds the deep PETSC_DIR path as RPATH in its library.
# Swap it out for a standard path, or else dh_shlibdeps gets confused
chrpath -d .pybuild/pythonX.Y_*/build/petsc4py/lib/PETSc*.so
open: No such file or directory
elf_open: Invalid argument
make[1]: *** [debian/rules:39: override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: petsc4py
Source-Version: 3.8.1-3

We believe that the bug you reported is fixed in the latest version of
petsc4py, 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 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated petsc4py 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: Wed, 21 Mar 2018 09:26:49 +0800
Source: petsc4py
Binary: python-petsc4py python3-petsc4py python-petsc4py-docs
Architecture: source
Version: 3.8.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Description:
 python-petsc4py - Python 2 bindings for PETSc libraries
 python-petsc4py-docs - Python bindings for PETSc libraries: documentation and 
examples
 python3-petsc4py - Python 3 bindings for PETSc libraries
Closes: 893653
Changes:
 petsc4py (3.8.1-3) unstable; urgency=medium
 .
   * update VCS tags to salsa.debian.org
   * d/rules: update path to PETSc*.so to remove RUNPATH (python build
 infrastructure has changed). Closes: #893653.
   * Build-Depends: python3-distutils
Checksums-Sha1:
 7deca9d2cdc44a9a2f42d2d267ba4920c6f319bc 2366 petsc4py_3.8.1-3.dsc
 936bbd7780254d23b649832a73e6cf4c722ef566 6524 petsc4py_3.8.1-3.debian.tar.xz
Checksums-Sha256:
 46d30424a4051b1a2ad54309316d4ac58ec1d42434ba48b8e51b809259a54895 2366 
petsc4py_3.8.1-3.dsc
 b1e1e28af37715b138106536e9c0b705ec33f194391446c338b91c84f4add7b7 6524 
petsc4py_3.8.1-3.debian.tar.xz
Files:
 01e131db25ce704549c27bea7d9306de 2366 python optional petsc4py_3.8.1-3.dsc
 f7caea8475d191c836c6b805e5f2d50e 6524 python optional 
petsc4py_3.8.1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAlqxtkkUHGRwYXJzb25z
QGRlYmlhbi5vcmcACgkQVz7x5L1aAforFg//brwz50DxSmjlsQDrAHc8vb0+mlBp
Mcts92wWjQEDwINT+hXbOH+eZ9n20gZg3xgXaTotDj51dK8tQcM/Z/ar4JHMZt/F
xKLnlFGoX8Rjpxgz2OBmjP8+f6J5pk0q9GRDyuPoHsCNRwwNJ1K7KJ73v9tAOSPb
2bxI+nTbtvV3e9qkumn6j7eFiG5L4C77iBrJE1JOzwQZa6ArRVxAX3/ylG33BFza
SrzuTsgNugw0kyA4LJSXdC5nJHBTvfKWQDlyfeEXdinYuqJE9T0sqy+1cPa3sjFM
EjVbE1EVK3yORn05iGnzmRFCrCk/NyhsRrZGj+jdzVpEjFOiCpSuQMciHfl9MqZZ
96M0SUf93eZKP5APpaTmkWkDAakknnmg0Cb3unpJ4FN/19PN5b6sW9onqhm5RhS7
mOk5h8E6cYKMNI9DA3Wew64nTTFU5n9mHINawRAsGTjnadl7otxba9545DSzkxc6
vphH43lZlkIwfsWQd0tuvizeq9Sz6YtxZy/0CFW8lHB9sBxDnmKJva0Ob2VOIhjM
gow6GODdhpP5/+0RYvYYGJiQlA825WgKihoer7vTHavIQ1/JU6IHc1Jq0aSkpV31
1Km1gX7b4nsz0LEEEJvr+C6/dHUyecmZWVs+PkehgY31fU0kiKZVCfry90sbopQ6
mDHdOnCFtYt4cCw=
=w+bn
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#893598: yasnippet-snippets: Error while updating

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #893598 [yasnippet-snippets] yasnippet-snippets: Error while updating
Severity set to 'serious' from 'normal'

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

Bug#893664: sambamba: Fails to build on i386

[Jeremy Bicha]

Source: sambamba
Version: 0.6.7-1
Severity: serious

sambamba fails to build from source on i386:

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

Thanks,
Jeremy Bicha

Bug#891570: marked as done (SSL connect attempt failed error:141A90B5:SSL routines:ssl_cipher_list_to_bytes:no ciphers available)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 23:35:31 +
with message-id 
and subject line Bug#891570: fixed in openssl 1.1.1~~pre3-1
has caused the Debian Bug report #891570,
regarding SSL connect attempt failed error:141A90B5:SSL 
routines:ssl_cipher_list_to_bytes:no ciphers available
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.)


-- 
891570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libssl1.1
Version: 1.1.1~~pre1-1
Severity: grave

SSL connect attempt failed error:141A90B5:SSL 
routines:ssl_cipher_list_to_bytes:no ciphers available
--- End Message ---
--- Begin Message ---
Source: openssl
Source-Version: 1.1.1~~pre3-1

We believe that the bug you reported is fixed in the latest version of
openssl, 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 891...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Andrzej Siewior  (supplier of updated 
openssl 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: Wed, 21 Mar 2018 00:01:08 +0100
Source: openssl
Binary: openssl libssl1.1 libcrypto1.1-udeb libssl1.1-udeb libssl-dev libssl-doc
Architecture: source
Version: 1.1.1~~pre3-1
Distribution: experimental
Urgency: medium
Maintainer: Debian OpenSSL Team 
Changed-By: Sebastian Andrzej Siewior 
Description:
 libcrypto1.1-udeb - Secure Sockets Layer toolkit - libcrypto udeb (udeb)
 libssl-dev - Secure Sockets Layer toolkit - development files
 libssl-doc - Secure Sockets Layer toolkit - development documentation
 libssl1.1  - Secure Sockets Layer toolkit - shared libraries
 libssl1.1-udeb - ssl shared library - udeb (udeb)
 openssl- Secure Sockets Layer toolkit - cryptographic utility
Closes: 878303 891570
Changes:
 openssl (1.1.1~~pre3-1) experimental; urgency=medium
 .
   * Update to 1.1.1-pre3
   * Don't suggest 1024 bit RSA key to be typical (Closes: #878303).
   * Don't insist on TLS1.3 cipher for --- End Message ---

Bug#893181: marked as done (jasmin-sable FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 23:20:07 +
with message-id 
and subject line Bug#893181: fixed in jasmin-sable 2.5.0-2
has caused the Debian Bug report #893181,
regarding jasmin-sable FTBFS with openjdk-9
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.)


-- 
893181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893181
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jasmin-sable
Version: 2.5.0-1
Severity: serious
Tags: buster sid

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

...
jas:
[javac] /build/1st/jasmin-sable-2.5.0/build.xml:84: 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 1.6
[javac] Using javac -target 1.5 is no longer supported, switching to 1.6
[javac] Compiling 62 source files to /build/1st/jasmin-sable-2.5.0/classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.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/jasmin-sable-2.5.0/lib/jas/src/jas/InvokeDynamicCP.java:28: error: 
unmappable character (0xA4) for encoding US-ASCII
[javac] uniq = (bsmClassName + "fv0?" + bsmName + "&%$91&" + bsmSig+ 
"*(012$" + methodName + "dfg8932" + methodSig).intern();
[javac]^
[javac] 
/build/1st/jasmin-sable-2.5.0/lib/jas/src/jas/MethodHandleCP.java:27: error: 
unmappable character (0xA4) for encoding US-ASCII
[javac] uniq = kind + "$gfd?" + ownerName + "&%$91&" + 
fieldOrMethodName + "*(012$" + sig;
[javac]^
[javac] 2 errors
[javac] 4 warnings

BUILD FAILED
/build/1st/jasmin-sable-2.5.0/build.xml:84: Compile failed; see the compiler 
error output for details.

Total time: 11 seconds
make[1]: *** [debian/rules:10: override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: jasmin-sable
Source-Version: 2.5.0-2

We believe that the bug you reported is fixed in the latest version of
jasmin-sable, 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 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated jasmin-sable 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: Tue, 20 Mar 2018 23:24:25 +0100
Source: jasmin-sable
Binary: jasmin-sable
Architecture: source
Version: 2.5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 jasmin-sable - Java class (.class) file assembler
Closes: 893181
Changes:
 jasmin-sable (2.5.0-2) unstable; urgency=medium
 .
   * Fixed the build failure with Java 9 (Closes: #893181)
   * Standards-Version updated to 4.1.3
   * Switch to debhelper level 11
Checksums-Sha1:
 732af3577a052fe2adf2b5a19b452d5d150112bd 2052 jasmin-sable_2.5.0-2.dsc
 e36eef9d391ed45f8003b2b1c8bddc0c3b3d5e82 5288 
jasmin-sable_2.5.0-2.debian.tar.xz
 1c6a12cc31391f08bf0a1dfa599713d07faa5045 10125 
jasmin-sable_2.5.0-2_source.buildinfo
Checksums-Sha256:
 7e825eb210d4394af3d56d536429224ab6fad6b3cf9665eb05b7892d9fc19940 2052 
jasmin-sable_2.5.0-2.dsc
 b1bfee56102a7c347177bfc354331af3af1a9a7ee0526f5c1a5ab62fcf1f735e 5288 
jasmin-sable_2.5.0-2.debian.tar.xz
 c83014d7bf6edb8db0355d797a18fa94383bf33c9354d64a5205103a9d4f9e72 10125 
jasmin-sable_2.5.0-2_source.buildinfo
Files:
 63eb86baf39fdd45565d89007eda3989 2052 devel optional jasmin-sable_2.5.0-2.dsc
 96a4de6c8626c8d139196a49c0328bc2 5288 devel optional 
jasmin-sable_2.5.0-2.debian.tar.xz
 baa78baa880e762a5510bda3266e2a6a 10125 devel optional 
jasmin-sable_2.5.0-2_source.buildinfo

-BEGIN PGP 

Bug#893602: marked as done (macro.h:423:18: error: expected ')' before '__attribute__')

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 23:21:59 +
with message-id 
and subject line Bug#893426: fixed in systemd 238-3
has caused the Debian Bug report #893426,
regarding macro.h:423:18: error: expected ')' before '__attribute__'
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.)


-- 
893426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: systemd
Version: 238-2
Severity: important
User: debian-m...@lists.debian.org
Usertags: mipsel

For some reason I cannot build systemd on a sid/mipsel system (sid
schroot on eller.d.o):

[7/1280] Compiling C object 'src/journal/journal-client@sta/sd-journal.c.o'.
FAILED: src/journal/journal-client@sta/sd-journal.c.o
cc  -Isrc/journal/journal-client@sta -Isrc/journal -I../src/journal
-I. -I../ -Isrc/libsystemd-network -I../src/libsystemd-network
-I../src/libsystemd/sd-network -I../src/libsystemd/sd-netlink
-I../src/libsystemd/sd-id128 -I../src/libsystemd/sd-hwdb
-I../src/libsystemd/sd-device -I../src/libsystemd/sd-bus -Isrc/core
-I../src/core -Isrc/libudev -I../src/libudev -Isrc/udev -I../src/udev
-Isrc/login -I../src/login -Isrc/timesync -I../src/timesync
-Isrc/resolve -I../src/resolve -Isrc/systemd -I../src/systemd
-Isrc/shared -I../src/shared -Isrc/basic -I../src/basic -flto
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=gnu99
-Wextra -Werror=undef -Wlogical-op -Wmissing-include-dirs
-Wold-style-definition -Wpointer-arith -Winit-self
-Wdeclaration-after-statement -Wfloat-equal
-Wsuggest-attribute=noreturn -Werror=missing-prototypes
-Werror=implicit-function-declaration -Werror=missing-declarations
-Werror=return-type -Werror=incompatible-pointer-types
-Werror=format=2 -Wstrict-prototypes -Wredundant-decls
-Wmissing-noreturn -Wimplicit-fallthrough=5 -Wshadow -Wendif-labels
-Wstrict-aliasing=2 -Wwrite-strings -Werror=overflow -Wdate-time
-Wnested-externs -ffast-math -fno-common -fdiagnostics-show-option
-fno-strict-aliasing -fvisibility=hidden -fstack-protector
-fstack-protector-strong --param=ssp-buffer-size=4 -fPIE
-Wno-unused-parameter -Wno-missing-field-initializers
-Wno-unused-result -Wno-format-signedness -Wno-error=nonnull
-Werror=shadow -ffunction-sections -fdata-sections -include config.h
-g -O2 -fdebug-prefix-map=/home/malat/systemd-238=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -fvisibility=default -MD -MQ
'src/journal/journal-client@sta/sd-journal.c.o' -MF
'src/journal/journal-client@sta/sd-journal.c.o.d' -o
'src/journal/journal-client@sta/sd-journal.c.o' -c
../src/journal/sd-journal.c
In file included from ../src/basic/alloc-util.h:28:0,
 from ../src/journal/sd-journal.c:33:
../src/basic/macro.h:423:18: error: expected ')' before '__attribute__'
 #define noreturn __attribute__((noreturn))
  ^
In file included from /usr/include/gcrypt.h:30:0,
 from ../src/journal/journal-file.h:26,
 from ../src/journal/sd-journal.c:46:
/usr/include/mipsel-linux-gnu/gpg-error.h:1545:46: error: expected ','
or ';' before ')' token
 void gpgrt_log_bug (const char *fmt, ...)GPGRT_ATTR_NR_PRINTF(1,2);
  ^
In file included from ../src/basic/alloc-util.h:28:0,
 from ../src/journal/sd-journal.c:33:
../src/basic/macro.h:423:18: error: expected ')' before '__attribute__'
 #define noreturn __attribute__((noreturn))
  ^
In file included from /usr/include/gcrypt.h:30:0,
 from ../src/journal/journal-file.h:26,
 from ../src/journal/sd-journal.c:46:
/usr/include/mipsel-linux-gnu/gpg-error.h:1546:46: error: expected ','
or ';' before ')' token
 void gpgrt_log_fatal (const char *fmt, ...)  GPGRT_ATTR_NR_PRINTF(1,2);
  ^
In file included from ../src/basic/alloc-util.h:28:0,
 from ../src/journal/sd-journal.c:33:
../src/basic/macro.h:423:18: error: expected ')' before '__attribute__'
 #define noreturn __attribute__((noreturn))
  ^
In file included from /usr/include/gcrypt.h:30:0,
 from ../src/journal/journal-file.h:26,
 from ../src/journal/sd-journal.c:46:
/usr/include/mipsel-linux-gnu/gpg-error.h:1558:43: error: expected ','
or ';' before ')' token
 const char *func) GPGRT_ATTR_NORETURN;
   ^
ninja: build stopped: subcommand failed.
--- End Message ---
--- Begin Message 

Bug#893426: marked as done (systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 23:21:59 +
with message-id 
and subject line Bug#893426: fixed in systemd 238-3
has caused the Debian Bug report #893426,
regarding systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN
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.)


-- 
893426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 238-2
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

systemd fails to build from source on amd64. Here is a tail of the build
log.

| FAILED: journal-core@sta/src_journal_journald-context.c.o 
| cc  -Ijournal-core@sta -I. -I.. -I../ -Isrc/libsystemd-network 
-I../src/libsystemd-network -I../src/libsystemd/sd-network 
-I../src/libsystemd/sd-netlink -I../src/libsystemd/sd-id128 
-I../src/libsystemd/sd-hwdb -I../src/libsystemd/sd-device 
-I../src/libsystemd/sd-bus -Isrc/core -I../src/core -Isrc/libudev 
-I../src/libudev -Isrc/udev -I../src/udev -Isrc/login -I../src/login 
-Isrc/timesync -I../src/timesync -Isrc/resolve -I../src/resolve -Isrc/journal 
-I../src/journal -Isrc/systemd -I../src/systemd -Isrc/shared -I../src/shared 
-Isrc/basic -I../src/basic -flto -fdiagnostics-color=always -pipe 
-D_FILE_OFFSET_BITS=64 -std=gnu99 -Wextra -Werror=undef -Wlogical-op 
-Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self 
-Wdeclaration-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn 
-Werror=missing-prototypes -Werror=implicit-function-declaration 
-Werror=missing-declarations -Werror=return-type 
-Werror=incompatible-pointer-types -Werror=format=2 -Wstrict-prototypes 
-Wredundant-decls -Wmissing-noreturn -Wimplicit-fallthrough=5 -Wshadow 
-Wendif-labels -Wstrict-aliasing=2 -Wwrite-strings -Werror=overflow -Wdate-time 
-Wnested-externs -ffast-math -fno-common -fdiagnostics-show-option 
-fno-strict-aliasing -fvisibility=hidden -fstack-protector 
-fstack-protector-strong --param=ssp-buffer-size=4 -fPIE -Wno-unused-parameter 
-Wno-missing-field-initializers -Wno-unused-result -Wno-format-signedness 
-Wno-error=nonnull -Werror=shadow -ffunction-sections -fdata-sections -include 
config.h -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ 
'journal-core@sta/src_journal_journald-context.c.o' -MF 
'journal-core@sta/src_journal_journald-context.c.o.d' -o 
'journal-core@sta/src_journal_journald-context.c.o' -c 
../src/journal/journald-context.c
| In file included from ../src/basic/alloc-util.h:28:0,
|  from ../src/journal/journald-context.c:25:
| ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’
|  #define noreturn __attribute__((noreturn))
|   ^
| In file included from /usr/include/gcrypt.h:30:0,
|  from ../src/journal/journal-file.h:26,
|  from ../src/journal/journald-server.h:31,
|  from ../src/journal/journald-context.h:30,
|  from ../src/journal/journald-context.c:33:
| /usr/include/x86_64-linux-gnu/gpg-error.h:1545:46: error: expected ‘,’ or ‘;’ 
before ‘)’ token
|  void gpgrt_log_bug (const char *fmt, ...)GPGRT_ATTR_NR_PRINTF(1,2);
|   ^
| In file included from ../src/basic/alloc-util.h:28:0,
|  from ../src/journal/journald-context.c:25:
| ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’
|  #define noreturn __attribute__((noreturn))
|   ^
| In file included from /usr/include/gcrypt.h:30:0,
|  from ../src/journal/journal-file.h:26,
|  from ../src/journal/journald-server.h:31,
|  from ../src/journal/journald-context.h:30,
|  from ../src/journal/journald-context.c:33:
| /usr/include/x86_64-linux-gnu/gpg-error.h:1546:46: error: expected ‘,’ or ‘;’ 
before ‘)’ token
|  void gpgrt_log_fatal (const char *fmt, ...)  GPGRT_ATTR_NR_PRINTF(1,2);
|   ^
| In file included from ../src/basic/alloc-util.h:28:0,
|  from ../src/journal/journald-context.c:25:
| ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’
|  #define noreturn __attribute__((noreturn))
|   ^
| In file included from /usr/include/gcrypt.h:30:0,
|  from ../src/journal/journal-file.h:26,
|  from ../src/journal/journald-server.h:31,
|  from 

Bug#893251: jabref 3.8 is started with OpenJDK 9 instead of 8

[gregor herrmann]

On Mon, 19 Mar 2018 22:40:47 -0700, tony mancill wrote:

> > Maybe that's caused by the recent update of liblog4j2-java 2.8.2-2 -> 
> > 2.10.0-1
> > Indeed, downgrading liblog4j2-java to 2.8.2-2 helps.
> > Not sure if this is a jabref problem or a liblog4j2-java issue; let's
> > hope the java experts can shed some light on this bug.
> Ouch indeed!  I'm pretty certain that this is an issue with how
> liblog4j2-java is being built for Debian.  There is some discussion of
> the issue here [1].  Basically, we need to take precautions when
> building libraries with JDK 9 that are expected to run with JDK 8
> runtimes.

Thanks for looking into this issue and for digging up this reference.
 
> That said, so far I'm not able to build a liblog4j2-java from the
> 2.10.0-1 source package that will play nicely with jabref, but I'll keep
> looking at that and other options (aside from suggesting that we start
> recommending a stretch chroot for jabref...)

Thanks. And I'm optimistic that you'll succeed in the end :)

Should we reassign this bug to liblog4j2-java (+ affects jabref)? I
suppose the problem doesn't exclusively hit jabref?
 
> [1] https://github.com/plasma-umass/doppio/issues/497


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: Rebekka Bakken & Wolfgang Muthspiel: Nowhere


signature.asc
Description: Digital Signature

Bug#893098: axis FTBFS with openjdk-9

[Markus Koschany]

Am 20.03.2018 um 23:13 schrieb Emmanuel Bourg:
> I got a quick look, the source encoding is easily fixed and the
> org.apache.axis.enum was long deprecated and can be removed. But there
> is more than that. Axis implements interfaces from javax.xml.soap that
> were upgraded in Java 9, so Axis now fails to build due to missing
> method implementations. I wonder if it's really worth upgrading Axis, or
> if we should try to remove it.

I've pushed some changes a few minutes ago. If my IDE was working with
OpenJDK 9 it would be relatively painless to generate the missing
methods but it doesn't yet. There are quite a few reverse-dependencies
though.



signature.asc
Description: OpenPGP digital signature

Bug#893561: libtablelayout-java: license does not seem to meet the DFSG

[Francesco Poli]

On Tue, 20 Mar 2018 00:41:04 +0200 Adrian Bunk wrote:

[...]
> In https://lists.debian.org/debian-legal/2005/01/msg00142.html you 
> agreed entirely that it is OK when software is made DFSG-free through
> renaming to avoid trademark violations.
> 
> What difference would it make whether our users are forbidden to change
> the namespace back to "info.clearthought" due to
> 1. trademark
> 2. licence
> 3. both

Hello Adrian,
thanks for your prompt followup!

I see an important difference between the case at hand and the Mozilla
case.

One thing is the requirement to change the *name* for the work: this is
just how the work presents itself to the user, not something that
really affects functionality/interoperability/interfaces/...
Even if the name of the executable file of a program is changed, there
are many ways to easily let the user invoke it by another name
(symlinks, wrapper scripts, aliases, and so forth...).

I think the requirement to change *namespace* for library classes
is different: it affects the possibility to create modified drop-in
replacements for the library, without having to adapt all the
programs or other libraries that use the original library.
The namespace looks like a functional aspect.

I think it's not by chance that DFSG#4 accepts the requirements to
change the *name* or the *version number*, but not the requirements
to change other, more functional, labels in a package...


I hope this clarifies.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpbU9ih8M40e.pgp
Description: PGP signature

Bug#893181: Pending fixes for bugs in the jasmin-sable package

[pkg-java-maintainers]

tag 893181 + pending
thanks

Some bugs in the jasmin-sable package are closed in revision
fa9a5c75ee33a4ff8380cda039a42636e236ca5b in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/jasmin-sable.git/commit/?id=fa9a5c7

Commit message:

Fixed the build failure with Java 9 (Closes: #893181)

Processed: Pending fixes for bugs in the jasmin-sable package

[Debian Bug Tracking System]

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

> tag 893181 + pending
Bug #893181 [src:jasmin-sable] jasmin-sable FTBFS with openjdk-9
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#892881: Bug #892881 in networking-arista marked as pending

[zigo]

Control: tag -1 pending

Hello,

Bug #892881 in networking-arista 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/openstack-team/services/networking-arista/commit/2e99485cd954bcccf271b89ef61392344498315b


Switched to Python 3 (Closes: #892881).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/892881

Processed: Bug #892881 in networking-arista marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #892881 [python-networking-arista] python-networking-arista build-depends 
on cruft package python-neutron
Added tag(s) pending.

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

Bug#892746: marked as done (python-zake FTBFS: FAIL: zake.tests.test_client.TestClient.test_child_watch_no_create)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 22:13:23 +
with message-id 
and subject line Bug#892746: fixed in python-zake 0.2.2-1
has caused the Debian Bug report #892746,
regarding python-zake FTBFS: FAIL: 
zake.tests.test_client.TestClient.test_child_watch_no_create
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.)


-- 
892746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-zake
Version: 0.1.6-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes python-zake FTBFS:

https://tests.reproducible-builds.org/debian/history/python-zake.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-zake.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/python-zake-0.1.6'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh /usr/share/openstack-pkg-tools/pkgos.make --buildsystem=python_distutils 
--with python2,python3
dh: Unknown sequence /usr/share/openstack-pkg-tools/pkgos.make (choose from: 
binary binary-arch binary-indep build build-arch build-indep clean install 
install-arch install-indep)
set -ex && for pyvers in 2.7; do \
PYTHON=python$pyvers nosetests ; \
done
+ PYTHON=python2.7 nosetests
...F
==
FAIL: zake.tests.test_client.TestClient.test_child_watch_no_create
--
_StringException: Traceback (most recent call last):
  File "/build/1st/python-zake-0.1.6/zake/tests/test_client.py", line 462, in 
test_child_watch_no_create
self.client, "/b", cb)
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 485, in 
assertRaises
self.assertThat(our_callable, matcher)
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 498, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError:  returned 



--
Ran 44 tests in 5.276s

FAILED (failures=1)
make[1]: *** [debian/rules:27: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: python-zake
Source-Version: 0.2.2-1

We believe that the bug you reported is fixed in the latest version of
python-zake, 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 892...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-zake 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, 20 Mar 2018 22:02:44 +0100
Source: python-zake
Binary: python-zake python3-zake
Architecture: source all
Version: 0.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-zake - provides a set of testing utilities for the kazoo library - Pytho
 python3-zake - provides a set of testing utilities for the kazoo library - 
Pytho
Closes: 892746
Changes:
 python-zake (0.2.2-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/rules: Changed UPSTREAM_GIT protocol to https
   * d/copyright: Changed source URL to https protocol
 .
   [ Daniel Baumann ]
   * Updating copyright format url.
   * Updating maintainer field.
   * Running wrap-and-sort -bast.
   * Removing gbp.conf, not used anymore or should be specified in the
 developers dotfiles.
 .
   [ Thomas Goirand ]
   * New upstream release.
   * Exclude broken test (Closes: #892746):
 - zake.tests.test_client.TestClient.test_child_watch_no_create.
   * Using pkgos-dh_auto_install.
Checksums-Sha1:
 cecb7ef2d56a7e5fbcb0b2a20b4eab391bf49e0f 2328 python-zake_0.2.2-1.dsc
 1b4497ed8ad15b69350d3b78a37b44715aca9e7a 16740 

Bug#893655: libwoodstox-java FTBFS with openjdk-9

[Adrian Bunk]

Source: libwoodstox-java
Version: 1:4.1.3-1
Severity: serious
Tags: buster sid
Control: fixed -1 1:5.0.3-2
Control: close -1

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

...

compile.woodstox:
[javac] Using javac -source 1.4 is no longer supported, switching to 1.6
[javac] Using javac -target 1.4 is no longer supported, switching to 1.6
[javac] Compiling 176 source files to 
/build/1st/libwoodstox-java-4.1.3/build/classes/woodstox
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.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/libwoodstox-java-4.1.3/src/java/com/ctc/wstx/osgi/WstxBundleActivator.java:29:
 error: no suitable method found for 
registerService(String,InputFactoryProviderImpl,Properties)
[javac] 
ctxt.registerService(Stax2InputFactoryProvider.class.getName(), inputP, 
inputP.getProperties());
[javac] ^
[javac] method 
BundleContext.registerService(String[],Object,Dictionary) is not 
applicable
[javac]   (argument mismatch; String cannot be converted to String[])
[javac] method 
BundleContext.registerService(String,Object,Dictionary) is not 
applicable
[javac]   (argument mismatch; Properties cannot be converted to 
Dictionary)
[javac] method 
BundleContext.registerService(Class,S#1,Dictionary) is not 
applicable
[javac]   (cannot infer type-variable(s) S#1
[javac] (argument mismatch; String cannot be converted to 
Class))
[javac] method 
BundleContext.registerService(Class,ServiceFactory,Dictionary)
 is not applicable
[javac]   (cannot infer type-variable(s) S#2
[javac] (argument mismatch; String cannot be converted to 
Class))
[javac]   where S#1,S#2 are type-variables:
[javac] S#1 extends Object declared in method 
registerService(Class,S#1,Dictionary)
[javac] S#2 extends Object declared in method 
registerService(Class,ServiceFactory,Dictionary)
[javac] 
/build/1st/libwoodstox-java-4.1.3/src/java/com/ctc/wstx/osgi/WstxBundleActivator.java:31:
 error: no suitable method found for 
registerService(String,OutputFactoryProviderImpl,Properties)
[javac] 
ctxt.registerService(Stax2OutputFactoryProvider.class.getName(), outputP, 
outputP.getProperties());
[javac] ^
[javac] method 
BundleContext.registerService(String[],Object,Dictionary) is not 
applicable
[javac]   (argument mismatch; String cannot be converted to String[])
[javac] method 
BundleContext.registerService(String,Object,Dictionary) is not 
applicable
[javac]   (argument mismatch; Properties cannot be converted to 
Dictionary)
[javac] method 
BundleContext.registerService(Class,S#1,Dictionary) is not 
applicable
[javac]   (cannot infer type-variable(s) S#1
[javac] (argument mismatch; String cannot be converted to 
Class))
[javac] method 
BundleContext.registerService(Class,ServiceFactory,Dictionary)
 is not applicable
[javac]   (cannot infer type-variable(s) S#2
[javac] (argument mismatch; String cannot be converted to 
Class))
[javac]   where S#1,S#2 are type-variables:
[javac] S#1 extends Object declared in method 
registerService(Class,S#1,Dictionary)
[javac] S#2 extends Object declared in method 
registerService(Class,ServiceFactory,Dictionary)
[javac] 
/build/1st/libwoodstox-java-4.1.3/src/java/com/ctc/wstx/osgi/WstxBundleActivator.java:35:
 error: no suitable method found for 
registerService(String,ValidationSchemaFactoryProviderImpl,Properties)
[javac] 
ctxt.registerService(Stax2ValidationSchemaFactoryProvider.class.getName(), 
impl, impl.getProperties());
[javac] ^
[javac] method 
BundleContext.registerService(String[],Object,Dictionary) is not 
applicable
[javac]   (argument mismatch; String cannot be converted to String[])
[javac] method 
BundleContext.registerService(String,Object,Dictionary) is not 
applicable
[javac]   (argument mismatch; Properties cannot be converted to 
Dictionary)
[javac] method 
BundleContext.registerService(Class,S#1,Dictionary) is not 
applicable
[javac]   (cannot infer type-variable(s) S#1
[javac] (argument mismatch; String cannot be converted to 

Bug#893098: axis FTBFS with openjdk-9

[Emmanuel Bourg]

I got a quick look, the source encoding is easily fixed and the
org.apache.axis.enum was long deprecated and can be removed. But there
is more than that. Axis implements interfaces from javax.xml.soap that
were upgraded in Java 9, so Axis now fails to build due to missing
method implementations. I wonder if it's really worth upgrading Axis, or
if we should try to remove it.

Emmanuel Bourg

Processed: libwoodstox-java FTBFS with openjdk-9

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1:5.0.3-2
Bug #893655 [src:libwoodstox-java] libwoodstox-java FTBFS with openjdk-9
Marked as fixed in versions libwoodstox-java/1:5.0.3-2.
> close -1
Bug #893655 [src:libwoodstox-java] libwoodstox-java FTBFS with openjdk-9
Marked Bug as done

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

Processed: tagging 893647

[Debian Bug Tracking System]

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

> tags 893647 + buster sid
Bug #893647 [kterm] kterm: should this package be removed?
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: tagging 893649

[Debian Bug Tracking System]

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

> tags 893649 + buster sid
Bug #893649 [xvt] xvt: should this package be removed?
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#893652: strophejs FTBFS with node-almond 0.3.3+dfsg-1

[Adrian Bunk]

Source: strophejs
Version: 1.2.14+dfsg-2
Severity: serious

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

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/strophejs-1.2.14+dfsg'
node /usr/lib/nodejs/requirejs/r.js -o build.js name=/usr/lib/nodejs/almond.js 
insertRequire=strophe-polyfill include=strophe-polyfill out=strophe.min.js
Error: Error: ERROR: module path does not exist: /usr/lib/nodejs/almond.js for 
module named: /usr/lib/nodejs/almond.js. Path is relative to: 
/build/1st/strophejs-1.2.14+dfsg
at /usr/lib/nodejs/requirejs/r.js:25979:35

make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1

Bug#893653: petsc4py FTBFS

[Adrian Bunk]

Source: petsc4py
Version: 3.8.1-2
Severity: serious

Some recent change in unstable makes petsc4py FTBFS:

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

...
# petsc4py embeds the deep PETSC_DIR path as RPATH in its library.
# Swap it out for a standard path, or else dh_shlibdeps gets confused
chrpath -d .pybuild/pythonX.Y_*/build/petsc4py/lib/PETSc*.so
open: No such file or directory
elf_open: Invalid argument
make[1]: *** [debian/rules:39: override_dh_auto_build] Error 1

Bug#893651: isso FTBFS with node-almond 0.3.3+dfsg-1

[Adrian Bunk]

Source: isso
Version: 0.10.6+git20170928+dfsg-1
Severity: serious

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

...
mkdir -p man/man1/ man/man5
mv man/isso.1 man/man1/isso.1
mv man/isso.conf.5 man/man5/isso.conf.5
node /usr/lib/nodejs/requirejs/r.js -o isso/js/build.embed.js 
out=isso/js/embed.min.js
Error: Error: ERROR: module path does not exist: /usr/lib/nodejs/almond.js for 
module named: /usr/lib/nodejs/almond.js. Path is relative to: 
/build/1st/isso-0.10.6+git20170928+dfsg
at /usr/lib/nodejs/requirejs/r.js:25979:35

make[2]: *** [Makefile:42: isso/js/embed.min.js] Error 1

Bug#877457: stretch update for trafficserver

[Adrian Bunk]

On Fri, Mar 16, 2018 at 02:47:42PM +0100, Jean Baptiste Favre wrote:
> Hello Adrian,

Hello Jean,

> I'd love to fix  it for Stretch.

thanks!

> But, I'm only a Debian Maintainer and I'm not sure I've upload rights.

Your upload rights also work for uploads to (old)stable
(and this is nothing that would go through NEW).

> Besides, I don't know the exact procedure I'll have to follow to
> propagate such fixes to stable (but I'm eager to learn it :) )

https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable

> Cheers,
> Jean Baptiste

cu
Adrian

> On 14/03/2018 18:58, Adrian Bunk wrote:
> > On Wed, Jan 17, 2018 at 09:42:09AM +, Debian Bug Tracking System wrote:
> >> ...
> >>  trafficserver (7.1.1-1) unstable; urgency=medium
> >>  .
> >>* Fix trafficserver-dev dependencies. (Closes: #877457)
> >> ...
> > 
> > Thanks a lot for fixing this bug for unstable.
> > 
> > It is still present in stretch, could you also fix it there?
> > Alternatively, I can fix it for stretch if you don't object.
> > 
> > Thanks
> > Adrian
> > 

Bug#893649: xvt: should this package be removed?

[Adam Borowski]

Package: xvt
Version: 2.1-20.3
Severity: serious
Justification: QA query

Hi!
I believe that xvt is no longer suitable for inclusion in Debian, and thus
propose its removal.  Not only has it been dead upstream since times
immemorial but also it lacks features so basic it's mind-boggling.

For example, I believed that Windows 3.11's TELNET.EXE was the last terminal
in existence that lacked color support.  Turns out, here we ship xvt, in
2018.  Or, no UTF-8 support is probably worth a RC bug on its own.

More than two decades ago, xvt was superseded by its fork rxvt, which in
turn spawned a multitude of forks on its own.  I for one remember using a
bunch of them on IRIX, when the world was still young...  Those forks have
then died out around the beginning of this millenium, of them only
rxvt-unicode is still struggling along.

As this package is still nominally maintained (well, your last upload was in
2006...), I can't file a RoQA immediately.  Thus, please tell me whether it
should be removed.  If not, please close this bug, otherwise I'll ask for
removal before Buster freeze.


Meow!
-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.0-rc6-debug-00033-g80c3264499c7 (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages xvt depends on:
ii  libc6 2.27-2
ii  libx11-6  2:1.6.5-1

xvt recommends no packages.

Versions of packages xvt suggests:
pn  menu  

-- no debconf information

Bug#890633: Bug #890633 in caps marked as pending

[fsateler]

Control: tag -1 pending

Hello,

Bug #890633 in caps 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/multimedia-team/caps/commit/a411203d6390456a2ea62e1628528fb6b6c1e72a


Use standard exp10f instead of pow10f

Thanks to Aurelien Jarno for the patch.

Closes: #890633



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/890633

Processed: Bug #890633 in caps marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #890633 [caps] caps: FTBFS with glibc 2.27: error: 'pow10f' was not 
declared in this scope
Added tag(s) pending.

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

Bug#881358: breaks compatibility with libva1

[Jamon Terrell]

You're right, I'm mistaken.  I suppose that was manually installed during
my troubleshooting as well. Sorry about that.

That aside, though--while it was a manual install, libva1 does work
side-by-side with libva2, but vdpau-va-driver does not.

It would be incredibly nice if one could run both side-by-side without
hacking their way outside of the debian package management world.  Is this
something that any thought has been given to?  I guess snap/flatpak/etc is
the "future" debian solution to this problem, though?  Do you have other
suggestions for better ways of supporting users who would like to be able
to run apps that haven't spent the time necessary to chase the latest
breaking changes in each new release?

On Tue, Mar 20, 2018 at 3:30 PM Sebastian Ramacher 
wrote:

> On 2018-03-20 19:46:14, Jamon Terrell wrote:
> > Not all applications have been updated to work with libva2, and debian
> > unstable does allow installation of libva1 and libva2 concurrently, but
> > this doesn't work for vdpau because vdpau-va-driver 0.7.4-6 only works
> with
> > libva1 and vdpau-va-driver 0.7.4-7 only works with libva2.  This forces
> > users who want libva1 support to manually install the older version of
> > vdpau-va-driver, and doesn't allow concurrent use of both.
>
> I'm not sure how you come to the conclusion that one is still able to
> install
> libva1 in unstable. It was removed long time ago. Also, all users of libva
> in
> Debian have migrated to libva2.
>
> Cheers
> --
> Sebastian Ramacher
>

Bug#893647: kterm: should this package be removed?

[Adam Borowski]

Package: kterm
Version: 6.2.0-46.2
Severity: serious
Justification: QA query


Hi!
I believe that kterm is no longer suitable for inclusion in Debian, and thus
propose its removal.  It lacks features considered basic for a terminal
emulator, such as UTF-8 support; its compatibility with terminal abilities
taken for granted these days is poor, and it has been dead upstream since
times immemorial (predating the first Debian version in 1996).

As the package is at least nominally maintained (well, no maintainer upload
since 2006...), I'm not supposed to RoQA it immediately.  Thus, please tell
me whether it should be removed.  If not, please close this bug, otherwise
I'll ask for removal before Buster freeze.


Meow!
-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.0-rc6-debug-00033-g80c3264499c7 (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages kterm depends on:
ii  libc6 2.27-2
ii  libtinfo5 6.1-1
ii  libx11-6  2:1.6.5-1
ii  libxaw7   2:1.0.13-1+b2
ii  libxmu6   2:1.1.2-2
ii  libxt61:1.1.5-1
ii  ncurses-term  6.1-1

Versions of packages kterm recommends:
ii  locales  2.27-2

Versions of packages kterm suggests:
pn  xfonts-shinonome | xfonts-a12k12  

-- no debconf information

Bug#893218: marked as done (jackson-datatype-joda FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 21:12:34 +
with message-id 
and subject line Bug#893218: fixed in jackson-datatype-joda 2.9.4-2
has caused the Debian Bug report #893218,
regarding jackson-datatype-joda FTBFS with openjdk-9
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.)


-- 
893218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jackson-datatype-joda
Version: 2.9.4-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jackson-datatype-joda.html

...
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running com.fasterxml.jackson.datatype.joda.JodaMapperTest
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.269 s 
- in com.fasterxml.jackson.datatype.joda.JodaMapperTest
[INFO] Running com.fasterxml.jackson.datatype.joda.TestVersions
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.204 s 
- in com.fasterxml.jackson.datatype.joda.TestVersions
[INFO] Running com.fasterxml.jackson.datatype.joda.IntervalSerializationTest
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.214 s 
- in com.fasterxml.jackson.datatype.joda.IntervalSerializationTest
[INFO] Running com.fasterxml.jackson.datatype.joda.DateTimeTest
[ERROR] Tests run: 10, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.605 
s <<< FAILURE! - in com.fasterxml.jackson.datatype.joda.DateTimeTest
[ERROR] 
testCustomPatternStyle(com.fasterxml.jackson.datatype.joda.DateTimeTest)  Time 
elapsed: 1.256 s  <<< FAILURE!
junit.framework.ComparisonFailure: expected:<{"date":"1/1/70[] 12:00 AM"}> but 
was:<{"date":"1/1/70[,] 12:00 AM"}>
at 
com.fasterxml.jackson.datatype.joda.DateTimeTest.testCustomPatternStyle(DateTimeTest.java:126)

[INFO] Running com.fasterxml.jackson.datatype.joda.TimeZoneTest
[INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.026 s 
- in com.fasterxml.jackson.datatype.joda.TimeZoneTest
[INFO] Running com.fasterxml.jackson.datatype.joda.ser.JodaSerializationTest
[INFO] Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.553 s 
- in com.fasterxml.jackson.datatype.joda.ser.JodaSerializationTest
[INFO] Running com.fasterxml.jackson.datatype.joda.ser.WriteZoneIdTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in 
com.fasterxml.jackson.datatype.joda.ser.WriteZoneIdTest
[INFO] Running com.fasterxml.jackson.datatype.joda.DateMidnightTest
[INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.32 s - 
in com.fasterxml.jackson.datatype.joda.DateMidnightTest
[INFO] Running com.fasterxml.jackson.datatype.joda.MixedListTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.859 s 
- in com.fasterxml.jackson.datatype.joda.MixedListTest
[INFO] Running 
com.fasterxml.jackson.datatype.joda.deser.DurationDeserializationTest
[INFO] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.211 s 
- in com.fasterxml.jackson.datatype.joda.deser.DurationDeserializationTest
[INFO] Running com.fasterxml.jackson.datatype.joda.deser.LocalTimeDeserTest
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.2 s - 
in com.fasterxml.jackson.datatype.joda.deser.LocalTimeDeserTest
[INFO] Running com.fasterxml.jackson.datatype.joda.deser.IntervalDeserTest
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s 
- in com.fasterxml.jackson.datatype.joda.deser.IntervalDeserTest
[INFO] Running com.fasterxml.jackson.datatype.joda.deser.YearMonthDeserTest
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.092 s 
- in com.fasterxml.jackson.datatype.joda.deser.YearMonthDeserTest
[INFO] Running com.fasterxml.jackson.datatype.joda.deser.LocalDateTimeDeserTest
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.329 s 
- in com.fasterxml.jackson.datatype.joda.deser.LocalDateTimeDeserTest
[INFO] Running 
com.fasterxml.jackson.datatype.joda.deser.PeriodDeserializationTest
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s 
- in com.fasterxml.jackson.datatype.joda.deser.PeriodDeserializationTest
[INFO] Running com.fasterxml.jackson.datatype.joda.deser.LocalDateDeserTest
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.068 s 
- in com.fasterxml.jackson.datatype.joda.deser.LocalDateDeserTest
[INFO] Running 

Bug#892760: marked as done (antlr3: FTBFS with Java 9)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 21:06:23 +
with message-id 
and subject line Bug#892760: fixed in antlr3 3.5.2-9
has caused the Debian Bug report #892760,
regarding antlr3: FTBFS with Java 9
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.)


-- 
892760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: antlr3
Version: 3.5.2-8
Severity: normal
User: debian-j...@lists.debian.org
Usertags: default-java9

antlr3 fails to build with Java 9:

[INFO] 
[INFO] Reactor Summary:
[INFO]
[INFO] ANTLR 3 Master build control POM ... SUCCESS [  0.570 s]
[INFO] ANTLR 3 Runtime  SUCCESS [  4.100 s]
[INFO] ANTLR 3 Tool ... SUCCESS [  6.755 s]
[INFO] ANTLR 3 Maven plugin ... SUCCESS [  1.580 s]
[INFO] ANTLR 3 gUnit .. FAILURE [  1.392 s]
[INFO] ANTLR 3 gUnit Maven plugin . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 14.708 s
[INFO] Finished at: 2018-03-12T17:41:21+01:00
[INFO] Final Memory: 12M/42M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (default-cli) on 
project gunit: MavenReportException: Error while generating Javadoc:
[ERROR] Exit code: 1 - 
./antlr3/gunit/src/main/java/org/antlr/gunit/swingui/model/TestSuiteFactory.java:30:
 error: package org.antlr.gunit.swingui.parsers does not exist
[ERROR] import org.antlr.gunit.swingui.parsers.ANTLRv3Lexer;
[ERROR]   ^
[ERROR] 
./antlr3/gunit/src/main/java/org/antlr/gunit/swingui/model/TestSuiteFactory.java:31:
 error: package org.antlr.gunit.swingui.parsers does not exist
[ERROR] import org.antlr.gunit.swingui.parsers.ANTLRv3Parser;
[ERROR]   ^
[ERROR] 
./antlr3/gunit/src/main/java/org/antlr/gunit/swingui/model/TestSuiteFactory.java:32:
 error: package org.antlr.gunit.swingui.parsers does not exist
[ERROR] import org.antlr.gunit.swingui.parsers.StGUnitLexer;
[ERROR]   ^
[ERROR] 
./antlr3/gunit/src/main/java/org/antlr/gunit/swingui/model/TestSuiteFactory.java:33:
 error: package org.antlr.gunit.swingui.parsers does not exist
[ERROR] import org.antlr.gunit.swingui.parsers.StGUnitParser;
[ERROR]   ^
[ERROR]
[ERROR] Command line was: /usr/lib/jvm/java-9-openjdk-amd64/bin/javadoc 
@options @packages
[ERROR]
[ERROR] Refer to the generated Javadoc files in './antlr3/gunit/target/apidocs' 
dir.
--- End Message ---
--- Begin Message ---
Source: antlr3
Source-Version: 3.5.2-9

We believe that the bug you reported is fixed in the latest version of
antlr3, 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 892...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated antlr3 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: Tue, 20 Mar 2018 21:34:54 +0100
Source: antlr3
Binary: antlr3 antlr3-doc antlr3-maven-plugin libantlr3-runtime-java 
libantlr3-gunit-java libantlr3-gunit-java-doc antlr3-gunit-maven-plugin
Architecture: source
Version: 3.5.2-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 antlr3 - language tool for constructing recognizers, compilers etc
 antlr3-doc - language tool for constructing compilers etc - documentation
 antlr3-gunit-maven-plugin - Maven plugin for gUnit, a unit test framework for 
ANTLR grammars
 antlr3-maven-plugin - Maven plugin for ANTLR 3
 libantlr3-gunit-java - Unit Test framework for ANTLR 

Bug#893645: os-autoinst: FTBFS: FAIL: 02-test_ocr.t

[Steve Langasek]

Source: os-autoinst
Version: 4.4.1508936943.39adc5eb-2
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic

In addition to bug #880791, os-autoinst now fails to build with a second
test failure:

[...]
FAIL: 02-test_ocr.t
===

Use of uninitialized value in index at ../needle.pm line 44.
Use of uninitialized value $bmwqemu::vars{"PRJDIR"} in addition (+) at 
../needle.pm line 45.
20:27:15.8564 433 MATCH(bootmenu-ocr.ref:1.00)
Tesseract Open Source OCR Engine v4.00.00alpha with Leptonica
Warning. Invalid resolution 0 dpi. Using 70 instead.
Estimating resolution as 132
Tesseract Open Source OCR Engine v4.00.00alpha with Leptonica
Warning. Invalid resolution 0 dpi. Using 70 instead.
Estimating resolution as 138
ok 1 - ocr match 1
Tesseract Open Source OCR Engine v4.00.00alpha with Leptonica
Warning. Invalid resolution 0 dpi. Using 70 instead.
Estimating resolution as 132
Tesseract Open Source OCR Engine v4.00.00alpha with Leptonica
Warning. Invalid resolution 0 dpi. Using 70 instead.
Estimating resolution as 138
not ok 2 - multiple OCR regions
#   Failed test 'multiple OCR regions'
#   at ./02-test_ocr.t line 42.
1..2
# Looks like you failed 1 test of 2.
FAIL 02-test_ocr.t (exit status: 1)
[...]

First seen in Ubuntu at
,
this failure is also reproducible in unstable.

Perhaps this is a regression in, or incompatibility with, tesseract-ocr
4.00.  (The last successful builds of os-autoinst in Debian used
tesseract-ocr 3.04.01-6.)

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#892760: Pending fixes for bugs in the antlr3 package

[pkg-java-maintainers]

tag 892760 + pending
thanks

Some bugs in the antlr3 package are closed in revision
1db6ad90371aab09110b44ce94b6c2ad3b3043f8 in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/antlr3.git/commit/?id=1db6ad9

Commit message:

Fix FTBFS with Java 9.

Thanks: Tiago Stürmer Daitx for the patch.
Closes: #892760

Processed: Pending fixes for bugs in the antlr3 package

[Debian Bug Tracking System]

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

> tag 892760 + pending
Bug #892760 [antlr3] antlr3: FTBFS with Java 9
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#880886: maven-bundle-plugin FTBFS with libmaven-dependency-tree-java

[Emmanuel Bourg]

On 20/03/2018 16:29, 殷啟聰 | Kai-Chung Yan wrote:
> I adopted the patch from Fedora and it looks good. The package builds fine 
> now and 154 of its reverse-build-dependencies built successfully. 27 failed:

Great!


> They either failed in compilation due to Java 9 or failed in tests. But I 
> would say the result is confident enough to prove that the patch works.

I agree. An error in this plugin would have broken the build before the
test phase.


> However this package fails to build in Sid currently because of Java 9. I 
> attached the log. The Maven Javadoc Plugin failed to honor the compile 
> classpath.

The javadoc is useless for Maven plugins anyway, nobody codes against
their API. I suggest removing it.

Emmanuel Bourg

Bug#881358: breaks compatibility with libva1

[Sebastian Ramacher]

On 2018-03-20 19:46:14, Jamon Terrell wrote:
> Not all applications have been updated to work with libva2, and debian
> unstable does allow installation of libva1 and libva2 concurrently, but
> this doesn't work for vdpau because vdpau-va-driver 0.7.4-6 only works with
> libva1 and vdpau-va-driver 0.7.4-7 only works with libva2.  This forces
> users who want libva1 support to manually install the older version of
> vdpau-va-driver, and doesn't allow concurrent use of both.

I'm not sure how you come to the conclusion that one is still able to install
libva1 in unstable. It was removed long time ago. Also, all users of libva in
Debian have migrated to libva2.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: Pending fixes for bugs in the jackson-datatype-joda package

[Debian Bug Tracking System]

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

> tag 893218 + pending
Bug #893218 [src:jackson-datatype-joda] jackson-datatype-joda FTBFS with 
openjdk-9
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#893218: Pending fixes for bugs in the jackson-datatype-joda package

[pkg-java-maintainers]

tag 893218 + pending
thanks

Some bugs in the jackson-datatype-joda package are closed in revision
66e01c619a2cbed627ad19368ba982d1f10ad5ac in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/jackson-datatype-joda.git/commit/?id=66e01c6

Commit message:

Fix FTBFS with Java9

Closes: #893218

Bug#893472: libfurl-perl: broken on s390x?

[Niko Tyni]

On Tue, Mar 20, 2018 at 10:02:34AM +0100, Jonas Smedegaard wrote:

> I believe circular build-dependencies for testsuite needs can - and 
> should be addressed by marking such build-dependencies appropriately, 
> rather than skipping them - for exactly situations like this.

Sure.
 
> Question then what the appropriate way to express cycle-breaking 
> hints... :-)

I believe the way to express this is to annotate the build dependency
with . (Though build cycles are probably not much of a deal
with arch:all packages in the first place.)
-- 
Niko

Processed: Re: Bug#893472: libfurl-perl: broken on s390x?

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libplack-middleware-deflater-perl: broken on big endian hosts
Bug #893472 [src:libfurl-perl] libfurl-perl: broken on s390x?
Changed Bug title to 'libplack-middleware-deflater-perl: broken on big endian 
hosts' from 'libfurl-perl: broken on s390x?'.
> reassign -1 libplack-middleware-deflater-perl 0.12-1
Bug #893472 [src:libfurl-perl] libplack-middleware-deflater-perl: broken on big 
endian hosts
Bug reassigned from package 'src:libfurl-perl' to 
'libplack-middleware-deflater-perl'.
No longer marked as found in versions libfurl-perl/3.13-1.
Ignoring request to alter fixed versions of bug #893472 to the same values 
previously set
Bug #893472 [libplack-middleware-deflater-perl] 
libplack-middleware-deflater-perl: broken on big endian hosts
Marked as found in versions libplack-middleware-deflater-perl/0.12-1.
> tag -1 patch
Bug #893472 [libplack-middleware-deflater-perl] 
libplack-middleware-deflater-perl: broken on big endian hosts
Added tag(s) patch.
> affects -1 libfurl-perl
Bug #893472 [libplack-middleware-deflater-perl] 
libplack-middleware-deflater-perl: broken on big endian hosts
Added indication that 893472 affects libfurl-perl

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

Bug#893472: libfurl-perl: broken on s390x?

[Niko Tyni]

Control: retitle -1 libplack-middleware-deflater-perl: broken on big endian 
hosts
Control: reassign -1 libplack-middleware-deflater-perl 0.12-1
Control: tag -1 patch
Control: affects -1 libfurl-perl

On Mon, Mar 19, 2018 at 09:35:03PM +0200, Niko Tyni wrote:

> I got as far as seeing that removing line 144 in Deflater.pm
> 
>  
> https://sources.debian.org/src/libplack-middleware-deflater-perl/0.12-1/lib/Plack/Middleware/Deflater.pm/#L144
> 
> -   $buf .= pack("LL", $self->{crc},$self->{length}) if $self->{encoding} 
> eq 'gzip';
> 
> makes both test suites pass, but that doesn't seem like a fully
> satisfactory patch. (And no, s/LL/NN/ doesn't fix it.)

Hum, this is somewhat embarrassing. s/LL/VV/ does seem to fix it, which
makes sense as L and N are equivalent on big-endian while L and V are
equivalent on little-endian. I blame lack of sleep.

Also, RFC 1952 says

  All multi-byte numbers in the format described here are stored
  with the least-significant byte first (at the lower memory address).

so little endian seems to be correct.

Lightly tested patch attached; reassigning.
-- 
Niko
>From 480e68c781ddad1e5a19446c13134c8fde2a34e8 Mon Sep 17 00:00:00 2001
From: Niko Tyni 
Date: Tue, 20 Mar 2018 21:51:49 +0200
Subject: [PATCH] Fix gzip trailer on big endian hosts

These values need to be stored as little endian regardless
of the host endianness.

Bug-Debian: https://bugs.debian.org/893472
---
 lib/Plack/Middleware/Deflater.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/Plack/Middleware/Deflater.pm b/lib/Plack/Middleware/Deflater.pm
index 4cb0b03..c823c38 100644
--- a/lib/Plack/Middleware/Deflater.pm
+++ b/lib/Plack/Middleware/Deflater.pm
@@ -141,7 +141,7 @@ sub print : method {
 if ( !$self->{header} && $self->{encoding} eq 'gzip' ) {
 $buf = pack("nccVcc",GZIP_MAGIC,Z_DEFLATED,0,time(),0,$Compress::Raw::Zlib::gzip_os_code) . $buf
 }
-$buf .= pack("LL", $self->{crc},$self->{length}) if $self->{encoding} eq 'gzip';
+$buf .= pack("VV", $self->{crc},$self->{length}) if $self->{encoding} eq 'gzip';
 $self->{closed} = 1;
 return $buf;
 }
-- 
2.16.2

Processed: reassign 893242 to src:python-pygit2

[Debian Bug Tracking System]

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

> reassign 893242 src:python-pygit2 0.26.2-2
Bug #893242 [python-pygit2] python-pygit2 FTBFS with dh-python 3.20180313
Bug reassigned from package 'python-pygit2' to 'src:python-pygit2'.
No longer marked as found in versions python-pygit2/0.26.2-2.
Ignoring request to alter fixed versions of bug #893242 to the same values 
previously set
Bug #893242 [src:python-pygit2] python-pygit2 FTBFS with dh-python 3.20180313
Marked as found in versions python-pygit2/0.26.2-2.
> thanks
Stopping processing here.

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

Bug#893637: pyraf FTBFS with dh-python 3.20180313

[Adrian Bunk]

Source: pyraf
Version: 2.1.14+dfsg
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/pyraf-2.1.14+dfsg'
HOME=/tmp/ PYTHONPATH=/build/1st/pyraf-2.1.14+dfsg/.pybuild/pythonX.Y_2.7/build 
python2.7 debian/tests/pyraf-test.py
Traceback (most recent call last):
  File "debian/tests/pyraf-test.py", line 18, in 
from pyraf import iraf
ImportError: No module named pyraf
make[1]: *** [debian/rules:12: test-python2.7] Error 1


See #893242 for background.

Processed: Re: Bug#893242: python-pygit2 FTBFS with dh-python 3.20180313

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python-pygit2 0.26.2-2
Bug #893242 [dh-python] python-pygit2 FTBFS with dh-python 3.20180313
Bug reassigned from package 'dh-python' to 'python-pygit2'.
No longer marked as found in versions dh-python/3.20180313.
Ignoring request to alter fixed versions of bug #893242 to the same values 
previously set
Bug #893242 [python-pygit2] python-pygit2 FTBFS with dh-python 3.20180313
Marked as found in versions python-pygit2/0.26.2-2.
> severity -1 serious
Bug #893242 [python-pygit2] python-pygit2 FTBFS with dh-python 3.20180313
Severity set to 'serious' from 'normal'
> tags -1 - wontfix
Bug #893242 [python-pygit2] python-pygit2 FTBFS with dh-python 3.20180313
Removed tag(s) wontfix.

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

Bug#881358: breaks compatibility with libva1

[Jamon Terrell]

Not all applications have been updated to work with libva2, and debian
unstable does allow installation of libva1 and libva2 concurrently, but
this doesn't work for vdpau because vdpau-va-driver 0.7.4-6 only works with
libva1 and vdpau-va-driver 0.7.4-7 only works with libva2.  This forces
users who want libva1 support to manually install the older version of
vdpau-va-driver, and doesn't allow concurrent use of both.

Processed: tagging 891293

[Debian Bug Tracking System]

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

> tags 891293 + fixed-upstream
Bug #891293 [trinity] trinity: FTBFS with glibc 2.27: error: static declaration 
of 'memfd_create' follows non-static declaration
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#893246: marked as done (trove-dashboard: Cannot fulfill the build dependencies)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 21:11:57 +0200
with message-id <20180320191157.GV9516@localhost>
and subject line Fixed in 10.0.0-1
has caused the Debian Bug report #893246,
regarding trove-dashboard: Cannot fulfill the build dependencies
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.)


-- 
893246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trove-dashboard
Version: 7.0.0-3
Severity: serious
Tags: buster sid

 builddeps:trove-dashboard : Depends: python-django-openstack-auth (>= 2.0.0) 
but it is not going to be installed

This is dues to the OpenStack Python 2 -> 3.
--- End Message ---
--- Begin Message ---
Version: 10.0.0-1

This is fixed in trove-dashboard 10.0.0-1, currently in NEW.

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--- End Message ---

Bug#890672: x42-plugins: diff for NMU version 20170428-1.1

[Adrian Bunk]

Control: tags 890672 + pending

Dear maintainer,

I've prepared an NMU for x42-plugins (versioned as 20170428-1.1) and 
uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

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

diff -Nru x42-plugins-20170428/debian/changelog x42-plugins-20170428/debian/changelog
--- x42-plugins-20170428/debian/changelog	2017-06-26 00:32:24.0 +0300
+++ x42-plugins-20170428/debian/changelog	2018-03-20 20:30:37.0 +0200
@@ -1,3 +1,11 @@
+x42-plugins (20170428-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch from Aurelien Jarno to fix FTBFS with glibc 2.27.
+(Closes: #890672)
+
+ -- Adrian Bunk   Tue, 20 Mar 2018 20:30:37 +0200
+
 x42-plugins (20170428-1) unstable; urgency=medium
 
   * New upstream version 20170428
diff -Nru x42-plugins-20170428/debian/patches/pow10f.patch x42-plugins-20170428/debian/patches/pow10f.patch
--- x42-plugins-20170428/debian/patches/pow10f.patch	1970-01-01 02:00:00.0 +0200
+++ x42-plugins-20170428/debian/patches/pow10f.patch	2018-03-20 20:30:34.0 +0200
@@ -0,0 +1,15 @@
+Description: Replace deprecated pow10f by exp10f.
+Author: Aurelien Jarno 
+Forwarded: no
+
+--- x42-plugins-20170428.orig/meters.lv2/gui/phasewheel.c
 x42-plugins-20170428/meters.lv2/gui/phasewheel.c
+@@ -812,7 +812,7 @@ static bool cb_set_gain (RobWidget* hand
+ 		queue_draw(ui->m2);
+ 	}
+ #ifdef __USE_GNU
+-	const float thresh = pow10f(.05 * (MIN_CUTOFF - val));
++	const float thresh = exp10f(.05 * (MIN_CUTOFF - val));
+ #else
+ 	const float thresh = powf(10, .05 * (MIN_CUTOFF - val));
+ #endif
diff -Nru x42-plugins-20170428/debian/patches/series x42-plugins-20170428/debian/patches/series
--- x42-plugins-20170428/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ x42-plugins-20170428/debian/patches/series	2018-03-20 20:30:34.0 +0200
@@ -0,0 +1 @@
+pow10f.patch

Processed: x42-plugins: diff for NMU version 20170428-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 890672 + pending
Bug #890672 [x42-plugins] x42-plugins: FTBFS with glibc 2.27: error: 'pow10f' 
was not declared in this scope
Added tag(s) pending.

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

Bug#893627: apscheduler: unsatisfiable build-dependency: python3-trollius removed

[Adrian Bunk]

On Tue, Mar 20, 2018 at 09:51:04AM -0700, Steve Langasek wrote: KK> 
>... 
> The linked bug shows that python-trollius is not compatible with python3.6.
> Dropping support for python3 and stranding its users on the legacy python2
> is surely questionable,

https://github.com/vstinner/trollius

Warning

The Trollius project is deprecated since the release 2.1.! Use asyncio 
on Python 3 instead.

> but the net effect is that apscheduler has
> non-releasable build-dependencies.
>...

The build dependency on python3-trollius is incorrect and should be removed:
https://sources.debian.org/src/apscheduler/3.4.0-2/setup.py/#L44

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

Processed: add polarssl to mbedtls cve bugs

[Debian Bug Tracking System]

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

> found 890287 polarssl/1.2.8-1
Bug #890287 {Done: James Cowgill } [src:mbedtls] mbedtls: 
CVE-2018-0488 - Risk of remote code execution when truncated HMAC is enabled
Marked as found in versions polarssl/1.2.8-1.
> found 890288 polarssl/1.2.8-1
Bug #890288 {Done: James Cowgill } [src:mbedtls] mbedtls: 
CVE-2018-0487 - Risk of remote code execution when verifying RSASSA-PSS 
signatures
Marked as found in versions polarssl/1.2.8-1.
> thanks
Stopping processing here.

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

Bug#893509: marked as done (petsc: FTBFS with make 4.1)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 17:53:56 +
with message-id 
and subject line Bug#893509: fixed in petsc 3.8.3+dfsg1-7
has caused the Debian Bug report #893509,
regarding petsc: FTBFS with make 4.1
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.)


-- 
893509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: petsc
Version: 3.8.3+dfsg1-6
Severity: serious
Tags: sid buster

Hi,

petsc FTBFS with this error on the architectures with make 4.1 (others
have make 4.2.1):
> dh_auto_build -plibpetsc-real3.8-dbg -ppetsc3.8-doc --  \
>   PETSC_DIR=/<>/petsc-3.8.3+dfsg1 
> PETSC_ARCH=i386-linux-gnu-real-debug \
>   CFLAGS="-fdebug-prefix-map=/<>/petsc-3.8.3+dfsg1=." 
> CXXFLAGS="-fdebug-prefix-map=/<>/petsc-3.8.3+dfsg1=." \
>   FCFLAGS="-fdebug-prefix-map=/<>/petsc-3.8.3+dfsg1=."  
> FFLAGS="-fdebug-prefix-map=/<>/petsc-3.8.3+dfsg1=."
>   make -j4 -O PETSC_DIR=/<>/petsc-3.8.3\+dfsg1 
> PETSC_ARCH=i386-linux-gnu-real-debug 
> CFLAGS=-fdebug-prefix-map=/<>/petsc-3.8.3\+dfsg1=. 
> CXXFLAGS=-fdebug-prefix-map=/<>/petsc-3.8.3\+dfsg1=. 
> FCFLAGS=-fdebug-prefix-map=/<>/petsc-3.8.3\+dfsg1=. 
> FFLAGS=-fdebug-prefix-map=/<>/petsc-3.8.3\+dfsg1=.
> make[2]: Entering directory '/<>/petsc-3.8.3+dfsg1'
> * ERROR **
> PETSc toplevel makefile does not support -j option.
> Instead - use: "make MAKE_NP=". Current value of MAKE_NP is 4.
> **
> /<>/petsc-3.8.3+dfsg1/lib/petsc/conf/rules:19: recipe for target 
> 'chk_makej' failed
> make[2]: *** [chk_makej] Error 1

On the architectures with make 4.2.1, the build succeeds incorrectly (at
least according to the intention of the -jX check). This happens because
the check in lib/petsc/conf/rules checks for " -j " (with spaces) in
MAKEFLAGS. In make 4.2.1 the behavior was changed to include the number
of parallel jobs in MAKEFLAGS which causes this test to never report a
parallel build.

I think you either need to use -j1, or remove the upstream -jX check if
it is invalid for some reason.

James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: petsc
Source-Version: 3.8.3+dfsg1-7

We believe that the bug you reported is fixed in the latest version of
petsc, 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 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated petsc 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: Wed, 21 Mar 2018 00:59:49 +0800
Source: petsc
Binary: libpetsc-real3.8-dev petsc-dev libpetsc-real3.8 libpetsc-real3.8-dbg 
petsc3.8-doc libpetsc-complex3.8-dev libpetsc-complex3.8 libpetsc-complex3.8-dbg
Architecture: source
Version: 3.8.3+dfsg1-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Description:
 libpetsc-complex3.8 - Shared libraries for version 3.8 of PETSc with Complex 
Numbers
 libpetsc-complex3.8-dbg - Debugging libraries for PETSc
 libpetsc-complex3.8-dev - Static libraries, shared links, header files for 
PETSc
 libpetsc-real3.8 - Shared libraries for version 3.8 of PETSc
 libpetsc-real3.8-dbg - Debugging libraries for PETSc
 libpetsc-real3.8-dev - Static libraries, shared links, header files for PETSc
 petsc-dev  - Virtual package depending on latest PETSc development package
 petsc3.8-doc - Documentation and examples for PETSc
Closes: 893509
Changes:
 petsc (3.8.3+dfsg1-7) unstable; urgency=medium
 .
   * debian patch make_parallel_f88a919.patch, adapted from upstream
 merge f88a919 to facilitate parallel builds. Closes: #893509.
Checksums-Sha1:
 e55e041f0aaa7f8d9958c8b863219f0bd1e3f116 2984 petsc_3.8.3+dfsg1-7.dsc
 5cb5c4cd020fc11e1e73c442f6c51e1636613e1f 40540 
petsc_3.8.3+dfsg1-7.debian.tar.xz
Checksums-Sha256:
 20d5733e5bfb53ec86fc9548d21b0b5543d97fce9a7d56f559fd788ef478b0aa 2984 

Bug#880795: marked as done (rakudo: t/02-rakudo/repl.t frequently fails)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 17:54:05 +
with message-id 
and subject line Bug#880795: fixed in rakudo 2018.02.1-3
has caused the Debian Bug report #880795,
regarding rakudo: t/02-rakudo/repl.t frequently fails
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.)


-- 
880795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rakudo
Version: 2017.10-1
Severity: serious

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

...
t/02-rakudo/repl.t .. 
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/39 subtests 
(less 3 skipped subtests: 35 okay)
t/05-messages/01-errors.t ... ok

Test Summary Report
---
t/02-rakudo/repl.t(Wstat: 256 Tests: 39 Failed: 1)
  Failed test:  34
  Non-zero exit status: 1
Files=67, Tests=839, 380 wallclock secs ( 1.20 usr  0.27 sys + 865.60 cusr 
434.20 csys = 1301.27 CPU)
Result: FAIL
Makefile:568: recipe for target 'm-coretest5' failed
make[1]: *** [m-coretest5] Error 1
--- End Message ---
--- Begin Message ---
Source: rakudo
Source-Version: 2018.02.1-3

We believe that the bug you reported is fixed in the latest version of
rakudo, 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 880...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dominique Dumont  (supplier of updated rakudo 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: Tue, 20 Mar 2018 18:24:29 +0100
Source: rakudo
Binary: rakudo
Architecture: source
Version: 2018.02.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Rakudo Maintainers 
Changed-By: Dominique Dumont 
Description:
 rakudo - Perl 6 implementation on top of Moar virtual machine
Closes: 880795
Changes:
 rakudo (2018.02.1-3) unstable; urgency=medium
 .
   * rules: run tests one at a time
   * patch repl test (Closes: #880795)
Checksums-Sha1:
 7b6dd14343fa2d42121476a2d0afb58f1751387c 2366 rakudo_2018.02.1-3.dsc
 93a7dfb2e27d529d0e28ddb76bd18ce38798a24a 13652 rakudo_2018.02.1-3.debian.tar.xz
 e44bec798f1ba9c1138cb47b18d62bfdb0f8d53a 5738 
rakudo_2018.02.1-3_source.buildinfo
Checksums-Sha256:
 ec8c78a18ef4655144ffc742b5c087f7fdcce505e1488f2026f1bc2479c9ce21 2366 
rakudo_2018.02.1-3.dsc
 28718aff939e5636e3456029d59f14ee574f5481fbdfdf55057bf19ae829cccf 13652 
rakudo_2018.02.1-3.debian.tar.xz
 7241ddeddd27d2a74d3600c4c273a216d1f72fb620486b7de60f245616729131 5738 
rakudo_2018.02.1-3_source.buildinfo
Files:
 6a46e41a624b43c7c04021cfca911be1 2366 interpreters optional 
rakudo_2018.02.1-3.dsc
 a77d3ee9be816fdb74aa1dad8175ac5b 13652 interpreters optional 
rakudo_2018.02.1-3.debian.tar.xz
 0b0d14aeec3ee255a8a5bd1a113e9f33 5738 interpreters optional 
rakudo_2018.02.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn3I5/LZk8Qsz6dwDwx9P2UmrK2wFAlqxRYUACgkQwx9P2Umr
K2yBSw/+PQ9GdpxsymTJi95rtglGvhyE+5EK+IotKsEQmay+Y7Ck2wbl3iIzhVSi
4JcTIgsUaMMSY6WbRVORq/J4jxx6N8qwVPK7fRJGmu7xVc61fW3LMF5Sd6iXCNlw
iS2SPv8iwzPpfscaZCXmQD5M/pf/FoPYC1OxPOUMEqr3iRL9yzGSmLifn3cV/ImG
FaEzgDSl3soFgW/pOEGp9yNbfCJYXbc3s2AfGylLOUyyh746DptZkltPsPK4Ei63
aMLfi/TtM7A9f3OQWwyDhKfdlOvP1jb5LTwDf6hQW53sl0EMwuvM+7d0UfzUlEYn
B6kMVUFqriecFXFq4gZSEPGfzoRJQ1Ly8MxElo8Dc0mHblAIsOwd9Kyd/RIQmLsz
C6cQEn5JGkHBKlD0i2D2ZQIUWKU9xXyFN1o1YwdwyDvmDHclDf2LNFiSypXQ1vEf
V5aRTymTJ/aS2bfv0SdfZAaL91Vj4g+OdpSQ7Jd+ocmL6ijvx+pYC1/NMa8R5iHu
3Xn5JNLk0ytg90SjFWtmgaQReCFVp2day+TV3xao63hfNAEL6MYXk2535UaD4KF8
4bl2vCUxdjTljK5X8WEPph+NNZl66jIr9OjZKixCZvE0OqFYdxPTXQyuD+5mOFfh
l3doK8ViZFPUNGR94vrtS7n62FGe27WvR0grs1UZOLav3PtFMus=
=kdpI
-END PGP SIGNATURE End Message ---

Bug#890634: eq10q: diff for NMU version 2.2~repack0-2.1

[Adrian Bunk]

Control: tags 890634 + pending

Dear maintainer,

I've prepared an NMU for eq10q (versioned as 2.2~repack0-2.1) and 
uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

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

diff -Nru eq10q-2.2~repack0/debian/changelog eq10q-2.2~repack0/debian/changelog
--- eq10q-2.2~repack0/debian/changelog	2016-12-13 16:26:26.0 +0200
+++ eq10q-2.2~repack0/debian/changelog	2018-03-20 19:40:58.0 +0200
@@ -1,3 +1,11 @@
+eq10q (2.2~repack0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch from Aurelien Jarno to fix FTBFS with glibc 2.27.
+(Closes: #890634)
+
+ -- Adrian Bunk   Tue, 20 Mar 2018 19:40:58 +0200
+
 eq10q (2.2~repack0-2) unstable; urgency=medium
 
   * Remove redundant amd64 cflags.
diff -Nru eq10q-2.2~repack0/debian/patches/05-pow10.patch eq10q-2.2~repack0/debian/patches/05-pow10.patch
--- eq10q-2.2~repack0/debian/patches/05-pow10.patch	1970-01-01 02:00:00.0 +0200
+++ eq10q-2.2~repack0/debian/patches/05-pow10.patch	2018-03-20 19:40:58.0 +0200
@@ -0,0 +1,73 @@
+Description: Replace deprecated pow10 by exp10.
+Author: Aurelien Jarno 
+Forwarded: no
+
+--- eq10q-2.2~repack0.orig/gui/widgets/bandctl.cpp
 eq10q-2.2~repack0/gui/widgets/bandctl.cpp
+@@ -949,7 +949,7 @@ bool BandCtl::parseBtnString(BandCtl::Bu
+   if(str_k.length() > 0)
+   {
+ val_k = atof(str_k.c_str()) * 1e3;
+-val *= pow10(3.0 - str.length());
++val *= exp10(3.0 - str.length());
+ if(str.length() > 3)
+ {
+   //throw an error, imposible to match str > 3 with k
+@@ -960,7 +960,7 @@ bool BandCtl::parseBtnString(BandCtl::Bu
+   }
+   if(str_d.length() > 0)
+   {
+-val_d = atof(str_d.c_str())/ pow10((double)str_d.length());
++val_d = atof(str_d.c_str())/ exp10((double)str_d.length());
+   }
+
+   btn->value = val + val_k + val_d;
+--- eq10q-2.2~repack0.orig/gui/widgets/bodeplot.cpp
 eq10q-2.2~repack0/gui/widgets/bodeplot.cpp
+@@ -194,14 +194,14 @@ void PlotEQCurve::resetCenterSpan()
+ {
+   //Compute center and span for the full range spectrum
+   double sp = log10(MAX_FREQ/MIN_FREQ);
+-  double cn = MIN_FREQ * sqrt(pow10(sp));
++  double cn = MIN_FREQ * sqrt(exp10(sp));
+   setCenterSpan(cn, sp);
+ }
+ 
+ void PlotEQCurve::setCenterSpan(double center, double span)
+ { 
+-  m_minFreq = center / sqrt(pow10(span));
+-  m_maxFreq = center * sqrt(pow10(span));
++  m_minFreq = center / sqrt(exp10(span));
++  m_maxFreq = center * sqrt(exp10(span));
+ 
+   //Initalize the grid
+   const double f_grid[GRID_VERTICAL_LINES] = {20.0, 30.0, 40.0, 50.0, 60.0, 70.0, 80.0, 90.0,
+@@ -246,8 +246,8 @@ void PlotEQCurve::setCenter(double cente
+ {
+   //Limit center to the possible range according the current span
+   double sp = log10(m_maxFreq/m_minFreq);
+-  double cmin = MIN_FREQ * sqrt(pow10(sp));
+-  double cmax = MAX_FREQ / sqrt(pow10(sp));
++  double cmin = MIN_FREQ * sqrt(exp10(sp));
++  double cmax = MAX_FREQ / sqrt(exp10(sp));
+   
+   double cn = center;
+   cn = cn > cmax ? cmax : cn;
+@@ -259,7 +259,7 @@ void PlotEQCurve::setSpan(double span)
+ {
+   //Limit center to the possible range according the current span
+   double sp_act = log10(m_maxFreq/m_minFreq);
+-  double cn = m_minFreq * sqrt(pow10(sp_act));
++  double cn = m_minFreq * sqrt(exp10(sp_act));
+   double smax1 = 2.0*log10(cn/MIN_FREQ);
+   double smax2= 2.0*log10(MAX_FREQ/cn);
+   double smax = smax1 < smax2 ? smax1 : smax2;
+@@ -306,7 +306,7 @@ void PlotEQCurve::recomputeCenterFreq(do
+   double fmax = MIN_FREQ*pow((MAX_FREQ/MIN_FREQ),((local_x2 + 3.5)/((double)m_zoom_surface_ptr->get_width(;
+   
+   double sp_act = log10(fmax/fmin);
+-  double cn = fmin * sqrt(pow10(sp_act));
++  double cn = fmin * sqrt(exp10(sp_act));
+   setCenter(cn);
+ }
+ 
diff -Nru eq10q-2.2~repack0/debian/patches/series eq10q-2.2~repack0/debian/patches/series
--- eq10q-2.2~repack0/debian/patches/series	2016-12-13 16:24:56.0 +0200
+++ eq10q-2.2~repack0/debian/patches/series	2018-03-20 19:40:58.0 +0200
@@ -2,3 +2,4 @@
 02-remove_sse_flags.patch
 03-fix_flags.patch
 04-spelling.patch
+05-pow10.patch

Processed: eq10q: diff for NMU version 2.2~repack0-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 890634 + pending
Bug #890634 [eq10q] eq10q: FTBFS with glibc 2.27: error: 'pow10' was not 
declared in this scope
Added tag(s) pending.

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

Processed: fixed 892971 in 1.0.0+dfsg4-4

[Debian Bug Tracking System]

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

> fixed 892971 1.0.0+dfsg4-4
Bug #892971 {Done: Jose Luis Rivero } 
[libignition-fuel-tools1-dev,libignition-fuel-tools1-1] 
libignition-fuel-tools1-{1,dev}: both ship /usr/lib/ruby/ignition/cmdfuel1.rb
Marked as fixed in versions ignition-fuel-tools/1.0.0+dfsg4-4.
> thanks
Stopping processing here.

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

Bug#893627: apscheduler: unsatisfiable build-dependency: python3-trollius removed

[Steve Langasek]

Source: apscheduler
Version: 3.4.0-2
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic

Dear Laszlo,

The latest version of apscheduler has just added a build-dependency on
python{,3}-trollius:

apscheduler (3.4.0-2) unstable; urgency=medium

  * Patch to don't check for SCM source version.
  * Fix test with Python 2.7 (closes: #884107).
  * Add python{,3}-trollius to build depends.
  * Update debhelper level to 11 .
  * Update Standards-Version to 4.1.2 .

But python-trollius has in turn just dropped its python3 support in
unstable:

python-trollius (2.1~b1-5) unstable; urgency=medium

  [ Ondřej Nový ]
  * d/rules: Changed UPSTREAM_GIT protocol to https

  [ Daniel Baumann ]
  * Updating vcs fields.
  * Updating copyright format url.
  * Updating maintainer field.
  * Running wrap-and-sort -bast.
  * Removing gbp.conf, not used anymore or should be specified in the
developers dotfiles.

  [ Thomas Goirand ]
  * Stop building python3-trollius. (Closes: #867771)
  * Updating standards version to 4.1.1.

 -- Thomas Goirand   Tue, 24 Oct 2017 19:54:51 +


The linked bug shows that python-trollius is not compatible with python3.6.
Dropping support for python3 and stranding its users on the legacy python2
is surely questionable, but the net effect is that apscheduler has
non-releasable build-dependencies.

FYI this prevents apscheduler 3.4.0-2 from being included in the upcoming
Ubuntu release.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#893273: bcolz: FTBFS and Debci failure

[Daniel Stender]

A couple of failures like this also with 1.1.2/blosc 1.14.2:


==
FAIL: test01b (bcolz.tests.test_carray.bloscFiltersTest)
Testing all available filters in big arrays (bcolz.defaults)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 2322, in test01b
"carray does not seem to compress at all")
AssertionError: carray does not seem to compress at all

==
FAIL: test01c (bcolz.tests.test_carray.bloscFiltersTest)
Testing all available filters in big arrays (context)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 2344, in test01c
self.assertTrue(bcolz.defaults.cparams['shuffle'] == bcolz.SHUFFLE)
AssertionError: False is not true

==
FAIL: test01b (bcolz.tests.test_carray.filtersDiskTest)
Testing all available filters in big arrays (bcolz.defaults)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 2322, in test01b
"carray does not seem to compress at all")
AssertionError: carray does not seem to compress at all

==
FAIL: test01c (bcolz.tests.test_carray.filtersDiskTest)
Testing all available filters in big arrays (context)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 2344, in test01c
self.assertTrue(bcolz.defaults.cparams['shuffle'] == bcolz.SHUFFLE)
AssertionError: False is not true

==
FAIL: test01a (bcolz.tests.test_carray.filtersMemoryTest)
Testing all available filters in big arrays (setdefaults)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 2302, in test01a
"carray does not seem to compress at all")
AssertionError: carray does not seem to compress at all

==
FAIL: test01b (bcolz.tests.test_carray.filtersMemoryTest)
Testing all available filters in big arrays (bcolz.defaults)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 2322, in test01b
"carray does not seem to compress at all")
AssertionError: carray does not seem to compress at all

==
FAIL: test01c (bcolz.tests.test_carray.filtersMemoryTest)
Testing all available filters in big arrays (context)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 2344, in test01c
self.assertTrue(bcolz.defaults.cparams['shuffle'] == bcolz.SHUFFLE)
AssertionError: False is not true

==
FAIL: test01 (bcolz.tests.test_carray.miscDiskTest)
Testing __sizeof__() (big carrays)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 639, in test01
"carray does not seem to compress at all")
AssertionError: carray does not seem to compress at all

==
FAIL: test01 (bcolz.tests.test_carray.miscMemoryTest)
Testing __sizeof__() (big carrays)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 639, in test01
"carray does not seem to compress at all")
AssertionError: carray does not seem to compress at all

==
FAIL: test_repr_disk_array_append (bcolz.tests.test_carray.reprDiskTest)
--
Traceback (most recent call last):
  File "bcolz/tests/test_carray.py", line 2430, in test_repr_disk_array_append
self.assertEqual(expected, repr(y))
AssertionError: "carray((0,), float64)\n  nbytes := 0; cbytes := 16.00 KB; ratio: 0.00\n  
cparams := cparams(clevel=5, shuffle=1, cname='blosclz', quantize=0)\n  chunklen := 2048; 
chunksize: 16384; blocksize: 0\n  rootdir := '/tmp/bcolz-reprDiskTestDqkqDw'\n  mode:= 
'a'\n[]" != "carray((0,), float64)\n  nbytes := 0; cbytes := 16.00 KB; ratio: 0.00\n  
cparams := cparams(clevel=9, shuffle=0, cname='blosclz', quantize=0)\n  chunklen := 2048; 
chunksize: 16384; blocksize: 0\n  rootdir := 

Bug#893620: Bug #893620 in sphinx marked as pending

[mitya57]

Control: tag -1 pending

Hello,

Bug #893620 in sphinx 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/python-team/modules/sphinx/commit/c89adc1031ab365689bcf22e7f75f094813db5ff


Make python3-sphinx depend on python3-distutils.

Closes: #893620.



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/893620

Processed: Bug #893620 in sphinx marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #893620 [python3-sphinx] python3-sphinx: needs python3-distuils dependency
Added tag(s) pending.

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

Processed: forwarded 893273

[Debian Bug Tracking System]

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

> forwarded 893273 https://github.com/Blosc/bcolz/issues/374
Bug #893273 [src:bcolz] bcolz: FTBFS and Debci failure
Set Bug forwarded-to-address to 'https://github.com/Blosc/bcolz/issues/374'.
> thanks
Stopping processing here.

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

Bug#878101: [pkg-cinnamon] Bug#878101: nemo: Nemo segfault on thumbnailing of a moved file

[Fabio Fantoni]

I'm using nemo 3.6 where I never had the problem and I'm unable to
reproduce it but I had it in past, this issue is reported also by many
users out of here.
I prepared Stretch vm and tried to reproduce it without success,
probably because I tried only with few small images.
Anyway I prepared a test packages with patch that should solves the issue:
wget -O - http://debomatic.fantu.eu/fantutestingrepo.gpg.key | sudo
apt-key add -
#add repository to /etc/apt/sources.list
deb http://debomatic.fantu.eu/deb stretch main contrib non-free
apt-get update
apt-get upgrade

If you want test it please report if solves or not the issues reported here.

Bug#893622: deepin-movie-reborn: Fails to build

[Jeremy Bicha]

Source: deepin-movie-reborn
Version: 3.2.3-1
Severity: serious

deepin-movie-reborn fails to build from source:

https://buildd.debian.org/status/package.php?p=deepin-movie-reborn

Thanks,
Jeremy Bicha

Bug#880886: maven-bundle-plugin FTBFS with libmaven-dependency-tree-java

[殷啟聰 | Kai-Chung Yan]

I adopted the patch from Fedora and it looks good. The package builds fine now 
and 154 of its reverse-build-dependencies built successfully. 27 failed:

* activemq-activeio
* activemq
* apache-directory-server
* dnssecjava
* istack-commons
* jackson-datatype-joda
* javassist
* jayway-jsonpath
* jboss-xnio
* jcommander
* jruby
* jsoup
* kryo-serializers
* libcommons-lang3-java
* libhtmlcleaner-java
* libitext5-java
* libpgjava
* libxbean-java
* libxml-security-java
* openhft-chronicle-bytes
* openhft-chronicle-core
* openhft-chronicle-wire
* openhft-lang
* openjpa
* sisu-ioc
* tika
* undertow

They either failed in compilation due to Java 9 or failed in tests. But I would 
say the result is confident enough to prove that the patch works.

However this package fails to build in Sid currently because of Java 9. I 
attached the log. The Maven Javadoc Plugin failed to honor the compile 
classpath.
I: Copying COW directory
I: forking: rm -rf /media/data/VMs/pbuilder/build/cow.29816
I: forking: cp -al /media/data/VMs/pbuilder/default.cow /media/data/VMs/pbuilder/build/cow.29816
I: removed stale ilistfile /media/data/VMs/pbuilder/build/cow.29816/.ilist
I: forking: chroot /media/data/VMs/pbuilder/build/cow.29816 cowdancer-ilistcreate /.ilist 'find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a -links +1 -print0 \) | xargs -0 stat --format '%d %i ''
I: Invoking pbuilder
I: forking: pbuilder build --buildplace /media/data/VMs/pbuilder/build/cow.29816 --buildresult /var/cache/pbuilder/result/ --no-targz --internal-chrootexec 'chroot /media/data/VMs/pbuilder/build/cow.29816 cow-shell' /media/data/Documents/debian/maven-bundle-plugin_3.5.0-1.dsc
W: /home/seamlik/.pbuilderrc does not exist
I: Running in no-targz mode
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Tue Mar 20 22:40:43 CST 2018
I: pbuilder-time-stamp: 1521556843
I: copying local configuration
W: No local /etc/mailname to copy, relying on /media/data/VMs/pbuilder/build/cow.29816/etc/mailname to be correct
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: Mounting /media/data/VMs/pbuilder/deb
I: policy-rc.d already exists
I: Using pkgname logfile
I: Current time: Tue Mar 20 22:40:43 CST 2018
I: pbuilder-time-stamp: 1521556843
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [/media/data/Documents/debian/maven-bundle-plugin_3.5.0-1.dsc]
I: copying [/media/data/Documents/debian/maven-bundle-plugin_3.5.0.orig.tar.xz]
I: copying [/media/data/Documents/debian/maven-bundle-plugin_3.5.0-1.debian.tar.xz]
I: Extracting source
dpkg-source: warning: extracting unsigned source package (maven-bundle-plugin_3.5.0-1.dsc)
dpkg-source: info: extracting maven-bundle-plugin in maven-bundle-plugin-3.5.0
dpkg-source: info: unpacking maven-bundle-plugin_3.5.0.orig.tar.xz
dpkg-source: info: unpacking maven-bundle-plugin_3.5.0-1.debian.tar.xz
dpkg-source: info: applying remove_bndlib_spring_support.diff
dpkg-source: info: applying support_plexus_utils_1_5.diff
dpkg-source: info: applying use-changelog-date-as-pom.properties-timestamp.patch
dpkg-source: info: applying maven-archiver3-869361.patch
dpkg-source: info: applying maven3-compatibility.patch
dpkg-source: info: applying 0001-Port-to-current-maven-dependency-tree.patch
I: Installing the build-deps
I: user script /media/data/VMs/pbuilder/build/cow.29816/tmp/hooks/D00deps starting
dpkg-scanpackages: info: Wrote 2 entries to output Packages file.

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Get:1 file:/media/data/VMs/pbuilder/deb ./ InRelease
Ign:1 file:/media/data/VMs/pbuilder/deb ./ InRelease
Get:2 file:/media/data/VMs/pbuilder/deb ./ Release
Ign:2 file:/media/data/VMs/pbuilder/deb ./ Release
Get:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Ign:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Get:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Ign:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Get:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Ign:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Get:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Ign:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Get:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Ign:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Get:3 file:/media/data/VMs/pbuilder/deb ./ Packages [2786 B]
Get:4 http://cdn-fastly.deb.debian.org/debian sid InRelease [241 kB]
Get:5 http://cdn-fastly.deb.debian.org/debian sid/main amd64 Packages.diff/Index [27.9 kB]
Get:6 http://cdn-fastly.deb.debian.org/debian sid/main amd64 Packages 2018-03-20-0828.04.pdiff [29.6 kB]
Get:6 http://cdn-fastly.deb.debian.org/debian sid/main amd64 Packages 2018-03-20-0828.04.pdiff [29.6 kB]
Fetched 298 kB in 8s (37.7 kB/s)
Reading package lists...
Building dependency tree...
Reading state information...
11 packages can be upgraded. Run 'apt list 

Bug#892096: gcc-snapshot: AddressSanitizer uses glibc internal functions

[Vincent Lefevre]

On 2018-03-20 01:06:50 +0100, Vincent Lefevre wrote:
> Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84761
> Control: tags -1 fixed-upstream
> 
> in the sense that this will be OK at least up to glibc 2.27.
> 
> See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84761#c9
> 
> Author: jakub
> Date: Mon Mar 19 20:47:29 2018
> New Revision: 258663
> 
> URL: https://gcc.gnu.org/viewcvs?rev=258663=gcc=rev
> Log:
>   PR sanitizer/84761
>   * sanitizer_common/sanitizer_linux_libcdep.cc (__GLIBC_PREREQ):
>   Define if not defined.
>   (DL_INTERNAL_FUNCTION): Don't define.
>   (InitTlsSize): For __i386__ if not compiled against glibc 2.27+
>   determine at runtime whether to use regparm(3), stdcall calling
>   convention for older glibcs or normal calling convention for
>   newer glibcs for call to _dl_get_tls_static_info.
> 
> Modified:
> trunk/libsanitizer/ChangeLog
> trunk/libsanitizer/sanitizer_common/sanitizer_linux_libcdep.cc

I confirm that gcc-snapshot 1:20180320-1 in experimental fixes the
problem.

Thanks,

-- 
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#892971: marked as done (libignition-fuel-tools1-{1,dev}: both ship /usr/lib/ruby/ignition/cmdfuel1.rb)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 16:09:17 +0100
with message-id 

Bug#875336: FTBFS with Java 9: _ as identifier

[殷啟聰 | Kai-Chung Yan]

I just tried building it and Groovy was fine enough, but now Gradle 
complains

Theoretically, ALL Gradle packages FTBFS since the current version is too old 
to play with Java 9's fancy version number.



signature.asc
Description: OpenPGP digital signature

Bug#893620: python3-sphinx: needs python3-distuils dependency

[Rene Engelhard]

Package: python3-sphinx
Version: 1.6.7-1
Severity: serious

Dear Maintainer,

$ grep -ri distutils /usr/lib/python3/dist-packages/sphinx/ 
/usr/share/sphinx/scripts/python3
/usr/lib/python3/dist-packages/sphinx/setup_command.py:Setuptools/distutils 
commands to assist the building of sphinx
/usr/lib/python3/dist-packages/sphinx/setup_command.py:from distutils.cmd 
import Command
/usr/lib/python3/dist-packages/sphinx/setup_command.py:from distutils.errors 
import DistutilsOptionError, DistutilsExecError  # type: ignore
/usr/lib/python3/dist-packages/sphinx/setup_command.py:Distutils command to 
build Sphinx documentation.
/usr/lib/python3/dist-packages/sphinx/setup_command.py:The Sphinx build can 
then be triggered from distutils, and some Sphinx
/usr/lib/python3/dist-packages/sphinx/setup_command.py:# Overriding 
distutils' Command._ensure_stringlike which doesn't support
/usr/lib/python3/dist-packages/sphinx/setup_command.py:raise 
DistutilsOptionError("'%s' must be a %s (got `%s`)"
/usr/lib/python3/dist-packages/sphinx/setup_command.py:
raise DistutilsExecError(
Übereinstimmungen in Binärdatei 
/usr/lib/python3/dist-packages/sphinx/ext/__pycache__/doctest.cpython-36.pyc
/usr/lib/python3/dist-packages/sphinx/ext/doctest.py:from distutils.version 
import LooseVersion
Übereinstimmungen in Binärdatei 
/usr/lib/python3/dist-packages/sphinx/__pycache__/setup_command.cpython-36.pyc
/usr/lib/python3/dist-packages/sphinx/util/docutils.py:from distutils.version 
import LooseVersion
/usr/lib/python3/dist-packages/sphinx/util/compat.py:from distutils.version 
import LooseVersion
Übereinstimmungen in Binärdatei 
/usr/lib/python3/dist-packages/sphinx/util/__pycache__/compat.cpython-36.pyc
Übereinstimmungen in Binärdatei 
/usr/lib/python3/dist-packages/sphinx/util/__pycache__/docutils.cpython-36.pyc
rene@frodo:~/tmp$ 
rene@frodo:~/tmp$ 

And since python3.6 3.6.5~rc1-2 dropped its python3-distutils dependency
I'd say python3-shinx now needs to depend on it itself...

Regards,

Rene

Bug#892559: marked as done (mame FTBFS with gcc 7.3)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 13:50:51 +
with message-id 
and subject line Bug#892559: fixed in mame 0.195+dfsg.1-1
has caused the Debian Bug report #892559,
regarding mame FTBFS with gcc 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.)


-- 
892559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mame
Version: 0.189+dfsg.1-1
Severity: serious

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

...
In file included from ../../../../../3rdparty/glm/glm/detail/precision.hpp:6:0,
 from ../../../../../3rdparty/glm/glm/detail/type_vec.hpp:6,
 from ../../../../../3rdparty/glm/glm/detail/type_vec3.hpp:6,
 from 
../../../../../3rdparty/glm/glm/detail/func_geometric.hpp:13,
 from ../../../../../3rdparty/glm/glm/geometric.hpp:6,
 from ../../../../../src/mame/video/model1.cpp:4:
../../../../../3rdparty/glm/glm/detail/setup.hpp:456:100: note: #pragma 
message: GLM: GCC older than 4.6 has a bug presenting the use of rgba and stpq 
components
 # pragma message("GLM: GCC older than 4.6 has a bug presenting the use of rgba 
and stpq components")

^
In file included from 
../../../../../3rdparty/glm/glm/detail/type_vec4.inl:968:0,
 from ../../../../../3rdparty/glm/glm/detail/type_vec4.hpp:453,
 from 
../../../../../3rdparty/glm/glm/detail/func_exponential.hpp:16,
 from 
../../../../../3rdparty/glm/glm/detail/func_geometric.inl:4,
 from 
../../../../../3rdparty/glm/glm/detail/func_geometric.hpp:113,
 from ../../../../../3rdparty/glm/glm/geometric.hpp:6,
 from ../../../../../src/mame/video/model1.cpp:4:
../../../../../3rdparty/glm/glm/detail/type_vec4_simd.inl: In static member 
function 'static glm::tvec4 
glm::detail::compute_vec4_div::call(const 
glm::tvec4&, const glm::tvec4&)':
../../../../../3rdparty/glm/glm/detail/type_vec4_simd.inl:156:11: error: 
'struct glm::tvec4' has no member named 'data'
Result.data = _mm_mul_ps(a.data, _mm_rcp_ps(b.data));
   ^~~~



mame should use libglm-dev instead of an own bundled copy.
--- End Message ---
--- Begin Message ---
Source: mame
Source-Version: 0.195+dfsg.1-1

We believe that the bug you reported is fixed in the latest version of
mame, 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 892...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jordi Mallach  (supplier of updated mame 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: Sat, 17 Mar 2018 01:31:35 +0100
Source: mame
Binary: mame mame-data mame-tools mame-doc
Architecture: source
Version: 0.195+dfsg.1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Jordi Mallach 
Description:
 mame   - Multiple Arcade Machine Emulator (MAME)
 mame-data  - Multiple Arcade Machine Emulator (MAME) -- data files
 mame-doc   - Documentation for MAME
 mame-tools - Tools for MAME
Closes: 892559
Changes:
 mame (0.195+dfsg.1-1) experimental; urgency=medium
 .
   [ Cesare Falco ]
   * New upstream release.
 .
   [ Jordi Mallach ]
   * Reinstate check rule, as a failure to run indicates grave problems
 in the generated binary.
   * Remove transitional mess package again, as mess-desktop-entries has
 been fixed.
   * Use system libglm, rapidjson and utf8proc. Drop definitions for system
 libuv which is no longer used (closes: #892559).
   * Drop avoid_linenoise.patch and build definitions, as the bundled
 linenoise fork no longer has GPL-incompatible material.
   * Apply several formatting fixes to copyright file.
   * Bump debhelper compat to v11.

Bug#893454: marked as done (libjloda-java: FTBFS with java 9)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 13:35:33 +
with message-id 
and subject line Bug#893454: fixed in libjloda-java 0.0+20180317-1
has caused the Debian Bug report #893454,
regarding libjloda-java: FTBFS with java 9
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.)


-- 
893454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893454
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libjloda-java
Version: 0.0+20170502-1
Severity: serious
Justification: fails to build from source

Hi,

libjloda-java FTBFS with openjdk-9 as default jdk:

compile:
[javac] Compiling 265 source files to 
/build/libjloda-java-0.0+20170502/antbuild/class
[javac] 
/build/libjloda-java-0.0+20170502/antbuild/src/jloda/phylo/PhyloTree.java:30: 
error: package com.sun.istack.internal is not visible
[javac] import com.sun.istack.internal.Nullable;
[javac]  ^
[javac]   (package com.sun.istack.internal is declared in module 
java.xml.bind, which is not in the module graph)
[javac] 
/build/libjloda-java-0.0+20170502/antbuild/src/jloda/graphview/NodeView.java:258:
 warning: [dep-ann] deprecated item is not annotated with @Deprecated
[javac] public void setShape(byte a) {
[javac] ^
[javac] 
/build/libjloda-java-0.0+20170502/antbuild/src/jloda/graphview/NodeView.java:268:
 warning: [dep-ann] deprecated item is not annotated with @Deprecated
[javac] public byte getShape() {
[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] 2 warnings


Andreas


libjloda-java_0.0+20170502-1_indep.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libjloda-java
Source-Version: 0.0+20180317-1

We believe that the bug you reported is fixed in the latest version of
libjloda-java, 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 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libjloda-java 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, 20 Mar 2018 12:43:52 +0100
Source: libjloda-java
Binary: libjloda-java
Architecture: source
Version: 0.0+20180317-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libjloda-java - Java library of data structures and algorithms for 
bioinformatics
Closes: 893454
Changes:
 libjloda-java (0.0+20180317-1) experimental; urgency=medium
 .
   * New upstream commit
 Closes: #893454
   * Standards-Version: 4.1.3
   * debhelper 11
Checksums-Sha1:
 7884bc1ef954febcdac14d5139e35273e75837cd 2131 libjloda-java_0.0+20180317-1.dsc
 835c0028ef44d7ea9f629af138aef0dc199dc8a6 360916 
libjloda-java_0.0+20180317.orig.tar.xz
 2c3e30cc3c63de45470d02c83b27821f22ec5a4f 3848 
libjloda-java_0.0+20180317-1.debian.tar.xz
Checksums-Sha256:
 67a5e7df4e2f2a87764e1f61bd1e76bc89de4cfce9622c88b560ecb72bca7940 2131 
libjloda-java_0.0+20180317-1.dsc
 23127c3a6fde96263259750eb7ff8718795d81976ff63682bfadc56188143c37 360916 
libjloda-java_0.0+20180317.orig.tar.xz
 9c66384ac62a135489d966a1e53833a4c270ed969ebfa3142fef091089ae6700 3848 
libjloda-java_0.0+20180317-1.debian.tar.xz
Files:
 70e0d7f212e9737249f934e053ac2165 2131 science optional 
libjloda-java_0.0+20180317-1.dsc
 03b0b5b4d41ae51bc33fed364b911a91 360916 science optional 
libjloda-java_0.0+20180317.orig.tar.xz
 093ab835c5551d609046bb2cb7622de2 3848 science optional 
libjloda-java_0.0+20180317-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlqxCg8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHivRAAmyP+am1rVDZx4mAeD0/OvjZuCJImBiby
lEpdU/ClIFgCCToiWgNOg0mK32jJNveA0v7ha14LVhsvCjkCmevsgQRUznlJonEO

Bug#893390: marked as done (ed: no longer M-A:foreign, wrecks havoc on whole system on upgrade)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 13:34:17 +
with message-id 
and subject line Bug#893390: fixed in ed 1.14.2-2
has caused the Debian Bug report #893390,
regarding ed: no longer M-A:foreign, wrecks havoc on whole system on upgrade
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.)


-- 
893390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ed
Version: 1.14.2-1
Severity: serious

Despite the changelog saying “Restore Multi-Arch: foreign”
the .deb file actually does not carry any M-A annotation.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
--- End Message ---
--- Begin Message ---
Source: ed
Source-Version: 1.14.2-2

We believe that the bug you reported is fixed in the latest version of
ed, 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 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lev Lamberov  (supplier of updated ed 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: Tue, 20 Mar 2018 18:11:37 +0500
Source: ed
Binary: ed
Architecture: source amd64
Version: 1.14.2-2
Distribution: unstable
Urgency: medium
Maintainer: Martin Zobel-Helas 
Changed-By: Lev Lamberov 
Description:
 ed - classic UNIX line editor
Closes: 893390
Changes:
 ed (1.14.2-2) unstable; urgency=medium
 .
   * Remove the Testsuit field, since d/tests/control exists
   * Move Multi-Arch field to binary package section (Closes: #893390)
Checksums-Sha1:
 98550ac0e910139620a1ab2b0960caf2ce287b62 1855 ed_1.14.2-2.dsc
 d7e094491c38e977b30ce453964d424db05e7312 8296 ed_1.14.2-2.debian.tar.xz
 641ea63a9f8e12788073570fc46dc48c06db597c 53160 ed-dbgsym_1.14.2-2_amd64.deb
 2e00be64776df3d71031b62c96a47213c825dd65 5548 ed_1.14.2-2_amd64.buildinfo
 d7e9fa3db52372c3e639713888a63cd78f73d835 59584 ed_1.14.2-2_amd64.deb
Checksums-Sha256:
 f9c6081c15b59aa9aa9d487abe201b222e3e932628fe753df974fd46b8be2cd5 1855 
ed_1.14.2-2.dsc
 bdcd47f105803481070a620eed174c524ae593d5771bd34ece037e2baccef566 8296 
ed_1.14.2-2.debian.tar.xz
 e1ccf6dc21e223db963fa0a0309ad273b8b0ef7c2d90713099f05990cdd9d28c 53160 
ed-dbgsym_1.14.2-2_amd64.deb
 afe6201101c0f73df42b1a588a7cf22f3d47a2bbb7fc3aea6eefe2c21df5485b 5548 
ed_1.14.2-2_amd64.buildinfo
 61f9814aa23cef9bee33c01177359e6399e6bd678c04904582f63a2d001e6838 59584 
ed_1.14.2-2_amd64.deb
Files:
 4463aa49154d025ff00ce32cc88235d8 1855 editors optional ed_1.14.2-2.dsc
 666badb1df530674a06a5ed57a7b1d95 8296 editors optional 
ed_1.14.2-2.debian.tar.xz
 8e72881011b7e376aa7375d1be3991f0 53160 debug optional 
ed-dbgsym_1.14.2-2_amd64.deb
 3a7001c1ad1f18f1c81928d05711ae14 5548 editors optional 
ed_1.14.2-2_amd64.buildinfo
 f47144597db25d6289e406802223727d 59584 editors optional ed_1.14.2-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE3mumcdV9mwCc9oZQXudu4gIW0qUFAlqxCSATHGRvZ3NsZWdA
ZGViaWFuLm9yZwAKCRBe527iAhbSpShMD/wJ2+cOAHb7NkZDMS0jN3ASnys6E8Eq
PVEnV9fGR9nZLsHg5TLnZJeK0VkcsvEGQOAOnk46ijfff+0n+fJ6EPr3OtzIGU/1
gIYHabaYrJse7Cu6G8VDQEpwKTsyuPDewQXawg3qzi0HfNkNT7INCn6jiz0Tysx+
NjKEszw68TXBEGtTPBp2fFAZVC0KyITGuwEYYcRUerybcwYzm5/QC3VKrgtv06Cq
8UCkW/NgNgv+XQtdZaHCyHFTCLHnzlpxJtihSmARYNXsBiusL5Tpv625mVZNu+Wa
t1+q4yDWtdwN4d7dhvZlpJZqpOSZm85K7r1iq3xDAsX0NIUkaJfrpXDynF5lc/yS
1AL+6NZme56lp/T+H/Far/geS52e0IDO9wyydz+ucuXXNEqEO1dq/9rNvMF+NL2B
c+OVqJtSBlqaAaf4MQoe/B4dd+YGNUsQGJZPhJr4tI25c5qquPWJOaZMlKbCbAMc
glLkiHy7IjPZmtORmiWzhGyyVjUOoMBwWmuimzJVfchG70Aqam/WLax9mcr5/CBe
cC5l3r4auY9S+IkBVD2KnA0mv1ltI7zkD5rXzKuXsZ2QhC2j2YoNkbNvClyZXwAg
Pyhr9BVNdE9o88ZvaWxGw9zWyNOEVggBRmAwdcsT0P8HvWHGOqOPNEC8VRxNm+FV
X9lKcnauwW+veg==
=qmjb
-END PGP SIGNATURE End Message ---

Processed: severity of 893610 is grave

[Debian Bug Tracking System]

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

> severity 893610 grave
Bug #893610 [src:ruby-sanitize] ruby-sanitize: CVE-2018-3740
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#893219: marked as done (activemq-activeio FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 13:04:15 +
with message-id 
and subject line Bug#893219: fixed in activemq-activeio 3.1.4-3
has caused the Debian Bug report #893219,
regarding activemq-activeio FTBFS with openjdk-9
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.)


-- 
893219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: activemq-activeio
Version: 3.1.4-2
Severity: serious

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

...
[INFO] Compiling 17 source files to 
/build/1st/activemq-activeio-3.1.4/activeio-core/target/test-classes
Use of target 1.5 is no longer supported, switching to 1.7
Use of source 1.5 is no longer supported, switching to 1.7
[WARNING] bootstrap class path not set in conjunction with -source 1.7
[WARNING] 
/build/1st/activemq-activeio-3.1.4/activeio-core/src/test/java/org/apache/activeio/journal/active/JournalImplTest.java:[72,24]
 close() in org.apache.activeio.journal.active.JournalImpl has been deprecated
[INFO] 
/build/1st/activemq-activeio-3.1.4/activeio-core/src/test/java/org/apache/activeio/journal/active/JournalImplTest.java:
 Some input files use unchecked or unsafe operations.
[INFO] 
/build/1st/activemq-activeio-3.1.4/activeio-core/src/test/java/org/apache/activeio/journal/active/JournalImplTest.java:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-surefire-plugin:2.20.1:test (default-test) @ activeio-core ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-bundle-plugin:2.5.4:bundle (default-bundle) @ activeio-core ---
[WARNING] Bundle org.apache.activemq:activeio-core:bundle:3.1.4 : Unused 
Import-Package instructions: [org.objectweb.howl.log*] 
[INFO] 
[INFO] --- maven-jar-plugin:3.0.2:test-jar (default) @ activeio-core ---
[INFO] Building jar: 
/build/1st/activemq-activeio-3.1.4/activeio-core/target/activeio-core-3.1.4-tests.jar
[INFO] 
[INFO] --- maven-javadoc-plugin:3.0.0:jar (default-cli) @ activeio-core ---
[WARNING] Source files encoding has not been set, using platform encoding 
ANSI_X3.4-1968, i.e. build is platform dependent!
[INFO] 
Loading source files for package org.apache.activeio.packet...
Loading source files for package org.apache.activeio.adapter...
Loading source files for package org.apache.activeio.journal.howl...
Loading source files for package org.apache.activeio.journal...
Loading source files for package org.apache.activeio.journal.active...
Loading source files for package org.apache.activeio.oneport...
Loading source files for package org.apache.activeio.xnet...
Loading source files for package org.apache.activeio.xnet.hba...
Constructing Javadoc information...
13 errors
[INFO] 
[INFO] 
[INFO] Skipping ActiveIO
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] ActiveIO ... SUCCESS [ 13.462 s]
[INFO] ActiveIO :: Core ... FAILURE [02:05 min]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 02:56 min
[INFO] Finished at: 2018-03-16T14:34:40-12:00
[INFO] Final Memory: 20M/68M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (default-cli) on 
project activeio-core: MavenReportException: Error while generating Javadoc: 
[ERROR] Exit code: 1 - 
/build/1st/activemq-activeio-3.1.4/activeio-core/src/main/java/org/apache/activeio/journal/howl/HowlJournal.java:29:
 error: package org.objectweb.howl.log does not exist
[ERROR] import org.objectweb.howl.log.Configuration;
[ERROR]  ^
[ERROR] 
/build/1st/activemq-activeio-3.1.4/activeio-core/src/main/java/org/apache/activeio/journal/howl/HowlJournal.java:30:
 error: package org.objectweb.howl.log does not exist
[ERROR] import org.objectweb.howl.log.InvalidFileSetException;
[ERROR]  ^
[ERROR] 
/build/1st/activemq-activeio-3.1.4/activeio-core/src/main/java/org/apache/activeio/journal/howl/HowlJournal.java:31:
 error: package 

Bug#893233: marked as done (python-lesscpy: python3-lesscpy not working with python)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 12:20:08 +
with message-id 
and subject line Bug#893233: fixed in python-lesscpy 0.13.0+ds-1
has caused the Debian Bug report #893233,
regarding python-lesscpy: python3-lesscpy not working with python
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.)


-- 
893233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-lesscpy
Version: 0.10-1
Severity: important

python-lesscpy 0.10 do not support python 3.5 or newer. Please upgrade
this package to have a working python-lesscpy with python3.

The actual stable upstream version is 0.13

Thanks

Regards
--- End Message ---
--- Begin Message ---
Source: python-lesscpy
Source-Version: 0.13.0+ds-1

We believe that the bug you reported is fixed in the latest version of
python-lesscpy, 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 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Andrejak  (supplier of updated python-lesscpy 
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: Sun, 18 Mar 2018 18:14:47 +0200
Source: python-lesscpy
Binary: python-lesscpy python3-lesscpy
Architecture: source
Version: 0.13.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Thomas Andrejak 
Changed-By: Thomas Andrejak 
Description:
 python-lesscpy - LessCss Compiler for Python 2.x
 python3-lesscpy - LessCss Compiler for Python 3.x
Closes: 893233 893373
Changes:
 python-lesscpy (0.13.0+ds-1) unstable; urgency=medium
 .
   * New maintainer: Thomas Andrejak (Closes: #893373)
   * New upstream release: 0.13.0 (Closes: #893233)
 - Upload a new tarball without .pyc files
 - Update d/control dependencies
 - Remove an old patch not necessary now
   * Upgrade debhelper and compat from 9 to 11
   * Update d/watch file based on pypi.debian.net
   * Update d/rules: cleanup, migrate to pybuild
   * Update d/control:
 - Update old style fields on python things
 - Standards-Version upgrade to 4.1.3
 - Update Vcs-* fields
   * Update d/copyright
   * Remove postrm file for update-alternatives
 .
 python-lesscpy (0.10-2) UNRELEASED; urgency=medium
 .
   [ Ondřej Nový ]
   * Fixed VCS URLs (https).
   * d/rules: Changed UPSTREAM_GIT protocol to https
   * d/copyright: Changed source URL to https protocol
   * d/s/options: extend-diff-ignore of .gitreview
   * d/control: Using OpenStack's Gerrit as VCS URLs.
   * Bumped debhelper compat version to 10
 .
   [ Daniel Baumann ]
   * Updating vcs fields.
   * Updating copyright format url.
   * Updating maintainer field.
   * Running wrap-and-sort -bast.
   * Updating standards version to 4.0.0.
   * Removing gbp.conf, not used anymore or should be specified in the
 developers dotfiles.
   * Correcting permissions in debian packaging files.
   * Updating standards version to 4.0.1.
   * Updating standards version to 4.1.0.
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/control: Add trailing tilde to min version depend to allow
 backports
Checksums-Sha1:
 ac8d4e3d367885c4b1264e9a39245ee5c2b7363c 2085 python-lesscpy_0.13.0+ds-1.dsc
 85e39120027258a02e0f54e9e6307144b3da1ded 152995 
python-lesscpy_0.13.0+ds.orig.tar.gz
 2fa8f002e50ec12701a6a37958be5a3cb8d5bec0 3340 
python-lesscpy_0.13.0+ds-1.debian.tar.xz
 cff07ce47d899927eb1f743a7ab3646324f608cb 6708 
python-lesscpy_0.13.0+ds-1_amd64.buildinfo
Checksums-Sha256:
 754ef994f0684882730f9151b18bf1b23f6a17d206edd8edb81061b4bcc45a42 2085 
python-lesscpy_0.13.0+ds-1.dsc
 98132786d91a689f89681426d643761f02982a4a5a3ccad70f29d413f59d340c 152995 
python-lesscpy_0.13.0+ds.orig.tar.gz
 b9574fa926b970860b76c7ad6efbd2ad884c36ee870d427b5c2690780534db2e 3340 
python-lesscpy_0.13.0+ds-1.debian.tar.xz
 2abe0a85ed2714bfff404e59730aede13d85f2429b0aab3297f15584f9f3aa13 6708 
python-lesscpy_0.13.0+ds-1_amd64.buildinfo
Files:
 7719827c2d1a728d4883eaa93965902d 2085 python optional 
python-lesscpy_0.13.0+ds-1.dsc
 

Processed: Re: fixed 890850 in 3.4.0-4

[Debian Bug Tracking System]

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

> close 890850
Bug #890850 [src:ruby-redcarpet] ruby-redcarpet FTBFS on 32bit: test failures 
with ruby 2.3
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#893608: sbuild: Silent arch:all defaults change breaks buildd setups

[James Clarke]

Package: sbuild
Version: 0.74.0-1
Severity: serious

[Feel free to downgrade severity, but from my PoV this needs addressing before
Buster is released]

Hi,
In the latest upload, #870263 was fixed (which I support, for what it's worth;
any+all builds is the right default for users), meaning that buildd setups now
build arch:all packages, which we *have* to work around by setting
$build_arch_all=0 in sbuild.conf. Without this, uploads are rejected by the
archive (the buildd's signing key does not have upload rights for arch:all
packages, the arch:all packages already exist, etc). This is therefore a
breaking change, and so deserves at least a mention in the NEWS file. Moreover,
having to configure this in sbuild.conf is sub-optimal; ideally, buildd would
pass --no-arch-all to sbuild when an arch:any build is requested by wanna-build;
as far as I know, the assumption is always that a non-Architecture:all build is
arch:any.

We probably also don't want lintian run during buildd builds as it fork-bombs on
packages like gcc-8-cross-ports (#890873), and there's lintian.debian.org doing
that for x86, which is probably good enough, though I suppose in an ideal world
it would be run too.

Regards,
James

Bug#893607: jsxgraph FTBFS with node-almond 0.3.3+dfsg-1

[Adrian Bunk]

Source: jsxgraph
Version: 0.99.6+dfsg1-1
Severity: serious

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

...
make -j1
make[1]: Entering directory '/build/1st/jsxgraph-0.99.6+dfsg1'
# add symlinks to replace node_modules utilities
#
# replace almond
mkdir -p node_modules/almond
ln -s /usr/lib/nodejs/almond.js node_modules/almond/
mkdir -p node_modules/requirejs/bin
#ln -s /usr/lib/nodejs/r.js node_modules/requirejs/bin
mkdir -p build/bin
nodejs ./node_modules/bin/r.js -o build/core.build.json
Error: Error: ERROR: module path does not exist: 
/build/1st/jsxgraph-0.99.6+dfsg1/src/../node_modules/almond/almond.js for 
module named: ../node_modules/almond/almond. Path is relative to: 
/build/1st/jsxgraph-0.99.6+dfsg1
at /build/1st/jsxgraph-0.99.6+dfsg1/node_modules/bin/r.js:30214:35

make[1]: *** [Makefile:72: core] Error 1

Bug#893485: marked as done (gjs: FTBFS on mips* - error: braces around scalar initializer for type 'int')

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 11:49:10 +
with message-id 
and subject line Bug#893485: fixed in gjs 1.52.0-2
has caused the Debian Bug report #893485,
regarding gjs: FTBFS on mips* - error: braces around scalar initializer for 
type 'int'
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.)


-- 
893485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gjs
Version: 1.52.0-1
Severity: serious
Tags: sid buster patch

Hi,

gjs FTBFS on mips* with this error:
> gjs/profiler.cpp: In function 'void gjs_profiler_start(GjsProfiler*)':
> gjs/profiler.cpp:380:33: error: braces around scalar initializer for type 
> 'int'
>  struct sigaction sa = {{ 0 }};
>  ^
> make[2]: *** [Makefile:2422: gjs/libgjs_la-profiler.lo] Error 1

This happens because sigaction has an unusual layout on mips where the
first field is sa_flags instead of the usual sa_handler/sa_sigaction union.

I've attached a patch to fix this.

Thanks,
James
Description: Fix FTBFS on mips*
 Do not assume the first field of sigaction is a struct or union.
Author: James Cowgill 
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/gjs/profiler.cpp
+++ b/gjs/profiler.cpp
@@ -377,9 +377,9 @@ gjs_profiler_start(GjsProfiler *self)
 
 g_return_if_fail(!self->capture);
 
-struct sigaction sa = {{ 0 }};
-struct sigevent sev = {{ 0 }};
-struct itimerspec its = {{ 0 }};
+struct sigaction sa = { 0 };
+struct sigevent sev = { 0 };
+struct itimerspec its = { 0 };
 struct itimerspec old_its;
 
 GjsAutoChar path = g_strdup(self->filename);
@@ -491,7 +491,7 @@ gjs_profiler_stop(GjsProfiler *self)
 
 #ifdef ENABLE_PROFILER
 
-struct itimerspec its = {{ 0 }};
+struct itimerspec its = { 0 };
 timer_settime(self->timer, 0, , nullptr);
 timer_delete(self->timer);
 


signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: gjs
Source-Version: 1.52.0-2

We believe that the bug you reported is fixed in the latest version of
gjs, 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 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated gjs 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: Tue, 20 Mar 2018 07:35:20 -0400
Source: gjs
Binary: gjs gjs-tests libgjs0g libgjs-dev
Architecture: source
Version: 1.52.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 gjs- Mozilla-based javascript bindings for the GNOME platform
 gjs-tests  - Mozilla-based javascript bindings for the GNOME platform
 libgjs-dev - Mozilla-based javascript bindings for the GNOME platform
 libgjs0g   - Mozilla-based javascript bindings for the GNOME platform
Closes: 893485
Changes:
 gjs (1.52.0-2) unstable; urgency=medium
 .
   [ James Cowgill ]
   * Add mips-sigaction.patch to fix build on mips* (Closes: #893485)
Checksums-Sha1:
 1c9cc42e773f5f44ddf6ac603419579248743b51 2476 gjs_1.52.0-2.dsc
 7a092df3fd21ad6d7c166535e26e1a701c5134c9 11976 gjs_1.52.0-2.debian.tar.xz
 ae6233a04e3c8e86f3e9e15835175aa0dfb79036 17216 gjs_1.52.0-2_source.buildinfo
Checksums-Sha256:
 75da1b23dddc6755a998e4ed07c5d8a4b095cd03d9e617fa3c0b5419c4e50fc7 2476 
gjs_1.52.0-2.dsc
 1e2d311353116edf4a69085ad9a8bc7a447a89dc77d4e758e8cc400ec4f7aa8d 11976 
gjs_1.52.0-2.debian.tar.xz
 f4ff7aa90dfbcac069e3efda9646395e0dd507edea14cc8847f095347a2228d2 17216 
gjs_1.52.0-2_source.buildinfo
Files:
 5b9ad867c98cc1003eef6e76283f1680 2476 interpreters optional gjs_1.52.0-2.dsc
 ecd4dfebf2b7c17ff8e7060ea35bf366 11976 interpreters optional 
gjs_1.52.0-2.debian.tar.xz
 929db7b7e85ef1a3b58b7bc37b404191 17216 interpreters optional 
gjs_1.52.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAlqw8isACgkQ5mx3Wuv+

Processed: reassign 893426 to src:systemd, forcibly merging 893426 893602

[Debian Bug Tracking System]

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

> reassign 893426 src:systemd
Bug #893426 [systemd] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN
Bug reassigned from package 'systemd' to 'src:systemd'.
No longer marked as found in versions systemd/238-1.
Ignoring request to alter fixed versions of bug #893426 to the same values 
previously set
> forcemerge 893426 893602
Bug #893426 [src:systemd] systemd FTBFS: syntax error close to 
GPGRT_ATTR_NORETURN
Bug #893602 [src:systemd] macro.h:423:18: error: expected ')' before 
'__attribute__'
Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/pull/8456'.
Severity set to 'serious' from 'important'
Added indication that 893602 affects systemd
Added tag(s) pending and patch.
Bug #893426 [src:systemd] systemd FTBFS: syntax error close to 
GPGRT_ATTR_NORETURN
Marked as found in versions systemd/238-2.
Added tag(s) confirmed.
Merged 893426 893602
> thanks
Stopping processing here.

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

Processed: Bug #893485 in gjs marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #893485 [src:gjs] gjs: FTBFS on mips* - error: braces around scalar 
initializer for type 'int'
Added tag(s) pending.

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

Bug#893485: Bug #893485 in gjs marked as pending

[jcowgill]

Control: tag -1 pending

Hello,

Bug #893485 in gjs 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/gnome-team/gjs/commit/7064124a9729d3199c52de7d365d8a782f67e1ab


Add patch to fix build on mips* (Closes: #893485)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/893485

Processed: Re: Bug#893485: gjs: FTBFS on mips* - error: braces around scalar initializer for type 'int'

[Debian Bug Tracking System]

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

> forwarded 893485 https://gitlab.gnome.org/GNOME/gjs/merge_requests/96
Bug #893485 [src:gjs] gjs: FTBFS on mips* - error: braces around scalar 
initializer for type 'int'
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/gjs/merge_requests/96'.
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: macro.h:423:18: error: expected ')' before '__attribute__'

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 893426 -1
Bug #893426 [systemd] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN
Unable to merge bugs because:
package of #893602 is 'src:systemd' not 'systemd'
Failed to forcibly merge 893426: Did not alter merged bugs.


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

Bug#890805: marked as done (imagemagick: Update for 6.9.9-35)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 11:05:42 +
with message-id 
and subject line Bug#890805: fixed in imagemagick 8:6.9.9.39+dfsg-1
has caused the Debian Bug report #890805,
regarding imagemagick: Update for 6.9.9-35
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.)


-- 
890805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: imagemagick
Severity: security

This release fixes many many security issues. They have not been issued
CVEs as far as I know. You can get a sense of them by reviewing the commit
history: https://github.com/ImageMagick/ImageMagick/commits/ImageMagick-6
Commits which are links to the OSS-Fuzz issue tracker are often security
vulnerability fixes.

Cheers!

-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
GPG Key fingerprint: D1B3 ADC0 E023 8CA6
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.9.9.39+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 890...@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, 19 Mar 2018 17:03:39 +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-5 
libmagickcore-6.q16-5-extra libmagickcore-6.q16-dev libmagickwand-6.q16-5 
libmagickwand-6.q16-dev libmagick++-6.q16-8 libmagick++-6.q16-dev 
libimage-magick-q16-perl imagemagick-6.q16hdri libmagickcore-6.q16hdri-5 
libmagickcore-6.q16hdri-5-extra libmagickcore-6.q16hdri-dev 
libmagickwand-6.q16hdri-5 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.9.39+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-5 - low-level image manipulation library -- quantum depth 
Q16
 libmagickcore-6.q16-5-extra - low-level image manipulation library - extra 
codecs (Q16)
 libmagickcore-6.q16-dev - low-level image 

Bug#890751: marked as done (rake FTBFS with Ruby 2.5: cannot load such file -- ubygems (LoadError))

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 10:51:06 +
with message-id 
and subject line Bug#890751: fixed in rake 12.3.0-2
has caused the Debian Bug report #890751,
regarding rake FTBFS with Ruby 2.5: cannot load such file -- ubygems (LoadError)
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.)


-- 
890751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rake
Version: 12.3.0-1
Severity: serious

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

...
┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rb  │
└──┘

RUBYLIB=/build/1st/rake-12.3.0/debian/rake/usr/lib/ruby/vendor_ruby:. 
GEM_PATH=debian/rake/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 debian/ruby-tests.rb
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot 
load such file -- ubygems (LoadError)
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /build/1st/rake-12.3.0/debian/rake returned 
exit code 1
make: *** [debian/rules:4: binary] Error 1
--- End Message ---
--- Begin Message ---
Source: rake
Source-Version: 12.3.0-2

We believe that the bug you reported is fixed in the latest version of
rake, 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 890...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Georg Faerber  (supplier of updated rake 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: Tue, 20 Mar 2018 03:04:12 +0100
Source: rake
Binary: rake
Architecture: source
Version: 12.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Georg Faerber 
Description:
 rake   - ruby make-like utility
Closes: 890751
Changes:
 rake (12.3.0-2) unstable; urgency=medium
 .
   * debian/control:
 - Add myself as Uploader.
 - Bump required debhelper version to >= 11~.
 - Bump Standards-Version to 4.1.3, no changes needed.
 - Use salsa.debian.org for Vcs-{Git,Browser} fields.
 - Run wrap-and-sort.
   * debian/copyright:
 - Use HTTPS in link to copyright format specification.
 - Include missing authors and bump years to include 2018.
   * debian/compat: Bump debhelper compat level to 11.
   * debian/ruby-tests.rb: Ensure tests are working with ruby 2.5: Remove the
 call to the dropped option '-rubygems' in ruby 2.5, make the run of the
 testsuite verbose, and, drop the fixed seed, again. The later was needed
 to ensure the testsuite was executed successfully; this was fixed
 upstream, now. (Closes: #890751)
   * debian/rules: Install upstream changelog.
Checksums-Sha1:
 2e1d5bc958848fbc383a93bdfaaa681b32b7bf10 1742 rake_12.3.0-2.dsc
 dfaf16e78e6b45add0eb9fa2faf3371328d4f541 7256 rake_12.3.0-2.debian.tar.xz
 220ed4b75085265ca36f08059974ebabac0c7496 6413 rake_12.3.0-2_source.buildinfo
Checksums-Sha256:
 923d12e3350115282852d2b2d498a1591215a5b7dea94a3dda23a491a5a4d8ca 1742 
rake_12.3.0-2.dsc
 46dbe522d4285b9c9908efd1cef87f18d42144ff15a1fcbff492d8a5c1156360 7256 
rake_12.3.0-2.debian.tar.xz
 5a5dd9bb6d2f2de7990ad26f2eba3fd0dc246e9febee364e7a7746dd11de1e11 6413 
rake_12.3.0-2_source.buildinfo
Files:
 e3563c67fca73355a31651abf45289b9 1742 ruby optional rake_12.3.0-2.dsc
 8438fd62525e4b8dcf67be31b98e01e7 7256 ruby optional rake_12.3.0-2.debian.tar.xz
 19612dba777e298e2e747595b683f06f 6413 ruby optional 
rake_12.3.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnM1rMZ2/jkCrGr0aia+CtznNIXoFAlqw4SsACgkQia+CtznN
IXorYAf/cAWTUuG84Ww5XOgOIrclIbXf1bWlIxj3a66+bDtz7C3vC1IPPUvAIe2F

Bug#893485: gjs: FTBFS on mips* - error: braces around scalar initializer for type 'int'

[James Cowgill]

Hi,

On 19/03/18 12:52, Jeremy Bicha wrote:
> On Mon, Mar 19, 2018 at 6:28 AM, James Cowgill  wrote:
>> I've attached a patch to fix this.
> 
> I really appreciate your patch! Are you interested in submitting this
> as a merge proposal upstream?
> 
> https://gitlab.gnome.org/GNOME/gjs

Yeah I'll try and submit it upstream today.

James



signature.asc
Description: OpenPGP digital signature

Bug#890751: Bug #890751 in rake marked as pending

[georg]

Control: tag -1 pending

Hello,

Bug #890751 in rake 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/ruby-team/rake/commit/ea933f4e55577f043d38bce87ffb02d31ca8fab4


debian/ruby-tests.rb: Ensure tests are working with ruby 2.5

This commit removes the call to the dropped option '-rubygems' in ruby
2.5, makes the run of the testsuite verbose, and, drops the fixed seed,
again. This was introduced in 213d8513e32320b84584066069d0d78bc47f713f,
but now fixed upstream.

Closes: #890751



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/890751

Processed: Bug #890751 in rake marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #890751 [src:rake] rake FTBFS with Ruby 2.5: cannot load such file -- 
ubygems (LoadError)
Ignoring request to alter tags of bug #890751 to the same tags previously set

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

Bug#893513: marked as done (libayatana-indicator FTBFS: error: assignment from incompatible pointer type)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 10:20:56 +
with message-id 
and subject line Bug#893513: fixed in libayatana-indicator 0.6.2-1
has caused the Debian Bug report #893513,
regarding libayatana-indicator FTBFS: error: assignment from incompatible 
pointer type
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.)


-- 
893513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libayatana-indicator
Version: 0.6.1-1
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

After failing to cross build libayatana-indicator, I tried to build it
natively, but it fails the same way:

| /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../../libayatana-indicator -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -pthread 
-I/usr/include/libayatana-ido3-0.4 -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include  
-DG_LOG_DOMAIN=\"libayatana-indicator\" -Wall -Werror 
-Wno-error=deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
libayatana_indicator3_la-indicator-ng.lo `test -f 'indicator-ng.c' || echo 
'../../../libayatana-indicator/'`indicator-ng.c
| libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../libayatana-indicator 
-I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread 
-I/usr/include/libayatana-ido3-0.4 -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-DG_LOG_DOMAIN=\"libayatana-indicator\" -Wall -Werror 
-Wno-error=deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c 
../../../libayatana-indicator/indicator-ng.c  -fPIC -DPIC -o 
.libs/libayatana_indicator3_la-indicator-ng.o
| ../../../libayatana-indicator/indicator-ng.c: In function 'indicator_ng_init':
| ../../../libayatana-indicator/indicator-ng.c:690:21: error: assignment from 
incompatible pointer type [-Werror=incompatible-pointer-types]
|self->entry.label = g_object_ref_sink (gtk_label_new (NULL));
|  ^
| ../../../libayatana-indicator/indicator-ng.c:691:21: error: assignment from 
incompatible pointer type [-Werror=incompatible-pointer-types]
|self->entry.image = g_object_ref_sink (gtk_image_new ());
|  ^
| ../../../libayatana-indicator/indicator-ng.c:693:20: error: assignment from 
incompatible pointer type [-Werror=incompatible-pointer-types]
|self->entry.menu = g_object_ref_sink (gtk_menu_new ());
| ^
| cc1: all warnings being treated as errors
| make[5]: *** [Makefile:770: libayatana_indicator3_la-indicator-ng.lo] Error 1
| make[5]: Leaving directory 
'/<>/builddir/gtk3/libayatana-indicator'
| make[4]: *** [Makefile:520: all] Error 2
| make[4]: Leaving directory 
'/<>/builddir/gtk3/libayatana-indicator'
| make[3]: *** [Makefile:439: all-recursive] Error 1
| make[3]: Leaving directory '/<>/builddir/gtk3'
| make[2]: *** [Makefile:370: all] Error 2
| make[2]: Leaving directory '/<>/builddir/gtk3'
| dh_auto_build: cd builddir/gtk3 && make -j1 returned exit code 2
| make[1]: *** [debian/rules:33: dobuild-gtk3] Error 2
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:20: build-arch] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Helmut
--- End Message ---
--- Begin Message ---
Source: libayatana-indicator
Source-Version: 0.6.2-1

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

A summary of 

Bug#893513: marked as pending

[Mike Gabriel]

tag 893513 pending
thanks

Hello,

Bug #893513 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/pkg-ayatana/libayatana-indicator.git/commit/?id=d51f433

---
commit d51f433b7c1fe91eca949d9c530ec6cda57f9715
Author: Mike Gabriel 
Date:   Tue Mar 20 10:54:06 2018 +0100

upload to unstable (debian/0.6.2-1)

diff --git a/debian/changelog b/debian/changelog
index a33e2ea..099ab9c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,16 @@
-libayatana-indicator (0.6.2-1) UNRELEASED; urgency=medium
+libayatana-indicator (0.6.2-1) unstable; urgency=medium
 
   * New upstream release.
+- Type cast assignments from g_object_ref_sink().
+  (Closes: #893513).
+  * debian/control:
++ Bump Standards-Version: to 4.1.3. No changes needed.
+  * debian/copyright:
++ Use secure URI for copyright format reference.
+  * debian/watch:
++ Use secure URL to obtain upstream sources.
 
- -- Mike Gabriel   Tue, 20 Mar 2018 10:44:32 +0100
+ -- Mike Gabriel   Tue, 20 Mar 2018 10:51:28 +0100
 
 libayatana-indicator (0.6.1-1) unstable; urgency=medium
 

Processed: Bug#893513 marked as pending

[Debian Bug Tracking System]

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

> tag 893513 pending
Bug #893513 [src:libayatana-indicator] libayatana-indicator FTBFS: error: 
assignment from incompatible pointer type
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#893458: marked as done (libundead depends on cruft packages.)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 09:12:42 +
with message-id 
and subject line Bug#893458: fixed in libundead 1.0.9-2
has caused the Debian Bug report #893458,
regarding libundead depends on cruft packages.
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.)


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

Package: libundead
Version: 1.0.9-1
Severity: serious

libundead-dev depends on libphobos2-ldc-dev
libundead0 depends on libphobos2-ldc76

Neither of these packages is built by ldc anymore. They seem to have been 
replaced by  libphobos2-ldc-shared-dev and libphobos2-ldc-shared78

It seems there has not been an attempt to been an attempt to binnmu libundead 
for this transition in Debian. When we binnmu'd it in raspbian the dependency 
on libphobos2-ldc76 was replaced by libphobos2-ldc-shared78 but the dependency 
on libphobos2-ldc-dev remained.

Please update your package.
--- End Message ---
--- Begin Message ---
Source: libundead
Source-Version: 1.0.9-2

We believe that the bug you reported is fixed in the latest version of
libundead, 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 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libundead 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, 20 Mar 2018 09:18:06 +0100
Source: libundead
Binary: libundead0 libundead-dev
Architecture: source
Version: 1.0.9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libundead-dev - Obsolete Phobos modules - development files
 libundead0 - Obsolete Phobos modules upgraded to work with the latest D
Closes: 893458
Changes:
 libundead (1.0.9-2) unstable; urgency=medium
 .
   [ Matthias Klumpp ]
   * Adjust dependencies
 Closes: #893458
   * Use dh-dlang
   * d/rules: s/list-missing/fail-missing/
 .
   [ Andreas Tille ]
   * Standards-Version: 4.1.3
   * debhelper 11
Checksums-Sha1:
 307e181608f13424ca11f71c80319a77a5637702 2056 libundead_1.0.9-2.dsc
 afaf1f76f329730ebecbcafd63e11bb10305ca41 4640 libundead_1.0.9-2.debian.tar.xz
Checksums-Sha256:
 2250484b3af4b306438e63c70335acb2bb6f8ff3291d6125244b88c211ca76c9 2056 
libundead_1.0.9-2.dsc
 fedef2edc20deb1cafede35e443139b15600e9d114ffaf5d9c0a898766655602 4640 
libundead_1.0.9-2.debian.tar.xz
Files:
 46ae410f7c5fc31f925eac0b9f79d7cc 2056 libs optional libundead_1.0.9-2.dsc
 8bab61dd2dff2ad2fe2c4b2e39b6ff7f 4640 libs optional 
libundead_1.0.9-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlqwxwARHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHBVhAAgwcibzyhfsS/xb9u8MLu9rMWOe3A/Pio
vLSy7vGxAsRs3kBMUgY/RGfYLD4VpmwOwObpwWR2FkaR7ZtZ8b1ZyVFN1CiQxinu
Tz21LeffbYtfPt7q1vKjGFpajDtTL6u7je4aILYE/InQKOmWnacgzEs3VLB3Hds2
D2XBckWvUFAY+vXZPy6Toxkz6JO3v+eVlrKP4icn4wnOk91ByrmUa67Al8t1lNSZ
KXnCHM4Cg9jgAyvrUjofIXCAPP3KxDj+aji8Op2o9xPCtFzvRRxnTIqZeZX+DMaA
TlUd6mHx90bMXgBwPcQvyZKWlHNH2wdRjWiyWJyy6xdkXw2+D1VFewXKIE6s/T+G
+MX8DbS4NCgG7DSIGRExz0RQqTUbw0ZX11nDTRHBNrcdV8/1rMTy5JJno5hUNl9Y
Qn9xURskjVdNDzTiFBYBwEc0IzprnvfazcB4FB5Cny+MCek1JzEKtoG3ze8Q17X9
VO8zc+ysYxLOCZGME1G4NRwJUCrgOgls499YStmBhh3kGDkMwKfabDwm8h/gY/IX
RARDcC1FMoHz8C2dHUqydC36F7GJ1A7kdx0y3oU8LOU7qN7fjiX+3M8P8Q/6k5BV
KPQSwQuPjHz78yG71G5Cdtl6d8EBNw246S7EgwfOl0YLwuABg3DW5irntptUQ2ON
+3MogkLmfFw=
=80DH
-END PGP SIGNATURE End Message ---

Bug#893472: libfurl-perl: broken on s390x?

[Jonas Smedegaard]

Quoting Niko Tyni (2018-03-19 20:35:03)
> On Mon, Mar 19, 2018 at 01:03:12AM -0700, Steve Langasek wrote:
> > Source: libfurl-perl
> > Version: 3.13-1
> > Severity: grave
> > User: ubuntu-de...@lists.ubuntu.com
> > Usertags: origin-ubuntu bionic autopkgtest
> 
> > t/100_low/13_deflate.t .. 
> > # normal 1 gzip
> > Uncompress error: data error at /usr/share/perl5/Furl/HTTP.pm line 845.
> 
> > From what I'm able to tell, this test failure points to the library 
> > actually being broken on s390x, as it fails to decompress data sent 
> > back by the test server which is implemented using 
> > libplack-middleware-deflater-perl. But it's also possible that it's 
> > libplack-middleware-deflater-perl which is broken on s390x, in which 
> > case this bug should be certainly reassigned.
> 
> Thanks for the report. Testing on zelenka.d.o, I see the same behaviour.

Thanks to both of you for the investigations.

> I suspect the real culprit is libplack-middleware-deflater-perl; it 
> uses pack() in suspicious ways that might break on big vs. little 
> endian. Its own t/furl.t is failing similarly, but gets skipped on 
> Debian build+autopkgtest because libfurl-perl is not a build 
> dependency of libplack-middleware-deflater-perl (possibly due to build 
> cycle reasons.)

I believe circular build-dependencies for testsuite needs can - and 
should be addressed by marking such build-dependencies appropriately, 
rather than skipping them - for exactly situations like this.

Question then what the appropriate way to express cycle-breaking 
hints... :-)

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#893458: libundead depends on cruft packages.

[Andreas Tille]

Thanks a lot, Matthias. 

-- 
http://fam-tille.de

Bug#893547: ant: please do not emit --ignore-source-errors on Java 9

[Ole Streicher]

Hi Tony,


On 20.03.2018 05:20, tony mancill wrote:
> I'm in the midst of preparing an update for ant.  Is there any context
> in which we want to add "--ignore-source-errors" to the ant javadoc
> task, or should this patch [1] be removed entirely?
>

I am not familar with ant, so I can't recommend here. The failure seems
to not generally appear, but only on specific targets.

This is the snippet that produces the error:

    

while this one (from another package, starjava-pal) works fine:

    

So, it may have something to do with the doclet.

Best

Ole

Bug#883951: cyrus-imapd fails to build with libical3

[Steve Langasek]

Package: cyrus-imapd
Followup-For: Bug #883951
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Hello,

I have backported the indicated upstream patch to cyrus-imapd 2.5.10; see
attached.

This patch has been uploaded to Ubuntu to fix the build failure there. 
Please consider including it in Debian as well.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru 
cyrus-imapd-2.5.10/debian/patches/icaltimetype_is_utc_field_removal.patch 
cyrus-imapd-2.5.10/debian/patches/icaltimetype_is_utc_field_removal.patch
--- cyrus-imapd-2.5.10/debian/patches/icaltimetype_is_utc_field_removal.patch   
1969-12-31 16:00:00.0 -0800
+++ cyrus-imapd-2.5.10/debian/patches/icaltimetype_is_utc_field_removal.patch   
2018-03-19 21:25:27.0 -0700
@@ -0,0 +1,225 @@
+From 1966c22fc4249a1157a4d4c1224138ce78653514 Mon Sep 17 00:00:00 2001
+From: Ken Murchison 
+Date: Sat, 21 Oct 2017 19:04:08 -0400
+Subject: [PATCH] Account for the removal of icaltimetype.is_utc field in
+ upcoming libical
+Bug-Debian: https://bugs.debian.org/883951
+
+---
+ configure.ac |  5 +
+ imap/http_caldav.c   |  2 +-
+ imap/http_caldav_sched.c |  4 ++--
+ imap/http_tzdist.c   | 22 +++---
+ imap/ical_support.c  |  9 +
+ imap/ical_support.h  |  2 ++
+ imap/jmap_ical.c |  4 ++--
+ imap/xcal.c  |  4 ++--
+ 8 files changed, 34 insertions(+), 18 deletions(-)
+
+Index: cyrus-imapd-2.5.10/configure.ac
+===
+--- cyrus-imapd-2.5.10.orig/configure.ac
 cyrus-imapd-2.5.10/configure.ac
+@@ -1251,6 +1251,11 @@
+   AC_DEFINE(HAVE_RSCALE,[], [Build RSCALE support into 
httpd?]))
+   fi
+ 
++  AC_CHECK_MEMBER(icaltimetype.is_utc,
++  AC_DEFINE(ICALTIME_HAS_IS_UTC,[],
++  [Does icaltimetype have is_utc field?]),
++   [], [#include ])
++
+   LIBS="${saved_LIBS}"
+   CPPFLAGS="${saved_CPPFLAGS}"
+ fi
+Index: cyrus-imapd-2.5.10/imap/http_caldav.c
+===
+--- cyrus-imapd-2.5.10.orig/imap/http_caldav.c
 cyrus-imapd-2.5.10/imap/http_caldav.c
+@@ -2014,7 +2014,7 @@
+   goto fail;
+ }
+ 
+-tt.is_utc = 1;
++icaltime_set_utc(, 1);
+ return tt;
+ 
+   fail:
+Index: cyrus-imapd-2.5.10/imap/xcal.c
+===
+--- cyrus-imapd-2.5.10.orig/imap/xcal.c
 cyrus-imapd-2.5.10/imap/xcal.c
+@@ -113,8 +113,8 @@
+ static char str[21];
+ const char *fmt;
+ 
+-if (tt.is_date) fmt = "%04d-%02d-%02d";
+-else if (tt.is_utc) fmt = "%04d-%02d-%02dT%02d:%02d:%02dZ";
++if (icaltime_is_date(tt)) fmt = "%04d-%02d-%02d";
++else if (icaltime_is_utc(tt)) fmt = "%04d-%02d-%02dT%02d:%02d:%02dZ";
+ else fmt = "%04d-%02d-%02dT%02d:%02d:%02d";
+ 
+ snprintf(str, sizeof(str), fmt, tt.year, tt.month, tt.day,
+Index: cyrus-imapd-2.5.10/imap/http_timezone.c
+===
+--- cyrus-imapd-2.5.10.orig/imap/http_timezone.c
 cyrus-imapd-2.5.10/imap/http_timezone.c
+@@ -388,7 +388,7 @@
+   param = hash_lookup("changedsince", >req_qparams);
+   if (param) {
+   changedsince = icaltime_from_string(param->s);
+-  if (param->next || !changedsince.is_utc) {  /* once only, UTC */
++  if (param->next || !icaltime_is_utc(changedsince)) {  /* once only, 
UTC */
+   return json_error_response(txn, TZ_INVALID_CHANGEDSINCE,
+  param, );
+   }
+@@ -396,7 +396,7 @@
+ 
+   name = hash_lookup("tzid", >req_qparams);
+   if (name) {
+-  if (changedsince.is_utc) {
++  if (icaltime_is_utc(changedsince)) {
+   return json_error_response(txn, TZ_INVALID_TZID,
+  param, );
+   }
+@@ -589,7 +589,7 @@
+ 
+   /* Adjust DTSTART observance to UTC */
+   icaltime_adjust(, 0, 0, 0, -obs.offset_from);
+-  obs.onset.is_utc = 1;
++  icaltime_set_utc(, 1);
+ 
+   /* Check DTSTART vs window close */
+   if (!icaltime_is_null_time(end) &&
+@@ -651,7 +651,7 @@
+   if (!infinite) {
+   /* Adjust UNTIL to local time (for iterator) */
+   icaltime_adjust(, 0, 0, 0, obs.offset_from);
+-  rrule.until.is_utc = 0;
++  icaltime_set_utc(, 0);
+   }
+ 
+   if (trunc_dtstart) {
+@@ -675,7 +675,7 @@
+ 
+   /* Adjust observance to UTC */
+   icaltime_adjust(, 0,