Bug#919256: dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1

[Axel Beckert]

Control: reopen -1
Control: found -1 0.17+repack-2

Hi Diane,

Diane Trout wrote:
> I found the place that was causing the segfault on installation, made a
> patch, it worked for me, and I pushed a new release.

Thanks for caring and looking into it.

> Please let me know if dnssec-trigger-0.17+repack-2 works for you.

Unfortuantely not:

Preparing to unpack .../dnssec-trigger_0.17+repack-2_amd64.deb ...
Unpacking dnssec-trigger (0.17+repack-2) over (0.17+repack-1) ...
Setting up dnssec-trigger (0.17+repack-2) ...
[] Restarting : dnssec-triggerdJan 16 08:36:03 dnssec-triggerd[31539] 
error: Error for server-cert-file: /etc/dnssec-trigger/dnssec_trigger_server.pem
Jan 16 08:36:03 dnssec-triggerd[31539] error: Error in SSL_CTX 
use_certificate_file crypto error:140AB18F:SSL 
routines:SSL_CTX_use_certificate:ee key too small
Jan 16 08:36:03 dnssec-triggerd[31539] error: cannot setup SSL context
Jan 16 08:36:03 dnssec-triggerd[31539] fatal error: could not init server
 failed!

So the service start still failed, but the package upgraded now
properly (which I don't think happened before, but IMHO shouldn't
happen in this case anyway) while still failing to start, also on the
commandline:

# service dnssec-triggerd start
Jan 16 08:46:36 dnssec-triggerd[32323] error: Error for server-cert-file: 
/etc/dnssec-trigger/dnssec_trigger_server.pem
Jan 16 08:46:36 dnssec-triggerd[32323] error: Error in SSL_CTX 
use_certificate_file crypto error:140AB18F:SSL 
routines:SSL_CTX_use_certificate:ee key too small
Jan 16 08:46:36 dnssec-triggerd[32323] error: cannot setup SSL context
Jan 16 08:46:36 dnssec-triggerd[32323] fatal error: could not init server
#

Reason seems to be at least in this case that
dnssec-trigger-control-setup (which you patched for the key length
check) is never called in my case.

>From the postinst script:

# summary of how this script can be called:
#*  `configure' 
[...]
case "$1" in
configure)
# configure the control channel if run for the first time
if [ -z "$2" ]; then
dnssec-trigger-control-setup
fi
;;

So as I read it, dnssec-trigger-control-setup is only called if there
was no previously configured version installed and is hence never
called when upgrading the package and hence never removes, the too
small old keys on upgrade.

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

Processed: Re: Bug#919256: dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #919256 {Done: Diane Trout } [dnssec-trigger] 
dnssec-trigger: Failed to upgrade: installed dnssec-trigger package 
post-installation script subprocess returned error exit status 1
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions dnssec-trigger/0.17+repack-2.
> found -1 0.17+repack-2
Bug #919256 [dnssec-trigger] dnssec-trigger: Failed to upgrade: installed 
dnssec-trigger package post-installation script subprocess returned error exit 
status 1
Marked as found in versions dnssec-trigger/0.17+repack-2.

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

Bug#900821: linux-image-4.9.0-6-amd64: apache reads wrong data over cifs filesystems served by samba

[Karel Kozlík]

Hi,

I am facing this problem with debian stable, but kernel from backports:

ii  linux-image-4.19.0-0.bpo.1-amd64-unsigned 4.19.12-1~bpo9+1
   amd64Linux 4.19 for 64-bit PCs

Linux version 4.19.0-0.bpo.1-amd64 (debian-ker...@lists.debian.org) (gcc
version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 SMP Debian
4.19.12-1~bpo9+1 (2018-12-30)

The problem appear around twice a day while copying data via rsync to
software raid disk array.

Jan 15 22:31:48 kk-router kernel: [ 6406.089208] general protection
fault:  [#1] SMP PTI
Jan 15 22:31:48 kk-router kernel: [ 6406.089330] CPU: 2 PID: 1183 Comm:
sshd Tainted: GE 4.19.0-0.bpo.1-amd64 #1 Debian
4.19.12-1~bpo9+1
Jan 15 22:31:48 kk-router kernel: [ 6406.089598] Hardware name: Gigabyte
Technology Co., Ltd. Default string/J3455N-D3H, BIOS F2 03/07/2017
Jan 15 22:31:48 kk-router kernel: [ 6406.089751] RIP:
0010:__check_object_size+0x7b/0x1a0
Jan 15 22:31:48 kk-router kernel: [ 6406.089834] Code: 00 00 80 48 2b 15
5d 0e c7 00 48 01 c2 48 c1 ea 0c 48 c1 e2 06 48 03 15 3b 0e c7 00 48 8b
42 08 48 8d 48 ff a8 01 48 0f 45 d1 <48> 8b 4a 08 48 8d 41 ff 83 e1 01
48 0f 44 c2 48 8b 00 f6 c4 01 75
Jan 15 22:31:48 kk-router kernel: [ 6406.090115] RSP:
0018:96f9415dfc58 EFLAGS: 00010202
Jan 15 22:31:48 kk-router kernel: [ 6406.090202] RAX: efffd06949355a01
RBX: 896a0d56cc02 RCX: efffd06949355a00
Jan 15 22:31:48 kk-router kernel: [ 6406.090314] RDX: efffd06949355a00
RSI: 896a3fff RDI: 896a8d56cc02
Jan 15 22:31:48 kk-router kernel: [ 6406.090426] RBP: 05a8
R08: 05a8 R09: 05a8
Jan 15 22:31:48 kk-router kernel: [ 6406.090538] R10: 
R11:  R12: 0001
Jan 15 22:31:48 kk-router kernel: [ 6406.090650] R13: 896a0d56d1aa
R14: 05a8 R15: 896a0d56cc02
Jan 15 22:31:48 kk-router kernel: [ 6406.090764] FS:
7ff8efe39d40() GS:896a37b0() knlGS:
Jan 15 22:31:48 kk-router kernel: [ 6406.090890] CS:  0010 DS:  ES:
 CR0: 80050033
Jan 15 22:31:48 kk-router kernel: [ 6406.090982] CR2: 7fadf5efbfb0
CR3: 000265ebc000 CR4: 003406e0
Jan 15 22:31:48 kk-router kernel: [ 6406.091095] Call Trace:
Jan 15 22:31:48 kk-router kernel: [ 6406.091152]
skb_copy_datagram_iter+0x75/0x260
Jan 15 22:31:48 kk-router kernel: [ 6406.091232]  tcp_recvmsg+0x72b/0xca0
Jan 15 22:31:48 kk-router kernel: [ 6406.091300]  ? aa_sk_perm+0x44/0x130
Jan 15 22:31:48 kk-router kernel: [ 6406.091366]  inet_recvmsg+0x5b/0xd0
Jan 15 22:31:48 kk-router kernel: [ 6406.091430]  sock_read_iter+0x94/0xf0
Jan 15 22:31:48 kk-router kernel: [ 6406.091498]  new_sync_read+0xfa/0x160
Jan 15 22:31:48 kk-router kernel: [ 6406.091565]  vfs_read+0x91/0x130
Jan 15 22:31:48 kk-router kernel: [ 6406.091624]  ksys_read+0x52/0xc0
Jan 15 22:31:48 kk-router kernel: [ 6406.091685]  do_syscall_64+0x55/0x110
Jan 15 22:31:48 kk-router kernel: [ 6406.091752]
entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jan 15 22:31:48 kk-router kernel: [ 6406.091837] RIP: 0033:0x7ff8edfad6d0
Jan 15 22:31:48 kk-router kernel: [ 6406.091900] Code: b6 fe ff ff 48 8d
3d 17 be 08 00 48 83 ec 08 e8 06 db 01 00 66 0f 1f 44 00 00 83 3d 39 30
2c 00 00 75 10 b8 00 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 31 c3 48 83
ec 08 e8 de 9b 01 00 48 89 04 24
Jan 15 22:31:48 kk-router kernel: [ 6406.092180] RSP:
002b:7ffe060775a8 EFLAGS: 0246 ORIG_RAX: 
Jan 15 22:31:48 kk-router kernel: [ 6406.092301] RAX: ffda
RBX: 0003 RCX: 7ff8edfad6d0
Jan 15 22:31:48 kk-router kernel: [ 6406.092413] RDX: 4000
RSI: 7ffe060775b0 RDI: 0003
Jan 15 22:31:48 kk-router kernel: [ 6406.092525] RBP: 5572caec33e0
R08:  R09: 4500
Jan 15 22:31:48 kk-router kernel: [ 6406.092637] R10: 7ffe0607b530
R11: 0246 R12: 
Jan 15 22:31:48 kk-router kernel: [ 6406.092748] R13: 7ffe0607b63f
R14: 5572c925cb67 R15: 0003
Jan 15 22:31:48 kk-router kernel: [ 6406.092862] Modules linked in:
snd_hda_codec_hdmi(E) snd_hda_codec_realtek(E) snd_hda_codec_generic(E)
nls_ascii(E) intel_rapl(E) nls_cp437(E) x86_pkg_temp_thermal(E)
intel_powerclamp(E) vfat(E) coretemp(E) fat(E) efi_pstore(E) kvm(E)
irqbypass(E) snd_soc_skl(E) snd_soc_skl_ipc(E) snd_soc_sst_ipc(E)
crct10dif_pclmul(E) snd_soc_sst_dsp(E) snd_hda_ext_core(E) ppdev(E)
snd_soc_acpi_intel_match(E) snd_soc_acpi(E) crc32_pclmul(E) i915(E)
snd_soc_core(E) snd_compress(E) snd_hda_intel(E) ghash_clmulni_intel(E)
intel_cstate(E) drm_kms_helper(E) intel_rapl_perf(E) snd_hda_codec(E)
drm(E) evdev(E) snd_hda_core(E) i2c_algo_bit(E) snd_hwdep(E) efivars(E)
pcspkr(E) snd_pcm(E) lpc_ich(E) snd_timer(E) snd(E) mei_me(E)
soundcore(E) mei(E) sg(E) button(E) parport_pc(E) parport(E) video(E)
pcc_cpufreq(E) nfsd(E) auth_rpcgss(E)
Jan 15 22:31:48 kk-router kernel: [ 6406.094025]  nfs_acl(E) lockd(E)
grace(E) sunrpc(E) efivarfs(E) ip_tables(E) 

Bug#888130: ruby-net-http-persistent: FTBFS on ruby2.5: ssl verification fails

[Ritesh Raj Sarraf]

Package: src:ruby-net-http-persistent
Followup-For: Bug #888130

The one uploaded recently into experimental has built successfully. Can
the maintainer please upload it to Unstable so that it does get included
in Buster ?

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

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

Bug#878470: marked as done (scute FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 06:34:27 +
with message-id 
and subject line Bug#878470: fixed in scute 1:1.5.0-1
has caused the Debian Bug report #878470,
regarding scute 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.)


-- 
878470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scute
Version: 1.5.0+git20160808+94eeb2d-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes scute FTBFS:

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

...
make  check-TESTS
make[4]: Entering directory '/build/1st/scute-1.5.0+git20160808+94eeb2d/tests'
make[5]: Entering directory '/build/1st/scute-1.5.0+git20160808+94eeb2d/tests'
PASS: t-link
PASS: t-getfunctionlist
PASS: t-initialize
PASS: t-getinfo
gpg-agent[58357]: can't connect to the SCdaemon: End of file
gpg-agent[58357]: DBG: agent_card_learn failed: No SmartCard daemon
gpg-agent[58357]: command 'LEARN' failed: No SmartCard daemon
FAIL: t-getslotlist
gpg-agent[58357]: can't connect to the SCdaemon: End of file
gpg-agent[58357]: DBG: agent_card_learn failed: No SmartCard daemon
gpg-agent[58357]: command 'LEARN' failed: No SmartCard daemon
FAIL: t-getslotinfo
gpg-agent[58357]: can't connect to the SCdaemon: End of file
gpg-agent[58357]: DBG: agent_card_learn failed: No SmartCard daemon
gpg-agent[58357]: command 'LEARN' failed: No SmartCard daemon
FAIL: t-gettokeninfo
gpg-agent[58357]: can't connect to the SCdaemon: End of file
gpg-agent[58357]: DBG: agent_card_learn failed: No SmartCard daemon
gpg-agent[58357]: command 'LEARN' failed: No SmartCard daemon
FAIL: t-getmechanismlist
gpg-agent[58357]: can't connect to the SCdaemon: End of file
gpg-agent[58357]: DBG: agent_card_learn failed: No SmartCard daemon
gpg-agent[58357]: command 'LEARN' failed: No SmartCard daemon
FAIL: t-getmechanisminfo
gpg-agent[58357]: can't connect to the SCdaemon: End of file
gpg-agent[58357]: DBG: agent_card_learn failed: No SmartCard daemon
gpg-agent[58357]: command 'LEARN' failed: No SmartCard daemon
FAIL: t-opensession
gpg-agent[58357]: can't connect to the SCdaemon: End of file
gpg-agent[58357]: DBG: agent_card_learn failed: No SmartCard daemon
gpg-agent[58357]: command 'LEARN' failed: No SmartCard daemon
FAIL: t-closeallsessions
gpg-agent[58357]: can't connect to the SCdaemon: End of file
gpg-agent[58357]: DBG: agent_card_learn failed: No SmartCard daemon
gpg-agent[58357]: command 'LEARN' failed: No SmartCard daemon
FAIL: t-getsessioninfo
gpg-agent[58357]: can't connect to the SCdaemon: End of file
gpg-agent[58357]: DBG: agent_card_learn failed: No SmartCard daemon
gpg-agent[58357]: command 'LEARN' failed: No SmartCard daemon
FAIL: t-findobjects
gpg-agent[58357]: can't connect to the SCdaemon: End of file
gpg-agent[58357]: DBG: agent_card_learn failed: No SmartCard daemon
gpg-agent[58357]: command 'LEARN' failed: No SmartCard daemon
FAIL: t-getattribute
gpg-agent[58357]: can't connect to the SCdaemon: End of file
gpg-agent[58357]: DBG: agent_card_learn failed: No SmartCard daemon
gpg-agent[58357]: command 'LEARN' failed: No SmartCard daemon
FAIL: t-auth
gpg-agent[58357]: can't connect to the SCdaemon: End of file
gpg-agent[58357]: DBG: agent_card_learn failed: No SmartCard daemon
gpg-agent[58357]: command 'LEARN' failed: No SmartCard daemon
FAIL: t-generaterandom
===
   scute 1.5.0-unknown: tests/test-suite.log
===

# TOTAL: 16
# PASS:  4
# SKIP:  0
# XFAIL: 0
# FAIL:  12
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: t-getslotlist
===

t-getslotlist.c:53: Function failed
FAIL t-getslotlist (exit status: 1)

FAIL: t-getslotinfo
===

t-getslotinfo.c:52: Function failed
FAIL t-getslotinfo (exit status: 1)

FAIL: t-gettokeninfo


t-gettokeninfo.c:49: Function failed
FAIL t-gettokeninfo (exit status: 1)

FAIL: t-getmechanismlist


t-getmechanismlist.c:50: Function failed
FAIL t-getmechanismlist (exit status: 1)

FAIL: t-getmechanisminfo


t-getmechanisminfo.c:50: Function failed
FAIL t-getmechanisminfo (exit status: 1)

FAIL: t-opensession
===

t-opensession.c:51: Function failed
FAIL t-opensession (exit status: 1)

FAIL: t-closeallsessions


t-closeallsessions.c:51: Function failed
FAIL t-closeallsessions (exit status: 1)

FAIL: 

Bug#915995: nfs-utils FTBFS with glibc 2.28

[Ritesh Raj Sarraf]

Package: src:nfs-utils
Followup-For: Bug #915995

Please find attached a patch to fix the build failure

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

Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru nfs-utils-1.3.4/debian/changelog nfs-utils-1.3.4/debian/changelog
--- nfs-utils-1.3.4/debian/changelog2018-10-20 18:34:07.0 +0530
+++ nfs-utils-1.3.4/debian/changelog2019-01-16 11:33:27.0 +0530
@@ -1,3 +1,9 @@
+nfs-utils (1:1.3.4-2.4) unstable; urgency=medium
+
+  * Fix FTBFS causes by undefined reference to major. (Closes: #915995) 
+
+ -- Ritesh Raj Sarraf   Wed, 16 Jan 2019 11:33:27 +0530
+
 nfs-utils (1:1.3.4-2.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru nfs-utils-1.3.4/debian/patches/fix-ftbfs-undefined-major.patch 
nfs-utils-1.3.4/debian/patches/fix-ftbfs-undefined-major.patch
--- nfs-utils-1.3.4/debian/patches/fix-ftbfs-undefined-major.patch  
1970-01-01 05:30:00.0 +0530
+++ nfs-utils-1.3.4/debian/patches/fix-ftbfs-undefined-major.patch  
2019-01-16 11:33:19.0 +0530
@@ -0,0 +1,11 @@
+Fix FBTFS cause by undefined reference to major
+--- a/utils/blkmapd/device-discovery.c
 b/utils/blkmapd/device-discovery.c
+@@ -31,6 +31,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ #include 
+ #include 
diff -Nru nfs-utils-1.3.4/debian/patches/series 
nfs-utils-1.3.4/debian/patches/series
--- nfs-utils-1.3.4/debian/patches/series   2018-10-20 18:20:42.0 
+0530
+++ nfs-utils-1.3.4/debian/patches/series   2019-01-16 11:31:58.0 
+0530
@@ -12,3 +12,4 @@
 29-start-statd-fd-9.patch
 0001-rpc.c-added-include-file-so-UINT16_MAX-is-defined.patch
 30-remove-whitespace-service.patch
+fix-ftbfs-undefined-major.patch

Bug#919256: marked as done (dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1)

[Debian Bug Tracking System]

Your message dated Wed, 16 Jan 2019 06:04:07 +
with message-id 
and subject line Bug#919256: fixed in dnssec-trigger 0.17+repack-2
has caused the Debian Bug report #919256,
regarding dnssec-trigger: Failed to upgrade: installed dnssec-trigger package 
post-installation script subprocess returned error exit status 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.)


-- 
919256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dnssec-trigger
Version: 0.17+repack-1
Severity: serious

Setting up dnssec-trigger (0.17+repack-1) ...
Job for dnssec-triggerd.service failed because the control process exited with 
error code.
See "systemctl status dnssec-triggerd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript dnssec-triggerd, action "restart" failed.
# dnssec-triggerd.service - Reconfigure local DNSSEC resolver on connectivity 
changes
   Loaded: loaded (/lib/systemd/system/dnssec-triggerd.service; enabled; vendor 
preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Mon 2019-01-14 
07:20:18 CET; 16ms ago
  Process: 29431 ExecStartPre=/usr/lib/dnssec-trigger/dnssec-trigger-script 
--prepare (code=exited, status=0/SUCCESS)
  Process: 29438 ExecStart=/usr/sbin/dnssec-triggerd -d (code=exited, 
status=1/FAILURE)
  Process: 29439 ExecStartPost=/usr/lib/dnssec-trigger/dnssec-trigger-script 
--update_all (code=exited, status=0/SUCCESS)
  Process: 29443 ExecStopPost=/usr/lib/dnssec-trigger/dnssec-trigger-script 
--cleanup (code=exited, status=1/FAILURE)
 Main PID: 29438 (code=exited, status=1/FAILURE)
dpkg: error processing package dnssec-trigger (--configure):
 installed dnssec-trigger package post-installation script subprocess returned 
error exit status 1
Processing triggers for libc-bin (2.28-5) ...
Errors were encountered while processing:
 dnssec-trigger

I said "no" to the new dnssec-trigger.conf, but except comments the only
difference is the search domain setting:

$ diff /etc/dnssec-trigger/dnssec-trigger.conf 
/etc/dnssec-trigger/dnssec-trigger.conf.dpkg-dist 
28c28
< search: "deuxchevaux.org noone.org ethz.ch debian.org"
---
> # search: ""
51c51
< # check-updates: 
---
> # check-updates: no
65a66
> # These relay incoming DNS traffic on the other port numbers to the usual DNS
76a78,86
> 
> # Use VPN servers for all traffic
> # use-vpn-forwarders: no
> 
> # Forward RFC 1918 private addresses to global forwarders
> # use-private-addresses: yes
> 
> # Add domains provided by VPN connections into Unbound forward zones
> # add-wifi-provided-zones: no

The syslog shows again this:

Jan 14 07:18:59 c-cactus2 dnssec-triggerd[22039]: Jan 14 07:18:59 
dnssec-triggerd[22039] error: Error in SSL_CTX use_certificate_file crypto 
error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small

So maybe https://bugs.debian.org/898969 is not fully fixed yet?

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

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

Versions of packages dnssec-trigger depends on:
ii  gir1.2-nm-1.0   1.14.4-4
ii  libc6   2.28-5
ii  libgdk-pixbuf2.0-0  2.38.0+dfsg-7
ii  libglib2.0-02.58.2-3
ii  libgtk2.0-0 2.24.32-3
ii  libldns21.7.0-3.1+b1
ii  libssl1.1   1.1.1a-1
ii  python3 3.7.1-3
ii  python3-gi  3.30.4-1
ii  python3-lockfile1:0.12.2-2
ii  sensible-utils  0.0.12
ii  unbound 1.8.1-1+b1

dnssec-trigger recommends no packages.

dnssec-trigger suggests no packages.

-- Configuration Files:
/etc/dnssec-trigger/dnssec-trigger.conf changed:
search: "deuxchevaux.org noone.org ethz.ch debian.org"
url: "http://ster.nlnetlabs.nl/hotspot.txt OK"
url: "http://fedoraproject.org/static/hotspot.txt OK"
tcp80: 185.49.140.67
tcp80: 2a04:b900::10:0:0:67
ssl443: 185.49.140.67 
7E:CF:B4:BE:B9:9A:56:0D:F7:3B:40:51:A4:78:E6:A6:FD:66:0F:10:58:DC:A8:2E:C0:43:D4:77:5A:71:8A:CF
ssl443: 2a04:b900::10:0:0:67 
7E:CF:B4:BE:B9:9A:56:0D:F7:3B:40:51:A4:78:E6:A6:FD:66:0F:10:58:DC:A8:2E:C0:43:D4:77:5A:71:8A:CF


-- no debconf information
--- End Message ---
--- Begin Message ---
Source: 

Bug#919256: dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1

[Diane Trout]

Ok

I found the place that was causing the segfault on installation, made a
patch, it worked for me, and I pushed a new release.

(Fixes also sent upstream)

dnssec-trigger should also now only look for configuration files in
/etc/dnssec-trigger, and it shouldn't try to create ones in /etc any
more.

This may cause problems with the location for your customized
configuration file, but that probably should be a new bug.

Please let me know if dnssec-trigger-0.17+repack-2 works for you.

Diane


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

Bug#919322: marked as done (CVE-2019-6245 CVE-2019-6247)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 21:54:35 -0800
with message-id 

and subject line Re: CVE-2019-6245 CVE-2019-6247
has caused the Debian Bug report #919322,
regarding CVE-2019-6245 CVE-2019-6247
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.)


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

Please see
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6245
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6247

Given that the package isn't exactly fast-moving, how about
revisiting #377270 for buster? Right now we need to coordinate
rebuilds against the fixed agg...

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
CVE-2019-6245 
was fixed in libagg-dev 1:2.4, SVG++ uses a 5 year old copy of AGG
that predates this fix.

CVE-2019-6247 
is a bug in SVG++ calling AGG functions with incorrect values for the
buffer used. See SVG++ commit: #70 Fix for bug 2

which fixes the call to use the correct arguments. AGG is working as
expected and doesn't exhibit this vulnerability when called with the
proper arguments.
--- End Message ---

Processed: yotta #919286

[Debian Bug Tracking System]

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

> owner 919286 Nick Morrott 
Bug #919286 [yotta] yotta: /usr/bin/yt is already provided by the python3-yt 
package
Owner recorded as Nick Morrott .
> tags 919286 + pending
Bug #919286 [yotta] yotta: /usr/bin/yt is already provided by the python3-yt 
package
Added tag(s) pending.
> quit
Stopping processing here.

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

Bug#911616: emacs-common: copyright file missing after upgrade of emacs-nox from stretch

[Andreas Beckmann]

Followup-For: Bug #911616
Control: tag -1 patch
Control: found -1 1:26.1+1-3

Hi,

attached you can find a patch that should properly handle the
dir_to_symlink conversion manually. I tested this on the
stretch->buster upgrade path of two previously failing packages
in my piuparts engine.


Andreas
>From d205f2459ad0f7be2f4f37b37a095c86b904f5eb Mon Sep 17 00:00:00 2001
From: Andreas Beckmann 
Date: Wed, 16 Jan 2019 03:37:44 +0100
Subject: [PATCH] Really handle the emacs-{gtk,lucid,nox} doc dir transition
 manually

reimplementing the guts of dir_to_symlink is quite easy:
in the postinst replace the empty directory with the intended symlink
caveats compared to dpkg-maintscript-helper:
* fails during postinst (not preinst) if the directory is not empty
* absolutely no rollback or downgrade support
---
 debian/emacsVAR.postinst | 14 ++
 debian/emacsVAR.preinst  | 23 ---
 debian/rules |  3 ---
 3 files changed, 14 insertions(+), 26 deletions(-)
 delete mode 100644 debian/emacsVAR.preinst

diff --git a/debian/emacsVAR.postinst b/debian/emacsVAR.postinst
index 8dadd23a896..fcadb1c4540 100644
--- a/debian/emacsVAR.postinst
+++ b/debian/emacsVAR.postinst
@@ -2,6 +2,20 @@
 
 set -e
 
+# Manual dir_to_symlink conversion since dpkg-maintscript-helper does not
+# handle this in combination with arch:all to arch:any switches (#813455).
+# Keep this code for buster and bullseye to ease backports.
+if [ "$1" = "configure" ] && dpkg --compare-versions "$2" lt-nl "1:26.1+1-4~"
+then
+   test -n '@PKG_NAME@'
+   if [ -d /usr/share/doc/@PKG_NAME@ ] && [ ! -h /usr/share/doc/@PKG_NAME@ 
]
+   then
+   # This will intentionally fail if the directory is not empty.
+   rmdir /usr/share/doc/@PKG_NAME@
+   ln -sv emacs-common /usr/share/doc/@PKG_NAME@
+   fi
+fi
+
 update-alternatives \
   --install /usr/bin/emacs emacs \
 /usr/bin/emacs-@X_SUPPORT@ @BIN_PRIORITY@ \
diff --git a/debian/emacsVAR.preinst b/debian/emacsVAR.preinst
deleted file mode 100644
index 26aac393c65..000
--- a/debian/emacsVAR.preinst
+++ /dev/null
@@ -1,23 +0,0 @@
-#!/bin/sh
-
-set -e
-
-doc_dir=/usr/share/doc/@PKG_NAME@
-
-test '@PKG_NAME@'
-
-case "$1" in
-install|upgrade)
-# Before the unversioning, emacs-{gtk,lucid,nox} packages were
-# in a different source package (emacs-defaults) and were arch
-# all, and dpkg can't handle dir to symlink transitions.
-rm -rf "$doc_dir"
-;;
-abort-upgrade)
-;;
-*)
-echo "unexpected $(basename "$0") argument"
-;;
-esac
-
-#DEBHELPER#
diff --git a/debian/rules b/debian/rules
index 6a3c40a2833..b2bd4931fcc 100755
--- a/debian/rules
+++ b/debian/rules
@@ -129,12 +129,9 @@ nonpersistent_autogen_install_files := \
   debian/emacs-common.postinst \
   debian/emacs-common.prerm \
   debian/emacs-nox.postinst \
