Processed: cloning 917485, reassign -1 to release.debian.org, retitle -1 to nmu: ckermit_302-5.3 (stretch) ...

[Debian Bug Tracking System]

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

> clone 917485 -1
Bug #917485 [ckermit] ckermit: please rebuild Stretch against new OpenSSL
Bug 917485 cloned as bug 919043
> reassign -1 release.debian.org
Bug #919043 [ckermit] ckermit: please rebuild Stretch against new OpenSSL
Bug reassigned from package 'ckermit' to 'release.debian.org'.
No longer marked as found in versions ckermit/302-5.3.
Ignoring request to alter fixed versions of bug #919043 to the same values 
previously set
> retitle -1 nmu: ckermit_302-5.3 (stretch)
Bug #919043 [release.debian.org] ckermit: please rebuild Stretch against new 
OpenSSL
Changed Bug title to 'nmu: ckermit_302-5.3 (stretch)' from 'ckermit: please 
rebuild Stretch against new OpenSSL'.
> severity -1 normal
Bug #919043 [release.debian.org] nmu: ckermit_302-5.3 (stretch)
Severity set to 'normal' from 'grave'
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was a...@debian.org).
> usertags -1 binnmu
There were no usertags set.
Usertags are now: binnmu.
> tags -1 = stretch
Bug #919043 [release.debian.org] nmu: ckermit_302-5.3 (stretch)
Added tag(s) stretch; removed tag(s) security.
> block 917485 with -1
Bug #917485 [ckermit] ckermit: please rebuild Stretch against new OpenSSL
917485 was not blocked by any bugs.
917485 was not blocking any bugs.
Added blocking bug(s) of 917485: 919043
> thanks
Stopping processing here.

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

Processed: tagging 917535, tagging 917536, severity of 915680 is normal, tagging 915680 ...

[Debian Bug Tracking System]

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

> tags 917535 + stretch buster sid
Bug #917535 [debian-archive-keyring] debian-archive-keyring: ftp-master key for 
buster
Added tag(s) sid, buster, and stretch.
> tags 917536 + stretch buster sid
Bug #917536 [debian-archive-keyring] debian-archive-keyring: release key for 
buster
Added tag(s) sid, buster, and stretch.
> severity 915680 normal
Bug #915680 [piuparts] mender-client: broken symlink: /var/lib/mender -> 
/data/mender, target violates FHS
Severity set to 'normal' from 'serious'
> tags 915680 - moreinfo
Bug #915680 [piuparts] mender-client: broken symlink: /var/lib/mender -> 
/data/mender, target violates FHS
Removed tag(s) moreinfo.
> found 918808 2:13.0.2-4
Bug #918808 {Done: Thomas Goirand } [neutron-common] 
neutron-fwaas-common: fails to remove: IndentationError in 
"/usr/bin/neutron-plugin-manage", line 117
Marked as found in versions neutron/2:13.0.2-4.
> thanks
Stopping processing here.

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

Bug#917650: FTBFS: include/qi.h:104:29: error: duplicate 'const' declaration specifier [-Werror=duplicate-decl-specifier]

[Andreas Beckmann]

Followup-For: Bug #917650

Hi,

qi also FTBFS in stretch and jessie with different errors, just tested
on abel.d.o. I think the will show up on sid as well once compilation
proceeds a bit further.

The minimal fix would probably be dropping -Werror (and getting a NULL
definition), without cosmetic fixes (debhelper, standards-version), and
to rebuild the fixed package for stretch ~deb9u1 and jessie ~deb8u1.


stretch:

dh binary
dh: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_testdir
   dh_update_autotools_config
   dh_auto_configure
dh_auto_configure: Compatibility levels before 9 are deprecated (level 8 in use)
   debian/rules override_dh_auto_build
make[1]: Entering directory '/home/anbe/qi/qi-2013'
/usr/bin/make CPU=s3c2442 CROSS_COMPILE="" BUILD_BRANCH=debian 
BUILD_HEAD=2013-1.1
make[2]: Entering directory '/home/anbe/qi/qi-2013'
gcc -Wall -Werror -I include -g -c -Os -fno-strict-aliasing -mlong-calls 
-fno-common -ffixed-r8 -msoft-float -fno-builtin -ffreestanding -march=armv4t 
-mno-thumb-interwork -Wstrict-prototypes -DBUILD_HOST="abel" 
-DBUILD_VERSION="debian_2013-1.1" -DBUILD_DATE="2019-01-12T06:59:40+00:00" 
-DQI_CPU="s3c2442" -o src/cpu/s3c2442/start.o src/cpu/s3c2442/start.S
gcc -Wall -Werror -I include -g -c -Os -fno-strict-aliasing -mlong-calls 
-fno-common -ffixed-r8 -msoft-float -fno-builtin -ffreestanding -march=armv4t 
-mno-thumb-interwork -Wstrict-prototypes -DBUILD_HOST="abel" 
-DBUILD_VERSION="debian_2013-1.1" -DBUILD_DATE="2019-01-12T06:59:40+00:00" 
-DQI_CPU="s3c2442" -o src/cpu/s3c2442/lowlevel_init.o 
src/cpu/s3c2442/lowlevel_init.S
gcc -Wall -Werror -I include -g -c -Os -fno-strict-aliasing -mlong-calls 
-fno-common -ffixed-r8 -msoft-float -fno-builtin -ffreestanding -march=armv4t 
-mno-thumb-interwork -Wstrict-prototypes -DBUILD_HOST="abel" 
-DBUILD_VERSION="debian_2013-1.1" -DBUILD_DATE="2019-01-12T06:59:40+00:00" 
-DQI_CPU="s3c2442" -o src/utils-phase2.o src/utils-phase2.c
gcc -Wall -Werror -I include -g -c -Os -fno-strict-aliasing -mlong-calls 
-fno-common -ffixed-r8 -msoft-float -fno-builtin -ffreestanding -march=armv4t 
-mno-thumb-interwork -Wstrict-prototypes -DBUILD_HOST="abel" 
-DBUILD_VERSION="debian_2013-1.1" -DBUILD_DATE="2019-01-12T06:59:40+00:00" 
-DQI_CPU="s3c2442" -o src/memory-test.o src/memory-test.c
gcc -Wall -Werror -I include -g -c -Os -fno-strict-aliasing -mlong-calls 
-fno-common -ffixed-r8 -msoft-float -fno-builtin -ffreestanding -march=armv4t 
-mno-thumb-interwork -Wstrict-prototypes -DBUILD_HOST="abel" 
-DBUILD_VERSION="debian_2013-1.1" -DBUILD_DATE="2019-01-12T06:59:40+00:00" 
-DQI_CPU="s3c2442" -o src/crc32.o src/crc32.c
gcc -Wall -Werror -I include -g -c -Os -fno-strict-aliasing -mlong-calls 
-fno-common -ffixed-r8 -msoft-float -fno-builtin -ffreestanding -march=armv4t 
-mno-thumb-interwork -Wstrict-prototypes -DBUILD_HOST="abel" 
-DBUILD_VERSION="debian_2013-1.1" -DBUILD_DATE="2019-01-12T06:59:40+00:00" 
-DQI_CPU="s3c2442" -o src/blink_led.o src/blink_led.c
gcc -Wall -Werror -I include -g -c -Os -fno-strict-aliasing -mlong-calls 
-fno-common -ffixed-r8 -msoft-float -fno-builtin -ffreestanding -march=armv4t 
-mno-thumb-interwork -Wstrict-prototypes -DBUILD_HOST="abel" 
-DBUILD_VERSION="debian_2013-1.1" -DBUILD_DATE="2019-01-12T06:59:40+00:00" 
-DQI_CPU="s3c2442" -o src/ctype.o src/ctype.c
gcc -Wall -Werror -I include -g -c -Os -fno-strict-aliasing -mlong-calls 
-fno-common -ffixed-r8 -msoft-float -fno-builtin -ffreestanding -march=armv4t 
-mno-thumb-interwork -Wstrict-prototypes -DBUILD_HOST="abel" 
-DBUILD_VERSION="debian_2013-1.1" -DBUILD_DATE="2019-01-12T06:59:40+00:00" 
-DQI_CPU="s3c2442" -o src/phase2.o src/phase2.c
src/phase2.c: In function 'do_params':
src/phase2.c:242:2: error: this 'if' clause does not guard... 
[-Werror=misleading-indentation]
  if (this_kernel->commandline_append)
  ^~
src/phase2.c:245:3: note: ...this statement, but the latter is misleadingly 
indented as if it is guarded by the 'if'
   if (commandline_rootfs_append[0])
   ^~
In file included from src/phase2.c:29:0:
src/phase2.c: At top level:
include/image.h:367:13: error: inline function 'image_print_contents_noindent' 
declared but never defined [-Werror]
 inline void image_print_contents_noindent (image_header_t *hdr);
 ^
include/image.h:366:13: error: inline function 'image_print_contents' declared 
but never defined [-Werror]
 inline void image_print_contents (image_header_t *hdr);
 ^~~~
cc1: all warnings being treated as errors
Makefile:69: recipe for target 'src/phase2.o' failed
make[2]: *** [src/phase2.o] Error 1
make[2]: Leaving directory '/home/anbe/qi/qi-2013'
debian/rules:8: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/home/anbe/qi/qi-2013'
debian/rules:6: recipe for target 'binary' failed 


jessie:

dh binary
   dh_testdir
   

Bug#917655: biojava4-live: FTBFS (cannot find symbol JAXBContext)

[tony mancill]

On Fri, Jan 11, 2019 at 10:26:58PM +0100, Andreas Tille wrote:
> Control: tags -1 help upstream
> 
> Hi,
> 
> I've commited a new minor upstream version to Git but the problem exists
> also in this version.  I've asked at debian-java list for help[1]

Hello Andreas,

I took a quick look at this and was able to resolve the build problems
by dropping the references to the java.se.ee. module and adding
jaxb-impl and jaxb-api JARs to the classpath.

It might not be the cleanest way - strictly speaking, you should only
need the jaxb-api JAR during the build and only the jaxb-impl on the
classpath while running tests.

Attached are a set of commits that let the package build for me locally.

Cheers,
tony
From f8f5c72b866718e05811b33f8445ee311228da12 Mon Sep 17 00:00:00 2001
From: tony mancill 
Date: Fri, 11 Jan 2019 20:17:27 -0800
Subject: [PATCH 1/3] Add build-dep on libjaxb-api-java and libjaxb-java

---
 debian/control | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index 1f6cc04..71257a0 100644
--- a/debian/control
+++ b/debian/control
@@ -28,7 +28,9 @@ Build-Depends-Indep: libcommons-dbcp-java,
  liblog4j2-java,
  libslf4j-java,
  libxmlunit-java,
- libjgrapht-java
+ libjgrapht-java,
+ libjaxb-api-java,
+ libjaxb-java
 Standards-Version: 4.3.0
 Vcs-Browser: https://salsa.debian.org/med-team/biojava4-live
 Vcs-Git: https://salsa.debian.org/med-team/biojava4-live.git
-- 
2.20.1

From ac9fad6e89d9d5ff8501a05da46b26bd158af5f8 Mon Sep 17 00:00:00 2001
From: tony mancill 
Date: Fri, 11 Jan 2019 20:25:49 -0800
Subject: [PATCH 2/3] Add jaxb-api and jaxb-impl JARs to classpaths in
 debian/build.xml

---
 debian/build.xml | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/debian/build.xml b/debian/build.xml
index 250c143..fae837d 100644
--- a/debian/build.xml
+++ b/debian/build.xml
@@ -28,7 +28,7 @@
 	
 		
 	
-	
+	
 
 	
 
@@ -52,6 +52,8 @@
 
 
 
+
+
 			
 			
 
-- 
2.20.1

From c25549fd76d3378cad50029a6718353858f6cce4 Mon Sep 17 00:00:00 2001
From: tony mancill 
Date: Fri, 11 Jan 2019 20:36:27 -0800
Subject: [PATCH 3/3] Drop --add-modules java.se.ee from javadoc task

---
 debian/build.xml | 16 +++-
 1 file changed, 3 insertions(+), 13 deletions(-)

diff --git a/debian/build.xml b/debian/build.xml
index fae837d..406f208 100644
--- a/debian/build.xml
+++ b/debian/build.xml
@@ -75,18 +75,9 @@
 	
 
 		
-
-
-
-http://java.sun.com/j2se/1.6.0/docs/api/"/>
-
-
-
-
-http://java.sun.com/j2se/1.6.0/docs/api/"/>
-
-
-
+
+http://java.sun.com/j2se/1.6.0/docs/api/"/>
+
 	
 	
 	
@@ -130,7 +121,6 @@
 
 
 
-  
   
   
   
-- 
2.20.1



signature.asc
Description: PGP signature

Bug#874727: marked as done (libcoin80v5: Program using libcoin80v5 and any other library that uses lebexpat1 segfaults.)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 23:00:04 -0600
with message-id 
and subject line 
has caused the Debian Bug report #874727,
regarding libcoin80v5: Program using libcoin80v5 and any other library that 
uses lebexpat1 segfaults.
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.)


-- 
874727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874727
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcoin80v5
Version: 3.1.4~abc9f50+dfsg1-2
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

Due to the change in libexpat1 (since 2.2.0, currently at 2.2.3) the included 
copy of it in libcoin results in segfaults of any program that uses libexpat1. 
Specifically any program that uses xml from python and links against libcoin 
will segfault.

The stacktrace looks like it is a problem with libexpat1 leading to a segfault 
in XML_SetHashSalt - however looking at that function there is no way it could 
possibly segfault - unless of course the provided XMLParser pointer does not 
actually point to what expat expects to be an XMLParser - which is indeed the 
case because the XMLParser instance was created by a call into lobcoin which is 
still on libexpat 2.2.0.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing'), (750, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages libcoin80v5 depends on:
ii  libc6 2.24-17
ii  libgcc1   1:7.2.0-3
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libice6   2:1.0.9-2
ii  libsm62:1.2.2-1+b3
ii  libstdc++67.2.0-3
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1+b2

libcoin80v5 recommends no packages.

Versions of packages libcoin80v5 suggests:
ii  libbz2-1.0 1.0.6-8.1
ii  libfreetype6   2.8-0.2
pn  libopenal0a
ii  libsimage-dev  1.7.1~2c958a6.dfsg-4
ii  zlib1g 1:1.2.8.dfsg-5

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.0.0~CMake~6f54f1602475+ds1-1--- End Message ---

Bug#919037: xmms2-scrobbler: Non-working maintainer address

[Scott Kitterman]

Package: xmms2-scrobbler
Version: 0.4.0-4
Severity: serious
Justification: Policy 3.3

A working maintainer address is required:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  r...@debian.org
Unrouteable address

Reporting-MTA: dns; muffat.debian.org

Action: failed
Final-Recipient: rfc822;r...@debian.org
Status: 5.0.0

Scott K

Processed: merging 919033 919034

[Debian Bug Tracking System]

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

> merge 919033 919034
Bug #919033 [src:zeitgeist] src:zeitgeist: Non-functional maintainer address
Bug #919034 [src:zeitgeist] src:zeitgeist: Non-functional maintainer address
Merged 919033 919034
> thanks
Stopping processing here.

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

Bug#919036: libopenexr24 botched upload issue also affects libopenexr23 and libilmbase23

[積丹尼 Dan Jacobson]

Package: libopenexr23
Version: 2.3.0-3
Severity: grave

Please replace these. I had to
Marking version 2.3.0-3 of package libopenexr23 as forbidden
Marking version 2.3.0-3 of package libilmbase23 as forbidden
and
install libopenexr23=2.2.1-4 libilmbase23=2.2.1-2
else gimp won't start, etc.

Bug#916079: hyperic-sigar FTBFS with glibc 2.28

[Logan Rosen]

Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * d/p/ftbfs-glibc-2.28.diff: Fix FTBFS against glibc 2.28.

Thanks for considering the patch.

Logan Rosen

