Bug#917072: mmm-mode: fails to byte-compile with emacs-26

[David Bremner]

Source: mmm-mode
Version: 0.5.7-2
Severity: serious
Justification: fails to install

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256


I'm not quite sure whether this is a bug in emacs 26 or in mmm-mode,
but in any case it seems the file mmm-sample.el doesn't really need to
be byte compiled.

Attached is an nmudiff that I plan to upload to DELAYED/5

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAlwd6OIACgkQ8gKXHaSn
niyJmQv/fnUdj6larMpf7Af/5qVgwAeZyOzIdlDoSbjZ9NA6n99LYagXPUKAPyUD
ohbKFueDSU5OwAeLN6h07F47vKBcDe7sVfTOX0ntEPY8Eh5u5EXsRuEpBKnBqhwg
NAgwlwKHpVUdzpT8XUKcZEhEeisyqbP3ZdtYNvrgz2DoLFBLcJdgCJcVopl1/CJD
PTFOEdW5JaATGcPeoSf8Hdzj74SK3NiFPoaeryNkV4SRvCyNqRMPJDD8/tmZTE26
8f7YbWMVcmciZnjwx2HRsYxIjpL5nczkTtDM9bYucq+zCah/k5cx760fGw0XdAtf
caDlGrDmJbyIxqtrff90tU0KnmKNUI39/WzmtqDrWCjxKYF0bA78AlZCDgT3ITpf
j0iXs02ESIq4YPB9v3dfY0oTuJdEUD0laubeY9wNMgHiB42PZzpNi/K0I0nIhe7A
X02Bk9vFqb61d1HqQcJLQZe+xiHPvi0lNd35rRWueWqKrRFDBt9eIslvFeI5nrsF
oD7IQw8C
=kLlK
-END PGP SIGNATURE-
diff --git a/debian/changelog b/debian/changelog
index f44b0bb..76a7b5d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+mmm-mode (0.5.7-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Disable byte compilation of mmm-sample.el as this hangs with emacs-26
+
+ -- David Bremner   Sat, 22 Dec 2018 16:27:49 +0900
+
 mmm-mode (0.5.7-2) unstable; urgency=high
 
   * fix function and file conflicts between emacs and xemacs
diff --git a/mmm-sample.el b/mmm-sample.el
index 5ee4419..58cebd4 100644
--- a/mmm-sample.el
+++ b/mmm-sample.el
@@ -1,4 +1,4 @@
-;;; mmm-sample.el --- Sample MMM submode classes
+;;; mmm-sample.el --- Sample MMM submode classes -*- no-byte-compile: t; -*-
 
 ;; Copyright (C) 2000-2004, 2012-2015, 2018  Free Software Foundation, Inc.
 

Bug#914666: marked as done (dlt-daemon: FTBFS with glibc 2.28 (upstream fix attached))

[Debian Bug Tracking System]

Your message dated Sat, 22 Dec 2018 07:19:16 +
with message-id 
and subject line Bug#914666: fixed in dlt-daemon 2.17.0-3
has caused the Debian Bug report #914666,
regarding dlt-daemon: FTBFS with glibc 2.28 (upstream fix attached)
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.)


-- 
914666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dlt-daemon
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch
Version: 2.17.0-2
Severity: important
Tags: patch

thanks for considering it :)

G.
>From 0be9c2726c45485cb0e00cec57c0bd1c167eb9c5 Mon Sep 17 00:00:00 2001
From: Oleksandr Kravchuk 
Date: Sun, 26 Aug 2018 01:48:48 +0200
Subject: [PATCH] Fix compilation with glibc 2.28

Package compilation fails with GLIBC 2.28:

stat.h:56:8: error: redefinition of 'struct statx_timestamp'
stat.h:99:8: error: redefinition of 'struct statx'

Signed-off-by: Oleksandr Kravchuk 
---
 src/daemon/dlt-daemon.c| 2 +-
 src/daemon/dlt_daemon_client.c | 2 +-
 src/daemon/dlt_daemon_socket.c | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/daemon/dlt-daemon.c b/src/daemon/dlt-daemon.c
index 0232cb1..5695a4b 100644
--- a/src/daemon/dlt-daemon.c
+++ b/src/daemon/dlt-daemon.c
@@ -47,7 +47,7 @@
 #endif
 #include 
 #include 
-#ifdef linux
+#ifdef defined(linux) && defined(__NR_statx)
 #include 
 #endif
 
diff --git a/src/daemon/dlt_daemon_client.c b/src/daemon/dlt_daemon_client.c
index 7c6e1bd..cb59239 100644
--- a/src/daemon/dlt_daemon_client.c
+++ b/src/daemon/dlt_daemon_client.c
@@ -46,7 +46,7 @@
 #endif
 #include 
 #include 
-#ifdef linux
+#ifdef defined(linux) && defined(__NR_statx)
 #include 
 #endif
 
diff --git a/src/daemon/dlt_daemon_socket.c b/src/daemon/dlt_daemon_socket.c
index 961556c..4ae1d86 100644
--- a/src/daemon/dlt_daemon_socket.c
+++ b/src/daemon/dlt_daemon_socket.c
@@ -49,7 +49,7 @@
 #endif
 #include 
 #include 
-#ifdef linux
+#ifdef defined(linux) && defined(__NR_statx)
 #include 
 #endif
 
--- End Message ---
--- Begin Message ---
Source: dlt-daemon
Source-Version: 2.17.0-3

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

Debian distribution maintenance software
pp.
Aigars Mahinovs  (supplier of updated dlt-daemon 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: Sat, 22 Dec 2018 07:45:18 +0200
Source: dlt-daemon
Binary: libdlt-dev libdlt2 dlt-daemon dlt-tools libdlt-examples
Architecture: source
Version: 2.17.0-3
Distribution: unstable
Urgency: medium
Maintainer: Aigars Mahinovs 
Changed-By: Aigars Mahinovs 
Description:
 dlt-daemon - Diagnostic Log and Trace logging daemon
 dlt-tools  - Diagnostic Log and Trace (DLT) (documentation)
 libdlt-dev - Diagnostic Log and Trace (DLT) library (development)
 libdlt-examples - Diagnostic Log and Trace (DLT) (documentation)
 libdlt2- Diagnostic Log and Trace (DLT) library
Closes: 914666
Changes:
 dlt-daemon (2.17.0-3) unstable; urgency=medium
 .
   * Fix building with glibc 2.28 (Closes: #914666)
Checksums-Sha1:
 71720eff027e08b600c6effd29b8125a765a0b12 2090 dlt-daemon_2.17.0-3.dsc
 8318ff6878f391313b29a920151a31fbfeacf152 4756 dlt-daemon_2.17.0-3.debian.tar.xz
 76ba0bfe86c0d4ee5ece0ddd0caf02d6bd4b0f12 10852 
dlt-daemon_2.17.0-3_amd64.buildinfo
Checksums-Sha256:
 29af1c4279d6aa36291760f98438809e4e69359c6afb94ff3c09ed10003f935b 2090 
dlt-daemon_2.17.0-3.dsc
 7b82ec8b852d2321950b673154898377ce40609a161a99979122c7427230 4756 
dlt-daemon_2.17.0-3.debian.tar.xz
 83d0e8bc4e6536964467faeca53c9e21b07001e2a859d529f5b88791c11a95f0 10852 
dlt-daemon_2.17.0-3_amd64.buildinfo
Files:
 e957c9b09a5f27f637917f06976d3bc8 2090 libs optional dlt-daemon_2.17.0-3.dsc
 b1f986b83b715a01264f0ecef85bd6ba 4756 libs optional 
dlt-daemon_2.17.0-3.debian.tar.xz
 6a10f7689765497bc1eba9a27f31ebd4 10852 libs optional 
dlt-daemon_2.17.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEFmwrqIlWRDzdY39G+mQ7ph0ievsFAlwd4FUUHGFpZ2FyaXVz

Bug#917018: wget: Unusable - permanent segmentation fault

[rwpenney]

Hello Bernhard,

Thanks for investigating this.

I agree that there may not be a problem with the version of wget in 
"buster", but the version currently in "stable" (i.e. 1.18-5+deb9u) is 
definitely not usable on two different stretch-amd64 systems I've tried. 
I believe a fix is needed specifically for the package within stretch.


The output from your gdb recipe is as follows:


Reading symbols from wget...(no debugging symbols found)...done.
Starting program: /usr/bin/wget -r -k -l inf http://www.debian.org
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
_IO_new_fclose (fp=0x0) at iofclose.c:53
53    iofclose.c: No such file or directory.
#0  _IO_new_fclose (fp=0x0) at iofclose.c:53
#1  0x555722ca in ?? ()
#2  0x5556102c in ?? ()
#3  0x769b62e1 in __libc_start_main (main=0xfb40, 
argc=6, argv=0x7fffe848, init=, fini=, 
rtld_fini=, stack_end=0x7fffe838) at 
../csu/libc-start.c:291

#4  0x5556147a in ?? ()
Detaching from program: /usr/bin/wget, process 2009


Thanks,

RW Penney

Bug#852654: marked as done (src:pbcopper: no point to releasing it without `unanimity`)

[Debian Bug Tracking System]

Your message dated Sat, 22 Dec 2018 06:50:41 +
with message-id 
and subject line Bug#852654: fixed in pbcopper 0.4.1+dfsg-2
has caused the Debian Bug report #852654,
regarding src:pbcopper: no point to releasing it without `unanimity`
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.)


-- 
852654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pbcopper
Version: 0.0.1+20161202-2
Severity: important

There is nothing actually wrong with pbcopper, but there is no sense in
releasing this package for stretch since it basically only exists to
support unanimity, which did not make the cutoff.