-  debian/emacs-nox.preinst \
   debian/emacs-nox.prerm \
   debian/emacs-lucid.postinst \
-  debian/emacs-lucid.preinst \
   debian/emacs-lucid.prerm \
-  debian/emacs-gtk.preinst \
   debian/emacs-gtk.postinst \
   debian/emacs-gtk.prerm
 
-- 
2.11.0

Processed: Re: emacs-common: copyright file missing after upgrade of emacs-nox from stretch

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #911616 [emacs-nox,emacs-gtk,emacs-lucid] emacs-common: copyright file 
missing after upgrade of emacs-nox from stretch
Added tag(s) patch.
> found -1 1:26.1+1-3
Bug #911616 [emacs-nox,emacs-gtk,emacs-lucid] emacs-common: copyright file 
missing after upgrade of emacs-nox from stretch
Marked as found in versions emacs/1:26.1+1-3.

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

Bug#918026: ruby-sinatra-contrib: uninstallable; depends on versions not present in the archive

[Hideki Yamane]

On Fri, 4 Jan 2019 10:22:08 -0300
Antonio Terceiro  wrote:
> Are you working on updating sinatra? I started working on a new sinatra
> upstream release to unbreak debci after a new rack was uploaded, and
> could build binaries for ruby-sinatra-contrib (and ruby-rack-protection,
> which was also moved into sinatra) from the ruby-sinatra source in one
> go.

 Thanks Antonio for updating sinatra package!
 
 And now I've found that ruby-sinatra-contrib was removed from repository,
 is that intended?

 See https://ftp-master.debian.org/removals.txt


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#919322: CVE-2019-6245 CVE-2019-6247

[John Horigan]

I have prepared a new version of libagg-dev that fixes #377270 and I was
about to ask the package sponsor to upload it when this issue surfaced. I
will fold in fixes for the new bugs too.

-- john

On Mon, 14 Jan 2019 23:27:23 +0100 Moritz Muehlenhoff 
wrote:
> Source: agg
> Severity: grave
>
> Please see
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6245
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6247
>
> Given that the package isn't exactly fast-moving, how about
> revisiting #377270 for buster? Right now we need to coordinate
> rebuilds against the fixed agg...
>
> Cheers,
> Moritz
>
>

Bug#918993: marked as done (sagemath-jupyter: Invalid path to sage kernel makes notebook unusable)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 23:50:34 +
with message-id 
and subject line Bug#918993: fixed in sagemath 8.6-1
has caused the Debian Bug report #918993,
regarding sagemath-jupyter: Invalid path to sage kernel makes notebook unusable
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.)


-- 
918993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sagemath-jupyter
Version: 8.4-4
Severity: important

Dear Maintainer,

the jupyter notebook with sage is unusable because the kernel config is invalid,
in /usr/share/jupyter/kernels/sagemath/kernel.json there is:

{"display_name": "SageMath 8.6.rc0", 
 "argv": ["/build/sagemath-FTVAsu/sagemath-8.6~rc0/debian/build/usr/bin/sage",
  "--python", "-m", "sage.repl.ipython_kernel", "-f", "{connection_file}"]}

The hardcoded path contains what looks like a temporary build path, which
does not exists on my system. This makes the sage kernel unusable with jupyuter.
I tried to manually replace the path with /usr/bin/sage and it works.

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

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

Versions of packages sagemath-jupyter depends on:
ii  jupyter-client  5.2.3-1
ii  jupyter-core4.4.0-2
ii  jupyter-nbextension-jupyter-js-widgets  6.0.0-2
ii  python-ipykernel4.9.0-1
ii  python-ipywidgets   6.0.0-2
ii  python-nbconvert5.4-1
ii  python-nbformat 4.4.0-1
ii  python-notebook 5.4.1-1
ii  sagemath8.4-4

sagemath-jupyter recommends no packages.

sagemath-jupyter suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sagemath
Source-Version: 8.6-1

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

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

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