-- System Information:
Debian Release: buster/sid
  APT prefers cosmic-updates
  APT policy: (500, 'cosmic-updates'), (500, 'cosmic-security'), (500, 
'cosmic'), (400, 'cosmic-proposed'), (100, 'cosmic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-13-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru hyperic-sigar-1.6.4+dfsg/debian/patches/ftbfs-glibc-2.28.diff 
hyperic-sigar-1.6.4+dfsg/debian/patches/ftbfs-glibc-2.28.diff
--- hyperic-sigar-1.6.4+dfsg/debian/patches/ftbfs-glibc-2.28.diff   
1969-12-31 19:00:00.0 -0500
+++ hyperic-sigar-1.6.4+dfsg/debian/patches/ftbfs-glibc-2.28.diff   
2019-01-11 22:38:38.0 -0500
@@ -0,0 +1,22 @@
+Description: Fix FTBFS against glibc 2.28
+Author: Logan Rosen 
+Forwarded: https://github.com/hyperic/sigar/pull/127
+Last-Update: 2019-01-11
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/os/linux/linux_sigar.c
 b/src/os/linux/linux_sigar.c
+@@ -22,8 +22,13 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ 
++#ifdef __GNU_LIBRARY__
++#include 
++#endif
++
+ #include "sigar.h"
+ #include "sigar_private.h"
+ #include "sigar_util.h"
diff -Nru hyperic-sigar-1.6.4+dfsg/debian/patches/series 
hyperic-sigar-1.6.4+dfsg/debian/patches/series
--- hyperic-sigar-1.6.4+dfsg/debian/patches/series  2014-11-03 
00:25:28.0 -0500
+++ hyperic-sigar-1.6.4+dfsg/debian/patches/series  2019-01-11 
22:36:13.0 -0500
@@ -3,3 +3,4 @@
 0003-bindings-java-Use-sane-name-for-JNI-library.patch
 0004-make-the-package-compile-on-MIPS.patch
 no-m64-mips-arm.diff
+ftbfs-glibc-2.28.diff

Processed: Re: hyperic-sigar FTBFS with glibc 2.28

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #916079 [src:hyperic-sigar] hyperic-sigar FTBFS with glibc 2.28
Added tag(s) patch.

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

Bug#919035: elpa-persp-projectile: broken with recent elpa-perspective

[Sean Whitton]

Package: elpa-persp-projectile
Version: 1:0.2.0-2
Severity: grave

`perspectives-hash' is now a function that returns something which does
not pass `hash-table-p'.  So patching is required.

Since this package is up for adoption, I won't be doing that patching
myself.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#919034: src:zeitgeist: Non-functional maintainer address

[Scott Kitterman]

Package: src:zeitgeist
Version: 1.0.1-0.3
Severity: serious
Justification: Policy 3.3

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  rai...@ubuntu.com
host mx.canonical.com [91.189.95.10]
SMTP error from remote mail server after RCPT TO::
550 5.1.1 : Recipient address rejected:
User unknown in virtual alias table

A working maintainer address is required.

Scott K

Bug#919033: src:zeitgeist: Non-functional maintainer address

[Scott Kitterman]

Package: src:zeitgeist
Version: 1.0.1-0.3
Severity: serious
Justification: Policy 3.3

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  rai...@ubuntu.com
host mx.canonical.com [91.189.95.10]
SMTP error from remote mail server after RCPT TO::
550 5.1.1 : Recipient address rejected:
User unknown in virtual alias table

A working maintainer address is required.

Scott K

Bug#919029: grub-pc: meaningless message "RUB boot loader was previously installed..."

[Vincent Lefevre]

On 2019-01-12 01:49:10 +0100, Vincent Lefevre wrote:
> Text is missing on the left. Moreover, I don't know why I get such
> a message (I haven't changed anything).

For the message itself, it is probably a consequence of this bug:

  https://github.com/systemd/systemd/issues/11264

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: Re: Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #918764 {Done: Axel Beckert } [udev] udev: "udevadm 
control --reload-rules" kills all processes except init
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 240-3.
> found -1 240-3
Bug #918764 [udev] udev: "udevadm control --reload-rules" kills all processes 
except init
Marked as found in versions systemd/240-3.

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

Bug#918764: udev: "udevadm control --reload-rules" kills all processes except init

[Axel Beckert]

Control: reopen -1
Control: found -1 240-3

Hi Michael,

Michael Biebl wrote:
> > I luckily can no more reproduce this with udev 240-3 and kernel
> > 4.19.13-1 or 4.20-1~exp1.
> 
> Ok, thanks for testing.

*sigh* I'm sorry to say, but it just happened again with udev 240-3
and kernel 4.20-1~exp1.

> > Since I can no more reproduce this with the versions above and I'm
> > also affected by (parts of) #918590 which make every reboot taking
> > about 8 to 9 minutes due to waiting for LVM (
> 
> If I would have to guess, I'd say it's another instance of
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908796
> 
> You could try to add a sleep 5 at around line 179 in /etc/init.d/udev
> right before the udevadm calls.

Did that. And since the grub update (which calls LVM commands en
masse) took ages, I thought that I can maybe speed that up by
restarting udev with the modified init script:

"service udev restart" clearly didn't call "sleep 5", exited
successfully within a second or so.

So I did a "service udev stop" and a few seconds later a "service udev
start". After that 5 seconds of nothing, I got about a dozen lines of
warnings (something about mtp devices with I/O errors, maybe related
to my USB card reader without cards in it) and then was suddenly back
on my console login's getty.

Afterwards only init and the gettys were running.

Not sure if the still running grub package configuration triggered it
or part of the udev init script.

Another "service udev stop" and "service udev start" though didn't
trigger the issue again. Will try "udevadm control --reload-rules"
once grub is finished updating and then will reboot, see if that
changes anything (startup delays or process killings) and report more
details.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: Re: grub-pc: meaningless message "RUB boot loader was previously installed..."

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #919029 [grub-pc] grub-pc: meaningless message "RUB boot loader was 
previously installed..."
Severity set to 'grave' from 'important'

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

Processed: spyder: 1

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #919000 [spyder3] Missing distribution 'keyring'
Severity set to 'normal' from 'critical'

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

Bug#919000: spyder: 1

[Drew Parsons]

Package: spyder
Version: 3.3.2+dfsg1-1
Followup-For: Bug #919000
Control: severity -1 normal

It's hardly critical.  Please don't overinflate bug severities.

https://www.debian.org/Bugs/Developer#severities

Bug#918855: marked as done (debconf: Impossible to upgrade from 1.5.59 -> 1.5.69)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 15:26:11 -0800
with message-id <87wona6ajw@secretsauce.net>
and subject line Re: Bug#918855: debconf: Impossible to upgrade from 1.5.59 -> 
1.5.69
has caused the Debian Bug report #918855,
regarding debconf: Impossible to upgrade from 1.5.59 -> 1.5.69
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.)


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

Hi.

I'm running a mostly-up-to-date Debian/sid system. I just tried updating
it, and it barf at me when I ask it to update debconf:


root@machine:~# aptitude install debconf 

The following NEW packages will be installed:
  libauthen-sasl-perl{a} libdata-dump-perl{a} libencode-locale-perl{a} 
libfile-listing-perl{a} libfont-afm-perl{a} libgdbm-compat4{a} 
libhtml-form-perl{a} libhtml-format-perl{a} libhtml-parser-perl{a} 
libhtml-tagset-perl{a} 
  libhtml-tree-perl{a} libhttp-cookies-perl{a} libhttp-daemon-perl{a} 
libhttp-date-perl{a} libhttp-message-perl{a} libhttp-negotiate-perl{a} 
libio-html-perl{a} libio-socket-ssl-perl{a} liblwp-mediatypes-perl{a} 
  liblwp-protocol-https-perl{a} libmailtools-perl{a} libnet-http-perl{a} 
libnet-smtp-ssl-perl{a} libnet-ssleay-perl{a} libperl5.28{a} 
libtext-unidecode-perl{a} libtry-tiny-perl{a} libwww-perl{a} 
libwww-robotrules-perl{a} 
  libxml-libxml-perl{a} libxml-namespacesupport-perl{a} 
libxml-parser-perl{a} libxml-sax-base-perl{a} libxml-sax-expat-perl{a} 
libxml-sax-perl{a} perl-modules-5.28{ab} perl-openssl-defaults{a} 
python3-apt{a} python3-debconf{a} 
  tex-common{a} 
The following packages will be upgraded:
  apt-listchanges debconf perl perl-base{b} texinfo 
5 packages upgraded, 40 newly installed, 0 to remove and 37 not upgraded.
Need to get 0 B/12.8 MB of archives. After unpacking 49.9 MB will be used.
The following packages have unmet dependencies:
 perl-base : Breaks: perl-modules (< 5.28.1~) but 5.20.1-1 is installed
 debconf-i18n : Depends: debconf (= 1.5.59) but 1.5.69 is to be installed
 perl-modules-5.28 : Conflicts: perl-modules (< 5.22.0~) but 5.20.1-1 is 
installed
 libfcgi-perl : Depends: perlapi-5.20.0 which is a virtual package, 
provided by:
 - perl-base (5.20.1-1), but 5.28.1-3 is to be 
installed

 liblocale-gettext-perl : PreDepends: perlapi-5.20.0 which is a virtual 
package, provided by:
  - perl-base (5.20.1-1), but 5.28.1-3 
is to be installed

 libperl5.20 : Depends: perl-base (= 5.20.1-1) but 5.28.1-3 is to be 
installed
 libtext-soundex-perl : Depends: perlapi-5.20.0 which is a virtual package, 
provided by:
 - perl-base (5.20.1-1), but 5.28.1-3 is to 
be installed

 libio-pty-perl : Depends: perlapi-5.20.0 which is a virtual package, 
provided by:
   - perl-base (5.20.1-1), but 5.28.1-3 is to be 
installed

 libtext-iconv-perl : Depends: perlapi-5.20.0 which is a virtual package, 
provided by:
   - perl-base (5.20.1-1), but 5.28.1-3 is to 
be installed

 libtext-charwidth-perl : Depends: perlapi-5.20.0 which is a virtual 
package, provided by:
   - perl-base (5.20.1-1), but 5.28.1-3 is 
to be installed

The following actions will resolve these dependencies:

  Remove the following packages:  
1)  libperl5.20 [5.20.1-1 (now)]  
2)  perl-modules [5.20.1-1 (now)] 

  Install the following packages: 
3)  libpython3.7 [3.7.2-1 (unstable)] 
4)  libtcl8.6 [8.6.9+dfsg-1 (unstable)]   

  Upgrade the following packages: 
5)  debconf-i18n [1.5.59 (now) -> 1.5.69 (unstable)]  
6)  libfcgi-perl [0.77-1+b1 (now) -> 0.78-2+b3 (unstable)]
7)  libio-pty-perl [1:1.08-1+b4 (now) -> 1:1.08-1.1+b5 (unstable)]
8)  liblocale-gettext-perl [1.05-8+b1 (now) -> 1.07-3+b4 (unstable)]  
9)  libtext-charwidth-perl [0.04-7+b3 (now) -> 0.04-7.1+b1 (unstable)]
10) libtext-iconv-perl [1.7-5+b2 (now) -> 1.7-5+b7 (unstable)]
11) libtext-soundex-perl [3.4-1+b2 (now) -> 

Processed: severity of 918993 is serious

[Debian Bug Tracking System]

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

> severity 918993 serious
Bug #918993 [sagemath-jupyter] sagemath-jupyter: Invalid path to sage kernel 
makes notebook unusable
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#915290: strace FTBFS with glibc 2.28

[Andreas Henriksson]

On Tue, Dec 04, 2018 at 02:53:22AM +, Steve McIntyre wrote:
> ACK, thanks for the pointer. I'm a few releases behind due to lack of
> time. Hoping to get that fixed shortly...

For your convenince I've pushed an updated version to branches to salsa:
wip/master
wip/upstream
wip/pristine-tar

If you don't have time to review, merge, upload I'm happy to help out
with a NMU. Just tell me about it

Regards,
Andreas Henriksson

Processed: severity of 919001 is serious

[Debian Bug Tracking System]

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

> severity 919001 serious
Bug #919001 [emacs-gtk] emacs-gtk: fails to upgrade to 1.26.1+1-3
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#918767: marked as done (rivet FTBFS with yaml-cpp 0.6.2)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 23:37:00 +
with message-id 
and subject line Bug#918767: fixed in rivet 1.8.3-3
has caused the Debian Bug report #918767,
regarding rivet FTBFS with yaml-cpp 0.6.2
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.)


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

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

...
In file included from /usr/include/c++/8/array:35,
 from /usr/include/yaml-cpp/node/convert.h:10,
 from /usr/include/yaml-cpp/yaml.h:18,
 from AnalysisInfo.cc:7:
/usr/include/c++/8/bits/c++0x_warning.h:32:2: error: #error This file requires 
compiler and library support for the ISO C++ 2011 standard. This support must 
be enabled with the -std=c++11 or -std=gnu++11 compiler options.
 #error This file requires compiler and library support \


Fix attached.
Description: Don't force a lower C++ standard with -ansi
 This causes FTBFS with yaml-cpp 0.6.2.
Author: Adrian Bunk 

--- rivet-1.8.3.orig/configure.ac
+++ rivet-1.8.3/configure.ac
@@ -316,7 +316,6 @@ AM_CPPFLAGS="$AM_CPPFLAGS -I\$(BOOSTINCP
 AM_CPPFLAGS="$AM_CPPFLAGS -I\$(HEPMCINCPATH)"
 AM_CPPFLAGS="$AM_CPPFLAGS -I\$(FASTJETINCPATH)"
 AC_CEDAR_CHECKCXXFLAG([-pedantic], [AM_CXXFLAGS="$AM_CXXFLAGS -pedantic"])