--
Afif Elghraoui
--- End Message ---
--- Begin Message ---
Source: pbcopper
Source-Version: 0.4.1+dfsg-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated pbcopper 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: Sat, 22 Dec 2018 07:26:24 +0100
Source: pbcopper
Binary: libpbcopper-dev
Architecture: source
Version: 0.4.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libpbcopper-dev - data structures, algorithms, and utilities for C++ 
applications -
Closes: 852654
Changes:
 pbcopper (0.4.1+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * Unanimity is now in unstable
 Closes: #852654
   * Standards-Version: 4.2.1
   * Remove trailing whitespace in debian/copyright
Checksums-Sha1:
 a252b4534c68e5639bef3482aa347735a9081469 2023 pbcopper_0.4.1+dfsg-2.dsc
 e6cceba4d779d4d00bcf3f59b34bdfc6cbac1ee5 3628 
pbcopper_0.4.1+dfsg-2.debian.tar.xz
Checksums-Sha256:
 4a31a0df446492bae45988c72d2d409456ebd25fb17b9ff893702671cedb5c04 2023 
pbcopper_0.4.1+dfsg-2.dsc
 535a9bb35ca0f82fe20fef98d797c8349348bc228e2c766ba01abdf2f657f24e 3628 
pbcopper_0.4.1+dfsg-2.debian.tar.xz
Files:
 775dc6f476df53cd4bc16f431ff6fae4 2023 libs optional pbcopper_0.4.1+dfsg-2.dsc
 d2f6398de93a03d177c4f5360f729d4f 3628 libs optional 
pbcopper_0.4.1+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlwd3A0RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGeMw//Rmq586cFkgzmtfLQZeQ/m7RGq8AK9jZr
BR4u6eJ6gNX7x86Aa+x8r9+G9nlSx+d4SyUcacHyp7jrk4ykBaA5vaI35cOMacC1
028WKiJ+5gQc8LwNwlJZ+fLE2fyNBq/dzSPMnrvp4jyF/vLCxQVURoCxZHL0zjC1
ZBk1vcMxttZsJ3i+NXlkTxLIMZKBCwI58p81sXI8B5wyhYP2zQjDrO8KkMuy
m41IASSclRIwpUx2Kzryfi7pg2eXWoDjlnEJo8yKJOTVQ5tzAQd6oc4YsrcSf4rn
K4JsSp12mznpvlfezpAGX01zbCQU3XmFa4mNYlnMX2vCe7IAjvpKZ/bzLwcg3dfB
ZzsR4rdVXNljpvtg1lq/hfgxx/ZTiqdB5SKs+YDZOKb/JShNx6imu8C0MmzMhGNf
+dLPT77dlI33F4WewmaK2ZVIIfCR9qpcXq8RNkXcZfuKugWzlnDRoSFLMYu5al7e
gfQCmrzJz7TNfxmV2MwZvwM/6Rq7VkuMn2vnigI62yRsNlNhsvUtMHaYi+s4j1kI
fQdh/n4sn3pvl7kJF0QS6oDo4cc48fbyuaa2TI56XGdpcKJxQeUW4hhf9ZdORt3A
bzf9hb5kqKm9zvLz7U2COaMzb7gMvXBqXtdphA8a8uSL6UOWuEY0BtQ7M+/UX4Jo
+nGYTYMzsmQ=
=6exn
-END PGP SIGNATURE End Message ---

Bug#917071: elpa-persp-projectile: byte compilation fails: make-variable-frame-local

[David Bremner]

Package: elpa-persp-projectile
Version: 1:0.2.0-2
Severity: serious
Justification: fails to install

install/persp-projectile-0.2.0: Handling install of emacsen flavor emacs
install/persp-projectile-0.2.0: byte-compiling for emacs

In toplevel form:
persp-projectile.el:47:1:Error: Symbol’s function definition is void: 
make-variable-frame-local
ERROR: install script from elpa-persp-projectile package failed
dpkg: error processing package elpa-persp-projectile (--configure):
 installed elpa-persp-projectile package post-installation script subprocess 
returned error exit status 1
Errors were encountered while processing:
 elpa-persp-projectile


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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages elpa-persp-projectile depends on:
ii  elpa-perspective   1.12+git20160216.add7942-2
ii  elpa-projectile1.0.0-1
ii  emacs  1:26.1+1-2
ii  emacs-gtk [emacs]  1:26.1+1-2
ii  emacsen-common 3.0.4

Versions of packages elpa-persp-projectile recommends:
ii  emacs  1:26.1+1-2
ii  emacs-gtk [emacs]  1:26.1+1-2

elpa-persp-projectile suggests no packages.

-- no debconf information

Bug#917070: elpa-smex: byte-compilation fails

[David Bremner]

Package: elpa-smex
Version: 3.0-2
Severity: serious
Justification: fails to install


  install/smex-3.0: byte-compiling for emacs

In smex-already-running:
smex.el:91:11:Warning: defsubst ‘smex-already-running’ was used before it was
defined

In smex-update-and-rerun:
smex.el:94:11:Warning: defsubst ‘smex-update-and-rerun’ was used before it was
defined

In smex-read-and-run:
smex.el:107:10:Warning: ‘execute-extended-command’ is for interactive use
only; use ‘command-execute’ instead.

In smex-initialize-ido:
smex.el:228:4:Warning: ‘ido-init-completion-maps’ is an obsolete function (as
of 25.1); it does nothing.

In smex-load-save-file:
smex.el:245:13:Error: missing value for ‘smex-history’ at end of setq
smex.el:245:30:Error: missing value for ‘smex-data’ at end of setq

In smex-save-file-not-empty-p:
smex.el:247:11:Warning: defsubst ‘smex-save-file-not-empty-p’ was used before
it was defined
ERROR: install script from elpa-smex package failed
dpkg: error processing package elpa-smex (--configure):
 installed elpa-smex package post-installation script subprocess returned error 
exit status 1
Errors were encountered while processing:
 elpa-smex



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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages elpa-smex depends on:
ii  emacs  1:26.1+1-2
ii  emacs-gtk [emacs]  1:26.1+1-2
ii  emacsen-common 3.0.4

Versions of packages elpa-smex recommends:
ii  emacs  1:26.1+1-2
ii  emacs-gtk [emacs]  1:26.1+1-2

elpa-smex suggests no packages.

-- no debconf information

Bug#917068: timbl (build-)depends on cruft packages.

[peter green]

package: timbl
version: 6.4.8-1
severity: serious

timbl and libtimbl4 depend on libticcutils2v5 and the timbl source package 
depends on libtimbl4-dev. These packages are no longer build by the ticcutils 
source package.

I notice there is a new version in new that looks like it probablly fixes this, 
but that looks strange too, the changelog claims it makes a soname bumb from 
3->4 but the soname in sid appears to already be 4.

Processed: block 912046 with 913883

[Debian Bug Tracking System]

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

> block 912046 with 913883
Bug #912046 [ebtables] ebtables provides the same executables as iptables 
packages without using alternatives
912046 was not blocked by any bugs.
912046 was not blocking any bugs.
Added blocking bug(s) of 912046: 913883
> thanks
Stopping processing here.

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

Processed: block 916106 with 913883

[Debian Bug Tracking System]

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

> block 916106 with 913883
Bug #916106 [arptables] arptables provides the same executables as iptables 
packages without using alternatives
916106 was not blocked by any bugs.
916106 was not blocking any bugs.
Added blocking bug(s) of 916106: 913883
> thanks
Stopping processing here.

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

Bug#917064: praat FTBFS on big endian: 2 tests segfault

[Adrian Bunk]

Source: praat
Version: 6.0.43-1
Severity: serious
Tags: ftbfs

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

...
= test_SpeechSynthesizer_alignment.praat
test_SpeechSynthesizer_alignment.praat
Segmentation fault
...
= test_alignment.praat
test_alignment.praat
Segmentation fault
...
113 tests passed, 111 ok
Failed test(s):

test_SpeechSynthesizer_alignment.praat
test_alignment.praat
make[1]: *** [debian/rules:86: override_dh_auto_test] Error 1

Bug#917052: [Pkg-emacsen-addons] Bug#917052: elpa-xml-rpc: Hangs infinitely when compiling for emacs 1:26.1+1-2

[David Bremner]

Control: tag -1 unreproducible
Control: severity -1 important

Axel Beckert  writes:

> Package: elpa-xml-rpc
> Version: 1.6.12-2
> Severity: serious
>
> Hi,
>
> when upgrading emacs from 1:25.2+1-11 to 1:26.1+1-2, it hangs
> infinitely at "install/xml-rpc-1.6.12: byte-compiling for emacs".
>
>
> P.S.: This looks very similar to https://bugs.debian.org/917050
> against elpa-markdown-mode.

Yup, I also can't replicate this one.  Here's  what I did in both cases,
with the relevant elpa package installed:

% apt install emacs-common=1:25.2+1-11 emacs-bin-common=1:25.2+1-11 
emacs-gtk=1:25.2+1-11 emacs-el=1:25.2+1-11
% apt install -t unstable emacs

Byte compilation finishes smoothly.

For now I'm lowering the severity to help triage the emacs26 related
bugs.

Processed: Re: [Pkg-emacsen-addons] Bug#917052: elpa-xml-rpc: Hangs infinitely when compiling for emacs 1:26.1+1-2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 unreproducible
Bug #917052 [elpa-xml-rpc] elpa-xml-rpc: Hangs infinitely when compiling for 
emacs 1:26.1+1-2
Added tag(s) unreproducible.
> severity -1 important
Bug #917052 [elpa-xml-rpc] elpa-xml-rpc: Hangs infinitely when compiling for 
emacs 1:26.1+1-2
Severity set to 'important' from 'serious'

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

Processed (with 1 error): Re: [Pkg-emacsen-addons] Bug#917050: Hangs infinitely when compiling for emacs 1:26.1+1-2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 unpreproducible
Unknown tag/s: unpreproducible.
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.

> severity -1 important
Bug #917050 [elpa-markdown-mode] elpa-markdown-mode: Hangs infinitely when 
compiling for emacs 1:26.1+1-2
Severity set to 'important' from 'serious'

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

Bug#917050: [Pkg-emacsen-addons] Bug#917050: Hangs infinitely when compiling for emacs 1:26.1+1-2

[David Bremner]

Control: tag -1 unpreproducible
Control: severity -1 important

Axel Beckert  writes:

> when upgrading emacs from 1:25.2+1-11 to 1:26.1+1-2, it hangs
> infinitely at "install/markdown-mode-2.3snapshot154: byte-compiling
> for emacs".
>

I can't duplicate this problem here (in a buster system). Can you tell
us anything more about the configuration where you see it?

d

Bug#917063: golang-gopkg-cheggaaa-pb.v2 FTBFS: FAIL: TestElementBar

[Adrian Bunk]

Source: golang-gopkg-cheggaaa-pb.v2
Version: 2.0.6-2
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-gopkg-cheggaaa-pb.v2.html

...
=== RUN   TestElementBar
--- FAIL: TestElementBar (0.43s)
element_test.go:34: Unexpected result: '⚑⚒ ⚟⚐'; want: '⚑⚒⚒⚒⚟⚐'
...

Bug#917062: python-bumps: binary-any FTBFS

[Adrian Bunk]

Source: python-bumps
Version: 0.7.11-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=python-bumps=sid

...
   debian/rules override_dh_installinfo
make[1]: Entering directory '/<>'
cd build/texinfo; \
for p in *.png; do mv $p bumps-$p; done; \
sed "s/@image{/@image{bumps-/" -i bumps.texi; \
makeinfo bumps.texi
/bin/sh: 1: cd: can't cd to build/texinfo
mv: cannot stat '*.png': No such file or directory
sed: can't read bumps.texi: No such file or directory
could not open bumps.texi: No such file or directory
make[1]: *** [debian/rules:57: override_dh_installinfo] Error 1


This can be reproduced with
  dpkg-buildpackage -B

Processed: retitle 917057 to libpolyclipping-dev: pkg-config file contains bogus includedir

[Debian Bug Tracking System]

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

> retitle 917057 libpolyclipping-dev: pkg-config file contains bogus includedir
Bug #917057 [libpolyclipping-dev] libpolyclipping-dev: pjg-config file contains 
bogus includedir
Changed Bug title to 'libpolyclipping-dev: pkg-config file contains bogus 
includedir' from 'libpolyclipping-dev: pjg-config file contains bogus 
includedir'.
> thanks
Stopping processing here.

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

Bug#917058: ocaml-migrate-parsetree FTBFS:

[Adrian Bunk]

Source: ocaml-migrate-parsetree
Version: 1.0.10-2
Severity: serious
Tags: ftbfs

Some recent change in unstable makes ocaml-migrate-parsetree FTBFS:

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

...
make -j1 install DESTDIR=/build/1st/ocaml-migrate-parsetree-1.0.10/debian/tmp 
AM_UPDATE_INFO_DIR=no 
"INSTALL_ARGS=--destdir=/build/1st/ocaml-migrate-parsetree-1.0.10/debian/tmp 
--libdir=/build/1st/ocaml-migrate-parsetree-1.0.10/debian/tmp/usr/lib/ocaml 
--verbose"
make[2]: Entering directory '/build/1st/ocaml-migrate-parsetree-1.0.10'
jbuilder install --destdir=/build/1st/ocaml-migrate-parsetree-1.0.10/debian/tmp 
--libdir=/build/1st/ocaml-migrate-parsetree-1.0.10/debian/tmp/usr/lib/ocaml 
--verbose
# Workspace root: /build/1st/ocaml-migrate-parsetree-1.0.10
Running[0]: /usr/bin/nproc > /tmp/dune67e2fd.output 2> /dev/null
# # Workspace root: /build/1st/ocaml-migrate-parsetree-1.0.10
# Auto-detected concurrency: 16
Running[1]: /usr/bin/ocamlc.opt -config > /tmp/dune707986.output
# # # Workspace root: /build/1st/ocaml-migrate-parsetree-1.0.10
# # Auto-detected concurrency: 16
# Dune context:
#  ((name default)
#   (kind default)
#   (profile release)
#   (merlin true)
#   (for_host ())
#   (build_dir (In_build_dir default))
#   (toplevel_path ())
#   (ocaml_bin (External /usr/bin))
#   (ocaml (External /usr/bin/ocaml))
#   (ocamlc (External /usr/bin/ocamlc.opt))
#   (ocamlopt ((External /usr/bin/ocamlopt.opt)))
#   (ocamldep (External /usr/bin/ocamldep.opt))
#   (ocamlmklib (External /usr/bin/ocamlmklib.opt))
#   (env
#((CAML_LD_LIBRARY_PATH
#  
/build/1st/ocaml-migrate-parsetree-1.0.10/_build/install/default/lib/stublibs)
# (DUNE_CONFIGURATOR /usr/bin/ocamlc.opt)
# (INSIDE_DUNE 1)
# (MANPATH
#  /build/1st/ocaml-migrate-parsetree-1.0.10/_build/install/default/bin)
# (OCAMLFIND_IGNORE_DUPS_IN
#  /build/1st/ocaml-migrate-parsetree-1.0.10/_build/install/default/lib)
# (OCAMLPATH
#  /build/1st/ocaml-migrate-parsetree-1.0.10/_build/install/default/lib)))
#   (findlib_path ((External /usr/lib/ocaml)))
#   (arch_sixtyfour true)
#   (natdynlink_supported true)
#   (supports_shared_libraries true)
#   (opam_vars ())
#   (ocaml_config
#((version 4.05.0)
# (standard_library_default /usr/lib/ocaml)
# (standard_library /usr/lib/ocaml)
# (standard_runtime /usr/bin/ocamlrun)
# (ccomp_type cc)
# (c_compiler gcc)
# (ocamlc_cflags
#  (-O2
#   -fno-strict-aliasing
#   -fwrapv
#   -D_FILE_OFFSET_BITS=64
#   -D_REENTRANT
#   -fPIC))
# (ocamlopt_cflags
#  (-O2 -fno-strict-aliasing -fwrapv -D_FILE_OFFSET_BITS=64 -D_REENTRANT))
# (bytecomp_c_compiler
#  (gcc
#   -O2
#   -fno-strict-aliasing
#   -fwrapv
#   -D_FILE_OFFSET_BITS=64
#   -D_REENTRANT
#   -fPIC))
# (bytecomp_c_libraries (-lm -ldl -lcurses -lpthread))
# (native_c_compiler
#  (gcc
#   -O2
#   -fno-strict-aliasing
#   -fwrapv
#   -D_FILE_OFFSET_BITS=64
#   -D_REENTRANT))
# (native_c_libraries (-lm -ldl))
# (cc_profile (-pg))
# (architecture amd64)
# (model default)
# (int_size 63)
# (word_size 64)
# (system linux)
# (asm (as))
# (asm_cfi_supported true)
# (with_frame_pointers false)
# (ext_exe )
# (ext_obj .o)
# (ext_asm .s)
# (ext_lib .a)
# (ext_dll .so)
# (os_type Unix)
# (default_executable_name a.out)
# (systhread_supported true)
# (host x86_64-pc-linux-gnu)
# (target x86_64-pc-linux-gnu)
# (profiling true)
# (flambda false)
# (spacetime false)
# (safe_string false)
# (exec_magic_number Caml1999X011)
# (cmi_magic_number Caml1999I021)
# (cmo_magic_number Caml1999O011)
# (cma_magic_number Caml1999A012)
# (cmx_magic_number Caml1999Y015)
# (cmxa_magic_number Caml1999Z014)
# (ast_impl_magic_number Caml1999M020)
# (ast_intf_magic_number Caml1999N018)
# (cmxs_magic_number Caml2007D002)
# (cmt_magic_number Caml2012T009)
# (natdynlink_supported true)
# (supports_shared_libraries true)
# (windows_unicode false)))
#   (which
#((ocaml ((External /usr/bin/ocaml)))
# (ocamlc ((External /usr/bin/ocamlc.opt))
Running[2]: /usr/bin/opam config var prefix > /tmp/dune55264d.output
Output[2]:
[WARNING] Running as root is not recommended
[ERROR] Opam has not been initialised, please run `opam init'
Warning: Command [2] exited with code 50, but I'm ignoring it, hope that's OK.
...
   dh_install
dh_install: Cannot find (any matches for) 
"/usr/lib/ocaml/ocaml-migrate-parsetree/META" (tried in ., debian/tmp)

dh_install: libmigrate-parsetree-ocaml missing files: 
/usr/lib/ocaml/ocaml-migrate-parsetree/META
dh_install: Cannot find (any matches for) 
"/usr/lib/ocaml/ocaml-migrate-parsetree/opam" (tried in ., debian/tmp)

dh_install: 

Bug#916961: octave-symbolic FTBFS: test failures

[Mike Miller]

On Thu, Dec 20, 2018 at 22:29:16 +0200, Adrian Bunk wrote:
> Some recent change in unstable makes octave-symbolic FTBFS:
[…]
> * test
>  % performance: want roughly O(1) not O(n)
>  A = linspace(sym(0), sym(10), 3);  % do one first, avoid caching
>  tic; A = linspace(sym(0), sym(10), 3);   t1 = toc();
>  tic; A = linspace(sym(0), sym(10), 100); t2 = toc();
>  if (t2 >= 10*t1)
>assert (false);
>  end
> ! test failed
> assert (false) failed

This is comparing timing, I guess the results could be fragile and
depend so much on what else the system may be doing. May pass most of
the time but fail randomly. Turn into xtest?

> * test
>  % maple, matrix inputs
>  A = [5.61467232547723663908 20.6144884613920190965];
>  B = pochhammer ([0.9 0.8], [3.1 4.2]);
>  assert (A, B, -eps);
> ! test failed
> ASSERT errors for:  assert (A,B,-eps)
> 
>   Location  |  Observed  |  Expected  |  Reason
> (2)20.6145  20.6145  Rel err 5.1702e-16 exceeds tol 
> 2.2204e-16 by 3e-16

Confirmed in a virtualenv that this is due to the recently released
mpmath version 1.1.0.

Filed upstream issue: https://github.com/cbm755/octsympy/issues/918

Bumping the tolerance seems appropriate.

-- 
mike


signature.asc
Description: PGP signature

Bug#912048: marked as done (obs-build: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Sat, 22 Dec 2018 00:55:22 +
with message-id 
and subject line Bug#912048: fixed in obs-build 20180831-2
has caused the Debian Bug report #912048,
regarding obs-build: FTBFS: Test failures
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.)


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

>From my pbuilder build log:

...
   dh_auto_test
   make -j1 test
make[1]: Entering directory '/build/obs-build-20180831'
PERL5LIB=. prove -v
Can't locate Date/Parse.pm in @INC (you may need to install the
Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2
/usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
/usr/share/perl/5.26 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
BEGIN failed--compilation aborted at ./changelog2spec line 31.

#   Failed test 'changelog2spec --selftest rpm python-rpm.changes rpm.changes'
#   at t/changelog2spec.t line 10.
#  got: ''
# expected: 'rpm.changes'
Can't locate Date/Parse.pm in @INC (you may need to install the
Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2
/usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
/usr/share/perl/5.26 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
BEGIN failed--compilation aborted at ./changelog2spec line 31.

#   Failed test 'changelog2spec --selftest python-rpm
python-rpm.changes rpm.changes'
#   at t/changelog2spec.t line 10.
#  got: ''
# expected: 'python-rpm.changes'
Can't locate Date/Parse.pm in @INC (you may need to install the
Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2
/usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
/usr/share/perl/5.26 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
BEGIN failed--compilation aborted at ./changelog2spec line 31.

#   Failed test 'changelog2spec --selftest antlr antlr.changes
antlr-bootstrap.changes'
#   at t/changelog2spec.t line 10.
#  got: ''
# expected: 'antlr.changes'
Can't locate Date/Parse.pm in @INC (you may need to install the
Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2
/usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
/usr/share/perl/5.26 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
BEGIN failed--compilation aborted at ./changelog2spec line 31.

#   Failed test 'changelog2spec --selftest antlr anyunrelated.changes'
#   at t/changelog2spec.t line 10.
#  got: ''
# expected: 'anyunrelated.changes'
Can't locate Date/Parse.pm in @INC (you may need to install the
Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2
/usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
/usr/share/perl/5.26 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
BEGIN failed--compilation aborted at ./changelog2spec line 31.

#   Failed test 'changelog2spec --selftest antlr-bootstrap
antlr.changes antlr-bootstrap.changes'
#   at t/changelog2spec.t line 10.
#  got: ''
# expected: 'antlr-bootstrap.changes'
Can't locate Date/Parse.pm in @INC (you may need to install the
Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2
/usr/local/share/perl/5.26.2 /usr/lib/x86_64-linux-gnu
/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26
/usr/share/perl/5.26 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base .) at ./changelog2spec line 31.
BEGIN failed--compilation aborted at ./changelog2spec line 31.

#   Failed test 'changelog2spec --selftest antlr-bootstrap antlr.changes'
#   at t/changelog2spec.t line 10.
#  got: ''
# expected: 'antlr.changes'
Can't locate Date/Parse.pm in @INC (you may need to install the
Date::Parse module) (@INC contains: /usr/lib/build . /etc/perl

Bug#917057: libpolyclipping-dev: pjg-config file contains bogus includedir

[Adrian Bunk]

Package: libpolyclipping-dev
Version: 6.4.2-4
Severity: serious
Control: affects -1 src:cura-engine

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

...
CMake Error at 
/usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
  Could NOT find Polyclipping (missing: Polyclipping_INCLUDE_DIRS)
Call Stack (most recent call first):
  /usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:378 
(_FPHSA_FAILURE_MESSAGE)
  cmake/FindPolyclipping.cmake:60 (find_package_handle_standard_args)
  CMakeLists.txt:20 (find_package)


-- Configuring incomplete, errors occurred!


Root cause:

$  cat /usr/lib/x86_64-linux-gnu/pkgconfig/polyclipping.pc
prefix=/usr
exec_prefix=/usr
libdir=lib/x86_64-linux-gnu
sharedlibdir=lib/x86_64-linux-gnu
includedir=include
...


I would suspect the #915267 change as root cause.

Processed: libpolyclipping-dev: pjg-config file contains bogus includedir

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:cura-engine
Bug #917057 [libpolyclipping-dev] libpolyclipping-dev: pjg-config file contains 
bogus includedir
Added indication that 917057 affects src:cura-engine

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

Bug#917056: python-libarchive-c FTBFS with libarchive 3.3.3

[Adrian Bunk]

Source: python-libarchive-c
Version: 2.1-3.1
Severity: serious
Tags: ftbfs buster sid

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

...
=== FAILURES ===
_ test_check_archiveentry_using_python_testtar _

def test_check_archiveentry_using_python_testtar():
>   check_entries(join(data_dir, 'testtar.tar'))

tests/test_entry.py:63: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

test_file = '/build/1st/python-libarchive-c-2.1/tests/data/testtar.tar'
regen = False, ignore = []

def check_entries(test_file, regen=False, ignore=''):
ignore = ignore.split()
fixture_file = test_file + '.json'
if regen:
entries = list(get_entries(test_file))
with open(fixture_file, 'w', encoding='UTF-8') as ex:
json.dump(entries, ex, indent=2)
with open(fixture_file, encoding='UTF-8') as ex:
expected = json.load(ex)
actual = list(get_entries(test_file))
for e1, e2 in zip(actual, expected):
for key in ignore:
e1.pop(key)
e2.pop(key)
>   assert e1 == e2
E   AssertionError: assert {'isblk': Fal...': False, ...} == {'isblk': 
Fals...': False, ...}
E Common items:
E {u'isblk': False,
E  u'ischr': False,
E  u'isdev': False,
E  u'isdir': False,
E  u'isfifo': False,
E  u'islnk': False,
E  u'isreg': True,
E  u'issym': False,
E  u'linkpath': None,
E  u'mode': u'rw-r--r--',
E  u'mtime': 1041808783,
E  u'path': u'pax/regtype4'}
E Differing items:
E {'size': 7011} != {'size': 0}
E Full diff:
E {u'isblk': False,
E u'ischr': False,
E u'isdev': False,
E u'isdir': False,
E u'isfifo': False,
E u'islnk': False,
E u'isreg': True,
E u'issym': False,
E u'linkpath': None,
E u'mode': u'rw-r--r--',
E u'mtime': 1041808783,
E u'path': u'pax/regtype4',
E -  u'size': 7011}
E ?   - --
E +  u'size': 0}

tests/test_entry.py:96: AssertionError
-- Captured log call ---
ffi.py  82 WARNING  Pathname can't be converted from UTF-8 
to current locale.
= 1 failed, 15 passed in 0.30 seconds ==
make[1]: *** [debian/rules:9: override_dh_auto_test] Error 1

Processed: severity of 917054 is serious

[Debian Bug Tracking System]

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

> # Uninstallability is not grave but serious; the same happens on upgrade, 
> too, btw.
> severity 917054 serious
Bug #917054 [dump1090-mutability] Template parse error near `in Sekunden.', in 
stanza #18 of /var/lib/dpkg/info/dump1090-mutability.templates
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.

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

Processed: severity of 914666 is serious

[Debian Bug Tracking System]

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

> severity 914666 serious
Bug #914666 [dlt-daemon] dlt-daemon: FTBFS with glibc 2.28 (upstream fix 
attached)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#917055: blktool FTBFS with glibc 2.28

[Adrian Bunk]

Source: blktool
Version: 4-7
Severity: serious
Tags: ftbfs buster sid

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