Debian distribution maintenance software
pp.
Tobias Hansen  (supplier of updated sagemath 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: Wed, 16 Jan 2019 00:25:58 +0100
Source: sagemath
Binary: sagemath sagemath-common sagemath-jupyter sagemath-doc-ca 
sagemath-doc-de sagemath-doc-en sagemath-doc-es sagemath-doc-fr sagemath-doc-hu 
sagemath-doc-it sagemath-doc-ja sagemath-doc-pt sagemath-doc-ru sagemath-doc-tr
Architecture: source
Version: 8.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Tobias Hansen 
Description:
 sagemath   - Open Source Mathematical Software
 sagemath-common - Open Source Mathematical Software - architecture-independent 
file
 sagemath-doc-ca - Open Source Mathematical Software - documentation (Catalan; 
Valen
 sagemath-doc-de - Open Source Mathematical Software - documentation (German)
 sagemath-doc-en - Open Source Mathematical Software - documentation (English)
 sagemath-doc-es - Open Source Mathematical Software - documentation (Spanish; 
Casti
 sagemath-doc-fr - Open Source Mathematical Software - documentation (French)
 sagemath-doc-hu - Open Source Mathematical Software - documentation (Hungarian)
 sagemath-doc-it - Open Source Mathematical Software - documentation (Italian)
 sagemath-doc-ja - Open Source Mathematical Software - documentation (Japanese)
 sagemath-doc-pt - Open Source Mathematical Software - documentation 
(Portuguese)
 sagemath-doc-ru - Open Source Mathematical Software - documentation (Russian)
 sagemath-doc-tr - Open Source Mathematical Software - documentation (Turkish)
 sagemath-jupyter - Open Source Mathematical Software - Jupyter kernel
Closes: 918993
Changes:
 sagemath (8.6-1) unstable; urgency=medium
 .
   * Upload to unstable.
   * New upstream 

Bug#919374: marked as done (libodb-mysql: FTBFS with mariadb-10.3: ../../odb/mysql/mysql-types.hxx:16:12: fatal error: mysql/mysql_time.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 23:49:19 +
with message-id 
and subject line Bug#919374: fixed in libodb-mysql 2.4.0-4
has caused the Debian Bug report #919374,
regarding libodb-mysql: FTBFS with mariadb-10.3: 
../../odb/mysql/mysql-types.hxx:16:12: fatal error: mysql/mysql_time.h: No such 
file or directory
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.)


-- 
919374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libodb-mysql
Version: 2.4.0-3
Severity: serious
Tags: sid buster
Justification: fails to build from source (but built successfully in the past)

Hi,

libodb-mysql FTBFS with mariadb-10.3 in sid:

libtool: compile:  g++ -DHAVE_CONFIG_H -I../.. -I../.. 
-DLIBODB_MYSQL_DYNAMIC_LIB -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/build/libodb-mysql-2.4.0=. -fstack-protector-strong 
-Wformat -Werror=fo
rmat-security -D_REENTRANT -c connection-factory.cxx  -fPIC -DPIC -o 
.libs/connection-factory.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I../.. -I../.. 
-DLIBODB_MYSQL_DYNAMIC_LIB -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/build/libodb-mysql-2.4.0=. -fstack-protector-strong 
-Wformat -Werror=fo
rmat-security -D_REENTRANT -c database.cxx  -fPIC -DPIC -o .libs/database.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I../.. -I../.. 
-DLIBODB_MYSQL_DYNAMIC_LIB -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/build/libodb-mysql-2.4.0=. -fstack-protector-strong 
-Wformat -Werror=fo
rmat-security -D_REENTRANT -c enum.cxx  -fPIC -DPIC -o .libs/enum.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I../.. -I../.. 
-DLIBODB_MYSQL_DYNAMIC_LIB -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/build/libodb-mysql-2.4.0=. -fstack-protector-strong 
-Wformat -Werror=fo
rmat-security -D_REENTRANT -c connection.cxx  -fPIC -DPIC -o .libs/connection.o
In file included from ../../odb/mysql/mysql.hxx:10,
 from connection-factory.cxx:17:
../../odb/mysql/mysql-types.hxx:16:12: fatal error: mysql/mysql_time.h: No such 
file or directory
 #  include 
^~~~
compilation terminated.
libtool: compile:  g++ -DHAVE_CONFIG_H -I../.. -I../.. 
-DLIBODB_MYSQL_DYNAMIC_LIB -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/build/libodb-mysql-2.4.0=. -fstack-protector-strong 
-Wformat -Werror=format-security -D_REENTRANT -c prepared-query.cxx  -fPIC 
-DPIC -o .libs/prepared-query.o
make[3]: *** [Makefile:540: connection-factory.lo] Error 1


Cheers,

Andreas


libodb-mysql_2.4.0-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libodb-mysql
Source-Version: 2.4.0-4

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated libodb-mysql 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Jan 2019 20:20:59 +
Source: libodb-mysql
Binary: libodb-mysql-2.4 libodb-mysql-dev
Architecture: source
Version: 2.4.0-4
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 libodb-mysql-2.4 - ODB Runtime Library for MySQL
 libodb-mysql-dev - ODB Runtime Library for MySQL (development)
Closes: 919374
Changes:
 libodb-mysql (2.4.0-4) unstable; urgency=medium
 .
   * Fix FTBFS with recent MariaDB (closes: #919374).
   * Update debhelper level to 11:
 - remove dh-autoreconf build dependency,
 - don't specify parallel to debhelper.
   * Update Standards-Version to 4.3.0 .
Checksums-Sha1:
 a41cfff636949ef6685a19e2e1ccb74e5c45d30f 1900 libodb-mysql_2.4.0-4.dsc
 0a023fcac548eff6d9659ffb7d9a67ec91dcf72b 2696 
libodb-mysql_2.4.0-4.debian.tar.xz
 19988cc9cbc19e9b22533bb160a7f1843b7543cc 7378 
libodb-mysql_2.4.0-4_amd64.buildinfo
Checksums-Sha256:
 3be39734177a0b6701556d815993ce40d84e6fd0e75179b84d7dc80ca9931431 1900 
libodb-mysql_2.4.0-4.dsc
 

Bug#919443: ifupdown2: leaves diversion after upgrade from stretch

[Andreas Beckmann]

Package: ifupdown2
Version: 1.2.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to remove some
diversions after upgrading from stretch and removing the package
afterwards.

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

0m51.2s ERROR: FAIL: Installed diversions (dpkg-divert) not removed by purge:
  diversion of /sbin/ifreload to /sbin/ifreload.disabled by ifupdown2
  diversion of /etc/bash_completion.d/ifdown to 
/etc/bash_completion.d/ifdown.disabled by ifupdown2
  diversion of /usr/share/man/man8/ifup.8.gz to 
/usr/share/man/man8/ifup.8.gz.disabled by ifupdown2
  diversion of /usr/share/man/man8/ifquery.8.gz to 
/usr/share/man/man8/ifquery.8.gz.disabled by ifupdown2
  diversion of /usr/share/bash-completion/completions/ifquery to 
/usr/share/bash-completion/completions/ifquery.disabled by ifupdown2
  diversion of /usr/share/bash-completion/completions/ifdown to 
/usr/share/bash-completion/completions/ifdown.disabled by ifupdown2
  diversion of /sbin/ifquery to /sbin/ifquery.disabled by ifupdown2
  diversion of /sbin/ifdown to /sbin/ifdown.disabled by ifupdown2
  diversion of /etc/bash_completion.d/ifup to 
/etc/bash_completion.d/ifup.disabled by ifupdown2
  diversion of /sbin/ifup to /sbin/ifup.disabled by ifupdown2
  diversion of /usr/share/man/man5/interfaces.5.gz to 
/usr/share/man/man5/interfaces.5.gz.disabled by ifupdown2
  diversion of /usr/share/man/man8/ifreload.8.gz to 
/usr/share/man/man8/ifreload.8.gz.disabled by ifupdown2
  diversion of /usr/share/man/man8/ifdown.8.gz to 
/usr/share/man/man8/ifdown.8.gz.disabled by ifupdown2
  diversion of /usr/share/bash-completion/completions/ifreload to 
/usr/share/bash-completion/completions/ifreload.disabled by ifupdown2
  diversion of /etc/bash_completion.d/ifquery to 
/etc/bash_completion.d/ifquery.disabled by ifupdown2
  diversion of /etc/bash_completion.d/ifreload to 
/etc/bash_completion.d/ifreload.disabled by ifupdown2
  diversion of /usr/share/bash-completion/completions/ifup to 
/usr/share/bash-completion/completions/ifup.disabled by ifupdown2


If these diversions were used in stretch, but not afterwards, 
you should remove them in the postinst script, i.e. on package upgrade.


cheers,

Andreas


ifupdown2_1.2.2-1.log.gz
Description: application/gzip

Bug#919442: python-dmidecode-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: python-dmidecode-dbg
Version: 3.12.2-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  stretch -> buster

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m37.0s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/python-dmidecode-dbg/AUTHORS (python-dmidecode-dbg) != 
/usr/share/doc/python-dmidecode/AUTHORS (python-dmidecode)
/usr/share/doc/python-dmidecode-dbg -> python-dmidecode
  /usr/share/doc/python-dmidecode-dbg/AUTHORS.upstream (python-dmidecode-dbg) 
!= /usr/share/doc/python-dmidecode/AUTHORS.upstream (python-dmidecode)
/usr/share/doc/python-dmidecode-dbg -> python-dmidecode
  /usr/share/doc/python-dmidecode-dbg/README (python-dmidecode-dbg) != 
/usr/share/doc/python-dmidecode/README (python-dmidecode)
/usr/share/doc/python-dmidecode-dbg -> python-dmidecode
  /usr/share/doc/python-dmidecode-dbg/README.types (python-dmidecode-dbg) != 
/usr/share/doc/python-dmidecode/README.types (python-dmidecode)
/usr/share/doc/python-dmidecode-dbg -> python-dmidecode
  /usr/share/doc/python-dmidecode-dbg/README.upstream.gz (python-dmidecode-dbg) 
!= /usr/share/doc/python-dmidecode/README.upstream.gz (python-dmidecode)
/usr/share/doc/python-dmidecode-dbg -> python-dmidecode
  /usr/share/doc/python-dmidecode-dbg/changelog.Debian.gz 
(python-dmidecode-dbg) != /usr/share/doc/python-dmidecode/changelog.Debian.gz 
(python-dmidecode)
/usr/share/doc/python-dmidecode-dbg -> python-dmidecode
  /usr/share/doc/python-dmidecode-dbg/changelog.gz (python-dmidecode-dbg) != 
/usr/share/doc/python-dmidecode/changelog.gz (python-dmidecode)
/usr/share/doc/python-dmidecode-dbg -> python-dmidecode
  /usr/share/doc/python-dmidecode-dbg/copyright (python-dmidecode-dbg) != 
/usr/share/doc/python-dmidecode/copyright (python-dmidecode)
/usr/share/doc/python-dmidecode-dbg -> python-dmidecode


cheers,

Andreas


python-dmidecode-dbg_3.12.2-6.log.gz
Description: application/gzip

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

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 23:19:38 +
with message-id 
and subject line Bug#919376: fixed in ncmpc 0.33-2
has caused the Debian Bug report #919376,
regarding ncmpc: 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.)


-- 
919376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919376
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ncmpc
Version: 0.33-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with sphinxdoc
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
-Dartist_screen=true \
-Dasync_connect=true \
-Dcolors=true \
-Dchat_screen=true \
-Dcurses=ncursesw \
-Ddocumentation=auto \
-Dkey_screen=true \

[... snipped ...]

Installing /<>/doc/keys.sample to 
/<>/debian/tmp/usr/share/doc/ncmpc
Installing /<>/doc/ncmpc.lirc to 
/<>/debian/tmp/usr/share/doc/ncmpc
Running custom install script '/usr/bin/meson --internal gettext install 
--subdir=po --localedir=share/locale --pkgname=ncmpc'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
# Remove useless doc files
rm -rf debian/ncmpc/usr/share/doc/ncmpc/COPYING
rm -rf debian/ncmpc/usr/share/doc/ncmpc/NEWS
#TODO: move mkdir to dh *.dirs files?
mkdir -p debian/ncmpc/usr/share/doc/ncmpc/examples
mv  debian/ncmpc/usr/share/doc/ncmpc/*sample \
debian/ncmpc/usr/share/doc/ncmpc/*.lirc \
debian/ncmpc/usr/share/doc/ncmpc/examples
mv: cannot stat 'debian/ncmpc/usr/share/doc/ncmpc/*sample': No such file or 
directory
mv: cannot stat 'debian/ncmpc/usr/share/doc/ncmpc/*.lirc': No such file or 
directory
make[1]: *** [debian/rules:42: override_dh_install] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: 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.

Please consider uploading in source-only form (dpkg-buildpackage -S) so that 
these
kind of bugs are less likely to propagate to testing.

Thanks.
--- End Message ---
--- Begin Message ---
Source: ncmpc
Source-Version: 0.33-2

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

Debian distribution maintenance software
pp.
Geoffroy Youri Berret  (supplier of updated ncmpc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Jan 2019 16:53:45 +0100
Source: ncmpc
Binary: ncmpc ncmpc-lyrics
Architecture: source
Version: 0.33-2
Distribution: unstable
Urgency: medium
Maintainer: mpd maintainers 
Changed-By: Geoffroy Youri Berret 
Description:
 ncmpc  - ncurses-based audio player
 ncmpc-lyrics - ncurses-based audio player (lyrics plugins)
Closes: 919376
Changes:
 ncmpc (0.33-2) unstable; urgency=medium
 .
   * Install examples with dh, fixes FTBS (Closes: #919376)
Checksums-Sha1:
 e2b7ef0b2c46bfa2c0257e3186a779dec8e95ec6 2342 ncmpc_0.33-2.dsc
 f7d206524c8a7b816d161fa1f365666c48458a51 16396 ncmpc_0.33-2.debian.tar.xz
 138bc0c838b8ef9b9b2ad882690556b761cc130f 8020 ncmpc_0.33-2_amd64.buildinfo
Checksums-Sha256:
 7ad01c475062046ee63f60b65ed5a213d4d06651ba8743003c4d2ac7354b05de 2342 
ncmpc_0.33-2.dsc
 a691899d0eeb891212c1e312aa17d4d3b393f6d4312c511a61e54bd4a0888d97 16396 
ncmpc_0.33-2.debian.tar.xz
 9fe53198008303d7a823934a1afbfa32a37d8ed5960a8690328fa020d59a65d0 8020 
ncmpc_0.33-2_amd64.buildinfo
Files:
 cb3a8d5b442fb464909343dc3790dd8e 2342 sound optional ncmpc_0.33-2.dsc
 

Processed: Re: Bug#905200 closed by Yangfl ()

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #905200 {Done: Yangfl } [natpmp-utils,libnatpmp-dev] 
natpmp-utils,libnatpmp-dev: unhandled symlink to directory conversion: 
/usr/share/doc/PACKAGE
Bug reopened
Ignoring request to alter fixed versions of bug #905200 to the same values 
previously set
> found -1 20150609-6
Bug #905200 [natpmp-utils,libnatpmp-dev] natpmp-utils,libnatpmp-dev: unhandled 
symlink to directory conversion: /usr/share/doc/PACKAGE
Marked as found in versions libnatpmp/20150609-6.

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

Bug#905200: closed by Yangfl ()

[Andreas Beckmann]

Control: reopen -1
Control: found -1 20150609-6

On 2019-01-06 17:45, Debian Bug Tracking System wrote:
> This should have been fixed: natpmp-utils gets maintscript and
> libnatpmp-dev gets its symlink back

The .maintscript does not work thanks to a completely bogus version.

Please bump the version in the .maintscript to 20150609-7~
with your next upload (which will probably be 20150609-7)


>From the dpkg-maintscript-helper manpage:

   prior-version
  Defines the latest version of the package whose upgrade
should trigger the operation. It is important to calculate prior-version
correctly so that the operations are correctly  performed  even
  if  the  user  rebuilt  the  package with a local version.
If prior-version is empty or omitted, then the operation is tried on
every upgrade (note: it's safer to give the version and have the
  operation tried only once).

  If the conffile has not been shipped for several versions,
and you are now modifying the maintainer scripts to clean up the
obsolete file, prior-version should be based on the version  of  the
  package that you are now preparing, not the first version
of the package that lacked the conffile. This applies to all other
actions in the same way.

  For  example,  for  a  conffile  removed  in version 2.0-1
of a package, prior-version should be set to 2.0-1~. This will cause the
conffile to be removed even if the user rebuilt the previous
  version 1.0-1 as 1.0-1local1. Or a package switching a
path from a symlink (shipped in version 1.0-1) to a directory (shipped
in version 2.0-1), but only performing the actual  switch  in  the
  maintainer scripts in version 3.0-1, should set
prior-version to 3.0-1~.


Andreas

Processed: Re: Bug#919397: apcalc FTBFS on 32bit big endian

[Debian Bug Tracking System]

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

> tags 919397 pending
Bug #919397 [src:apcalc] apcalc FTBFS on 32bit big endian
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#919397: apcalc FTBFS on 32bit big endian

[Martin Buck]

tags 919397 pending
thanks


Thanks for your report. I already noticed the problem and a fix is in the
pipeline.

Martin


On Tue, Jan 15, 2019 at 04:31:30PM +0200, Adrian Bunk wrote:
> Source: apcalc
> Version: 2.12.7.2-1
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/package.php?p=apcalc
> 
> ...
> In file included from qmath.h:32,
>  from cmath.h:32,
>  from value.h:33,
>  from calc.h:33,
>  from file.c:39:
> file.c: In function 'filepos2z':
> zmath.h:85:46: error: incompatible types when assigning to type 'HALF' {aka 
> 'long unsigned int'} from type 'FILEPOS' {aka 'struct _G_fpos_t'}
>  #define SWAP_HALF_IN_B32(dest, src) (*(dest) = *(src))
>   ^
> fposval.h:15:42: note: in expansion of macro 'SWAP_HALF_IN_B32'
>  #define SWAP_HALF_IN_FILEPOS(dest, src)  SWAP_HALF_IN_B32(dest, src)
>   ^~~~
> file.c:1370:2: note: in expansion of macro 'SWAP_HALF_IN_FILEPOS'
>   SWAP_HALF_IN_FILEPOS(ret.v, );
>   ^~~~
> make[1]: *** [Makefile:2364: file.o] Error 1

Bug#919376: Bug #919376 in ncmpc marked as pending

[Florian Schlichting]

Control: tag -1 pending

Hello,

Bug #919376 in ncmpc 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/mpd-team/ncmpc/commit/e56e14b24c3469d40e025819f2aa152f6a4f8916


Install examples with dh, fixes FTBS

Closes: #919376


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/919376

Processed: Bug #919376 in ncmpc marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #919376 [src:ncmpc] ncmpc: FTBFS when built with dpkg-buildpackage -A
Added tag(s) pending.

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

Bug#919438: libgsm1-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: libgsm1-dev
Version: 1.0.18-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  stretch -> buster

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m26.1s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libgsm1-dev/MACHINES (libgsm1-dev:amd64) != 
/usr/share/doc/libgsm1/MACHINES (libgsm1:amd64)
/usr/share/doc/libgsm1-dev -> libgsm1
  /usr/share/doc/libgsm1-dev/README (libgsm1-dev:amd64) != 
/usr/share/doc/libgsm1/README (libgsm1:amd64)
/usr/share/doc/libgsm1-dev -> libgsm1
  /usr/share/doc/libgsm1-dev/changelog.Debian.gz (libgsm1-dev:amd64) != 
/usr/share/doc/libgsm1/changelog.Debian.gz (libgsm1:amd64)
/usr/share/doc/libgsm1-dev -> libgsm1
  /usr/share/doc/libgsm1-dev/changelog.gz (libgsm1-dev:amd64) != 
/usr/share/doc/libgsm1/changelog.gz (libgsm1:amd64)
/usr/share/doc/libgsm1-dev -> libgsm1
  /usr/share/doc/libgsm1-dev/copyright (libgsm1-dev:amd64) != 
/usr/share/doc/libgsm1/copyright (libgsm1:amd64)
/usr/share/doc/libgsm1-dev -> libgsm1


cheers,

Andreas


libgsm1-dev_1.0.18-1.log.gz
Description: application/gzip

Bug#919429: marked as done (displaycal: removal of displaycal makes files disappear from dispcalgui)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 22:21:01 +
with message-id 
and subject line Bug#919429: fixed in displaycal 3.7.1.3-5
has caused the Debian Bug report #919429,
regarding displaycal: removal of displaycal makes files disappear from 
dispcalgui
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.)


-- 
919429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: displaycal
Version: 3.7.1.3-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

The installation sequence to reproduce this problem is

  apt-get install dispcalgui/stretch
  # (1)
  apt-get install displaycal/buster
  apt-get remove displaycal
  # (2)

The list of installed files at points (1) and (2) should be identical,
but the following files have disappeared:

  /etc/xdg/autostart/z-displaycal-apply-profiles.desktop owned by: 
displaycal
  /usr/bin/displaycalowned by: displaycal
  /usr/bin/displaycal-3dlut-makerowned by: displaycal
  /usr/bin/displaycal-apply-profiles owned by: displaycal
  /usr/bin/displaycal-curve-viewer   owned by: displaycal
  /usr/bin/displaycal-profile-info   owned by: displaycal
...
  /usr/share/man/man1/displaycal-scripting-client.1.gz   owned by: displaycal
  /usr/share/man/man1/displaycal-synthprofile.1.gz   owned by: displaycal
  /usr/share/man/man1/displaycal-testchart-editor.1.gz   owned by: displaycal
  /usr/share/man/man1/displaycal-vrml-to-x3d-converter.1.gz  owned by: 
displaycal
  /usr/share/man/man1/displaycal.1.gzowned by: displaycal


This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
and also see the footnote that describes this incorrect behavior:
https://www.debian.org/doc/debian-policy/ch-relationships.html#id13

The displaycal package has the following relationships with dispcalgui:

  Conflicts: n/a
  Breaks:n/a
  Replaces:  dispcalgui

Since dispcalgui is a transitional package since 3.6.1.0-1
you should add/update
  Breaks+Replaces: dispcalgui (<< 3.6.1.0)
in the displaycal package.


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

0m41.7s ERROR: FAIL: After purging files have disappeared:
  /etc/xdg/autostart/z-displaycal-apply-profiles.desktop owned by: 
displaycal
  /usr/bin/displaycalowned by: displaycal
  /usr/bin/displaycal-3dlut-makerowned by: displaycal
  /usr/bin/displaycal-apply-profiles owned by: displaycal
  /usr/bin/displaycal-curve-viewer   owned by: displaycal
  /usr/bin/displaycal-profile-info   owned by: displaycal
...
  /usr/share/man/man1/displaycal-scripting-client.1.gz   owned by: displaycal
  /usr/share/man/man1/displaycal-synthprofile.1.gz   owned by: displaycal
  /usr/share/man/man1/displaycal-testchart-editor.1.gz   owned by: displaycal
  /usr/share/man/man1/displaycal-vrml-to-x3d-converter.1.gz  owned by: 
displaycal
  /usr/share/man/man1/displaycal.1.gzowned by: displaycal

0m41.7s ERROR: FAIL: After purging files have been modified:
  /etc/mailcap   not owned
  /var/lib/dpkg/info/dispcalgui.list not owned


cheers,

Andreas


dispcalgui=3.2.2.0-1_displaycal=3.7.1.3-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: displaycal
Source-Version: 3.7.1.3-5

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

Debian distribution maintenance software
pp.
Christian Marillat  (supplier of updated displaycal 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Jan 2019 23:08:26 +0100
Source: displaycal
Binary: displaycal dispcalgui
Architecture: source all amd64
Version: 3.7.1.3-5
Distribution: unstable
Urgency: medium
Maintainer: Christian 

Processed: Re: Bug#717636: latex-sanskrit package

[Debian Bug Tracking System]

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

> reassign 717636 texlive-lang-other
Bug #717636 [texlive-lang-indic] [latex-sanskrit] Package contain type1 
startlock fragment from black book
Bug reassigned from package 'texlive-lang-indic' to 'texlive-lang-other'.
No longer marked as found in versions texlive-lang/2014.20141024-1.
Ignoring request to alter fixed versions of bug #717636 to the same values 
previously set
> found 717636 2018.20181214-1
Bug #717636 [texlive-lang-other] [latex-sanskrit] Package contain type1 
startlock fragment from black book
Marked as found in versions texlive-lang/2018.20181214-1.
> stop
Stopping processing here.

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

Processed: tagging 919249

[Debian Bug Tracking System]

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

> tags 919249 + upstream
Bug #919249 {Done: Christopher Knadle } [mumble] 
security issue: instability and crash due to crafted message flooding
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#717636: latex-sanskrit package

[Hilmar Preuße]

reassign 717636 texlive-lang-other
found 717636 2018.20181214-1
stop

On 13.10.14 13:34, intrigeri wrote:

> On current sid, with texlive-lang-indic installed:
> 
> $ t1disasm 
> /usr/share/texlive/texmf-dist/fonts/type1/public/sanskrit/sktb10.pfb  | grep 
> start
> dup 3 {systemdict /internaldict known not {pop 3} {1183615869 systemdict 
> /internaldict get exec dup /startlock known {/startlock get exec} {dup 
> /strtlck known {/strtlck get exec} {pop 3} ifelse} ifelse} ifelse} 
> executeonly put
> 
Still there:

root@amd64-sid:~# t1disasm
/usr/share/texlive/texmf-dist/fonts/type1/public/sanskrit-t1/sktb10.pfb
|grep start
dup 3 {systemdict /internaldict known not {pop 3} {1183615869 systemdict
/internaldict get exec dup /startlock known {/startlock get exec} {dup
/strtlck known {/strtlck get exec} {pop 3} ifelse} ifelse} ifelse}
executeonly put

found and reassign.

H.
-- 
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Bug#919307: marked as done (casacore-data: Depends: casacore-data-jplde but it is not installable)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 22:04:26 +
with message-id 
and subject line Bug#919307: fixed in casacore-data 1.2
has caused the Debian Bug report #919307,
regarding casacore-data: Depends: casacore-data-jplde but it is not installable
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.)


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

The following packages have unmet dependencies:
 casacore-data : Depends: casacore-data-jplde but it is not installable


src:casacore-data-jplde builds casacore-data-jpl-de200
and casacore-data-jpl-de405 but no casacore-data-jplde
binary package.
--- End Message ---
--- Begin Message ---
Source: casacore-data
Source-Version: 1.2

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated casacore-data 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, 14 Jan 2019 20:52:33 +0100
Source: casacore-data
Binary: casacore-data
Architecture: source
Version: 1.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Description:
 casacore-data - Data for Common Astronomy Software Applications core library
Closes: 919307
Changes:
 casacore-data (1.2) unstable; urgency=medium
 .
   * Fix JPLDE dependencies (Closes: #919307)
Checksums-Sha1:
 d01cfef6080de5f83fdda95db6542dbe2ff232b2 1710 casacore-data_1.2.dsc
 107bd8d9ff4e9eb91f60d2616ffc6f7ba6495321 4144 casacore-data_1.2.tar.xz
Checksums-Sha256:
 8a458c863921217d2df20177f8b766436f3873f40e478185d0659ec21e6da4c1 1710 
casacore-data_1.2.dsc
 8139c67a00884f3d8b935bf3626c6700d284c840ca1f5f51a82acfde77c0abf2 4144 
casacore-data_1.2.tar.xz
Files:
 51ff4cba1b79f70d7564f0fb0639848d 1710 metapackages optional 
casacore-data_1.2.dsc
 71d7a92a847bea7ed67371abeeced5b2 4144 metapackages optional 
casacore-data_1.2.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAlw+U8kACgkQcRWv0HcQ
3PcCMw//TNcNHT1io5d1iJJ8r+Fde6UueuzkVG51WqJ6qmKhKegxVphrUDVUxfrg
PUaCVQmoMm/p8JyxryuUOJ4iUGaTtW1rka50tiRFUiueXZ1OCNCYmFDqYNtWy+j8
88ge++cGQjAXdD5dxNI5UtFmKAbduSnXomXDKIqAMT/fpcEouRCOx/kiysaw4W0W
11gswL+sRUvnmZdcheraPGJO0HR/SzU8+DLoQ/hfYp31USkImO1FTUblH5WrXelO
IPqOBIngnedrhDKAGEG6kExdQyWvcm0Z1VVPLpgMAgx6k64t+8/1xZ0sqNC84Zwf
w7omZPYbMgnL0y0S+ZytnwZ5RN6fCdKCEW4T5oHbS9TCvC1LvfLHXaAhHBfPAOah
6eL4v7BDLrQuTIagh4XKRJ9ewo3fNQb6/dA49oqGOqJc6BTsqvneNQynIPF8SfXz
lTfKPFibz3EnDWjuUsbDeihtq8TW8XMaZLlE+R8H+Cbp5q2L/sPdM1Ry81ORW2Ua
r9PYazIGv1upu1EDwgWNq8/hngBPln92/fRWBK7+Q1HkHKq46JQ6Ovot6YsnsqiK
zal8dFtAoKMEUTHgy5nV4/PVp1y+Cu2dNG62wNePR3iklslNZrv7iPZVR88Vu2r9
QydjviKkN0EmbwCF7KMoYWd6XVl4hUWLpw5wEs6DqDLp1/37bIk=
=PYk6
-END PGP SIGNATURE End Message ---

Bug#919001: marked as done (emacspeak: fails to upgrade with emacs 1.26.1+1-3)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 21:19:41 +
with message-id 
and subject line Bug#919001: fixed in emacspeak 49.0+dfsg-2
has caused the Debian Bug report #919001,
regarding emacspeak: fails to upgrade with emacs 1.26.1+1-3
to be marked as done.

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

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


-- 
919001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs-gtk
Version: 1:25.2+1-11
Severity: important

Dear Maintainer,

when trying to upgrade emacs to 1.26.1+1-3, some installation script fails with 
following error:

Preparing to unpack .../emacs-gtk_1%3a26.1+1-3_amd64.deb ...
Remove elpa-pdf-tools for emacs
remove/pdf-tools-0.80: Handling removal of emacsen flavor emacs
dh-elpa: purging flavor specific files for emacs
Remove flim for emacs
remove/flim: purging byte-compiled files for emacs
Remove w3m-el for emacs
remove/w3m-el: purging byte-compiled files for emacs
Remove elpa-jabber for emacs
remove/jabber-0.8.92: Handling removal of emacsen flavor emacs
dh-elpa: purging flavor specific files for emacs
Remove elpa-yasnippet-snippets for emacs
remove/yasnippet-snippets-0.7: Handling removal of emacsen flavor emacs
dh-elpa: purging flavor specific files for emacs
Remove mew for emacs
remove/mew: purging byte-compiled files for emacs
Remove elpa-tablist for emacs
remove/tablist-0.70: Handling removal of emacsen flavor emacs
dh-elpa: purging flavor specific files for emacs
Remove global for emacs
remove/global: Handling removal of emacsen flavor emacs
Remove gnuserv for emacs
Remove elpa-debian-el for emacs
remove/debian-el-37: Handling removal of emacsen flavor emacs
dh-elpa: purging flavor specific files for emacs
Remove riece for emacs
Remove elpa-systemd for emacs
remove/systemd-1.6: Handling removal of emacsen flavor emacs
dh-elpa: purging flavor specific files for emacs
Remove vm for emacs
remove/vm: Removing for 
emacs.../usr/share/emacs/site-lisp/vm/.../usr/share/emacs/site-lisp/vm.in... 
done.
Remove howm for emacs
remove/howm-1.4.4: Handling removal of emacsen flavor emacs
dh-elpa: purging flavor specific files for emacs
Remove slime for emacs
remove/slime-2.23: Handling removal of emacsen flavor emacs
dh-elpa: purging flavor specific files for emacs
Remove apel for emacs
remove/apel: purging byte-compiled files for emacs
Remove elpa-fsm for emacs
remove/fsm-0.2.1: Handling removal of emacsen flavor emacs
dh-elpa: purging flavor specific files for emacs
Remove elpa-restart-emacs for emacs
remove/restart-emacs-0.1.1: Handling removal of emacsen flavor emacs
dh-elpa: purging flavor specific files for emacs
Remove dictionaries-common for emacs
Remove elpa-yasnippet for emacs
remove/yasnippet-0.13.0: Handling removal of emacsen flavor emacs
dh-elpa: purging flavor specific files for emacs
Remove maxima-emacs for emacs
Remove elpa-let-alist for emacs
remove/let-alist-1.0.5: Handling removal of emacsen flavor emacs
dh-elpa: purging flavor specific files for emacs
Remove elpa-no-littering for emacs
remove/no-littering-1.0.0: Handling removal of emacsen flavor emacs
dh-elpa: purging flavor specific files for emacs
Remove mu4e for emacs
Remove cdargs for emacs
remove/cdargs: Handling removal of emacsen flavor emacs
remove/cdargs: purging byte-compiled files for emacs
Remove dictem for emacs
Remove elpa-with-editor for emacs
remove/with-editor-2.6.0: Handling removal of emacsen flavor emacs
dh-elpa: purging flavor specific files for emacs
Remove cmake-data for emacs
Remove why3 for emacs
Remove emacspeak for emacs
remove/emacspeak: purging byte-compiled files for emacs
rm: missing operand
Try 'rm --help' for more information.
ERROR: remove script from emacspeak package failed
dpkg: warning: old emacs-gtk package pre-removal script subprocess returned 
error exit status 1
dpkg: trying script from the new package instead ...
Remove elpa-pdf-tools for emacs
remove/pdf-tools-0.80: Handling removal of emacsen flavor emacs
dh-elpa: purging flavor specific files for emacs
Remove elpa-yasnippet-snippets for emacs
remove/yasnippet-snippets-0.7: Handling removal of emacsen flavor emacs
dh-elpa: purging flavor specific files for emacs
Remove w3m-el for emacs
remove/w3m-el: purging byte-compiled files for emacs
Remove flim for emacs
remove/flim: purging byte-compiled files for emacs
Remove elpa-jabber for emacs
remove/jabber-0.8.92: Handling removal of emacsen flavor emacs
dh-elpa: purging flavor specific files for emacs
Remove elpa-systemd for emacs
remove/systemd-1.6: Handling removal of emacsen flavor emacs
dh-elpa: purging flavor specific files for 

Processed: emacspeak

[Debian Bug Tracking System]

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

> tags 919001 pending
Bug #919001 [emacspeak] emacspeak: fails to upgrade with emacs 1.26.1+1-3
Added tag(s) pending.
> tags 919427 pending
Bug #919427 [emacspeak] emacspeak eterm  does not speak several key commands
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: libopenmpi-dev: fails to upgrade from 'stretch': new libopenmpi-dev package pre-installation script subprocess returned error exit status 2

[Debian Bug Tracking System]

Processing control commands:

> found -1 3.1.3-9
Bug #915025 {Done: Alastair McKinstry } [libopenmpi-dev] 
libopenmpi-dev: fails to upgrade from 'stretch': new libopenmpi-dev package 
pre-installation script subprocess returned error exit status 2
Marked as found in versions openmpi/3.1.3-9 and reopened.

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

Bug#915025: libopenmpi-dev: fails to upgrade from 'stretch': new libopenmpi-dev package pre-installation script subprocess returned error exit status 2

[Andreas Beckmann]

Followup-For: Bug #915025
Control: found -1 3.1.3-9

  Preparing to unpack .../45-libopenmpi-dev_3.1.3-9_amd64.deb ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-bUBTzo/45-libopenmpi-dev_3.1.3-9_amd64.deb (--unpack):
   new libopenmpi-dev package pre-installation script subprocess returned error 
exit status 2
  update-alternatives: using /usr/lib/x86_64-linux-gnu/openmpi/include to 
provide /usr/include/mpi (mpi) in auto mode


Andreas


libopenmpi-dev_3.1.3-9.log.gz
Description: application/gzip

Bug#919429: displaycal: removal of displaycal makes files disappear from dispcalgui

[Andreas Beckmann]

Package: displaycal
Version: 3.7.1.3-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

The installation sequence to reproduce this problem is

  apt-get install dispcalgui/stretch
  # (1)
  apt-get install displaycal/buster
  apt-get remove displaycal
  # (2)

The list of installed files at points (1) and (2) should be identical,
but the following files have disappeared:

  /etc/xdg/autostart/z-displaycal-apply-profiles.desktop owned by: 
displaycal
  /usr/bin/displaycalowned by: displaycal
  /usr/bin/displaycal-3dlut-makerowned by: displaycal
  /usr/bin/displaycal-apply-profiles owned by: displaycal
  /usr/bin/displaycal-curve-viewer   owned by: displaycal
  /usr/bin/displaycal-profile-info   owned by: displaycal
...
  /usr/share/man/man1/displaycal-scripting-client.1.gz   owned by: displaycal
  /usr/share/man/man1/displaycal-synthprofile.1.gz   owned by: displaycal
  /usr/share/man/man1/displaycal-testchart-editor.1.gz   owned by: displaycal
  /usr/share/man/man1/displaycal-vrml-to-x3d-converter.1.gz  owned by: 
displaycal
  /usr/share/man/man1/displaycal.1.gzowned by: displaycal


This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
and also see the footnote that describes this incorrect behavior:
https://www.debian.org/doc/debian-policy/ch-relationships.html#id13

The displaycal package has the following relationships with dispcalgui:

  Conflicts: n/a
  Breaks:n/a
  Replaces:  dispcalgui

Since dispcalgui is a transitional package since 3.6.1.0-1
you should add/update
  Breaks+Replaces: dispcalgui (<< 3.6.1.0)
in the displaycal package.


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

0m41.7s ERROR: FAIL: After purging files have disappeared:
  /etc/xdg/autostart/z-displaycal-apply-profiles.desktop owned by: 
displaycal
  /usr/bin/displaycalowned by: displaycal
  /usr/bin/displaycal-3dlut-makerowned by: displaycal
  /usr/bin/displaycal-apply-profiles owned by: displaycal
  /usr/bin/displaycal-curve-viewer   owned by: displaycal
  /usr/bin/displaycal-profile-info   owned by: displaycal
...
  /usr/share/man/man1/displaycal-scripting-client.1.gz   owned by: displaycal
  /usr/share/man/man1/displaycal-synthprofile.1.gz   owned by: displaycal
  /usr/share/man/man1/displaycal-testchart-editor.1.gz   owned by: displaycal
  /usr/share/man/man1/displaycal-vrml-to-x3d-converter.1.gz  owned by: 
displaycal
  /usr/share/man/man1/displaycal.1.gzowned by: displaycal

0m41.7s ERROR: FAIL: After purging files have been modified:
  /etc/mailcap   not owned
  /var/lib/dpkg/info/dispcalgui.list not owned


cheers,

Andreas


dispcalgui=3.2.2.0-1_displaycal=3.7.1.3-4.log.gz
Description: application/gzip

Bug#919249: marked as done (security issue: instability and crash due to crafted message flooding)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 20:42:54 +
with message-id 
and subject line Bug#919249: fixed in mumble 1.3.0~git20190114.9fcc588+dfsg-1
has caused the Debian Bug report #919249,
regarding security issue: instability and crash due to crafted message flooding
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.)


-- 
919249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mumble
Version: 1.2.19-3
Severity: important
Tags: security fixed-upstream fixed-in-experimental


It is currently possible to cause mumble-server to freeze and/or crash by
sending specifically it crafted commands, leading to a denial of service.
The server usually automatically recovers, however it has been reported that
in some instances it can take up to an hour after the attack has ended.
The attack can be done remotely and does not need special permissions.

All versions of mumble 1.2.x and 1.3.0 snapshots prior to 2018-08-31 are 
affected.



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: mumble
Source-Version: 1.3.0~git20190114.9fcc588+dfsg-1

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

Debian distribution maintenance software
pp.
Christopher Knadle  (supplier of updated mumble 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 15 Jan 2019 05:53:33 +
Source: mumble
Binary: mumble mumble-server
Architecture: source
Version: 1.3.0~git20190114.9fcc588+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Christopher Knadle 
Changed-By: Christopher Knadle 
Description:
 mumble - Low latency encrypted VoIP client
 mumble-server - Low latency encrypted VoIP server
Closes: 874683 875058 915273 919249
Changes:
 mumble (1.3.0~git20190114.9fcc588+dfsg-1) unstable; urgency=medium
 .
   * New upstream git snapshot from 2019-01-14
 Fixes wishlist bug "mumble: please package a QT5 version of mumble"
 (Closes: #874683)
 Fixes "[mumble] Future Qt4 removal from Buster"
 (Closes: #875058)
 Thanks to Lisandro Damián Nicanor Pérez Meyer 
 for reporting the bug
 Fixes "mumble: sound glitches when starting mumble"
 (Closes: #915273)
 Thanks to Axel R.  for reporting the bug
 Fixes security issue: instability and crash due to crafted message flooding
 Thanks to "The Zom.bi Community" for reporting the bug and fixing the bug
 upstream
 (Closes: #919249)
   * debian/control:
 - Update Build-Depends to use Qt5 dependencies
 - Remove Suggests: dbus package for mumble-server
 - Add Suggests: libqt5sql5-sqlite for mumble-server
 - Update Standards-Version to 4.3.0 (no changes needed)
   * debian/copyright:
 - Add Files-Excluded section to document files removed from the upstream
   tarball for DFSG compliance.  [The removals are for draft IETF documents
   for CELT, Opus, Speex codecs that have a restrictive license.]
 - Update Source link to https://dl.mumble.info
 - Remove Files: macx/overlay/* section (code removed upstream)
 - Update copyright year for files in debian/*
   * debian/extras:
 - Add make-mumble-git-tarball.sh and murmur.ini.system.diff for
   creating a tarball from the git repository to allow verifying the
   tarball used in the package
   * debian/mumble-server.examples:
 - Update for file move in new version
   * debian/NEWS:
 - Add entry to describe new Perfect Forward Secrecy SSL support,
   tarball repack, and tarball PGP check removal
   * debian/patches:
 - Remove 05-lsb-description.diff (incorporated upstream)
 - Update 07-use-embedded-celt-baseline.diff for Mumble 1.3
 - Remove 12-mumble-server-disable-dbus-and-ice.diff,
   Add 12-disable-ice-by-default.diff to disable Ice by default
 - Remove 17-change-pulseaudio-role.diff (incorporated upstream)
 - Remove 19-move-xlib-initializtion-earlier.diff (incorporated upstream)
 - Remove 

Bug#918618: marked as done (golang-github-grpc-ecosystem-grpc-gateway FTBFS: github.com/grpc-ecosystem/grpc-gateway/runtime [build failed])

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 20:41:31 +
with message-id 
and subject line Bug#918618: fixed in golang-github-grpc-ecosystem-grpc-gateway 
1.6.4-1
has caused the Debian Bug report #918618,
regarding golang-github-grpc-ecosystem-grpc-gateway FTBFS: 
github.com/grpc-ecosystem/grpc-gateway/runtime [build failed]
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.)


-- 
918618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-grpc-ecosystem-grpc-gateway
Version: 1.3.0-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-grpc-ecosystem-grpc-gateway.html

...
# github.com/grpc-ecosystem/grpc-gateway/runtime_test 
[github.com/grpc-ecosystem/grpc-gateway/runtime.test]
src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:71:46: too few 
values in  literal
src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:72:47: too few 
values in  literal
src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:73:46: too few 
values in  literal
src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:74:46: too few 
values in  literal
src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:75:47: too few 
values in  literal
src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:76:47: too few 
values in  literal
src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:77:45: too few 
values in  literal
src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:78:47: too few 
values in  literal
src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:118:46: too 
few values in  literal
src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:119:47: too 
few values in  literal
src/github.com/grpc-ecosystem/grpc-gateway/runtime/query_test.go:119:47: too 
many errors
FAILgithub.com/grpc-ecosystem/grpc-gateway/runtime [build failed]
?   github.com/grpc-ecosystem/grpc-gateway/runtime/internal [no test files]
--- End Message ---
--- Begin Message ---
Source: golang-github-grpc-ecosystem-grpc-gateway
Source-Version: 1.6.4-1

We believe that the bug you reported is fixed in the latest version of
golang-github-grpc-ecosystem-grpc-gateway, which is due to be installed in the 
Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated 
golang-github-grpc-ecosystem-grpc-gateway package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Jan 2019 21:13:00 +0100
Source: golang-github-grpc-ecosystem-grpc-gateway
Binary: golang-github-grpc-ecosystem-grpc-gateway-dev golang-grpc-gateway
Architecture: source
Version: 1.6.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Dr. Tobias Quathamer 
Description:
 golang-github-grpc-ecosystem-grpc-gateway-dev - gRPC to JSON proxy generator 
for Golang -- sources
 golang-grpc-gateway - gRPC to JSON proxy generator for Golang -- binaries
Closes: 918618
Changes:
 golang-github-grpc-ecosystem-grpc-gateway (1.6.4-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Martín Ferrari ]
   * debian/control: Add missing dependency on genproto.
 .
   [ Alexandre Viau ]
   * Point Vcs-* urls to salsa.debian.org.
 .
   [ Dr. Tobias Quathamer ]
   * New upstream release 1.6.4 (Closes: #918618).
 - Add new dependency golang-github-ghodss-yaml-dev
   * Update d/watch
   * Use debhelper v11
   * Update team name
   * Update to Standards-Version 4.3.0
Checksums-Sha1:
 be9d5d319941644b0bda638813dd4352be7519b0 2752 
golang-github-grpc-ecosystem-grpc-gateway_1.6.4-1.dsc
 30e55b35c49eab4637713f93cf24dc103efa2184 273118 
golang-github-grpc-ecosystem-grpc-gateway_1.6.4.orig.tar.gz
 c50c1e5ef223c6633d453ac5eee34f1cf0107628 3788 
golang-github-grpc-ecosystem-grpc-gateway_1.6.4-1.debian.tar.xz
 6027978bb39bea927e60e456de192edde1ee0a7d 7207 
golang-github-grpc-ecosystem-grpc-gateway_1.6.4-1_amd64.buildinfo
Checksums-Sha256:
 2f0fadd47c572906b7875d2f5fea33e352bad0b153f63acef28978bf5e3b828f 

Bug#916468: whitedune: diff for NMU version 0.30.10-2.2

[Paul Gevers]

tags 916468 + patch
tags 916468 + pending

Dear maintainer,

I've prepared an NMU for whitedune (versioned as 0.30.10-2.2) and
uploaded it to DELAYED/10. Please feel free to tell me if I should delay
it longer. I have based my NMU on top of what is currently in the salsa
archive, so it includes a bit more than needed to fix this bug.

Regards.
Paul
diff -Nru whitedune-0.30.10/debian/changelog whitedune-0.30.10/debian/changelog
--- whitedune-0.30.10/debian/changelog  2016-03-07 17:19:38.0 +0100
+++ whitedune-0.30.10/debian/changelog  2019-01-15 20:45:29.0 +0100
@@ -1,3 +1,24 @@
+whitedune (0.30.10-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Johannes Brandstätter ]
+  * Update watch file to new upstream release page
+
+  [ Ondřej Nový ]
+  * d/control: Set Vcs-* to salsa.debian.org
+
+  [ Felipe Sateler ]
+  * Change maintainer address to debian-multime...@lists.debian.org
+
+  [ Ondřej Nový ]
+  * d/rules: Remove trailing whitespaces
+
+  [ Paul Gevers ]
+  * Drop /usr/bin/dune softlink (Closes: #916468)
+
+ -- Paul Gevers   Tue, 15 Jan 2019 20:45:29 +0100
+
 whitedune (0.30.10-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru whitedune-0.30.10/debian/control whitedune-0.30.10/debian/control
--- whitedune-0.30.10/debian/control2016-01-09 21:12:53.0 +0100
+++ whitedune-0.30.10/debian/control2019-01-15 20:45:29.0 +0100
@@ -1,7 +1,7 @@
 Source: whitedune
 Section: graphics
 Priority: optional
-Maintainer: Debian Multimedia Maintainers 

+Maintainer: Debian Multimedia Maintainers 
 Uploaders: Philippe Coval 
 Build-Depends:
  autoconf,
@@ -20,8 +20,8 @@
  x11proto-core-dev
 Standards-Version: 3.9.6
 Homepage: http://vrml.cip.ica.uni-stuttgart.de/dune/
-Vcs-Git: git://anonscm.debian.org/pkg-multimedia/whitedune.git
-Vcs-Browser: https://anonscm.debian.org/cgit/pkg-multimedia/whitedune.git
+Vcs-Git: https://salsa.debian.org/multimedia-team/whitedune.git
+Vcs-Browser: https://salsa.debian.org/multimedia-team/whitedune
 
 Package: whitedune
 Architecture: any
diff -Nru whitedune-0.30.10/debian/NEWS whitedune-0.30.10/debian/NEWS
--- whitedune-0.30.10/debian/NEWS   1970-01-01 01:00:00.0 +0100
+++ whitedune-0.30.10/debian/NEWS   2019-01-15 20:45:29.0 +0100
@@ -0,0 +1,6 @@
+whitedune (0.30.10-2.2) unstable; urgency=medium
+
+  The /usr/bin/dune softlink was dropped because there was a namespace
+clash.
+
+ -- Paul Gevers   Tue, 15 Jan 2019 20:42:23 +0100
diff -Nru whitedune-0.30.10/debian/rules whitedune-0.30.10/debian/rules
--- whitedune-0.30.10/debian/rules  2016-01-09 21:44:44.0 +0100
+++ whitedune-0.30.10/debian/rules  2019-01-15 20:45:29.0 +0100
@@ -113,6 +113,6 @@
dh_builddeb -a
 
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install 
+.PHONY: build clean binary-indep binary-arch binary install
 
 #eof "$Id: rules -- rzr $"
diff -Nru whitedune-0.30.10/debian/watch whitedune-0.30.10/debian/watch
--- whitedune-0.30.10/debian/watch  2016-01-09 16:22:17.0 +0100
+++ whitedune-0.30.10/debian/watch  2019-01-15 20:45:29.0 +0100
@@ -1,3 +1,3 @@
 version=3
-http://vrml.cip.ica.uni-stuttgart.de/dune/down.html \
-  http://129.69.35.12/dune/white_dune-(\d*\.\d*pl\d*)\.tar\.gz
+http://wdune.ourproject.org/ \
+  ftp://ftp.ourproject.org/pub/wdune/wdune-(\d*\.\d*pl\d*)\.tar\.bz2
diff -Nru whitedune-0.30.10/debian/whitedune.links 
whitedune-0.30.10/debian/whitedune.links
--- whitedune-0.30.10/debian/whitedune.links2016-01-09 16:40:49.0 
+0100
+++ whitedune-0.30.10/debian/whitedune.links1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
-/usr/bin/whitedune /usr/bin/dune


signature.asc
Description: OpenPGP digital signature

Processed (with 5 errors): whitedune: diff for NMU version 0.30.10-2.2

[Debian Bug Tracking System]

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

> tags 916468 + patch
Bug #916468 [whitedune] dune: /usr/bin/dune is already provided by the 
whitedune package
Added tag(s) patch.
> tags 916468 + pending
Bug #916468 [whitedune] dune: /usr/bin/dune is already provided by the 
whitedune package
Added tag(s) pending.
> Dear maintainer,
Unknown command or malformed arguments to command.
> I've prepared an NMU for whitedune (versioned as 0.30.10-2.2) and
Unknown command or malformed arguments to command.
> uploaded it to DELAYED/10. Please feel free to tell me if I should delay
Unknown command or malformed arguments to command.
> it longer. I have based my NMU on top of what is currently in the salsa
Unknown command or malformed arguments to command.
> archive, so it includes a bit more than needed to fix this bug.
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

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

Processed: severity of 919231 is serious

[Debian Bug Tracking System]

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

> severity 919231 serious
Bug #919231 [salt-master] salt-master: Upgrade Stretch -> Buster: permission 
denied on certain files/directories
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#892656: even more tests fail with version 2.0.2

[Paul Gevers]

Hi Paolo,

On 14-01-2019 08:24, Paolo Greppi wrote:
> Hi Paul, seems like npm registry now has is-descriptor 3.0.0:
> https://www.npmjs.com/package/is-descriptor
> 
> but even define-property 2.0.2 still wants is-descriptor 1.0.2:
> https://github.com/jonschlinkert/define-property/blob/master/package.json#L27
> 
> Now that we consider acceptable to embed tiny node modules (and is-descriptor 
> certainly is tiny) we have two options:
> 1. (old #3) downgrade node-is-descriptor to 1.0.2
> 2. remove node-is-descriptor 2.0.0 and embed is-descriptor 1.0.2 into 
> node-define-property

I hope you can make the call yourself as I am a mere bystander. But I do
want to get rid of RC bugs as they are delaying the release.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#919421: src:g810-led: FTBFS when /usr/bin/systemd-run isn't available

[Stephen Kitt]

Package: src:g810-led
Version: 0.3.1-1
Severity: serious
Justification: ftbfs

Dear Maintainer,

g810-led FTBFS when /usr/bin/systemd-run isn't available.

Regards,

The Maintainer


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

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

Bug#919419: yatex: hangs while installing along xemacs21

[Andreas Beckmann]

Package: yatex
Version: 1.81-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

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.

If yatex is installed in a piuparts chroot that has already xemacs21
installed, the installation will hand infinitely (until it is killed
by a timeout). All processes are idle, there does not seem to be a busy
loop involved:

root  9236 32750  0 18:28 pts/000:00:00 /usr/bin/dpkg --force-unsafe-io 
--status-fd 19 --configure --pending
root 11033  9236  0 18:28 pts/000:00:00 /bin/sh 
/var/lib/dpkg/info/yatex.postinst configure
root 11035 11033  0 18:28 pts/000:00:00 /usr/bin/perl -w 
/usr/lib/emacsen-common/emacs-package-install --postinst yatex
root 11057 11035  0 18:28 pts/000:00:00 [emacs-package-i] 
root 11148 11035  0 18:28 pts/000:00:00 /bin/bash -e 
/usr/lib/emacsen-common/packages/install/yatex xemacs21
root 11151 11148  0 18:28 pts/000:00:00 /bin/bash -e 
/usr/lib/emacsen-common/packages/install/yatex xemacs21
root 11152 11151  0 18:28 pts/000:00:00 xemacs21 -batch -no-site-file 
-no-init-file -l ./lp.el -e bcf-and-exit comment.el yatex.el yatexadd.el 
yatexgen.el yatexenv.el yatexlib.el yatexprc.el yatexmth.el yatexhks.el 
yatexhlp.el yatexm-o.el yatexsec.el yatexhie.el yahtml.el yatexpkg.el
root 11153 11151  0 18:28 pts/000:00:00 gzip -9qf

It has been in this state for 30 minutes now ...


cheers,

Andreas

Bug#915402: marked as done (esys-particle: FTBFS on mips/mipsel: OOM)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 18:34:29 +
with message-id 
and subject line Bug#915402: fixed in esys-particle 2.3.5+dfsg1-2.1
has caused the Debian Bug report #915402,
regarding esys-particle: FTBFS on mips/mipsel: OOM
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.)


-- 
915402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: esys-particle
Severity: serious
Version: 2.3.5+dfsg1-2

Dear maintainer,

https://buildd.debian.org/status/fetch.php?pkg=esys-particle=mips=2.3.5%2Bdfsg1-2%2Bb2=1542967319=0

as: out of memory allocating 32 bytes after a total of 562651136 bytes
/tmp/ccyqT2fq.s: Assembler messages:
/tmp/ccyqT2fq.s: Fatal error: can't close .libs/SubLatticeControler.o: memory 
exhausted
make[4]: *** [Makefile:637: SubLatticeControler.lo] Error 1
make[4]: Leaving directory '/<>/esys-particle-2.3.5+dfsg1/Parallel'
make[3]: *** [Makefile:459: all-recursive] Error 1
make[3]: Leaving directory '/<>/esys-particle-2.3.5+dfsg1'
make[2]: *** [Makefile:390: all] Error 2
make[2]: Leaving directory '/<>/esys-particle-2.3.5+dfsg1'
dh_auto_build: make V=1 -j2 returned exit code 2
make[1]: *** [debian/rules:30: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/esys-particle-2.3.5+dfsg1'
make: *** [debian/rules:6: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


https://buildd.debian.org/status/fetch.php?pkg=esys-particle=mipsel=2.3.5%2Bdfsg1-2%2Bb2=1543344040=0

as: out of memory allocating 32 bytes after a total of 564113408 bytes
/tmp/ccrXCjhb.s: Assembler messages:
/tmp/ccrXCjhb.s: Fatal error: can't close .libs/SubLatticeControler.o: memory 
exhausted
make[4]: *** [Makefile:637: SubLatticeControler.lo] Error 1
make[4]: Leaving directory '/<>/esys-particle-2.3.5+dfsg1/Parallel'
make[3]: *** [Makefile:459: all-recursive] Error 1
make[3]: Leaving directory '/<>/esys-particle-2.3.5+dfsg1'
make[2]: *** [Makefile:390: all] Error 2
make[2]: Leaving directory '/<>/esys-particle-2.3.5+dfsg1'
dh_auto_build: make V=1 -j4 returned exit code 2
make[1]: *** [debian/rules:30: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/esys-particle-2.3.5+dfsg1'
make: *** [debian/rules:6: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: esys-particle
Source-Version: 2.3.5+dfsg1-2.1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 01 Jan 2019 17:13:15 +0200
Source: esys-particle
Binary: esys-particle
Architecture: source
Version: 2.3.5+dfsg1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Adrian Bunk 
Description:
 esys-particle - Software for particle-based numerical modelling. MPI version.
Closes: 915402
Changes:
 esys-particle (2.3.5+dfsg1-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build with -g1 on mips/mipsel to work around address space
 limitations. (Closes: #915402)
Checksums-Sha1:
 5e7d043c2007421952641754c9a120ac001abbba 2380 esys-particle_2.3.5+dfsg1-2.1.dsc
 7844c803e440b72ad6b4f2b7bcae5f7bb4b42f4a 564912 
esys-particle_2.3.5+dfsg1-2.1.debian.tar.xz
Checksums-Sha256:
 3380e8775b66333b99239c2d4a12691aff5d3b2a87c52fa4c28630742ab4bcc9 2380 
esys-particle_2.3.5+dfsg1-2.1.dsc
 69419c9fa567cfe204525d600237539330ee11cfc22617a14fa62882598e9a02 564912 

Bug#919418: kuttypy: FTBFS in sid (pyuic5: Command not found)

[Santiago Vila]

Package: src:kuttypy
Version: 0.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python3
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   dh_auto_build -i
make -j1 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
?. Using QT Version: PyQt5 pyuic5 pyrcc5 pylupdate5 3
for d in utilities; do make PYUIC=pyuic5 PYRCC=pyrcc5 PYLUPDATE=pylupdate5 
PY_VERSION=3 -C $d all; done
make[2]: Entering directory '/<>/utilities'
for d in templates; do make -C $d all; done
make[3]: Entering directory '/<>/utilities/templates'
PYRCC=pyrcc5
pyuic5 --from-import dio.ui -o ui_dio.py
make[3]: pyuic5: Command not found
make[3]: *** [Makefile:26: ui_dio.py] Error 127
make[3]: Leaving directory '/<>/utilities/templates'
make[2]: *** [Makefile:6: recursive_all] Error 2
make[2]: Leaving directory '/<>/utilities'
make[1]: *** [Makefile:31: recursive_all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 "INSTALL=install --strip-program=true" returned exit 
code 2
make: *** [debian/rules:4: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


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

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

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

Thanks.

Bug#919167: tmuxp FTBFS and completely broken with python-click 7.0-1

[Fabian Grünbichler]

FWIW, this was reported upstream[0], and fixed[1], and released as part
of 1.5.0a. Either backporting the relevant changes from PR 434 or
updating to 1.5.0(a) seems like a good idea.

0: https://github.com/tmux-python/tmuxp/issues/433
1: https://github.com/tmux-python/tmuxp/pull/434
2: https://github.com/tmux-python/tmuxp/releases/tag/v1.5.0a

Processed: severity of 919249 is serious

[Debian Bug Tracking System]

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

> severity 919249 serious
Bug #919249 [mumble] security issue: instability and crash due to crafted 
message flooding
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#919103: fixed in libreoffice 1:6.1.4-4

[Cyril Brulebois]

Hi Rene,

Rene Engelhard  (2019-01-15):
>  libreoffice (1:6.1.4-4) unstable; urgency=medium
>  .
>* debian/control.in: bump recommends for apparmor to >= 2.13.1 and conflict
>  against apparmor (<< 2.13.1~) (closes: #918499)
>* debian/control.in, debian/rules: make apparmor recommends/conflicts
>  dependant on ENABLE_APPARMOR_PROFILES=y
>* debian/control.transitonals.in: add missing {misc:Depends} for -ogltrans
>* debian/control.kde*.in: Replaces: libreoffice-kde (<< 1:6.1.0~alpha1-1)
>  (closes: #919103)

FWIW, I've just confirmed that this makes the dist-upgrade successful
(trying an upgrade from stretch to unstable, instead of one from stretch
to buster, since libreoffice will need some time to build everywhere and
become a candidate for migration):

Result: KO RC=100 for 
cmd=/home/kibi/work/release-checks.git/scripts/upgrade-desktop-task stretch 
buster kde
Result: OK RC=0 for 
cmd=/home/kibi/work/release-checks.git/scripts/upgrade-desktop-task stretch 
unstable kde


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#919138: wpasupplicant: Fails to connect to some Wifi networks on version 2:2.7-3

[Ben Greear]

You might try adding this patch and disabling the oper-class IE:

http://lists.infradead.org/pipermail/hostap/2018-August/038792.html

I'd be curious to know if it fixes the problem.

Thanks,
Ben

On 1/14/19 4:35 PM, Different55 wrote:

On Monday, January 14, 2019 10:37 AM, Ben Greear  
wrote:


What is the model number of your home AP?

Thanks,
Ben


It is a Comtrend VR-3033




--
Ben Greear 
Candela Technologies Inc  http://www.candelatech.com

Bug#919415: isight-firmware-tools: Build-Depends on cruft package libgcrypt11-dev

[Andreas Beckmann]

Source: isight-firmware-tools
Version: 1.6-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

isight-firmware-tools build-depends on libgcrypt11-dev. This was a
transitional package, please use libgcrypt20-dev instead.

Andreas

Processed: Severity serious (keep xfce4-screensaver out of testing)

[Debian Bug Tracking System]

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

> severity 919348 serious
Bug #919348 [xfce4-screensaver] xfce4-screensaver: Accidental upload to 
unstable while fixing bug #919151
Ignoring request to change severity of Bug 919348 to the same value.
> thanks
Stopping processing here.

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

Processed: severity of 919277 is serious

[Debian Bug Tracking System]

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

> severity 919277 serious
Bug #919277 [uucp] postinst failed on the recent upgrade because it required 
update-inetd
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 919291 is serious

[Debian Bug Tracking System]

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

> severity 919291 serious
Bug #919291 [crash] crash: invalid kernel virtual address / crash: cannot 
allocate any more memory!
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#837361: marked as done (fsl: FTBFS with GCC 6: error: no match for 'operator>' (operand types are 'std::ifstream' and 'int'))

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 17:34:37 +
with message-id 
and subject line Bug#837361: fixed in fsl 5.0.8-6
has caused the Debian Bug report #837361,
regarding fsl: FTBFS with GCC 6: error: no match for 'operator>' (operand types 
are 'std::ifstream' and 'int')
to be marked as done.

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

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


-- 
837361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fsl
Version: 5.0.8-5
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

fsl FTBFS since the default compiler was switched to GCC 6:

[...]
g++ -g -O2 -fdebug-prefix-map=/build/fsl-5.0.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-DHAVE_LIBFREETYPE -fPIC -I/usr/include/nifti -I/usr/include/gifti -I/usr/i
nclude/newmat -I/build/fsl-5.0.8/extras/src/libprob 
-I/build/fsl-5.0.8/extras/src/libcprob -I/build/fsl-5.0.8/src   -O3 
-Wno-deprecated -ggdb -I/usr/include/newmat 
-I/build/fsl-5.0.8/extras/include/libprob -I/u
sr/include -I/usr/include -I/usr/include/libpng -I/usr/include -I. 
-I/build/fsl-5.0.8/include -I/build/fsl-5.0.8/include   -c -o meldata.o 
meldata.cc
meldata.cc: In member function 'void Melodic::MelodicData::est_smoothness()':
meldata.cc:997:12: error: no match for 'operator>' (operand types are 
'std::ifstream {aka std::basic_ifstream}' and 'int')
   if(in>0){
  ~~^~
[...]

(full log attached)

Andreas


fsl_5.0.8-5.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: fsl
Source-Version: 5.0.8-6

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated fsl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Jan 2019 16:42:15 +0100
Source: fsl
Binary: fsl fsl-5.0 fsl-core fsl-5.0-core
Architecture: source amd64 all
Version: 5.0.8-6
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Andreas Tille 
Description:
 fsl- transitional dummy package
 fsl-5.0- transitional dummy package
 fsl-5.0-core - analysis tools for FMRI, MRI and DTI brain imaging
 fsl-core   - metapackage for the latest version of FSL
Closes: 804881 837361 864178
Changes:
 fsl (5.0.8-6) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Yaroslav Halchenko ]
   * Add 'file' to Depends of fsl-5.0-core. Required by fslFixText utility
   * debian/fsl.sh - place FSL's bin path first (not the last) within adjusted
 $PATH (Closes: #804881)
   * debian/patches/up_in_compar to fix FTBFS of melodic on 17.04
 Closes: #837361
 .
   [ Michael Hanke ]
   * Move 'fslview' from a dependency into suggests. It can no longer be
 built in Debian unstable.
 Closes: #864178
 .
   [ Andreas Tille ]
   * Replace watch line pointing to alioth which does not exist any more
 by fake watch file
   * debhelper 9
   * Point Vcs fields to salsa.debian.org
   * Standards-Version: 4.3.0
   * Fix call of overloaded 'round(float)' is ambiguous
   * Silence lintian about false positive spelling
   * fsl-5.0-core Depends: sensible-utils
   * Drop Encoding key from desktop file
   * Drop Debian menu file (since there is a desktop file)
   * hardening=+all
Checksums-Sha1:
 6e8a1fb0f0cc2a1558a1b7fa8bd00b1627bc6a8c 2421 fsl_5.0.8-6.dsc
 370cf2cb97ebb6d0a2b47a725054a5c411b068ea 42616 fsl_5.0.8-6.debian.tar.xz
 f539df5deca892fae38eaacee33dc9fead684c3a 153645380 
fsl-5.0-core-dbgsym_5.0.8-6_amd64.deb
 17300011f64f941bdd5c3ed27def50658dc888e2 8365888 fsl-5.0-core_5.0.8-6_amd64.deb
 2811268688cb53b220c2acf8cb1ef60720cb0f48 20028 fsl-5.0_5.0.8-6_all.deb
 3ef31da705273ee0880e6f04ca59b5fdc2358cfb 21192 fsl-core_5.0.8-6_all.deb
 edba08409ceabe90ecd0dec4c5837d259cf83dbd 21560 fsl_5.0.8-6_all.deb
 d4a008c2509ff77e7db0268520bb8d06f42bd560 14675 fsl_5.0.8-6_amd64.buildinfo
Checksums-Sha256:
 2de76e045a975189b5d44d229cd1130edba9b18621f74be1084a8e8a7dbada20 2421 

Bug#864178: marked as done (fsl-5.0-core: depends on no longer available fslview)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 17:34:38 +
with message-id 
and subject line Bug#864178: fixed in fsl 5.0.8-6
has caused the Debian Bug report #864178,
regarding fsl-5.0-core: depends on no longer available fslview
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.)


-- 
864178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fsl-5.0-core
Version: 5.0.8-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

The following packages have unmet dependencies:
 fsl-5.0-core : Depends: fslview but it is not installable

fslview has been removed from the archive, see
https://bugs.debian.org/861330 for details.


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: fsl
Source-Version: 5.0.8-6

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated fsl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Jan 2019 16:42:15 +0100
Source: fsl
Binary: fsl fsl-5.0 fsl-core fsl-5.0-core
Architecture: source amd64 all
Version: 5.0.8-6
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Andreas Tille 
Description:
 fsl- transitional dummy package
 fsl-5.0- transitional dummy package
 fsl-5.0-core - analysis tools for FMRI, MRI and DTI brain imaging
 fsl-core   - metapackage for the latest version of FSL
Closes: 804881 837361 864178
Changes:
 fsl (5.0.8-6) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Yaroslav Halchenko ]
   * Add 'file' to Depends of fsl-5.0-core. Required by fslFixText utility
   * debian/fsl.sh - place FSL's bin path first (not the last) within adjusted
 $PATH (Closes: #804881)
   * debian/patches/up_in_compar to fix FTBFS of melodic on 17.04
 Closes: #837361
 .
   [ Michael Hanke ]
   * Move 'fslview' from a dependency into suggests. It can no longer be
 built in Debian unstable.
 Closes: #864178
 .
   [ Andreas Tille ]
   * Replace watch line pointing to alioth which does not exist any more
 by fake watch file
   * debhelper 9
   * Point Vcs fields to salsa.debian.org
   * Standards-Version: 4.3.0
   * Fix call of overloaded 'round(float)' is ambiguous
   * Silence lintian about false positive spelling
   * fsl-5.0-core Depends: sensible-utils
   * Drop Encoding key from desktop file
   * Drop Debian menu file (since there is a desktop file)
   * hardening=+all
Checksums-Sha1:
 6e8a1fb0f0cc2a1558a1b7fa8bd00b1627bc6a8c 2421 fsl_5.0.8-6.dsc
 370cf2cb97ebb6d0a2b47a725054a5c411b068ea 42616 fsl_5.0.8-6.debian.tar.xz
 f539df5deca892fae38eaacee33dc9fead684c3a 153645380 
fsl-5.0-core-dbgsym_5.0.8-6_amd64.deb
 17300011f64f941bdd5c3ed27def50658dc888e2 8365888 fsl-5.0-core_5.0.8-6_amd64.deb
 2811268688cb53b220c2acf8cb1ef60720cb0f48 20028 fsl-5.0_5.0.8-6_all.deb
 3ef31da705273ee0880e6f04ca59b5fdc2358cfb 21192 fsl-core_5.0.8-6_all.deb
 edba08409ceabe90ecd0dec4c5837d259cf83dbd 21560 fsl_5.0.8-6_all.deb
 d4a008c2509ff77e7db0268520bb8d06f42bd560 14675 fsl_5.0.8-6_amd64.buildinfo
Checksums-Sha256:
 2de76e045a975189b5d44d229cd1130edba9b18621f74be1084a8e8a7dbada20 2421 
fsl_5.0.8-6.dsc
 53f61a818589f95b21db5997ae992fc895c1d1cd1d89ba01ffcc769e06d6a93f 42616 
fsl_5.0.8-6.debian.tar.xz
 5deef18a26980a6c5857e6d27dacf313f0757457787e44b26c9942738b7ca9ce 153645380 
fsl-5.0-core-dbgsym_5.0.8-6_amd64.deb
 fe5123e06e43d9b1206e65444773a15949f98c25bdfde913995f1a0cda89ca0e 8365888 
fsl-5.0-core_5.0.8-6_amd64.deb
 f1d10bcf8c859ce45852c378f7c523a53d4c8904cae548e920dbe79a54322c66 20028 
fsl-5.0_5.0.8-6_all.deb
 0d95b08f1e5a5b8a6b7a6e124e4d354b53205c0b00a11e89af3b1e3512f9a865 21192 
fsl-core_5.0.8-6_all.deb
 33e298e6ce439eb319a0ddb0395ef8ddb3f4c0695b9c8025280d78108a254f04 21560 
fsl_5.0.8-6_all.deb
 1d76a785f1c6091c8bef793c51a73e8cb4d58d6f50d758de2dd080588a3d3018 14675 
fsl_5.0.8-6_amd64.buildinfo
Files:
 

Processed: Re: Bug#919289: [Pkg-kde-extras] Bug#919289: kile: After upgrade, kile will not open until okular installed

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #919289 [kile] kile: After upgrade, kile will not open until okular 
installed
Severity set to 'serious' from 'normal'

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

Processed: Re: casparcg-server: FTBFS in sid (cannot find -lpthreads)

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 casparcg-server: FTBFS: Xrandr library not found - required for 
> GLFW
Bug #919332 {Done: Santiago Vila } [src:casparcg-server] 
casparcg-server: FTBFS in sid (cannot find -lpthreads)
Changed Bug title to 'casparcg-server: FTBFS: Xrandr library not found - 
required for GLFW' from 'casparcg-server: FTBFS in sid (cannot find 
-lpthreads)'.

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

Bug#919332: casparcg-server: FTBFS in sid (cannot find -lpthreads)

[Andreas Beckmann]

Followup-For: Bug #919332
Control: retitle -1 casparcg-server: FTBFS: Xrandr library not found - required 
for GLFW


The relevant part from the build log seems to be

-- Found X11: /usr/lib/x86_64-linux-gnu/libX11.so
CMake Error at CMakeModules/FindGLFW.cmake:146 (message):
  Xrandr library not found - required for GLFW
Call Stack (most recent call first):
  CMakeModules/Bootstrap_Linux.cmake:44 (FIND_PACKAGE)
  CMakeLists.txt:18 (INCLUDE)


-- Configuring incomplete, errors occurred!


Andreas

Bug#919058: mate-utils: frequent parallel FTBFS

[Jeremy Bicha]

Control: reopen -1

Sadly, --no-parallel didn't work.

https://buildd.debian.org/status/package.php?p=mate-utils

Thanks,
Jeremy Bicha

Processed: Re: Bug#919058: mate-utils: frequent parallel FTBFS

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #919058 {Done: Mike Gabriel } [src:mate-utils] 
mate-utils: frequent parallel FTBFS
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions mate-utils/1.20.2-2.

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

Bug#822586: Upstream status update

[Raphael Hertzog]

Hello,

just FYI since upstream was unable to port the code to the GObject
Introspection bindings, he started to rewrite the application in
C++ using GTKmm. This is happening in the "future" directory of the
upstream git repository (master branch) and the author shares
some progress information here:
https://www.giuspen.com/topic/status-of-the-development/

As of today, it seems that the C++ rewrite is able to display
content in read-only mode so it's not finished yet.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#919390: udev: network interface gets ID_NET_NAME even when NAME has been set by /etc/udev/rules.d/70-persistent-net.rules

[Michal Hocko]

On Tue, Jan 15, 2019 at 02:36:46PM +0100, Michael Biebl wrote:
> Am 15.01.19 um 14:32 schrieb Michal Hocko:
> > On Tue, Jan 15, 2019 at 02:28:55PM +0100, Michael Biebl wrote:
[...]
> >> Have you made sure to rebuild the initramfs after changing the udev rule?
> > 
> > Hmm, I haven't but is this really important? My eth driver is built in
> > CONFIG_E1000E=y
> 
> Yes, you must update the initramfs so it contains
> /etc/udev/rules.d/70-persistent-net.rules,

I have checked my initrd and it seems to have that rule under
lib/udev/rules.d/70-persistent-net.rules

Besides that there is apparatently renaming from eth0->lan0 happening as
per kernel log mentioned earlier:

[3.563937] e1000e :00:1f.6 lan0: renamed from eth0

Anyway, I will try to regenerate and reboot later just to be sure.
Thanks!
-- 
Michal Hocko

Bug#919412: rng-tools: Build-Depends on cruft package libgcrypt11-dev

[Andreas Beckmann]

Source: rng-tools
Version: 5-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

rng-tools/sid build-depends on libgcrypt11-dev. This was a
transitional package, please use libgcrypt20-dev instead.


Cheers,

Andreas

Bug#919326: msmtp: account default not found: no configuration file available

[Simon Deziel]

On 2019-01-14 6:03 p.m., Sergio Mendoza wrote:
>   Yes.  I have now checked and I have .msmtprc as a symlink.  If it is not
> a symlink then I have no problems and everything runs smooth.

Great, thanks Sergio.

>  In any case
> this is the output you asked for:
> 
> root@quetzalli:~# dmesg | grep apparmor | tail -n 20
> [1064151.025521] audit: type=1400 audit(1547506707.004:157): 
> apparmor="DENIED" operation="open" profile="/usr/bin/msmtp" 
> name="/home/sergio/Private/.msmtprc" pid=14560 comm="msmtp" 
> requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000

This should eventually work even when ~/.msmtprc will be a symlink to
~/Private/.msmtprc. I hope the fix will land in the next package update [*].

> [1064177.994021] audit: type=1400 audit(1547506733.971:158): 
> apparmor="DENIED" operation="open" profile="/usr/bin/msmtp" 
> name="/home/sergio/mail/msmtp/log.txt" pid=14580 comm="msmtp" 
> requested_mask="ac" denied_mask="ac" fsuid=1000 ouid=1000
> [1064281.325901] audit: type=1400 audit(1547506837.302:159): 
> apparmor="DENIED" operation="open" profile="/usr/bin/msmtp" 
> name="/home/sergio/mail/msmtp/log.txt" pid=14656 comm="msmtp" 
> requested_mask="ac" denied_mask="ac" fsuid=1000 ouid=1000

This shows that msmtp was denied logging to ~/mail/msmtp/log.txt.

Unfortunately, this isn't a common location to for logs so it likely
won't be supported by the default base Apparmor profile. You have few
options to make it work though:

1) you can have it log to more usual locations like one of those:
  ~/.msmtp.log
  ~/.cache/msmtp/*.log
2) add this local override rule to /etc/apparmor.d/local/usr.bin.msmtp:
  owner @{HOME}/mail/msmtp/log.txt wk,
3) disable the Apparmor profile

1 would be preferable but for 2 and 3, please refer to the README.Debian
file for detailed instructions.

Regards,
Simon


*: https://salsa.debian.org/kolter/msmtp/merge_requests/3

Bug#919356: Licensing of include/linux/hash.h

[Domenico Andreoli]

Hi Nadia,

  As part of the licensing assessment on pahole [0] that I am making for
Debian, I realized that file hash.h in both pahole [1] and the kernel
[2] comes without any licensing specification.

Could you please make an explicit choice and maybe provide patches?

Kind regards,
Domenico

[0] https://git.kernel.org/pub/scm/devel/pahole/pahole.git/
[1] https://git.kernel.org/pub/scm/devel/pahole/pahole.git/tree/hash.h
[2] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/hash.h

-- 
3B10 0CA1 8674 ACBA B4FE  FCD2 CE5B CF17 9960 DE13


signature.asc
Description: PGP signature

Bug#919399: FTBFS: undefined reference to makedev

[James Clarke]

Control: forcemerge 916062 -1

> On 15 Jan 2019, at 14:05, Ritesh Raj Sarraf  wrote:
> 
> Source: cowdancer
> Version: 0.87

This was already reported as the bug mentioned above and fixed in the 0.88
upload a week ago. Also please don't forward raw multi-part MIME messages; you
end up with the horrendous mess that you can see below.

James

> Severity: serious
> Tags: patch
> Justification: fails to build from source (but built successfully in the past)
> 
> Content-Type: multipart/mixed; boundary="===1317036836604284426=="
> MIME-Version: 1.0
> From: Ritesh Raj Sarraf 
> To: Debian Bug Tracking System 
> Subject: FTBFS: undefined reference to makedev
> Message-ID: 
> <154756077354.13753.2447109323940488229.report...@priyasi.researchut.com>
> X-Mailer: reportbug 7.5.1
> Date: Tue, 15 Jan 2019 19:29:33 +0530
> X-Debbugs-Cc: r...@debian.org
> 
> This is a multi-part MIME message sent by reportbug.
> 
> 
> --===1317036836604284426==
> Content-Type: text/plain; charset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: base64
> Content-Disposition: inline
> 
> U291cmNlOiBjb3dkYW5jZXIKVmVyc2lvbjogMC44NwpTZXZlcml0eTogc2VyaW91cwpUYWdzOiBw
> YXRjaApKdXN0aWZpY2F0aW9uOiBmYWlscyB0byBidWlsZCBmcm9tIHNvdXJjZSAoYnV0IGJ1aWx0
> IHN1Y2Nlc3NmdWxseSBpbiB0aGUgcGFzdCkKCgpsaWJ0b29sOiBjb21waWxlOiAgZ2NjIC1EUEFD
> S0FHRV9OQU1FPVwiY293ZGFuY2VyXCIgLURQQUNLQUdFX1RBUk5BTUU9XCJjb3dkYW5jZXJcIiAt
> RFBBQ0tBR0VfVkVSU0lPTj1cIjAuODdcIiAiLURQQUNLQUdFX1NUUklORz1cImNvd2RhbmNlciAw
> Ljg3XCIiIC1EUEFDS0FHRV9CVUdSRVBPUlQ9XCJcIiAtRFBBQ0tBR0VfVVJMPVwiXCIgLURQQUNL
> QUdFPVwiY293ZGFuY2VyXCIgLURWRVJTSU9OPVwiMC44N1wiIC1EU1REQ19IRUFERVJTPTEgLURI
> QVZFX1NZU19UWVBFU19IPTEgLURIQVZFX1NZU19TVEFUX0g9MSAtREhBVkVfU1RETElCX0g9MSAt
> REhBVkVfU1RSSU5HX0g9MSAtREhBVkVfTUVNT1JZX0g9MSAtREhBVkVfU1RSSU5HU19IPTEgLURI
> QVZFX0lOVFRZUEVTX0g9MSAtREhBVkVfU1RESU5UX0g9MSAtREhBVkVfVU5JU1REX0g9MSAtREhB
> VkVfRExGQ05fSD0xIC1ETFRfT0JKRElSPVwiLmxpYnMvXCIgLUkuIC1XZGF0ZS10aW1lIC1EX0ZP
> UlRJRllfU09VUkNFPTIgLWZuby1zdHJpY3QtYWxpYXNpbmcgLURDT1dEQU5DRVJfU089XCIvdXNy
> L2xpYi9jb3dkYW5jZXIvbGliY293ZGFuY2VyLnNvXCIgLWcgLU8yIC1mZGVidWctcHJlZml4LW1h
> cD0vYnVpbGQvY293ZGFuY2VyLTAuODc9LiAtZnN0YWNrLXByb3RlY3Rvci1zdHJvbmcgLVdmb3Jt
> YXQgLVdlcnJvcj1mb3JtYXQtc2VjdXJpdHkgLWMgY293ZGFuY2VyLmMgLW8gbGliY293ZGFuY2Vy
> X2xhLWNvd2RhbmNlci5vID4vZGV2L251bGwgMj4mMQpsaWJ0b29sOiBsaW5rOiBnY2MgLWZuby1z
> dHJpY3QtYWxpYXNpbmcgLURDT1dEQU5DRVJfU089XCIvdXNyL2xpYi9jb3dkYW5jZXIvbGliY293
> ZGFuY2VyLnNvXCIgLWcgLU8yIC1mZGVidWctcHJlZml4LW1hcD0vYnVpbGQvY293ZGFuY2VyLTAu
> ODc9LiAtZnN0YWNrLXByb3RlY3Rvci1zdHJvbmcgLVdmb3JtYXQgLVdlcnJvcj1mb3JtYXQtc2Vj
> dXJpdHkgLVdsLC16IC1XbCxyZWxybyAtV2wsLXogLVdsLG5vdyAtbyBjb3didWlsZGVyIGNvd2J1
> aWxkZXIubyBwYXJhbWV0ZXIubyBmb3JrZXhlYy5vIGlsaXN0Y3JlYXRlLm8gbWFpbi5vIGNvd2J1
> aWxkZXJfdXRpbC5vIGxvZy5vICAtbGRsIC1sbmN1cnNlcwpsaWJ0b29sOiBsaW5rOiBnY2MgLWZu
> by1zdHJpY3QtYWxpYXNpbmcgLURDT1dEQU5DRVJfU089XCIvdXNyL2xpYi9jb3dkYW5jZXIvbGli
> Y293ZGFuY2VyLnNvXCIgLWcgLU8yIC1mZGVidWctcHJlZml4LW1hcD0vYnVpbGQvY293ZGFuY2Vy
> LTAuODc9LiAtZnN0YWNrLXByb3RlY3Rvci1zdHJvbmcgLVdmb3JtYXQgLVdlcnJvcj1mb3JtYXQt
> c2VjdXJpdHkgLVdsLC16IC1XbCxyZWxybyAtV2wsLXogLVdsLG5vdyAtbyBxZW11YnVpbGRlciBx
> ZW11YnVpbGRlci1xZW11YnVpbGRlci5vIHFlbXVidWlsZGVyLXBhcmFtZXRlci5vIHFlbXVidWls
> ZGVyLWZvcmtleGVjLm8gcWVtdWJ1aWxkZXItcWVtdWlwc2FuaXRpemUubyBxZW11YnVpbGRlci1x
> ZW11YXJjaC5vIHFlbXVidWlsZGVyLWZpbGUubyBxZW11YnVpbGRlci1tYWluLm8gcWVtdWJ1aWxk
> ZXItbG9nLm8gIC1sZGwgLWxuY3Vyc2VzCi91c3IvYmluL2xkOiBxZW11YnVpbGRlci1xZW11YXJj
> aC5vOiBpbiBmdW5jdGlvbiBgcWVtdV9jcmVhdGVfYXJjaF9zZXJpYWxkZXZpY2UnOgouL3FlbXVh
> cmNoLmM6NjA6IHVuZGVmaW5lZCByZWZlcmVuY2UgdG8gYG1ha2VkZXYnCi91c3IvYmluL2xkOiAu
> L3FlbXVhcmNoLmM6NjI6IHVuZGVmaW5lZCByZWZlcmVuY2UgdG8gYG1ha2VkZXYnCi91c3IvYmlu
> L2xkOiBxZW11YnVpbGRlci1xZW11YXJjaC5vOiBpbiBmdW5jdGlvbiBgcWVtdV9jcmVhdGVfYXJj
> aF9kZXZpY2VzJzoKLi9xZW11YXJjaC5jOjg1OiB1bmRlZmluZWQgcmVmZXJlbmNlIHRvIGBtYWtl
> ZGV2JwovdXNyL2Jpbi9sZDogLi9xZW11YXJjaC5jOjg3OiB1bmRlZmluZWQgcmVmZXJlbmNlIHRv
> IGBtYWtlZGV2JwovdXNyL2Jpbi9sZDogLi9xZW11YXJjaC5jOjg5OiB1bmRlZmluZWQgcmVmZXJl
> bmNlIHRvIGBtYWtlZGV2JwovdXNyL2Jpbi9sZDogcWVtdWJ1aWxkZXItcWVtdWFyY2gubzouL3Fl
> bXVhcmNoLmM6OTE6IG1vcmUgdW5kZWZpbmVkIHJlZmVyZW5jZXMgdG8gYG1ha2VkZXYnIGZvbGxv
> dwpjb2xsZWN0MjogZXJyb3I6IGxkIHJldHVybmVkIDEgZXhpdCBzdGF0dXMKbWFrZVsxXTogKioq
> IFtNYWtlZmlsZTo5OTY6IHFlbXVidWlsZGVyXSBFcnJvciAxCm1ha2VbMV06ICoqKiBXYWl0aW5n
> IGZvciB1bmZpbmlzaGVkIGpvYnMuLi4uCm1ha2VbMV06IExlYXZpbmcgZGlyZWN0b3J5ICcvYnVp
> bGQvY293ZGFuY2VyLTAuODcnCmRoX2F1dG9fYnVpbGQ6IG1ha2UgLWo0IHJldHVybmVkIGV4aXQg
> Y29kZSAyCm1ha2U6ICoqKiBbZGViaWFuL3J1bGVzOjY6IGJpbmFyeV0gRXJyb3IgMgpkcGtnLWJ1
> aWxkcGFja2FnZTogZXJyb3I6IGRlYmlhbi9ydWxlcyBiaW5hcnkgc3VicHJvY2VzcyByZXR1cm5l
> ZCBleGl0IHN0YXR1cyAyCkk6IGNvcHlpbmcgbG9jYWwgY29uZmlndXJhdGlvbgpFOiBGYWlsZWQg
> YXV0b2J1aWxkaW5nIG9mIHBhY2thZ2UKSTogdW5tb3VudGluZyAvdmFyL2NhY2hlL2FwdC9hcmNo
> aXZlcy8gZmlsZXN5c3RlbQpJOiB1bm1vdW50aW5nIGRldi9wdG14IGZpbGVzeXN0ZW0KSTogdW5t
> b3VudGluZyBkZXYvcHRzIGZpbGVzeXN0ZW0KSTogdW5tb3VudGluZyBkZXYvc2htIGZpbGVzeXN0
> 

Processed: Re: Bug#919399: FTBFS: undefined reference to makedev

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 916062 -1
Bug #916062 {Done: Mattia Rizzolo } [src:cowdancer] 
cowdancer FTBFS with glibc 2.28
Bug #919399 {Done: Mattia Rizzolo } [src:cowdancer] FTBFS: 
undefined reference to makedev
Bug #919399 {Done: Mattia Rizzolo } [src:cowdancer] FTBFS: 
undefined reference to makedev
Merged 916062 919399

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

Bug#919409: scikit-learn: binary-any FTBFS

[Adrian Bunk]

Source: scikit-learn
Version: 0.20.1+dfsg-2
Severity: serious
Tags: ftbfs
Control: block 907806 by -1

https://buildd.debian.org/status/package.php?p=scikit-learn=sid

...
python3.7 -m sphinx -j 4 -D mathjax_path=MathJax.js -b html -d _build/doctrees  
  . _build/html/stable
/usr/bin/python3.7: No module named sphinx
make[1]: *** [Makefile:47: html] Error 1


Seems some package(s) have to move from Build-Depends-Indep
to Build-Depends.

Processed: scikit-learn: binary-any FTBFS

[Debian Bug Tracking System]

Processing control commands:

> block 907806 by -1
Bug #907806 {Done: Yangfl } [src:scikit-learn] 
scikit-learn: FTBFS in buster/sid (could not import 'distributed')
907806 was blocked by: 911830
907806 was not blocking any bugs.
Added blocking bug(s) of 907806: 919409

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

Bug#918588: marked as done (libtool: generated libtool script is broken, affecting build on AIX)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 16:50:59 +
with message-id 
and subject line Bug#918588: fixed in libtool 2.4.6-8
has caused the Debian Bug report #918588,
regarding libtool: generated libtool script is broken, affecting build on AIX
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.)


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

There's a major quoting issue in a recent change of libtool.
This makes the MPFR build fail on AIX:

$ make
Making all in doc
Target "all" is up to date.
Making all in src
make  all-am
/bin/sh ../libtool  --tag=CC--mode=compile 
/tmp/mpfrtests-vinc17-11403832/mpfr-4.0.2-rc1/compile gcc -DMPFR_WANT_ASSERT=2 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DLT_OBJDIR=\".libs/\" 
-DHAVE_DOUBLE_IEEE_BIG_ENDIAN=1 -DHAVE_BIG_ENDIAN=1 -DTIME_WITH_SYS_TIME=1 
-DHAVE_LOCALE_H=1 -DHAVE_WCHAR_H=1 -DHAVE_STDARG=1 -DHAVE_SYS_TIME_H=1 
-DHAVE_STRUCT_LCONV_DECIMAL_POINT=1 -DHAVE_STRUCT_LCONV_THOUSANDS_SEP=1 
-DHAVE_ALLOCA_H=1 -DHAVE_VA_COPY=1 -DHAVE_SETLOCALE=1 -DHAVE_GETTIMEOFDAY=1 
-DHAVE_SIGNAL=1 -DHAVE_SIGACTION=1 -DHAVE_LONG_LONG=1 -DHAVE_INTMAX_T=1 
-DMPFR_HAVE_INTMAX_MAX=1 -DMPFR_PRINTF_MAXLM=\"j\" -DMPFR_HAVE_NORETURN=1 
-DMPFR_HAVE_BUILTIN_UNREACHABLE=1 -DMPFR_HAVE_CONSTRUCTOR_ATTR=1 
-DHAVE_PTHREAD_PRIO_INHERIT=1 -DHAVE_PTHREAD=1 -DMPFR_HAVE_FESETROUND=1 
-DHAVE_DENORMS=1 -DHAVE_DENORMS_FLT=1 -DHAVE_SIGNEDZ=1 -DHAVE_ROUND=1 
-DHAVE_TRUNC=1 -DHAVE_FLOOR=1 -DHAVE_CEIL=1 -DHAVE_NEARBYINT=1 
-DHAVE_LDOUBLE_IS_DOUBLE=1 -DMPFR_USE_STATIC_ASSERT=1 -DHAVE_CLOCK_GETTIME=1 
-DHAVE_ATTRIBUTE_MODE=1 -DPRINTF_L=1 -DPRINTF_T=1 -DPRINTF_GROUPFLAG=1 
-DHAVE___GMPN_SBPI1_DIVAPPR_Q=1 -DHAVE___GMPN_INVERT_LIMB=1 
-DMPFR_LONG_WITHIN_LIMB=1 -DHAVE_GETRUSAGE=1  -I. -I../../mpfr-4.0.2-rc1/src   
-I/opt/cfarm/gmp-latest/include   -Wall -Wmissing-prototypes -Wpointer-arith 
-O2 -pedantic -maix64 -mpowerpc64 -mtune=power8 -MT exceptions.lo -MD -MP -MF 
.deps/exceptions.Tpo -c -o exceptions.lo ../../mpfr-4.0.2-rc1/src/exceptions.c
libtool: compile:  /tmp/mpfrtests-vinc17-11403832/mpfr-4.0.2-rc1/compile gcc 
-DMPFR_WANT_ASSERT=2 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 "" 
-DHAVE_DOUBLE_IEEE_BIG_ENDIAN=1 -DHAVE_BIG_ENDIAN=1 -DTIME_WITH_SYS_TIME=1 
-DHAVE_LOCALE_H=1 -DHAVE_WCHAR_H=1 -DHAVE_STDARG=1 -DHAVE_SYS_TIME_H=1 
-DHAVE_STRUCT_LCONV_DECIMAL_POINT=1 -DHAVE_STRUCT_LCONV_THOUSANDS_SEP=1 
-DHAVE_ALLOCA_H=1 -DHAVE_VA_COPY=1 -DHAVE_SETLOCALE=1 -DHAVE_GETTIMEOFDAY=1 
-DHAVE_SIGNAL=1 -DHAVE_SIGACTION=1 -DHAVE_LONG_LONG=1 -DHAVE_INTMAX_T=1 
-DMPFR_HAVE_INTMAX_MAX=1 "" -DMPFR_HAVE_NORETURN=1 
-DMPFR_HAVE_BUILTIN_UNREACHABLE=1 -DMPFR_HAVE_CONSTRUCTOR_ATTR=1 
-DHAVE_PTHREAD_PRIO_INHERIT=1 -DHAVE_PTHREAD=1 -DMPFR_HAVE_FESETROUND=1 
-DHAVE_DENORMS=1 -DHAVE_DENORMS_FLT=1 -DHAVE_SIGNEDZ=1 -DHAVE_ROUND=1 
-DHAVE_TRUNC=1 -DHAVE_FLOOR=1 -DHAVE_CEIL=1 -DHAVE_NEARBYINT=1 
-DHAVE_LDOUBLE_IS_DOUBLE=1 -DMPFR_USE_STATIC_ASSERT=1 -DHAVE_CLOCK_GETTIME=1 
-DHAVE_ATTRIBUTE_MODE=1 -DPRINTF_L=1 -DPRINTF_T=1 -DPRINTF_GROUPFLAG=1 
-DHAVE___GMPN_SBPI1_DIVAPPR_Q=1 -DHAVE___GMPN_INVERT_LIMB=1 
-DMPFR_LONG_WITHIN_LIMB=1 -DHAVE_GETRUSAGE=1 -I. -I../../mpfr-4.0.2-rc1/src 
-I/opt/cfarm/gmp-latest/include -Wall -Wmissing-prototypes -Wpointer-arith -O2 
-pedantic -maix64 -mpowerpc64 -mtune=power8 -MT exceptions.lo -MD -MP -MF 
.deps/exceptions.Tpo -c ../../mpfr-4.0.2-rc1/src/exceptions.c  -fPIC -DPIC -o 
.libs/exceptions.o
gcc: error: : No such file or directory
gcc: error: : No such file or directory

See, the -DLT_OBJDIR=\".libs/\" and -DMPFR_PRINTF_MAXLM=\"j\" have
been transformed to "".

When I do a diff on the libtool script between a working version
(based on 2.4.6-2) and a buggy version (based on 2.4.6-6), I can
see a new function func_quote. This might be related. I've attached
the diff.

In the changelog, I can see:

libtool (2.4.6-6) unstable; urgency=medium

  * Undo broken patch inclusion. Closes: #910076
  * Disable refactor patch 0012-funclib-refactor-quoting-methods-a-bit.patch
that breaks pkgs  on AIX (no bash optimization). Closes: #900276
  * Add build-dep on libltdl-dev for test 102

but apparently that wasn't enough.

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

Kernel: Linux 4.18.0-3-amd64 (SMP w/12 CPU cores)
Locale: LANG=POSIX, 

Bug#919341: marked as done (libtool-bin: amd64 /usr/bin/libtool is a zero byte file)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 16:50:59 +
with message-id 
and subject line Bug#919341: fixed in libtool 2.4.6-8
has caused the Debian Bug report #919341,
regarding libtool-bin: amd64 /usr/bin/libtool is a zero byte file
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.)


-- 
919341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtool-bin
Version: 2.4.6-7
Severity: serious
File: /usr/bin/libtool

The amd64 package, the only one not built on a buildd, contains a
zero-byte /usr/bin/libtool.  This makes it completely non-functional.

$ dpkg-deb -c libtool-bin_2.4.6-7_amd64.deb
drwxr-xr-x root/root 0 2019-01-12 09:10 ./
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/bin/
-rwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/bin/libtool
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/share/
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/share/doc/
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/share/doc/libtool-bin/
-rw-r--r-- root/root  9329 2019-01-12 09:10 
./usr/share/doc/libtool-bin/changelog.Debian.gz
-rw-r--r-- root/root342562 2015-02-15 12:15 
./usr/share/doc/libtool-bin/changelog.gz
-rw-r--r-- root/root  1976 2019-01-12 09:10 
./usr/share/doc/libtool-bin/copyright
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/share/man/
drwxr-xr-x root/root 0 2019-01-12 09:10 ./usr/share/man/man1/
-rw-r--r-- root/root20 2019-01-12 09:10 
./usr/share/man/man1/libtool.1.gz

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

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

Versions of packages libtool-bin depends on:
ii  libtool  2.4.6-7

libtool-bin recommends no packages.

libtool-bin suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libtool
Source-Version: 2.4.6-8

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated libtool package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Jan 2019 13:42:46 +
Source: libtool
Binary: libtool libtool-bin libtool-doc libltdl7 libltdl-dev
Architecture: source amd64 all
Version: 2.4.6-8
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libltdl-dev - System independent dlopen wrapper for GNU libtool
 libltdl7   - System independent dlopen wrapper for GNU libtool
 libtool- Generic library support script
 libtool-bin - Generic library support script (libtool binary)
 libtool-doc - Generic library support script
Closes: 918588 919341
Changes:
 libtool (2.4.6-8) unstable; urgency=medium
 .
   * Fix Typos in sed expressions in d/rules. Closes: #919341
   * Close bug fixed in previous release. Closes: #918588
Checksums-Sha1:
 f96b48f56caf66250db55725360dfe03e73b171e 2479 libtool_2.4.6-8.dsc
 42aefb476baff9ba2816bbff4d8ac709a66e0722 48384 libtool_2.4.6-8.debian.tar.xz
 3ec42758329ccaa75e89ad5dba7b84555db41064 161960 libltdl-dev_2.4.6-8_amd64.deb
 7436b9c3cef2acfa9601f7fe217542a46f1f2012 46820 
libltdl7-dbgsym_2.4.6-8_amd64.deb
 32a89c9878e58948a317f6951ee764b9e0a95466 389928 libltdl7_2.4.6-8_amd64.deb
 e3737e4e8bf9c60700f0c34ea37626d02f0d4912 431308 libtool-bin_2.4.6-8_amd64.deb
 f8f1a55c77e48aafccd43fb17c219425b348beef 582288 libtool-doc_2.4.6-8_all.deb
 fa54656deca22eb74f1b2484167f725d30533bf6 546744 libtool_2.4.6-8_all.deb
 62d3af3127fb81409c72f7cf8c3259332015ed82 7138 libtool_2.4.6-8_amd64.buildinfo
Checksums-Sha256:
 

Processed: severity of 919363 is serious

[Debian Bug Tracking System]

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

> severity 919363 serious
Bug #919363 [src:lua5.2] lua5.2 ftbfs in unstable
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#919406: kdiff3 FTBFS: missing -latomic

[Helmut Grohne]

Source: kdiff3
Version: 1.7.90-1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap

While conducting cross build tests, I found that kdiff3 fails to build
from source natively on armel, mips and mipsel due to missing symbols
that are present in -latomic, e.g.:

| cd /<>/obj-mipsel-linux-gnu/src && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/kdiff3.dir/link.txt --verbose=1
| /usr/bin/mipsel-linux-gnu-g++  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++0x -fno-operator-names -fno-exceptions -Wall 
-Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long 
-Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual 
-Werror=return-type -Wvla -Wdate-time -Wall -Wduplicated-cond 
-Wduplicated-branches -Wshadow  -Wl,--enable-new-dtags -Wl,-z,relro 
-Wl,--as-needed -rdynamic CMakeFiles/kdiff3.dir/main.cpp.o 
CMakeFiles/kdiff3.dir/kdiff3_shell.cpp.o 
CMakeFiles/kdiff3.dir/kdiff3_part.cpp.o CMakeFiles/kdiff3.dir/kdiff3.cpp.o 
CMakeFiles/kdiff3.dir/directorymergewindow.cpp.o 
CMakeFiles/kdiff3.dir/merger.cpp.o CMakeFiles/kdiff3.dir/pdiff.cpp.o 
CMakeFiles/kdiff3.dir/difftextwindow.cpp.o CMakeFiles/kdiff3.dir/diff.cpp.o 
CMakeFiles/kdiff3.dir/optiondialog.cpp.o 
CMakeFiles/kdiff3.dir/mergeresultwindow.cpp.o 
CMakeFiles/kdiff3.dir/fileaccess.cpp.o 
CMakeFiles/kdiff3.dir/gnudiff_analyze.cpp.o 
CMakeFiles/kdiff3.dir/gnudiff_io.cpp.o 
CMakeFiles/kdiff3.dir/gnudiff_xmalloc.cpp.o CMakeFiles/kdiff3.dir/common.cpp.o 
CMakeFiles/kdiff3.dir/smalldialogs.cpp.o CMakeFiles/kdiff3.dir/progress.cpp.o 
CMakeFiles/kdiff3.dir/ProgressProxyExtender.cpp.o 
CMakeFiles/kdiff3.dir/PixMapUtils.cpp.o 
CMakeFiles/kdiff3.dir/MergeFileInfos.cpp.o CMakeFiles/kdiff3.dir/Utils.cpp.o 
CMakeFiles/kdiff3.dir/selection.cpp.o CMakeFiles/kdiff3.dir/cvsignorelist.cpp.o 
CMakeFiles/kdiff3.dir/kdiff3_autogen/mocs_compilation.cpp.o  -o kdiff3 
/usr/lib/mipsel-linux-gnu/libKF5Parts.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5KIOWidgets.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5KIOCore.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5Crash.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5JobWidgets.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libQt5Concurrent.so.5.11.3 
/usr/lib/mipsel-linux-gnu/libKF5XmlGui.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libQt5PrintSupport.so.5.11.3 
/usr/lib/mipsel-linux-gnu/libQt5Network.so.5.11.3 
/usr/lib/mipsel-linux-gnu/libKF5TextWidgets.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5IconThemes.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5Service.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5Completion.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5ConfigWidgets.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5ConfigGui.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5ConfigCore.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libQt5Xml.so.5.11.3 
/usr/lib/mipsel-linux-gnu/libKF5I18n.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5WidgetsAddons.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5Codecs.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5Auth.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libKF5CoreAddons.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libQt5DBus.so.5.11.3 
/usr/lib/mipsel-linux-gnu/libKF5SonnetUi.so.5.51.0 
/usr/lib/mipsel-linux-gnu/libQt5Widgets.so.5.11.3 
/usr/lib/mipsel-linux-gnu/libQt5Gui.so.5.11.3 
/usr/lib/mipsel-linux-gnu/libQt5Core.so.5.11.3 
| /usr/lib/gcc-cross/mipsel-linux-gnu/8/../../../../mipsel-linux-gnu/bin/ld: 
CMakeFiles/kdiff3.dir/progress.cpp.o: undefined reference to symbol 
'__atomic_load_8@@LIBATOMIC_1.0'
| /usr/lib/gcc-cross/mipsel-linux-gnu/8/../../../../mipsel-linux-gnu/bin/ld: 
//usr/lib/mipsel-linux-gnu/libatomic.so.1: error adding symbols: DSO missing 
from command line
| collect2: error: ld returned 1 exit status
| make[3]: *** [src/CMakeFiles/kdiff3.dir/build.make:447: src/kdiff3] Error 1
| make[3]: Leaving directory '/<>/obj-mipsel-linux-gnu'
| make[2]: *** [CMakeFiles/Makefile2:309: src/CMakeFiles/kdiff3.dir/all] Error 2
| make[2]: Leaving directory '/<>/obj-mipsel-linux-gnu'
| make[1]: *** [Makefile:144: all] Error 2
| make[1]: Leaving directory '/<>/obj-mipsel-linux-gnu'
| make: *** [/usr/share/cdbs/1/class/makefile.mk:77: 
debian/stamp-makefile-build] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Helmut

Processed: stardict: FTBFS with mariadb-10.3: wikipediaImage.cpp:34:76: error: 'MYSQL_PORT' was not declared in this scope

[Debian Bug Tracking System]

Processing control commands:

> block 919395 with -1 918394
Bug #919395 [release.debian.org] transition: mariadb-10.3
919395 was blocked by: 919393 918387 917758 918393 919374 919373 919379 919375
919395 was not blocking any bugs.
Added blocking bug(s) of 919395: 918394 and 919408

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

Bug#919408: stardict: FTBFS with mariadb-10.3: wikipediaImage.cpp:34:76: error: 'MYSQL_PORT' was not declared in this scope

[Andreas Beckmann]

Source: stardict
Version: 3.0.6-0.2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Control: block 919395 with -1 918394

Hi,

stardict FTBFS with mariadb-10.3 in sid:

g++ -DHAVE_CONFIG_H -I. -I..  -Wall -pthread -I/usr/include/gtk-2.0 
-I/usr/lib/i386-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/us
r/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/fribidi -I/usr/include/freetype2 -I/usr/include/libpn
g16 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/uuid 
-I/usr/include/glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -I.. -I.. 
-I/usr/include/mariadb -I/usr/include/mariadb/mysql -Wdate-time -D
_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/build/stardict-3.0.6=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
wikipediaImage-wikipediaImage.o `test -f 'wikipediaImage.cpp' || echo './'`wiki
pediaImage.cpp
wikipediaImage.cpp: In function 'void dump_file()':
wikipediaImage.cpp:34:76: error: 'MYSQL_PORT' was not declared in this scope
  if (!mysql_real_connect(, CONN_HOST , CONN_USER , CONN_PASS, NULL , 
MYSQL_PORT, NULL, 0))

^~
wikipediaImage.cpp:34:76: note: suggested alternative: 'MYSQL_STMT'
  if (!mysql_real_connect(, CONN_HOST , CONN_USER , CONN_PASS, NULL , 
MYSQL_PORT, NULL, 0))

^~

MYSQL_STMT
make[5]: *** [Makefile:2162: wikipediaImage-wikipediaImage.o] Error 1


Cheers,

Andreas


stardict_3.0.6-0.2.log.gz
Description: application/gzip

Processed: Re: Bug#918503: glusterfs-common: support files not separated from shared library

[Debian Bug Tracking System]

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

> tag #918503 + pending
Bug #918503 [glusterfs-common] glusterfs-common: support files not separated 
from shared library
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#919332: marked as done (casparcg-server: FTBFS in sid (cannot find -lpthreads))

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 17:20:06 +0100
with message-id <20190115162006.k5ynwpbg7zmdixod@nucold>
and subject line Re: Bug#919332: casparcg-server: FTBFS in sid (cannot find 
-lpthreads)
has caused the Debian Bug report #919332,
regarding casparcg-server: FTBFS in sid (cannot find -lpthreads)
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.)


-- 
919332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:casparcg-server
Version: 2.2.0+dfsg-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --sourcedirectory=src --buildsystem=cmake
   dh_update_autotools_config -a -O--sourcedirectory=src -O--buildsystem=cmake
   dh_autoreconf -a -O--sourcedirectory=src -O--buildsystem=cmake
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/casparcg-server-2.2.0+dfsg'
dh_auto_configure -- -DENABLE_HTML=OFF
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DENABLE_HTML=OFF ../src
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done

[... snipped ...]

./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8:
 undefined reference to `pthread_create'
collect2: error: ld returned 1 exit status
make[3]: *** [CMakeFiles/cmTC_43642.dir/build.make:87: cmTC_43642] Error 1
make[3]: Leaving directory 
'/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: *** [Makefile:121: cmTC_43642/fast] Error 2
make[2]: Leaving directory 
'/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'

File 
/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:
/* */
#include 

int main(int argc, char** argv)
{
  (void)argv;
#ifndef pthread_create
  return ((int*)(_create))[argc];
#else
  (void)argc;
  return 0;
#endif
}

Determining if the function pthread_create exists in the pthreads failed with 
the following output:
Change Dir: 
/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_24c32/fast"
make[2]: Entering directory 
'/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_24c32.dir/build.make 
CMakeFiles/cmTC_24c32.dir/build
make[3]: Entering directory 
'/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_24c32.dir/CheckFunctionExists.c.o
/usr/bin/cc   -g -O2 
-fdebug-prefix-map=/<>/casparcg-server-2.2.0+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create   -o 
CMakeFiles/cmTC_24c32.dir/CheckFunctionExists.c.o   -c 
/usr/share/cmake-3.13/Modules/CheckFunctionExists.c
Linking C executable cmTC_24c32
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_24c32.dir/link.txt 
--verbose=1
/usr/bin/cc -g -O2 
-fdebug-prefix-map=/<>/casparcg-server-2.2.0+dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create  -Wl,-z,relro  
-rdynamic CMakeFiles/cmTC_24c32.dir/CheckFunctionExists.c.o  -o cmTC_24c32 
-lpthreads 
/usr/bin/ld: cannot find -lpthreads
collect2: error: ld returned 1 exit status
make[3]: *** [CMakeFiles/cmTC_24c32.dir/build.make:87: cmTC_24c32] Error 1
make[3]: Leaving directory 
'/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: *** [Makefile:121: cmTC_24c32/fast] Error 2
make[2]: Leaving directory 
'/<>/casparcg-server-2.2.0+dfsg/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'


dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 

Bug#919332: casparcg-server: FTBFS in sid (cannot find -lpthreads)

[Santiago Vila]

Version: 2.2.0+dfsg-2

This version builds ok.

Thanks.

Bug#918503: glusterfs-common: support files not separated from shared library

[Patrick Matthäi]

tag #918503 + pending
thanks

Am 06.01.2019 um 20:46 schrieb Helmut Grohne:
> Package: glusterfs-common
> Version: 5.2-1
> Severity: serious
> Justification: 8.2
> Tags: patch
> Control: block 881526 by -1
>
> glusterfs-common combines shared libraries with a lot of other files and
> even a glusterfs user. Doing so violates the Debian policy section 8.2:
>
> | If your package contains files whose names do not change with each
> | change in the library shared object version, you must not put them in
> | the shared library package.
>
> It is quite evident that the python module, firewalld integration,
> logrotate.d snippet and many other files will not change with an soname
> bump. Given that other packages (e.g. fio) link libglusterfs0, it is
> evident that libglusterfs0 is not a private shared library. Therefore
> glusterfs-common violates a policy must.
>
> The attached patch fixes that. I'm filing it as a separate bug, because
> the policy violation is much narrower in scope than #881526 is.
>
> Helmut

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

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

Processed: severity 919348 serious (Keep xfce4-screensaver out of testing)

[Debian Bug Tracking System]

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

> severity 919348 serious
Bug #919348 [xfce4-screensaver] xfce4-screensaver: Accidental upload to 
unstable while fixing bug #919151
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: forcibly merging 916062 919399

[Debian Bug Tracking System]

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

> forcemerge 916062 919399
Bug #916062 {Done: Mattia Rizzolo } [src:cowdancer] 
cowdancer FTBFS with glibc 2.28
Bug #916062 {Done: Mattia Rizzolo } [src:cowdancer] 
cowdancer FTBFS with glibc 2.28
Added tag(s) patch.
Bug #919399 [src:cowdancer] FTBFS: undefined reference to makedev
Marked Bug as done
Marked as fixed in versions cowdancer/0.88.
Added tag(s) ftbfs.
Merged 916062 919399
> thanks
Stopping processing here.

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

Bug#919393: marked as done (python-mysqldb: FTBFS with mariadb-10.3: _mysql.c:1911:41: error: 'MYSQL' {aka 'struct st_mysql'} has no member named 'reconnect')

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 16:20:33 +
with message-id 
and subject line Bug#919393: fixed in python-mysqldb 1.3.10-2
has caused the Debian Bug report #919393,
regarding python-mysqldb: FTBFS with mariadb-10.3: _mysql.c:1911:41: error: 
'MYSQL' {aka 'struct st_mysql'} has no member named 'reconnect'
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.)


-- 
919393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-mysqldb
Version: 1.3.10-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

python-mysqldb FTBFS with mariadb-10.3 in sid:

building '_mysql' extension
creating build
creating build/temp.linux-i386-2.7
i686-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fdebug-prefix-map=/build/python-mysqldb-1.3.10=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -Dversion_info=(1,3,10,'final',0) 
-D__version__=1.3.10 -I/usr/include/mariadb -I/usr/include/mariadb/mysql 
-I/usr/include/python2.7 -c _mysql.c -o build/temp.linux-i386-2.7/_mysql.o
In file included from _mysql.c:29:
/usr/include/mariadb/my_config.h:3:2: warning: #warning This file should not be 
included by clients, include only  [-Wcpp]
 #warning This file should not be included by clients, include only 
  ^~~
In file included from _mysql.c:30:
/usr/include/mariadb/mysql.h:440:3: warning: function declaration isn't a 
prototype [-Wstrict-prototypes]
   MYSQL_CLIENT_PLUGIN_HEADER
   ^~
_mysql.c: In function '_mysql_ConnectionObject_ping':
_mysql.c:1911:41: error: 'MYSQL' {aka 'struct st_mysql'} has no member named 
'reconnect'
  if ( reconnect != -1 ) self->connection.reconnect = reconnect;
 ^
error: command 'i686-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:338: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 


Cheers,

Andreas


python-mysqldb_1.3.10-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-mysqldb
Source-Version: 1.3.10-2

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-mysqldb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Jan 2019 16:56:13 +0100
Source: python-mysqldb
Binary: python-mysqldb python-mysqldb-dbg python3-mysqldb python3-mysqldb-dbg
Architecture: source amd64
Version: 1.3.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Thomas Goirand 
Description:
 python-mysqldb - Python interface to MySQL
 python-mysqldb-dbg - Python interface to MySQL (debug extension)
 python3-mysqldb - Python interface to MySQL
 python3-mysqldb-dbg - Python interface to MySQL (debug extension)
Closes: 919393
Changes:
 python-mysqldb (1.3.10-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/control: Deprecating priority extra as per policy 4.0.1
   * d/changelog: Remove trailing whitespaces
 .
   [ Thomas Goirand ]
   * Update Standards-Version to 4.3.0.
   * Ran wrap-and-sort -bast.
   * Add upstream patch to avoid FTBFS with recent MariaDB (Closes: #919393).
Checksums-Sha1:
 a55e42e608d835a08860a4dbf9e9a7eb8cb69bd1 2420 python-mysqldb_1.3.10-2.dsc
 6f75fc8e0107a612d5c814760c09e5af5f0917c5 9592 
python-mysqldb_1.3.10-2.debian.tar.xz
 ff1a486f37f98f68d3d684f5f24524e2790e2ece 2 
python-mysqldb-dbg_1.3.10-2_amd64.deb
 361c7fa8be26fbc274b779a72a31f8802ffcb5a4 8379 
python-mysqldb_1.3.10-2_amd64.buildinfo
 d3021af41686035c6f5bbaf7532378270e7fa070 59112 
python-mysqldb_1.3.10-2_amd64.deb
 55f478413eef91d5a11c44d9b989d09d6afea988 33492 
python3-mysqldb-dbg_1.3.10-2_amd64.deb
 

Processed: affects 918439

[Debian Bug Tracking System]

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

> affects 918439 src:cockpit
Bug #918439 {Done: Martin Pitt } [libssh-4] cockpit: FTBFS 
(failing tests)
Bug #918892 {Done: Martin Pitt } [libssh-4] libssh-4: 0.8.6 
breaks server-side host key algorithm negotiation
Added indication that 918439 affects src:cockpit
Added indication that 918892 affects src:cockpit
> thanks
Stopping processing here.

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

Bug#919390: udev: network interface gets ID_NET_NAME even when NAME has been set by /etc/udev/rules.d/70-persistent-net.rules

[Michael Biebl]

Am 15.01.19 um 14:59 schrieb Michal Hocko:

> [3.563937] e1000e :00:1f.6 lan0: renamed from eth0
> 

Seems I can reproduce the issue, so there is no need on your side to
further debug debug this.
Will forward this to the upstream bug tracker.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#919393: Bug #919393 in python-mysqldb marked as pending

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #919393 in python-mysqldb 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-mysqldb/commit/e5f0fb5d9f68dc1ecd248b53490bc3e508bda64d


Add upstream patch to avoid FTBFS with recent MariaDB (Closes: #919393).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/919393

Processed: Bug #919393 in python-mysqldb marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #919393 [python-mysqldb] python-mysqldb: FTBFS with mariadb-10.3: 
_mysql.c:1911:41: error: 'MYSQL' {aka 'struct st_mysql'} has no member named 
'reconnect'
Added tag(s) pending.

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

Processed: tagging 919379

[Debian Bug Tracking System]

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

> tags 919379 + pending
Bug #919379 {Done: Bernd Zeimetz } [src:pmacct] pmacct: FTBFS 
with mariadb-10.3: mysql_plugin.c:672:10: error: 'MYSQL' {aka 'struct 
st_mysql'} has no member named 'reconnect'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#919390: udev: network interface gets ID_NET_NAME even when NAME has been set by /etc/udev/rules.d/70-persistent-net.rules

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #919390 [udev] udev: network interface gets ID_NET_NAME even when NAME has 
been set by /etc/udev/rules.d/70-persistent-net.rules
Severity set to 'serious' from 'normal'
> forwarded -1 https://github.com/systemd/systemd/issues/11436
Bug #919390 [udev] udev: network interface gets ID_NET_NAME even when NAME has 
been set by /etc/udev/rules.d/70-persistent-net.rules
Set Bug forwarded-to-address to 
'https://github.com/systemd/systemd/issues/11436'.

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

Bug#919399: FTBFS: undefined reference to makedev

[Ritesh Raj Sarraf]

Source: cowdancer
Version: 0.87
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)

Content-Type: multipart/mixed; boundary="===1317036836604284426=="
MIME-Version: 1.0
From: Ritesh Raj Sarraf 
To: Debian Bug Tracking System 
Subject: FTBFS: undefined reference to makedev
Message-ID: 
<154756077354.13753.2447109323940488229.report...@priyasi.researchut.com>
X-Mailer: reportbug 7.5.1
Date: Tue, 15 Jan 2019 19:29:33 +0530
X-Debbugs-Cc: r...@debian.org

This is a multi-part MIME message sent by reportbug.


--===1317036836604284426==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

U291cmNlOiBjb3dkYW5jZXIKVmVyc2lvbjogMC44NwpTZXZlcml0eTogc2VyaW91cwpUYWdzOiBw
YXRjaApKdXN0aWZpY2F0aW9uOiBmYWlscyB0byBidWlsZCBmcm9tIHNvdXJjZSAoYnV0IGJ1aWx0
IHN1Y2Nlc3NmdWxseSBpbiB0aGUgcGFzdCkKCgpsaWJ0b29sOiBjb21waWxlOiAgZ2NjIC1EUEFD
S0FHRV9OQU1FPVwiY293ZGFuY2VyXCIgLURQQUNLQUdFX1RBUk5BTUU9XCJjb3dkYW5jZXJcIiAt
RFBBQ0tBR0VfVkVSU0lPTj1cIjAuODdcIiAiLURQQUNLQUdFX1NUUklORz1cImNvd2RhbmNlciAw
Ljg3XCIiIC1EUEFDS0FHRV9CVUdSRVBPUlQ9XCJcIiAtRFBBQ0tBR0VfVVJMPVwiXCIgLURQQUNL
QUdFPVwiY293ZGFuY2VyXCIgLURWRVJTSU9OPVwiMC44N1wiIC1EU1REQ19IRUFERVJTPTEgLURI
QVZFX1NZU19UWVBFU19IPTEgLURIQVZFX1NZU19TVEFUX0g9MSAtREhBVkVfU1RETElCX0g9MSAt
REhBVkVfU1RSSU5HX0g9MSAtREhBVkVfTUVNT1JZX0g9MSAtREhBVkVfU1RSSU5HU19IPTEgLURI
QVZFX0lOVFRZUEVTX0g9MSAtREhBVkVfU1RESU5UX0g9MSAtREhBVkVfVU5JU1REX0g9MSAtREhB
VkVfRExGQ05fSD0xIC1ETFRfT0JKRElSPVwiLmxpYnMvXCIgLUkuIC1XZGF0ZS10aW1lIC1EX0ZP
UlRJRllfU09VUkNFPTIgLWZuby1zdHJpY3QtYWxpYXNpbmcgLURDT1dEQU5DRVJfU089XCIvdXNy
L2xpYi9jb3dkYW5jZXIvbGliY293ZGFuY2VyLnNvXCIgLWcgLU8yIC1mZGVidWctcHJlZml4LW1h
cD0vYnVpbGQvY293ZGFuY2VyLTAuODc9LiAtZnN0YWNrLXByb3RlY3Rvci1zdHJvbmcgLVdmb3Jt
YXQgLVdlcnJvcj1mb3JtYXQtc2VjdXJpdHkgLWMgY293ZGFuY2VyLmMgLW8gbGliY293ZGFuY2Vy
X2xhLWNvd2RhbmNlci5vID4vZGV2L251bGwgMj4mMQpsaWJ0b29sOiBsaW5rOiBnY2MgLWZuby1z
dHJpY3QtYWxpYXNpbmcgLURDT1dEQU5DRVJfU089XCIvdXNyL2xpYi9jb3dkYW5jZXIvbGliY293
ZGFuY2VyLnNvXCIgLWcgLU8yIC1mZGVidWctcHJlZml4LW1hcD0vYnVpbGQvY293ZGFuY2VyLTAu
ODc9LiAtZnN0YWNrLXByb3RlY3Rvci1zdHJvbmcgLVdmb3JtYXQgLVdlcnJvcj1mb3JtYXQtc2Vj
dXJpdHkgLVdsLC16IC1XbCxyZWxybyAtV2wsLXogLVdsLG5vdyAtbyBjb3didWlsZGVyIGNvd2J1
aWxkZXIubyBwYXJhbWV0ZXIubyBmb3JrZXhlYy5vIGlsaXN0Y3JlYXRlLm8gbWFpbi5vIGNvd2J1
aWxkZXJfdXRpbC5vIGxvZy5vICAtbGRsIC1sbmN1cnNlcwpsaWJ0b29sOiBsaW5rOiBnY2MgLWZu
by1zdHJpY3QtYWxpYXNpbmcgLURDT1dEQU5DRVJfU089XCIvdXNyL2xpYi9jb3dkYW5jZXIvbGli
Y293ZGFuY2VyLnNvXCIgLWcgLU8yIC1mZGVidWctcHJlZml4LW1hcD0vYnVpbGQvY293ZGFuY2Vy
LTAuODc9LiAtZnN0YWNrLXByb3RlY3Rvci1zdHJvbmcgLVdmb3JtYXQgLVdlcnJvcj1mb3JtYXQt
c2VjdXJpdHkgLVdsLC16IC1XbCxyZWxybyAtV2wsLXogLVdsLG5vdyAtbyBxZW11YnVpbGRlciBx
ZW11YnVpbGRlci1xZW11YnVpbGRlci5vIHFlbXVidWlsZGVyLXBhcmFtZXRlci5vIHFlbXVidWls
ZGVyLWZvcmtleGVjLm8gcWVtdWJ1aWxkZXItcWVtdWlwc2FuaXRpemUubyBxZW11YnVpbGRlci1x
ZW11YXJjaC5vIHFlbXVidWlsZGVyLWZpbGUubyBxZW11YnVpbGRlci1tYWluLm8gcWVtdWJ1aWxk
ZXItbG9nLm8gIC1sZGwgLWxuY3Vyc2VzCi91c3IvYmluL2xkOiBxZW11YnVpbGRlci1xZW11YXJj
aC5vOiBpbiBmdW5jdGlvbiBgcWVtdV9jcmVhdGVfYXJjaF9zZXJpYWxkZXZpY2UnOgouL3FlbXVh
cmNoLmM6NjA6IHVuZGVmaW5lZCByZWZlcmVuY2UgdG8gYG1ha2VkZXYnCi91c3IvYmluL2xkOiAu
L3FlbXVhcmNoLmM6NjI6IHVuZGVmaW5lZCByZWZlcmVuY2UgdG8gYG1ha2VkZXYnCi91c3IvYmlu
L2xkOiBxZW11YnVpbGRlci1xZW11YXJjaC5vOiBpbiBmdW5jdGlvbiBgcWVtdV9jcmVhdGVfYXJj
aF9kZXZpY2VzJzoKLi9xZW11YXJjaC5jOjg1OiB1bmRlZmluZWQgcmVmZXJlbmNlIHRvIGBtYWtl
ZGV2JwovdXNyL2Jpbi9sZDogLi9xZW11YXJjaC5jOjg3OiB1bmRlZmluZWQgcmVmZXJlbmNlIHRv
IGBtYWtlZGV2JwovdXNyL2Jpbi9sZDogLi9xZW11YXJjaC5jOjg5OiB1bmRlZmluZWQgcmVmZXJl
bmNlIHRvIGBtYWtlZGV2JwovdXNyL2Jpbi9sZDogcWVtdWJ1aWxkZXItcWVtdWFyY2gubzouL3Fl
bXVhcmNoLmM6OTE6IG1vcmUgdW5kZWZpbmVkIHJlZmVyZW5jZXMgdG8gYG1ha2VkZXYnIGZvbGxv
dwpjb2xsZWN0MjogZXJyb3I6IGxkIHJldHVybmVkIDEgZXhpdCBzdGF0dXMKbWFrZVsxXTogKioq
IFtNYWtlZmlsZTo5OTY6IHFlbXVidWlsZGVyXSBFcnJvciAxCm1ha2VbMV06ICoqKiBXYWl0aW5n
IGZvciB1bmZpbmlzaGVkIGpvYnMuLi4uCm1ha2VbMV06IExlYXZpbmcgZGlyZWN0b3J5ICcvYnVp
bGQvY293ZGFuY2VyLTAuODcnCmRoX2F1dG9fYnVpbGQ6IG1ha2UgLWo0IHJldHVybmVkIGV4aXQg
Y29kZSAyCm1ha2U6ICoqKiBbZGViaWFuL3J1bGVzOjY6IGJpbmFyeV0gRXJyb3IgMgpkcGtnLWJ1
aWxkcGFja2FnZTogZXJyb3I6IGRlYmlhbi9ydWxlcyBiaW5hcnkgc3VicHJvY2VzcyByZXR1cm5l
ZCBleGl0IHN0YXR1cyAyCkk6IGNvcHlpbmcgbG9jYWwgY29uZmlndXJhdGlvbgpFOiBGYWlsZWQg
YXV0b2J1aWxkaW5nIG9mIHBhY2thZ2UKSTogdW5tb3VudGluZyAvdmFyL2NhY2hlL2FwdC9hcmNo
aXZlcy8gZmlsZXN5c3RlbQpJOiB1bm1vdW50aW5nIGRldi9wdG14IGZpbGVzeXN0ZW0KSTogdW5t
b3VudGluZyBkZXYvcHRzIGZpbGVzeXN0ZW0KSTogdW5tb3VudGluZyBkZXYvc2htIGZpbGVzeXN0
ZW0KSTogdW5tb3VudGluZyBwcm9jIGZpbGVzeXN0ZW0KSTogdW5tb3VudGluZyBzeXMgZmlsZXN5
c3RlbQpJOiBjbGVhbmluZyB0aGUgYnVpbGQgZW52IApJOiByZW1vdmluZyBkaXJlY3RvcnkgL3Rt
cC8vOTUxNCBhbmQgaXRzIHN1YmRpcmVjdG9yaWVzCjE5OjE5IOKZkuKZkuKZkiAgICDimLkg8J+Y
nz0+IDEgIAoKCgoKCi0tIFN5c3RlbSBJbmZvcm1hdGlvbjoKRGViaWFuIFJlbGVhc2U6IGJ1c3Rl
ci9zaWQKICBBUFQgcHJlZmVycyB0ZXN0aW5nCiAgQVBUIHBvbGljeTogKDkwMCwgJ3Rlc3Rpbmcn
KSwgKDUwMCwgJ3Vuc3RhYmxlJyksICgxLCAnZXhwZXJpbWVudGFsJykKQXJjaGl0ZWN0dXJlOiBh

Bug#919398: nim FTBFS on big endian

[Adrian Bunk]

Source: nim
Version: 0.19.2-1
Severity: serious
Tags: ftbfs

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

...
Hint:  [Link]
Hint: operation successful (30380 lines compiled; 8.532 sec total; 31.883MiB 
peakmem; Debug Build) [SuccessX]
Hint: /<>/.cache/nim/times_d/runnableExamples/times_examples6  
[Exec]
times_examples6.nim(5)   times_examples6
system.nim(3877) failedAssertImpl
system.nim(3870) raiseAssert
system.nim(2916) sysFatal
Error: unhandled exception: 
/<>/.cache/nim/times_d/runnableExamples/times_examples6.nim(5, 12) 
`$utc(fromUnix(0)) == "1970-01-01T00:00:00Z"`  [AssertionError]
Error: execution of an external program failed: 
'/<>/.cache/nim/times_d/runnableExamples/times_examples6 '
[Examples] failed: see 
/<>/.cache/nim/times_d/runnableExamples/times_examples6.nim

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

Bug#919397: apcalc FTBFS on 32bit big endian

[Adrian Bunk]

Source: apcalc
Version: 2.12.7.2-1
Severity: serious
Tags: ftbfs

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

...
In file included from qmath.h:32,
 from cmath.h:32,
 from value.h:33,
 from calc.h:33,
 from file.c:39:
file.c: In function 'filepos2z':
zmath.h:85:46: error: incompatible types when assigning to type 'HALF' {aka 
'long unsigned int'} from type 'FILEPOS' {aka 'struct _G_fpos_t'}
 #define SWAP_HALF_IN_B32(dest, src) (*(dest) = *(src))
  ^
fposval.h:15:42: note: in expansion of macro 'SWAP_HALF_IN_B32'
 #define SWAP_HALF_IN_FILEPOS(dest, src)  SWAP_HALF_IN_B32(dest, src)
  ^~~~
file.c:1370:2: note: in expansion of macro 'SWAP_HALF_IN_FILEPOS'
  SWAP_HALF_IN_FILEPOS(ret.v, );
  ^~~~
make[1]: *** [Makefile:2364: file.o] Error 1

Bug#902760: marked as done (python-igraph FTBFS with ARPACK 3.6)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 14:47:01 +
with message-id 
and subject line Bug#902760: fixed in igraph 0.7.1-4
has caused the Debian Bug report #902760,
regarding python-igraph FTBFS with ARPACK 3.6
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.)


-- 
902760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-igraph
Version: 0.7.1.post6-5
Severity: serious
Tags: ftbfs

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

...
==
ERROR: testEigenvectorCentrality (igraph.test.structural.CentralityTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/structural.py", line 301, in 
testEigenvectorCentrality
cent = g.evcent()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi 
factorization

==
ERROR: testAuthorityScore (igraph.test.atlas.GraphAtlasTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/atlas.py", line 83, in testAuthorityScore
sc = g.authority_score()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi 
factorization

==
ERROR: testHubScore (igraph.test.atlas.GraphAtlasTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/atlas.py", line 71, in testHubScore
sc = g.hub_score()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi 
factorization

==
ERROR: testAuthorityScore (igraph.test.atlas.IsoclassTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/atlas.py", line 83, in testAuthorityScore
sc = g.authority_score()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi 
factorization

==
ERROR: testHubScore (igraph.test.atlas.IsoclassTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/atlas.py", line 71, in testHubScore
sc = g.hub_score()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi 
factorization

==
FAIL: testEigenvectorCentrality (igraph.test.atlas.GraphAtlasTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/atlas.py", line 35, in 
testEigenvectorCentrality
self.assertTrue(False, msg="Eigenvector centrality threw exception for 
graph #%d: %s" % (idx, ex))
AssertionError: Eigenvector centrality threw exception for graph #5: Error at 
arpack.c:944: ARPACK error, Could not build an Arnoldi factorization

==
FAIL: testEigenvectorCentrality (igraph.test.atlas.IsoclassTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/atlas.py", line 35, in 
testEigenvectorCentrality
self.assertTrue(False, msg="Eigenvector centrality threw exception for 
graph #%d: %s" % (idx, ex))
AssertionError: Eigenvector centrality threw exception for graph #3: Error at 
arpack.c:1174: ARPACK error, Could not build an Arnoldi factorization

--
Ran 307 tests in 9.738s

FAILED (failures=2, errors=5, skipped=3)
Test failed: 
error: Test failed: 
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:7: build-arch] Error 25
--- End Message ---
--- Begin Message ---
Source: igraph
Source-Version: 0.7.1-4

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

Bug#919379: marked as done (pmacct: FTBFS with mariadb-10.3: mysql_plugin.c:672:10: error: 'MYSQL' {aka 'struct st_mysql'} has no member named 'reconnect')

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 15:04:46 +
with message-id 
and subject line Bug#919379: fixed in pmacct 1.7.2-1
has caused the Debian Bug report #919379,
regarding pmacct: FTBFS with mariadb-10.3: mysql_plugin.c:672:10: error: 
'MYSQL' {aka 'struct st_mysql'} has no member named 'reconnect'
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.)


-- 
919379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pmacct
Version: 1.7.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

pmacct FTBFS with mariadb-10.3 in sid:

btool: compile:  gcc -DPACKAGE_NAME=\"pmacct\" -DPACKAGE_TARNAME=\"pmacct\" 
-DPACKAGE_VERSION=\"1.7.0\" "-DPACKAGE_STRING=\"pmacct 1.7.0\"" 
-DPACKAGE_BUGREPORT=\"pa...@pmacct.net\" -DPACKAGE_URL=\"\" -DPACKAGE=
\"pmacct\" -DVERSION=\"1.7.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNIST
D_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DLINUX=1 -DPROGNAME=1 
-DIM_LITTLE_ENDIAN=1 -DHAVE_L2=1 -DHAVE_INET_PTON=1 -DHAVE_INET_NTOP=1 
-DENABLE_IPV6=1 -DENABLE_PLABEL=1 -DHAVE_PCAP_H=1 -DHAVE_LIBPCAP=1 -DPCA
P_NOBPF=1 -DPCAP_TYPE_linux=1 -DWITH_MYSQL=1 -DWITH_PGSQL=1 -DWITH_SQLITE3=1 
-DWITH_RABBITMQ=1 -DWITH_ZMQ=1 -DWITH_KAFKA=1 -DWITH_GEOIPV2=1 -DWITH_JANSSON=1 
-DHAVE_LIBJANSSON=1 -DHAVE_JSON_OBJECT_UPDATE_MISSING=1
 -DHAVE_DLOPEN=1 -DHAVE_ZLIB=1 -DSTDC_HEADERS=1 -DHAVE_SYS_WAIT_H=1 
-DHAVE_GETOPT_H=1 -DHAVE_SYS_SELECT_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_U_INT64_T=1 
-DHAVE_U_INT32_T=1 -DHAVE_U_INT16_T=1 -DHAVE_U_INT8_T=1 -DHAVE_UI
NT64_T=1 -DHAVE_UINT32_T=1 -DHAVE_UINT16_T=1 -DHAVE_UINT8_T=1 
-DHAVE_64BIT_COUNTERS=1 -DENABLE_THREADS=1 -D_XOPEN_SOURCE=600 -D_GNU_SOURCE=1 
-DWITH_NFLOG=1 -DHAVE_TRAFFIC_BINS=1 -DHAVE_BGP_BINS=1 -DHAVE_BMP_BINS=
1 -DHAVE_ST_BINS=1 -DRETSIGTYPE=void -DHAVE_VSNPRINTF=1 -DHAVE_MALLOPT=1 
-DHAVE_TDESTROY=1 "-DCOMPILE_ARGS=\" '--build=i686-linux-gnu' '--prefix=/usr' 
'--includedir=\${prefix}/include' '--mandir=\${prefix}/share/
man' '--infodir=\${prefix}/share/info' '--sysconfdir=/etc' 
'--localstatedir=/var' '--disable-silent-rules' 
'--libdir=\${prefix}/lib/i386-linux-gnu' 
'--libexecdir=\${prefix}/lib/i386-linux-gnu' '--disable-maintain
er-mode' '--disable-dependency-tracking' 
'--with-pgsql-includes=/usr/include/postgresql' '--enable-l2' '--enable-ipv6' 
'--enable-plabel' '--enable-mysql' '--enable-pgsql' '--enable-sqlite3' 
'--enable-rabbitmq' '-
-enable-zmq' '--enable-kafka' '--enable-geoipv2' '--enable-jansson' 
'--enable-64bit' '--enable-threads' '--enable-traffic-bins' '--enable-bgp-bins' 
'--enable-bmp-bins' '--enable-st-bins' '--enable-nflog' 'build_a
lias=i686-linux-gnu' 'CFLAGS=-g -O2 -fdebug-prefix-map=/build/pmacct-1.7.0=. 
-fstack-protector-strong -Wformat -Werror=format-security' 
'LDFLAGS=-Wl,-z,relro' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'\"" -I. -Wd
ate-time -D_FORTIFY_SOURCE=2 -I/usr/include/mariadb 
-I/usr/include/mariadb/mysql -I/usr/include/postgresql -isystem 
/usr/include/mit-krb5 -I/usr/include/pgm-5.2 
-I/usr/lib/i386-linux-gnu/pgm-5.2/include -I/usr/in
clude/i386-linux-gnu -I/usr/include/mariadb -I/usr/include/mariadb/mysql 
-I/usr/include/postgresql -isystem /usr/include/mit-krb5 -I/usr/include/pgm-5.2 
-I/usr/lib/i386-linux-gnu/pgm-5.2/include -O2 -g -O2 -fdebu
g-prefix-map=/build/pmacct-1.7.0=. -fstack-protector-strong -Wformat 
-Werror=format-security -c mysql_plugin.c  -fPIC -DPIC -o 
.libs/libdaemons_la-mysql_plugin.o
In file included from mysql_plugin.c:30:
sql_common_m.c: In function 'SQL_SetENV_child':
sql_common_m.c:261:43: warning: format '%u' expects argument of type 'unsigned 
int', but argument 4 has type 'time_t' {aka 'const long int'} [-Wformat=]
 snprintf(tmpptr, envbuf.end-tmpptr, "%u", idata->elap_time);
  ~^   
  %lu
sql_common_m.c:294:43: warning: format '%u' expects argument of type 'unsigned 
int', but argument 4 has type 'time_t' {aka 'const long int'} [-Wformat=]
 snprintf(tmpptr, envbuf.end-tmpptr, "%u", idata->basetime);
  ~^   ~~~
  %lu
sql_common_m.c:305:43: warning: format '%u' expects argument of type 'unsigned 
int', but argument 4 has type 'time_t' {aka 'const long int'} [-Wformat=]
 snprintf(tmpptr, envbuf.end-tmpptr, "%u", idata->timeslot);
   

Bug#902945: marked as done (igraph: FTBFS with ARPACK 3.6)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 14:47:01 +
with message-id 
and subject line Bug#902760: fixed in igraph 0.7.1-4
has caused the Debian Bug report #902760,
regarding igraph: FTBFS with ARPACK 3.6
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.)


-- 
902760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: igraph
Version: 0.7.1-2.1
Severity: serious
Tags: ftbfs

Hi maintainer

Since the upload of arpack 3.6.0-1 to unstable, igraph FTBFS [1] with
the following test failures:

BLAS, LAPACK and ARPACK based functions

191: Basic BLAS functions (igraph_blas_*):   ok
192: Dense symmetric eigenvalues and eigenvectors (igraph_lapack_dsyevr): ok
193: Dense non-symmetric eigenvalues and eigenvectors (igraph_lapack_dgeev): ok
194: Dense non-symmetric eigenvalues and eigenvectors (igraph_lapack_dgeevx): ok
195: Solving linear systems with LU factorization (igraph_lapack_dgesv): ok
196: Upper Hessenberg transformation (igraph_lapack_dgehrd): ok
197: Eigenvector centrality (igraph_eigenvector_centrality): FAILED
(arpack.at:59)
198: Non-symmetric ARPACK solver (igraph_arpack_rnsolve): FAILED (arpack.at:66)

Bipartite graphs

199: Create bipartite graphs (igraph_create_bipartite): ok
200: Projection of bipartite graphs (igraph_bipartite_projection): ok

Centralization

201: Centralization (igraph_centralization_*):   FAILED
(centralization.at:26)

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/history/amd64/igraph.html
--- End Message ---
--- Begin Message ---
Source: igraph
Source-Version: 0.7.1-4

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated igraph package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 15 Jan 2019 15:10:32 +0100
Source: igraph
Binary: libigraph0v5 libigraph0-dev
Architecture: source
Version: 0.7.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libigraph0-dev - library for creating and manipulating graphs - development 
files
 libigraph0v5 - library for creating and manipulating graphs
Closes: 902760
Changes:
 igraph (0.7.1-4) unstable; urgency=medium
 .
   * use a different starting vector for
 igraph_community_leading_eigenvector() to prevent errors
 with ARPACK 3.6.3 (Thanks for the patch to Tamás Nepusz)
 Closes: #902760
   * Drop Tamás Nepusz  from uploaders (Tamás, thanks
 for your previous work on the Debian package and the support you
 provide on upstream code)
   * debhelper 12
   * Standards-Version: 4.3.0
Checksums-Sha1:
 b9b915651287f1047c3b7fa3ca7a57d9083dd1a5 2101 igraph_0.7.1-4.dsc
 9815a35f54c4ef94601a06b0624a6e0e0b82a473 13024 igraph_0.7.1-4.debian.tar.xz
Checksums-Sha256:
 c079947c402bba1ac9e9e6c52c2a927cffd45810f544d510d265b02935c128f9 2101 
igraph_0.7.1-4.dsc
 8c890d7f6165480654b45f091680e409182e09ba2abece2467e9f32b08ca7812 13024 
igraph_0.7.1-4.debian.tar.xz
Files:
 6f35cd744dac72806a41432ae3c04c6c 2101 libs optional igraph_0.7.1-4.dsc
 9bc16c8b3da3926dc896fc47c19a1dc8 13024 libs optional 
igraph_0.7.1-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlw97JMRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGyshAAgFmS8A3IAIHDXQ3y/tU+pP2fvdHW1KPX
stucNUNI64tuTYgYlNWhlRzpMHrCsat9i/ixcMAU2f0oCTUwAaG3eKsz8ch2axQR
dxxC30Vy0iHAihq3hUEvPuhNdZp4msHmZksA/zSafqWSuy3jTMClDhMX+SiulAXH
o6EQsEJK+5mC5lcaEg0f5EMqQTzlkG7hIUALC6Pw961feuIGCDkK0STW93f/ghYK
7u6b4knFA2ev2/jeNUgDIVKNLWiw3jdvC228ctsw3NOlBaTaAlAvOd7Xwc2Af/Jc
0S1qjPNojvUt73SwAzMfYjAk4aYcdxmOqunTz4Fyre/K9cLaD7Ad1PjOSOYWfMGc
qkUImiKtCZWVWIaIWwg5Q4pFbMvQa5kM1xNdVf3qInTZoJBEcryiNpl6CeDnw3IZ
9khnQaF6OaZlOtlariT+uf3j3jgf7zOPbdVdHuGzEGYfk0123PLCFB/y7j0XaMeF
60R+5fAtjzSSDRyu/7/RedM/dbdj+kVFjfUlWNGsVmnTEhjhzQKMtEgBXMxEgZCp
0XPZWocVu7AVJKt1HU1R8hW+1XT+kERxM/qGjfHM8zIL0st0jEoqfnrID7mitEPs
942yqtwFPfRoAqC3VBEITrhhaXVJ6+CiwQKJLO63CwMeQzdT4X0qi4SK6Z1+Uc9Q

Bug#916286:

[Remon Sijrier]

New tarball link: http://traverso-daw.org/traverso-0.49.6.tar.gz

Bug#918409: marked as done (node-merge-descriptors FTBFS with nodejs 10.15.0)

[Debian Bug Tracking System]

Your message dated Tue, 15 Jan 2019 13:35:06 +
with message-id 
and subject line Bug#918409: fixed in node-merge-descriptors 1.0.1-2
has caused the Debian Bug report #918409,
regarding node-merge-descriptors FTBFS with nodejs 10.15.0
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.)


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-merge-descriptors.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/node-merge-descriptors-1.0.1'
mocha --reporter spec --bail --check-leaks test/


  merge(dest, src)
arguments
  dest
1) should be required


  0 passing (52ms)
  1 failing

  1) merge(dest, src)
   arguments
 dest
   should be required:
 TypeError [ERR_AMBIGUOUS_ARGUMENT]: The "error/message" argument is 
ambiguous. The error message "argument dest is required" is identical to the 
message.
  at expectsError (assert.js:629:15)
  at Function.throws (assert.js:690:3)
  at Context. (test/merge.js:19:16)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:354:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:346:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:442:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:560:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:356:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:366:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:290:14)
  at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:334:5)



make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: node-merge-descriptors
Source-Version: 1.0.1-2

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

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

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-merge-descriptors 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 15 Jan 2019 14:14:22 +0100
Source: node-merge-descriptors
Binary: node-merge-descriptors
Architecture: source
Version: 1.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Xavier Guimard 
Changed-By: Xavier Guimard 
Closes: 918409
Description: 
 node-merge-descriptors - merge objects using descriptors
Changes:
 node-merge-descriptors (1.0.1-2) unstable; urgency=medium
 .
   * Team upload
   * Add gbp.conf
   * Add patch to update error strings in test (Closes: #918409)
   * Declare compliance with policy 4.3.0
   * Fix debian/copyright format url
   * Skip tests if "nocheck" is set
   * Add upstream/metadata file
Checksums-Sha1: 
 50cbf6d9f940c696f45a54695b7969bbcd3c9859 2166 
node-merge-descriptors_1.0.1-2.dsc
 080d32929b0f44fac9c7deabec468251d8018008 3080 
node-merge-descriptors_1.0.1-2.debian.tar.xz
Checksums-Sha256: 
 8bde7f7d0a9e7d685215ca2fb68156c287048d28427a1daf1143ea66c582fb24 2166 
node-merge-descriptors_1.0.1-2.dsc
 f2b79b202b71ad02a817b4b93be0ffab618d13fcacd876eb6b652a862dafb872 3080 
node-merge-descriptors_1.0.1-2.debian.tar.xz
Files: 
 d9cb1bf5a563a29888712ed7fb3355de 2166 javascript optional 
node-merge-descriptors_1.0.1-2.dsc
 2edbf6a7616fbd1c25fb44ed0f814bdd 3080 javascript optional 
node-merge-descriptors_1.0.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlw93icQHHlhZGRAZGVi
aWFuLm9yZwAKCRD210ynyZnu6V/TEACUcgSGGq9wHZkYtzvcgJw4c8/3dg4ZA2gV
bNYjtTkGS5tbrd3UfYUdVrnAvEZdO0rm1oiZYsd+r8y7zDty31YT+cLvE4WC0Hlx
Hfm5HoyarlE5OR0EZMpfS/ddYOGbwtfAfbyMootJBPV17d7TVS64wpb2rqHT7Efm
Djzfr5p01edkEqB+IWgoz5XKD7s2WoF0KQWdq+ocFq6amsHN3kjKJVQ+KXaG8+Mb
9vBKUSl3vBA9EBDHoJiQzYtuJmlTMRkMiI8oR8gLDewgqIiexZJQD8ghpamFpKvu
tjXqPY46IFt4CqKp7GAtnkP8DeXL1lZXSKpLK6m+caVdIzzjgjNotsWfMEQuTMaK
lfMPfw1F+/3sYQU2hguCPMPHNTj26l8WpQmfdBYoPNqsaiyNQLGGfO2X88WW8baf

Bug#916286: traverso: baseline violation on i386

[Remon Sijrier]

Hello,

By default Traverso has DETECT_HOST_CPU_FEATURES set to ON, will update
this to OFF, should fix the issue.

Will post updated tarball soon on traverso website, thanks

Remon

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

[Michael Biebl]

Control: severity -1 important


I'm downgrading this to non-RC, as I'm not convinced this is actually a
bug in udev

Am 15.01.19 um 09:08 schrieb Axel Beckert:
> Control: found -1 239-15
> 
> Hi Michael,
> 
> Michael Biebl wrote:
>> Am 12.01.19 um 01:02 schrieb Axel Beckert:
>>> Control: reopen -1
>>> Control: found -1 240-3
>>
>>> *sigh* I'm sorry to say, but it just happened again with udev 240-3
>>> and kernel 4.20-1~exp1.
>>
>> Would be good to know, if it also happens with 239-15 or if it's caused
>> by some other update.
> 
> I just downloaded udev and libudev1 239-15 from
> https://snapshot.debian.org/, installed it and immediately afterwards
> ran "udevadm control --reload-rules" and everything was gone again.
> (Was running under kernel 4.20-1~exp1.)
> 
> After that I rebooted into 4.20-1~exp1 with the downgraded udev again,
> ran "udevadm control --reload-rules" directly after reboot and nothing
> (unexpected) happened.
> 
> Then I started to write this mail, doing not much more than logging in
> on the text console (despite X was running) using zsh, running
> ssh-agent, ssh-add and then ssh via autossh to connect to a screen
> session on some other host to write the mail with mutt.
> 
> After about 20 minutes of uptime I was about to send that mail and
> thought, I should just try running "udevadm control --reload-rules"
> once again: And it killed all processes again -- systemd-udevd has
> been started again, too:
> 
> ~ # ps auxwww | fgrep udev
> root 10696  0.0  0.0  13152  3592 ?S08:27   0:00 
> /lib/systemd/systemd-udevd
> root 11582  0.0  0.0   8144   892 tty1 R+   08:33   0:00 grep -F 
> --color=auto udev
> ~ # uptime
>  08:33:49 up 25 min,  2 users,  load average: 0.07, 0.15, 0.34
> 
> Unfortunately there is not much in the syslog (had to start rsyslog
> first again, too):
> 
> Jan 15 08:37:16 c6 kernel: [ 1717.930890] printk: systemd-udevd: 159 output 
> lines suppressed due to ratelimiting
> 
> I though didn't get rsyslog to drop the rate-limiting and I'm a little
> bit in a hurry at the moment.
> 
> Will report back later.
> 
> I must admit that I also had one crash/process killing yesterday where
> I can't say what triggered it. aptitude just finished starting up in
> TUI mode (inside screen started via ssh from remote) and I was
> starting to browse through the package list while the connection
> suddenly was lost (likely due to a killed sshd).


This all sounds, like udevd is not the root cause of all this, tbh,
especially since you also reproduced it with 239.
I think "udevadm trigger" trigger something when then causes another
component of your system to act this way.

> Some other facts gathered recently:
> 
> * With udev 239-15 the bootup lag is gone even without the "sleep 5".
> 
> * The "sleep 5" helped on another box (EeePC 900A with sysvinit) where
>   drivers weren't loaded anymore and had to be specified manually in
>   /etc/modules until the "sleep 5" was added.
> * memtest86 and memtest86+ just show an empty screen. Will try again
>   with grub's graphical mode disabled just to make sure the issue is
>   not triggered by some memory fault. Question would be then why I
>   could (within a reboot where it happened) reliably reproduce the
>   issue again and again. Will report any findings on this front.
> * As alternative I ran memtester for one night, no issues found. (Not
>   sure if it was able to test everything as the affected box has 64 GB
>   of RAM.)
> * If the issue happens while using X, there's no chance to switch back
>   to the text console with the getty to login again. The machine needs
>   a hard reboot via reset or power button then.
> 
>> Tbh, udevd or udevadm control --reload killing all processes, sounds
>> pretty strange.
> 
> Definitely.
> 
>> Can you also try to run udevd in debug mode to get a log from udevd (see
>> /etc/udev/udev.conf) and also an strace of the udevadm command.
> 
> I think I alread sent the strace, but forgot the debug mode. Enabled
> that when starting to write this mail, but it's currently caught by
> rsyslogd's rate-limiting, see above.

It's the kernel, which does the rate limiting. Add
log_buf_len=1M printk.devkmsg=on
to the kernel command line to turn off the ratelimiting and increase the
ring buffer.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #918764 [udev] udev: "udevadm control --reload-rules" kills all processes 
except init
Severity set to 'important' from 'critical'

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