-AC_CEDAR_CHECKCXXFLAG([-ansi], [AM_CXXFLAGS="$AM_CXXFLAGS -ansi"])
 AC_CEDAR_CHECKCXXFLAG([-Wall], [AM_CXXFLAGS="$AM_CXXFLAGS -Wall"])
 AC_CEDAR_CHECKCXXFLAG([-Wno-long-long], [AM_CXXFLAGS="$AM_CXXFLAGS 
-Wno-long-long"])
 AC_CEDAR_CHECKCXXFLAG([-Wno-format], [AM_CXXFLAGS="$AM_CXXFLAGS -Wno-format"])
--- End Message ---
--- Begin Message ---
Source: rivet
Source-Version: 1.8.3-3

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

Debian distribution maintenance software
pp.
Simon Quigley  (supplier of updated rivet 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: Fri, 11 Jan 2019 17:07:18 -0600
Source: rivet
Binary: rivet rivet-user-manual rivet-reference rivet-plugins rivet-plugins-dev 
rivet-plugins-doc rivet-plugins-data librivet11v5 librivet-dev python-rivet
Architecture: source
Version: 1.8.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Simon Quigley 
Description:
 librivet-dev - Development files of Rivet
 librivet11v5 - Run-time library of Rivet
 python-rivet - Python bindings of Rivet
 rivet  - Robust Independent Validation of Experiment and Theory
 rivet-plugins - Analysis plugins of Rivet
 rivet-plugins-data - Data files of Rivet analysis plugins
 rivet-plugins-dev - Template generator of Rivet analysis plugin
 rivet-plugins-doc - HTML documentation for Rivet analysis plugins
 rivet-reference - Rivet code reference
 rivet-user-manual - Robust Independent Validation of Experiment and Theory - 
User Man
Closes: 918767
Changes:
 rivet (1.8.3-3) unstable; urgency=medium
 .
   [ Simon Quigley ]
   * Team upload.
 .
   [ Christopher James Halse Rogers ]
   * d/rules: Pass -std=c++11 to fix build with new yaml-cpp (Closes: #918767)
Checksums-Sha1:
 d1b47ce8b9b30b46b5a3d55277946f2fe04bf75a 2769 rivet_1.8.3-3.dsc
 e622720b115e1421a21cc08795c878dab77017e9 18732 rivet_1.8.3-3.debian.tar.xz
 3720d9e03772c959fee93729a2683a11cb18113a 6516 rivet_1.8.3-3_source.buildinfo
Checksums-Sha256:
 52dea6f0fa40b66f7c4ff9790c1b6611374d765afef17f86fe20215f564b084c 2769 
rivet_1.8.3-3.dsc
 45b6f2d04bb02cdfe72aa1de6cedb1cc188d77af4d7b5db03de23025ac67cc58 18732 
rivet_1.8.3-3.debian.tar.xz
 14ed3c28aaaea6a46510eaf4c1b19e78361fc86a7995fea6c68b3c135f1e5b81 6516 
rivet_1.8.3-3_source.buildinfo
Files:
 3f607b1ca010ce0d67f23b1c4011b062 2769 science optional rivet_1.8.3-3.dsc
 f7a0bbd5aca187292e19f62a2a57aa39 18732 science optional 
rivet_1.8.3-3.debian.tar.xz
 0168bb9d9226ec7c425377172145a590 6516 science optional 
rivet_1.8.3-3_source.buildinfo

-BEGIN PGP 

Bug#918560: marked as done (csound-manual FTBFS: IndexError: tuple index out of range)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 23:34:37 +
with message-id 
and subject line Bug#918560: fixed in csound-manual 1:6.12.0~dfsg-2
has caused the Debian Bug report #918560,
regarding csound-manual FTBFS: IndexError: tuple index out of range
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.)


-- 
918560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: csound-manual
Version: 1:6.12.0~dfsg-1
Severity: serious
Tags: ftbfs

Some recent change in unstable makes csound-manual FTBFS:

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

...
Traceback (most recent call last):
  File "csd2docbook.py", line 373, in 
CsoundScoreLexer.tokens['root'][3] = (stateTuple[0], Token.Name.Builtin, 
stateTuple[2])
IndexError: tuple index out of range
make[2]: *** [Makefile:699: examples-xml/stamp] Error 1
--- End Message ---
--- Begin Message ---
Source: csound-manual
Source-Version: 1:6.12.0~dfsg-2

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

Debian distribution maintenance software
pp.
Felipe Sateler  (supplier of updated csound-manual 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: Fri, 11 Jan 2019 20:08:47 -0300
Source: csound-manual
Binary: csound-doc
Architecture: source
Version: 1:6.12.0~dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Felipe Sateler 
Description:
 csound-doc - documentation for csound
Closes: 918560
Changes:
 csound-manual (1:6.12.0~dfsg-2) unstable; urgency=medium
 .
   * Fix FTBFS due to newer python-pygments.
 Score statements are now a 2-tuple instead of a 3-tuple (Closes: #918560)
Checksums-Sha1:
 f4f5caa972c31f4a770216d282051d1c5bbae8c1 2237 csound-manual_6.12.0~dfsg-2.dsc
 03ba5184a8925fcbb64593e2aba63619f5d05714 6412 
csound-manual_6.12.0~dfsg-2.debian.tar.xz
Checksums-Sha256:
 befb4883b55e789b6460fcfe79c0313513452970ace7b17546015711817b26ac 2237 
csound-manual_6.12.0~dfsg-2.dsc
 b0f69415c85db06d4fdef6881997390e47a13dca4d3447584f01c0bee0c433a9 6412 
csound-manual_6.12.0~dfsg-2.debian.tar.xz
Files:
 9c286686ab46229b0f283292d21f3456 2237 doc optional 
csound-manual_6.12.0~dfsg-2.dsc
 7bae1ada51dcb1e43dfa84201d7c218f 6412 doc optional 
csound-manual_6.12.0~dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEIY7gNiAzyHtsE1+ko7q64kCN1s8FAlw5IlgUHGZzYXRlbGVy
QGRlYmlhbi5vcmcACgkQo7q64kCN1s+Blg/8C21KMa3jiBvi6nnm4Pq+wwNxQmiq
HWC8PIYX8Tk9nRVR3HDnZX069k4Hu/93lcuEycQYW2+wWhRJ4vrfBL3vFrS6mVUR
7Am8nOPQLU6MGeI02g5HsxppPMGuA9us5qXXUMWIq9pOOKtRa//tqyY/AFfdxTlJ
t70fGd8QYHzGdRvOrNBAW7llIgce1pOsUH41FTlwp0NXjluGHjelDmVXOZFDPU+F
RCUPpvXRt6cL/y2mk44kWBWI6idmKUw2H5A0QinjQ5YrRE5vKwcJ79NxfO3xZHkW
eOKROJd7/eA/GDCCf8wIdIn5v333XHX20o0SokigrUV6ToAx7os7XdTB42jPGxLQ
Lzcrfbai2eoOeuI8jO6Ag+wux28kHobDtua9S1Q9dQCH4mLhJAt9GlyD5N5TgUmk
GlZ7LlfsGaBvtu/5aSclBvQas77fQ96y4v19VOpkmt8OcudMPhNhfdNARWyxfsSn
qf+7jf61FNZHqHlIx4RJpUFG3I/0xedXEqWdYnNWYkjZWPOrODSLLPw8VS0qDFQl
DdBX3HMELxjrBHMHeN+QMqHXXdjSOwiAi/whX8TI/ODeU06C2LfKrk3/MxxtBCF9
7sH5a6Q3trFGMMp5Y1Gho25sA2lOInYXH2A0hQw8wPDxzcC/Qy0LWygygPIrEEpC
SyFCXwDQWOaUdRQ=
=PLFq
-END PGP SIGNATURE End Message ---

Processed: bug 918779 is forwarded to https://github.com/puppetlabs/r10k/issues/853

[Debian Bug Tracking System]

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

> forwarded 918779 https://github.com/puppetlabs/r10k/issues/853
Bug #918779 [r10k] r10k: uninitialized constant Cri::Error
Set Bug forwarded-to-address to 'https://github.com/puppetlabs/r10k/issues/853'.
> thanks
Stopping processing here.

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

Bug#883778: marked as done (problems building guile-2.0 on armel)

[Debian Bug Tracking System]

Your message dated Sat, 12 Jan 2019 01:06:28 +0200
with message-id <20190111230628.GA2487@localhost>
and subject line Re: Bug#883778: problems building guile-2.0 on armel
has caused the Debian Bug report #883778,
regarding problems building guile-2.0 on armel
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.)


-- 
883778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: guile-2.0
Version: 2.0.13+1-5
Severity: serious

Hi.

Putting this information into the BTS for posterity...

Trying to build guile-2.0/armel is currently crashing our buildds and
porter box. See

  https://buildd.debian.org/status/package.php?p=guile-2.0=sid

at the moment - hartmann tried to build the package, but
crashed. Adrian Bunk says he's tried to build it on abel too, and that
caused the same issue. I've just tried a local rebuild here on the
same hardware as the buildds (Marvell Armada XP) and I see the same
issue. Unfortunately, there's no diagnostic output I can share. The
machine simply died overnight without even any kernel messages to show
for it.

I was also running top and displaying CPU temperature in a loop during
the build, with no problems shown at the point of failure.

Interestingly, in armhf mode the package builds just fine on the same
type of hardware (built ok on hoiby). Wondering what on earth is going
on...


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

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

Versions of packages guile-2.0 depends on:
ii  guile-2.0-libs  2.0.13+1-4

guile-2.0 recommends no packages.

Versions of packages guile-2.0 suggests:
pn  guile-2.0-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, Jan 02, 2019 at 07:42:44PM -0600, Rob Browning wrote:
> Kurt Roeckx  writes:
> 
> > I've enabled guile-2.0 and 2.2 again on armel yesterday, and it
> > seems to build without issues now.
> 
> Nice!  And thanks much.

guile-2.0, guile-2.2 and many reverse build dependencies have been on 
the buildds, and not a single buildd was killed and required someone
to push the reset button.

I'm closing this bug since it seems the problem has gone away.

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#892348: marked as done (xmlroff: Please use 'pkg-config' to find FreeType 2)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 23:16:19 +
with message-id 
and subject line Bug#892348: fixed in xmlroff 0.6.2-1.4
has caused the Debian Bug report #892348,
regarding xmlroff: Please use 'pkg-config' to find FreeType 2
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.)


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

Dear Maintainer,

The next release of libfreetype6-dev will *not* ship
`freetype-config', as the script has now been deprecated in favour of
`pkg-config'.

This is an upstream change:

"Use of the `freetype-config' script to get compilation and

linking options is deprecated since it doesn't support

cross-compiling, among other deficiencies. Instead, you should

use the `pkg-config' interface." [1]

Please use `pkg-config' to detect the FreeType 2 headers and
libraries in xmlroff.

If this bug is not resolved prior to the release of FreeType 2.9.1,
your package may FTBFS.

Thank you

[1]
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=b0
a93839b52818abbfe9b4c8755b4aa0f5232063 
--- End Message ---
--- Begin Message ---
Source: xmlroff
Source-Version: 0.6.2-1.4

We believe that the bug you reported is fixed in the latest version of
xmlroff, 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 Henriksson  (supplier of updated xmlroff 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: Fri, 11 Jan 2019 22:44:04 +0100
Source: xmlroff
Binary: xmlroff
Architecture: source
Version: 0.6.2-1.4
Distribution: unstable
Urgency: medium
Maintainer: Debian XML/SGML Group 
Changed-By: Andreas Henriksson 
Description:
 xmlroff- XSL formatter mainly for DocBook
Closes: 892348
Changes:
 xmlroff (0.6.2-1.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/watch: point at new github repo location.
   * Add debian/patches/pkg-config.patch from upstream commit fcc36764a5f
 - the orig tarball seems to be repacked compared to whats available
   on github and there are no instructions, so backport commit instead
   of updating to new release for simplicity.
 (Closes: #892348)
   * Add pkg-config build-dependency for above.
   * debian/source/format: 3.0 (quilt)
   * debian/patches/xmlroff-package-changes.patch:
 - the upstream source was "patched" and the changes made now lives
   in this separate patch file for visibility.
   * Drop deprecated DM-Upload-Allowed field.
   * Bump dh compat to 9
 - 5 is deprecated
   * Replace autotools-dev build-dependency with dh-autoreconf
   * debian/rules: include autoreconf.mk cdbs rules
Checksums-Sha1:
 5f824f8e276976d7eb12f4f3230e1d2f7f9533a6 2140 xmlroff_0.6.2-1.4.dsc
 73172ab9b92da533557004b948938712813270b3 8632 xmlroff_0.6.2-1.4.debian.tar.xz
 07b49926e63fb08c11810a046d1757fdcf06083e 11076 
xmlroff_0.6.2-1.4_amd64.buildinfo
Checksums-Sha256:
 fc0246d5a8d2e6239a20efcbc9c66f52ee6de78c070bd787b2827d80eba201b7 2140 
xmlroff_0.6.2-1.4.dsc
 65399e8e6b1a53c423c640c14a003febfd3b27fcfd3651c9055c6ff03ab5d5ce 8632 
xmlroff_0.6.2-1.4.debian.tar.xz
 86427417ffb91b71f41ed9e97fa8f786a2153bc510cdd0620f4f9fee22da4315 11076 
xmlroff_0.6.2-1.4_amd64.buildinfo
Files:
 9c75bb386f34976ae96b371e67c85ae9 2140 text optional xmlroff_0.6.2-1.4.dsc
 a0ba3e2fb5d060ca8bc6a26117ad00f4 8632 text optional 
xmlroff_0.6.2-1.4.debian.tar.xz
 2eabbf8933d1d52f32c48de044deef0d 11076 text optional 
xmlroff_0.6.2-1.4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE+uHltkZSvnmOJ4zCC8R9xk0TUwYFAlw5HZcRHGFuZHJlYXNA
ZmF0YWwuc2UACgkQC8R9xk0TUwZz/g/9GSufdMd+YnQ5LNejmVH+P6rTwUG9c/O/
gKC1hfDmTvr+WRVDsKSuVOGVnfFGtL4PJwbHi9IzVLVJ2RHoUFhIn3WVs1MC85mO
QSpmLO4CvtIAJdh502PtFfbl9iWFdzWspcLOY0y/9WusFF7ptGDUu4wW+M8fZr60
/i9JZwyLhedGjBiTZcrxHQyzQzXYpGhzSMBFTLJSmp8ouPlXDtBbKlHiETPJCmBD
jRvLXa6TPmL5RymEy43YDvGV8OVx9M5Kj17mYhX8eJT0QF2CWG6isxzCqowhjTLp
gDeQmbeEwFh9Rv9LK0ePIwvZFDxfFQFr/ebo48EbTmo4OLAMalRu24pjZu4zOvnT
ffJ9tRKItF3bW12IbDgWAj6riXWYE4HWjNtP7wodOU/ptsuiUmVwjyg9QVApJIT1

Bug#918855: debconf: Impossible to upgrade from 1.5.59 -> 1.5.69

[Adrian Bunk]

On Wed, Jan 09, 2019 at 04:17:32PM -0800, Dima Kogan wrote:
> Package: debconf
> Version: 1.5.69
> Severity: serious
> 
> Hi.
> 
> I'm running a mostly-up-to-date Debian/sid system. I just tried updating
> it, and it barf at me when I ask it to update debconf:
>...
> The punchline is at the end. I haven't tried to figure out what this
> loop means, and I haven't attempted the setting suggested by the error
> message, since it sounds like it could break something. This probably
> shouldn't be happening. I'm attaching the output of 'dpkg -l'.

ii  perl  5.20.1-1 amd64
Larry Wall's Practical Extraction and Report Language
ii  perl-base 5.20.1-1 amd64
minimal Perl system
ri  perl-modules  5.20.1-1 all  
Core Perl modules

There are packages from unstable at some point between wheezy and jessie.
debconf 1.5.59 was pre-stretch unstable.

Are you somehow pinning/holding ancient packages on your system?

> Thanks!

cu
Adrian

-- 

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

Processed: Re: Bug#917655: biojava4-live: FTBFS (cannot find symbol JAXBContext)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help upstream
Bug #917667 [src:biojava4-live] biojava4-live: FTBFS: error: package 
javax.xml.bind.annotation does not exist
Bug #917655 [src:biojava4-live] biojava4-live: FTBFS (cannot find symbol 
JAXBContext)
Ignoring request to alter tags of bug #917667 to the same tags previously set
Ignoring request to alter tags of bug #917655 to the same tags previously set

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

Processed: Re: Bug#917655: biojava4-live: FTBFS (cannot find symbol JAXBContext)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help upstream
Bug #917655 [src:biojava4-live] biojava4-live: FTBFS (cannot find symbol 
JAXBContext)
Bug #917667 [src:biojava4-live] biojava4-live: FTBFS: error: package 
javax.xml.bind.annotation does not exist
Added tag(s) help and upstream.
Added tag(s) upstream and help.

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

Bug#917655: biojava4-live: FTBFS (cannot find symbol JAXBContext)

[Andreas Tille]

Control: tags -1 help upstream

Hi,

I've commited a new minor upstream version to Git but the problem exists
also in this version.  I've asked at debian-java list for help[1]

Kind regards

Andreas.

[1] https://lists.debian.org/debian-java/2019/01/msg00011.html

-- 
http://fam-tille.de

Bug#917511: harvest-tools: diff for NMU version 1.3-3.1

[Andreas Tille]

Hi Adrian,

On Fri, Jan 11, 2019 at 10:31:41PM +0200, Adrian Bunk wrote:
> I've prepared an NMU for harvest-tools (versioned as 1.3-3.1) and 
> uploaded it to DELAYED/14. Please feel free to tell me if I should 
> cancel it.

Thanks a lot for your work on this and sorry for missing this one.
Pretty please next time use maximum DELAYED/1 for Debian Med packages.
That's perfectly fine.  I could have speeded up the upload but I decided
to do some more polishing on the package and upload directly.

Thanks again for all your work

 Andreas.

PS: Most probably a ping to the bug report would have been sufficient
and might have saved your time. ;-)

-- 
http://fam-tille.de

Bug#917495: marked as done (hhsuite: FTBFS ('ffsort_index' was not declared in this scope))

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 23:54:50 +0200
with message-id <20190111215450.GG17164@localhost>
and subject line Fixed in 3.0~beta3+dfsg-2
has caused the Debian Bug report #917495,
regarding hhsuite: FTBFS ('ffsort_index' 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.)


-- 
917495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hhsuite
Version: 3.0~beta3+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --builddirectory=mybuild
   dh_update_autotools_config -i -O--builddirectory=mybuild
   dh_autoreconf -i -O--builddirectory=mybuild
   dh_auto_configure -i -O--builddirectory=mybuild
cd mybuild && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ..
-- The CXX compiler identification is GNU 8.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Compiler is GNU 

[... snipped ...]

make[1]: Entering directory '/<>/hhsuite-3.0~beta3+dfsg'
dh_auto_build -- NO_PNG=1
cd mybuild && make -j1 NO_PNG=1
make[2]: Entering directory '/<>/hhsuite-3.0~beta3+dfsg/mybuild'
/usr/bin/cmake -S"/<>/hhsuite-3.0~beta3+dfsg" 
-B"/<>/hhsuite-3.0~beta3+dfsg/mybuild" --check-build-system 
CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start 
"/<>/hhsuite-3.0~beta3+dfsg/mybuild/CMakeFiles" 
"/<>/hhsuite-3.0~beta3+dfsg/mybuild/CMakeFiles/progress.marks"
make -f CMakeFiles/Makefile2 all
make[3]: Entering directory '/<>/hhsuite-3.0~beta3+dfsg/mybuild'
make -f src/CMakeFiles/A3M_COMPRESS_OBJECT.dir/build.make 
src/CMakeFiles/A3M_COMPRESS_OBJECT.dir/depend
make[4]: Entering directory '/<>/hhsuite-3.0~beta3+dfsg/mybuild'
cd "/<>/hhsuite-3.0~beta3+dfsg/mybuild" && /usr/bin/cmake -E 
cmake_depends "Unix Makefiles" "/<>/hhsuite-3.0~beta3+dfsg" 
"/<>/hhsuite-3.0~beta3+dfsg/src" 
"/<>/hhsuite-3.0~beta3+dfsg/mybuild" 
"/<>/hhsuite-3.0~beta3+dfsg/mybuild/src" 
"/<>/hhsuite-3.0~beta3+dfsg/mybuild/src/CMakeFiles/A3M_COMPRESS_OBJECT.dir/DependInfo.cmake"
 --color=
Scanning dependencies of target A3M_COMPRESS_OBJECT
make[4]: Leaving directory '/<>/hhsuite-3.0~beta3+dfsg/mybuild'
make -f src/CMakeFiles/A3M_COMPRESS_OBJECT.dir/build.make 
src/CMakeFiles/A3M_COMPRESS_OBJECT.dir/build
make[4]: Entering directory '/<>/hhsuite-3.0~beta3+dfsg/mybuild'
[  1%] Building CXX object 
src/CMakeFiles/A3M_COMPRESS_OBJECT.dir/a3m_compress.cpp.o
cd "/<>/hhsuite-3.0~beta3+dfsg/mybuild/src" && /usr/bin/c++  -DOPENMP 
-DSSE -I"/<>/hhsuite-3.0~beta3+dfsg/src" 
-I"/<>/hhsuite-3.0~beta3+dfsg/src/cs" 
-I"/<>/hhsuite-3.0~beta3+dfsg/mybuild"  -g -O2 
-fdebug-prefix-map=/<>/hhsuite-3.0~beta3+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -march=native -msse4.2 -mfpmath=sse -fopenmp 
-fno-strict-aliasing   -o CMakeFiles/A3M_COMPRESS_OBJECT.dir/a3m_compress.cpp.o 
-c "/<>/hhsuite-3.0~beta3+dfsg/src/a3m_compress.cpp"
make[4]: Leaving directory '/<>/hhsuite-3.0~beta3+dfsg/mybuild'
[  1%] Built target A3M_COMPRESS_OBJECT
make -f src/CMakeFiles/a3m_database_filter.dir/build.make 
src/CMakeFiles/a3m_database_filter.dir/depend
make[4]: Entering directory '/<>/hhsuite-3.0~beta3+dfsg/mybuild'
cd "/<>/hhsuite-3.0~beta3+dfsg/mybuild" && /usr/bin/cmake -E 
cmake_depends "Unix Makefiles" "/<>/hhsuite-3.0~beta3+dfsg" 
"/<>/hhsuite-3.0~beta3+dfsg/src" 
"/<>/hhsuite-3.0~beta3+dfsg/mybuild" 
"/<>/hhsuite-3.0~beta3+dfsg/mybuild/src" 
"/<>/hhsuite-3.0~beta3+dfsg/mybuild/src/CMakeFiles/a3m_database_filter.dir/DependInfo.cmake"
 --color=
Scanning dependencies of target a3m_database_filter
make[4]: Leaving directory '/<>/hhsuite-3.0~beta3+dfsg/mybuild'
make -f src/CMakeFiles/a3m_database_filter.dir/build.make 
src/CMakeFiles/a3m_database_filter.dir/build
make[4]: Entering directory '/<>/hhsuite-3.0~beta3+dfsg/mybuild'
[  2%] Building CXX object 
src/CMakeFiles/a3m_database_filter.dir/a3m_database_filter.cpp.o
cd "/<>/hhsuite-3.0~beta3+dfsg/mybuild/src" 

Processed: fixed 916646 in 2018.12-2

[Debian Bug Tracking System]

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

> fixed 916646 2018.12-2
Bug #916646 {Done: Robert Lemmen } [rakudo] perl6-zef: 
fails to remove: No such file or directory at /usr/share/perl6/rakudo-helper.pl 
line 70.
Marked as fixed in versions rakudo/2018.12-2.
> thanks
Stopping processing here.

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

Processed: affects 916646

[Debian Bug Tracking System]

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

> affects 916646 perl6-zef
Bug #916646 {Done: Robert Lemmen } [rakudo] perl6-zef: 
fails to remove: No such file or directory at /usr/share/perl6/rakudo-helper.pl 
line 70.
Added indication that 916646 affects perl6-zef
> thanks
Stopping processing here.

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

Processed: reassign 916646 to rakudo

[Debian Bug Tracking System]

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

> reassign 916646 rakudo 2018.11-1
Bug #916646 {Done: Robert Lemmen } [perl6-zef] 
perl6-zef: fails to remove: No such file or directory at 
/usr/share/perl6/rakudo-helper.pl line 70.
Bug reassigned from package 'perl6-zef' to 'rakudo'.
No longer marked as found in versions perl6-zef/0.5.3-1.
No longer marked as fixed in versions rakudo/2018.12-2.
Bug #916646 {Done: Robert Lemmen } [rakudo] perl6-zef: 
fails to remove: No such file or directory at /usr/share/perl6/rakudo-helper.pl 
line 70.
Marked as found in versions rakudo/2018.11-1.
> thanks
Stopping processing here.

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

Processed: fixed-upstream

[Debian Bug Tracking System]

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

> tags 892348 fixed-upstream
Bug #892348 [src:xmlroff] xmlroff: Please use 'pkg-config' to find FreeType 2
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#917511: marked as done (harvest-tools FTBFS, "This code requires C++14. Either your compiler does not support it or it is not enabled.")

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 21:06:22 +
with message-id 
and subject line Bug#917511: fixed in harvest-tools 1.3-4
has caused the Debian Bug report #917511,
regarding harvest-tools FTBFS, "This code requires C++14. Either your compiler 
does not support it or it is not enabled."
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.)


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

Package: harvest-tools
Version: 1.3-3
Tags: buster sid patch

harvest-tools failed to build during the binnmu for the capng transition with.

/usr/include/kj/common.h:36:4: error: #error "This code requires C++14. Either your 
compiler does not support it or it is not enabled."
   #error "This code requires C++14. Either your compiler does not support it or it 
is not enabled."

I replaced c++11 with c++14 in configure.ac and Makefile.in and was able to
get a successful build in raspbian buster-staging which I went ahead and
uploaded to raspbian. A debdiff should appear soon at
https://debdiffs.raspbian.org/main/h/harvest-tools/

No intent to NMU in Debian.
--- End Message ---
--- Begin Message ---
Source: harvest-tools
Source-Version: 1.3-4

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated harvest-tools 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: Fri, 11 Jan 2019 21:47:40 +0100
Source: harvest-tools
Binary: harvest-tools
Architecture: source
Version: 1.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 harvest-tools - archiving and postprocessing for reference-compressed genomic 
mul
Closes: 917511
Changes:
 harvest-tools (1.3-4) unstable; urgency=medium
 .
   [ Adrian Bunk ]
   * Add fix from Peter Michael Green for FTBFS with new capng.
 (Closes: #917511)
 .
   [ Andreas Tille ]
   * debhelper 12 (+override_dh_auto_clean)
   * Standards-Version: 4.3.0
Checksums-Sha1:
 ae471e26bf9cc1808fe083d66588828f07670bfe 2108 harvest-tools_1.3-4.dsc
 16c3811f84300a0cfd73cd6871812738dd584d5c 5444 harvest-tools_1.3-4.debian.tar.xz
 86b22bf4eecc9e7047a361256e5e28f6180e4d8d 6553 
harvest-tools_1.3-4_amd64.buildinfo
Checksums-Sha256:
 7f88c54bf59ed1d0b25926027c7067917afde8906cc3981ab68d3091719b5cf2 2108 
harvest-tools_1.3-4.dsc
 ae106236f309a74e1ea08a442961f59d164ccd1d328e1c16fe2ad368b77de415 5444 
harvest-tools_1.3-4.debian.tar.xz
 ec848f86b704cd8cfd54a810f0ad6e2e3dbe57188304eeda3392bb7b10246528 6553 
harvest-tools_1.3-4_amd64.buildinfo
Files:
 6c0d61efad343b4e1bee2dd32e808729 2108 science optional harvest-tools_1.3-4.dsc
 f6bbc96408011048ad5004bd43a87163 5444 science optional 
harvest-tools_1.3-4.debian.tar.xz
 0448f689e14268f9c5bfd4192a1d4968 6553 science optional 
harvest-tools_1.3-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlw5AYIRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHRNQ//RfqeHbeW5GXeurO+nWYKluWIISz3icg1
Jr2z1ZIjUcfbyp64kEWJCOUq7uI1FLbX9pSp+cetEy8s/So+lgBx7DzjgdDdIrou
M9k3kLQ8UjoXNy+BuOGaZ/aHvIe0wDXZc9OEYt9daIn26SrbHfGgZxkeYf3SHjjO
4yLXt3vBwFyyrQNebzCNSUxkNQLvSljJxYZqF52AXAJNlJhtIWQ5egvv2s9g2Ywt
9ncz6DltOVQBYz12is+6uUj4Vs5oviU0fyb+GWLvLzzwVmfFjwDt67ABIIyYTKBN
pn7gH1XaDwuLJuD2Xvnu9qKekfrnrkpaW2vmvI7np8kRZlZXyCG4tKskakGkhwKZ
zVJM2w7DJoynB3kHAKD2xquNE+SJXUkR6RQmhF+z+mQeDPYEG/Sq/hk9ntuYguNY
TCGYMGUJrrO6DXxGTPQ/L7ZGU3/nDLPxjKQ0chRxZEltu7HAtSaa3wPKDfgjHWzn
t7NNhkQK2QhfUBFZQ1Z2/i21S6M46q2d5h+S2WfdK1c1CwF3cWmreZAQlYrRWPyr
RbTwWADE17L0ryA6+Zi2eG8allx+GFbvMsdAF8lVrIOqQAumwpJJI2mC0eZSJbLd
cgVcyPEMICeSmtJ+pbUnvIt6MC2lMvoinIEDPEHPmrvX1p/8IjhDcZzjb+jGbV1b
0e26U0QcItc=
=Bv/I
-END PGP SIGNATURE End Message ---

Bug#917689: marked as done (harvest-tools: FTBFS: configure: error: Cap'n Proto headers not found.)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 21:06:22 +
with message-id 
and subject line Bug#917511: fixed in harvest-tools 1.3-4
has caused the Debian Bug report #917511,
regarding harvest-tools: FTBFS: configure: error: Cap'n Proto headers not found.
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.)


-- 
917511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: harvest-tools
Version: 1.3-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> checking google/protobuf/stubs/common.h presence... yes
> checking for google/protobuf/stubs/common.h... yes
> checking capnp/common.h usability... no
> checking capnp/common.h presence... no
> checking for capnp/common.h... no
> configure: error: Cap'n Proto headers not found.
>   tail -v -n \+0 config.log

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/harvest-tools_1.3-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: harvest-tools
Source-Version: 1.3-4

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated harvest-tools 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: Fri, 11 Jan 2019 21:47:40 +0100
Source: harvest-tools
Binary: harvest-tools
Architecture: source
Version: 1.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 harvest-tools - archiving and postprocessing for reference-compressed genomic 
mul
Closes: 917511
Changes:
 harvest-tools (1.3-4) unstable; urgency=medium
 .
   [ Adrian Bunk ]
   * Add fix from Peter Michael Green for FTBFS with new capng.
 (Closes: #917511)
 .
   [ Andreas Tille ]
   * debhelper 12 (+override_dh_auto_clean)
   * Standards-Version: 4.3.0
Checksums-Sha1:
 ae471e26bf9cc1808fe083d66588828f07670bfe 2108 harvest-tools_1.3-4.dsc
 16c3811f84300a0cfd73cd6871812738dd584d5c 5444 harvest-tools_1.3-4.debian.tar.xz
 86b22bf4eecc9e7047a361256e5e28f6180e4d8d 6553 
harvest-tools_1.3-4_amd64.buildinfo
Checksums-Sha256:
 7f88c54bf59ed1d0b25926027c7067917afde8906cc3981ab68d3091719b5cf2 2108 
harvest-tools_1.3-4.dsc
 ae106236f309a74e1ea08a442961f59d164ccd1d328e1c16fe2ad368b77de415 5444 
harvest-tools_1.3-4.debian.tar.xz
 ec848f86b704cd8cfd54a810f0ad6e2e3dbe57188304eeda3392bb7b10246528 6553 
harvest-tools_1.3-4_amd64.buildinfo
Files:
 6c0d61efad343b4e1bee2dd32e808729 2108 science optional harvest-tools_1.3-4.dsc
 f6bbc96408011048ad5004bd43a87163 5444 science optional 
harvest-tools_1.3-4.debian.tar.xz
 0448f689e14268f9c5bfd4192a1d4968 6553 science optional 
harvest-tools_1.3-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlw5AYIRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHRNQ//RfqeHbeW5GXeurO+nWYKluWIISz3icg1
Jr2z1ZIjUcfbyp64kEWJCOUq7uI1FLbX9pSp+cetEy8s/So+lgBx7DzjgdDdIrou
M9k3kLQ8UjoXNy+BuOGaZ/aHvIe0wDXZc9OEYt9daIn26SrbHfGgZxkeYf3SHjjO
4yLXt3vBwFyyrQNebzCNSUxkNQLvSljJxYZqF52AXAJNlJhtIWQ5egvv2s9g2Ywt
9ncz6DltOVQBYz12is+6uUj4Vs5oviU0fyb+GWLvLzzwVmfFjwDt67ABIIyYTKBN
pn7gH1XaDwuLJuD2Xvnu9qKekfrnrkpaW2vmvI7np8kRZlZXyCG4tKskakGkhwKZ
zVJM2w7DJoynB3kHAKD2xquNE+SJXUkR6RQmhF+z+mQeDPYEG/Sq/hk9ntuYguNY
TCGYMGUJrrO6DXxGTPQ/L7ZGU3/nDLPxjKQ0chRxZEltu7HAtSaa3wPKDfgjHWzn
t7NNhkQK2QhfUBFZQ1Z2/i21S6M46q2d5h+S2WfdK1c1CwF3cWmreZAQlYrRWPyr
RbTwWADE17L0ryA6+Zi2eG8allx+GFbvMsdAF8lVrIOqQAumwpJJI2mC0eZSJbLd

Processed: severity of 918779 is grave

[Debian Bug Tracking System]

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

> severity 918779 grave
Bug #918779 [r10k] r10k: uninitialized constant Cri::Error
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#917276: marked as done (mysql-defaults and MariaDB 10.3)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 21:46:33 +0200
with message-id 

and subject line mysql-defaults done
has caused the Debian Bug report #917276,
regarding mysql-defaults and MariaDB 10.3
to be marked as done.

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

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


-- 
917276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mysql-defaults
Version: 1.0.5
Severity: serious
Justification: makes the package in question unusable or mostly so

The package has been updated to depend on Mariadb 10.3, which is
currently available only in Debian unstable. This serious bug report
is done to prevent mysql-defaults from entering Debian testing before
mariadb-10.3 has done so.
--- End Message ---
--- Begin Message ---
Closing this bug as the transition checker itself handles this
automatically, as stated by Ivo above and now also visible at
https://tracker.debian.org/pkg/mysql-defaults--- End Message ---

Processed: harvest-tools: diff for NMU version 1.3-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 917511 + pending
Bug #917511 [src:harvest-tools] harvest-tools FTBFS, "This code requires C++14. 
Either your compiler does not support it or it is not enabled."
Bug #917689 [src:harvest-tools] harvest-tools: FTBFS: configure: error: Cap'n 
Proto headers not found.
Added tag(s) pending.
Added tag(s) pending.

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

Bug#917511: harvest-tools: diff for NMU version 1.3-3.1

[Adrian Bunk]

Control: tags 917511 + pending

Dear maintainer,

I've prepared an NMU for harvest-tools (versioned as 1.3-3.1) and 
uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

cu
Adrian

-- 

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

diff -Nru harvest-tools-1.3/debian/changelog harvest-tools-1.3/debian/changelog
--- harvest-tools-1.3/debian/changelog	2018-11-26 08:48:51.0 +0200
+++ harvest-tools-1.3/debian/changelog	2019-01-11 22:27:35.0 +0200
@@ -1,3 +1,11 @@
+harvest-tools (1.3-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add fix from Peter Michael Green for FTBFS with new capng.
+(Closes: #917511)
+
+ -- Adrian Bunk   Fri, 11 Jan 2019 22:27:35 +0200
+
 harvest-tools (1.3-3) unstable; urgency=medium
 
   [ Jelmer Vernoo ]
diff -Nru harvest-tools-1.3/debian/patches/series harvest-tools-1.3/debian/patches/series
--- harvest-tools-1.3/debian/patches/series	2018-11-26 08:48:51.0 +0200
+++ harvest-tools-1.3/debian/patches/series	2019-01-11 22:27:32.0 +0200
@@ -3,3 +3,4 @@
 hardening.patch
 remove_memwrap.patch
 parallel.patch
+use-c++-14.patch
diff -Nru harvest-tools-1.3/debian/patches/use-c++-14.patch harvest-tools-1.3/debian/patches/use-c++-14.patch
--- harvest-tools-1.3/debian/patches/use-c++-14.patch	1970-01-01 02:00:00.0 +0200
+++ harvest-tools-1.3/debian/patches/use-c++-14.patch	2019-01-11 22:27:35.0 +0200
@@ -0,0 +1,28 @@
+Description: Use c++14 rather than c++11 for compatibility with new capng.
+Author: Peter Michael Green 
+Bug-Debian: https://bugs.debian.org/917511
+Last-Update: 2018-12-27
+
+Index: harvest-tools-1.3/configure.ac
+===
+--- harvest-tools-1.3.orig/configure.ac
 harvest-tools-1.3/configure.ac
+@@ -29,7 +29,7 @@ then
+ 	AC_MSG_ERROR([Cap'n Proto compiler (capnp) not found.])
+ fi
+ 
+-CPPFLAGS="-I$with_protobuf/include -I$with_capnp/include -std=c++11"
++CPPFLAGS="-I$with_protobuf/include -I$with_capnp/include -std=c++14"
+ 
+ AC_CHECK_HEADER(google/protobuf/stubs/common.h, [result=1], [result=0])
+ 
+Index: harvest-tools-1.3/Makefile.in
+===
+--- harvest-tools-1.3.orig/Makefile.in
 harvest-tools-1.3/Makefile.in
+@@ -1,4 +1,4 @@
+-CXXFLAGS += -std=c++11 -Isrc -I@protobuf@/include -I@capnp@/include
++CXXFLAGS += -std=c++14 -Isrc -I@protobuf@/include -I@capnp@/include
+ 
+ UNAME_S=$(shell uname -s)
+ 

Processed: lpr: diff for NMU version 1:2008.05.17.3

[Debian Bug Tracking System]

Processing control commands:

> tags 916148 + patch
Bug #916148 [src:lpr] lpr FTBFS with glibc 2.28
Added tag(s) patch.
> tags 916148 + pending
Bug #916148 [src:lpr] lpr FTBFS with glibc 2.28
Added tag(s) pending.

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

Bug#916148: lpr: diff for NMU version 1:2008.05.17.3

[Adrian Bunk]

Control: tags 916148 + patch
Control: tags 916148 + pending

Dear maintainer,

I've prepared an NMU for lpr (versioned as 1:2008.05.17.3) and uploaded 
it to DELAYED/15. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru lpr-2008.05.17.2/debian/changelog lpr-2008.05.17.3/debian/changelog
--- lpr-2008.05.17.2/debian/changelog	2016-09-25 16:08:29.0 +0300
+++ lpr-2008.05.17.3/debian/changelog	2019-01-11 22:06:54.0 +0200
@@ -1,3 +1,12 @@
+lpr (1:2008.05.17.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with glibc 2.28. (Closes: #916148)
+  * Sugggest ghostscript instead of gs. (Closes: #601355)
+  * Build with -g to get non-empty -dbgsym.
+
+ -- Adrian Bunk   Fri, 11 Jan 2019 22:06:54 +0200
+
 lpr (1:2008.05.17.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru lpr-2008.05.17.2/debian/control lpr-2008.05.17.3/debian/control
--- lpr-2008.05.17.2/debian/control	2016-09-25 16:08:29.0 +0300
+++ lpr-2008.05.17.3/debian/control	2019-01-11 22:06:54.0 +0200
@@ -10,7 +10,7 @@
 Package: lpr
 Architecture: any
 Depends: ${shlibs:Depends}, netbase
-Suggests: magicfilter | apsfilter, gs
+Suggests: magicfilter | apsfilter, ghostscript
 Conflicts: suidmanager (<< 0.50)
 Replaces: logcheck-database
 Description: BSD lpr/lpd line printer spooling system
diff -Nru lpr-2008.05.17.2/debian/rules lpr-2008.05.17.3/debian/rules
--- lpr-2008.05.17.2/debian/rules	2016-09-25 16:08:29.0 +0300
+++ lpr-2008.05.17.3/debian/rules	2019-01-11 22:06:54.0 +0200
@@ -5,8 +5,8 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-CFLAGS = -Wall -O2 -D_GNU_SOURCE -D__KAME__ -I../common_source
-CPPFLAGS = -Wall -O2 -D_GNU_SOURCE -D__KAME__ -I../common_source
+CFLAGS = -Wall -g -O2 -D_GNU_SOURCE -D__KAME__ -I../common_source
+CPPFLAGS = -Wall -g -O2 -D_GNU_SOURCE -D__KAME__ -I../common_source
 # -D_BSD_SOURCE
 
 build: build-stamp
diff -Nru lpr-2008.05.17.2/lpr/lpr.c lpr-2008.05.17.3/lpr/lpr.c
--- lpr-2008.05.17.2/lpr/lpr.c	2008-05-18 01:47:19.0 +0300
+++ lpr-2008.05.17.3/lpr/lpr.c	2019-01-11 20:58:27.0 +0200
@@ -60,6 +60,7 @@
 #include 
 #include 
 #include 
+#include 
 
 #include 
 #include 

Bug#915689: prevent from migrating to testing

[Michael Stone]

On Fri, Jan 11, 2019 at 01:57:28PM -0500, Michael Stone wrote:
There never should have been an NMU simply replacing rng-tools with 
rng-tools5. I did not notice that this had happened.


Also, the correct fix for buster is an upload to put things back the way 
they were, which is going to be ugly.

Bug#918613: marked as done (ruby-rack-contrib FTBFS with ruby-rack 2.0.6-2)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 19:51:39 +
with message-id 
and subject line Bug#918766: Removed package(s) from unstable
has caused the Debian Bug report #918613,
regarding ruby-rack-contrib FTBFS with ruby-rack 2.0.6-2
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.)


-- 
918613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rack-contrib
Version: 1.3.0-3
Severity: serious
Tags: ftbfs buster sid

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

...
usr/lib/ruby/2.5.0/rubygems/dependency.rb:312:in `to_specs': Could not find 
'rack' (~> 1.4) - did find: [rack-2.0.6] (Gem::MissingSpecVersionError)
...
--- End Message ---
--- Begin Message ---
Version: 1.3.0-3+rm

Dear submitter,

as the package ruby-rack-contrib has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/918766

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#915689: prevent from migrating to testing

[Michael Stone]

There never should have been an NMU simply replacing rng-tools with 
rng-tools5. I did not notice that this had happened.


On Fri, Jan 11, 2019 at 07:21:49PM +0100, Andreas Henriksson wrote:

That has apparently failed to materialize well in time for buster.
Looking at the contents of the binary packages it seems rng-tools
(in unstable) has more contents and likely provides more
functionality/integration (but I haven't looked into details, eg.
rng-tools5 has no /etc/default file which might be a good thing as those
are generally frowed upon in the current systemd service age, but has
there been any work on actual migration of current rng-tools users
configuration to what rng-tools5 uses?)


It's not possible to migrate people from rng-tools to rng-tools5 as the 
functionality does not entirely overlap. There's no meaningful 
conversion from one to the other, nor does there need to be. (A user 
currently running rng-tools has no need to move to rng-tools5.) There's 
a chance (though increasingly small as the legacy hardware ages) that 
forcing a migration from rng-tools to rng-tools5 will break an existing 
setup.


The intent of transitioning was entirely to make it easier for people 
reading non-debian-specific instructions on the internet telling them to 
install "rng-tools" in order to get certain functionality (specifically 
RDRAND/RDSEED) would get the package they were expecting. The end result 
for buster would be rng-tools2 and rng-tools5 packages, with an 
rng-tools package pulling in rng-tools2 as a replacement. 

Given that the kernel seems to be moving in the direction of allowing 
RDRAND/RDSEED to seed /dev/random without blocking (see 
RANDOM_TRUST_CPU) I'm not sure a package renaming dance is worthwhile as 
the most common reason for installing rng-tools5 will no longer be 
as relevant.


Another option is to simply remove rng-tools, which eliminates the 
confusion. But, doing that will mean dropping support for certain 
(legacy) configurations supported in the current rng-tools package but 
not rng-tools5.

Bug#896025: Segfault in test suite of new upstream version (Was: python-mne FTBFS with python-matplotlib 2.2.2-1)

[Andreas Tille]

Hi,

any success with fixing this?

Kind regards

 Andreas.

-- 
http://fam-tille.de

Processed: blktool: diff for NMU version 4-7.1

[Debian Bug Tracking System]

Processing control commands:

> tags 917055 + pending
Bug #917055 [src:blktool] blktool FTBFS with glibc 2.28
Added tag(s) pending.

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

Bug#917055: blktool: diff for NMU version 4-7.1

[Adrian Bunk]

Control: tags 917055 + pending

Dear maintainer,

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

cu
Adrian

-- 

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

diff -Nru blktool-4/debian/changelog blktool-4/debian/changelog
--- blktool-4/debian/changelog	2015-07-08 02:13:29.0 +0300
+++ blktool-4/debian/changelog	2019-01-11 20:35:44.0 +0200
@@ -1,3 +1,12 @@
+blktool (4-7.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with glibc 2.28. (Closes: #917055)
+  * Package description improvement from Aputsiaq Janussen.
+(Closes: #636500)
+
+ -- Adrian Bunk   Fri, 11 Jan 2019 20:35:44 +0200
+
 blktool (4-7) unstable; urgency=low
 
   * New maintainer. (Closes: #695127).
diff -Nru blktool-4/debian/control blktool-4/debian/control
--- blktool-4/debian/control	2015-07-08 01:17:17.0 +0300
+++ blktool-4/debian/control	2019-01-11 20:35:44.0 +0200
@@ -16,5 +16,5 @@
  device.  It is like hdparm but a more general tool, as it works on
  SCSI, IDE and SATA devices.
  .
- This program is for those who know what they're doing and should be
- used it at your own risk as it could cause damage to your hardware.
+ This program is for those who know what they're doing and it should
+ be used at your own risk as it could cause damage to your hardware.
diff -Nru blktool-4/debian/patches/0004-fix-ftbfs-glibc-2.28.patch blktool-4/debian/patches/0004-fix-ftbfs-glibc-2.28.patch
--- blktool-4/debian/patches/0004-fix-ftbfs-glibc-2.28.patch	1970-01-01 02:00:00.0 +0200
+++ blktool-4/debian/patches/0004-fix-ftbfs-glibc-2.28.patch	2019-01-11 20:35:38.0 +0200
@@ -0,0 +1,14 @@
+Description: Fix FTBFS with glibc 2.28
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/917055
+
+--- blktool-4.orig/blktool.c
 blktool-4/blktool.c
+@@ -18,6 +18,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ #include 
+ #include 
diff -Nru blktool-4/debian/patches/series blktool-4/debian/patches/series
--- blktool-4/debian/patches/series	2015-06-13 01:05:10.0 +0300
+++ blktool-4/debian/patches/series	2019-01-11 20:35:44.0 +0200
@@ -1,3 +1,4 @@
 0001-fix-typos-in-manpage.patch
 0002-fix-string-error.patch
 0003-Fix-3-d-argument-for-BLKROSET-it-must-be-const-int.patch
+0004-fix-ftbfs-glibc-2.28.patch

Bug#918751: python-shade: BSP tag

[Stewart Ferguson]

user debian-rele...@lists.debian.org
usertags -1 + bsp-2019-01-nl-venlo
thank you


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

Bug#918671: python-shade: BSP tag

[Stewart Ferguson]

user debian-rele...@lists.debian.org
usertags -1 + bsp-2019-01-nl-venlo
thank you


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

Processed: pyzo: diff for NMU version 4.4.3-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 917085 + patch
Bug #917085 [src:pyzo] pyzo: missing dependancy to python3-pkg-resources
Added tag(s) patch.
> tags 917085 + pending
Bug #917085 [src:pyzo] pyzo: missing dependancy to python3-pkg-resources
Added tag(s) pending.

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

Bug#917085: pyzo: diff for NMU version 4.4.3-1.2

[Adrian Bunk]

Control: tags 917085 + patch
Control: tags 917085 + pending

Dear maintainer,

I've prepared an NMU for pyzo (versioned as 4.4.3-1.2) and uploaded
it to DELAYED/10. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru pyzo-4.4.3/debian/changelog pyzo-4.4.3/debian/changelog
--- pyzo-4.4.3/debian/changelog	2018-11-30 17:17:18.0 +0200
+++ pyzo-4.4.3/debian/changelog	2019-01-11 20:09:52.0 +0200
@@ -1,3 +1,11 @@
+pyzo (4.4.3-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add the missing dependency on python3-pkg-resources,
+thanks to Julien Cervelle. (Closes: #917085)
+
+ -- Adrian Bunk   Fri, 11 Jan 2019 20:09:52 +0200
+
 pyzo (4.4.3-1.1) unstable; urgency=high
 
   * Non-maintainer upload.
diff -Nru pyzo-4.4.3/debian/control pyzo-4.4.3/debian/control
--- pyzo-4.4.3/debian/control	2017-10-09 21:59:11.0 +0300
+++ pyzo-4.4.3/debian/control	2019-01-11 20:09:52.0 +0200
@@ -21,7 +21,8 @@
 Architecture: all
 Depends: ${misc:Depends},
  ${python3:Depends},
- python3-qtpy
+ python3-qtpy,
+ python3-pkg-resources
 Suggests: pyzo-doc
 Description: interactive editor for scientific Python
  Pyzo is a cross-platform Python IDE focused on interactivity and introspection,

Bug#915689: prevent from migrating to testing

[Andreas Henriksson]

Hello Aron Xu and everyone else,

On Thu, Dec 06, 2018 at 01:25:03PM +0800, Aron Xu wrote:
> Package: rng-tools
> Version: 5-1
> Severity: serious
> Tags: sid
> 
> We need to prevent this version of rng-tools from migrating to testing
> before finding a solution of coordinating with the rng-tools5 package.

I'm interested in rng-tools and would like to see it in good shape
for buster, but the current state makes me uncomfortable.

Could you please update me on what the current state is since this
bug report was opened? Have any progress been made or attempted
that isn't tracked here?

The initial changelog entry of rng-tools5 states:
"This is part of an intended transition, with this package becoming the
default rng-tools post stretch release."

That has apparently failed to materialize well in time for buster.
Looking at the contents of the binary packages it seems rng-tools
(in unstable) has more contents and likely provides more
functionality/integration (but I haven't looked into details, eg.
rng-tools5 has no /etc/default file which might be a good thing as those
are generally frowed upon in the current systemd service age, but has
there been any work on actual migration of current rng-tools users
configuration to what rng-tools5 uses?)

I'd be really interested to hear what people have on their minds for
this task and how I can help out.

Regards,
Andreas Henriksson

Bug#916977: snoopy w/ ld preload enabled breaks "apt upgrade" jessie-to-buster

[Adrian Bunk]

On Thu, Dec 20, 2018 at 05:26:25PM -0500, deb...@mailinator.com wrote:
> Package: snoopy
> Version: 2.4.6-4
> Severity: critical
> Justification: breaks unrelated software
> 
> Dear Maintainer,
> 
> With snoopy installed and enabled on jessie, apt upgrade to buster will break 
> the upgrade process, as the snoopy library goes missing while the ld preload 
> setting persists.  This causes every command invocation to trigger an error 
> message concerning the missing library.  
>...

Hw did you upgrade from jessie to buster?

Skipping a release when upgrading is not supported,
only jessie -> stretch -> buster is supported.

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#918982: marked as done (libspandsp-doc: missing Breaks+Replaces: libspandsp-dev (<< 0.0.6+dfsg-1))

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 17:50:58 +
with message-id 
and subject line Bug#918982: fixed in spandsp 0.0.6+dfsg-2
has caused the Debian Bug report #918982,
regarding libspandsp-doc: missing Breaks+Replaces: libspandsp-dev (<< 
0.0.6+dfsg-1)
to be marked as done.

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

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


-- 
918982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918982
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libspandsp-doc
Version: 0.0.6+dfsg-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/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../libspandsp-doc_0.0.6+dfsg-1_all.deb ...
  Unpacking libspandsp-doc (0.0.6+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libspandsp-doc_0.0.6+dfsg-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libspandsp-dev/DueDiligence', which is 
also in package libspandsp-dev:amd64 0.0.6+dfsg-0.1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libspandsp-doc_0.0.6+dfsg-1_all.deb


This is probably caused by a behavioral change of dh_installdocs
in debhelper compat level 11.


cheers,

Andreas


libspandsp-dev=0.0.6+dfsg-0.1_libspandsp-doc=0.0.6+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: spandsp
Source-Version: 0.0.6+dfsg-2

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

Debian distribution maintenance software
pp.
Bernhard Schmidt  (supplier of updated spandsp 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: Fri, 11 Jan 2019 18:17:42 +0100
Source: spandsp
Binary: libspandsp2 libspandsp-dev libspandsp-doc
Architecture: source
Version: 0.0.6+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Bernhard Schmidt 
Description:
 libspandsp-dev - Telephony signal processing library - development headers
 libspandsp-doc - Documentation for the spandsp signal processing library
 libspandsp2 - Telephony signal processing library
Closes: 918982
Changes:
 spandsp (0.0.6+dfsg-2) unstable; urgency=medium
 .
   * Team upload
   * Move DueDiligence document back to libspandsp-dev (Closes: #918982)
   * Set Rules-Requires-Root to no
Checksums-Sha1:
 edb7e7b66107b174919ae4e29f64f48767f9b9fb 2325 spandsp_0.0.6+dfsg-2.dsc
 0b125f6c93a1a81c4986e3708627994ff1b64eb1 15220 
spandsp_0.0.6+dfsg-2.debian.tar.xz
 6681f34b9ce0c8124cd0ce8513efeac8ab941d3e 7885 
spandsp_0.0.6+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 523ccfd781448cd4803b4bc99cecd301dff3dd7ec78d6fc09e25ad0c8c9f0f2a 2325 
spandsp_0.0.6+dfsg-2.dsc
 7c282dc889b459802a4db31f7925db64fc99ba386670f98c1a14e31876192902 15220 
spandsp_0.0.6+dfsg-2.debian.tar.xz
 5aa12802898cef62cd96cdbf23c70388df0c5dedbdc46eb80e6204fb5049d213 7885 
spandsp_0.0.6+dfsg-2_amd64.buildinfo
Files:
 cca7b617dc1ec3db739129e44360c199 2325 libs optional spandsp_0.0.6+dfsg-2.dsc
 a5552af014bfab4b1273adde09cd9ec7 15220 libs optional 
spandsp_0.0.6+dfsg-2.debian.tar.xz
 10bc94783fee20ce741801ea42969744 7885 libs optional 
spandsp_0.0.6+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE1uAexRal3873GVbTd1B55bhQvJMFAlw40O4RHGJlcm5pQGRl
Ymlhbi5vcmcACgkQd1B55bhQvJNpPw/8Dcy29rUigX6abYKjJXuXKeHNfKfVNEQW
KKdJowKEtwfmONK4UHDpyqnVJ4vlUHdg1p61Hphg+JVHPk3WyrTW7KcECw9G+zzh
ymSuUIxq4Ot3eGELPQ7vG6a3GpNd2gclobLiAQSaLZ1Ud0x0b4P4lgSqPz4TYWTQ
3PIfTJZD/jBino59nBTbU7YCWeH+6QdqpIFDX3iKr6RzrsuLf4Psd/b17Q4eRs/k
dJ7DssLNWCTecwgtyQLTODoqON3V0JJ+nmUwV8u0Nh4zo2rRa+iuThvZi7LTWDmM

Processed: ledmon: diff for NMU version 0.90-0.1

[Debian Bug Tracking System]

Processing control commands:

> tags 878271 + patch
Bug #878271 [ledmon] Update ledmon to 0.90
Added tag(s) patch.
> tags 878271 + pending
Bug #878271 [ledmon] Update ledmon to 0.90
Added tag(s) pending.
> tags 915476 + patch
Bug #915476 [src:ledmon] ledmon FTBFS with glibc 2.28
Added tag(s) patch.
> tags 915476 + pending
Bug #915476 [src:ledmon] ledmon FTBFS with glibc 2.28
Added tag(s) pending.

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

Bug#915476: ledmon: diff for NMU version 0.90-0.1

[Adrian Bunk]

Control: tags 878271 + patch
Control: tags 878271 + pending
Control: tags 915476 + patch
Control: tags 915476 + pending

Dear maintainer,

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

cu
Adrian

-- 

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

Processed: notfound 918236 in ruby-prawn-svg/0.28.0-2

[Debian Bug Tracking System]

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

> notfound 918236 ruby-prawn-svg/0.28.0-2
Bug #918236 {Done: Cédric Boutillier } [src:ruby-prawn-svg] 
ruby-prawn-svg: FTBFS in sid
No longer marked as found in versions ruby-prawn-svg/0.28.0-2.
> thanks
Stopping processing here.

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

Processed: notfound 918235 in ruby-prawn-icon/2.3.0-2

[Debian Bug Tracking System]

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

> notfound 918235 ruby-prawn-icon/2.3.0-2
Bug #918235 {Done: Cédric Boutillier } [src:ruby-prawn-icon] 
ruby-prawn-icon: FTBFS in sid
No longer marked as found in versions ruby-prawn-icon/2.3.0-2.
> thanks
Stopping processing here.

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

Processed: Re: Bug#918979: Emacs now just shows dark red dots for images

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 918646
Bug #918979 [emacs-gtk] Emacs now just shows dark red dots for images
918979 was not blocked by any bugs.
918979 was not blocking any bugs.
Added blocking bug(s) of 918979: 918646

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

Processed: block 918687 with 919007

[Debian Bug Tracking System]

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

> block 918687 with 919007
Bug #918687 [release.debian.org] transition: exempi
918687 was not blocked by any bugs.
918687 was not blocking any bugs.
Added blocking bug(s) of 918687: 919007
> thanks
Stopping processing here.

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

Processed: reassign 919002 to src:systemd, forcibly merging 918841 919002

[Debian Bug Tracking System]

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

> reassign 919002 src:systemd
Bug #919002 [systemd] CVE's for systemd vulnerabilities CVE-2018-16864, 
CVE-2018-16865 and CVE-2018-16866
Bug reassigned from package 'systemd' to 'src:systemd'.
No longer marked as found in versions systemd/240-3.
Ignoring request to alter fixed versions of bug #919002 to the same values 
previously set
> forcemerge 918841 919002
Bug #918841 [src:systemd] systemd: CVE-2018-16864
Bug #919002 [src:systemd] CVE's for systemd vulnerabilities CVE-2018-16864, 
CVE-2018-16865 and CVE-2018-16866
Severity set to 'grave' from 'normal'
Marked as found in versions systemd/240-2, systemd/204-1, and 
systemd/232-25+deb9u6.
Added tag(s) upstream and security.
Merged 918841 919002
> thanks
Stopping processing here.

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

Bug#919007: Needs to be updated for libexempi8

[Michael Biebl]

Source: python-xmp-toolkit
Version: 2.0.1+git20140309.5437b0a-5
Severity: serious

Hi,

libexempi bumped its soname from 3 → 8.
The transition is tracked at
https://release.debian.org/transitions/html/auto-exempi.html
and via #918687.

I tried updating the package with the attached patch, but this triggers
test-suite failures (see build.log).

Unfortunately I don't know enough Python to fix this myself.

Regards,
Michael


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

Kernel: Linux 4.19.0-1-amd64 (SMP w/4 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)
LSM: AppArmor: enabled
diff -Nru python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/changelog 
python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/changelog
--- python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/changelog   
2017-06-19 19:40:03.0 +0200
+++ python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/changelog   
2019-01-11 17:22:13.0 +0100
@@ -1,3 +1,9 @@
+python-xmp-toolkit (2.0.1+git20140309.5437b0a-6) UNRELEASED; urgency=medium
+
+  * Update to libexempi8
+
+ -- Michael Biebl   Fri, 11 Jan 2019 17:22:13 +0100
+
 python-xmp-toolkit (2.0.1+git20140309.5437b0a-5) unstable; urgency=medium
 
   * Orphaning package:
diff -Nru python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/control 
python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/control
--- python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/control 2017-06-19 
19:39:58.0 +0200
+++ python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/control 2019-01-11 
17:21:55.0 +0100
@@ -5,7 +5,7 @@
 Build-Depends:
  debhelper (>= 9),
  dh-python,
- libexempi3 (>= 2.2.0),
+ libexempi8 (>= 2.2.0),
  python-all,
  python-mock,
  python-setuptools,
@@ -25,7 +25,7 @@
 Package: python-libxmp
 Architecture: all
 Depends:
- libexempi3,
+ libexempi8,
  ${misc:Depends},
  ${python:Depends}
 Suggests:
@@ -43,7 +43,7 @@
 Package: python3-libxmp
 Architecture: all
 Depends:
- libexempi3,
+ libexempi8,
  ${misc:Depends},
  ${python3:Depends}
 Suggests:
diff -Nru 
python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/patches/0001-hardcode-library-name.patch
 
python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/patches/0001-hardcode-library-name.patch
--- 
python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/patches/0001-hardcode-library-name.patch
2017-01-22 18:29:41.0 +0100
+++ 
python-xmp-toolkit-2.0.1+git20140309.5437b0a/debian/patches/0001-hardcode-library-name.patch
2019-01-11 17:22:13.0 +0100
@@ -18,7 +18,7 @@
  Loads exempi library.
  """
 -path = ctypes.util.find_library('exempi')
-+path = 'libexempi.so.3'
++path = 'libexempi.so.8'
  if path is None:
  if platform.system().startswith('Darwin'):
  if os.path.exists('/opt/local/lib/libexempi.dylib'):
I: Copying COW directory
I: forking: rm -rf /var/cache/pbuilder/build/cow.13636
I: forking: cp -al /var/cache/pbuilder/sid.cow 
/var/cache/pbuilder/build/cow.13636
I: removed stale ilistfile /var/cache/pbuilder/build/cow.13636/.ilist
I: forking: chroot /var/cache/pbuilder/build/cow.13636 
cowdancer-ilistcreate /.ilist 'find . -xdev -path ./home -prune -o \( \( -type 
l -o -type f \) -a -links +1 -print0 \) | xargs -0 stat --format '%d %i ''
I: Invoking pbuilder
I: forking: pbuilder build --buildplace /var/cache/pbuilder/build/cow.13636 
--buildresult /var/cache/pbuilder/result/ --mirror 
http://ftp.de.debian.org/debian/ --distribution sid --no-targz 
--internal-chrootexec 'chroot /var/cache/pbuilder/build/cow.13636 cow-shell' 
/home/michael/debian/build-area/python-xmp-toolkit/python-xmp-toolkit_2.0.1+git20140309.5437b0a-6.dsc
I: Running in no-targz mode
I: pbuilder: network access will be disabled during build
I: Current time: Fri Jan 11 17:39:00 CET 2019
I: pbuilder-time-stamp: 1547224740
I: copying local configuration
W: --override-config is not set; not updating apt.conf Read the manpage 
for details.
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: policy-rc.d already exists
I: using eatmydata during job
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying 
[/home/michael/debian/build-area/python-xmp-toolkit/python-xmp-toolkit_2.0.1+git20140309.5437b0a-6.dsc]
I: copying 
[/home/michael/debian/build-area/python-xmp-toolkit/python-xmp-toolkit_2.0.1+git20140309.5437b0a.orig.tar.gz]
I: copying 

Bug#918236: transient bug in ruby-prawn

[Cédric Boutillier]

Control: tag -1 notfound ruby-prawn-svg/0.28.0-2

This was caused during the transition to ruby-prawn 2.2.0 during which
a mismatch for version of ruby-ttfunk occurred.

This is now solved, and has no root in this package.
Closing.

Cheers,

Cédric


signature.asc
Description: PGP signature

Bug#918236: marked as done (ruby-prawn-svg: FTBFS in sid)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 17:40:07 +0100
with message-id <2019064007.GA32200@esfahan>
and subject line transient bug in ruby-prawn
has caused the Debian Bug report #918236,
regarding ruby-prawn-svg: FTBFS in sid
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.)


-- 
918236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ruby-prawn-svg
Version: 0.28.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby

[... snipped ...]

cmath (default: 1.0.0)
css_parser (1.6.0)
csv (default: 1.0.0)
date (default: 1.0.0)
dbm (default: 1.0.0)
did_you_mean (1.2.1)
diff-lcs (1.3)
etc (default: 1.0.0)
fcntl (default: 1.0.0)
fiddle (default: 1.0.0)
fileutils (default: 1.0.2)
gdbm (default: 2.0.0)
hashery (2.1.2)
io-console (default: 0.4.6)
ipaddr (default: 1.2.0)
json (default: 2.1.0)
minitest (5.11.3)
net-telnet (0.1.1)
openssl (default: 2.1.2)
pdf-core (0.6.1)
pdf-reader (2.1.0)
power_assert (1.1.1)
prawn (2.1.0)
psych (default: 3.0.2)
public_suffix (3.0.3)
rake (12.3.1)
rdoc (default: 6.0.1)
rspec (3.8.0)
rspec-core (3.8.0)
rspec-expectations (3.8.1)
rspec-mocks (3.8.0)
rspec-support (3.8.0)
ruby-rc4 (0.1.5)
scanf (default: 1.0.0)
sdbm (default: 1.0.0)
stringio (default: 0.0.1)
strscan (default: 1.0.0)
test-unit (3.2.8)
thread_order (1.1.0)
ttfunk (1.5.1)
webrick (default: 1.4.2)
xmlrpc (0.3.0)
zlib (default: 1.0.0)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-prawn-svg 
returned exit code 1
make: *** [debian/rules:6: binary-indep] Error 1
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Control: tag -1 notfound ruby-prawn-svg/0.28.0-2

This was caused during the transition to ruby-prawn 2.2.0 during which
a mismatch for version of ruby-ttfunk occurred.

This is now solved, and has no root in this package.
Closing.

Cheers,

Cédric


signature.asc
Description: PGP signature
--- End Message ---

Bug#919006: FTBFS: test failure with new DBD::SQLite

[gregor herrmann]

Source: libclass-dbi-plugin-type-perl
Version: 0.02-8
Severity: serious
Tags: upstream buster sid ftbfs
Justification: fails to build from source
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=128135

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As seen on ci.debian.net, libclass-dbi-plugin-type-perl fails its
test suite since recently:

t/1.t .. 
1..6
ok 1 - use Class::DBI::Plugin::Type;
not ok 2 - notes is text
#   Failed test 'notes is text'
#   at t/1.t line 28.
#   undef
# doesn't match '(?^:text|blob)'
not ok 3 - tasted is a date
#   Failed test 'tasted is a date'
#   at t/1.t line 29.
#  got: undef
# expected: 'date'
not ok 4 - price is decimal
#   Failed test 'price is decimal'
#   at t/1.t line 30.
#   undef
# doesn't match '(?^:^decimal)'
not ok 5 - id is integer
#   Failed test 'id is integer'
#   at t/1.t line 31.
#   undef
# doesn't match '(?^:^int)'
not ok 6 - name is varchar
#   Failed test 'name is varchar'
#   at t/1.t line 32.
#   undef
# doesn't match '(?^:^varchar)'
# Looks like you failed 5 tests of 6.
Dubious, test returned 5 (wstat 1280, 0x500)
Failed 5/6 subtests 

Test Summary Report
- ---
t/1.t (Wstat: 1280 Tests: 6 Failed: 5)
  Failed tests:  2-6
  Non-zero exit status: 5
Files=1, Tests=6,  0 wallclock secs ( 0.03 usr  0.00 sys +  0.10 cusr  0.02 
csys =  0.15 CPU)
Result: FAIL


This can also be seen on cpantesters, and the upstream bug report at
https://rt.cpan.org/Public/Bug/Display.html?id=128135
claims it's related to a newer version of DBD::SQLite
(in Debian libdbd-sqlite3-perl 1.62-1 was uploaded on 2018-12-31).


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlw4xlxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbTihAAuFlaJ6IReFWTZ4sSdEebYPkDeG9fKD5HXayCJJviKDGqcm2t5ay9UA/S
hYVGyFqqUmPR4Atc0CBcnQRwmPg9PxcZ62HnmmRZSYB3PkzAjJJXh4pOQUgCEr3Q
4FGqvmxJyyvBrG3ZcRiunN1jPcNcix2lRttyJ9monxIROERjIEYaKQTjGz8Vxuae
xYfzHO1FOYkp0fi9UPAu7kkAvXGwWAutlwHtIvqdjBV6Ert9hAj2+dFhZcRp1QeZ
6dc+35iUa5J9vyrg7pe37NRcxMGuGntXIfrzISc45pefp/f+coZmCwJUzOt/Cuxe
jn9Lmk+Ju0Pb5djSyvolmbgnRgUOakxR8GAhUEmBCvLp4fYyP1SBQ54zrgpcUrg2
HmsG44q51+6XFtF3SAjfqP1qw9c9DmKkVdt3T3DgqzWP433QK4FN4Uj2va2ZdZ82
b0FBmCedizBEih/ZFj3Km84g9Zk7I7N1E07NySd9CGl7lFs+ATCJpTTU5XkuQypk
CzYumo0JRk5uno6jjxpwFZEdVGTZql/NwXRfwxWOFcW2YxPsmAlZK+Gbm0kxxdR3
7QzZN+hsr2twoVox51emeHjQi9bi9G4GjZYJ6z/2084x2zCQUOjZM4HQUVDan18Q
5zEyzVeYgSAhjVmMuc5MF8TDJjK8yF4wAxe+72d1SieFsyEm5Lw=
=684Z
-END PGP SIGNATURE-

Processed (with 1 error): Re: Bug#919002: CVE's for systemd vulnerabilities CVE-2018-16864, CVE-2018-16865 and CVE-2018-16866

[Debian Bug Tracking System]

Processing control commands:

> forcemerge -1 918841
Bug #919002 [systemd] CVE's for systemd vulnerabilities CVE-2018-16864, 
CVE-2018-16865 and CVE-2018-16866
Unable to merge bugs because:
package of #918841 is 'src:systemd' not 'systemd'
Failed to forcibly merge 919002: Did not alter merged bugs.


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

Bug#918235: transient bug in ruby-prawn

[Cédric Boutillier]

Control: tag -1 notfound ruby-prawn-icon/2.3.0-2

This was caused during the transition to ruby-prawn 2.2.0 during which
a mismatch for version of ruby-ttfunk occurred.

This is now solved, and has no root in this package.
Closing.

Cheers,

Cédric


signature.asc
Description: PGP signature

Bug#918235: marked as done (ruby-prawn-icon: FTBFS in sid)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 17:36:51 +0100
with message-id <2019063651.GA30244@esfahan>
and subject line transient bug in ruby-prawn
has caused the Debian Bug report #918235,
regarding ruby-prawn-icon: FTBFS in sid
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.)


-- 
918235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918235
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ruby-prawn-icon
Version: 2.3.0-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:


[...]
 debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_autoreconf -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
   create-stamp debian/debhelper-build-stamp
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby

[... snipped ...]

Ascii85 (1.0.3)
bigdecimal (default: 1.3.4)
cmath (default: 1.0.0)
csv (default: 1.0.0)
date (default: 1.0.0)
dbm (default: 1.0.0)
did_you_mean (1.2.1)
diff-lcs (1.3)
etc (default: 1.0.0)
fcntl (default: 1.0.0)
fiddle (default: 1.0.0)
fileutils (default: 1.0.2)
gdbm (default: 2.0.0)
hashery (2.1.2)
io-console (default: 0.4.6)
ipaddr (default: 1.2.0)
json (default: 2.1.0)
minitest (5.11.3)
net-telnet (0.1.1)
openssl (default: 2.1.2)
pdf-core (0.6.1)
pdf-reader (2.1.0)
power_assert (1.1.1)
prawn (2.1.0)
psych (default: 3.0.2)
rake (12.3.1)
rdoc (default: 6.0.1)
rspec (3.8.0)
rspec-core (3.8.0)
rspec-expectations (3.8.1)
rspec-mocks (3.8.0)
rspec-support (3.8.0)
ruby-rc4 (0.1.5)
scanf (default: 1.0.0)
sdbm (default: 1.0.0)
stringio (default: 0.0.1)
strscan (default: 1.0.0)
test-unit (3.2.8)
thread_order (1.1.0)
ttfunk (1.5.1)
webrick (default: 1.4.2)
xmlrpc (0.3.0)
zlib (default: 1.0.0)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-prawn-icon 
returned exit code 1
make: *** [debian/rules:9: binary-indep] Error 1
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


The build was made in my autobuilder with "dpkg-buildpackage -A"
but it also fails here:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Control: tag -1 notfound ruby-prawn-icon/2.3.0-2

This was caused during the transition to ruby-prawn 2.2.0 during which
a mismatch for version of ruby-ttfunk occurred.

This is now solved, and has no root in this package.
Closing.

Cheers,

Cédric


signature.asc
Description: PGP signature
--- End Message ---

Processed (with 1 error): fixed with 3.8.1-2 upload

[Debian Bug Tracking System]

Processing control commands:

> tag -1 fixed ryby-rspec-rails/3.8.1-2
Unknown tag/s: ryby-rspec-rails/3.8.1-2.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore.

Bug #918605 [src:ruby-rspec-rails] ruby-rspec-rails FTBFS with rails 5.2
Added tag(s) fixed.

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

Bug#918605: marked as done (ruby-rspec-rails FTBFS with rails 5.2)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 17:12:19 +0100
with message-id <2019061219.GB2@esfahan>
and subject line fixed with 3.8.1-2 upload
has caused the Debian Bug report #918605,
regarding ruby-rspec-rails FTBFS with rails 5.2
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.)


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

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

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

RUBYLIB=/build/1st/ruby-rspec-rails-3.8.0/debian/ruby-rspec-rails/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-rspec-rails/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/rspec/\*\*/\*_spec.rb --format 
documentation
Run options: include {:focus=>true}

All examples were filtered out; ignoring {:focus=>true}

Randomized with seed 3554

ActiveJob matchers
  have_been_enqueued
passes with default jobs count (exactly one)
counts all enqueued jobs
fails when job is not enqueued
passes when negated
  have_enqueued_job
passes when using alias
fails when too many jobs enqueued
passes multiple arguments to with block
reports correct number in fail error message
raises ArgumentError when no Proc passed to expect
generates failure message with at most hint
passes with :thrice count
does not have an enqueued job when providing at of :no_wait and there is a 
wait
generates failure message with at least hint
passes with multiple jobs
passes with provided arguments containing global id object
fails with with block with incorrect data
throws descriptive error when no test adapter set
passes with at_most count when enqueued jobs are under limit
passes with job name
passes with at_least count when enqueued jobs are over limit
passes with default jobs count (exactly one)
only calls with block if other conditions are met
passes with :twice count
generates failure message with all provided options
has an enqueued job when providing at of :no_wait and there is no wait
passes with provided queue name
fails when job is not enqueued
passes with provided argument matchers
passes with :once count
passess deserialized arguments to with block
passes with provided arguments
has an enqueued job when not providing at and there is a wait
passes with provided at date
passes when negated
counts only jobs enqueued in block
fails when negated and job is enqueued

RSpec::Rails::ViewExampleGroup
  routes helpers collides with asset helpers
uses routes helpers
  #view
delegates to _view
is accessible to hooks
  behaves like an rspec-rails example group mixin
adds does not add `:type` metadata on inclusion
when `infer_spec_type_from_file_location!` is configured
  includes itself in example groups tagged with `:type => :view`
  for an example group defined in a file in the .\spec\views\ directory
allows users to override the type
applies configured `before(:context)` hooks with `:type => :view` 
metadata
includes itself in the example group
tags groups in that directory with `:type => :view`
  for an example group defined in a file in the ./spec/views/ directory
tags groups in that directory with `:type => :view`
applies configured `before(:context)` hooks with `:type => :view` 
metadata
allows users to override the type
includes itself in the example group
when `infer_spec_type_from_file_location!` is not configured
  includes itself in example groups tagged with `:type => :view`
  for an example group defined in a file in the ./spec/views/ directory
does not tag groups in that directory with `:type => :view`
does not include itself in the example group
  for an example group defined in a file in the .\spec\views\ directory
does not include itself in the example group
does not tag groups in that directory with `:type => 

Bug#918605: fixed with 3.8.1-2 upload

[Cédric Boutillier]

Control: tag -1 fixed ryby-rspec-rails/3.8.1-2

Hi,

This has been fixed with the upload of ruby-rspec-rails/3.8.1-2 in
unstable.

Cheers,

Cédric


signature.asc
Description: PGP signature

Bug#841889: marked as done (grub-pc: ucf prompt that wants to change nothing except remove admin-defined config)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 15:52:54 +
with message-id 
and subject line Bug#812574: fixed in grub2 2.02+dfsg1-10
has caused the Debian Bug report #812574,
regarding grub-pc: ucf prompt that wants to change nothing except remove 
admin-defined config
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.)


-- 
812574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-pc
Version: 2.02~beta3-1
Severity: important
Justification: Policy §3.9.1

Upgrading GRUB:

Unpacking grub-pc (2.02~beta3-1) over (2.02~beta2-36) ...
[…]
Setting up grub-pc (2.02~beta3-1) ...

Then I get an ucf prompt, and the entire diff is:

Package configuration

┌─┤ Configuring grub-pc 
├─┐
│   
  │
│ Line by line differences between versions 
  │
│   
  │
│ --- /etc/default/grub root.root 0644 2016-04-21 15:08:07  
  │
│ +++ /tmp/grub.Z2QbwNev1k root.root 0644 2016-10-24 07:45:50   
  │
│ @@ -8,8 +8,6 @@   
  │
│  GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` 
  │
│  GRUB_CMDLINE_LINUX_DEFAULT=""
  │
│  GRUB_CMDLINE_LINUX="net.ifnames=0 kaslr" 
  │
│ -GRUB_DISABLE_SUBMENU=y   
  │
│ -GRUB_FONT=/usr/share/grub/FixedMisc.pf2  
  │
│   
  │
│  # Uncomment to enable BadRAM filtering, modify to suit your 
needs  │
│  # This works with Linux (no patch required) and with any kernel 
that obtains   │
│ @@ -25,7 +23,7 @@ 
  │
│  #GRUB_GFXMODE=640x480
  │
│   
  │
│  # Uncomment if you don't want GRUB to pass "root=UUID=xxx" 
parameter to Linux  │
│ -GRUB_DISABLE_LINUX_UUID=true 
  │
│ +#GRUB_DISABLE_LINUX_UUID=true
  │
│   
  │
│  # Uncomment to disable generation of recovery mode menu entries  
  │
│  #GRUB_DISABLE_RECOVERY="true"
  │
│   
  │
│   
  │
│   
  │

└─┘


This is *nothing* changed in the base config, and almost *all*
changes the local admin did reverted.

Packages, by policy, “should try to minimize the amount of prompting
they need to do”, and, furthermore, “an upgrade should not ask the same
questions again”. I also expect a package to respect the local admin’s
configuration changes, so this is border-line RC.



-- Package-specific info:

*** BEGIN /proc/mounts
/dev/mapper/vg--ci--busyapps-lv--root / ext4 
rw,noatime,errors=remount-ro,data=ordered 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export 

Bug#908162: marked as done (grub-efi-amd64-signed: cryptdisk support missing)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 15:52:54 +
with message-id 
and subject line Bug#908162: fixed in grub2 2.02+dfsg1-10
has caused the Debian Bug report #908162,
regarding grub-efi-amd64-signed: cryptdisk support missing
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.)


-- 
908162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-efi-amd64-signed
Version: 1+2.02+dfsg1+6
Severity: critical
Justification: makes the system completely unbootable

When grub-efi-amd64-signed is installed and /boot is on an encrypted
file system and GRUB_ENABLE_CRYPTODISK=y is present in
/etc/default/grub, the system fails to boot, since cryptodisk appears to
be missing from the installed image.

Removing grub-efi-amd64-signed works around the problem, since it then
seems to use a locally built image?  I suspect just adding cryptodisk to
GRUB_MODULES in grub's debian/build-efi-images would be sufficient to
make this work correctly.

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

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

-- no debconf information

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
--- End Message ---
--- Begin Message ---
Source: grub2
Source-Version: 2.02+dfsg1-10

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

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

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

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated grub2 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: Fri, 11 Jan 2019 15:24:20 +
Source: grub2
Binary: grub2 grub-linuxbios grub-efi grub-common grub2-common grub-emu 
grub-emu-dbg grub-pc-bin grub-pc-dbg grub-pc grub-rescue-pc grub-coreboot-bin 
grub-coreboot-dbg grub-coreboot grub-efi-ia32-bin grub-efi-ia32-dbg 
grub-efi-ia32 grub-efi-ia32-signed-template grub-efi-amd64-bin 
grub-efi-amd64-dbg grub-efi-amd64 grub-efi-amd64-signed-template 
grub-efi-ia64-bin grub-efi-ia64-dbg grub-efi-ia64 grub-efi-arm-bin 
grub-efi-arm-dbg grub-efi-arm grub-efi-arm64-bin grub-efi-arm64-dbg 
grub-efi-arm64 grub-efi-arm64-signed-template grub-ieee1275-bin 
grub-ieee1275-dbg grub-ieee1275 grub-firmware-qemu grub-uboot-bin 
grub-uboot-dbg grub-uboot grub-xen-bin grub-xen-dbg grub-xen grub-xen-host 
grub-yeeloong-bin grub-yeeloong-dbg grub-yeeloong grub-theme-starfield 
grub-mount-udeb
Architecture: source
Version: 2.02+dfsg1-10
Distribution: unstable
Urgency: medium
Maintainer: GRUB Maintainers 
Changed-By: Colin Watson 
Description:
 grub-common - GRand Unified Bootloader (common files)
 grub-coreboot - GRand Unified Bootloader, version 2 (Coreboot version)
 grub-coreboot-bin - GRand Unified Bootloader, version 2 (Coreboot modules)
 grub-coreboot-dbg - GRand Unified Bootloader, version 2 (Coreboot debug files)
 grub-efi   - GRand Unified Bootloader, version 2 (dummy package)
 grub-efi-amd64 - GRand Unified Bootloader, version 2 (EFI-AMD64 version)
 grub-efi-amd64-bin - GRand Unified Bootloader, version 2 (EFI-AMD64 modules)
 grub-efi-amd64-dbg - GRand Unified Bootloader, version 2 (EFI-AMD64 debug 
files)
 grub-efi-amd64-signed-template - GRand Unified Bootloader, version 2 
(EFI-AMD64 signing template)
 grub-efi-arm - GRand Unified Bootloader, version 2 (ARM UEFI version)
 grub-efi-arm-bin - GRand Unified Bootloader, version 2 (ARM UEFI modules)
 grub-efi-arm-dbg - GRand Unified Bootloader, version 2 (ARM UEFI debug files)
 grub-efi-arm64 - GRand Unified Bootloader, version 2 (ARM64 UEFI version)
 grub-efi-arm64-bin - GRand Unified Bootloader, version 2 (ARM64 UEFI modules)
 grub-efi-arm64-dbg - GRand Unified Bootloader, version 2 (ARM64 UEFI debug 
files)
 grub-efi-arm64-signed-template - GRand 

Bug#812574: marked as done (grub-pc: wants to overwrite admin configuration on each upgrade)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 15:52:54 +
with message-id 
and subject line Bug#812574: fixed in grub2 2.02+dfsg1-10
has caused the Debian Bug report #812574,
regarding grub-pc: wants to overwrite admin configuration on each upgrade
to be marked as done.

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

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


-- 
812574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-pc
Version: 2.02~beta2-35
Severity: serious
Justification: Policy 10.7.3 (MUST), 3.9.1 (SHOULD)

On each upgrade, I get prompted by ucf, despite there never being
any diff introduced by grub-pc, i.e. all it wants is to remove my
local admin-provided changes and revert to the package’s default:

Package configuration

┌─┤ Configuring grub-pc 
├─┐
│   
  │
│ Line by line differences between versions
│
│ --- /etc/default/grub 2016-01-12 20:02:57.475863370 +0100
│ +++ /tmp/grub.urpnpGUUyO 2016-01-25 09:21:12.178819012 +0100
│ @@ -8,8 +8,6 @@
│  GRUB_DISTRIBUTOR=sb_release -i -s 2> /dev/null || echo Debian
│  GRUB_CMDLINE_LINUX_DEFAULT=""
│  GRUB_CMDLINE_LINUX="syscall.x32=y net.ifnames=0"
│ -GRUB_DISABLE_SUBMENU=y
│ -GRUB_FONT=/usr/share/grub/FixedMisc.pf2
│
│  # Uncomment to enable BadRAM filtering, modify to suit your needs
│  # This works with Linux (no patch required) and with any kernel 
that obtains
│ @@ -22,10 +20,10 @@
│  # The resolution used on graphical terminal
│  # note that you can use only modes which your graphic card 
supports via VBE
│  # you can see them in real GRUB with the command beinfo'
│ -GRUB_GFXMODE=1280x1024
│ +#GRUB_GFXMODE=640x480
│
│  # Uncomment if you don't want GRUB to pass "root=UUID=xxx" 
parameter to Linux
│ -GRUB_DISABLE_LINUX_UUID=true
│ +#GRUB_DISABLE_LINUX_UUID=true
│
│  # Uncomment to disable generation of recovery mode menu entries
│  #GRUB_DISABLE_RECOVERY="true"
│
│ 
│   
  │

└─┘

This is not only rather annoying but also violates the part in Policy
about configuration file handling “must cope with all the variety
 of ways `dpkg' can call maintainer scripts, must not overwrite or
 otherwise mangle the user's configuration without asking, must not ask
 unnecessary questions (particularly during upgrades), and must
 otherwise be good citizens.”

Please ensure to use ucf only in a way that only asks the user or
merges when there are diffs between the package-provided versions
(old and new) of the package, not to revert the admin-made changes.

-- Package-specific info:

*** BEGIN /proc/mounts
/dev/dm-0 / ext4 rw,relatime,data=ordered 0 0
/dev/md1 /boot ext4 rw,noatime,data=ordered 0 0
/dev/dm-0 /var/lib/schroot/mount/vncsess ext4 rw,relatime,data=ordered 0 0
/dev/dm-0 /var/lib/schroot/mount/vncsess/home ext4 rw,relatime,data=ordered 0 0
/dev/dm-0 /var/lib/schroot/mount/vncsess/var/lib/libvirt ext4 
rw,relatime,data=ordered 0 0
/dev/dm-0 /var/lib/schroot/mount/vncsess/var/cache/pbuilder ext4 
rw,relatime,data=ordered 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"

Bug#919000: Missing distribution 'keyring'

[Michael Krusemark]

Package: spyder3
Version: 3.3.2+dfsg1-1
Severity: critical

pkg_resources.DistributionNotFound: The 'keyring' distribution was not found 
and is required by spyderpkg_resources.DistributionNotFound: The 'keyring' 
distribution was not found and is required by spyder

-- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.155-94.50-default (SMP w/12 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to 
de_DE.UTF-8)
Shell: /bin/sh linked to /usr/bin/bash
Init: unable to detect

Versions of packages spyder3 depends on:
ii  python3-spyder  3.3.2+dfsg1-1
ii  python3.7   3.7.2~rc1-1

spyder3 recommends no packages.

spyder3 suggests no packages.

Versions of packages python3-spyder depends on:
ii  libjs-jquery3.2.1-1
ii  libjs-mathjax   2.7.4+dfsg-1
ii  pylint3 2.1.1-2
ii  python3 3.7.1-2
ii  python3-chardet 3.0.4-1
ii  python3-cloudpickle 0.5.6-1
ii  python3-jedi0.12.0-1.1
ii  python3-nbconvert   5.3.1-1
ii  python3-numpydoc0.7.0-1
ii  python3-pickleshare 0.7.5-1
ii  python3-psutil  5.4.8-1
ii  python3-pycodestyle 2.4.0-2
ii  python3-pyflakes2.0.0-1
ii  python3-pygments2.2.0+dfsg-2
ii  python3-qtawesome   0.4.4+ds1-1
ii  python3-qtconsole   4.3.1-1
ii  python3-qtpy1.3.1-1
ii  python3-rope0.10.5-3
ii  python3-sphinx  1.7.9-1
ii  python3-spyder-kernels  1.0.1+really0.2.4-1
ii  python3-zmq 17.1.2-1
ii  spyder-common   3.3.2+dfsg1-1

Versions of packages python3-spyder suggests:
pn  cython3 
pn  python3-matplotlib  
ii  python3-numpy   1:1.15.4-2
ii  python3-pandas  0.23.3-1
pn  python3-pil 
ii  python3-scipy   1.1.0-2
pn  python3-sympy   

Versions of packages python3-pyqt5 depends on:
ii  libc6 2.28-2
ii  libgcc1   1:8.2.0-12
ii  libpython3.7  3.7.2~rc1-1
ii  libqt5core5a [qtbase-abi-5-11-2]  5.11.2+dfsg-7
ii  libqt5dbus5   5.11.2+dfsg-7
ii  libqt5designer5   5.11.2-5
ii  libqt5gui55.11.2+dfsg-7
ii  libqt5help5   5.11.2-5
ii  libqt5network55.11.2+dfsg-7
ii  libqt5printsupport5   5.11.2+dfsg-7
ii  libqt5test5   5.11.2+dfsg-7
ii  libqt5widgets55.11.2+dfsg-7
ii  libqt5xml55.11.2+dfsg-7
ii  libstdc++68.2.0-12
ii  python3   3.7.1-2
ii  python3-sip [sip-py3api-12.5] 4.19.13+dfsg-1

Versions of packages python3-pyqt5 suggests:
pn  python3-pyqt5-dbg  

-- no debconf information

Bug#918602: marked as done (ruby-haml FTBFS with rails 5.2)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 16:41:56 +0100
with message-id <2019054156.GA32130@esfahan>
and subject line fixed with upload of ruby-haml/5.0.4-1
has caused the Debian Bug report #918602,
regarding ruby-haml FTBFS with rails 5.2
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.)


-- 
918602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-haml
Version: 4.0.7-1
Severity: serious
Tags: ftbfs buster sid

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

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

RUBYLIB=/build/1st/ruby-haml-4.0.7/debian/ruby-haml/usr/lib/ruby/vendor_ruby:. 
GEM_PATH=debian/ruby-haml/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:lib:test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/parser_test.rb" 
"test/helper_test.rb" "test/filters_test.rb" "test/template_test.rb" 
"test/engine_test.rb" "test/util_test.rb" "test/haml-spec/ruby_haml_test.rb" 
/build/1st/ruby-haml-4.0.7/lib/haml/helpers/safe_erubis_template.rb:3:in 
`': uninitialized constant ActionView::Template::Handlers::Erubis 
(NameError)
from 
/build/1st/ruby-haml-4.0.7/lib/haml/helpers/safe_erubis_template.rb:1:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /build/1st/ruby-haml-4.0.7/lib/haml/railtie.rb:21:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /build/1st/ruby-haml-4.0.7/lib/haml.rb:23:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /build/1st/ruby-haml-4.0.7/test/test_helper.rb:25:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /build/1st/ruby-haml-4.0.7/test/parser_test.rb:1:in `'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in 
`require'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:17:in `block in 
'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:5:in `select'
from /usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb:5:in `'
rake aborted!
Command failed with status (1): [ruby -w -I"lib:lib:test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/parser_test.rb" 
"test/helper_test.rb" "test/filters_test.rb" "test/template_test.rb" 
"test/engine_test.rb" "test/util_test.rb" "test/haml-spec/ruby_haml_test.rb" ]

Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /build/1st/ruby-haml-4.0.7/debian/ruby-haml 
returned exit code 1
make: *** [debian/rules:15: binary] Error 1
--- End Message ---
--- Begin Message ---
Control: tag -1 fixed ruby-haml/5.0.4-1

This problem has disappeared with the upload of version 5.0.4-1, which
is compatible with Rails 5.2.

Cheers,

Cédric


signature.asc
Description: PGP signature
--- End Message ---

Bug#915831: marked as done (zfsutils-linux: Upgrading to 0.7.12 breaks during dpkg --configure)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 15:00:53 +
with message-id 
and subject line Bug#915831: fixed in zfs-linux 0.7.12-2
has caused the Debian Bug report #915831,
regarding zfsutils-linux: Upgrading to 0.7.12 breaks during dpkg --configure
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.)


-- 
915831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915831
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zfsutils-linux
Version: 0.7.12-1
Severity: normal

Dear Maintainer,

Tried upgrading from stretch-backports 0.7.11 to testing 0.7.12, because
the package hadn't landed in backports yet, and discovered it broke on
dpkg --configure :
Setting up zfsutils-linux (0.7.12-1) ...
insserv: Service zfs-zed has to be enabled to start service zfs-share
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package zfsutils-linux (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of zfs-zed:
 zfs-zed depends on zfsutils-linux (>= 0.7.12-1); however:
  Package zfsutils-linux is not configured yet.

Someone else had reported a similar problem upstream to ZoL from Ubuntu's
packages, at:
https://github.com/zfsonlinux/zfs/issues/8127

I worked up a terrible hackjob of a patch to work around this long enough to
install it and then reverted the patch (attached), but there's probably a better
way to handle this.

(Don't mind the arc_summary changed warning; I've been testing improvements to 
it.)

-- System Information:
Debian Release: 9.6
  APT prefers stable-debug
  APT policy: (1000, 'stable-debug'), (1000, 'stable'), (900, 'testing-debug'), 
(900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (500, 
'stable-updates'), (500, 'proposed-updates-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages zfsutils-linux depends on:
ii  libblkid12.29.2-1+deb9u1
ii  libc62.24-11+deb9u3
ii  libnvpair1linux  0.7.12-1
ii  libuuid1 2.29.2-1+deb9u1
ii  libuutil1linux   0.7.12-1
ii  libzfs2linux 0.7.12-1
ii  libzpool2linux   0.7.12-1
ii  python3  3.5.3-1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages zfsutils-linux recommends:
ii  lsb-base9.20161125
ii  zfs-dkms [zfs-modules]  0.7.12-1
ii  zfs-zed 0.7.12-1

Versions of packages zfsutils-linux suggests:
ii  nfs-kernel-server  1:1.3.4-2.1
ii  samba-common-bin   2:4.5.12+dfsg-2+deb9u4
ii  zfs-initramfs  0.7.12-1

-- Configuration Files:
/etc/sudoers.d/zfs [Errno 13] Permission denied: '/etc/sudoers.d/zfs'

-- debconf-show failed

-- debsums errors found:
debsums: changed file /usr/sbin/arc_summary (from zfsutils-linux package)
diff --git a/init.d/zfs-share b/init.d/zfs-share
index 6564720..2e800d1 100755
--- a/init.d/zfs-share
+++ b/init.d/zfs-share
@@ -9,8 +9,8 @@
 #
 ### BEGIN INIT INFO
 # Provides:  zfs-share
-# Required-Start:$local_fs $network $remote_fs zfs-mount zfs-zed
-# Required-Stop: $local_fs $network $remote_fs zfs-mount zfs-zed
+# Required-Start:$local_fs $network $remote_fs zfs-mount
+# Required-Stop: $local_fs $network $remote_fs zfs-mount
 # Default-Start: 2 3 4 5
 # Default-Stop:  0 1 6
 # Should-Start:  iscsi iscsitarget istgt scst nfs-kernel-server samba 
samba4 zfs-mount zfs-zed
@@ -34,7 +34,7 @@

 do_depend()
 {
-   after sysfs zfs-mount zfs-zed
+   after sysfs zfs-mount
keyword -lxc -openvz -prefix -vserver
 }
--- End Message ---
--- Begin Message ---
Source: zfs-linux
Source-Version: 0.7.12-2

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

Debian distribution maintenance software
pp.
Aron Xu  (supplier of updated zfs-linux 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)

Bug#918982: libspandsp-doc: missing Breaks+Replaces: libspandsp-dev (<< 0.0.6+dfsg-1)

[Andreas Beckmann]

Package: libspandsp-doc
Version: 0.0.6+dfsg-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/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../libspandsp-doc_0.0.6+dfsg-1_all.deb ...
  Unpacking libspandsp-doc (0.0.6+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libspandsp-doc_0.0.6+dfsg-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libspandsp-dev/DueDiligence', which is 
also in package libspandsp-dev:amd64 0.0.6+dfsg-0.1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libspandsp-doc_0.0.6+dfsg-1_all.deb


This is probably caused by a behavioral change of dh_installdocs
in debhelper compat level 11.


cheers,

Andreas


libspandsp-dev=0.0.6+dfsg-0.1_libspandsp-doc=0.0.6+dfsg-1.log.gz
Description: application/gzip

Bug#915886: marked as done (zfs-dkms: module FTBFS for 4.18.0-3-amd64: NR_FILE_PAGES in either node_stat_item or zone_stat_item: NOT FOUND)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 13:35:59 +
with message-id <2019033559.GA23073@Asuna>
and subject line Re: zfs-dkms: module FTBFS for 4.18.0-3-amd64: NR_FILE_PAGES 
in either node_stat_item or zone_stat_item: NOT FOUND
has caused the Debian Bug report #915886,
regarding zfs-dkms: module FTBFS for 4.18.0-3-amd64: NR_FILE_PAGES in either 
node_stat_item or zone_stat_item: NOT FOUND
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.)


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

Hi,

# dkms build -k 4.18.0-3-amd64 zfs/0.7.12   

Kernel preparation unnecessary for this kernel.  Skipping...

Running the pre_build script:
checking for gawk... no
checking for mawk... mawk
checking metadata... META file
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether make supports nested variables... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... none
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu 
format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... 
func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /bin/dd
checking how to truncate binary pipes... /bin/dd bs=4096 count=1
checking for mt... no
checking if : is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared 
libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking dependency style of gcc... none
checking 

Bug#909974: backports.ssl-match-hostname should be removed for buster

[Felipe Sateler]

On Tue, Oct 2, 2018 at 4:22 PM Felipe Sateler  wrote:

> Hi Matthias, Ivo,
>
> On Sun, 30 Sep 2018 22:59:26 +0200 Ivo De Decker  wrote:
> > clone 869896 -1
> > retitle -1 remove unneeded dependency on backports.ssl-match-hostname
> > block 869896 by -1
> > clone -1 -2 -3 -4 -5
> > reassign -1 libcloud
> > reassign -2 python-docker
> > reassign -3 websocket-client
> > reassign -4 docker-compose
> > reassign -5 sagemath
> > thanks
>

Turns out the version of match_hostname in py2 does not accept ip addresses:

py2:
ssl.match_hostname = match_hostname(cert, hostname)
Verify that *cert* (in decoded format as returned by
SSLSocket.getpeercert()) matches the *hostname*.  RFC 2818 and RFC 6125
rules are followed, but IP addresses are not accepted for *hostname*.

CertificateError is raised on failure. On success, the function
returns nothing.

py3
ssl.match_hostname = match_hostname(cert, hostname)
Verify that *cert* (in decoded format as returned by
SSLSocket.getpeercert()) matches the *hostname*.  RFC 2818 and RFC 6125
rules are followed.

The function matches IP addresses rather than dNSNames if hostname is a
valid ipaddress string. IPv4 addresses are supported on all platforms.
IPv6 addresses are supported on platforms with IPv6 support (AF_INET6
and inet_pton).

CertificateError is raised on failure. On success, the function
returns nothing.

So, if python2 backport of match_hostname does not match behavior of
python3.5, I cannot drop the dependency. I have reverted the change and
reopened this bug.

I urge you to reconsider if the py2 version really needs to be dropped.

-- 

Saludos,
Felipe Sateler

Bug#914804: fixed in pycuda 2018.1.1-2

[Graham Inggs]

Control: severity -1 important

Hi Santiago

On 2019/01/11 14:54, Santiago Vila wrote:

Hi. Sorry for the reopening but this is apparently still happening.
The error is now slightly different:

/usr/bin/ld: cannot find -lcuda
collect2: error: ld returned 1 exit status
error: command 'x86_64-linux-gnu-g++' failed with exit status 1


The error you now see has nothing to do with boost1.67.

I believe this is due to the following temporary change in 
nvidia-cuda-toolkit 9.2.148-3 [1]:


   * Relax the libcuda1 dependency to start the transition in unstable
 while the required driver is still in experimental.

I'm lowering severity since pycuda is in contrib and not autobuilt.
This bug should not block it from migrating to testing.

Regards
Graham


[1] 
https://packages.qa.debian.org/n/nvidia-cuda-toolkit/news/20190108T233632Z.html

Processed: Re: Bug#914804: fixed in pycuda 2018.1.1-2

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #914804 [src:pycuda] pycuda: FTBFS with boost1.67: /usr/bin/ld: cannot find 
-lcuda
Severity set to 'important' from 'serious'

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

Bug#916885: marked as done (pass-tomb: depends on kcov which is not in testing)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 13:05:43 +
with message-id 
and subject line Bug#916885: fixed in pass-tomb 1.1-4
has caused the Debian Bug report #916885,
regarding pass-tomb: depends on kcov which is not in testing
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.)


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

pass-tomb build-depends on kcov which is not in testing. britney migrated
the package to testing regardless. However the package is not fit for a
release because it can not be built in testing as of now [0].

This bug can be closed either once kcov migrates to testing or if
pass-tomb drops the build-dependency on kcov.

[0] 
https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/pass-tomb.html

Sebastian
--- End Message ---
--- Begin Message ---
Source: pass-tomb
Source-Version: 1.1-4

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

Debian distribution maintenance software
pp.
David Kunz  (supplier of updated pass-tomb 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: Fri, 11 Jan 2019 13:27:49 +0100
Source: pass-tomb
Binary: pass-extension-tomb
Architecture: source all
Version: 1.1-4
Distribution: unstable
Urgency: medium
Maintainer: David Kunz 
Changed-By: David Kunz 
Description:
 pass-extension-tomb - lightweight directory-based password manager (tomb 
extension)
Closes: 916885
Changes:
 pass-tomb (1.1-4) unstable; urgency=medium
 .
   * Remove build depends because the testsuite was already deactivated
 (Closes: #916885).
Checksums-Sha1:
 ea8eafac9dd2c936c139aeea1c9594466b1a2848 1848 pass-tomb_1.1-4.dsc
 9a6d80aab3edc5c236df56e70d219d1c544e7160 1888 pass-tomb_1.1-4.debian.tar.xz
 b746cb3c85d90ba00f4a7c449f27f0ca16e1f87e 9100 pass-extension-tomb_1.1-4_all.deb
 e680eb6a7a1839445c85ecfb31ccfc91e35913fb 5255 pass-tomb_1.1-4_amd64.buildinfo
Checksums-Sha256:
 52c4424e05a2bb7c5cf1f169dbadbf31d5f3c6f46764564ec5f2739ce3f81c9c 1848 
pass-tomb_1.1-4.dsc
 0deeb276f3fb08ff023561bb89a8d3cd7791384d159d90ec7e93b12c67316c86 1888 
pass-tomb_1.1-4.debian.tar.xz
 bc060ca7eb21272cd50e68898b6baae0a4ac2f9daa59e8023f948dd87756fa9d 9100 
pass-extension-tomb_1.1-4_all.deb
 d5c01ef1cfa49ba0442ca862f6b4ad40a8e1a3ad543f8a26a073f17b866789e1 5255 
pass-tomb_1.1-4_amd64.buildinfo
Files:
 3e763e96f3f9b68d688bdad7da537657 1848 admin optional pass-tomb_1.1-4.dsc
 4f0f131e6aa1ddf028640c1e41aab870 1888 admin optional 
pass-tomb_1.1-4.debian.tar.xz
 0e1c54cd66c0897635cb4a27e11fa6bd 9100 admin optional 
pass-extension-tomb_1.1-4_all.deb
 0fd8b13be249e7abc2e0b7ab65e04a80 5255 admin optional 
pass-tomb_1.1-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAlw4jyAACgkQVc8b+Yar
uccG+xAAm3Z4KcfHAm6BtW30GeHRXcMAY1zu8piEunAdKwgEs0AmqquFVHSk1/83
wdDERU1uhgvU2qcQnQXwdZBTYboTHL4p+yBqz48A6qVY2WIPfEFwLjSBLtILZLF4
f52fFPmkm/w+Bitsd5Y0IGVollhH8v9J9x7niKhRZy4sfQBXu8OahULoZwPDQJgp
G5lajNTOyDIoLD7wjCYVpyAl7Qv95olDBN/dynx/UMOnREjYMz87CTC4oj3IQTIN
TTcOZPWMtMuVQoRHwRVRrT8a6YC3Jhj+JK8KlLeuhwoWrHrl+7yMe25Czm2HLHPj
SKdiGcrdAhrPeuXZGnLOAY4h6AZZ63AV0zpx//RaM3/FDuiVcZh5S1Jba+TAizXl
7GCD/OnR4QjPHDRTuGvgETl0jXcwioIv+jPos+tL9Dl973jnow93PDm4ZbmPeEpT
Lw+oGQSLooxXcgRjAI8cMigUaE6YuO/GYe4UNPxZJE9mZ0yTkEoqEhWcxerNnBG0
4dj3CthdRC0RDp1BBPZ0iAeT4VIDn5ucpDRb4vgWLu7RPFwopN12WE8iZfw44BLE
ZSEsKFcB5u8GqrDhESDYs/sU+pKBKvdVYNh1sYqdwLPO8uc1WfmjxudCydFBStdo
W5jjGAwhQbTc/Cxk1hD1N4yxwsWSlBcHcTvk9FG8P5h77DNp434=
=aqKi
-END PGP SIGNATURE End Message ---

Bug#907624: marked as done (ffindex: ffindex_modify segfaults during autopkgtest)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 13:04:05 +
with message-id 
and subject line Bug#907624: fixed in ffindex 0.9.9.8-1
has caused the Debian Bug report #907624,
regarding ffindex: ffindex_modify segfaults during autopkgtest
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.)


-- 
907624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ffindex
Version: 0.9.9.7+soedinglab+git20180802-1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Since the upload of version 0.9.9.7+soedinglab+git20180802-1 the
autopkgtest of your package started to fail. I have copied the output below.

Could you please investigate? Currently this failure is contributing to
delaying migration to testing with 13 days. You probably want to raise
the severity of this bug if the segfault doesn't only happen in some
corner-case of the test.

Paul

https://ci.debian.net/data/autopkgtest/unstable/amd64/f/ffindex/757862/log.gz

autopkgtest [01:45:16]: test run-unit-test: [---
+ ffindex_build -s ./test.data ./test.ffindex ./data ./data2
+ ffindex_get ./test.data ./test.ffindex a b foo
+ tee ./test.out
a
bb
fooo
fooo
+ ffindex_modify -u ./test.ffindex b
/tmp/autopkgtest-lxc.vvrqco0v/downtmp/build.ZBE/src/debian/tests/run-unit-test:
line 21:   897 Segmentation fault  ffindex_modify -u ./test.ffindex b
autopkgtest [01:45:16]: test run-unit-test: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ffindex
Source-Version: 0.9.9.8-1

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated ffindex 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: Fri, 11 Jan 2019 13:40:22 +0100
Source: ffindex
Binary: ffindex libffindex0 libffindex0-dev
Architecture: source
Version: 0.9.9.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 ffindex- simple index/database for huge amounts of small files
 libffindex0 - library for simple index/database for huge amounts of small files
 libffindex0-dev - library for simple index/database for huge amounts of small 
files
Closes: 907624
Changes:
 ffindex (0.9.9.8-1) unstable; urgency=medium
 .
   * Revert again to original code which now added the interface for
 hhsuite
 Closes: #907624
   * debhelper 12
Checksums-Sha1:
 fba2dcd334278a5e15d91db75ef008a0d90cd859 2171 ffindex_0.9.9.8-1.dsc
 3180441ead070e1dbe1ac3fb62dcc826cd83e1f5 37527 ffindex_0.9.9.8.orig.tar.gz
 5f8a12961188b359cf182038c9e409d6d8f8c169 14604 ffindex_0.9.9.8-1.debian.tar.xz
Checksums-Sha256:
 d8bd5cf46cd2538ab98099df1a23acd39182bd32572a360f7213f5ddda52ce20 2171 
ffindex_0.9.9.8-1.dsc
 bb1b2af511b07e5cdeead9278b6955aaf7e3fdea21e3c8d498a64d099b886378 37527 
ffindex_0.9.9.8.orig.tar.gz
 5d68b070903b177542d4f6295743a3ea3bd74481edb7bf5e54705cf9838417ac 14604 
ffindex_0.9.9.8-1.debian.tar.xz
Files:
 009dcc0cbfdf10ec2243c9945385f513 2171 science optional ffindex_0.9.9.8-1.dsc
 5c3735dd6a327a8ca487a315edc95f49 37527 science optional 
ffindex_0.9.9.8.orig.tar.gz
 4581acac69a70e25d01684c663bf5535 14604 science optional 
ffindex_0.9.9.8-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlw4kHwRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEvWQ//c04+/8vgc350LXoZQNMWDQ62zgUmiy02
1jKjBF8Fp11LcG10v5ovfS8Dmd0CaxQBCU/ltNVDrJRRLH6riI4iUc9A9I/IAJ8U
sMV7Xfnh1gulC0eBery8J1SSwkav7ZgfSmxa8g0mV/S5IPc/BQzQOhIHL2E/HPr8
p0M98AbEAAv+sa6agpV+loBMUVCm6UaD4cHxWvBtOScpiW4tusmePYUdpyITtlS8
pAbSeqAWZSpYLgvQEEKd/m0Ykc2+WuhKTVBilNtZ5xfv+SzHtOte3wOWiu4xA9Hx
+BssTgwIxUFrVl8w5j2W+gC/FVIcgSTH/IVjMaJ7oV3V9yaClVuv8gGVl6WFaYu+
H2sqg2z8Baiqy3gT8P0MKuGmKLOtIRG26RjUv7nznaO9DlV1oBNybJtSmBQd5riQ
Q5Osp96Q4W6vfbk7wv17kVlbcm1lACN4gIT1fL0QR8s7nsjIcpIeclyz6sGEXGif

Processed: Re: Bug#914804: fixed in pycuda 2018.1.1-2

[Debian Bug Tracking System]

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

> found 914804 2018.1.1-2
Bug #914804 {Done: Tomasz Rybak } [src:pycuda] pycuda: 
FTBFS with boost1.67: /usr/bin/ld: cannot find -lboost_python-py27
Marked as found in versions pycuda/2018.1.1-2; no longer marked as fixed in 
versions pycuda/2018.1.1-2 and reopened.
> retitle 914804 pycuda: FTBFS with boost1.67: /usr/bin/ld: cannot find -lcuda
Bug #914804 [src:pycuda] pycuda: FTBFS with boost1.67: /usr/bin/ld: cannot find 
-lboost_python-py27
Changed Bug title to 'pycuda: FTBFS with boost1.67: /usr/bin/ld: cannot find 
-lcuda' from 'pycuda: FTBFS with boost1.67: /usr/bin/ld: cannot find 
-lboost_python-py27'.
> thanks
Stopping processing here.

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

Bug#914804: fixed in pycuda 2018.1.1-2

[Santiago Vila]

found 914804 2018.1.1-2
retitle 914804 pycuda: FTBFS with boost1.67: /usr/bin/ld: cannot find -lcuda
thanks

Hi. Sorry for the reopening but this is apparently still happening.
The error is now slightly different:

/usr/bin/ld: cannot find -lcuda
collect2: error: ld returned 1 exit status
error: command 'x86_64-linux-gnu-g++' failed with exit status 1

I tried in two different machines, today, using sbuild with an
up-to-date sid chroot. Full build logs here:

https://people.debian.org/~sanvila/build-logs/pycuda/

Thanks.

Bug#918956: marked as done (tmpreaper: CVE-2019-3461)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 12:53:11 +
with message-id 
and subject line Bug#918956: fixed in tmpreaper 1.6.14
has caused the Debian Bug report #918956,
regarding tmpreaper: CVE-2019-3461
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.)


-- 
918956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918956
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tmpreaper
Version: 1.6.13+nmu1
Severity: grave
Tags: security
Control: fixed -1 1.6.13+nmu1+deb9u1

Hi,

The following vulnerability was published for tmpreaper, as per DSA
4365-1.

CVE-2019-3461[0]:
Stephen Roettger discovered a race condition in tmpreaper, a program that
cleans up files in directories based on their age, which could result in
local privilege escalation.

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

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: tmpreaper
Source-Version: 1.6.14

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

Debian distribution maintenance software
pp.
Paul Slootman  (supplier of updated tmpreaper 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: Fri, 11 Jan 2019 13:27:15 +0100
Source: tmpreaper
Binary: tmpreaper
Architecture: source amd64
Version: 1.6.14
Distribution: unstable
Urgency: medium
Maintainer: Paul Slootman 
Changed-By: Paul Slootman 
Description:
 tmpreaper  - cleans up files in directories based on their age
Closes: 918956
Changes:
 tmpreaper (1.6.14) unstable; urgency=medium
 .
   * Upload to unstable to fix the race condition described in CVE-2019-3461:
 There was a race condition when tmpreaper was testing for a (bind) mount,
 which was done via rename() which could potentially lead to a file being
 placed elsewhere on the filesystem hierarchy (e.g. /etc/cron.d/) if the
 directory being cleaned up was on the same physical filesystem.
 This has been fixed by using an alternative way of looking for bind mounts
 using code from mountpoint (from the util-linux package).
 closes: #918956
Checksums-Sha1:
 0b05ef2ad749d2d4cafbcfb36206b2bf8a89a7fa 1437 tmpreaper_1.6.14.dsc
 8965085694add283c6baca6c15e237012a4ed3c5 158981 tmpreaper_1.6.14.tar.gz
 47417e78521836aa12b7604753f58135d1385a0d 12888 
tmpreaper-dbgsym_1.6.14_amd64.deb
 e3f9b10ccab29600959f81d154dc99743f764762 6011 tmpreaper_1.6.14_amd64.buildinfo
 c1c06e052e971cea855d45038bc122763b869d12 47432 tmpreaper_1.6.14_amd64.deb
Checksums-Sha256:
 595b8535fc29b9e2b62e1c01496d2868efbd6cf2450e7d9b38ca60deebe2884c 1437 
tmpreaper_1.6.14.dsc
 4acb93745ceb8b8c5941313bbba78ceb2af0c3914f1afea0e0ae1f7950d6bdae 158981 
tmpreaper_1.6.14.tar.gz
 7c8cba09a9c6f109a663860ba10dad408178eb328be2c63190daefb8eb83ba55 12888 
tmpreaper-dbgsym_1.6.14_amd64.deb
 fef0f239f75cb9b6af5ea6abb490c4e99a62b78427c80fcda339091e88b0cb05 6011 
tmpreaper_1.6.14_amd64.buildinfo
 97acf216bbe125426ceed4db1fcf65d1fdc10c732068a0bea91348c2e05e86f6 47432 
tmpreaper_1.6.14_amd64.deb
Files:
 5c66a8dd6c5280afaecfa2bfbd169dd2 1437 admin optional tmpreaper_1.6.14.dsc
 a534f2457439fb569a6f62958e653082 158981 admin optional tmpreaper_1.6.14.tar.gz
 a6110a113b7bf829f95a53db6ed71f65 12888 debug optional 
tmpreaper-dbgsym_1.6.14_amd64.deb
 4198f3976462f848ee4529c344cff83c 6011 admin optional 
tmpreaper_1.6.14_amd64.buildinfo
 890ebe5dc6295e1c8764a4d9ffa521a8 47432 admin optional 
tmpreaper_1.6.14_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyfNP08AZcbxb9VhpMveNzq0RO4sFAlw4jAgACgkQMveNzq0R
O4tUEA//eJxwfdgkVa11tEhPuAHeCCgqU+OREr2FXIebvkmbK/69ve8zN6+uB1Os
zSyou34zmm6GZABMnNs5mwiD578jNL49zej+uWT0vlU7iotJheQmGK98rEnl6i0C
vP/9K6qMfLXHM/X2q5930rstFx5/SnjrqQFnxskhotDREAuSQPQJbEcRP/krAZD+
HMBGPGfkyJixBSAaKZIjpXwW/vS3VPvoz3vbCGB+1zCK+0aPw+picZNLZ82NEV5c
sgbI+jVK+iFXX3OxDfFoevP8UK4TUegx/xLheJDuDr/AUn98l8W0l941T7TvuuLo
QKJeyK3+LmaBasfZFVwhP+8rnfGxL1EvJOzraZBrGOMoocy/pfDS95roEzQGBN/D
CtH1yiRO7+2Bzz3xB1hVyscINCWqBYewhjhhE6HgxV0pq40s3bUjlnZkeoLhC8nj

Processed: severity of 918187 is normal

[Debian Bug Tracking System]

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

> severity 918187 normal
Bug #918187 [src:fai] fai - hook error handling completely broken
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#905697: kdepimlibs: don't depend on libical

[Emilio Pozuelo Monfort]

On 08/08/2018 10:38, Emilio Pozuelo Monfort wrote:
> Source: kdepimlibs
> Version: 4:4.14.10-10
> Severity: serious
> Control: block 884128 with -1
> 
> Hi,
> 
> libical2 from src:libical is superseded by libical3 (src:libical3).
> 
> Please either port kdepimlibs to libical3 or try to disable the
> libical support, so that we can only ship src:libical3 in buster.

Could someone who knows kdepimlibs take a look at this? Can we disable libical
support in kdepimlibs for buster? This is the last blocker for the libical 2
removal.

Thanks,
Emilio

Processed: severity of 918213 is serious

[Debian Bug Tracking System]

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

> severity 918213 serious
Bug #918213 [src:python-skbio] python-skbio: autopkgtest fails with 
python-numpy (1:1.16.0~rc1-3)
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#918585: marked as done (xfce4-screensaver: Unroutable maintainer address)

[Debian Bug Tracking System]

Your message dated Fri, 11 Jan 2019 12:00:17 +
with message-id 
and subject line Bug#918585: fixed in xfce4-screensaver 0.1.3-1
has caused the Debian Bug report #918585,
regarding xfce4-screensaver: Unroutable maintainer address
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.)


-- 
918585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfce4-screensaver
Severity: serious
Justification: Policy 3.3

As seen in the FTP team role account for the message subject 'Processing of
xfce4-screensaver_0.1.3-1_amd64.changes':

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  pkg-xfce-de...@lists.alioth.debian.org
host alioth-lists-mx.debian.net [2001:ba8:0:2c77:0:4:0:1]
SMTP error from remote mail server after RCPT TO::
550 Unrouteable address

Scott K
--- End Message ---
--- Begin Message ---
Source: xfce4-screensaver
Source-Version: 0.1.3-1

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

Debian distribution maintenance software
pp.
Jonathan Carter  (supplier of updated xfce4-screensaver 
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, 07 Jan 2019 15:36:20 +0200
Source: xfce4-screensaver
Binary: xfce4-screensaver
Architecture: source amd64
Version: 0.1.3-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Jonathan Carter 
Description:
 xfce4-screensaver - screen saver and locker that is integrated with the xfce4 
desktop
Closes: 95 918585
Changes:
 xfce4-screensaver (0.1.3-1) experimental; urgency=medium
 .
   * Initial release (Closes: #95, #918585)
Checksums-Sha1:
 54c789bbc9f4248175522248ab00a154417b0cb2 2241 xfce4-screensaver_0.1.3-1.dsc
 ba8be12c54a04efb43395b4dd3bd80e396623124 607080 
xfce4-screensaver_0.1.3.orig.tar.bz2
 5acbc957a346348d4a3f960d23e11ede5d5f874c 3212 
xfce4-screensaver_0.1.3-1.debian.tar.xz
 58cb8d3c9f06e397d50035298f9dd6b089feeb58 821724 
xfce4-screensaver-dbgsym_0.1.3-1_amd64.deb
 1a21263494f1dfaf04cb90e6f7c478296ad0accc 15479 
xfce4-screensaver_0.1.3-1_amd64.buildinfo
 50864b7227d6b2039c997a581fbc789c2451b18b 261032 
xfce4-screensaver_0.1.3-1_amd64.deb
Checksums-Sha256:
 4fea42104d54a449f0b9159293bc8ed4d8a410568eca8a8f1411dcca30f63c36 2241 
xfce4-screensaver_0.1.3-1.dsc
 1277f2501911c5eb4785120c8eb4c7b4cf9bea28de7c184c7186f319d05c70d7 607080 
xfce4-screensaver_0.1.3.orig.tar.bz2
 4043ee6a6855c95f82823ccfc2a47caeeae9c8f177c1d9e1058717ce99212087 3212 
xfce4-screensaver_0.1.3-1.debian.tar.xz
 60f379468bcab490c37e097d7c45a1defb732d03fda6996ad7a24439479cfbfc 821724 
xfce4-screensaver-dbgsym_0.1.3-1_amd64.deb
 175a41361ebd21de024d2328723f839a155b9d8817f4291b3d8bbdd7afa6fa85 15479 
xfce4-screensaver_0.1.3-1_amd64.buildinfo
 d64344153e780f5127472ab196a7fca2841017f2c5aefe6f5820723b3b4d6bb8 261032 
xfce4-screensaver_0.1.3-1_amd64.deb
Files:
 9e39f65a62d5e506391571b5935c9c44 2241 xfce optional 
xfce4-screensaver_0.1.3-1.dsc
 b03786067548cc6df79490380e140a9c 607080 xfce optional 
xfce4-screensaver_0.1.3.orig.tar.bz2
 51c7b299b139b38085a6d3e343d69102 3212 xfce optional 
xfce4-screensaver_0.1.3-1.debian.tar.xz
 bf1a20d175acf75c92ceddf2a2580690 821724 debug optional 
xfce4-screensaver-dbgsym_0.1.3-1_amd64.deb
 1200ae1831b7ce0fbb572c9d3bda53d3 15479 xfce optional 
xfce4-screensaver_0.1.3-1_amd64.buildinfo
 9983196c18f4e00b109901245ccbc47a 261032 xfce optional 
xfce4-screensaver_0.1.3-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAlwznzAPHGpjY0BkZWJp
YW4ub3JnAAoJELAdGnKsjcmhFYUP/3lw/Sg+X6fOTcph7ITvFSMh20z9APgY2Jgy
SnCGifZhITKOfEZByt6JTrFYFbz8tUSb0HlBIul9d7EGGwbROCSYa8FuIrPG4Uw3
2hjWU5a7/gYUrWgTJBv0lhmXYqAugBh6s2aUW0/4SMnT7ErIgP4MAwiZSAUs0Ddl
UNbC5EZwffndxM6jYqZW+F0GN7EugfGmgwOchf4lAD/j8/Y+jrZDvsWl+Gs7NKDg
Q2fxqamIFzZBFcQUOqjzq/OUzK9ZySljxgVxciH0eEHlz/m9OfAMDX4Zt2jB16Zw

Bug#915328: coinor-symphony: diff for NMU version 5.6.16+repack1-1.1

[Adrian Bunk]

Control: tags 915328 + patch
Control: tags 915328 + pending

Dear maintainer,

I've prepared an NMU for coinor-symphony (versioned as 5.6.16+repack1-1.1) and
uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru coinor-symphony-5.6.16+repack1/debian/changelog coinor-symphony-5.6.16+repack1/debian/changelog
--- coinor-symphony-5.6.16+repack1/debian/changelog	2017-08-21 22:41:01.0 +0300
+++ coinor-symphony-5.6.16+repack1/debian/changelog	2019-01-11 13:53:51.0 +0200
@@ -1,3 +1,10 @@
+coinor-symphony (5.6.16+repack1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with latest TeX Live. (Closes: #915328)
+
+ -- Adrian Bunk   Fri, 11 Jan 2019 13:53:51 +0200
+
 coinor-symphony (5.6.16+repack1-1) unstable; urgency=medium
 
   * [b1e7a6e] Set Standards-Version: 4.0.0
diff -Nru coinor-symphony-5.6.16+repack1/debian/patches/series coinor-symphony-5.6.16+repack1/debian/patches/series
--- coinor-symphony-5.6.16+repack1/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ coinor-symphony-5.6.16+repack1/debian/patches/series	2019-01-11 13:53:51.0 +0200
@@ -0,0 +1 @@
+tex-ftbfs.patch
diff -Nru coinor-symphony-5.6.16+repack1/debian/patches/tex-ftbfs.patch coinor-symphony-5.6.16+repack1/debian/patches/tex-ftbfs.patch
--- coinor-symphony-5.6.16+repack1/debian/patches/tex-ftbfs.patch	1970-01-01 02:00:00.0 +0200
+++ coinor-symphony-5.6.16+repack1/debian/patches/tex-ftbfs.patch	2019-01-11 13:53:51.0 +0200
@@ -0,0 +1,20 @@
+Description: Fix FTBFS with latest TeX Live
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/915328
+
+--- coinor-symphony-5.6.16+repack1.orig/Doc/man.tex
 coinor-symphony-5.6.16+repack1/Doc/man.tex
+@@ -76,12 +76,12 @@
+ \usepackage{amsmath}
+ \usepackage{amssymb}
+ \usepackage{fullpage}
++\usepackage[usenames]{color}
+ \usepackage{easyeqn}
+ \usepackage{fancyvrb}
+ \usepackage{listings}
+ \usepackage{url}
+ \usepackage{splitidx}
+-\usepackage[usenames]{color}
+ 
+ \makeindex
+ \newindex[Index of C API Functions]{f}

Processed: coinor-symphony: diff for NMU version 5.6.16+repack1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 915328 + patch
Bug #915328 [src:coinor-symphony] coinor-symphony FTBFSwith latest TeX Live: 
LaTeX Error: Option clash for package color.
Added tag(s) patch.
> tags 915328 + pending
Bug #915328 [src:coinor-symphony] coinor-symphony FTBFSwith latest TeX Live: 
LaTeX Error: Option clash for package color.
Added tag(s) pending.

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

Processed: toulbar2: diff for NMU version 1.0.0+dfsg3-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 916715 + patch
Bug #916715 [src:toulbar2] toulbar2: missing build dependency on zlib1g-dev
Added tag(s) patch.
> tags 916715 + pending
Bug #916715 [src:toulbar2] toulbar2: missing build dependency on zlib1g-dev
Added tag(s) pending.

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

Bug#916715: toulbar2: diff for NMU version 1.0.0+dfsg3-1.1

[Adrian Bunk]

Control: tags 916715 + patch
Control: tags 916715 + pending

Dear maintainer,

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

cu
Adrian

-- 

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

diff -Nru toulbar2-1.0.0+dfsg3/debian/changelog toulbar2-1.0.0+dfsg3/debian/changelog
--- toulbar2-1.0.0+dfsg3/debian/changelog	2018-08-13 06:22:14.0 +0300
+++ toulbar2-1.0.0+dfsg3/debian/changelog	2019-01-11 13:47:51.0 +0200
@@ -1,3 +1,10 @@
+toulbar2 (1.0.0+dfsg3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add the missing build dependency on zlib1g-dev. (Closes: #916715)
+
+ -- Adrian Bunk   Fri, 11 Jan 2019 13:47:51 +0200
+
 toulbar2 (1.0.0+dfsg3-1) unstable; urgency=medium
 
   [ Thomas Schiex ]
diff -Nru toulbar2-1.0.0+dfsg3/debian/control toulbar2-1.0.0+dfsg3/debian/control
--- toulbar2-1.0.0+dfsg3/debian/control	2018-08-13 06:18:41.0 +0300
+++ toulbar2-1.0.0+dfsg3/debian/control	2019-01-11 13:47:51.0 +0200
@@ -8,7 +8,7 @@
libgmp-dev, graphviz,
libboost-graph-dev,
libboost-iostreams-dev,
-   libjemalloc-dev
+   libjemalloc-dev, zlib1g-dev
 Standards-Version: 4.2.0
 Vcs-Browser: https://salsa.debian.org/science-team/toulbar2
 Vcs-Git: https://salsa.debian.org/science-team/toulbar2.git
@@ -33,4 +33,4 @@
  Satisfaction Problems and Bayesian Nets.
  .
  This package contains the API reference and user documentation, descriptions
- of the various file formats that toulbar2 can read as well as examples.
\ No newline at end of file
+ of the various file formats that toulbar2 can read as well as examples.