...
blktool.c: In function 'detect_dev_class':
blktool.c:295:10: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
  switch (major(st_rdev)) {
  ^
...
gcc -Wall -g -O2 -ffile-prefix-map=/build/1st/blktool-4=. 
-fstack-protector-strong -Wformat -Werror=format-security  -Wl,-z,relro -o 
blktool  blktool.o ata.o scsi.o util.o -lglib-2.0 
/usr/bin/ld: blktool.o: in function `detect_dev_class':
./blktool.c:295: undefined reference to `major'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:254: blktool] Error 1

Processed: affects 917052, affects 917050

[Debian Bug Tracking System]

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

> affects 917052 + emacs emacs-gtk
Bug #917052 [elpa-xml-rpc] elpa-xml-rpc: Hangs infinitely when compiling for 
emacs 1:26.1+1-2
Added indication that 917052 affects emacs and emacs-gtk
> affects 917050 + emacs emacs-gtk
Bug #917050 [elpa-markdown-mode] elpa-markdown-mode: Hangs infinitely when 
compiling for emacs 1:26.1+1-2
Added indication that 917050 affects emacs and emacs-gtk
> thanks
Stopping processing here.

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

Bug#917054: Template parse error near `in Sekunden.', in stanza #18 of /var/lib/dpkg/info/dump1090-mutability.templates

[Matthew W.S. Bell]

Package: dump1090-mutability
Version: 1.15~20180310.4a16df3+dfsg-4
Severity: grave

This version of the package is uninstallable:

Setting up dump1090-mutability (1.15~20180310.4a16df3+dfsg-4) ...
Template parse error near `in Sekunden.', in stanza #18 of 
/var/lib/dpkg/info/dump1090-mutability.templates
dpkg: error processing package dump1090-mutability (--configure):
 installed dump1090-mutability package post-installation script subprocess 
returned error exit status 25

Examining the package's template file reveals that, in the stanza for
dump1090-mutability/net-out-interval, wrapping of multiple lines is not as
rfc2822(?) records require. This seems to be the only issue, and resolving
it allows the package to finish installing.

Matthew W.S. Bell





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

Bug#917052: elpa-xml-rpc: Hangs infinitely when compiling for emacs 1:26.1+1-2

[Axel Beckert]

Package: elpa-xml-rpc
Version: 1.6.12-2
Severity: serious

Hi,

when upgrading emacs from 1:25.2+1-11 to 1:26.1+1-2, it hangs
infinitely at "install/xml-rpc-1.6.12: byte-compiling for emacs".

Relevant parts of an "ps auxwwwf" output:

root  5644  0.0  0.0   2392   768 pts/4S+   00:54   0:00
  \_ /bin/sh /var/lib/dpkg/info/emacs-gtk.postinst configure 1:25.2+1-11
root  5647  0.0  0.0  19168 11604 pts/4S+   00:54   0:00
  \_ /usr/bin/perl -w /usr/lib/emacsen-common/emacs-install emacs
root  5893  0.0  0.0  0 0 pts/4Z+   00:54   0:00
  \_ [emacs-install] 
root  6179  0.0  0.0   2392   772 pts/4S+   00:55   0:00
  \_ /bin/sh /usr/lib/emacsen-common/packages/install/elpa-xml-rpc emacs
root  6182  0.0  0.0   2392   108 pts/4S+   00:55   0:00
  \_ /bin/sh /usr/lib/emacsen-common/packages/install/elpa-xml-rpc 
emacs
root  6183 99.9  0.0 274740 41712 pts/4Rl+  00:55  18:39
  \_ emacs -q -batch -l package --eval (add-to-list 
'package-directory-list "/usr/share/emacs/site-lisp/elpa-src") -f 
package-initialize -f batch-byte-compile xml-rpc-autoloads.el xml-rpc-pkg.el 
xml-rpc.el

Please note the over 18 minutes of CPU time of process 6183.

Please feel free to reassign this to emacs in case you think this is
an issue with emacs 26.1 itself and not with this elpa package.

P.S.: This looks very similar to https://bugs.debian.org/917050
against elpa-markdown-mode.

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

Kernel: Linux 4.18.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages elpa-xml-rpc depends on:
ii  emacsen-common  3.0.4

Versions of packages elpa-xml-rpc recommends:
iu  emacs  1:26.1+1-2
ih  emacs-gtk [emacs]  1:26.1+1-2

elpa-xml-rpc suggests no packages.

-- no debconf information

Processed: retitle 917050 to elpa-markdown-mode: Hangs infinitely when compiling for emacs 1:26.1+1-2

[Debian Bug Tracking System]

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

> # Fix reportbug not having prepended the package name due to epoch version 
> number in subject
> retitle 917050 elpa-markdown-mode: Hangs infinitely when compiling for emacs 
> 1:26.1+1-2
Bug #917050 [elpa-markdown-mode] Hangs infinitely when compiling for emacs 
1:26.1+1-2
Changed Bug title to 'elpa-markdown-mode: Hangs infinitely when compiling for 
emacs 1:26.1+1-2' from 'Hangs infinitely when compiling for emacs 1:26.1+1-2'.
> thanks
Stopping processing here.

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

Bug#912048: obs-build: FTBFS: Test failures

[Santiago Vila]

On Fri, 21 Dec 2018, Hector Oron wrote:

> If you think the package still FTBFS, please reply this message and I'll
> re-try to reproduce it one more time.

Hello, I'm not Daniel, but I can reproduce this in my own autobuilders,
and the package still FTBFS in reproducible-builds:

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

The following message in the build log:

> Can't locate Date/Parse.pm in @INC (you may need to install the Date::Parse 
> module)

seems suspicious to me. Are you sure you tried to build the package in
a clean minimal chroot?

Thanks.

Processed: Re: Bug#912048: obs-build: FTBFS: Test failures

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #912048 [src:obs-build] obs-build: FTBFS: Test failures
Severity set to 'serious' from 'normal'

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

Bug#917050: Hangs infinitely when compiling for emacs 1:26.1+1-2

[Axel Beckert]

Package: elpa-markdown-mode
Version: 2.3+154-1
Severity: serious

Hi,

when upgrading emacs from 1:25.2+1-11 to 1:26.1+1-2, it hangs
infinitely at "install/markdown-mode-2.3snapshot154: byte-compiling
for emacs".

Relevant parts of an "ps auxwwwf" output:

root 20406  0.0  0.0   2388   764 pts/18   S+   Dec21   0:00  
\_ /bin/sh /var/lib/dpkg/info/emacs-gtk.postinst configure 1:25.2+1-11
root 20409  0.0  0.0  18984 11432 pts/18   S+   Dec21   0:00
  \_ /usr/bin/perl -w /usr/lib/emacsen-common/emacs-install emacs
root 20682  0.0  0.0  0 0 pts/18   Z+   Dec21   0:00
  \_ [emacs-install] 
root 20820  0.0  0.0   2388   764 pts/18   S+   Dec21   0:00
  \_ /bin/sh /usr/lib/emacsen-common/packages/install/elpa-markdown-mode 
emacs
root 20823  0.0  0.0   2388   100 pts/18   S+   Dec21   0:00
  \_ /bin/sh 
/usr/lib/emacsen-common/packages/install/elpa-markdown-mode emacs
root 20824 99.9  0.0 274260 41400 pts/18   Rl+  Dec21 526:43
  \_ emacs -q -batch -l package --eval (add-to-list 
'package-directory-list "/usr/share/emacs/site-lisp/elpa-src") -f 
package-initialize -f batch-byte-compile markdown-mode-autoloads.el 
markdown-mode-pkg.el markdown-mode.el

Please note 526 minutes (!) CPU time of process 20824.

Please feel free to reassign this to emacs in case you think this is
an issue with emacs 26.1 itself and not with this elpa package.

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

Kernel: Linux 4.18.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages elpa-markdown-mode depends on:
iu  emacs1:26.1+1-2
iu  emacs-gtk [emacsen]  1:26.1+1-2
ii  emacsen-common   3.0.4

elpa-markdown-mode recommends no packages.

elpa-markdown-mode suggests no packages.

-- no debconf information

Bug#917018: wget: Unusable - permanent segmentation fault

[Bernhard Übelacker]

Hello rwpenney,
just tried to reproduce and collect some information for the maintainer
on a minimal buster amd64 qemu VM.

Unfortunately I could not reproduce the crash
and after 700 files I stopped my test.

Maybe you could run the wget command like that:

gdb -q -ex 'set pagination off' -ex 'set width 0' -ex run -ex bt -ex detach 
-ex quit --args wget -r -k -l inf http://www.debian.org

Or you install a coredump collector like systemd-coredump and
provide the output of journalctl for that time.

In [1] are also some points to get more information into the backtrace.

Kind regards,
Bernhard

[1] https://wiki.debian.org/HowToGetABacktrace

Bug#878193: fails to start with minimal dependencies from testing

[Adrian Bunk]

On Fri, Dec 21, 2018 at 09:07:19AM +0100, intrigeri wrote:
> Hi,
> 
> AFAICT:
> 
>  - This bug is about installing packages from testing/sid on stable,
>i.e. partial upgrade, which is not supported.

This is kinda supported, and there are important usecases that have
a big overlap with it:
- ensuring everything continues working during an upgrade
  (might not be applicable in this specific case)
- ensuring the package does not migrate to testing too early
- ensuring the package works if backported

>  - Two different workarounds were documented (one visible here and one
>erroneously sent to cont...@bugs.debian.org:
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878193;msg=7)
> 
> So I don't understand why this bug should be RC for Buster: it does
> not actually affect Buster and there's no supported upgrade path given
> PuppetDB was not part of any Debian stable release yet.
> 
> Adrian, what do you think? Thanks in advance!

Ignoring the severity question, versioning the dependencies
on the 5 packages mentioned in the workaround should not be
a controversial thing. It would at least ensure that noone
will create a broken backport to stretch.

But there is a real blocker hidden in the workaroud:
  # java-1.8 should be the default runtime, if it's not check 
update-alternatives

The date when the autopkgtest started failing also indicate that the
package might be broken with Java >= 9, and buster will use Java 11.

> Cheers,

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 (with 1 error): forward this and that

[Debian Bug Tracking System]

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

> forwarded 904111 https://bugzilla.clamav.net/show_bug.cgi?id=12242
Bug #904111 [clamav-daemon] clamav-daemon causing deadlocks/blocking I/O.
Set Bug forwarded-to-address to 
'https://bugzilla.clamav.net/show_bug.cgi?id=12242'.
> forwarded 916146 https://bugzilla.clamav.net/show_bug.cgi?id=12241
Bug #916146 [clamav-freshclam] clamav-freshclam: Daily updater thinks it can 
use IPv6, but it's available for local network only
Set Bug forwarded-to-address to 
'https://bugzilla.clamav.net/show_bug.cgi?id=12241'.
> forwarded 916827 https://bugzilla.clamav.net/show_bug.cgi?id=12240
Bug #916827 [clamav] clamav UTF8 filenames
Set Bug forwarded-to-address to 
'https://bugzilla.clamav.net/show_bug.cgi?id=12240'.
> Sebastian
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Processed: crrcsim: diff for NMU version 0.9.13-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 916346 + patch
Bug #916346 [src:crrcsim] crrcsim build depends on libjpeg9-dev
Added tag(s) patch.
> tags 916346 + pending
Bug #916346 [src:crrcsim] crrcsim build depends on libjpeg9-dev
Added tag(s) pending.

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

Bug#916346: crrcsim: diff for NMU version 0.9.13-3.1

[Adrian Bunk]

Control: tags 916346 + patch
Control: tags 916346 + pending

Dear maintainer,

I've prepared an NMU for crrcsim (versioned as 0.9.13-3.1) and uploaded 
it to DELAYED/5. 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 crrcsim-0.9.13/debian/changelog crrcsim-0.9.13/debian/changelog
--- crrcsim-0.9.13/debian/changelog	2018-12-01 17:49:34.0 +0200
+++ crrcsim-0.9.13/debian/changelog	2018-12-22 01:02:57.0 +0200
@@ -1,3 +1,11 @@
+crrcsim (0.9.13-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch back to the libjpeg that will be in buster.
+(Closes: #916346)
+
+ -- Adrian Bunk   Sat, 22 Dec 2018 01:02:57 +0200
+
 crrcsim (0.9.13-3) unstable; urgency=medium
 
   * Fix sys/io unsupported, defining dummy interfaces for io operations
diff -Nru crrcsim-0.9.13/debian/control crrcsim-0.9.13/debian/control
--- crrcsim-0.9.13/debian/control	2018-12-01 17:49:34.0 +0200
+++ crrcsim-0.9.13/debian/control	2018-12-22 01:02:43.0 +0200
@@ -10,7 +10,7 @@
  libboost-thread-dev,
  libplib-dev,
  libcgal-dev,
- libjpeg9-dev,
+ libjpeg-dev,
  portaudio19-dev,
 Standards-Version: 4.1.4
 Homepage: http://crrcsim.berlios.de

Bug#915316: marked as done (ansible: FTBFS due to missing build dependency on python-jinja2)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 23:00:10 +
with message-id 
and subject line Bug#915316: fixed in ansible 2.7.5+dfsg-1
has caused the Debian Bug report #915316,
regarding ansible: FTBFS due to missing build dependency on python-jinja2
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.)


-- 
915316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ansible
Version: 2.7.1+dfsg-2
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch

Dear Maintainer,

ansible currently fails to build from source in a clean chroot due to a
lack of a build dependency on python-jinja2. I tested that sid has the
same failure as Ubuntu, which you can see here [1].

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

  * Build-depend on python-jinja2 to fix FTBFS.

Thanks for considering the patch.

Logan

[1] 
https://launchpadlibrarian.net/399587454/buildlog_ubuntu-disco-amd64.ansible_2.7.1+dfsg-2_BUILDING.txt.gz

-- 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-11-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 ansible-2.7.1+dfsg/debian/control ansible-2.7.1+dfsg/debian/control
--- ansible-2.7.1+dfsg/debian/control   2018-11-13 05:02:13.0 -0500
+++ ansible-2.7.1+dfsg/debian/control   2018-12-02 12:53:19.0 -0500
@@ -12,6 +12,7 @@
python-yaml,
python-nose,
python-passlib,
+   python-jinja2,
dh-python
 Standards-Version: 4.1.1
 Vcs-Browser: https://salsa.debian.org/debian/ansible
--- End Message ---
--- Begin Message ---
Source: ansible
Source-Version: 2.7.5+dfsg-1

We believe that the bug you reported is fixed in the latest version of
ansible, 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.
Lee Garrett  (supplier of updated ansible package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 19 Dec 2018 11:35:55 +0100
Source: ansible
Binary: ansible ansible-doc
Architecture: source all
Version: 2.7.5+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Harlan Lieberman-Berg 
Changed-By: Lee Garrett 
Description:
 ansible- Configuration management, deployment, and task execution system
 ansible-doc - Ansible documentation and examples
Closes: 848871 915316
Changes:
 ansible (2.7.5+dfsg-1) unstable; urgency=medium
 .
   * New upstream release
   * Remove any loading of external resources from the docs
   * Only symlink JS that dh_sphinxdoc doesn't take care of
   * Override lintian for a long line in layout.html
   * Build ansible-doc again (Closes: #848871)
   * Add build-depends to python-jinja2 (Closes: #915316)
   * Bump Standards-Version (no changes needed)
Checksums-Sha1:
 514a2da11db4847e8f77c0f3b3632d3f82a82184 2323 ansible_2.7.5+dfsg-1.dsc
 248ef6b9a065ae340f006d47d0b45843ba50e945 6380632 ansible_2.7.5+dfsg.orig.tar.xz
 b3a81de80595ef19035ec16c28d21513350840eb 18608 
ansible_2.7.5+dfsg-1.debian.tar.xz
 39109d0e58cec53c7949f2eeeb5f0773af20e396 3391316 
ansible-doc_2.7.5+dfsg-1_all.deb
 055617e7be9f4db6bb0649d42eb3635bf485c5fb 3952312 ansible_2.7.5+dfsg-1_all.deb
 e13f7e3cfea95f5b6aab850b15c4b99d8f4d 8022 
ansible_2.7.5+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 22903d76f71fe7e450bdfcca94bbefebfc152b9af55c14e225fa1162e19a8da3 2323 
ansible_2.7.5+dfsg-1.dsc
 860253fbf1b18e76e6d9fd98001c57eab4636a8f5951fcbf038f50067f6ee0ac 6380632 
ansible_2.7.5+dfsg.orig.tar.xz
 555f5f4e9c7c6cd49c7ab96d13c81701f736e60b912d4ff54f035a7ec05b8a0a 

Bug#915383: marked as done (freecad: Freecad using new version of coin3 with cmake)

[Debian Bug Tracking System]

Your message dated Sat, 22 Dec 2018 00:45:29 +0200
with message-id <20181221224529.GG20084@localhost>
and subject line Seems to be fixed in 0.17+dfsg1-6
has caused the Debian Bug report #915383,
regarding freecad: Freecad using new version of coin3 with cmake
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.)


-- 
915383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915383
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freecad
Severity: grave
Justification: renders package unusable

Dear Maintainer,

coin3 is in experimental and is in the beginning of a transition to a new 
version built with cmake.
freecad will need to use this version.



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

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

Versions of packages freecad depends on:
ii  libboost-atomic1.62.0   1.62.0+dfsg-4
ii  libboost-chrono1.62.0   1.62.0+dfsg-4
ii  libboost-date-time1.62.01.62.0+dfsg-4
ii  libboost-filesystem1.62.0   1.62.0+dfsg-4
ii  libboost-program-options1.62.0  1.62.0+dfsg-4
ii  libboost-python1.62.0   1.62.0+dfsg-4
ii  libboost-regex1.62.01.62.0+dfsg-4
ii  libboost-signals1.62.0  1.62.0+dfsg-4
ii  libboost-system1.62.0   1.62.0+dfsg-4
ii  libboost-thread1.62.0   1.62.0+dfsg-4
ii  libc6   2.24-11+deb9u3
pn  libcoin80v5 
ii  libfreeimage3   3.17.0+ds1-5
ii  libfreetype62.6.3-3.2
ii  libgcc1 1:6.3.0-18+deb9u1
ii  libgl1-mesa-glx [libgl1]13.0.6-1+b2
ii  libglu1-mesa [libglu1]  9.0.0-2.1
ii  liboce-foundation10 0.17.2-2
ii  liboce-modeling10   0.17.2-2
ii  liboce-ocaf-lite10  0.17.2-2
ii  liboce-ocaf10   0.17.2-2
ii  liboce-visualization10  0.17.2-2
ii  libpyside1.21.2.2-2+b1
ii  libpython2.72.7.13-2+deb9u3
ii  libqt4-network  4:4.8.7+dfsg-11
ii  libqt4-opengl   4:4.8.7+dfsg-11
ii  libqt4-svg  4:4.8.7+dfsg-11
ii  libqt4-xml  4:4.8.7+dfsg-11
ii  libqtcore4  4:4.8.7+dfsg-11
ii  libqtgui4   4:4.8.7+dfsg-11
ii  libqtwebkit42.3.4.dfsg-9.1
ii  libshiboken1.2v51.2.2-3.1
ii  libsoqt4-20 1.6.0~e8310f-3
ii  libspnav0   0.2.3-1
ii  libstdc++6  6.3.0-18+deb9u1
ii  libx11-62:1.6.4-3+deb9u1
ii  libxerces-c3.1  3.1.4+debian-2+deb9u1
ii  libxext62:1.3.3-1+b2
ii  libzipios++0v5  0.1.5.9+cvs.2007.04.28-6
ii  pyside-tools0.2.15-1+b1
ii  python  2.7.13-2
ii  python-collada  0.4-2
ii  python-matplotlib   2.0.0+dfsg1-2
pn  python-pivy 
ii  python-ply  3.9-1
ii  python-pyside   1.2.2-2
ii  python2.7   2.7.13-2+deb9u3
ii  zlib1g  1:1.2.8.dfsg-5

freecad recommends no packages.

Versions of packages freecad suggests:
ii  graphviz  2.38.0-17
pn  povray
--- End Message ---
--- Begin Message ---
Version: 0.17+dfsg1-6

Seems to be fixed in 0.17+dfsg1-6:
https://buildd.debian.org/status/package.php?p=freecad

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

Processed: dtfabric: Wrong name

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #917042 [dtfabric] dtfabric: Wrong name
Added tag(s) pending.

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

Bug#917042: dtfabric: Wrong name

[Hilko Bengen]

Package: dtfabric
Version: 20180808-1
Severity: serious
Control: tag -1 pending

Dear Maintainer,

the dtfabric package is a Python3 library which means that its name must
be prefixed with "python3-". (Python policy 3.3)

I am marking this bug as pending because I intend to upload a new
version that will fix this bug -- and will add a Python 2 package, in
order to be able to fix #914607 without having to migrate Plaso to
Python 3 _right now_.

Cheers,
-Hilko

Processed: Re: procmeter3 FTBFS with glibc 2.28

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #916054 [src:procmeter3] procmeter3 FTBFS with glibc 2.28
Added tag(s) patch.

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

Bug#916223: moonshot-gss-eap: FTBFS against xmltooling 3

[Sebastian Andrzej Siewior]

On 2018-12-11 18:26:24 [-0500], Sam Hartman wrote:
> Fixing moonshot-gss-eap and getting a new moonshot-ui is next up for me
> for Debian weekend tasks.

This means an upload from exp to unstable?

Sebastian

Bug#916054: procmeter3 FTBFS with glibc 2.28

[Aurelien Jarno]

control: tag -1 + patch

On 2018-12-09 19:12, Adrian Bunk wrote:
> Source: procmeter3
> Version: 3.6-1
> Severity: serious
> Tags: ftbfs buster sid
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/procmeter3.html
> 
> ...
> longrun.c:41:24: error: unknown type name 'loff_t'; did you mean 'off_t'?
>  static void read_cpuid(loff_t address, int *eax, int *ebx, int *ecx, int 
> *edx) {
> ^~

Please find below a patch to fix the issue.

diff -Nru procmeter3-3.6/debian/patches/loff_t.patch 
procmeter3-3.6/debian/patches/loff_t.patch
--- procmeter3-3.6/debian/patches/loff_t.patch  1970-01-01 00:00:00.0 
+
+++ procmeter3-3.6/debian/patches/loff_t.patch  2018-12-21 21:50:55.0 
+
@@ -0,0 +1,18 @@
+Description: Fix compilation with newer glibc
+Fixes compilation with newer glibc.
+If _XOPEN_SOURCE is defined _DEFAULT_SOURCE needs to be defined explicit
+to have the definition of loff_t.
+Author: Aurelien Jarno 
+Bug-Debian: https://bugs.debian.org/916054
+Last-Update: 2018-12-21
+
+--- procmeter3-3.6.orig/modules/longrun.c
 procmeter3-3.6/modules/longrun.c
+@@ -15,6 +15,7 @@
+   ***/
+ 
+ #define _XOPEN_SOURCE 500
++#define _DEFAULT_SOURCE
+ 
+ #include 
+ #include 
diff -Nru procmeter3-3.6/debian/patches/series 
procmeter3-3.6/debian/patches/series
--- procmeter3-3.6/debian/patches/series2014-03-22 15:38:22.0 
+
+++ procmeter3-3.6/debian/patches/series2018-12-21 21:50:55.0 
+
@@ -6,3 +6,4 @@
 #include.patch
 dont-override-flags.patch
 libX11.patch
+loff_t.patch

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#914607: Re-adding python-dfwinreg

[Hilko Bengen]

Good evening.

I am going to re-add the Python2 package for dfwinreg which was removed
by SZ Lin for 20181214-1. This might take a few days to resolve because
I think the package will have to go through NEW again.

A bunch of Plaso dependencies and eventually plaso itself will need to
be updated, too, I'll work on that over the next few days -- perhaps we
can even remove the Python2 packages before the buster release again.

Cheers,
-Hilko

Processed: bug 914537 is forwarded to https://gitlab.com/OpenMW/openmw/issues/4737

[Debian Bug Tracking System]

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

> forwarded 914537 https://gitlab.com/OpenMW/openmw/issues/4737
Bug #914537 [openmw] openmw: segfault at start
Set Bug forwarded-to-address to 'https://gitlab.com/OpenMW/openmw/issues/4737'.
> thanks
Stopping processing here.

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

Processed: severity of 891233 is serious

[Debian Bug Tracking System]

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

> severity 891233 serious
Bug #891233 [kamoso] kamoso: segmentation fault in kamoso in Debian 9 stable. 
Application crashes while starting.
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: photocollage: diff for NMU version 1.4.3-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 914440 + patch
Bug #914440 [photocollage] photocollage: ValueError: Namespace Gtk not available
Added tag(s) patch.
> tags 914440 + pending
Bug #914440 [photocollage] photocollage: ValueError: Namespace Gtk not available
Added tag(s) pending.

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

Bug#914440: photocollage: diff for NMU version 1.4.3-2.1

[Adrian Bunk]

Control: tags 914440 + patch
Control: tags 914440 + pending

Dear maintainer,

I've prepared an NMU for photocollage (versioned as 1.4.3-2.1) and 
uploaded it to DELAYED/9. 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 photocollage-1.4.3/debian/changelog photocollage-1.4.3/debian/changelog
--- photocollage-1.4.3/debian/changelog	2016-12-22 22:13:40.0 +0200
+++ photocollage-1.4.3/debian/changelog	2018-12-21 23:49:53.0 +0200
@@ -1,3 +1,10 @@
+photocollage (1.4.3-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add the missing dependency on gir1.2-gtk-3.0. (Closes: #914440)
+
+ -- Adrian Bunk   Fri, 21 Dec 2018 23:49:53 +0200
+
 photocollage (1.4.3-2) unstable; urgency=medium
 
   * Add missing 'python3-six' to dependencies
diff -Nru photocollage-1.4.3/debian/control photocollage-1.4.3/debian/control
--- photocollage-1.4.3/debian/control	2016-12-22 22:13:10.0 +0200
+++ photocollage-1.4.3/debian/control	2018-12-21 23:49:53.0 +0200
@@ -15,6 +15,7 @@
  ${misc:Depends},
  ${python3:Depends},
  python3-gi-cairo,
+ gir1.2-gtk-3.0,
  python3-six,
 Description: Graphical tool to make photo collage posters
  PhotoCollage allows you to create photo collage posters. It assembles

Bug#917041: golang-github-influxdata-influxql: Outdated version produces empty results for some queries

[Guillem Jover]

Source: golang-github-influxdata-influxql
Source-Version: 0.0~git20180330.145e067-2
Severity: serious

Hi!

This package is a bit outdated and it causes some queries to produce
empty results. We noticed this with our internal influxdb version, when
grafana was not showing some graphs for some stuff, and packaging and
upgrading it to 0.0~git20180925.1cbfca8-0.1 and rebuilding influxdb with
that fixed the issues. I think there are multiple upstream reports about
this, which I'll be commenting on, as they seem to be undiagnosed there.

A reproducer with packages from Debian sid follows:

  ,---
  $ influx
  Connected to http://localhost:8086 version 1.6.4
  InfluxDB shell version: 1.6.4
  > quit
  $ curl https://s3.amazonaws.com/noaa.water-database/NOAA_data.txt \
  -o NOAA_data.txt
  $ influx -import -path=NOAA_data.txt -precision=s \
  -database=NOAA_water_database
  $ influx -database NOAA_water_database \
  -execute 'show tag values with key = "randtag"'
  $
  `---

While that should be returning something like:

  ,---
  name: h2o_quality
  key   value
  ---   -
  randtag   1
  randtag   2
  randtag   3
  `---

Thanks,
Guillem

Processed: forcibly merging 916774 914966

[Debian Bug Tracking System]

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

> forcemerge 916774 914966
Bug #916774 [linux-perf-4.19] linux-perf metapackage fails to upgrade due to 
file conflict between linux-perf-4.18 & linux-perf-4.19
Bug #916774 [linux-perf-4.19] linux-perf metapackage fails to upgrade due to 
file conflict between linux-perf-4.18 & linux-perf-4.19
Marked as found in versions linux/4.19.5-1~exp1.
Bug #914966 [linux-perf-4.19] linux-perf-4.19: missing Breaks+Replaces: 
linux-perf-4.18
Added tag(s) pending.
Merged 914966 916774
> thanks
Stopping processing here.

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

Processed: severity of 915198 is important

[Debian Bug Tracking System]

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

> severity 915198 important
Bug #915198 [src:python-molotov] python-molotov FTBFS: BrokenPipeError: [Errno 
32] Broken pipe
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: tagging 915198

[Debian Bug Tracking System]

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

> tags 915198 + unreproducible
Bug #915198 [src:python-molotov] python-molotov FTBFS: BrokenPipeError: [Errno 
32] Broken pipe
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

Bug#917036: libswagger2-perl: dead upstream

[Jonas Smedegaard]

Package: libswagger2-perl
Version: 0.89-1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Homepage https://metacpan.org/release/Swagger2 is a 404 Not Found error.

Package has no reverse dependencies.

Severity raised to avoid getting it included with Buster.
Please lower if someone disagrees.


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlwdVC4ACgkQLHwxRsGg
ASFP6w//TgHQTR5JcU6f5uZrwWc+0JbaOvj7Viy3s7vuKW3Kk2Z165NsDSBbApU2
ezyFnPviT+IwqEOCjytXiE5GnPhf4C39r5d9dB9qy9a8zywmURLWMe4wEsHUeYnx
qvOkrpaRT1XG3UUqSrNDrmkHqRgWOVEXLf0RkyaNRsWHuI2AfhYkLb/SuMQf1hdd
rpdBXnQwtUMMrV6OyJ7FzvEuTYE6iOzDV8fj0FbZsI0WsLKA7e44qkvqDZBZWQw+
YEoJK54kUQIBYTTZ6nESP0zrj8a8IEuVXBC4fbexrbX9Jql8VEEYRecaSWK8ps2q
19WKIa+h4WaTDj5YTWDbaf8J4zVXdkRp6Zg+zKJUa5myOXOuAAkMcGc/eJnLLk6T
Q+puxA/KwoUsLrNt9/web2Kp2UDJP9o/jrvntU+SRkmrlDxl2HWdgk8tlknBDlJg
73NP1vbv73UWt72SP8OwhgfUBizEOjw7zd++OI6ECa+lYZleZi4xpBl/A5cLXWbv
NKOaDzPjIf4xhg8kyeZgoEg6ZVLNo9AxVGIDFqLDlOYF4LeR9wOXJuzsEJVkR9zP
U3GCDw2X3xazcvorEQuaHE9QDsyUh0NtAs6dC7fAwXOkqQDhLsR5o21m5nWXVViF
1SLhz8Sj0eDT1zboFknwOQkyykXaDfH9VDNXrBealjMY1ZegoBM=
=MVBf
-END PGP SIGNATURE-

Bug#915198: [Python-modules-team] Bug#915198: python-molotov FTBFS: BrokenPipeError: [Errno 32] Broken pipe

[Ondrej Novy]

Hi,

I can't reproduce it and I can build this package locally without any
problem.

-- 
Best regards
 Ondřej Nový

Email: n...@ondrej.org
PGP: 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B

Bug#915776: marked as done (python-werkzeug FTBFS: fixture 'xprocess' not found)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 20:46:43 +
with message-id 
and subject line Bug#915776: fixed in python-werkzeug 0.14.1+dfsg1-4
has caused the Debian Bug report #915776,
regarding python-werkzeug FTBFS: fixture 'xprocess' 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.)


-- 
915776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-werkzeug
Version: 0.14.1+dfsg1-3
Severity: serious
Tags: ftbfs

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

...
 ERRORS 
_ ERROR at setup of TestRedisCache.test_generic_get_dict[make_cache0] __
file /build/1st/python-werkzeug-0.14.1+dfsg1/tests/contrib/test_cache.py, line 
59
  def test_generic_get_dict(self, c):
file /build/1st/python-werkzeug-0.14.1+dfsg1/tests/contrib/test_cache.py, line 
54
  @pytest.fixture
  def c(self, make_cache):
file /build/1st/python-werkzeug-0.14.1+dfsg1/tests/contrib/test_cache.py, line 
202
  @pytest.fixture(params=[
  ([], dict()),
  ([redis.Redis()], dict()),
  ([redis.StrictRedis()], dict())
  ])
  def make_cache(self, xprocess, request):
E   fixture 'xprocess' not found
>   available fixtures: c, cache, capfd, capfdbinary, caplog, capsys, 
> capsysbinary, dev_server, doctest_namespace, fast_sleep, make_cache, 
> monkeypatch, pytestconfig, record_property, record_xml_attribute, 
> record_xml_property, recwarn, subprocess, tmp_path, tmp_path_factory, tmpdir, 
> tmpdir_factory
>   use 'pytest --fixtures [testpath]' for help on them.

/build/1st/python-werkzeug-0.14.1+dfsg1/tests/contrib/test_cache.py:202
_ ERROR at setup of TestRedisCache.test_generic_get_dict[make_cache1] __
file /build/1st/python-werkzeug-0.14.1+dfsg1/tests/contrib/test_cache.py, line 
59
  def test_generic_get_dict(self, c):
file /build/1st/python-werkzeug-0.14.1+dfsg1/tests/contrib/test_cache.py, line 
54
  @pytest.fixture
  def c(self, make_cache):
file /build/1st/python-werkzeug-0.14.1+dfsg1/tests/contrib/test_cache.py, line 
202
  @pytest.fixture(params=[
  ([], dict()),
  ([redis.Redis()], dict()),
  ([redis.StrictRedis()], dict())
  ])
  def make_cache(self, xprocess, request):
E   fixture 'xprocess' not found
>   available fixtures: c, cache, capfd, capfdbinary, caplog, capsys, 
> capsysbinary, dev_server, doctest_namespace, fast_sleep, make_cache, 
> monkeypatch, pytestconfig, record_property, record_xml_attribute, 
> record_xml_property, recwarn, subprocess, tmp_path, tmp_path_factory, tmpdir, 
> tmpdir_factory
>   use 'pytest --fixtures [testpath]' for help on them.
...
== 525 passed, 101 skipped, 61 error in 10.02 seconds ==
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/build/1st/python-werkzeug-0.14.1+dfsg1/.pybuild/cpython2_2.7_werkzeug/build; 
python2.7 -m pytest {dir}/tests -k-tests/contrib/test_cache.py
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
+ kill 30703
make[1]: *** [debian/rules:24: override_dh_auto_test] Error 25
--- End Message ---
--- Begin Message ---
Source: python-werkzeug
Source-Version: 0.14.1+dfsg1-4

We believe that the bug you reported is fixed in the latest version of
python-werkzeug, 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.
Ondřej Nový  (supplier of updated python-werkzeug 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, 21 Dec 2018 21:02:47 +0100
Source: python-werkzeug
Binary: python-werkzeug python3-werkzeug python-werkzeug-doc
Architecture: source
Version: 0.14.1+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: Python Modules Packaging Team 

Changed-By: Ondřej Nový 
Description:
 python-werkzeug - collection of utilities for WSGI applications (Python 2.x)
 python-werkzeug-doc - 

Processed: Bug #915776 in python-werkzeug marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #915776 [src:python-werkzeug] python-werkzeug FTBFS: fixture 'xprocess' not 
found
Added tag(s) pending.

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

Bug#915776: Bug #915776 in python-werkzeug marked as pending

[Ondřej Nový]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/python-werkzeug/commit/d3825765625627dc98cad4ef6672b35dbef78e6e


Don't run xprocess tests without xprocess (Closes: #915776)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/915776

Bug#913475: marked as done (salt: CVE-2018-15751: remote authentication bypass in salt-api(netapi) allows to execute arbitrary commands)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 19:20:58 +
with message-id 
and subject line Bug#913475: fixed in salt 2018.3.3+dfsg1-1
has caused the Debian Bug report #913475,
regarding salt: CVE-2018-15751: remote authentication bypass in 
salt-api(netapi) allows to execute arbitrary commands
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.)


-- 
913475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: salt
Version: 2017.7.4+dfsg1-1
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for salt.

CVE-2018-15751[0]:
| SaltStack Salt before 2017.7.8 and 2018.3.x before 2018.3.3 allow
| remote attackers to bypass authentication and execute arbitrary
| commands via salt-api(netapi).

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-15751
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-15751
[1] https://bugzilla.novell.com/show_bug.cgi?id=1113699
[2] https://docs.saltstack.com/en/2017.7/topics/releases/2017.7.8.html
https://docs.saltstack.com/en/latest/topics/releases/2018.3.3.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: salt
Source-Version: 2018.3.3+dfsg1-1

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

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated salt 
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, 21 Dec 2018 19:21:57 +0100
Source: salt
Binary: salt-common salt-master salt-minion salt-syndic salt-ssh salt-doc 
salt-cloud salt-api salt-proxy
Architecture: source all
Version: 2018.3.3+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Salt Team 
Changed-By: Benjamin Drung 
Description:
 salt-api   - Generic, modular network access system
 salt-cloud - public cloud VM management system
 salt-common - shared libraries that salt requires for all packages
 salt-doc   - additional documentation for salt, the distributed remote executi
 salt-master - remote manager to administer servers via salt
 salt-minion - client package for salt, the distributed remote execution system
 salt-proxy - Proxy client package for salt stack
 salt-ssh   - remote manager to administer servers via Salt SSH
 salt-syndic - master-of-masters for salt, the distributed remote execution syst
Closes: 893817 896921 898142 904654 905519 906275 908430 913475 913476
Changes:
 salt (2018.3.3+dfsg1-1) unstable; urgency=medium
 .
   * New upstream release
 - CVE-2018-15751: remote authentication bypass in salt-api (netapi) allows
   executing arbitrary commands (Closes: #913475)
 - CVE-2018-15750: Directory traversal in salt-api allows remote attackers
   to identitfy arbitrary files (Closes: #913476)
 - Support Python 3.7 (Closes: #904654)
 - Fix typo (Closes: #906275)
   * Drop 22 patches that were accepted by upstream and refresh remaining ones.
   * Remove inactive Wolodja Wentland. Thanks for your work. (Closes: #898142)
   * Remove empty /var/lib/salt on package purge (Closes: #905519)
   * Fix InstallRequirement.from_line for pip 18.1
   * Use collections.abc instead of collections for Python 3.7 (from upstream)
   * Add patch to support unittest.mock from Python >= 3.6 again
   * Fix RemoveCapacityFromDiskgroupTestCase require pyvmomi
   * Fix twilio version checking
   * Bump Standards-Version to 4.2.1 (no changes are required)
   * Call setup.py install with --install-layout deb
   * Fix documentation build (with five individual patches)
   * Upgrade to libjs-bootstrap version 3 (Closes: #908430)
   * Add multiple build dependencies to increase unittest coverage
   * Add autopkgtest to run the unittests
   * Skip failing test_event_subscription (for now) due to tornado bug #2536
 when using 

Bug#904654: marked as done (salt-common: fails to install with Python 3.7)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 19:20:58 +
with message-id 
and subject line Bug#904654: fixed in salt 2018.3.3+dfsg1-1
has caused the Debian Bug report #904654,
regarding salt-common: fails to install with Python 3.7
to be marked as done.

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

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


-- 
904654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904654
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: salt-common
Version: 2017.7.4+dfsg1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up salt-common (2017.7.4+dfsg1-1) ...
File "/usr/lib/python3/dist-packages/salt/client/mixins.py", line 495
  def async(self, fun, low, user='UNKNOWN', pub=None):
  ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/daemons/masterapi.py", line 1096
  return runner_client.async(fun,
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/master.py", line 1752
  return runner_client.async(fun,
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/minion.py", line 805
  self.io_loop.spawn_callback(self.process_manager.run, async=True)
^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/modules/cassandra_cql.py", line 
340
  def cql_query_with_prepare(query, statement_name, statement_arguments, 
async=False,

 ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/modules/saltutil.py", line 909
  def refresh_modules(async=True):
  ^
  SyntaxError: invalid syntax
  
File 
"/usr/lib/python3/dist-packages/salt/returners/cassandra_cql_return.py", line 
208
  async=True)
  ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/runner.py", line 240
  async_pub = self.async(self.opts['fun'],
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/transport/client.py", line 13
  from salt.utils.async import SyncWrapper
  ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/transport/tcp.py", line 25
  import salt.utils.async
^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/utils/async.py", line 60
  self.async = method(*args, **kwargs)
   ^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/utils/event.py", line 76
  import salt.utils.async
^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/utils/process.py", line 391
  def run(self, async=False):
^
  SyntaxError: invalid syntax
  
File "/usr/lib/python3/dist-packages/salt/wheel/__init__.py", line 119
  return self.async(fun, low)
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package salt-common (--configure):
   installed salt-common package post-installation script subprocess returned 
error exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


salt-common=2017.7.4+dfsg1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: salt
Source-Version: 2018.3.3+dfsg1-1

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

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated salt 
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: 

Bug#896921: marked as done (salt-minion does not start: TypeError: add_accept_handler() got an unexpected keyword argument 'io_loop')

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 19:20:58 +
with message-id 
and subject line Bug#896921: fixed in salt 2018.3.3+dfsg1-1
has caused the Debian Bug report #896921,
regarding salt-minion does not start: TypeError: add_accept_handler() got an 
unexpected keyword argument 'io_loop'
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.)


-- 
896921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: salt-minion
Version: 2017.7.4+dfsg1-1

salt-minion in testing is no longer able to start due to API bugs:

# salt-minion -l debug
[DEBUG   ] Reading configuration from /etc/salt/minion
[DEBUG   ] Including configuration from '/etc/salt/minion.d/_schedule.conf'
[DEBUG   ] Reading configuration from /etc/salt/minion.d/_schedule.conf
[DEBUG   ] Using cached minion ID from /etc/salt/minion_id: cayde7
[DEBUG   ] Configuration file path: /etc/salt/minion
[WARNING ] Insecure logging configuration detected! Sensitive data may be
logged.
[INFO] Setting up the Salt Minion "cayde7"
[DEBUG   ] Created pidfile: /var/run/salt-minion.pid
[WARNING ] /usr/lib/python3/dist-packages/salt/minion.py:802:
DeprecationWarning: zmq.eventloop.ioloop is deprecated in pyzmq 17. pyzmq
now works with default tornado and asyncio eventloops.
  zmq.eventloop.ioloop.install()

[DEBUG   ] Using selector: EpollSelector
[INFO] Starting up the Salt Minion
[DEBUG   ] AsyncEventPublisher PUB socket URI:
/var/run/salt/minion/minion_event_166db1290b_pub.ipc
[DEBUG   ] AsyncEventPublisher PULL socket URI:
/var/run/salt/minion/minion_event_166db1290b_pull.ipc
[INFO] Starting pull socket on
/var/run/salt/minion/minion_event_166db1290b_pull.ipc
Process Process-1:
Traceback (most recent call last):
  File "/usr/lib/python3.6/multiprocessing/process.py", line 258, in
_bootstrap
self.run()
  File "/usr/lib/python3.6/multiprocessing/process.py", line 93, in run
self._target(*self._args, **self._kwargs)
  File "/usr/lib/python3/dist-packages/salt/scripts.py", line 138, in
minion_process
minion.start()
  File "/usr/lib/python3/dist-packages/salt/cli/daemons.py", line 347, in
start
self.minion.tune_in()
  File "/usr/lib/python3/dist-packages/salt/minion.py", line 896, in tune_in
self._bind()
  File "/usr/lib/python3/dist-packages/salt/minion.py", line 814, in _bind
io_loop=self.io_loop,
  File "/usr/lib/python3/dist-packages/salt/utils/event.py", line 1019, in
__init__
self.publisher.start()
  File "/usr/lib/python3/dist-packages/salt/transport/ipc.py", line 517, in
start
io_loop=self.io_loop,
TypeError: add_accept_handler() got an unexpected keyword argument 'io_loop'
--- End Message ---
--- Begin Message ---
Source: salt
Source-Version: 2018.3.3+dfsg1-1

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

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated salt 
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, 21 Dec 2018 19:21:57 +0100
Source: salt
Binary: salt-common salt-master salt-minion salt-syndic salt-ssh salt-doc 
salt-cloud salt-api salt-proxy
Architecture: source all
Version: 2018.3.3+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Salt Team 
Changed-By: Benjamin Drung 
Description:
 salt-api   - Generic, modular network access system
 salt-cloud - public cloud VM management system
 salt-common - shared libraries that salt requires for all packages
 salt-doc   - additional documentation for salt, the distributed remote executi
 salt-master - remote manager to administer servers via salt
 salt-minion - client package for salt, the distributed remote execution system
 salt-proxy - Proxy client package for salt stack
 salt-ssh   - remote manager to administer servers via Salt SSH
 salt-syndic - master-of-masters for salt, the distributed remote execution syst
Closes: 893817 896921 898142 904654 905519 906275 908430 913475 913476
Changes:
 salt (2018.3.3+dfsg1-1) unstable; urgency=medium
 .
   * New upstream 

Bug#908430: marked as done (salt-doc depends on libjs-twitter-bootstrap that will not be in buster)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 19:20:58 +
with message-id 
and subject line Bug#908430: fixed in salt 2018.3.3+dfsg1-1
has caused the Debian Bug report #908430,
regarding salt-doc depends on libjs-twitter-bootstrap that will not be in buster
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.)


-- 
908430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: salt-doc
Version: 2017.7.4+dfsg1-1
Severity: serious
Control: block 907724 by -1

See #907724 for background.
--- End Message ---
--- Begin Message ---
Source: salt
Source-Version: 2018.3.3+dfsg1-1

We believe that the bug you reported is fixed in the latest version of
salt, 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.
Benjamin Drung  (supplier of updated salt 
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, 21 Dec 2018 19:21:57 +0100
Source: salt
Binary: salt-common salt-master salt-minion salt-syndic salt-ssh salt-doc 
salt-cloud salt-api salt-proxy
Architecture: source all
Version: 2018.3.3+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Salt Team 
Changed-By: Benjamin Drung 
Description:
 salt-api   - Generic, modular network access system
 salt-cloud - public cloud VM management system
 salt-common - shared libraries that salt requires for all packages
 salt-doc   - additional documentation for salt, the distributed remote executi
 salt-master - remote manager to administer servers via salt
 salt-minion - client package for salt, the distributed remote execution system
 salt-proxy - Proxy client package for salt stack
 salt-ssh   - remote manager to administer servers via Salt SSH
 salt-syndic - master-of-masters for salt, the distributed remote execution syst
Closes: 893817 896921 898142 904654 905519 906275 908430 913475 913476
Changes:
 salt (2018.3.3+dfsg1-1) unstable; urgency=medium
 .
   * New upstream release
 - CVE-2018-15751: remote authentication bypass in salt-api (netapi) allows
   executing arbitrary commands (Closes: #913475)
 - CVE-2018-15750: Directory traversal in salt-api allows remote attackers
   to identitfy arbitrary files (Closes: #913476)
 - Support Python 3.7 (Closes: #904654)
 - Fix typo (Closes: #906275)
   * Drop 22 patches that were accepted by upstream and refresh remaining ones.
   * Remove inactive Wolodja Wentland. Thanks for your work. (Closes: #898142)
   * Remove empty /var/lib/salt on package purge (Closes: #905519)
   * Fix InstallRequirement.from_line for pip 18.1
   * Use collections.abc instead of collections for Python 3.7 (from upstream)
   * Add patch to support unittest.mock from Python >= 3.6 again
   * Fix RemoveCapacityFromDiskgroupTestCase require pyvmomi
   * Fix twilio version checking
   * Bump Standards-Version to 4.2.1 (no changes are required)
   * Call setup.py install with --install-layout deb
   * Fix documentation build (with five individual patches)
   * Upgrade to libjs-bootstrap version 3 (Closes: #908430)
   * Add multiple build dependencies to increase unittest coverage
   * Add autopkgtest to run the unittests
   * Skip failing test_event_subscription (for now) due to tornado bug #2536
 when using openssl 1.1.1 with TLS 1.3.
   * Skip failing kubernetes test (for now, needs an upstream fix)
   * Use python3-tornado4 due to missing support for tornado version 5
 (Closes: #893817, #896921)
Checksums-Sha1:
 f5f4b22cbc466e2935c0be19c60bffb374dc50d0 4046 salt_2018.3.3+dfsg1-1.dsc
 eec9f6c2be5380831dccd2e21c4d531765a30056 9042056 
salt_2018.3.3+dfsg1.orig.tar.xz
 3bd4e7f35a6593c2a01d28517ef7e00d255db7c6 64888 
salt_2018.3.3+dfsg1-1.debian.tar.xz
 0b9ac0c0b552859c3ce2ddbf2b036c376aab769f 25692 
salt-api_2018.3.3+dfsg1-1_all.deb
 3736eb573c92b439307c9cbf18c17539a4f21d81 27564 
salt-cloud_2018.3.3+dfsg1-1_all.deb
 9ccead80f70cc625a412a8cffd29137101ff18dc 3226732 
salt-common_2018.3.3+dfsg1-1_all.deb
 c90f0082cf3f242ecca88151f0fa2e483c9a2546 9278356 
salt-doc_2018.3.3+dfsg1-1_all.deb
 

Bug#893817: marked as done (salt-minion does not start: AttributeError: type object 'IOLoop' has no attribute 'initialized')

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 19:20:58 +
with message-id 
and subject line Bug#893817: fixed in salt 2018.3.3+dfsg1-1
has caused the Debian Bug report #893817,
regarding salt-minion does not start: AttributeError: type object 'IOLoop' has 
no attribute 'initialized'
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.)


-- 
893817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: salt-minion
Version: 2017.7.4+dfsg1-1
Severity: important

Dear Maintainer,

I tried to (re)start salt-minion and got:

● salt-minion.service - The Salt Minion
   Loaded: loaded (/lib/systemd/system/salt-minion.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Thu 2018-03-22 20:24:27 CET; 2min 
25s ago
 Docs: man:salt-minion(1)
   file:///usr/share/doc/salt/html/contents.html
   https://docs.saltstack.com/en/latest/contents.html
  Process: 2224 ExecStart=/usr/bin/salt-minion (code=exited, status=1/FAILURE)
 Main PID: 2224 (code=exited, status=1/FAILURE)

Mär 22 20:24:27 palme salt-minion[2224]: self.prepare()
Mär 22 20:24:27 palme salt-minion[2224]:   File 
"/usr/lib/python3/dist-packages/salt/cli/daemons.py", line 317, in prepare
Mär 22 20:24:27 palme salt-minion[2224]: self.minion = 
salt.minion.MinionManager(self.config)
Mär 22 20:24:27 palme salt-minion[2224]:   File 
"/usr/lib/python3/dist-packages/salt/minion.py", line 802, in __init__
Mär 22 20:24:27 palme salt-minion[2224]: zmq.eventloop.ioloop.install()
Mär 22 20:24:27 palme salt-minion[2224]:   File 
"/usr/lib/python3/dist-packages/zmq/eventloop/ioloop.py", line 210, in install
Mär 22 20:24:27 palme salt-minion[2224]: assert (not 
ioloop.IOLoop.initialized()) or \
Mär 22 20:24:27 palme salt-minion[2224]: AttributeError: type object 'IOLoop' 
has no attribute 'initialized'
Mär 22 20:24:27 palme systemd[1]: salt-minion.service: Main process exited, 
code=exited, status=1/FAILURE
Mär 22 20:24:27 palme systemd[1]: salt-minion.service: Failed with result 
'exit-code'.

Looks like this is a problem with python-tornado(I have python-tornado 5.0.0-1 
installed) and salt is incompatible with tornado-5.0[1].

[1] https://github.com/saltstack/salt/issues/46340


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

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

Versions of packages salt-minion depends on:
ii  bsdmainutils 11.1.2
ii  dctrl-tools  2.24-2+b1
ii  lsb-base 9.20170808
ii  python3  3.6.4-1
ii  python3-crypto   2.6.1-8
ii  python3-systemd  234-1
ii  python3-zmq  16.0.2-2+b1
ii  salt-common  2017.7.4+dfsg1-1

Versions of packages salt-minion recommends:
pn  debconf-utils  
ii  dmidecode  3.1-1
ii  e2fsprogs  1.44.0-1
pn  sfdisk 

Versions of packages salt-minion suggests:
pn  python3-augeas  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: salt
Source-Version: 2018.3.3+dfsg1-1

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

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

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

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated salt 
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, 21 Dec 2018 19:21:57 +0100
Source: salt
Binary: salt-common salt-master salt-minion salt-syndic salt-ssh salt-doc 
salt-cloud salt-api salt-proxy
Architecture: source all
Version: 2018.3.3+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Salt Team 
Changed-By: Benjamin Drung 
Description:
 salt-api   - Generic, modular network access system
 salt-cloud - public cloud VM management system
 salt-common - shared libraries that salt requires for all packages
 salt-doc   - additional documentation for 

Bug#915986: marked as done (lvm2: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 19:19:47 +
with message-id 
and subject line Bug#915986: fixed in lvm2 2.03.01-2
has caused the Debian Bug report #915986,
regarding lvm2: Incomplete debian/copyright?
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.)


-- 
915986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lvm2
Version: 2.03.01-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Bastian Blank , ftpmas...@debian.org

Hi,

I just ACCEPTed lvm2 from NEW but noticed it was missing attribution 
in debian/copyright for at least Rackable Systems, Rackable Systems,
IBM, etc.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: lvm2
Source-Version: 2.03.01-2

We believe that the bug you reported is fixed in the latest version of
lvm2, 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.
Bastian Blank  (supplier of updated lvm2 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, 21 Dec 2018 20:05:26 +0100
Source: lvm2
Binary: lvm2 lvm2-udeb lvm2-dbusd lvm2-lockd libdevmapper-dev 
libdevmapper1.02.1 libdevmapper1.02.1-udeb dmsetup dmsetup-udeb 
libdevmapper-event1.02.1 dmeventd liblvm2cmd2.03 liblvm2-dev
Architecture: source
Version: 2.03.01-2
Distribution: unstable
Urgency: medium
Maintainer: Debian LVM Team 
Changed-By: Bastian Blank 
Description:
 dmeventd   - Linux Kernel Device Mapper event daemon
 dmsetup- Linux Kernel Device Mapper userspace library
 dmsetup-udeb - Linux Kernel Device Mapper userspace library (udeb)
 libdevmapper-dev - Linux Kernel Device Mapper header files
 libdevmapper-event1.02.1 - Linux Kernel Device Mapper event support library
 libdevmapper1.02.1 - Linux Kernel Device Mapper userspace library
 libdevmapper1.02.1-udeb - Linux Kernel Device Mapper userspace library (udeb)
 liblvm2-dev - LVM2 libraries - development files
 liblvm2cmd2.03 - LVM2 command library
 lvm2   - Linux Logical Volume Manager
 lvm2-dbusd - LVM2 D-Bus daemon
 lvm2-lockd - LVM locking daemon
 lvm2-udeb  - Linux Logical Volume Manager (udeb)
Closes: 915986
Changes:
 lvm2 (2.03.01-2) unstable; urgency=medium
 .
   * Upload to unstable.
   * Rewrite copyright file. (closes: #915986)
Checksums-Sha1:
 cfd4904278037e6465fff77d928a0fd90987c536 2636 lvm2_2.03.01-2.dsc
 1eca9c06d00dd6cce5a0a8071bac2dc6c68d166f 33348 lvm2_2.03.01-2.debian.tar.xz
 f01b99001f1c0c0ed9b2c90605910ae56a64631c 4015 lvm2_2.03.01-2_source.buildinfo
Checksums-Sha256:
 40ceaa258648f541cbb91791c28f2d166b4ea47663d4e18556b6cbb9a320721e 2636 
lvm2_2.03.01-2.dsc
 21c6066e5ae062ac539c9a83bd3e2ded1e4ae11a804105d821bda40829693eea 33348 
lvm2_2.03.01-2.debian.tar.xz
 956da537bd046eb674925165f0df74bf4f885861dcbf7308a93c3d1c15e6a1e5 4015 
lvm2_2.03.01-2_source.buildinfo
Files:
 b762c64ecda929b74fa6953bc7b33119 2636 admin optional lvm2_2.03.01-2.dsc
 698c8fbb40861bede1d61e004d086b84 33348 admin optional 
lvm2_2.03.01-2.debian.tar.xz
 20e9f56355cb019bab3cd5eb55c26d4f 4015 admin optional 
lvm2_2.03.01-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEER3HMN63jdS1rqjxLbZOIhYpp/lEFAlwdOiQACgkQbZOIhYpp
/lFsBggAw1NhzClXaPk8vEt/0wW7Et55KItNVPYKBpd6WgtcbhEPjNUFvrKp2oGk
9KMNNw6FkPlA8JsPjgs7ekk2f5uCSENWT7iG0Hd7Ene0J6haEPWJt/OON1TKpYIY
CM/X7dAZw+7feVdgIrFuFcT4Q025A0l5acmUhBruWyB7aIL55tavKWN2p6iSgjqM
9ju8/VLRHyPoxxUbhFHdkq3F5BeHjByqLXgSDoNcTmLlY6hLTMDqpwBrmlRNlQsI
bwfU8ZzVQYIUcapP2bLX0j3gqBiEssl9xU18P8DwjVGCJ3w/roKSsn3zxitCoG7J
V+HLjud1tpIb0Rj7NnOdhZXmzBTbFw==
=zs/s
-END PGP SIGNATURE End Message ---

Processed: Bug #908430 in salt marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #908430 [salt-doc] salt-doc depends on libjs-twitter-bootstrap that will 
not be in buster
Added tag(s) pending.

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

Bug#858928: marked as done (httest: Please migrate to openssl1.1 in buster)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 19:04:51 +
with message-id 
and subject line Bug#858928: fixed in httest 2.4.23-1
has caused the Debian Bug report #858928,
regarding httest: Please migrate to openssl1.1 in buster
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.)


-- 
858928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: httest
Version: 2.4.8-1.1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/httest_2.4.8-1.1_amd64-20160529-1428

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: httest
Source-Version: 2.4.23-1

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

Debian distribution maintenance software
pp.
Eva Ramon Salinas  (supplier of updated httest 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, 10 Dec 2018 09:14:00 +0200
Source: httest
Binary: httest
Architecture: source amd64
Version: 2.4.23-1
Distribution: unstable
Urgency: medium
Maintainer: Eva Ramon Salinas 
Changed-By: Eva Ramon Salinas 
Description:
 httest - HTTP test tool
Closes: 858928
Changes:
 httest (2.4.23-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #858928)
   * Minimal debian/rules with new debhelper
   * Patches review and update
   * Package source uploaded to salsa.debian.org
Checksums-Sha1:
 043e1168c53675332388e27c1c0017b9b8f74215 1924 httest_2.4.23-1.dsc
 fc7cb34af08e4acf0251b6b38d59672a9547021c 570604 httest_2.4.23.orig.tar.gz
 ac32afbb50812eac56e854888d4d8f90c9d041c7 3712 httest_2.4.23-1.debian.tar.xz
 a22aea81a6e05aacb6029173fbadbe927d7dc1d9 521452 
httest-dbgsym_2.4.23-1_amd64.deb
 78fb2976a558f4ec47063d4eef594f245e1fb954 6825 httest_2.4.23-1_amd64.buildinfo
 deba29032a0ff9e623095d0a37dd5594dad19b39 138732 httest_2.4.23-1_amd64.deb
Checksums-Sha256:
 0d6e36b471b0e868ae84333463d809651aad01b1ba123c51c4801bdb5f27552b 1924 
httest_2.4.23-1.dsc
 91906cc7191b5f1b71500fb13d5822ce3b6c9c702c85234e2f5ac2abc7f4ab12 570604 
httest_2.4.23.orig.tar.gz
 23936da16dafced47ffe4194e7019d61a4bccd4ee02ea73df16ceb6a96a5e7d0 3712 
httest_2.4.23-1.debian.tar.xz
 ae13c182b102f17e3bae353038303ee7db089a7efb05ea6e130bc844a4b11c16 521452 
httest-dbgsym_2.4.23-1_amd64.deb
 1f8af372b996638bc6047158f5039a6ccb74d42aa966c6cb1091eb4bdfd561e6 6825 
httest_2.4.23-1_amd64.buildinfo
 2d7fa6f089ad31a6d72863f68895bea253fd2085ef665f9c41ee7efb129e8215 138732 
httest_2.4.23-1_amd64.deb
Files:
 082c030ca7464be0d7955737f7b0e393 1924 devel optional httest_2.4.23-1.dsc
 9826e5b58fe58797ce3e000a1c9bd559 570604 devel optional 
httest_2.4.23.orig.tar.gz
 250845e8fe6caa9568f702aee817a9ba 3712 devel optional 
httest_2.4.23-1.debian.tar.xz
 4b9340a6ca68a32c9ffa6686423528d8 521452 debug optional 
httest-dbgsym_2.4.23-1_amd64.deb
 47aa4cf65950701bd875a4ecf6e917ae 6825 devel optional 
httest_2.4.23-1_amd64.buildinfo
 b8c89596fb6f8fb6dca739ccd381021b 138732 devel optional 
httest_2.4.23-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEIQ4c0KajE4aRShRRCVPte61pocsFAlwdM7EACgkQCVPte61p
ocsMtRAArz3hZe0dKmA4TIqdBtzfofv7QbH3qm8PRqvyZKrP23j0FNKkZqE+PyXP
DTXrqO3icX+d+VYueR/lqQiqgn+8hOZ5RFcxvnBLlDclw4HD3EYH8idzQGAY1Art
H+epa7k5A9utBZ1ma1CEbkEpjUVd+fAUgougsPHuTVRRw4JEv7kxhlWDFkNyBD2y
i93cuwJJ1/x1j4w2k0qU042MVqmbUKfV6lBru/ETpINuXnF5+le+uxyyEr8o/K6J
PxMIqcWkKvmO0yWFmXFpCMI+daXCyj89wgcvqTs/7ShlwYABk9FF6qw/dJB67dWH

Bug#908430: Bug #908430 in salt marked as pending

[Benjamin Drung]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/salt-team/salt/commit/0a76d0da49b895f03ec059bcf1bc8b2a3a9a88cb


Upgrade to libjs-bootstrap version 3

src:twitter-bootstrap is a 6.5 year old version of Bootstrap which is orphaned
since 2013. "Current" packages are in the archive as src:twitter-bootstrap3.
So switch from libjs-twitter-bootstrap (from src:twitter-bootstrap) to
libjs-bootstrap (from src:twitter-bootstrap3).

Closes: #908430


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/908430

Bug#901462: marked as done (seabios: SeaBIOS fails to build from source on sid and testing)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 19:05:34 +
with message-id 
and subject line Bug#901462: fixed in seabios 1.12.0-1
has caused the Debian Bug report #901462,
regarding seabios: SeaBIOS fails to build from source on sid and 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.)


-- 
901462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901462
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: seabios
Version: 1.11.1-1
Severity: serious
Justification: Policy 4.15

Dear Maintainer,

SeaBIOS fails to build from source when building on sid and testing.

The error message is:

=
  Compiling IASL src/fw/q35-acpi-dsdt.hex
build/src/fw/q35-acpi-dsdt.dsl.i446: Method(CPEJ, 2, NotSerialized) {
Remark   2146 - Method Argument is never used ^  (Arg0)

build/src/fw/q35-acpi-dsdt.dsl.i446: Method(CPEJ, 2, NotSerialized) {
Remark   2146 - Method Argument is never used ^  (Arg1)

ASL Input: build/src/fw/q35-acpi-dsdt.dsl.i - 515 lines, 28284 bytes, 413 
keywords
AML Output:build/src/fw/q35-acpi-dsdt.aml - 7506 bytes, 239 named objects, 
174 executable opcodes
Listing File:  build/src/fw/q35-acpi-dsdt.lst - 259530 bytes
Hex Dump:  build/src/fw/q35-acpi-dsdt.hex - 70865 bytes

Compilation complete. 0 Errors, 0 Warnings, 2 Remarks, 445 Optimizations
  Compiling IASL src/fw/ssdt-misc.hex
build/src/fw/ssdt-misc.dsl.i  4: DefinitionBlock ("ssdt-misc.aml", "SSDT", 
0x01, "BXPC", "BXSSDTSUSP", 0x1)
Error6155 - 
  Invalid OEM Table ID ^  (Length cannot exceed 8 characters)

ASL Input: build/src/fw/ssdt-misc.dsl.i - 102 lines, 2567 bytes, 35 keywords
Listing File:  build/src/fw/ssdt-misc.lst - 8417 bytes
Hex Dump:  build/src/fw/ssdt-misc.hex - 4098 bytes
=

Older SeaBIOS releases are also failing. Workaround is to build the package 
using a stretch chroot.

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

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: seabios
Source-Version: 1.12.0-1

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

Debian distribution maintenance software
pp.
Michael Tokarev  (supplier of updated seabios 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, 21 Dec 2018 21:06:17 +0300
Source: seabios
Binary: seabios
Architecture: source all
Version: 1.12.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QEMU Team 
Changed-By: Michael Tokarev 
Description:
 seabios- Legacy BIOS implementation
Closes: 901462 901547
Changes:
 seabios (1.12.0-1) unstable; urgency=medium
 .
   * new upstream release
 Closes: #901462
   * do not move away .hex files, just remove them (Closes: #901547)
   * update d/watch to point to https://www.seabios.org/downloads/
   * d/rules: update bios build options (remove more stuff for 128k)
Checksums-Sha1:
 b2124c98aade7da66b9e88e04084ac3b3292e655 1647 seabios_1.12.0-1.dsc
 3f8ee5c7cb449483e0e5bde50889bc7e54c4b0d1 613542 seabios_1.12.0.orig.tar.gz
 d7884c414245f0ae66d1e2877ef4858842c28600 17780 seabios_1.12.0-1.debian.tar.xz
 57783361f9498e2d72d7939a8dd501d6bcd6eb62 136216 seabios_1.12.0-1_all.deb
 0cc73bfda3d5e4d9a1ca45ebba5ae7f498a0cab0 5374 seabios_1.12.0-1_amd64.buildinfo
Checksums-Sha256:
 89bd825807ee1a9237361943362b343920328cea4717000b6292ec4772a2e3c1 1647 
seabios_1.12.0-1.dsc
 df17b8e565e75c27897ceb82af853b7c568eba7911f3bd173f8a68c1b4bda74b 613542 
seabios_1.12.0.orig.tar.gz
 

Bug#915888: marked as done (pytest-pylint FTBFS with pytest 3.10.1-1)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 19:05:25 +
with message-id 
and subject line Bug#915888: fixed in pytest-pylint 0.13.0-1
has caused the Debian Bug report #915888,
regarding pytest-pylint FTBFS with pytest 3.10.1-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.)


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

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

...
=== FAILURES ===
__ test_basic __

testdir = 

def test_basic(testdir):
"""Verify basic pylint checks"""
testdir.makepyfile("""import sys""")
result = testdir.runpytest('--pylint')
assert 'Missing module docstring' in result.stdout.str()
assert 'Unused import sys' in result.stdout.str()
assert 'Final newline missing' in result.stdout.str()
>   assert 'passed' not in result.stdout.str()
E   AssertionError: assert 'passed' not in '= 
test session starts ==\nplatform linux2 -- Python 
2.7.15+, p...s.pytest.org/en/latest/warnings.html\n 1 
failed, 17 warnings in 0.67 seconds =\n'
E+  where '= test session starts 
==\nplatform linux2 -- Python 2.7.15+, 
p...s.pytest.org/en/latest/warnings.html\n 1 failed, 17 
warnings in 0.67 seconds =\n' = >()
E+where > = 
<_pytest.pytester.LineMatcher object at 0x7f45db0e9250>.str
E+  where <_pytest.pytester.LineMatcher object at 0x7f45db0e9250> = 
<_pytest.pytester.RunResult object at 0x7f45db0e91d0>.stdout

/build/1st/pytest-pylint-0.12.3/test_pytest_pylint.py:18: AssertionError
...
=== 1 failed, 3 passed, 25 warnings in 43.48 seconds ===
E: pybuild pybuild:338: test: plugin custom failed with: exit code=1: python2.7 
-m pytest -v -x --ignore debian
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
make[1]: *** [debian/rules:13: override_dh_auto_install] Error 25
--- End Message ---
--- Begin Message ---
Source: pytest-pylint
Source-Version: 0.13.0-1

We believe that the bug you reported is fixed in the latest version of
pytest-pylint, 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.
Ondřej Nový  (supplier of updated pytest-pylint 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, 21 Dec 2018 19:49:27 +0100
Source: pytest-pylint
Binary: python-pytest-pylint python3-pytest-pylint
Architecture: source
Version: 0.13.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Description:
 python-pytest-pylint - pytest plugin to check source code with pylint - Python 
2.x
 python3-pytest-pylint - pytest plugin to check source code with pylint - 
Python 3.x
Closes: 915888
Changes:
 pytest-pylint (0.13.0-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #915888)
   * Add python{,3}-pytest-runner into B-D
Checksums-Sha1:
 57044e002b6de22b2f8863964083ce2273defe8f 2514 pytest-pylint_0.13.0-1.dsc
 c97f28da764b68e63ead45fa7badb65f24dd99fc 7219 pytest-pylint_0.13.0.orig.tar.gz
 368d746ee329131904f4566c5cfb173bbeef0262 7456 
pytest-pylint_0.13.0-1.debian.tar.xz
 754ce175207d85a9786644004830345a114dfff7 8225 
pytest-pylint_0.13.0-1_amd64.buildinfo
Checksums-Sha256:
 4eb0523c00b6b368b3576e36d975388134a78c81432f8e21b1b28524bbe85552 2514 
pytest-pylint_0.13.0-1.dsc
 b7f1d92bc771ad53e82dd286ce6a875270f7a410759ccc9d5e147ae433ca21b0 7219 
pytest-pylint_0.13.0.orig.tar.gz
 1889469272709a7f4d15048e31ff93c5385e365aac3331811a3939de41b59766 7456 
pytest-pylint_0.13.0-1.debian.tar.xz
 d50c4f98b17c2337dd834b16f3b7265de07c679c076a61434a65bdc6d233c912 8225 

Processed: tagging 897758

[Debian Bug Tracking System]

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

> tags 897758 + ftbfs
Bug #897758 [src:ggcov] ggcov: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#915888: Bug #915888 in pytest-pylint marked as pending

[Ondřej Nový]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/pytest-pylint/commit/826f494a4ee451d20f8bb961fef02bf013d92ae3


New upstream release (Closes: #915888)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/915888

Processed: Bug #915888 in pytest-pylint marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #915888 [src:pytest-pylint] pytest-pylint FTBFS with pytest 3.10.1-1
Added tag(s) pending.

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

Processed: block 912465 with 915464 ...

[Debian Bug Tracking System]

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

> block 912465 with 915464
Bug #912465 [release.debian.org] RM: mozvoikko/2.2-0.1
912465 was not blocked by any bugs.
912465 was not blocking any bugs.
Added blocking bug(s) of 912465: 915464
> retitle 915464 RM: mozvoikko -- RoQA; incompatible with newer firefox-esr 
> versions
Bug #915464 {Done: Jonas Smedegaard } [src:debian-parl] Depends 
on broken Firefox addons
Changed Bug title to 'RM: mozvoikko -- RoQA; incompatible with newer 
firefox-esr versions' from 'Depends on broken Firefox addons'.
> thanks
Stopping processing here.

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

Processed: tagging 917024

[Debian Bug Tracking System]

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

> tags 917024 + upstream
Bug #917024 [src:zoneminder] CVE-2018-1000832 CVE-2018-1000833
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: found 917024 in 1.32.2-1

[Debian Bug Tracking System]

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

> found 917024 1.32.2-1
Bug #917024 [src:zoneminder] CVE-2018-1000832 CVE-2018-1000833
Marked as found in versions zoneminder/1.32.2-1.
> thanks
Stopping processing here.

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

Bug#865851: marked as done (drf-extensions FTBFS with Django 1.11)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 18:21:32 +
with message-id 
and subject line Bug#865851: fixed in drf-extensions 0.4.0-1.1
has caused the Debian Bug report #865851,
regarding drf-extensions FTBFS with Django 1.11
to be marked as done.

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

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


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

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/drf-extensions-0.3.1'
dh_auto_test -- --system=custom --test-args="PYTHONPATH='.:tests_app' 
{interpreter} /usr/bin/django-admin test --settings=settings tests_app"
I: pybuild base:184: PYTHONPATH='.:tests_app' python3.5 /usr/bin/django-admin 
test --settings=settings tests_app
nosetests tests_app --processes=16 --process-timeout=100 --nocapture 
--verbosity=1
Creating test database for alias 'default'...
..EEE..FFF...
==
ERROR: Failure: ImportError (cannot import name 'flatatt')
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest
raise self.exc_val.with_traceback(self.tb)
  File "/usr/lib/python3/dist-packages/nose/loader.py", line 418, in 
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File "/usr/lib/python3.5/imp.py", line 234, in load_module
return load_source(name, filename, file)
  File "/usr/lib/python3.5/imp.py", line 172, in load_source
module = _load(spec)
  File "", line 693, in _load
  File "", line 673, in _load_unlocked
  File "", line 697, in exec_module
  File "", line 222, in _call_with_frames_removed
  File 
"/build/1st/drf-extensions-0.3.1/tests_app/tests/functional/mixins/list_destroy_model_mixin/urls.py",
 line 4, in 
from .views import CommentViewSet, CommentViewSetWithPermissions
  File 
"/build/1st/drf-extensions-0.3.1/tests_app/tests/functional/mixins/list_destroy_model_mixin/views.py",
 line 2, in 
import django_filters
  File "/usr/lib/python3/dist-packages/django_filters/__init__.py", line 3, in 

from .filterset import FilterSet
  File "/usr/lib/python3/dist-packages/django_filters/filterset.py", line 19, 
in 
from .filters import (Filter, CharFilter, BooleanFilter, BaseInFilter, 
BaseRangeFilter,
  File "/usr/lib/python3/dist-packages/django_filters/filters.py", line 16, in 

from .fields import (
  File "/usr/lib/python3/dist-packages/django_filters/fields.py", line 14, in 

from .widgets import RangeWidget, LookupTypeWidget, CSVWidget
  File "/usr/lib/python3/dist-packages/django_filters/widgets.py", line 13, in 

from django.forms.widgets import flatatt
ImportError: cannot import name 'flatatt'
...
FAILED (errors=27, failures=7)
Destroying test database for alias 'default'...
E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: 
PYTHONPATH='.:tests_app' python3.5 /usr/bin/django-admin test 
--settings=settings tests_app
dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.5 
--system=custom --test-args=PYTHONPATH='.:tests_app' {interpreter} 
/usr/bin/django-admin test --settings=settings tests_app returned exit code 13
debian/rules:16: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
--- End Message ---
--- Begin Message ---
Source: drf-extensions
Source-Version: 0.4.0-1.1

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

Debian distribution maintenance software
pp.
Wookey  (supplier of 

Bug#916944: marked as done (pytest FTBFS: TestRaises.test_raises_exception_looks_iterable fails)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 18:21:43 +
with message-id 
and subject line Bug#916944: fixed in pytest 3.10.1-2
has caused the Debian Bug report #916944,
regarding pytest FTBFS: TestRaises.test_raises_exception_looks_iterable fails
to be marked as done.

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

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


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

Some recent change in unstable makes pytest FTBFS:

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

...
=== FAILURES ===
___ TestRaises.test_raises_exception_looks_iterable 

self = 

def test_raises_exception_looks_iterable(self):
from six import add_metaclass

class Meta(type(object)):
def __getitem__(self, item):
return 1 / 0

def __len__(self):
return 1

@add_metaclass(Meta)
class ClassLooksIterableException(Exception):
pass

with pytest.raises(
Failed, match="DID NOT RAISE "
):
>   pytest.raises(ClassLooksIterableException, lambda: None)

/build/1st/pytest-3.10.1/testing/python/raises.py:174: 
...
 1 failed, 1986 passed, 47 skipped, 1 deselected, 10 xfailed in 268.71 seconds =
E: pybuild pybuild:338: test: plugin custom failed with: exit code=1: cd 
/build/1st/pytest-3.10.1/debian/tmp/test-working-directory && python3.7 -m 
pytest --lsof -rfsxX --ignore=/build/1st/pytest-3.10.1/testing/freeze 
--ignore=/build/1st/pytest-3.10.1/testing/test_entry_points.py 
--ignore=/build/1st/pytest-3.10.1/testing/test_pdb.py 
--ignore=/build/1st/pytest-3.10.1/testing/test_mark.py 
--ignore=/build/1st/pytest-3.10.1/testing/test_terminal.py -k 'not 
test_trial_pdb' /build/1st/pytest-3.10.1/testing
dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.7 
--system=custom returned exit code 13
make[1]: *** [debian/rules:47: override_dh_auto_test] Error 25
--- End Message ---
--- Begin Message ---
Source: pytest
Source-Version: 3.10.1-2

We believe that the bug you reported is fixed in the latest version of
pytest, 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.
Ondřej Nový  (supplier of updated pytest 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, 21 Dec 2018 18:49:26 +0100
Source: pytest
Binary: pypy-pytest python-pytest python-pytest-doc python3-pytest
Architecture: source
Version: 3.10.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Ondřej Nový 
Description:
 pypy-pytest - Simple, powerful testing in PyPy
 python-pytest - Simple, powerful testing in Python
 python-pytest-doc - Simple, powerful testing in Python - Documentation
 python3-pytest - Simple, powerful testing in Python3
Closes: 916944
Changes:
 pytest (3.10.1-2) unstable; urgency=medium
 .
   * Fix test_raises_exception_looks_iterable test with newer Python 3.7
 (Closes: #916944)
Checksums-Sha1:
 d42e747562c12115013774d48bd9c51d9424a2cd 3194 pytest_3.10.1-2.dsc
 80dd17d6a7867ae2ef991af1abdcd82b571f52ba 11024 pytest_3.10.1-2.debian.tar.xz
 7e6d46aea6a4b85a50557c4333d1046046e3df22 10595 pytest_3.10.1-2_amd64.buildinfo
Checksums-Sha256:
 d8e8c0fed34bb8e4404c1e4351add3ce4d1c5b195d0f8664c8d32e9c3873abb1 3194 
pytest_3.10.1-2.dsc
 47744b3c9b0b2de054cb360755a65ec6bf542bf1183e5dfb43e024b052f7871f 11024 
pytest_3.10.1-2.debian.tar.xz
 208f6910a53fdc3f2b51a7b2d7e1780fbfd7ce0f21a9d666aeef933c22e38ae5 10595 
pytest_3.10.1-2_amd64.buildinfo
Files:
 cfaf024cb8d12a0e854f8d743ef20b01 3194 python optional pytest_3.10.1-2.dsc
 32ac989a77ad79f143ce29a5109bae0f 11024 python optional 
pytest_3.10.1-2.debian.tar.xz
 1e33765cf85e1794e65569902509eb74 10595 python optional 
pytest_3.10.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#915731: marked as done (binutils-avr still uses GCC 7)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 18:19:50 +
with message-id 
and subject line Bug#915731: fixed in binutils-avr 2.26.20160125+Atmel3.6.1-4
has caused the Debian Bug report #915731,
regarding binutils-avr still uses GCC 7
to be marked as done.

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

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


-- 
915731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:binutils-avr
Version: 2.26.20160125+Atmel3.6.1-3.1
Severity: serious
Tags: sid buster

Please use the default GCC for the package so that we can remove GCC 7 for the
buster release.
--- End Message ---
--- Begin Message ---
Source: binutils-avr
Source-Version: 2.26.20160125+Atmel3.6.1-4

We believe that the bug you reported is fixed in the latest version of
binutils-avr, 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.
Hakan Ardo  (supplier of updated binutils-avr 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, 14 Dec 2018 11:05:22 +0100
Source: binutils-avr
Binary: binutils-avr
Architecture: source amd64
Version: 2.26.20160125+Atmel3.6.1-4
Distribution: unstable
Urgency: medium
Maintainer: Hakan Ardo 
Changed-By: Hakan Ardo 
Description:
 binutils-avr - Binary utilities supporting Atmel's AVR targets
Closes: 915731
Changes:
 binutils-avr (2.26.20160125+Atmel3.6.1-4) unstable; urgency=medium
 .
   * Now builds with gcc 8 (closes: #915731)
Checksums-Sha1:
 9279260fe25cf6f40de8e47d88f0f984948b999a 2093 
binutils-avr_2.26.20160125+Atmel3.6.1-4.dsc
 0afd20a40a850a94b42170519cf9d28e3ceaedd6 50190869 
binutils-avr_2.26.20160125+Atmel3.6.1.orig.tar.gz
 52757198cb6eae92c17609a0c1e4795befc84905 776168 
binutils-avr_2.26.20160125+Atmel3.6.1-4.diff.gz
 eb1a58e59529eddf81dd686e2fac4b312eb1be13 22392228 
binutils-avr-dbgsym_2.26.20160125+Atmel3.6.1-4_amd64.deb
 a98479738388303f7f84f1789a8aad9cab11b943 6774 
binutils-avr_2.26.20160125+Atmel3.6.1-4_amd64.buildinfo
 04946375a3d6cb1799842d4ee7b0500cab85c234 1463704 
binutils-avr_2.26.20160125+Atmel3.6.1-4_amd64.deb
Checksums-Sha256:
 222782d58ad4eb1304dcb5bbe155be064e11abfd65664ecc86663d7bfe5f61c0 2093 
binutils-avr_2.26.20160125+Atmel3.6.1-4.dsc
 d6a39c99a1cd91c709313e284dc52d9231fad3a3fbb96173999295c55bffed49 50190869 
binutils-avr_2.26.20160125+Atmel3.6.1.orig.tar.gz
 45bfea674cb9742d2969d3e430dbfd78efc1811e5a97009fa3d3aeadbbed2bbc 776168 
binutils-avr_2.26.20160125+Atmel3.6.1-4.diff.gz
 5c996f00ac31f503b61ac950f5bf638c29a4c53a861923865f812c87a796894e 22392228 
binutils-avr-dbgsym_2.26.20160125+Atmel3.6.1-4_amd64.deb
 b0c44833c5e128514d5043840376308708ddb166e21f0553d2c6b77412caa448 6774 
binutils-avr_2.26.20160125+Atmel3.6.1-4_amd64.buildinfo
 9d2e4b0c943bc599ab48aebc9ad690b03e1774b2e1f0a8f31f05526a4f726915 1463704 
binutils-avr_2.26.20160125+Atmel3.6.1-4_amd64.deb
Files:
 aeece37e750b3ce46cc0637c0a920e00 2093 devel optional 
binutils-avr_2.26.20160125+Atmel3.6.1-4.dsc
 de13cd6466ca841d4606f26bec4d0c33 50190869 devel optional 
binutils-avr_2.26.20160125+Atmel3.6.1.orig.tar.gz
 8c6df6f4a98ae96b51884e93734bf50e 776168 devel optional 
binutils-avr_2.26.20160125+Atmel3.6.1-4.diff.gz
 e5b7377bf83196f96eb35354f545e8b6 22392228 debug optional 
binutils-avr-dbgsym_2.26.20160125+Atmel3.6.1-4_amd64.deb
 7f4a6c88ce5c875a387bf3eeb7a7d78c 6774 devel optional 
binutils-avr_2.26.20160125+Atmel3.6.1-4_amd64.buildinfo
 3002b99a5d0740fc6b51fb9ab3d1f088 1463704 devel optional 
binutils-avr_2.26.20160125+Atmel3.6.1-4_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEiBxmoJbhJJA77soc6iX5+wapp9EFAlwZSFsACgkQ6iX5+wap
p9EOJBAAsOO/kUDU4wjGhATvn5o4J7F8gcyTXhLDuON+lBPVZPI1iAXjRDF5Fhan
gcaPa48N0YwToOhUObCy3tHcVhv9K+Y/ki4AktAL0n3thXDrszl+OiKvNWfKQ9FR
/mmlqCxYZ6XbSTy/Hb7mInXlRB3GJtKLEivFbDkBO6C1KrQOoqtVz9VGP06Rl439
4HwVwZocb3JHdLwpYu0IToJW1aKeHsrXFOHPXkBwyNMtobq2aNZ3ZV4elgWkRbkn
O/GkGHaglo8ZUKbDufqlVU35XPyd7r7mVSnn2fs/i4LV1wPEl9fkzoi1qCdyzsLJ
dMbsGXAxEni+T+2iprsdRp8i3p6TBq7B/T+9zC+REBWuug5SV+u7jCOzaYeS0JRH
HSmh4OY0TPvguFSr20wQOHsFAdb0L2NfNkWtKySV8AkejSZBG5sasArBCMXaW/QM

Processed: tagging 908405, block 908405 with 915464

[Debian Bug Tracking System]

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

> tags 908405 + moreinfo
Bug #908405 [release.debian.org] RM: y-u-no-validate -- RoQA; incompatible with 
newer firefox-esr versions
Added tag(s) moreinfo.
> block 908405 with 915464
Bug #908405 [release.debian.org] RM: y-u-no-validate -- RoQA; incompatible with 
newer firefox-esr versions
908405 was not blocked by any bugs.
908405 was not blocking any bugs.
Added blocking bug(s) of 908405: 915464
> thanks
Stopping processing here.

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

Processed: Bug #916944 in pytest marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #916944 [src:pytest] pytest FTBFS: 
TestRaises.test_raises_exception_looks_iterable fails
Added tag(s) pending.

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

Bug#916944: Bug #916944 in pytest marked as pending

[Ondřej Nový]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/pytest/commit/83b8efdee7fe7b4e1185d68a5c091b919271c100


Fix test_raises_exception_looks_iterable test with newer Python 3.7 (Closes: 
#916944)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/916944

Bug#916709: marked as done (fritzing: FTBFS when built with dpkg-buildpackage -A)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 17:34:57 +
with message-id 
and subject line Bug#916709: fixed in fritzing 0.9.3b+dfsg-8
has caused the Debian Bug report #916709,
regarding fritzing: FTBFS when built with dpkg-buildpackage -A
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.)


-- 
916709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fritzing
Version: 0.9.3b+dfsg-7
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with dpkg-buildpackage -A but it failed:


[...]

make[2]: Entering directory '/<>/fritzing-0.9.3b+dfsg'
make[2]: Nothing to be done for 'first'.
make[2]: Leaving directory '/<>/fritzing-0.9.3b+dfsg'
make[1]: Leaving directory '/<>/fritzing-0.9.3b+dfsg'
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep
   dh_testroot -i
   dh_prep -i
   dh_auto_install -i
make V=1 -j1 install 
DESTDIR=/<>/fritzing-0.9.3b\+dfsg/debian/tmp AM_UPDATE_INFO_DIR=no 
INSTALL_ROOT=/<>/fritzing-0.9.3b\+dfsg/debian/tmp
make[1]: Entering directory '/<>/fritzing-0.9.3b+dfsg'
make -f Makefile.Release install
make[2]: Entering directory '/<>/fritzing-0.9.3b+dfsg'
/usr/lib/qt5/bin/qmake -install qinstall -exe Fritzing 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/bin/Fritzing
: /<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/bin/Fritzing
/usr/lib/qt5/bin/qmake -install qinstall 
/<>/fritzing-0.9.3b+dfsg/fritzing.desktop 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/share/applications/fritzing.desktop
/usr/lib/qt5/bin/qmake -install qinstall 
/<>/fritzing-0.9.3b+dfsg/Fritzing.1 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/share/man/man1/Fritzing.1
install -D -m 0644 
/<>/fritzing-0.9.3b+dfsg/resources/images/fritzing_icon.png 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/share/icons/fritzing.png
/usr/lib/qt5/bin/qmake -install qinstall 
/<>/fritzing-0.9.3b+dfsg/sketches 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/share/fritzing/sketches
find /<>/fritzing-0.9.3b+dfsg/translations -name *.qm -size +128c 
-exec cp -pr {} 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/share/fritzing/translations \;
/usr/lib/qt5/bin/qmake -install qinstall 
/<>/fritzing-0.9.3b+dfsg/translations/syntax/arduino.xml 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/share/fritzing/translations/syntax/arduino.xml
/usr/lib/qt5/bin/qmake -install qinstall 
/<>/fritzing-0.9.3b+dfsg/translations/syntax/picaxe.xml 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/share/fritzing/translations/syntax/picaxe.xml
/usr/lib/qt5/bin/qmake -install qinstall 
/<>/fritzing-0.9.3b+dfsg/translations/syntax/styles.xml 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/share/fritzing/translations/syntax/styles.xml
/usr/lib/qt5/bin/qmake -install qinstall 
/<>/fritzing-0.9.3b+dfsg/help 
/<>/fritzing-0.9.3b+dfsg/debian/tmp/usr/share/fritzing/help
make[2]: Leaving directory '/<>/fritzing-0.9.3b+dfsg'
make[1]: Leaving directory '/<>/fritzing-0.9.3b+dfsg'
   debian/rules override_dh_install
make[1]: Entering directory '/<>/fritzing-0.9.3b+dfsg'
dh_install
convert 
/<>/fritzing-0.9.3b+dfsg/debian/fritzing/usr/share/pixmaps/fritzing_icon.png
 -resize 32x32 \

/<>/fritzing-0.9.3b+dfsg/debian/fritzing/usr/share/pixmaps/fritzing_icon.xpm
convert-im6.q16: unable to open image 
`/<>/fritzing-0.9.3b+dfsg/debian/fritzing/usr/share/pixmaps/fritzing_icon.png':
 No such file or directory @ error/blob.c/OpenBlob/2874.
convert-im6.q16: no images defined 
`/<>/fritzing-0.9.3b+dfsg/debian/fritzing/usr/share/pixmaps/fritzing_icon.xpm'
 @ error/convert.c/ConvertImageCommand/3258.
make[1]: *** [debian/rules:23: override_dh_install] Error 1
make[1]: Leaving directory '/<>/fritzing-0.9.3b+dfsg'
make: *** [debian/rules:12: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


Hint: Try splitting override_dh_install into override_dh_install-arch and
override_dh_install-indep.

While we are at it, please consider uploading in source-only form
(dpkg-buildpackage -S) so that this kind of bugs never propagate to
testing.

Thanks.
--- End Message ---
--- Begin Message ---
Source: fritzing
Source-Version: 0.9.3b+dfsg-8

We believe that the bug you reported is fixed in the latest version of
fritzing, 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 

Bug#911768: pinentry-gnome3 fails to open a window with 'No Gcr System Prompter available, falling back to curses'

[Daniel Kahn Gillmor]

Control: affects 911768 - gpg-agent
Control: affects 911768 + gcr

On Fri 2018-12-21 07:28:22 -0500, Theodore Y. Ts'o wrote:
> On Thu, Dec 20, 2018 at 03:17:03PM -0500, Daniel Kahn Gillmor wrote:
>> 
>> I wonder whether we can rule out any interaction with gpg-agent itself
>> -- does "echo getpin | pinentry-gnome3" itself fall back to curses on
>> your system when nfs-kernel-server is installed?
>
> I can confirm that that I did this experiment before I uninstalled
> nfs-kernel-server --- and it fell back to curses.

thanks!  I think that takes gpg-agent out of the picture (a nice
simplification in terms of debugging) but also implicates gcr itself, so
i'm adjusting the "affects" tag.

> The next experiment to do would be to reinstall nfs-kernel-server and
> reboot --- and see if it falls back to curses again.

Please report back if you do that experiment!  thanks for following up,
Ted.

   --dkg


signature.asc
Description: PGP signature

Processed: Re: Bug#911768: pinentry-gnome3 fails to open a window with 'No Gcr System Prompter available, falling back to curses'

[Debian Bug Tracking System]

Processing control commands:

> affects 911768 - gpg-agent
Bug #911768 [nfs-kernel-server] nfs-kernel-server causes dbus communications to 
fail for gpg-agent and pinentry-gnome3
Removed indication that 911768 affects gpg-agent
> affects 911768 + gcr
Bug #911768 [nfs-kernel-server] nfs-kernel-server causes dbus communications to 
fail for gpg-agent and pinentry-gnome3
Added indication that 911768 affects gcr

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

Bug#916963: marked as done (libarchive: CVE-2018-1000878)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 16:36:23 +
with message-id 
and subject line Bug#916963: fixed in libarchive 3.3.3-2
has caused the Debian Bug report #916963,
regarding libarchive: CVE-2018-1000878
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.)


-- 
916963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libarchive
Version: 3.3.3-1
Severity: important
Tags: security upstream
Control: found -1 3.2.2-2

Hi,

The following vulnerability was published for libarchive.

CVE-2018-1000878[0]:
| libarchive version commit 416694915449219d505531b1096384f3237dd6cc
| onwards (release v3.1.0 onwards) contains a CWE-416: Use After Free
| vulnerability in RAR decoder -
| libarchive/archive_read_support_format_rar.c that can result in
| Crash/DoS - it is unknown if RCE is possible. This attack appear to be
| exploitable via the victim must open a specially crafted RAR archive.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-1000878
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000878
[1] https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1794909
[2] https://github.com/libarchive/libarchive/pull/1105
[3] 
https://github.com/libarchive/libarchive/pull/1105/commits/bfcfe6f04ed20db2504db8a254d1f40a1d84eb28

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libarchive
Source-Version: 3.3.3-2

We believe that the bug you reported is fixed in the latest version of
libarchive, 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.
Peter Pentchev  (supplier of updated libarchive 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, 21 Dec 2018 18:01:29 +0200
Source: libarchive
Binary: libarchive-dev libarchive13 libarchive-tools bsdtar bsdcpio
Architecture: source
Version: 3.3.3-2
Distribution: unstable
Urgency: medium
Maintainer: Peter Pentchev 
Changed-By: Peter Pentchev 
Description:
 bsdcpio- transitional dummy package for moving bsdcpio to libarchive-tools
 bsdtar - transitional dummy package for moving bsdtar to libarchive-tools
 libarchive-dev - Multi-format archive and compression library (development 
files)
 libarchive-tools - FreeBSD implementations of 'tar' and 'cpio' and other 
archive too
 libarchive13 - Multi-format archive and compression library (shared library)
Closes: 916960 916962 916963 916964
Changes:
 libarchive (3.3.3-2) unstable; urgency=medium
 .
   * Add Daniel Axtens's security and reliability patches:
 - CVE-2018-1000877.patch: Closes: #916964
 - CVE-2018-1000878.patch: Closes: #916963
 - CVE-2018-1000879.patch: Closes: #916962
 - CVE-2018-1000880.patch: Closes: #916960
 - all merged upstream in https://github.com/libarchive/libarchive/pull/1105
 Thanks to Salvatore Bonaccorso for filing the Debian bugs!
Checksums-Sha1:
 1458c3bed4dbfdc5f0ac7a1376287f1e96f576ad 2356 libarchive_3.3.3-2.dsc
 2e2de7d85ed3d69e25697624336e9c38b92e7694 18460 libarchive_3.3.3-2.debian.tar.xz
 bed2c5d4bf0c174a92942bb4404f5968648a3c0e 7617 
libarchive_3.3.3-2_amd64.buildinfo
Checksums-Sha256:
 8bedc724c6d7250c93e112b35bd7e2a2e92e03bd74b64bfe495e384caf9f5751 2356 
libarchive_3.3.3-2.dsc
 5f9c11e19c428a3b98657b3643d04802e728bbc48f333fee3bfc41f441c140af 18460 
libarchive_3.3.3-2.debian.tar.xz
 463cf49e06e07440293a27dd3204b911dcb55369f1e5fda3bc23f736e8c87019 7617 
libarchive_3.3.3-2_amd64.buildinfo
Files:
 ed565ad2f49ee60059bb43c208c915a6 2356 libs optional libarchive_3.3.3-2.dsc
 f27f3687f7ea2c31299594df586b05f2 18460 libs optional 
libarchive_3.3.3-2.debian.tar.xz
 7c5e181637fc8d4ae6d3e224f498e93f 7617 libs optional 
libarchive_3.3.3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAlwdD4sACgkQZR7vsCUn
3xO7SxAA0MeHAu6PEriRFiXG6+7OMv4HJcckJgjtndqX5D0BfdDk5wcdiJEJ2KzU

Bug#917024: CVE-2018-1000832 CVE-2018-1000833

[Moritz Muehlenhoff]

Source: zoneminder
Severity: grave
Tags: security

Please see
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000832
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000833

Cheers,
Moritz

Bug#916279: marked as done (qemu-system-common: Overwrite /usr/share/doc-base/qemu-system-doc without declaring replacement)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 15:51:14 +
with message-id 
and subject line Bug#916279: fixed in qemu 1:3.1+dfsg-2
has caused the Debian Bug report #916279,
regarding qemu-system-common: Overwrite /usr/share/doc-base/qemu-system-doc 
without declaring replacement
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.)


-- 
916279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916279
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qemu-system-common
Version: 1:3.1+dfsg-1
Severity: serious

(Sorry for non-English text, but the output should be self-explainable).

/usr/share/doc-base/qemu-system-doc was previously provided by
qemu-system-data 1:2.12+dfsg-3 but now it is provided by qemu-system-common.

准备解压 .../15-qemu-system-common_1%3a3.1+dfsg-1_amd64.deb  ...
正在解压 qemu-system-common (1:3.1+dfsg-1) 并覆盖 (1:2.12+dfsg-3+b1) ...
dpkg: 处理归档 
/tmp/apt-dpkg-install-FyVVBs/15-qemu-system-common_1%3a3.1+dfsg-1_amd64.deb
(--unpack)时出错：
 正试图覆盖 /usr/share/doc-base/qemu-system-doc，它同时被包含于软件包 qemu-system-data
1:2.12+dfsg-3
dpkg-deb: 错误: 粘贴 子进程被信号(断开的管道) 终止了
在处理时有错误发生：
 /tmp/apt-dpkg-install-FyVVBs/15-qemu-system-common_1%3a3.1+dfsg-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

--
Thanks,
Boyuan Yang
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:3.1+dfsg-2

We believe that the bug you reported is fixed in the latest version of
qemu, 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.
Michael Tokarev  (supplier of updated qemu 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, 21 Dec 2018 16:51:39 +0300
Source: qemu
Binary: qemu qemu-system qemu-block-extra qemu-system-data qemu-system-common 
qemu-system-gui qemu-system-misc qemu-system-arm qemu-system-mips 
qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-user qemu-user-static 
qemu-user-binfmt qemu-utils qemu-guest-agent qemu-kvm
Architecture: source
Version: 1:3.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QEMU Team 
Changed-By: Michael Tokarev 
Description:
 qemu   - fast processor emulator, dummy package
 qemu-block-extra - extra block backend modules for qemu-system and qemu-utils
 qemu-guest-agent - Guest-side qemu-system agent
 qemu-kvm   - QEMU Full virtualization on x86 hardware
 qemu-system - QEMU full system emulation binaries
 qemu-system-arm - QEMU full system emulation binaries (arm)
 qemu-system-common - QEMU full system emulation binaries (common files)
 qemu-system-data - QEMU full system emulation (data files)
 qemu-system-gui - QEMU full system emulation binaries (user interface and 
audio sup
 qemu-system-mips - QEMU full system emulation binaries (mips)
 qemu-system-misc - QEMU full system emulation binaries (miscellaneous)
 qemu-system-ppc - QEMU full system emulation binaries (ppc)
 qemu-system-sparc - QEMU full system emulation binaries (sparc)
 qemu-system-x86 - QEMU full system emulation binaries (x86)
 qemu-user  - QEMU user mode emulation binaries
 qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user
 qemu-user-static - QEMU user mode emulation binaries (static version)
 qemu-utils - QEMU utilities
Closes: 684909 849798 903562 912655 916278 916279 916397 916625 916674 917007
Changes:
 qemu (1:3.1+dfsg-2) unstable; urgency=medium
 .
   * d/rules: split arch and indep builds
   * enable s390x cross-compiler and build s390-ccw.img (Closes: #684909)
   * build x86 optionrom in qemu-system-data (was in seabios/debian/)
   * qemu-system-data: Multi-Arch: allowed=>foreign (Closes: #903562)
   * fix Replaces: version for qemu-system-common (Closes: #916279)
   * add simple udev rules file for systemd guest agent (Closes: #916674)
   * usb-mtp-use-O_NOFOLLOW-and-O_CLOEXEC-CVE-2018-16872.patch
 Race condition in usb_mtp implementation (Closes: #916397)
   * 
bt-use-size_t-type-for-length-parameters-instead-of-int-CVE-2018-19665.patch
 Memory corruption in bluetooth subsystem (Closes: #916278)
   * hw_usb-fix-mistaken-de-initialization-of-CCID-state.patch (Closes: #917007)
   

Bug#916674: marked as done (qemu-guest-agent not started on boot with systemd)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 15:51:14 +
with message-id 
and subject line Bug#916674: fixed in qemu 1:3.1+dfsg-2
has caused the Debian Bug report #916674,
regarding qemu-guest-agent not started on boot with systemd
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.)


-- 
916674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qemu-guest-agent
Version: 1:3.1+dfsg-1
Severity: serious

Hello,

qemu-guest-agent now ships a systemd .service which is good, but it's
not being started on boot.

In Fedora/RHEL they are shipping the following file:
https://src.fedoraproject.org/cgit/rpms/qemu.git/tree/99-qemu-guest-agent.rules

That allows the daemon to be started if the device is present (or
appears when the machine has already booted).

Note that their .service file is a bit different:
https://src.fedoraproject.org/cgit/rpms/qemu.git/tree/qemu-guest-agent.service

I think that the udev rule should be enough though.

Also note that the path in the ExecStart is not correct either as the
qemu-ga daemon is installed in /usr/sbin/ and not /usr/bin

Kind regards,

Laurent Bigonville

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

Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages qemu-guest-agent depends on:
ii  libc6 2.28-3
ii  libgcc1   1:8.2.0-12
ii  libglib2.0-0  2.58.1-2
ii  libudev1  239-15
ii  lsb-base  10.2018112800

qemu-guest-agent recommends no packages.

qemu-guest-agent suggests no packages.
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:3.1+dfsg-2

We believe that the bug you reported is fixed in the latest version of
qemu, 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.
Michael Tokarev  (supplier of updated qemu 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, 21 Dec 2018 16:51:39 +0300
Source: qemu
Binary: qemu qemu-system qemu-block-extra qemu-system-data qemu-system-common 
qemu-system-gui qemu-system-misc qemu-system-arm qemu-system-mips 
qemu-system-ppc qemu-system-sparc qemu-system-x86 qemu-user qemu-user-static 
qemu-user-binfmt qemu-utils qemu-guest-agent qemu-kvm
Architecture: source
Version: 1:3.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QEMU Team 
Changed-By: Michael Tokarev 
Description:
 qemu   - fast processor emulator, dummy package
 qemu-block-extra - extra block backend modules for qemu-system and qemu-utils
 qemu-guest-agent - Guest-side qemu-system agent
 qemu-kvm   - QEMU Full virtualization on x86 hardware
 qemu-system - QEMU full system emulation binaries
 qemu-system-arm - QEMU full system emulation binaries (arm)
 qemu-system-common - QEMU full system emulation binaries (common files)
 qemu-system-data - QEMU full system emulation (data files)
 qemu-system-gui - QEMU full system emulation binaries (user interface and 
audio sup
 qemu-system-mips - QEMU full system emulation binaries (mips)
 qemu-system-misc - QEMU full system emulation binaries (miscellaneous)
 qemu-system-ppc - QEMU full system emulation binaries (ppc)
 qemu-system-sparc - QEMU full system emulation binaries (sparc)
 qemu-system-x86 - QEMU full system emulation binaries (x86)
 qemu-user  - QEMU user mode emulation binaries
 qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user
 qemu-user-static - QEMU user mode emulation binaries (static version)
 qemu-utils - QEMU utilities
Closes: 684909 849798 903562 912655 916278 916279 916397 916625 916674 917007
Changes:
 qemu (1:3.1+dfsg-2) unstable; urgency=medium
 .
   * d/rules: split arch 

Processed: severity of 912048 is normal

[Debian Bug Tracking System]

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

> severity 912048 normal
Bug #912048 [src:obs-build] obs-build: FTBFS: Test failures
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#875015: marked as done ([libkdegames-kde4] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 15:40:19 +
with message-id 
and subject line Bug#917012: Removed package(s) from unstable
has caused the Debian Bug report #875015,
regarding [libkdegames-kde4] Future Qt4 removal from Buster
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.)


-- 
875015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libkdegames-kde4
Version: 4:14.12.3-2
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 4:14.12.3-2+rm

Dear submitter,

as the package libkdegames-kde4 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/917012

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#841411: marked as done (libkf5kface: FTBFS: error with opencv 3.1)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 15:40:46 +
with message-id 
and subject line Bug#917013: Removed package(s) from unstable
has caused the Debian Bug report #841411,
regarding libkf5kface: FTBFS: error with opencv 3.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.)


-- 
841411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841411
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libkf5kface
Version: 15.12.0-3
Severity: important
Justification: fails to build from source

Dear Maintainer,

I am scheduled to transition of opencv.
   https://release.debian.org/transitions/html/auto-opencv.html
This package is target to transition. I tested build with opencv 3.1.
As a result, FTBFS with opencv 3.1.

-
Run Build Command:"/usr/bin/make" "cmTC_9dbba/fast"
make[2]: Entering directory
'/build/libkf5kface-15.12.0/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_9dbba.dir/build.make
CMakeFiles/cmTC_9dbba.dir/build
make[3]: Entering directory
'/build/libkf5kface-15.12.0/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_9dbba.dir/src.cxx.o
/usr/bin/c++   -D_GNU_SOURCE -D_LARGEFILE64_SOURCE  -g -O2
-fdebug-prefix-map=/build/libkf5kface-15.12.0=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2  -D_OFFT_IS_64BIT
 -o CMakeFiles/cmTC_9dbba.dir/src.cxx.o -c
/build/libkf5kface-15.12.0/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx
Linking CXX executable cmTC_9dbba
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_9dbba.dir/link.txt
--verbose=1
/usr/bin/c++   -g -O2 -fdebug-prefix-map=/build/libkf5kface-15.12.0=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2  -D_OFFT_IS_64BIT
 -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined
CMakeFiles/cmTC_9dbba.dir/src.cxx.o  -o cmTC_9dbba -rdynamic
make[3]: Leaving directory
'/build/libkf5kface-15.12.0/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: Leaving directory
'/build/libkf5kface-15.12.0/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'

Source file was:

#include 
 /* Check that off_t can represent 2**63 - 1 correctly.
We can't simply define LARGE_OFF_T to be 9223372036854775807,
since some C++ compilers masquerading as C compilers
incorrectly reject 9223372036854775807.  */
#define LARGE_OFF_T (((off_t) 1 << 62) - 1 + ((off_t) 1 << 62))
  int off_t_is_large[(LARGE_OFF_T % 2147483629 == 721 && LARGE_OFF_T %
2147483647 == 1) ? 1 : -1];
  int main() { return 0; }

dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var
-DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc
-DKDE_INSTALL_USE_QT_SYS_PATHS=ON returned exit code 1
/usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: recipe for target
'pre_configure_dh_auto_configure' failed
make[1]: *** [pre_configure_dh_auto_configure] Error 2
make[1]: Leaving directory '/build/libkf5kface-15.12.0'
/usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:112: recipe for target
'debian/dhmk_configure' failed
-

Could you check your package?

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6


libkf5kface_15.12.0-3_amd64.build.bz2
Description: BZip2 compressed data
--- End Message ---
--- Begin Message ---
Version: 15.12.0-3+rm

Dear submitter,

as the package libkf5kface 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/917013

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#896253: marked as done (python-visionegg: VisionEgg fails to import)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 15:37:47 +
with message-id 
and subject line Bug#916995: Removed package(s) from unstable
has caused the Debian Bug report #896253,
regarding python-visionegg: VisionEgg fails to import
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.)


-- 
896253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896253
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-visionegg
Version: 1.2.1-4
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-visionegg importing the module VisionEgg
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/VisionEgg/__init__.py", line 37, in 

import VisionEgg.ParameterTypes as ve_types
  File "/usr/lib/python2.7/dist-packages/VisionEgg/ParameterTypes.py", line 20, 
in 
import numpy.oldnumeric as numpyNumeric
ImportError: No module named oldnumeric

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Version: 1.2.1-5+rm

Dear submitter,

as the package visionegg 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/916995

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#916957: marked as done (julia (source): missing source for contrib/windows/7zS.sfx)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 15:22:24 +
with message-id 
and subject line Bug#916957: fixed in julia 1.0.3+dfsg-1
has caused the Debian Bug report #916957,
regarding julia (source): missing source for contrib/windows/7zS.sfx
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.)


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

Hi,

the source for contrib/windows/7zS.sfx seems to be missing.  As the
file is probably not needed for Debian, it could just be removed from
Debian's source tarball.

Ansgar
--- End Message ---
--- Begin Message ---
Source: julia
Source-Version: 1.0.3+dfsg-1

We believe that the bug you reported is fixed in the latest version of
julia, 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.
Mo Zhou  (supplier of updated julia 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, 21 Dec 2018 14:47:47 +
Source: julia
Binary: julia libjulia1 julia-common libjulia-dev julia-doc
Architecture: source
Version: 1.0.3+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Julia Team 
Changed-By: Mo Zhou 
Description:
 julia  - high-performance programming language for technical computing
 julia-common - high-performance programming language for technical computing 
(co
 julia-doc  - high-performance programming language for technical computing (do
 libjulia-dev - high-performance programming language for technical computing 
(de
 libjulia1  - high-performance programming language for technical computing (ru
Closes: 916957 916991
Changes:
 julia (1.0.3+dfsg-1) unstable; urgency=medium
 .
   * Users who want to use MKL as Julia's BLAS/LAPACK backend should
 rebuild this package after turning on the CUSTOM_MKL flag in d/rules.
 I temporarily reverted the use of alternatives mechanism because the
 code of stdlib/LinearAlgebra is not ready for such a feature.
 .
   * DFSG: Exclude contrib/windows/7zS.sfx (Closes: #916957)
   * Remove the aforementioned incremental patch since the
 source tarball has been refreshed.
   * Revert "Link libjulia.so.X against libblas.so.3 to take
 advantage from alternatives." (Closes: #916991)
Checksums-Sha1:
 d68143a22be369ffb1893bfd502d0836aba7cf57 3062 julia_1.0.3+dfsg-1.dsc
 ea103369bb681f9167a8a93291ca50d8bf26875e 3419456 julia_1.0.3+dfsg.orig.tar.xz
 ec320d9f556bc59b7b7e1cb97d1486786235e12c 3170352 
julia_1.0.3+dfsg-1.debian.tar.xz
 fe1996140c088c264aae412ad818eaccb9c28f52 9023 
julia_1.0.3+dfsg-1_source.buildinfo
Checksums-Sha256:
 ab9bf9d19ea66cadb25772f0614566f9497ef4517a697350d360ddc8821b7e3a 3062 
julia_1.0.3+dfsg-1.dsc
 8d66c4534a42ac2cb713f25f23cf9c13809c003fcb250dd48e517aca61eaf387 3419456 
julia_1.0.3+dfsg.orig.tar.xz
 05b8c593bcbaf82c1e8d08d807969fa630bc4d17189ddef76aebbef152fc9b47 3170352 
julia_1.0.3+dfsg-1.debian.tar.xz
 00b3fde9dc2f829cd77dc383245a285375a6aceedfc5acb78b4af66fcd609a25 9023 
julia_1.0.3+dfsg-1_source.buildinfo
Files:
 d80c629372d9d4b5447896a059201045 3062 science optional julia_1.0.3+dfsg-1.dsc
 0c8e7cff795b5692934455d459a65fc4 3419456 science optional 
julia_1.0.3+dfsg.orig.tar.xz
 480cf5a29c793b5f1d87bcf869de2c8e 3170352 science optional 
julia_1.0.3+dfsg-1.debian.tar.xz
 2f8ab508a47e9ba021b0f36fe279dbf4 9023 science optional 
julia_1.0.3+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAlwc/zsACgkQYmRes19o
aooA1g/+O4j6v9mur3u03jwVOcKdKzZuFzcuh/fCRndyR44O+x9kvm54fzclVoUo
UwDxMR86N+n502HcbkBjppi+j8LsVEcaGcIfc/xtFeIOy4WWjUh4yosTr/Fv+Um5
oviqPdlj9Asu1TqXCARWPcAQiB0o/4awlZk7yzuJIkER3pSQFf5m/98JF6d8QFTv
TdKgzonlVMtGiNIs+by8OVdnIwdJgov5vOpvLi2q5PHEXjRIypRWtoGQdaZjYrvi
sGhkJ4JJwMYhGxg5vxacarNvC8C0xnjhDQOcqldP2A/TbhLo9hgSO5JIvMqEa3OO
7Vq48kCcqlQmglIffoX5FVA6UwGsNULytccscu3d49l7v7OcJMQjgpV9JcWc0l+t
ah4nBmQuPA6V3JZX9o4nJilbVj5Z70vgqRUe2KFHUjaIESfUu/vagpDFod6sN1Bk
nVf+AHa3GiIfx/caeocyvKSm01yUYJo1+X/fmI8avTF8aLhatDNPphwWHmb+s7ZY

Processed: Re: Bug#912110: opensurgsim FTBFS: test failures

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #912110 [src:opensurgsim] opensurgsim FTBFS: test failures
Added tag(s) upstream.
> forwarded -1 https://github.com/simquest/opensurgsim/issues/1
Bug #912110 [src:opensurgsim] opensurgsim FTBFS: test failures
Set Bug forwarded-to-address to 
'https://github.com/simquest/opensurgsim/issues/1'.

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

Bug#912110: opensurgsim FTBFS: test failures

[Andreas Tille]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/simquest/opensurgsim/issues/1

Paul,

I have forwarded the issue upstream, may be you get involved there.

Kind regards, Andreas.


-- 
http://fam-tille.de

Bug#917018: wget: Unusable - permanent segmentation fault

[rwpenney]

Package: wget
Version: 1.18-5+deb9u2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

In ordinary use cases, 'wget' on Debian-9.6 ("stretch", amd64) is immediately
crashing with a segmentation fault when I try to mirror http or https websites.

A simple case is:
# wget -r -k -l inf http://www.debian.org

I have tried a variety of other URLs, and either http or https protocols.
No error messages are issued other than "Segmentation fault".

Without this basic functionality, "wget" under Debian-9 seems unusable
for http mirroring, which is a key use-case for this package.

Thanks.

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

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

Versions of packages wget depends on:
ii  libc62.24-11+deb9u3
ii  libgnutls30  3.5.8-5+deb9u4
ii  libidn11 1.33-1
ii  libnettle6   3.3-1+b2
ii  libpcre3 2:8.39-3
ii  libpsl5  0.17.0-3
ii  libuuid1 2.29.2-1+deb9u1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages wget recommends:
ii  ca-certificates  20161130+nmu1+deb9u1

wget suggests no packages.

-- no debconf information

Bug#911768: pinentry-gnome3 fails to open a window with 'No Gcr System Prompter available, falling back to curses'

[Theodore Y. Ts'o]

On Thu, Dec 20, 2018 at 03:17:03PM -0500, Daniel Kahn Gillmor wrote:
> 
> I wonder whether we can rule out any interaction with gpg-agent itself
> -- does "echo getpin | pinentry-gnome3" itself fall back to curses on
> your system when nfs-kernel-server is installed?

I can confirm that that I did this experiment before I uninstalled
nfs-kernel-server --- and it fell back to curses.

The next experiment to do would be to reinstall nfs-kernel-server and
reboot --- and see if it falls back to curses again.

  - Ted

Bug#887529: marked as done (aiohttp-cors FTBFS: test errors)

[Debian Bug Tracking System]

Your message dated Fri, 21 Dec 2018 12:19:10 +
with message-id 
and subject line Bug#887529: fixed in aiohttp-cors 0.7.0-1
has caused the Debian Bug report #887529,
regarding aiohttp-cors FTBFS: test errors
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.)


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

Some recent change in unstable makes aiohttp-cors FTBFS:

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

...
 ERRORS 
_ ERROR at teardown of TestMain.test_preflight_default _

self = 

def tearDown(self):
self.session.close()

if self.server is not None:
>   self.loop.run_until_complete(self.shutdown_server())

tests/integration/test_main.py:70: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3.6/asyncio/base_events.py:467: in run_until_complete
return future.result()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 

@asyncio.coroutine
def shutdown_server(self):
"""Shutdown server."""
assert self.server is not None

self.server.close()
>   yield from self.handler.finish_connections()
E   AttributeError: 'Server' object has no attribute 'finish_connections'

tests/integration/test_main.py:101: AttributeError
__ ERROR at teardown of TestMain.test_simple_default ___

self = 

def tearDown(self):
self.session.close()

if self.server is not None:
>   self.loop.run_until_complete(self.shutdown_server())

tests/integration/test_main.py:70: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3.6/asyncio/base_events.py:467: in run_until_complete
return future.result()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 

@asyncio.coroutine
def shutdown_server(self):
"""Shutdown server."""
assert self.server is not None

self.server.close()
>   yield from self.handler.finish_connections()
E   AttributeError: 'Server' object has no attribute 'finish_connections'

tests/integration/test_main.py:101: AttributeError
___ ERROR at teardown of TestMain.test_simple_expose_headers ___

self = 

def tearDown(self):
self.session.close()

if self.server is not None:
>   self.loop.run_until_complete(self.shutdown_server())

tests/integration/test_main.py:70: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3.6/asyncio/base_events.py:467: in run_until_complete
return future.result()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 

@asyncio.coroutine
def shutdown_server(self):
"""Shutdown server."""
assert self.server is not None

self.server.close()
>   yield from self.handler.finish_connections()
E   AttributeError: 'Server' object has no attribute 'finish_connections'

tests/integration/test_main.py:101: AttributeError
__ ERROR at teardown of TestMain.test_simple_with_credentials __

self = 

def tearDown(self):
self.session.close()

if self.server is not None:
>   self.loop.run_until_complete(self.shutdown_server())

tests/integration/test_main.py:70: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3.6/asyncio/base_events.py:467: in run_until_complete
return future.result()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 

@asyncio.coroutine
def shutdown_server(self):
"""Shutdown server."""
assert self.server is not None

self.server.close()
>   yield from self.handler.finish_connections()
E   AttributeError: 'Server' object has no attribute 'finish_connections'

tests/integration/test_main.py:101: AttributeError
=== FAILURES ===
__ TestMain.test_dummy_setup ___

self = 

def tearDown(self):
self.session.close()

if self.server is not 

Bug#914112: [debian-mysql] Bug#914112: galera-3 FTBFS: error: no matching function for call to 'asio::ssl::context::context(asio::io_service&, asio::ssl::context_base::method)'

[Otto Kekäläinen]

> Just submitted a merge request on Salsa. Thanks for the clear documentation 
> on how to set up the CI pipeline in my forked repo. One issue I noticed, 
> though, is that the GitLab CI configuration file is called 
> debian/.gitlab-ci.yml, while it's debian/gitlab-ci.yml in the other MariaDB 
> projects. The wiki page only mentions the latter path - maybe we should 
> standardize galera-3 with that one as well?

Right. Done now in
https://salsa.debian.org/mariadb-team/galera-3/commit/2705f72f31ed13c8e95e7e263e921abd90476d8d