Bug#959075: marked as done (ifupdown: Bonding is not working with ifenslave 2.10 wich removes ifenslave command)

[Debian Bug Tracking System]

Your message dated Sat, 27 Jun 2020 05:48:23 +
with message-id 
and subject line Bug#959075: fixed in ifenslave 2.10+nmu2
has caused the Debian Bug report #959075,
regarding ifupdown: Bonding is not working with ifenslave 2.10 wich removes 
ifenslave command
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.)


-- 
959075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ifupdown
Version: 0.8.35+b1
Severity: normal

Dear Maintainer,

The ifenslave package does not provides ifenslave command anymore
(starting from 2.10), bonding interface needs to be done with iproute2 :
# ip link set enp6s0 master bond0

I think ifupdown uses ifenslave command, because my system does not
bring my bond anymore.


-- Package-specific info:
--- /etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto enp6s0
iface enp6s0 inet manual
  ethernet-wol g
#  offload-lro off
#  offload-gro off

auto enp7s0
iface enp7s0 inet manual
  ethernet-wol g
#  offload-lro off
#  offload-gro off

auto bond0
iface bond0 inet manual
  bond-slaves enp6s0 enp7s0
  bond-mode balance-alb
  bond-miimon 100
  mtu 9000

auto br0
iface br0 inet static
  bridge_ports bond0
  bridge_fd 0
  bridge_stp off
  address 10.0.0.1
  netmask 255.255.255.0
  gateway 10.0.0.4
  dns-nameservers 10.0.0.4
  dns-search pastis21.loc
  up ip r a 213.163.183.90 via 10.0.0.4
  down ip r r 213.163.183.90 via 10.0.0.4

# Interface Wifi
#allow-hotplug wlan0
#iface wlan0 inet dhcp
#   wpa-conf /etc/wpa_supplicant.conf

--- up and down scripts installed:
/etc/network/if-down.d:
total 4
-rwxr-xr-x 1 root root 800 Jan  9  2017 postfix
lrwxrwxrwx 1 root root  32 Mar 24 11:13 wpasupplicant -> 
../../wpa_supplicant/ifupdown.sh

/etc/network/if-post-down.d:
total 8
lrwxrwxrwx 1 root root   23 Dec 13 17:00 avahi-daemon -> ../if-up.d/avahi-daemon
lrwxrwxrwx 1 root root   29 Jan 28  2019 bridge -> /lib/bridge-utils/ifupdown.sh
-rwxr-xr-x 1 root root 1714 Sep 27  2016 ifenslave
-rwxr-xr-x 1 root root  907 Jan 19  2012 vde2
lrwxrwxrwx 1 root root   32 Mar 24 11:13 wpasupplicant -> 
../../wpa_supplicant/ifupdown.sh

/etc/network/if-pre-up.d:
total 16
lrwxrwxrwx 1 root root   29 Jan 28  2019 bridge -> /lib/bridge-utils/ifupdown.sh
-rwxr-xr-x 1 root root  344 Jun  7  2010 ethtool
-rwxr-xr-x 1 root root 6417 May  8  2018 ifenslave
-rwxr-xr-x 1 root root 1793 Jan 19  2012 vde2
lrwxrwxrwx 1 root root   32 Mar 24 11:13 wpasupplicant -> 
../../wpa_supplicant/ifupdown.sh

/etc/network/if-up.d:
total 16
-rwxr-xr-x 1 root root  484 Mar  6  2013 avahi-daemon
-rwxr-xr-x 1 root root 1685 Sep 22  2014 ethtool
-rwxr-xr-x 1 root root 1741 Sep 27  2016 ifenslave
-rwxr-xr-x 1 root root 1117 Jan  9  2017 postfix
lrwxrwxrwx 1 root root   32 Mar 24 11:13 wpasupplicant -> 
../../wpa_supplicant/ifupdown.sh


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

Kernel: Linux 5.5.0-2-amd64 (SMP w/8 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 ifupdown depends on:
ii  adduser   3.118
ii  iproute2  5.6.0-1
ii  libc6 2.30-4
ii  lsb-base  11.1.0

Versions of packages ifupdown recommends:
ii  isc-dhcp-client [dhcp-client]  4.4.1-2.1+b2

Versions of packages ifupdown suggests:
ii  ppp 2.4.7-2+4.1+deb10u1
pn  rdnssd  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ifenslave
Source-Version: 2.10+nmu2
Done: Paul Wise 

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

Debian distribution maintenance software
pp.
Paul Wise  (supplier of updated ifenslave package)

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

Bug#959236: marked as done (Bringing up a bond results in an infinite loop)

[Debian Bug Tracking System]

Your message dated Sat, 27 Jun 2020 05:48:23 +
with message-id 
and subject line Bug#959075: fixed in ifenslave 2.10+nmu2
has caused the Debian Bug report #959075,
regarding Bringing up a bond results in an infinite loop
to be marked as done.

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

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


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

When trying to bring up a bonded network, I ran into this recursion depth error:

May 01 01:56:41 hostname ifup[4380]: /etc/network/if-pre-up.d/ifenslave: 67: 
Maximum function recursion depth (1000) reached
May 01 01:56:41 hostname ifup[4378]: run-parts: 
/etc/network/if-pre-up.d/ifenslave exited with return code 2
May 01 01:56:41 hostname ifup[4371]: ifup: failed to bring up bond1

This appears to be due to ifenslave using the same function name setup_master() 
twice in the same file and incorrectly calling itself.

The bond is in my interfaces file as:

allow-hotplug bond1
auto bond1

iface bond1 inet static
address 192.168.3.1/24
mtu 9000
bond-mode 4
bond-miimon 100
bond-lacp-rate 0
bond-slaves enp129s0f0 enp129s0f1 enp131s0f0 enp131s0f1
bond-min-links 2
bond-xmit_hash_policy layer2+3

iface bond1 inet static
address 192.168.5.100/24

iface bond1 inet static
address 192.168.5.99/24

System is Linux 5.6.0-1-amd64 #1 SMP Debian 5.6.7-1 (2020-04-29) x86_64 
GNU/Linux--- End Message ---
--- Begin Message ---
Source: ifenslave
Source-Version: 2.10+nmu2
Done: Paul Wise 

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

Debian distribution maintenance software
pp.
Paul Wise  (supplier of updated ifenslave package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 27 Jun 2020 13:41:40 +0800
Source: ifenslave
Architecture: source
Version: 2.10+nmu2
Distribution: unstable
Urgency: medium
Maintainer: Guus Sliepen 
Changed-By: Paul Wise 
Closes: 959075
Changes:
 ifenslave (2.10+nmu2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Re-add mistakenly removed variables. Closes: #959075
Checksums-Sha1:
 22e7f3fc9f4df636e4585a9af75c18121988860c 1574 ifenslave_2.10+nmu2.dsc
 40d521ef400135d335e7e43d9b0ad747ee91e663 11952 ifenslave_2.10+nmu2.tar.xz
Checksums-Sha256:
 528c03ea76815a775084025463fb6309bba025cc67c4ef1af3ae527eb0a7cde6 1574 
ifenslave_2.10+nmu2.dsc
 93da864c41e91502794d2aa1c0c6e2e7427bfc16147ca2e54449eecaeae52850 11952 
ifenslave_2.10+nmu2.tar.xz
Files:
 1647d00bbf7d5211f0707b630a9e6075 1574 net optional ifenslave_2.10+nmu2.dsc
 786fbf99802f1016e6bb93e9358ed073 11952 net optional ifenslave_2.10+nmu2.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAl723J0ACgkQMRa6Xp/6
aaOfCRAAk1mv0QY6munWIAW7mL2kvMNKTl3JaZoAIYJ0kv9vFOAu2jxLDGnQ/XzJ
W8MhoCrz8eIfye5l9xoOp0KXnNnDsnANpE3fKVMDbNeH4mT/bxbheWSmrR+Sjbi3
agyurJi8SaVNZZNW8CIKNwYXdbP+cNA3CtTjAM6cxIEnp0Y5wPzJl4M1X0WXBXJa
f8qxk4fBI1BOZ4WAdFHzItVNOTeG8Qg6bOqsEqhF8/X48/76PWv7xrbKJYOPNOrI
lX2GCYSnTkYFFay66Xpy/zqdmNIIJKUtvEjWo+qgy9curR/ia6SMDxfsGZalgrKp
I/+4TODovizhJpdz0xIPlQQXuzlwPiDjfKrQ+LAej8Jcm9Gc3Lx0x17nAcwFyjjx
r7w3PP51rZ3J24EFWKctRa41YKeZije6D5U66K+IFr9HOjVmiZ8cI2Dp/cCdBukV
TbMpnxAlvU7+OVttly7gmhwnqlVz/g4+jp7GM5w2L+g2aHpzB1r3bQb2IJv6u2LG
JNh35aP0APU9HMJALxff6Gh5KO9dQ/iFMOknyBt3B2ASzxeTPXJ41hovExgeBZey
CIGHR8MS4NEdnWJmQL3NydUTKb07tjsd2ljQpLVqJh+Uf+yJ4Cwwr7leI4vk/BxP
PP9TyOKCOpBkr3g8kvkmQbMO6cZJho1wVm7Evd7HRX6p7bar+Fw=
=Uakn
-END PGP SIGNATURE End Message ---

Processed: reopening 959075

[Debian Bug Tracking System]

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

> reopen 959075
Bug #959075 {Done: Paul Wise } [ifenslave] ifupdown: Bonding 
is not working with ifenslave 2.10 wich removes ifenslave command
Bug #959236 {Done: Paul Wise } [ifenslave] Bringing up a bond 
results in an infinite loop
'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 ifenslave/2.10+nmu1.
No longer marked as fixed in versions ifenslave/2.10+nmu1.
> thanks
Stopping processing here.

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

Bug#963211: Still occurs in 1:3.9-3

[Andreas Metzler]

On 2020-06-25 Jordi Mallach  wrote:
> Hi, I'm away for the week so I'd welcome a nmu. I assume this just
> needs further bumping the breaks/replaces to - 3~, but have no means
> to test. 

I will probably have time for this in afternoon. 


cu Andreas

Bug#963721: [pkg-cryptsetup-devel] Bug#963721: libcryptsetup12 v2:2.3.3-1 seems to be breaking libssl somehow

[Christian Weeks]

On Sat, 2020-06-27 at 04:35 +0200, Guilhem Moulin wrote:
> On Fri, 26 Jun 2020 at 20:39:32 -0400, Christian Weeks wrote:
> > After some more googling, it seems that the REAL culprit might be
> > libmount1.
> 
> Should this be reassigned to util-linux/2.35.2-5 then?

I guess so? I don't know how to do that.
>  
> > This seems like a really messy tangled web of nastiness. Good luck
> > figuring it out.
> 
> Unless there is a reproducer involving a targeted libcryptsetup12
> upgrade I don't think this belong here :-P  Aside from documentation
> files, the only thing libcryptsetup12 (2:2.1.0-5+deb10u2 and 2:2.3.3-1)
> ships is libcryptsetup.so.12*.  It doesn't touch libssl.
> 

It seems that libcryptsetup + the new libmount1 dependency on same are
the root cause somehow. Sorry for the confusion.

Processed (with 1 error): Re: Bug#963783: dependency problems prevent configuration of libgnutls-dane0:

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libmu-dbm6
Bug #963783 [libgnutls-dane0] dependency problems prevent configuration of 
libgnutls-dane0:
Bug reassigned from package 'libgnutls-dane0' to 'libmu-dbm6'.
Ignoring request to alter found versions of bug #963783 to the same values 
previously set
Ignoring request to alter fixed versions of bug #963783 to the same values 
previously set
> retitle libmu-dbm6 1:3.9-3 missing breaks/replaces with libmailutils6 
> 1:3.7-2.1
Unknown command or malformed arguments to command.

> forcemerge 963211 963783
Bug #963211 [libmu-dbm6] libmu-dbm6: Tries to overwrite `libmu_dbm.so.6.0.0` 
from `libmailutils6`
Bug #963783 [libmu-dbm6] dependency problems prevent configuration of 
libgnutls-dane0:
Severity set to 'serious' from 'normal'
Marked as found in versions mailutils/1:3.9-2 and mailutils/1:3.9-3.
Merged 963211 963783

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

Processed: fixed 875112 in projectm/3.1.3-1, closing 875112

[Debian Bug Tracking System]

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

> fixed 875112 projectm/3.1.3-1
Bug #875112 [src:projectm] [projectm] Future Qt4 removal from Buster
Marked as fixed in versions projectm/3.1.3-1.
> close 875112
Bug #875112 [src:projectm] [projectm] Future Qt4 removal from Buster
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 924925

[Debian Bug Tracking System]

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

> close 924925
Bug #924925 [projectm-pulseaudio] projectm-pulseaudio crashes after a few 
seconds
Bug #931900 [projectm-pulseaudio] Program crashes with message "free(): double 
free detected in tcache 2"
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: fixed 924925 in projectm-pulseaudio/3.1.3-1

[Debian Bug Tracking System]

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

> fixed 924925 projectm-pulseaudio/3.1.3-1
Bug #924925 [projectm-pulseaudio] projectm-pulseaudio crashes after a few 
seconds
Bug #931900 [projectm-pulseaudio] Program crashes with message "free(): double 
free detected in tcache 2"
The source projectm-pulseaudio and version 3.1.3-1 do not appear to match any 
binary packages
Marked as fixed in versions projectm-pulseaudio/3.1.3-1.
Marked as fixed in versions projectm-pulseaudio/3.1.3-1.
> thanks
Stopping processing here.

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

Processed (with 1 error): unarchiving 875112, reopening 875112, unarchiving 924925, reopening 924925, unarchiving 621789 ...

[Debian Bug Tracking System]

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

> # src:projectm was reintroduced: 
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 875112
Bug #875112 {Done: Debian FTP Masters } 
[src:projectm] [projectm] Future Qt4 removal from Buster
Unarchived Bug 875112
> reopen 875112
Bug #875112 {Done: Debian FTP Masters } 
[src:projectm] [projectm] Future Qt4 removal from Buster
'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 2.1.0+dfsg-4+rm.
> unarchive 924925
> reopen 924925
Bug #924925 {Done: Dennis Braun } [projectm-pulseaudio] 
projectm-pulseaudio crashes after a few seconds
Bug #931900 {Done: Dennis Braun } [projectm-pulseaudio] 
Program crashes with message "free(): double free detected in tcache 2"
'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 2.1.0+dfsg-4+rm and 
projectm-pulseaudio/3.1.3-1.
No longer marked as fixed in versions 2.1.0+dfsg-4+rm and 
projectm-pulseaudio/3.1.3-1.
> unarchive 621789
Bug #621789 {Done: Debian FTP Masters } 
[libprojectm2] ProjectM seg default crash with ATI video cards
Unarchived Bug 621789
> reopen 621789
Bug #621789 {Done: Debian FTP Masters } 
[libprojectm2] ProjectM seg default crash with ATI video cards
'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 2.1.0+dfsg-4+rm.
> unarchive 699383
Bug #699383 {Done: Debian FTP Masters } 
[libprojectm2] libprojectm2: unlisted dependency on package ttf-bitstream-vera
Unarchived Bug 699383
> reopen 699383
Bug #699383 {Done: Debian FTP Masters } 
[libprojectm2] libprojectm2: unlisted dependency on package ttf-bitstream-vera
'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 2.1.0+dfsg-4+rm.
> unarchive 833489
Bug #833489 {Done: Debian FTP Masters } 
[projectm-pulseaudio] projectm-pulseaudio: ttf-dejavu-core dependency not listed
Unarchived Bug 833489
> reopen 833489
Bug #833489 {Done: Debian FTP Masters } 
[projectm-pulseaudio] projectm-pulseaudio: ttf-dejavu-core dependency not listed
'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 2.1.0+dfsg-4+rm.
> unarchive 893926
Bug #893926 {Done: Debian FTP Masters } 
[projectm-data] mark projectm-data Multi-Arch: foreign
Unarchived Bug 893926
> reopen 893926
Bug #893926 {Done: Debian FTP Masters } 
[projectm-data] mark projectm-data Multi-Arch: foreign
'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 2.1.0+dfsg-4+rm.
> unarchive 908856
Bug #908856 {Done: Debian FTP Masters } 
[projectm-data] mark projectm-data Multi-Arch: foreign
Unarchived Bug 908856
> reopen 908856
Bug #908856 {Done: Debian FTP Masters } 
[projectm-data] mark projectm-data Multi-Arch: foreign
'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 2.1.0+dfsg-4+rm.
> unarchive 692582
Bug #692582 {Done: Debian FTP Masters } 
[projectm-jack] projectm-jack: It would be very nice if the man page listed the 
keyboard commands for projectM.
Unarchived Bug 692582
> reopen 692582
Bug #692582 {Done: Debian FTP Masters } 
[projectm-jack] projectm-jack: It would be very nice if the man page listed the 
keyboard commands for projectM.
'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 2.1.0+dfsg-4+rm.
> unarchive 909977
Bug #909977 {Done: Debian FTP Masters } 
[src:projectm] projectm: upstream has moved
Unarchived Bug 909977
> reopen 909977
Bug #909977 {Done: Debian FTP Masters } 
[src:projectm] projectm: upstream has moved
'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 2.1.0+dfsg-4+rm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
621789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621789
692582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692582
699383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699383
833489: 

Bug#963721: [pkg-cryptsetup-devel] Bug#963721: libcryptsetup12 v2:2.3.3-1 seems to be breaking libssl somehow

[Guilhem Moulin]

On Fri, 26 Jun 2020 at 20:39:32 -0400, Christian Weeks wrote:
> After some more googling, it seems that the REAL culprit might be
> libmount1.

Should this be reassigned to util-linux/2.35.2-5 then?
 
> This seems like a really messy tangled web of nastiness. Good luck
> figuring it out.

Unless there is a reproducer involving a targeted libcryptsetup12
upgrade I don't think this belong here :-P  Aside from documentation
files, the only thing libcryptsetup12 (2:2.1.0-5+deb10u2 and 2:2.3.3-1)
ships is libcryptsetup.so.12*.  It doesn't touch libssl.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#963721: [pkg-cryptsetup-devel] Bug#963721: libcryptsetup12 v2:2.3.3-1 seems to be breaking libssl somehow

[Guilhem Moulin]

On Fri, 26 Jun 2020 at 11:40:31 -0400, Christian Weeks wrote:
> Attached is the output of the various console commands, as well
> as the backtrace from the broken launcher with the new lib.

Thanks, however I fail to see how libcryptsetup12 is involved.  (Also I
think we can rule out i386 since the crash happens with x86_64.)  Is
that the entire reproducer?

  - launcher works with libcryptsetup12:amd64 2:2.1.0-5+deb10u2
  - `apt upgrade libcryptsetup12:amd64` (from 2:2.1.0-5+deb10u2
to 2:2.3.3-1, and *only* this package)
  - launcher no longer works

Do you confirm that the backtrace you shared previously was part of this
reproducer, and not something saved from a previous environment?  I see
no mention of libcryptsetup there, so I don't see how it comes to the
picture.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#961850: marked as done (dpkg: autopkgtest needs update for new version of make-dfsg: fails on warning)

[Debian Bug Tracking System]

Your message dated Sat, 27 Jun 2020 01:33:33 +
with message-id 
and subject line Bug#961850: fixed in dpkg 1.20.1
has caused the Debian Bug report #961850,
regarding dpkg: autopkgtest needs update for new version of make-dfsg: fails on 
warning
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.)


-- 
961850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dpkg
Version: 1.19.7
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, make-d...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:make-dfsg

Dear maintainer(s),

With a recent upload of make-dfsg the autopkgtest of dpkg fails in
testing when that autopkgtest is run with the binary packages of
make-dfsg from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
make-dfsg  from testing4.3-1
dpkg   from testing1.19.7
all others from testingfrom testing

I copied some of the output at the bottom of this report. Please fix the
warning, silence the warning or add the allow-stderr restriction.

Currently this regression is blocking the migration of make-dfsg to
testing [1].

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=make-dfsg

https://ci.debian.net/data/autopkgtest/testing/amd64/d/dpkg/5687475/log.gz

make[1]: Entering directory
'/tmp/autopkgtest-lxc.fw9ber8f/downtmp/build.IVc/src/test-root/man'
Makefile:894: warning: ignoring prerequisites on suffix rule definition
Makefile:896: warning: ignoring prerequisites on suffix rule definition
Makefile:898: warning: ignoring prerequisites on suffix rule definition
Makefile:900: warning: ignoring prerequisites on suffix rule definition
make[1]: Nothing to be done for 'installcheck'.
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.fw9ber8f/downtmp/build.IVc/src/test-root/man'
make[1]: Entering directory
'/tmp/autopkgtest-lxc.fw9ber8f/downtmp/build.IVc/src/test-root'
make[1]: Nothing to be done for 'installcheck-am'.
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.fw9ber8f/downtmp/build.IVc/src/test-root'
autopkgtest [18:08:09]: test test-root: ---]
autopkgtest [18:08:09]: test test-root:  - - - - - - - - - - results - -
- - - - - - - -
test-rootFAIL stderr: Makefile:894: warning: ignoring
prerequisites on suffix rule definition
autopkgtest [18:08:09]: test test-root:  - - - - - - - - - - stderr - -
- - - - - - - -
Makefile:894: warning: ignoring prerequisites on suffix rule definition
Makefile:896: warning: ignoring prerequisites on suffix rule definition
Makefile:898: warning: ignoring prerequisites on suffix rule definition
Makefile:900: warning: ignoring prerequisites on suffix rule definition



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: dpkg
Source-Version: 1.20.1
Done: Guillem Jover 

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated dpkg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 27 Jun 2020 02:41:48 +0200
Source: dpkg
Architecture: source
Version: 1.20.1
Distribution: unstable
Urgency: medium
Maintainer: Dpkg Developers 
Changed-By: Guillem Jover 
Closes: 832176 871808 953684 955028 955030 956055 956321 958229 958437 961850
Changes:
 dpkg (1.20.1) unstable; urgency=medium
 .
   [ Guillem Jover ]
   * Fix dpkg logging regression introduced in 1.20.0:
 - libdpkg: Use varbuf member .used instead of .size in log_message(),
   to avoid printing garbage.
 - libdpkg: Open the log file as write-only instead of read-only.
 Thanks to Roderich Schupp . Closes: #953684
   * Unify and cleanup Makefile fragment files 

Bug#963721: [pkg-cryptsetup-devel] Bug#963721: libcryptsetup12 v2:2.3.3-1 seems to be breaking libssl somehow

[Christian Weeks]

Update. I just discovered steam is still broken. After some more googling,
it seems that the REAL culprit might be libmount1.

Specifically, it seems that libmount1 v2.35.2-5 (bug #951048) has started
building with libcryptsetup-dev, but that is causing weird SSL leakages
everywhere, crashing unrelated software (minecraft launcher, steam, other
stuff using SSL).

I have upgraded libcryptsetup12 and downgraded libmount1 to 2.35.2-4
and it has resolved the problem as well.

This seems like a really messy tangled web of nastiness. Good luck figuring it
out.

I'm going to speculate that the guys at Mandriva found a similar problem:
https://github.com/ValveSoftware/steam-for-linux/issues/6861

Perhaps they might have a solution too?

Thanks

On Fri, 2020-06-26 at 11:40 -0400, Christian Weeks wrote:
> Attached is the output of the various console commands, as well
> as the backtrace from the broken launcher with the new lib.
> 
> Note that I am installing both amd64 and i386 versions. I do not
> have cryptsetup even installed on this machine, I think this lib
> is coming in from a dependency in gnome disks.
> 
> There is one key difference: in the older version, there is an
> explicit libssl in the linker, but in the new version, there 
> is not, even though it is somehow still being loaded.
> 
> Perhaps another lib is pulling a differing version somehow, and
> this lib is stamping on it?
> 
> Thanks!
> 
> On Fri, 2020-06-26 at 17:23 +0200, Guilhem Moulin wrote:
> > Control: tag -1 moreinfo
> > 
> > Hi Christian,
> > 
> > On Thu, 25 Jun 2020 at 21:58:43 -0400, Christian Weeks wrote:
> > > I installed the newest version of libcryptsetup12.
> > 
> > Unfortunately you appeared to file this bug using Buster's
> > libcryptsetup12 so the metada doesn't describe the buggy environment
> > (Version: 2:2.1.0-5+deb10u2).  Please show the output of `apt upgrade
> > libcryptsetup12` that yields the buggy environment.  (I.e., you don't
> > encounter the bug before the command but do after the upgrade.)  The
> > output of
> > 
> > ldd /lib/*-linux-gnu/libcryptsetup.so.12.6.0 /sbin/cryptsetup
> > 
> > and
> > 
> > dpkg-query -l "*cryptsetup*"
> > 
> > before *and* after the upgrade might be helpful too.
> > 
> > > Suddenly, minecraft would not run! 
> > > Backtraces in gdb indicate that something is broken in SSL.
> > 
> > Care to share said backtrace also?
> > 
> > cheers

Bug#963755: Fix that worked for me

[Ambroise Grau]

Hi, 

I realised the problem could come from the graphical interface loaded by Gnome, 
since Debian was able to start in recovery mode. For a strange reason I could 
not
configure my ethernet connection properly in that mode and had therefore not 
the possibility to download install drivers using apt (sideloading it was 
working but
the drivers I needed where too complicated to get that way).

In order to install all the firmware for my graphic card (nvidia GTX 1650) I 
entered
the rescue mode and followed all the steps of the setup leading to the selection
of the partition of the root file system to repair. Taking advantage of the 
hardware 
detection and settings run by the installer to have a working ethernet 
connection, 
I launched a shell in the target debian root file system and I was then able to 
set 
`apt` to get the firmware needed and install them. I was then able to reboot 
into
Debian with the full Gnome desktop environment.

Regarding Grub that noticed the Windows partition at installation, but did not 
write
it on the boot table, a simple `update-grub` from the recovery mode fixed it, 
and I
did not have to configure the menu.lst file as suggested in the FaQ 
(https://wiki.debian.org/DebianInstaller/FAQ#Q:_What_do_I_do_if_I_can_no_longer_boot_Windows_after_installing_Debian.3F
 

 ).

This therefore raises two questions from my part:
1/ Is Grub not updated after writing the new boot loader to the MBR?
2/ Would it be possible at the final step of the installation, just before the 
reboot,
to allow the use of a shell running in the newly created debian file system in 
order to install additional firmware that could not be loaded in another way 
and 
that are needed for some DE for example? 
(In my questions I am referring to the graphical installer in standard mode, as
I don’t feel confident enough to use the expert mode, and thus don’t know if 
this
is already accessible in that mode).


Apart from this, many thanks it worked great!

Ambroise

Bug#959655: drbd-doc: diff for NMU version 8.4~20151102-1.1

[Sudip Mukherjee]

Control: tags 959655 + patch
Control: tags 959655 + pending


Dear maintainer,

I've prepared an NMU for drbd-doc (versioned as 8.4~20151102-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

--
Regards
Sudip

diff -Nru drbd-doc-8.4~20151102/debian/changelog 
drbd-doc-8.4~20151102/debian/changelog
--- drbd-doc-8.4~20151102/debian/changelog  2016-03-15 18:03:58.0 
+
+++ drbd-doc-8.4~20151102/debian/changelog  2020-06-26 23:21:19.0 
+0100
@@ -1,3 +1,10 @@
+drbd-doc (8.4~20151102-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS. (Closes: #959655)
+
+ -- Sudip Mukherjee   Fri, 26 Jun 2020 23:21:19 
+0100
+
 drbd-doc (8.4~20151102-1) unstable; urgency=medium
 
   * Import upstream changes up to commit 0d6393f.
diff -Nru drbd-doc-8.4~20151102/debian/patches/fix_inkscape.patch 
drbd-doc-8.4~20151102/debian/patches/fix_inkscape.patch
--- drbd-doc-8.4~20151102/debian/patches/fix_inkscape.patch 1970-01-01 
01:00:00.0 +0100
+++ drbd-doc-8.4~20151102/debian/patches/fix_inkscape.patch 2020-06-26 
23:15:09.0 +0100
@@ -0,0 +1,45 @@
+Description: Fix arguments to inkscape
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/959655
+
+---
+
+--- drbd-doc-8.4~20151102.orig/makedoc/Makefile.am
 drbd-doc-8.4~20151102/makedoc/Makefile.am
+@@ -341,7 +341,7 @@ endif
+ # Generated images: Encapsulated PostScript from SVG
+ if USE_INKSCAPE
+ %.eps: %.svg
+-  $(INKSCAPE) --file=$< --export-area-drawing --export-eps=$@
++  $(INKSCAPE) --export-area-drawing --export-type=eps 
--export-filename=$@ $<
+ endif
+ 
+ # Generated images: PNG from SVG
+@@ -349,7 +349,7 @@ endif
+ if RENDER_SVG
+ %.png: %.svg
+ if USE_INKSCAPE
+-  $(INKSCAPE) --file=$< --export-dpi=90 --export-area-drawing 
--export-png=$@
++  $(INKSCAPE) --export-dpi=90 --export-area-drawing --export-type=png 
--export-filename=$@ $<
+ endif
+ if USE_RSVG
+   $(RSVG) --dpi-x=90 --dpi-y=90 --format=png $< $@
+@@ -358,7 +358,7 @@ endif
+ # Half-size SVG (from PNG)
+ %-small.png: %.svg
+ if USE_INKSCAPE
+-  $(INKSCAPE) --file=$< --export-dpi=45 --export-area-drawing 
--export-png=$@
++  $(INKSCAPE) --export-dpi=45 --export-area-drawing --export-type=png 
--export-filename=$@ $<
+ endif
+ if USE_RSVG
+   $(RSVG) --dpi-x=45 --dpi-y=45 --format=png $< $@
+@@ -367,7 +367,7 @@ endif
+ # Double-size SVG (from PNG)
+ %-large.png: %.svg
+ if USE_INKSCAPE
+-  $(INKSCAPE) --file=$< --export-dpi=180 --export-area-drawing 
--export-png=$@
++  $(INKSCAPE) --export-dpi=180 --export-area-drawing --export-type=png 
--export-filename=$@ $<
+ endif
+ if USE_RSVG
+   $(RSVG) --dpi-x=180 --dpi-y=180 --format=png $< $@
diff -Nru drbd-doc-8.4~20151102/debian/patches/series 
drbd-doc-8.4~20151102/debian/patches/series
--- drbd-doc-8.4~20151102/debian/patches/series 2016-03-15 17:51:28.0 
+
+++ drbd-doc-8.4~20151102/debian/patches/series 2020-06-26 23:14:08.0 
+0100
@@ -1,3 +1,4 @@
 drop-manpages.patch
 css-enhancements.patch
 mention-drbd.conf.5.patch
+fix_inkscape.patch

Processed: drbd-doc: diff for NMU version 8.4~20151102-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 959655 + patch
Bug #959655 [src:drbd-doc] drbd-doc: FTBFS: (process:30778): WARNING **: 
04:52:54.254: Unable to create profile directory (Permission denied) (13)
Added tag(s) patch.
> tags 959655 + pending
Bug #959655 [src:drbd-doc] drbd-doc: FTBFS: (process:30778): WARNING **: 
04:52:54.254: Unable to create profile directory (Permission denied) (13)
Added tag(s) pending.

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

Bug#963782: gpgme1.0: autopkgtest failure due to bash wrong syntax

[Gianfranco Costamagna]

Source: gpgme1.0
Version: 1.13.1-8
Severity: serious
Tags: patch

Hello, please accept this patch to fix a bad syntax.
(two main issues, missing


Processing triggers for libc-bin (2.31-0ubuntu10) ...
(Reading database ... 78068 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [15:17:55]: test checky2106: [---
unsigned long on this platform is 4 octets.
This means that GPGME will fail when encountering expiration
dates after 2106-02-07 06:28:16Z.

Please see https://dev.gnupg.org/T4766 and https://dev.gnupg.org/T4826
for more details.
/tmp/autopkgtest.FpdOQK/build.XhH/src/debian/tests/checky2106: line 25: [: 
missing `]'
autopkgtest [15:17:57]: test checky2106: ---]
autopkgtest [15:18:00]: test checky2106:  - - - - - - - - - - results - - - - - 
- - - - -
checky2106   FAIL non-zero exit status 1
autopkgtest [15:18:00]: test checky2106:  - - - - - - - - - - stderr - - - - - 
- - - - -
/tmp/autopkgtest.FpdOQK/build.XhH/src/debian/tests/checky2106: line 25: [: 
missing `]'
autopkgtest [15:18:02]:  summary
python3  PASS
checky2106   FAIL non-zero exit status 1



diff -Nru gpgme1.0-1.13.1/debian/changelog gpgme1.0-1.13.1/debian/changelog
--- gpgme1.0-1.13.1/debian/changelog2020-06-26 10:16:00.0 +0200
+++ gpgme1.0-1.13.1/debian/changelog2020-06-26 23:44:40.0 +0200
@@ -1,3 +1,9 @@
+gpgme1.0 (1.13.1-8ubuntu2) groovy; urgency=medium
+
+  * Fix test sadness on 32bit systems due to bad bash syntax.
+
+ -- Gianfranco Costamagna   Fri, 26 Jun 2020 
23:44:40 +0200
+
 gpgme1.0 (1.13.1-8ubuntu1) groovy; urgency=low
 
   * Merge from Debian unstable.  Remaining changes:
diff -Nru gpgme1.0-1.13.1/debian/tests/checky2106 
gpgme1.0-1.13.1/debian/tests/checky2106
--- gpgme1.0-1.13.1/debian/tests/checky2106 2020-06-26 10:15:43.0 
+0200
+++ gpgme1.0-1.13.1/debian/tests/checky2106 2020-06-26 23:44:17.0 
+0200
@@ -22,8 +22,8 @@
 Please see https://dev.gnupg.org/T4766 and https://dev.gnupg.org/T4826
 for more details.
 " "$sz" "$limit"
-if [ "$(dpkg-architecture -qDEB_HOST_ARCH_BITS)" == 32 &&
- $(date +%s) -lt $(TZ=UTC date +%s 2031-02-07) ]; then
+if [ "$(dpkg-architecture -qDEB_HOST_ARCH_BITS)" == 32 ] &&
+[ $(date +%s) -lt $(TZ=UTC date +%s --date='2031-02-07') ]; then
 printf "We permit skipping this test during autopkgtest until 75 years
 before the cutoff.
 

thanks!

Gianfranco

Bug#963713: net-snmp: CVE-2019-20892

[Andreas Hasenack]

I believe it was introduced in 5.8. The previous version we had was 5.7.3
and we didn't reproduce it there.

On Fri, Jun 26, 2020 at 6:18 PM Salvatore Bonaccorso 
wrote:

> Hi Andreas,
>
> On Thu, Jun 25, 2020 at 06:31:13PM -0300, Andreas Hasenack wrote:
> > Hi,
> >
> > we are not happy yet with those commits because they change a struct
> > without bumping the soname. We are investigating how impactful that is.
>
> Ack thanks for this heads-up.
>
> Do you have any indication where the issue was actually introduced?
> The oss-security post is slight confising in this regard. I can
> reproduce the issue with the given version 5.8+dfsg-2. But not in
> buster.
>
> Regards,
> Salvatore
>

Bug#963713: net-snmp: CVE-2019-20892

[Salvatore Bonaccorso]

Hi Andreas,

On Thu, Jun 25, 2020 at 06:31:13PM -0300, Andreas Hasenack wrote:
> Hi,
> 
> we are not happy yet with those commits because they change a struct
> without bumping the soname. We are investigating how impactful that is.

Ack thanks for this heads-up.

Do you have any indication where the issue was actually introduced?
The oss-security post is slight confising in this regard. I can
reproduce the issue with the given version 5.8+dfsg-2. But not in
buster.

Regards,
Salvatore

Processed: tagging 963493

[Debian Bug Tracking System]

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

> tags 963493 + confirmed pending
Bug #963493 [src:linux] Repeatable hard lockup running strace testsuite using 
4.19.118+2+deb10u1, 4.19.98+1+deb10u1 works fine
Added tag(s) confirmed and pending.
> thanks
Stopping processing here.

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

Bug#963493: Repeatable hard lockup running strace testsuite on 4.19.98+ onwards

[Sasha Levin]

On Fri, Jun 26, 2020 at 08:01:18PM +0100, Steve McIntyre wrote:

On Fri, Jun 26, 2020 at 10:29:28AM -0700, John Johansen wrote:

On 6/26/20 9:50 AM, Steve McIntyre wrote:


OK, will try that second...



I have not been able to reproduce but

So looking at linux-4.19.y it looks like
1f8266ff5884 apparmor: don't try to replace stale label in ptrace access check

was picked without
ca3fde5214e1 apparmor: don't try to replace stale label in ptraceme check

Both of them are marked as
Fixes: b2d09ae449ced ("apparmor: move ptrace checks to using labels")

so I would expect them to be picked together.

ptraceme is potentially updating the task's cred while the access check is
running.

Try building after picking
ca3fde5214e1 apparmor: don't try to replace stale label in ptraceme check


Bingo! With that one change the test suite runs to completion, no lockup.


I've queued ca3fde5214e1 for 4.19 and 4.14, thank you for your work!

--
Thanks,
Sasha

Processed: condor: CVE-2019-18823

[Debian Bug Tracking System]

Processing control commands:

> found -1 8.4.11~dfsg.1-1
Bug #963777 [src:condor] condor: CVE-2019-18823
Marked as found in versions condor/8.4.11~dfsg.1-1.

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

Bug#963777: condor: CVE-2019-18823

[Salvatore Bonaccorso]

Source: condor
Version: 8.6.8~dfsg.1-2
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 8.4.11~dfsg.1-1

Hi,

The following vulnerability was published for condor.

CVE-2019-18823[0]:
| HTCondor up to and including stable series 8.8.6 and development
| series 8.9.4 has Incorrect Access Control. It is possible to use a
| different authentication method to submit a job than the administrator
| has specified. If the administrator has configured the READ or WRITE
| methods to include CLAIMTOBE, then it is possible to impersonate
| another user to the condor_schedd. (For example to submit or remove
| jobs)


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-18823
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18823

Regards,
Salvatore

Bug#963493: Repeatable hard lockup running strace testsuite on 4.19.98+ onwards

[Steve McIntyre]

On Fri, Jun 26, 2020 at 10:29:28AM -0700, John Johansen wrote:
>On 6/26/20 9:50 AM, Steve McIntyre wrote:
>> 
>> OK, will try that second...
>> 
>
>I have not been able to reproduce but
>
>So looking at linux-4.19.y it looks like
>1f8266ff5884 apparmor: don't try to replace stale label in ptrace access check
>
>was picked without
>ca3fde5214e1 apparmor: don't try to replace stale label in ptraceme check
>
>Both of them are marked as
>Fixes: b2d09ae449ced ("apparmor: move ptrace checks to using labels")
>
>so I would expect them to be picked together.
>
>ptraceme is potentially updating the task's cred while the access check is
>running.
>
>Try building after picking
>ca3fde5214e1 apparmor: don't try to replace stale label in ptraceme check

Bingo! With that one change the test suite runs to completion, no lockup.

\o/

Thanks guys, I think we've found the cause here.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"The whole problem with the world is that fools and fanatics are
 always so certain of themselves, and wiser people so full of doubts."
   -- Bertrand Russell

Bug#963774: mcl breaks roary autopkgtest: Cannot find the mcxdeblast executable, please ensure its in your PATH

[Paul Gevers]

Source: mcl, roary
Control: found -1 mcl/1:14-137+ds-7
Control: found -1 roary/3.13.0+dfsg-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of mcl the autopkgtest of roary fails in testing
when that autopkgtest is run with the binary packages of mcl from
unstable. It passes when run with only packages from testing. In tabular
form:

   passfail
mclfrom testing1:14-137+ds-7
roary  from testing3.13.0+dfsg-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of mcl to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=mcl

https://ci.debian.net/data/autopkgtest/testing/amd64/r/roary/6058047/log.gz

autopkgtest [18:20:38]: test test-installed: [---
Use of uninitialized value in require at
/usr/share/perl5/HTTP/Headers.pm line 302.
Use of uninitialized value in require at
/usr/lib/x86_64-linux-gnu/perl/5.30/Encode.pm line 70.

Please cite Roary if you use any of the results it produces:
Andrew J. Page, Carla A. Cummins, Martin Hunt, Vanessa K. Wong,
Sandra Reuter, Matthew T. G. Holden, Maria Fookes, Daniel Falush,
Jacqueline A. Keane, Julian Parkhill,
"Roary: Rapid large-scale prokaryote pan genome analysis",
Bioinformatics, 2015 Nov 15;31(22):3691-3693
doi: http://doi.org/10.1093/bioinformatics/btv421
Pubmed: 26198102

2020/06/25 18:20:41 Cannot find the mcxdeblast executable, please ensure
its in your PATH
2,6c2,6
< out/_blast_results
< out/_clustered
< out/_clustered.clstr
< out/_combined_files
< out/_combined_files.groups
---
> out/accessory.header.embl
> out/accessory.tab
> out/accessory_binary_genes.fa
> out/accessory_binary_genes.fa.newick
> out/accessory_graph.dot
7a8,18
> out/clustered_proteins
> out/core_accessory.header.embl
> out/core_accessory.tab
> out/core_accessory_graph.dot
> out/gene_presence_absence.Rtab
> out/gene_presence_absence.csv
> out/number_of_conserved_genes.Rtab
> out/number_of_genes_in_pan_genome.Rtab
> out/number_of_new_genes.Rtab
> out/number_of_unique_genes.Rtab
> out/summary_statistics.txt
autopkgtest [18:20:41]: test test-installed: ---]



signature.asc
Description: OpenPGP digital signature

Bug#963296: marked as done (orocos-kdl: FTBFS: sipPyKDLpart1.cpp:2124:119: error: use of deleted function ‘KDL::ChainJntToJacSolver& KDL::ChainJntToJacSolver::operator=(const KDL::ChainJntToJacSolver

[Debian Bug Tracking System]

Your message dated Fri, 26 Jun 2020 18:49:06 +
with message-id 
and subject line Bug#963296: fixed in orocos-kdl 1.4.0-10
has caused the Debian Bug report #963296,
regarding orocos-kdl: FTBFS: sipPyKDLpart1.cpp:2124:119: error: use of deleted 
function ‘KDL::ChainJntToJacSolver& KDL::ChainJntToJacSolver::operator=(const 
KDL::ChainJntToJacSolver&)’
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.)


-- 
963296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: orocos-kdl
Version: 1.4.0-9
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> cd /<>/.pybuild/cpython3_3.8/build/python_orocos_kdl && 
> /usr/bin/c++  -Dpython_module_PyKDL_EXPORTS 
> -I/<>/.pybuild/cpython3_3.8/build/python_orocos_kdl/../orocos_kdl/src
>  -I/<>/.pybuild/cpython3_3.8/build/orocos_kdl/../../../include 
> -I/usr/include/eigen3 -I/usr/include/python3.8  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC   -o 
> CMakeFiles/python_module_PyKDL.dir/PyKDL/sipPyKDLpart3.o -c 
> /<>/.pybuild/cpython3_3.8/build/python_orocos_kdl/PyKDL/sipPyKDLpart3.cpp
> /<>/.pybuild/cpython3_3.8/build/python_orocos_kdl/PyKDL/sipPyKDLpart1.cpp:
>  In function ‘void assign_ChainJntToJacSolver(void*, Py_ssize_t, void*)’:
> /<>/.pybuild/cpython3_3.8/build/python_orocos_kdl/PyKDL/sipPyKDLpart1.cpp:2124:119:
>  error: use of deleted function ‘KDL::ChainJntToJacSolver& 
> KDL::ChainJntToJacSolver::operator=(const KDL::ChainJntToJacSolver&)’
>  2124 | };
>   |   
> ^
> In file included from /<>/python_orocos_kdl/PyKDL/kinfam.sip:567:
> /<>/.pybuild/cpython3_3.8/build/python_orocos_kdl/../orocos_kdl/src/kdl/chainjnttojacsolver.hpp:41:11:
>  note: ‘KDL::ChainJntToJacSolver& KDL::ChainJntToJacSolver::operator=(const 
> KDL::ChainJntToJacSolver&)’ is implicitly deleted because the default 
> definition would be ill-formed:
>41 | class ChainJntToJacSolver : public SolverI
>   |   ^~~
> /<>/.pybuild/cpython3_3.8/build/python_orocos_kdl/../orocos_kdl/src/kdl/chainjnttojacsolver.hpp:41:11:
>  error: non-static reference member ‘const KDL::Chain& 
> KDL::ChainJntToJacSolver::chain’, can’t use default assignment operator
> /<>/.pybuild/cpython3_3.8/build/python_orocos_kdl/PyKDL/sipPyKDLpart3.cpp:
>  In function ‘void assign_ChainIkSolverPos_NR(void*, Py_ssize_t, void*)’:
> /<>/.pybuild/cpython3_3.8/build/python_orocos_kdl/PyKDL/sipPyKDLpart3.cpp:204:119:
>  error: use of deleted function ‘KDL::ChainIkSolverPos_NR& 
> KDL::ChainIkSolverPos_NR::operator=(const KDL::ChainIkSolverPos_NR&)’
>   204 | reinterpret_cast< ::ChainIkSolverPos_NR *>(sipDst)[sipDstIdx] = 
> *reinterpret_cast< ::ChainIkSolverPos_NR *>(sipSrc);
>   |   
> ^
> In file included from /<>/python_orocos_kdl/PyKDL/kinfam.sip:386:
> /<>/.pybuild/cpython3_3.8/build/python_orocos_kdl/../orocos_kdl/src/kdl/chainiksolverpos_nr.hpp:38:11:
>  note: ‘KDL::ChainIkSolverPos_NR& KDL::ChainIkSolverPos_NR::operator=(const 
> KDL::ChainIkSolverPos_NR&)’ is implicitly deleted because the default 
> definition would be ill-formed:
>38 | class ChainIkSolverPos_NR : public ChainIkSolverPos
>   |   ^~~
> /<>/.pybuild/cpython3_3.8/build/python_orocos_kdl/../orocos_kdl/src/kdl/chainiksolverpos_nr.hpp:38:11:
>  error: non-static reference member ‘const KDL::Chain& 
> KDL::ChainIkSolverPos_NR::chain’, can’t use default assignment operator
> /<>/.pybuild/cpython3_3.8/build/python_orocos_kdl/../orocos_kdl/src/kdl/chainiksolverpos_nr.hpp:38:11:
>  error: non-static reference member ‘KDL::ChainIkSolverVel& 
> KDL::ChainIkSolverPos_NR::iksolver’, can’t use default assignment operator
> /<>/.pybuild/cpython3_3.8/build/python_orocos_kdl/../orocos_kdl/src/kdl/chainiksolverpos_nr.hpp:38:11:
>  error: non-static reference member ‘KDL::ChainFkSolverPos& 
> KDL::ChainIkSolverPos_NR::fksolver’, can’t use default assignment operator
> /<>/.pybuild/cpython3_3.8/build/python_orocos_kdl/PyKDL/sipPyKDLpart3.cpp:
>  In function ‘void assign_ChainFkSolverVel_recursive(void*, Py_ssize_t, 
> void*)’:
> 

Processed: mcl breaks roary autopkgtest: Cannot find the mcxdeblast executable, please ensure its in your PATH

[Debian Bug Tracking System]

Processing control commands:

> found -1 mcl/1:14-137+ds-7
Bug #963774 [src:mcl, src:roary] mcl breaks roary autopkgtest: Cannot find the 
mcxdeblast executable, please ensure its in your PATH
Marked as found in versions mcl/1:14-137+ds-7.
> found -1 roary/3.13.0+dfsg-1
Bug #963774 [src:mcl, src:roary] mcl breaks roary autopkgtest: Cannot find the 
mcxdeblast executable, please ensure its in your PATH
Marked as found in versions roary/3.13.0+dfsg-1.

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

Processed: nodejs breaks node-leveldown autopkgtest: Test: require Aborted

[Debian Bug Tracking System]

Processing control commands:

> found -1 nodejs/12.18.0~dfsg-3
Bug #963772 [src:nodejs, src:node-leveldown] nodejs breaks node-leveldown 
autopkgtest: Test: require Aborted
Marked as found in versions nodejs/12.18.0~dfsg-3.
> found -1 node-leveldown/5.4.1+dfsg-2
Bug #963772 [src:nodejs, src:node-leveldown] nodejs breaks node-leveldown 
autopkgtest: Test: require Aborted
Marked as found in versions node-leveldown/5.4.1+dfsg-2.

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

Bug#963772: nodejs breaks node-leveldown autopkgtest: Test: require Aborted

[Paul Gevers]

Source: nodejs, node-leveldown
Control: found -1 nodejs/12.18.0~dfsg-3
Control: found -1 node-leveldown/5.4.1+dfsg-2
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of nodejs the autopkgtest of node-leveldown fails
in testing when that autopkgtest is run with the binary packages of
nodejs from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
nodejs from testing12.18.0~dfsg-3
node-leveldown from testing5.4.1+dfsg-2
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of nodejs to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=nodejs

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-leveldown/6049319/log.gz

autopkgtest [21:35:55]: test pkg-js-autopkgtest-require:
[---
Using package.json
Node module name is leveldown
Test: require
Aborted
autopkgtest [21:35:55]: test pkg-js-autopkgtest-require:
---]



signature.asc
Description: OpenPGP digital signature

Processed: nodejs breaks node-immutable-tuple autopkgtest: can handle a lot of strings: AssertionError

[Debian Bug Tracking System]

Processing control commands:

> found -1 nodejs/12.18.0~dfsg-3
Bug #963771 [src:nodejs, src:node-immutable-tuple] nodejs breaks 
node-immutable-tuple autopkgtest: can handle a lot of strings: AssertionError
Marked as found in versions nodejs/12.18.0~dfsg-3.
> found -1 node-immutable-tuple/0.4.10-7
Bug #963771 [src:nodejs, src:node-immutable-tuple] nodejs breaks 
node-immutable-tuple autopkgtest: can handle a lot of strings: AssertionError
Marked as found in versions node-immutable-tuple/0.4.10-7.

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

Bug#963709: pyside2: FTBFS with Qt 5.14: 'PySide2.QtCore.QDate' called with wrong argument types: PySide2.QtCore.QDate(date)

[Dmitry Shachnev]

On Fri, Jun 26, 2020 at 03:27:58PM +0300, Dmitry Shachnev wrote:
> I tried to debug it, and found out that for some reason
> __glXLookupVendorByName("mesa") fails, so __glXLookupVendorByScreen
> falls back to FALLBACK_VENDOR_NAME (= "indirect") which does not work
> properly. No time to debug further...
>
> This issue happens with PySide and PyQt programs, but not with C++.
> Maybe it's the same issue as #960073.

Some more information on this: it looks like dlopen'ing libGLX_mesa.so.0
returns NULL (src/GLX/libglxmapping.c:430).

LD_PRELOAD'ing that library helps. Adding the following two lines to top
of web_engine_initialize.py also helps:

import ctypes
ctypes.CDLL('libGLX_mesa.so.0', ctypes.RTLD_GLOBAL)

I can't say why dlopen fails without that, though.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#963771: nodejs breaks node-immutable-tuple autopkgtest: can handle a lot of strings: AssertionError

[Paul Gevers]

Source: nodejs, node-immutable-tuple
Control: found -1 nodejs/12.18.0~dfsg-3
Control: found -1 node-immutable-tuple/0.4.10-7
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of nodejs the autopkgtest of node-immutable-tuple
fails in testing when that autopkgtest is run with the binary packages
of nodejs from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
nodejs from testing12.18.0~dfsg-3
node-immutable-tuple   from testing0.4.10-7
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of nodejs to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=nodejs

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-immutable-tuple/6049318/log.gz

  1) performance
   can handle a lot of strings:
 AssertionError [ERR_ASSERTION]: Expected values to be loosely
deep-equal:

tuple {
  '0': 'ftchujom2yv',
  '1': 'vfs12z46td',
  '2': 'vnjsdgd5oie',
  '3': 'p975if8h16t',
  '4': 'us43v9frwga',
  '5': '4u158uqgnu3',
  '6': 'uxs8h8druu',
  '7': '0d6egk7shh76',
  '8': '8sbvrilamav',
  '9': 'db4jmngu56t'
}

should loosely deep-equal

[
  'ftchujom2yv',
  'vfs12z46td',
  'vnjsdgd5oie',
  'p975if8h16t',
  'us43v9frwga',
  '4u158uqgnu3',
  'uxs8h8druu',
  '0d6egk7shh76',
  '8sbvrilamav',
  'db4jmngu56t'
]



signature.asc
Description: OpenPGP digital signature

Processed: nodejs breaks node-iconv-lite autopkgtest: malloc(): invalid next size (unsorted)

[Debian Bug Tracking System]

Processing control commands:

> found -1 nodejs/12.18.0~dfsg-3
Bug #963769 [src:nodejs, src:node-iconv-lite] nodejs breaks node-iconv-lite 
autopkgtest: malloc(): invalid next size (unsorted)
Marked as found in versions nodejs/12.18.0~dfsg-3.
> found -1 node-iconv-lite/0.5.1-1
Bug #963769 [src:nodejs, src:node-iconv-lite] nodejs breaks node-iconv-lite 
autopkgtest: malloc(): invalid next size (unsorted)
Marked as found in versions node-iconv-lite/0.5.1-1.

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

Bug#963769: nodejs breaks node-iconv-lite autopkgtest: malloc(): invalid next size (unsorted)

[Paul Gevers]

Source: nodejs, node-iconv-lite
Control: found -1 nodejs/12.18.0~dfsg-3
Control: found -1 node-iconv-lite/0.5.1-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of nodejs the autopkgtest of node-iconv-lite fails
in testing when that autopkgtest is run with the binary packages of
nodejs from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
nodejs from testing12.18.0~dfsg-3
node-iconv-litefrom testing0.5.1-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of nodejs to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=nodejs

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-iconv-lite/6049317/log.gz

autopkgtest [21:36:16]: test pkg-js-autopkgtest: [---
Using package.json
Node module name is iconv-lite
# Copy test files
Looking at /usr/lib/nodejs/iconv-lite
Looking at /usr/lib/*/nodejs/iconv-lite
Looking at /usr/share/nodejs/iconv-lite
Found /usr/share/nodejs/iconv-lite
Linking /usr/share/nodejs/iconv-lite/encodings
Linking /usr/share/nodejs/iconv-lite/generation
Linking /usr/share/nodejs/iconv-lite/lib
Linking /usr/share/nodejs/iconv-lite/node_modules
Linking /usr/share/nodejs/iconv-lite/package.json
Launch debian/tests/pkg-js/test with sh -ex
+ mocha --bail --reporter spec --grep .
malloc(): invalid next size (unsorted)
Aborted
autopkgtest [21:36:17]: test pkg-js-autopkgtest: ---]




signature.asc
Description: OpenPGP digital signature

Bug#963489: dgit mirror ssh wrapper breaks due to rsync update

[Samuel Henrique]

Hello Sean,

> Do you want me to REJECT it from NEW?

Yes, please.

I sent an email to ftpmaster.d.o asking for that on the 21st, the
title was "Removal of rsync package from the NEW queue".

Thanks,

--
Samuel Henrique 

Bug#963412: marked as done (libzt: FTBFS: dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include --mandir=\${prefix}/share/man --infodir=\${prefix

[Debian Bug Tracking System]

Your message dated Fri, 26 Jun 2020 20:23:43 +0200
with message-id <63c47b7b-7ccf-42cb-bd71-35e872245...@www.fastmail.com>
and subject line 
has caused the Debian Bug report #963412,
regarding libzt: FTBFS: dh_auto_configure: error: ./configure 
--build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include 
--mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --sysconfdir=/etc 
--localstatedir=/var --disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking returned exit code 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.)


-- 
963412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libzt
Version: 0.3-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> NOTE: Build tree is not configured, using curated compiler options.
> NOTE: Use ./configure to disable this mechanism
> rm -f *.o
> rm -f libzt.a
> rm -f libzt.so libzt.so.1
> rm -f man/libzt-test.1 man/libzt.3 man/zt_check.3 man/zt_claim.3 
> man/ZT_CMP_BOOL.3 man/ZT_CMP_INT.3 man/ZT_CMP_PTR.3 man/ZT_CMP_RUNE.3 
> man/ZT_CMP_UINT.3 man/ZT_CURRENT_LOCATION.3 man/ZT_FALSE.3 man/zt_location.3 
> man/zt_location_at.3 man/zt_main.3 man/ZT_NOT_NULL.3 man/ZT_NULL.3 
> man/zt_pack_boolean.3 man/zt_pack_integer.3 man/zt_pack_nothing.3 
> man/zt_pack_pointer.3 man/zt_pack_rune.3 man/zt_pack_string.3 
> man/zt_pack_unsigned.3 man/zt_test.3 man/zt_test_case_func.3 
> man/zt_test_suite_func.3 man/ZT_TRUE.3 man/zt_value.3 
> man/zt_visit_test_case.3 man/zt_visitor.3
> rm -f *.profdata *.profraw
> rm -f libzt-test
> rm -f *.i
> rm -f *.PVS-Studio.log
> rm -rf pvs-report
> rm -rf cov-int
> rm -f libzt-0.3-coverity.tar.gz
> rm -f GNUmakefile.configure.mk
> make[1]: Leaving directory '/<>'
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building libzt using existing ./libzt_0.3.orig.tar.gz
> dpkg-source: info: building libzt using existing ./libzt_0.3.orig.tar.gz.asc
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building libzt in libzt_0.3-2.debian.tar.xz
> dpkg-source: info: building libzt in libzt_0.3-2.dsc
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   ./configure --build=x86_64-linux-gnu --prefix=/usr 
> --includedir=\${prefix}/include --mandir=\${prefix}/share/man 
> --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
> --disable-option-checking --disable-silent-rules 
> --libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
> --disable-maintainer-mode --disable-dependency-tracking
> configure: unknown option --disable-option-checking
> dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr 
> --includedir=\${prefix}/include --mandir=\${prefix}/share/man 
> --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
> --disable-option-checking --disable-silent-rules 
> --libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
> --disable-maintainer-mode --disable-dependency-tracking returned exit code 1
> make: *** [debian/rules:4: binary] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/libzt_0.3-2_unstable.log

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

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

This bug is fixed as show here 
https://buildd.debian.org/status/package.php?p=libzt

This has also uncovered a genuine portability bug in the code, affecting 
big-endian architectures.--- End Message ---

Bug#959606: marked as done (sailcut: FTBFS: (process:28240): WARNING **: 04:35:52.116: Unable to create profile directory (Permission denied) (13))

[Debian Bug Tracking System]

Your message dated Fri, 26 Jun 2020 18:19:57 +
with message-id 
and subject line Bug#959606: fixed in sailcut 1.4.1-2.1
has caused the Debian Bug report #959606,
regarding sailcut: FTBFS: (process:28240): WARNING **: 04:35:52.116: Unable to 
create profile directory (Permission denied) (13)
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.)


-- 
959606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sailcut
Version: 1.4.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[4]: Entering directory '/<>/tests/geocpp'
> make[4]: Nothing to be done for 'install'.
> make[4]: Leaving directory '/<>/tests/geocpp'
> : /<>/debian/tmp/usr/bin/sailcut
> make[3]: Leaving directory '/<>/tests'
> /usr/lib/qt5/bin/qmake -install qinstall 
> /<>/share/doc/sailcut/html 
> /<>/debian/tmp/usr/share/doc/sailcut/html
> make[3]: Leaving directory '/<>/src'
> make[2]: Leaving directory '/<>'
> for i in 16 24 32 48 64 128 256; do \
>   mkdir -p debian/sailcut/usr/share/icons/hicolor/${i}x${i}/apps; \
>   inkscape -z 
> --export-png=debian/sailcut/usr/share/icons/hicolor/${i}x${i}/apps/sailcut.png
>  --export-width=$i --export-height=$i icons/sailcut.svg; \
> done
> 
> ** (process:28240): WARNING **: 04:35:52.116: Unable to create profile 
> directory (Permission denied) (13)
> Unable to init server: Could not connect: Connection refused
> Unknown option -z
> 
> ** (process:28246): WARNING **: 04:35:52.166: Unable to create profile 
> directory (Permission denied) (13)
> Unable to init server: Could not connect: Connection refused
> Unknown option -z
> 
> ** (process:28252): WARNING **: 04:35:52.215: Unable to create profile 
> directory (Permission denied) (13)
> Unable to init server: Could not connect: Connection refused
> Unknown option -z
> 
> ** (process:28258): WARNING **: 04:35:52.263: Unable to create profile 
> directory (Permission denied) (13)
> Unable to init server: Could not connect: Connection refused
> Unknown option -z
> 
> ** (process:28264): WARNING **: 04:35:52.310: Unable to create profile 
> directory (Permission denied) (13)
> Unable to init server: Could not connect: Connection refused
> Unknown option -z
> 
> ** (process:28270): WARNING **: 04:35:52.358: Unable to create profile 
> directory (Permission denied) (13)
> Unable to init server: Could not connect: Connection refused
> Unknown option -z
> 
> ** (process:28276): WARNING **: 04:35:52.405: Unable to create profile 
> directory (Permission denied) (13)
> Unable to init server: Could not connect: Connection refused
> Unknown option -z
> make[1]: *** [debian/rules:12: override_dh_auto_install] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/05/01/sailcut_1.4.1-2_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Sudip Mukherjee  (supplier of updated sailcut 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 19 Jun 2020 11:10:18 +0100
Source: sailcut
Architecture: source
Version: 1.4.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Jeremy Lainé 
Changed-By: Sudip Mukherjee 
Closes: 959606
Changes:
 sailcut (1.4.1-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update inkscape args to fix FTBFS. (Closes: #959606)
Checksums-Sha1:
 

Bug#963493: Repeatable hard lockup running strace testsuite on 4.19.98+ onwards

[Steve McIntyre]

Hi again,

On Fri, Jun 26, 2020 at 05:50:00PM +0100, Steve McIntyre wrote:
>On Fri, Jun 26, 2020 at 04:25:59PM +0200, Jann Horn wrote:
>>On Fri, Jun 26, 2020 at 3:41 PM Greg KH  wrote:
>>> On Fri, Jun 26, 2020 at 12:35:58PM +0100, Steve McIntyre wrote:
>
>...
>
>>> > Considering I'm running strace build tests to provoke this bug,
>>> > finding the failure in a commit talking about ptrace changes does look
>>> > very suspicious...!
>>> >
>>> > Annoyingly, I can't reproduce this on my disparate other machines
>>> > here, suggesting it's maybe(?) timing related.
>>
>>Does "hard lockup" mean that the HARDLOCKUP_DETECTOR infrastructure
>>prints a warning to dmesg? If so, can you share that warning?
>
>I mean the machine locks hard - X stops updating, the mouse/keyboard
>stop responding. No pings, etc. When I reboot, there's nothing in the
>logs.
>
>>If you don't have any way to see console output, and you don't have a
>>working serial console setup or such, you may want to try re-running
>>those tests while the kernel is booted with netconsole enabled to log
>>to a different machine over UDP (see
>>https://www.kernel.org/doc/Documentation/networking/netconsole.txt).
>
>ACK, will try that now for you.
>
>>You may want to try setting the sysctl kernel.sysrq=1 , then when the
>>system has locked up, press ALT+PRINT+L (to generate stack traces for
>>all active CPUs from NMI context), and maybe also ALT+PRINT+T and
>>ALT+PRINT+W (to collect more information about active tasks).
>
>Nod.
>
>>(If you share stack traces from these things with us, it would be
>>helpful if you could run them through scripts/decode_stacktrace.pl
>>from the kernel tree first, to add line number information.)
>
>ACK.

Output passed through scripts/decode_stacktrace.sh attached.

Just about to try John's suggestion next.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Dance like no one's watching. Encrypt like everyone is.
 - @torproject


tack.log.decoded.gz
Description: application/gzip

Bug#963493: Repeatable hard lockup running strace testsuite on 4.19.98+ onwards

[John Johansen]

On 6/26/20 9:50 AM, Steve McIntyre wrote:
> Hi Jann,
> 
> On Fri, Jun 26, 2020 at 04:25:59PM +0200, Jann Horn wrote:
>> On Fri, Jun 26, 2020 at 3:41 PM Greg KH  wrote:
>>> On Fri, Jun 26, 2020 at 12:35:58PM +0100, Steve McIntyre wrote:
> 
> ...
> 
 Considering I'm running strace build tests to provoke this bug,
 finding the failure in a commit talking about ptrace changes does look
 very suspicious...!

 Annoyingly, I can't reproduce this on my disparate other machines
 here, suggesting it's maybe(?) timing related.
>>
>> Does "hard lockup" mean that the HARDLOCKUP_DETECTOR infrastructure
>> prints a warning to dmesg? If so, can you share that warning?
> 
> I mean the machine locks hard - X stops updating, the mouse/keyboard
> stop responding. No pings, etc. When I reboot, there's nothing in the
> logs.
> 
>> If you don't have any way to see console output, and you don't have a
>> working serial console setup or such, you may want to try re-running
>> those tests while the kernel is booted with netconsole enabled to log
>> to a different machine over UDP (see
>> https://www.kernel.org/doc/Documentation/networking/netconsole.txt).
> 
> ACK, will try that now for you.
> 
>> You may want to try setting the sysctl kernel.sysrq=1 , then when the
>> system has locked up, press ALT+PRINT+L (to generate stack traces for
>> all active CPUs from NMI context), and maybe also ALT+PRINT+T and
>> ALT+PRINT+W (to collect more information about active tasks).
> 
> Nod.
> 
>> (If you share stack traces from these things with us, it would be
>> helpful if you could run them through scripts/decode_stacktrace.pl
>>from the kernel tree first, to add line number information.)
> 
> ACK.
> 
>> Trying to isolate the problem:
>>
>> __end_current_label_crit_section and end_current_label_crit_section
>> are aliases of each other (via #define), so that line change can't
>> have done anything.
>>
>> That leaves two possibilities AFAICS:
>> - the might_sleep() call by itself is causing issues for one of the
>> remaining users of begin_current_label_crit_section() (because it
>> causes preemption to happen more often where it didn't happen on
>> PREEMPT_VOLUNTARY before, or because it's trying to print a warning
>> message with the runqueue lock held, or something like that)
>> - the lack of "if (aa_replace_current_label(label) == 0)
>> aa_put_label(label);" in __begin_current_label_crit_section() is
>> somehow causing issues
>>
>> You could try to see whether just adding the might_sleep(), or just
>> replacing the begin_current_label_crit_section() call with
>> __begin_current_label_crit_section(), triggers the bug.
>>
>>
>> If you could recompile the kernel with CONFIG_DEBUG_ATOMIC_SLEEP - if
>> that isn't already set in your kernel config -, that might help track
>> down the problem, unless it magically makes the problem stop
>> triggering (which I guess would be conceivable if this indeed is a
>> race).
> 
> OK, will try that second...
> 

I have not been able to reproduce but

So looking at linux-4.19.y it looks like
1f8266ff5884 apparmor: don't try to replace stale label in ptrace access check

was picked without
ca3fde5214e1 apparmor: don't try to replace stale label in ptraceme check

Both of them are marked as
Fixes: b2d09ae449ced ("apparmor: move ptrace checks to using labels")

so I would expect them to be picked together.


ptraceme is potentially updating the task's cred while the access check is
running.

Try building after picking
ca3fde5214e1 apparmor: don't try to replace stale label in ptraceme check

Bug#963764: node-node-sass: uses embedded old security-buggy libsass

[Jonas Smedegaard]

Package: node-node-sass
Version: 4.13.1-2
Severity: serious
Tags: security

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

node-node-sass ships with an old release of libsass.

Since Debian release 4.13.1-2 this is explicitly used
(uncertain if previously it might alos accidentally be used).

Libsass has a series of known security flaws:
https://security-tracker.debian.org/tracker/source-package/libsass

The Debian package libsass is itself badly maintained regarding these
seciruty issues, but at least it is kept up-to-date with upstream,
meaning that _maybe_ they fixed all the issues:
https://bugs.debian.org/921952

Knowingly using older releases of libsass is unacceptable, and should
not be included in a stable release of Debian.


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl72LQAACgkQLHwxRsGg
ASG/fQ//WyKH6E3fW9fAndVJxR/2OcmE30JdTQpk69558VM8Qs/Vdr9JqLDVKuw0
I+K8LSQmsL4d39WsSGrWkZeqGFGOeIyAJ2y9GZi1uskRpNnA8/gJs3ZmIUY7yEWe
NloVaQE2KPUq4EdJnPWtDNDkObmZgtk0H8WtSfr7IHL/CctTBYZ3VImEz2NDoLjn
5i2SjZV2ypdYzlMWDvG6tksDKu6Ttcmy6PH78ibTFPHcMMBtD6mZ8e8TQjPb50WI
+lt8slQIRN791iM6f+6FoFtPRPAN+kAA6QqM0XJr7jO3qIqPAXtJpQLaRPEHozMu
8UTosXk1tRfkqhixB7JBmwRpCvmC90FPCIeAyYKIEoHO6Q0qdQW7RbHfzoEQIRwz
kDzI6E3eUgxsk9UsIQ2xqHnxL+iun5qQC3jnwWQvZiqU4KUwxVB/kYk5FPSlOTmC
Jb1UpgO1g3rFc8xYTB1ZHCbkGKTru3GsrdmmUJiweMhpo1SRheRdLNiMy90T3AdA
tZ2EZA6+W69LHdKmBDbDT4aHhx7PzKYjHhZAhzUvCStqoH44HKbvf2voAP7AFppp
bf8JmZ0ACbIhlQxjHSsav9SeYc28/tj4B7CFIPHZ+dbX6USn/DSSkvWjGxH93huq
cSqeo8ssV8beQLpeBtwLqf5IVJ0Kp6iW9e2I3MsUyDN2k76ttxw=
=yvR9
-END PGP SIGNATURE-

Bug#963493: Repeatable hard lockup running strace testsuite on 4.19.98+ onwards

[Steve McIntyre]

Hi Jann,

On Fri, Jun 26, 2020 at 04:25:59PM +0200, Jann Horn wrote:
>On Fri, Jun 26, 2020 at 3:41 PM Greg KH  wrote:
>> On Fri, Jun 26, 2020 at 12:35:58PM +0100, Steve McIntyre wrote:

...

>> > Considering I'm running strace build tests to provoke this bug,
>> > finding the failure in a commit talking about ptrace changes does look
>> > very suspicious...!
>> >
>> > Annoyingly, I can't reproduce this on my disparate other machines
>> > here, suggesting it's maybe(?) timing related.
>
>Does "hard lockup" mean that the HARDLOCKUP_DETECTOR infrastructure
>prints a warning to dmesg? If so, can you share that warning?

I mean the machine locks hard - X stops updating, the mouse/keyboard
stop responding. No pings, etc. When I reboot, there's nothing in the
logs.

>If you don't have any way to see console output, and you don't have a
>working serial console setup or such, you may want to try re-running
>those tests while the kernel is booted with netconsole enabled to log
>to a different machine over UDP (see
>https://www.kernel.org/doc/Documentation/networking/netconsole.txt).

ACK, will try that now for you.

>You may want to try setting the sysctl kernel.sysrq=1 , then when the
>system has locked up, press ALT+PRINT+L (to generate stack traces for
>all active CPUs from NMI context), and maybe also ALT+PRINT+T and
>ALT+PRINT+W (to collect more information about active tasks).

Nod.

>(If you share stack traces from these things with us, it would be
>helpful if you could run them through scripts/decode_stacktrace.pl
>from the kernel tree first, to add line number information.)

ACK.

>Trying to isolate the problem:
>
>__end_current_label_crit_section and end_current_label_crit_section
>are aliases of each other (via #define), so that line change can't
>have done anything.
>
>That leaves two possibilities AFAICS:
> - the might_sleep() call by itself is causing issues for one of the
>remaining users of begin_current_label_crit_section() (because it
>causes preemption to happen more often where it didn't happen on
>PREEMPT_VOLUNTARY before, or because it's trying to print a warning
>message with the runqueue lock held, or something like that)
> - the lack of "if (aa_replace_current_label(label) == 0)
>aa_put_label(label);" in __begin_current_label_crit_section() is
>somehow causing issues
>
>You could try to see whether just adding the might_sleep(), or just
>replacing the begin_current_label_crit_section() call with
>__begin_current_label_crit_section(), triggers the bug.
>
>
>If you could recompile the kernel with CONFIG_DEBUG_ATOMIC_SLEEP - if
>that isn't already set in your kernel config -, that might help track
>down the problem, unless it magically makes the problem stop
>triggering (which I guess would be conceivable if this indeed is a
>race).

OK, will try that second...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"I can't ever sleep on planes ... call it irrational if you like, but I'm
 afraid I'll miss my stop" -- Vivek Das Mohapatra

Bug#963761: node-node-sass: missing versioned dependency relation?: Sass could not find a binding for your current environment

[Paul Gevers]

Source: node-node-sass
Version: 4.14.1-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, nod...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:nodejs src:node-grunt-sass

Dear maintainer(s),

With a recent upload of nodejs the autopkgtest of node-grunt-sass fails
in testing when that autopkgtest is run with the binary packages of
nodejs from unstable. It passes when run with only packages from
testing. In tabular form:

   passfail
nodejs from testing12.18.0~dfsg-3
node-grunt-sassfrom testing3.1.0-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. Similar to the
issues with node-iconv and node-expat, node-node-sass seems to be
missing a versioned relation with nodejs. Because of the missing
relation, nodejs can be upgraded without the rebuild node-node-sass from
unstable.

Currently this regression is blocking the migration of nodejs to testing
[1]. Of course, nodejs shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in nodejs was
intended and your package needs to update to the new situation.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from nodejs should really add
a versioned Breaks on the unfixed version of (one of your) package(s).
Note: the Breaks is nice even if the issue is only in the autopkgtest as
it helps the migration software to figure out the right versions to
combine in the tests.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=nodejs

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-grunt-sass/6051450/log.gz

autopkgtest [01:12:40]: test pkg-js-autopkgtest: [---
Using package.json
Node module name is grunt-sass
# Copy test files
Looking at /usr/lib/nodejs/grunt-sass
Looking at /usr/lib/*/nodejs/grunt-sass
Looking at /usr/share/nodejs/grunt-sass
Found /usr/share/nodejs/grunt-sass
Linking /usr/share/nodejs/grunt-sass/package.json
Linking /usr/share/nodejs/grunt-sass/tasks
Launch debian/tests/pkg-js/test with sh -ex
+ grunt sass nodeunit
Loading "gruntfile.js" tasks...ERROR
>> Error: Missing binding
/usr/lib/x86_64-linux-gnu/nodejs/node-sass/vendor/linux-x64-72/binding.node
>> Node Sass could not find a binding for your current environment:
Linux 64-bit with Node.js 12.x
>>
>> Found bindings for the following environments:
>>   - Linux 64-bit with Node.js 10.x
>>
>> This usually happens because your environment has changed since
running `npm install`.
>> Run `npm rebuild node-sass` to download the binding for your current
environment.
Warning: Task "sass" not found. Use --force to continue.

Aborted due to warnings.
autopkgtest [01:12:41]: test pkg-js-autopkgtest: ---]



signature.asc
Description: OpenPGP digital signature

Processed: node-node-sass: missing versioned dependency relation?: Sass could not find a binding for your current environment

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:nodejs src:node-grunt-sass
Bug #963761 [src:node-node-sass] node-node-sass: missing versioned dependency 
relation?: Sass could not find a binding for your current environment
Added indication that 963761 affects src:nodejs and src:node-grunt-sass

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

Processed: your mail

[Debian Bug Tracking System]

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

> severity 963746 critical
Bug #963746 [nfs-common] nfs-common: Random Segmentation Violations of rpc.gssd 
Daemon
Severity set to 'critical' from 'normal'
> --
Stopping processing here.

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

Bug#963294: cmake-format: FTBFS: ./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create'

[Ian Campbell]

On Sun, 2020-06-21 at 21:52 +0200, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Thanks for the report Lucas.

I tried reproducing locally with:

sbuild -n -A -s --force-orig-source --apt-update -d unstable -v 
--no-run-lintian cmake-format_0.6.10-2.dsc

but the build was successful.

> Relevant part (hopefully):
> > /usr/bin/ld: CMakeFiles/cmTC_892ca.dir/src.c.o: in function `main':
> > ./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/src.c:11:
> >  undefined reference to `pthread_create'
> > /usr/bin/ld: 
> > ./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/src.c:12:
> >  undefined reference to `pthread_detach'
> > /usr/bin/ld: 
> > ./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/src.c:13:
> >  undefined reference to `pthread_join'
> > collect2: error: ld returned 1 exit status

There's also a little earlier:

   -- Looking for pthread.h
   -- Looking for pthread.h - found
   -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
   -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed

Which is not present in the successful builds.

What's weird is that in my local build and on the buildd I see:

  dh_auto_configure -O--buildsystem=pybuild
   pybuild --configure -i python{version} -p 3.8
   I: pybuild base:217: python3.8 setup.py config 
   running config
  dh_auto_build -O--buildsystem=pybuild
   pybuild --build -i python{version} -p 3.8
   I: pybuild base:217: /usr/bin/python3 setup.py build 

(buildd is slightly different since it has an extra `-i`)

Whereas in your log I see:

   dh_auto_configure -O--buildsystem=pybuild
pybuild --configure -i python{version} -p 3.8
I: pybuild base:217: dh_auto_configure --buildsystem=cmake 
--builddirectory="/<>/.pybuild/cpython3_3.8/build" -- <...snip...>
cd .pybuild/cpython3_3.8/build && <...>

It seems like pybuild has some heuristics for picking the build plugin
to use, for me (and buildd) it selects plugin_distutils.py but for you
it is selecting plugin_cmake.py. I can't see why. If you somehow had a
`CMakeCache.txt` in the package directory that might explain it, but
there's no reason for one of those to be there (I assume you'd have
said if this was e.g. a repeated build without cleaning the package dir
in the middle, but even if it was I don't think I'd ).

In the absence of a local repro I'm going to throw in a
'PYBUILD_SYSTEM=distutils' which ought to force things to go the
desired way no matter what. Fingers crossed!

Cheers,
Ian.

Bug#963039: node-iconv: versions of nodejs dependencies not properly documented

[Paul Gevers]

Hi Xavier,

On 20-06-2020 18:46, Xavier wrote:
> I think this will solve build/autopkgtest issue but not the real
> problem. You should instead add a:
> 
> Breaks: nodejs (<< ${source:Version}~)
> 
> In both libnode-dev and libnodeXX

I saw your upload (thanks for that), but how is *not* depending on
nodejs going to fix the issue we see in the autopkgtests?

As you can clearly see on the qa page [1] of nodejs, there is a relation
missing somewhere to make sure the right combination of packages is
tested. A "Breaks: node-iconv (<< 2.3.5-4~)" in nodejs would work, but
is that the appropriate solution?

Paul

[1] https://qa.debian.org/excuses.php?package=nodejs



signature.asc
Description: OpenPGP digital signature

Bug#959075: Still not working on Debian testing

[richard lucassen]

Quick & Dirty workaround:

Add a line in /etc/network/if-pre-up.d/ifenslave just under #!/bin/sh

BOND_MASTER=$IFACE

The BOND_MASTER variable is empty.

-- 
richard lucassen
http://contact.xaq.nl/

Bug#963757: fonts-font-awesome breaks streamlink autopkgtest: /usr/share/doc/python3-streamlink/html/_static/fonts/fontawesome-webfont.eot MISSING

[Paul Gevers]

Source: fonts-font-awesome, streamlink
Control: found -1 fonts-font-awesome/5.0.10+really4.7.0~dfsg-2
Control: found -1 streamlink/1.4.1+dfsg-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of fonts-font-awesome the autopkgtest of streamlink
fails in testing when that autopkgtest is run with the binary packages
of fonts-font-awesome from unstable. It passes when run with only
packages from testing. In tabular form:

   passfail
fonts-font-awesome from testing5.0.10+really4.7.0~dfsg-2
streamlink from testing1.4.1+dfsg-1
all others from testingfrom testing

I copied some of the output at the bottom of this report.
fonts-font-awesome changed paths, I didn't check if it forgot something,
or if streamlink needs adjustments (then fonts-font-awesome really
should add a versioned breaks).

Currently this regression is blocking the migration of
fonts-font-awesome to testing [1]. Due to the nature of this issue, I
filed this bug report against both packages. Can you please investigate
the situation and reassign the bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=fonts-font-awesome

https://ci.debian.net/data/autopkgtest/testing/amd64/s/streamlink/6047974/log.gz

Checking files:
Checking file /usr/share/doc/python3-streamlink/html/index.html OK
Checking file
/usr/share/doc/python3-streamlink/html/_static/fonts/FontAwesome.otf OK
Checking file
/usr/share/doc/python3-streamlink/html/_static/fonts/fontawesome-webfont.eot
MISSING
Checking file
/usr/share/doc/python3-streamlink/html/_static/fonts/fontawesome-webfont.svg
MISSING
Checking file
/usr/share/doc/python3-streamlink/html/_static/fonts/fontawesome-webfont.ttf
OK
Checking file
/usr/share/doc/python3-streamlink/html/_static/fonts/fontawesome-webfont.woff
MISSING
Checking file
/usr/share/doc/python3-streamlink/html/_static/js/modernizr.min.js OK



signature.asc
Description: OpenPGP digital signature

Processed: fonts-font-awesome breaks streamlink autopkgtest: /usr/share/doc/python3-streamlink/html/_static/fonts/fontawesome-webfont.eot MISSING

[Debian Bug Tracking System]

Processing control commands:

> found -1 fonts-font-awesome/5.0.10+really4.7.0~dfsg-2
Bug #963757 [src:fonts-font-awesome, src:streamlink] fonts-font-awesome breaks 
streamlink autopkgtest: 
/usr/share/doc/python3-streamlink/html/_static/fonts/fontawesome-webfont.eot 
MISSING
Marked as found in versions fonts-font-awesome/5.0.10+really4.7.0~dfsg-2.
> found -1 streamlink/1.4.1+dfsg-1
Bug #963757 [src:fonts-font-awesome, src:streamlink] fonts-font-awesome breaks 
streamlink autopkgtest: 
/usr/share/doc/python3-streamlink/html/_static/fonts/fontawesome-webfont.eot 
MISSING
Marked as found in versions streamlink/1.4.1+dfsg-1.

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

Bug#963721: [pkg-cryptsetup-devel] Bug#963721: libcryptsetup12 v2:2.3.3-1 seems to be breaking libssl somehow

[Christian Weeks]

Attached is the output of the various console commands, as well
as the backtrace from the broken launcher with the new lib.

Note that I am installing both amd64 and i386 versions. I do not
have cryptsetup even installed on this machine, I think this lib
is coming in from a dependency in gnome disks.

There is one key difference: in the older version, there is an
explicit libssl in the linker, but in the new version, there 
is not, even though it is somehow still being loaded.

Perhaps another lib is pulling a differing version somehow, and
this lib is stamping on it?

Thanks!

On Fri, 2020-06-26 at 17:23 +0200, Guilhem Moulin wrote:
> Control: tag -1 moreinfo
> 
> Hi Christian,
> 
> On Thu, 25 Jun 2020 at 21:58:43 -0400, Christian Weeks wrote:
> > I installed the newest version of libcryptsetup12.
> 
> Unfortunately you appeared to file this bug using Buster's
> libcryptsetup12 so the metada doesn't describe the buggy environment
> (Version: 2:2.1.0-5+deb10u2).  Please show the output of `apt upgrade
> libcryptsetup12` that yields the buggy environment.  (I.e., you don't
> encounter the bug before the command but do after the upgrade.)  The
> output of
> 
> ldd /lib/*-linux-gnu/libcryptsetup.so.12.6.0 /sbin/cryptsetup
> 
> and
> 
> dpkg-query -l "*cryptsetup*"
> 
> before *and* after the upgrade might be helpful too.
> 
> > Suddenly, minecraft would not run! 
> > Backtraces in gdb indicate that something is broken in SSL.
> 
> Care to share said backtrace also?
> 
> cheers
/lib/i386-linux-gnu/libcryptsetup.so.12.4.0:
linux-gate.so.1 (0xf7f31000)
libuuid.so.1 => /lib/i386-linux-gnu/libuuid.so.1 (0xf7e83000)
libdevmapper.so.1.02.1 => /lib/i386-linux-gnu/libdevmapper.so.1.02.1 
(0xf7e1e000)
libssl.so.1.1 => /lib/i386-linux-gnu/libssl.so.1.1 (0xf7d87000)
libcrypto.so.1.1 => /lib/i386-linux-gnu/libcrypto.so.1.1 (0xf7ac4000)
libargon2.so.1 => /lib/i386-linux-gnu/libargon2.so.1 (0xf7ab6000)
librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xf7aac000)
libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf7aa6000)
libjson-c.so.3 => /lib/i386-linux-gnu/libjson-c.so.3 (0xf7a99000)
libblkid.so.1 => /lib/i386-linux-gnu/libblkid.so.1 (0xf7a3e000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf785a000)
/lib/ld-linux.so.2 (0xf7f33000)
libselinux.so.1 => /lib/i386-linux-gnu/libselinux.so.1 (0xf782b000)
libudev.so.1 => /lib/i386-linux-gnu/libudev.so.1 (0xf77ff000)
libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf76fb000)
libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf76d9000)
libpcre2-8.so.0 => /lib/i386-linux-gnu/libpcre2-8.so.0 (0xf7642000)
/lib/x86_64-linux-gnu/libcryptsetup.so.12.4.0:
linux-vdso.so.1 (0x7ffefefa)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f8855e44000)
libdevmapper.so.1.02.1 => /lib/x86_64-linux-gnu/libdevmapper.so.1.02.1 
(0x7f8855dd8000)
libssl.so.1.1 => /lib/x86_64-linux-gnu/libssl.so.1.1 
(0x7f8855d46000)
libcrypto.so.1.1 => /lib/x86_64-linux-gnu/libcrypto.so.1.1 
(0x7f8855a5a000)
libargon2.so.1 => /lib/x86_64-linux-gnu/libargon2.so.1 
(0x7f8855a5)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f8855a45000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f8855a3e000)
libjson-c.so.3 => /lib/x86_64-linux-gnu/libjson-c.so.3 
(0x7f8855a31000)
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 
(0x7f88559e)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f885581d000)
/lib64/ld-linux-x86-64.so.2 (0x7f8855eda000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 
(0x7f88557f2000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f88557c6000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f885567f000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f885565e000)
libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0 
(0x7f88555ce000)
/sbin/cryptsetup:
ldd: /sbin/cryptsetup: No such file or directory

dpkg-query -l "*cryptsetup*"
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version   Architecture Description
+++-=-=--
un  cryptsetup-initramfs (no description 
available)
ii  libcryptsetup12:amd64 2:2.1.0-5+deb10u2 amd64disk encryption 
support - shared library
ii  libcryptsetup12:i386  2:2.1.0-5+deb10u2 i386 disk encryption 
support - shared library


sudo apt install libcryptsetup12 libcryptsetup12:i386
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following 

Bug#936513: marked as done (ffrenzy: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 26 Jun 2020 17:40:57 +0200
with message-id <20200626154057.GA135819@pisco.westfalen.local>
and subject line Re: ffrenzy: Python2 removal in sid/bullseye - reopen 936513
has caused the Debian Bug report #936513,
regarding ffrenzy: Python2 removal in sid/bullseye
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.)


-- 
936513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ffrenzy
Version: 1.0.2~svn20150731-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:ffrenzy

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
On Sat, Jan 18, 2020 at 09:23:59PM -0500, Sandro Tosi wrote:
> Control: reopen -1
> 
> This bug was closed, but the package has still some dependencies towards
> Python2 packages, in details:
> 
> (source:ffrenzy)Build-Depends->python
> (binary:ffrenzy)Depends->python:any
> (binary:ffrenzy)Depends->python-gtk2
> (binary:ffrenzy)Depends->python-glade2
> (binary:ffrenzy)Depends->python-pygame
> 
> Re-opening, so that they can be taken care of.

The package was removed from the archive, closing.

Cheers,
Moritz--- End Message ---

Processed: Re: [pkg-cryptsetup-devel] Bug#963721: libcryptsetup12 v2:2.3.3-1 seems to be breaking libssl somehow

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #963721 [libcryptsetup12] libcryptsetup12 v2:2.3.3-1 seems to be breaking 
libssl somehow
Added tag(s) moreinfo.

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

Bug#963721: [pkg-cryptsetup-devel] Bug#963721: libcryptsetup12 v2:2.3.3-1 seems to be breaking libssl somehow

[Guilhem Moulin]

Control: tag -1 moreinfo

Hi Christian,

On Thu, 25 Jun 2020 at 21:58:43 -0400, Christian Weeks wrote:
> I installed the newest version of libcryptsetup12.

Unfortunately you appeared to file this bug using Buster's
libcryptsetup12 so the metada doesn't describe the buggy environment
(Version: 2:2.1.0-5+deb10u2).  Please show the output of `apt upgrade
libcryptsetup12` that yields the buggy environment.  (I.e., you don't
encounter the bug before the command but do after the upgrade.)  The
output of

ldd /lib/*-linux-gnu/libcryptsetup.so.12.6.0 /sbin/cryptsetup

and

dpkg-query -l "*cryptsetup*"

before *and* after the upgrade might be helpful too.

> Suddenly, minecraft would not run! 
> Backtraces in gdb indicate that something is broken in SSL.

Care to share said backtrace also?

cheers
-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#963493: Repeatable hard lockup running strace testsuite on 4.19.98+ onwards

[Steve McIntyre]

On Fri, Jun 26, 2020 at 02:45:18PM +0100, Steve McIntyre wrote:
>Hey Greg,
>
>On Fri, Jun 26, 2020 at 03:41:32PM +0200, Greg KH wrote:
>>On Fri, Jun 26, 2020 at 12:35:58PM +0100, Steve McIntyre wrote:
>>> 
>>> e58f543fc7c0926f31a49619c1a3648e49e8d233 is the first bad commit
>>> commit e58f543fc7c0926f31a49619c1a3648e49e8d233
>>> Author: Jann Horn 
>>> Date:   Thu Sep 13 18:12:09 2018 +0200
>
>...
>
>>> Annoyingly, I can't reproduce this on my disparate other machines
>>> here, suggesting it's maybe(?) timing related.
>>> 
>>> Hope this helps - happy to give more information, test things, etc.
>>
>>So if you just revert this one patch, all works well?
>
>Correct.
>
>>I've added the authors of the patch to the cc: list...
>>
>>Also, does this problem happen on Linus's tree?
>
>Just building to check that now...

Current head here (3e08a95294a4fb3702bb3d35ed08028433c37fe6) works fine.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
The two hard things in computing:
 * naming things
 * cache invalidation
 * off-by-one errors  -- Stig Sandbeck Mathisen

Bug#963755: installation-report: fails to boot with Gnome DE

[Ambroise Grau]

Package: installation-reports
Version: 2.71
Severity: grave
Justification: renders package unusable

Dear Maintainer,


   * What led up to the situation?
Booting the debian after installation, hangs at loading Gnome DE.
   * What exactly did you do (or not do) that was effective (or
 ineffective)? 
Launched rescue mode, verified partition table and launched
interractive shell to verify logs.
   * What was the outcome of this action?
Partition table is as expected, shell works as expected, logs
indicate no obvious error.
   * What outcome did you expect instead?
Expected Debian to boot directly.



-- Package-specific info:

Boot method: USB floppy disc
Image version: 64-bit PC netinst iso, downloaded 2020/06/23, 
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-10.4.0-amd64-netinst.iso
Date: 

Machine: GameMax desktop
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[E]
Overall install:[E]

Comments/Problems:
The boot loader installed properly, detected the other OS present
(Windows 10) but failed to write the boot table correctly so that
only debian appears there.
Launching debian hangs after loading the Gnome DE in normal mode, recovery mode 
works fine.


-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="10 (buster) - installer build 20190702+deb10u4"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux GM-Debian 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2 (2020-04-29) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core 
Processor Family DRAM Controller [8086:0100] (rev 09)
lspci -knn: Subsystem: Intel Corporation Device [8086:2017]
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd 
Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 6 
Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
lspci -knn: Subsystem: Intel Corporation Device [8086:2017]
lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82579V 
Gigabit Network Connection [8086:1503] (rev 05)
lspci -knn: Subsystem: Intel Corporation Device [8086:2017]
lspci -knn: Kernel driver in use: e1000e
lspci -knn: Kernel modules: e1000e
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 
Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05)
lspci -knn: Subsystem: Intel Corporation Device [8086:2017]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series 
Chipset Family High Definition Audio Controller [8086:1c20] (rev 05)
lspci -knn: Subsystem: Intel Corporation Device [8086:2017]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: Kernel modules: snd_hda_intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b5)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 
Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 05)
lspci -knn: Subsystem: Intel Corporation Device [8086:2017]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: Kernel modules: ehci_pci
lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation H61 Express Chipset 
Family LPC Controller [8086:1c5c] (rev 05)
lspci -knn: Subsystem: Intel Corporation Device [8086:2017]
lspci -knn: 00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 
Series Chipset Family SATA AHCI Controller [8086:1c02] (rev 05)
lspci -knn: Subsystem: Intel Corporation Device [8086:2017]
lspci -knn: Kernel driver in use: ahci
lspci -knn: Kernel modules: ahci
lspci -knn: 00:1f.3 SMBus [0c05]: Intel Corporation 6 Series/C200 Series 
Chipset Family SMBus Controller [8086:1c22] (rev 05)
lspci -knn: Subsystem: 

Bug#963493: Repeatable hard lockup running strace testsuite on 4.19.98+ onwards

[Steve McIntyre]

Hey Greg,

On Fri, Jun 26, 2020 at 03:41:32PM +0200, Greg KH wrote:
>On Fri, Jun 26, 2020 at 12:35:58PM +0100, Steve McIntyre wrote:
>> 
>> e58f543fc7c0926f31a49619c1a3648e49e8d233 is the first bad commit
>> commit e58f543fc7c0926f31a49619c1a3648e49e8d233
>> Author: Jann Horn 
>> Date:   Thu Sep 13 18:12:09 2018 +0200

...

>> Annoyingly, I can't reproduce this on my disparate other machines
>> here, suggesting it's maybe(?) timing related.
>> 
>> Hope this helps - happy to give more information, test things, etc.
>
>So if you just revert this one patch, all works well?

Correct.

>I've added the authors of the patch to the cc: list...
>
>Also, does this problem happen on Linus's tree?

Just building to check that now...

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
< Aardvark> I dislike C++ to start with. C++11 just seems to be
handing rope-creating factories for users to hang multiple
instances of themselves.

Bug#963493: Repeatable hard lockup running strace testsuite on 4.19.98+ onwards

[Greg KH]

On Fri, Jun 26, 2020 at 12:35:58PM +0100, Steve McIntyre wrote:
> Hi folks,
> 
> I'm the maintainer in Debian for strace. Trying to reproduce
> https://bugs.debian.org/963462 on my machine (Thinkpad T470), I've
> found a repeatable hard lockup running the strace testsuite. Each time
> it seems to have failed in a slightly different place in the testsuite
> (suggesting it's not one particular syscall test that's triggering the
> failure). I initially found this using Debian's current Buster kernel
> (4.19.118+2+deb10u1), then backtracking I found that 4.19.98+1+deb10u1
> worked fine.
> 
> I've bisected to find the failure point along the linux-4.19.y stable
> branch and what I've got to is the following commit:
> 
> e58f543fc7c0926f31a49619c1a3648e49e8d233 is the first bad commit
> commit e58f543fc7c0926f31a49619c1a3648e49e8d233
> Author: Jann Horn 
> Date:   Thu Sep 13 18:12:09 2018 +0200
> 
> apparmor: don't try to replace stale label in ptrace access check
> 
> [ Upstream commit 1f8266ff58840d698a1e96d2274189de1bdf7969 ]
> 
> As a comment above begin_current_label_crit_section() explains,
> begin_current_label_crit_section() must run in sleepable context because
> when label_is_stale() is true, aa_replace_current_label() runs, which uses
> prepare_creds(), which can sleep.
> Until now, the ptrace access check (which runs with a task lock held)
> violated this rule.
> 
> Also add a might_sleep() assertion to begin_current_label_crit_section(),
> because asserts are less likely to be ignored than comments.
> 
> Fixes: b2d09ae449ced ("apparmor: move ptrace checks to using labels")
> Signed-off-by: Jann Horn 
> Signed-off-by: John Johansen 
> Signed-off-by: Sasha Levin 
> 
> :04 04 ca92f885a38c1747b812116f19de6967084a647e 
> 865a227665e460e159502f21e8a16e6fa590bf50 M security
> 
> Considering I'm running strace build tests to provoke this bug,
> finding the failure in a commit talking about ptrace changes does look
> very suspicious...!
> 
> Annoyingly, I can't reproduce this on my disparate other machines
> here, suggesting it's maybe(?) timing related.
> 
> Hope this helps - happy to give more information, test things, etc.

So if you just revert this one patch, all works well?

I've added the authors of the patch to the cc: list...

Also, does this problem happen on Linus's tree?

thanks,

greg k-h

Bug#963751: wordpress-shibboleth: Please depend on libapache2-mod-shib (not -shib2)

[Ferenc Wágner]

Package: wordpress-shibboleth
Severity: serious

Dear Maintainer,

The Shibboleth SP package migrated from providing libapache2-mod-shib2
to libapache2-mod-shib; the former is already transitional in buster.
Please switch to using the new package name to keep wordpress-shibboleth
installable.
-- 
Thanks,
Feri.

Processed: retitle 963678 to hedgewars: FTBFS with ghc 8.8

[Debian Bug Tracking System]

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

> # Fix missing program name in title: Version 8.8 of what? :-)
> retitle 963678 hedgewars: FTBFS with ghc 8.8
Bug #963678 [src:hedgewars] hedgewars: FTBFS with 8.8
Changed Bug title to 'hedgewars: FTBFS with ghc 8.8' from 'hedgewars: FTBFS 
with 8.8'.
> thanks
Stopping processing here.

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

Bug#963709: pyside2: FTBFS with Qt 5.14: 'PySide2.QtCore.QDate' called with wrong argument types: PySide2.QtCore.QDate(date)

[Dmitry Shachnev]

On Fri, Jun 26, 2020 at 11:55:51AM +0300, Dmitry Shachnev wrote:
> Have not looked at the arm64 failure yet.

Looked at arm64 now.

That failure is not new, it regressed between 5.13.2-3 and 5.14.0-1~exp1
where that test was un-blacklisted:

https://salsa.debian.org/qt-kde-team/qt/pyside2/-/commit/136f50b5760ddb10

Unfortunately undefining XDG_RUNTIME_DIR is not enough to make it pass.

Perhaps it can be re-added to blacklist as a temporary solution?

I tried to debug it, and found out that for some reason
__glXLookupVendorByName("mesa") fails, so __glXLookupVendorByScreen
falls back to FALLBACK_VENDOR_NAME (= "indirect") which does not work
properly. No time to debug further...

This issue happens with PySide and PyQt programs, but not with C++.
Maybe it's the same issue as #960073.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#963749: r-bioc-rwikipathways: non-installable in sid

[Gianfranco Costamagna]

Source: r-bioc-rwikipathways
Version: 1.6.1+dfsg-1
Severity: serious

Hello, for some reasons, dh-r is evaluating wrongly the runtime dependency on 
r-api-bioc (maybe from DESCRIPTION file?)

dpkg: dependency problems prevent configuration of r-bioc-rwikipathways:
 r-bioc-rwikipathways depends on r-api-bioc-3.10; however:
  Package r-api-bioc-3.10 is not installed.


this makes the package non-installable.
(please reassign to r-base if you think the problem is there)

thanks for having a look!

Gianfranco

Processed: bug 963493 is forwarded to https://lore.kernel.org/stable/20200626113558.ga32...@unset.einval.com/T/#u

[Debian Bug Tracking System]

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

> forwarded 963493 
> https://lore.kernel.org/stable/20200626113558.ga32...@unset.einval.com/T/#u
Bug #963493 [src:linux] Repeatable hard lockup running strace testsuite using 
4.19.118+2+deb10u1, 4.19.98+1+deb10u1 works fine
Set Bug forwarded-to-address to 
'https://lore.kernel.org/stable/20200626113558.ga32...@unset.einval.com/T/#u'.
> thanks
Stopping processing here.

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

Processed: notfound 963721 in 2:2.1.0-5+deb10u2, found 963721 in 2:2.3.3-1

[Debian Bug Tracking System]

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

> # Fixing the versions according to bug description, bug has been filed after 
> reverting to version in buster and version hasn't been fixed manually
> notfound 963721 2:2.1.0-5+deb10u2
Bug #963721 [libcryptsetup12] libcryptsetup12 v2:2.3.3-1 seems to be breaking 
libssl somehow
No longer marked as found in versions cryptsetup/2:2.1.0-5+deb10u2.
> found 963721 2:2.3.3-1
Bug #963721 [libcryptsetup12] libcryptsetup12 v2:2.3.3-1 seems to be breaking 
libssl somehow
Marked as found in versions cryptsetup/2:2.3.3-1.
> thanks
Stopping processing here.

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

Bug#877106: pinta: Pinta 1.6-2 crashes on image scaling and other image manipulation.

[Kentaro Hayashi]

Hi,

It doesn't resove the issue completely,
but the following commit may reduce crash frequency.

  Fix an NRE I randomly hit. 
  
https://github.com/PintaProject/Pinta/commit/1e6197674c1dc653a76f231eb1ace7cf69cdf984

--- a/Pinta.Core/Classes/DocumentWorkspace.cs
+++ b/Pinta.Core/Classes/DocumentWorkspace.cs
@@ -270,7 +270,8 @@

zoom = Math.Min (zoom, 3600);

-   PintaCore.Chrome.Canvas.GdkWindow.FreezeUpdates ();
+   if (PintaCore.Chrome.Canvas.GdkWindow != null)
+   PintaCore.Chrome.Canvas.GdkWindow.FreezeUpdates 
();
PintaCore.Actions.View.SuspendZoomUpdate ();

Gtk.Viewport view = 
(Gtk.Viewport)PintaCore.Chrome.Canvas.Parent;
@@ -336,7 +337,8 @@
RecenterView (center_x, center_y);

PintaCore.Actions.View.ResumeZoomUpdate ();
-   PintaCore.Chrome.Canvas.GdkWindow.ThawUpdates ();
+   if (PintaCore.Chrome.Canvas.GdkWindow != null)
+   PintaCore.Chrome.Canvas.GdkWindow.ThawUpdates 
();
}
#endregion
}

--- a/Pinta.Core/Classes/DocumentWorkspace.cs
+++ b/Pinta.Core/Classes/DocumentWorkspace.cs
@@ -270,7 +270,8 @@
 			
 			zoom = Math.Min (zoom, 3600);
 			
-			PintaCore.Chrome.Canvas.GdkWindow.FreezeUpdates ();
+			if (PintaCore.Chrome.Canvas.GdkWindow != null)
+PintaCore.Chrome.Canvas.GdkWindow.FreezeUpdates ();
 			PintaCore.Actions.View.SuspendZoomUpdate ();
 			
 			Gtk.Viewport view = (Gtk.Viewport)PintaCore.Chrome.Canvas.Parent;
@@ -336,7 +337,8 @@
 			RecenterView (center_x, center_y);
 			
 			PintaCore.Actions.View.ResumeZoomUpdate ();
-			PintaCore.Chrome.Canvas.GdkWindow.ThawUpdates ();
+			if (PintaCore.Chrome.Canvas.GdkWindow != null)
+PintaCore.Chrome.Canvas.GdkWindow.ThawUpdates ();
 		}
 		#endregion
 	}

Bug#963748: haskell-gitlib: FTBFS with ghc-8.8

[Ilias Tsitsimpis]

Source: haskell-gitlib
Version: 3.1.2-3
Severity: grave
Justification: renders package unusable

This package FTBFS with ghc-8.8.

-- 
Ilias

Bug#963493: Repeatable hard lockup running strace testsuite on 4.19.98+ onwards

[Steve McIntyre]

Hi folks,

I'm the maintainer in Debian for strace. Trying to reproduce
https://bugs.debian.org/963462 on my machine (Thinkpad T470), I've
found a repeatable hard lockup running the strace testsuite. Each time
it seems to have failed in a slightly different place in the testsuite
(suggesting it's not one particular syscall test that's triggering the
failure). I initially found this using Debian's current Buster kernel
(4.19.118+2+deb10u1), then backtracking I found that 4.19.98+1+deb10u1
worked fine.

I've bisected to find the failure point along the linux-4.19.y stable
branch and what I've got to is the following commit:

e58f543fc7c0926f31a49619c1a3648e49e8d233 is the first bad commit
commit e58f543fc7c0926f31a49619c1a3648e49e8d233
Author: Jann Horn 
Date:   Thu Sep 13 18:12:09 2018 +0200

apparmor: don't try to replace stale label in ptrace access check

[ Upstream commit 1f8266ff58840d698a1e96d2274189de1bdf7969 ]

As a comment above begin_current_label_crit_section() explains,
begin_current_label_crit_section() must run in sleepable context because
when label_is_stale() is true, aa_replace_current_label() runs, which uses
prepare_creds(), which can sleep.
Until now, the ptrace access check (which runs with a task lock held)
violated this rule.

Also add a might_sleep() assertion to begin_current_label_crit_section(),
because asserts are less likely to be ignored than comments.

Fixes: b2d09ae449ced ("apparmor: move ptrace checks to using labels")
Signed-off-by: Jann Horn 
Signed-off-by: John Johansen 
Signed-off-by: Sasha Levin 

:04 04 ca92f885a38c1747b812116f19de6967084a647e 
865a227665e460e159502f21e8a16e6fa590bf50 M security

Considering I'm running strace build tests to provoke this bug,
finding the failure in a commit talking about ptrace changes does look
very suspicious...!

Annoyingly, I can't reproduce this on my disparate other machines
here, suggesting it's maybe(?) timing related.

Hope this helps - happy to give more information, test things, etc.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Managing a volunteer open source project is a lot like herding
 kittens, except the kittens randomly appear and disappear because they
 have day jobs." -- Matt Mackall

Bug#963546: meson: autopkgtest failures

[Jussi Pakkanen]

On Fri, 26 Jun 2020 at 14:09, Gianfranco Costamagna
 wrote:

> > > I asked in Ubuntu to move the meson autopkgtests to a machine with more 
> > > ram memory, and
> > > now the test passes.
> > > The Ubuntu VMs have 1536MB of ram, probably not enough for the testsuite 
> > > to pass.
> >
> > Good that it works, but that seems a bit strange. I run the test suite
> > on an x86 Debian VM with 4 gigs of ram and it passes without problems.
>
> Probably if you lower the 4GB to 1.5GB you will get the same failure?

D'oh! I accidentally read that as 15 GB rather than 1.5GB because I
blindly assumed that there is no way the default value can be that
low. Compiling e.g. any C++ program of decent size makes the linker
take several gigabytes of ram easily.

Bug#963745: haskell-regex-tdfa-text: Removal notice: Deprecated

[Ilias Tsitsimpis]

Source: haskell-regex-tdfa-text
Version: 1.0.0.3-4
Severity: grave
Justification: renders package unusable

This package has been deprecated in favor of regex-tdfa.
I intend to remove this package.

-- 
Ilias

Bug#963546: meson: autopkgtest failures

[Gianfranco Costamagna]

On Fri, 26 Jun 2020 11:38:34 +0300 Jussi Pakkanen  wrote:
> On Fri, 26 Jun 2020 at 10:48, Gianfranco Costamagna
>  wrote:
> 
> > I asked in Ubuntu to move the meson autopkgtests to a machine with more ram 
> > memory, and
> > now the test passes.
> > The Ubuntu VMs have 1536MB of ram, probably not enough for the testsuite to 
> > pass.
> 
> Good that it works, but that seems a bit strange. I run the test suite
> on an x86 Debian VM with 4 gigs of ram and it passes without problems.
> 
> 

Probably if you lower the 4GB to 1.5GB you will get the same failure?

IIRC when I tried with a value around 2GB everything was good...

G.

Bug#963339: nova: FTBFS: ValueError: Sentinels must not start with _

[Thomas Goirand]

Hi,

This issue is in fact related to the recent upgrade of mock to version
4.0.2 as per the reports here:
https://github.com/testing-cabal/mock/issues/487

which itself looks like related to a Python 3.8 upstream issue.

Moving forward, I probably can disable the underscore test in oslo.utils
which shouldn't be a problem.

Cheers,

Thomas Goirand (zigo)

Processed: found 963712 in 1.4.7.1-1, notfound 963712 in 1.4.7.-1

[Debian Bug Tracking System]

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

> # fix meta data
> found 963712 1.4.7.1-1
Bug #963712 [src:haskell-aeson] haskell-aeson: FTBFS ON armel, armhf, i386, 
s390x
Marked as found in versions haskell-aeson/1.4.7.1-1.
> notfound 963712 1.4.7.-1
Bug #963712 [src:haskell-aeson] haskell-aeson: FTBFS ON armel, armhf, i386, 
s390x
The source 'haskell-aeson' and version '1.4.7.-1' do not appear to match any 
binary packages
No longer marked as found in versions haskell-aeson/1.4.7.-1.
> thanks
Stopping processing here.

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

Processed: unblock 951730 with 963699, unblock 951780 with 963699, unblock 951877 with 963699 ...

[Debian Bug Tracking System]

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

> unblock 951730 with 963699
Bug #951730 [argyll] OpenSSL linking without license exception
951730 was blocked by: 924937 963699
951730 was not blocking any bugs.
Removed blocking bug(s) of 951730: 963699
> unblock 951780 with 963699
Bug #951780 [eurephia] OpenSSL linking without license exception
951780 was blocked by: 963699 924937
951780 was not blocking any bugs.
Removed blocking bug(s) of 951780: 963699
> unblock 951877 with 963699
Bug #951877 [restbed] OpenSSL linking without license exception
951877 was blocked by: 924937
951877 was not blocking any bugs.
Removed blocking bug(s) of 951877: 963699
> unblock 951911 with 963699
Bug #951911 [librelp0] OpenSSL linking without license exception
951911 was blocked by: 924937
951911 was not blocking any bugs.
Removed blocking bug(s) of 951911: 963699
> unblock 952399 with 963699
Bug #952399 [kmod] OpenSSL linking without license exception
952399 was blocked by: 924937
952399 was not blocking any bugs.
Removed blocking bug(s) of 952399: 963699
> thanks
Stopping processing here.

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

Bug#963715: rsyslog: imuxsock overrides /dev/log from journald

[Michael Biebl]

Am 26.06.20 um 02:21 schrieb Michael Biebl:
> Am 25.06.20 um 23:48 schrieb Christian Göttsche:
>> Package: rsyslog
>> Version: 8.2006.0-1
>>
>> Hi,
>>
>> since version 8.2006.0-1 the rsyslog module imuxsock overrides
>> /dev/log, which is by default a symlink to
>> /run/systemd/journal/dev-log, by creating a socket.
>> This leads to not all messages being forwarded to systemd-journald.
>>
>> Is this an intended behaviour?
> 
> No.
> 
> I suspect this is a change triggered by this upstream commit:
> 
> 
> https://github.com/rsyslog/rsyslog/pull/4317
> 
> Specifically the syslog.socket bits. Can you try and revert those changes?
> 


--- a/rsyslog.service.in
+++ b/rsyslog.service.in
@@ -1,8 +1,10 @@
 [Unit]
 Description=System Logging Service
-Requires=syslog.socket
+;Requires=syslog.socket


@@ -16,4 +18,4 @@ LimitNOFILE=16384

 [Install]
 WantedBy=multi-user.target
-Alias=syslog.service
+;Alias=syslog.service


The result is, that the syslog.service symlink is no longer created upon
installation and syslog.socket not started during boot.



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#963715: rsyslog: imuxsock overrides /dev/log from journald

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #963715 [rsyslog] rsyslog: imuxsock overrides /dev/log from journald
Severity set to 'serious' from 'normal'

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

Bug#963709: pyside2: FTBFS with Qt 5.14: 'PySide2.QtCore.QDate' called with wrong argument types: PySide2.QtCore.QDate(date)

[Dmitry Shachnev]

Hi Kurt!

On Thu, Jun 25, 2020 at 02:37:43PM -0500, Kurt Kremitzki wrote:
> Hello,
>
> Yes, it can be uploaded, I meant to get to it last weekend but wasn't able
> to; I'll see if I can do it this evening.

Thanks for the upload!

Unfortunately, it FTBFS on armel and arm64.

The armel failure is caused by my change that dropped ARMv4 support from
qtbase:

https://salsa.debian.org/qt-kde-team/qt/qtbase/commit/4d28e91e32f57e1e

I tested on a porter box (abel.d.o), and found out that while GCC reports
ARM version as 5, clang reports it as 4 (and pyside2 uses clang):

$ gcc -dM -E - < /dev/null
[...]
#define __ARM_ARCH_5TE__ 1
#define __ARM_ARCH 5
[...]

$ clang -dM -E - < /dev/null
[...]
#define __ARM_ARCH 4
#define __ARM_ARCH_4T__ 1
[...]

So I will re-add that patch to qtbase, which should fix it.

Have not looked at the arm64 failure yet.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#963737: highlighting-kate: Removal notice: Deprecated

[Ilias Tsitsimpis]

Source: highlighting-kate
Version: 0.6.4-5
Severity: grave
Justification: renders package unusable

This package has been deprecated in favor of skylighting.
We should make sure that anyone using this package has migrated to
skylighting and then remove it.

-- 
Ilias

Bug#963546: meson: autopkgtest failures

[Jussi Pakkanen]

On Fri, 26 Jun 2020 at 10:48, Gianfranco Costamagna
 wrote:

> I asked in Ubuntu to move the meson autopkgtests to a machine with more ram 
> memory, and
> now the test passes.
> The Ubuntu VMs have 1536MB of ram, probably not enough for the testsuite to 
> pass.

Good that it works, but that seems a bit strange. I run the test suite
on an x86 Debian VM with 4 gigs of ram and it passes without problems.

Processed: fixed 874901 in gle-graphics/4.2.5-8

[Debian Bug Tracking System]

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

> fixed 874901 gle-graphics/4.2.5-8
Bug #874901 {Done: Paul Wise } [src:gle-graphics] 
[gle-graphics] Future Qt4 removal from Buster
Marked as fixed in versions gle-graphics/4.2.5-8.
> thanks
Stopping processing here.

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

Processed (with 1 error): fixed 874901 in src:gle-graphics/4.2.5-8, closing 874901

[Debian Bug Tracking System]

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

> fixed 874901 src:gle-graphics/4.2.5-8
Unknown command or malformed arguments to command.
> close 874901
Bug #874901 [src:gle-graphics] [gle-graphics] Future Qt4 removal from Buster
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: unarchiving 874901, reopening 874901, unarchiving 935720, reopening 935720, unarchiving 935913 ...

[Debian Bug Tracking System]

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

> # src:gle-graphics was reintroduced: 
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 874901
Bug #874901 {Done: Debian FTP Masters } 
[src:gle-graphics] [gle-graphics] Future Qt4 removal from Buster
Unarchived Bug 874901
> reopen 874901
Bug #874901 {Done: Debian FTP Masters } 
[src:gle-graphics] [gle-graphics] Future Qt4 removal from Buster
'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 4.2.5-7+rm.
> unarchive 935720
Bug #935720 {Done: Debian FTP Masters } 
[gle-graphics] gle-graphics: needs manual search for libgs.so
Unarchived Bug 935720
> reopen 935720
Bug #935720 {Done: Debian FTP Masters } 
[gle-graphics] gle-graphics: needs manual search for libgs.so
'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 4.2.5-7+rm.
> unarchive 935913
Bug #935913 {Done: Debian FTP Masters } 
[gle-graphics] gle-graphics: qgle segfaults when modifying text strings
Unarchived Bug 935913
> reopen 935913
Bug #935913 {Done: Debian FTP Masters } 
[gle-graphics] gle-graphics: qgle segfaults when modifying text strings
'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 4.2.5-7+rm.
> thanks
Stopping processing here.

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

Processed: found 963726 in 3.1.3-1, severity of 963726 is serious

[Debian Bug Tracking System]

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

> found 963726 3.1.3-1
Bug #963726 [projectm-data] projectm-data should conflict with libprojectm2v5
Marked as found in versions projectm/3.1.3-1.
> severity 963726 serious
Bug #963726 [projectm-data] projectm-data should conflict with libprojectm2v5
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#963335: autogen: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[Andreas Metzler]

On 2020-06-21 Lucas Nussbaum  wrote:
> Source: autogen
> Version: 1:5.18.16-4
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200620 ftbfs-bullseye

> Hi,

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

> Relevant part (hopefully):
> > make[3]: Leaving directory '/<>/xml2ag'
> > make[2]: Leaving directory '/<>/xml2ag'
> > Making check in doc
> > make[2]: Entering directory '/<>/doc'
> > make  check-am
> > make[3]: Entering directory '/<>/doc'
> > make[3]: Nothing to be done for 'check-am'.
> > make[3]: Leaving directory '/<>/doc'
> > make[2]: Leaving directory '/<>/doc'
> > Making check in pkg
> > make[2]: Entering directory '/<>/pkg'
> > make[2]: Nothing to be done for 'check'.
> > make[2]: Leaving directory '/<>/pkg'
> > make[2]: Entering directory '/<>'
> > make[2]: Leaving directory '/<>'
> > E: Build killed with signal TERM after 150 minutes of inactivity
[...]

This is caused/triggered by upgrading make from 4.2.1 to 4.3.

With 4.3. the build reprodicibly fails with -j2, make is hanging:

ametzler@argenau:~$ pstree -aph 243168
dpkg-buildpacka,243168 /usr/bin/dpkg-buildpackage -uc -us -rfakeroot -j1 -j2
  └─rules,243213 -f debian/rules binary
  └─dh,243216 /usr/bin/dh binary
  └─dh_auto_test,251687 /usr/bin/dh_auto_test
  └─make,251831 -j2 check VERBOSE=1

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#963546: meson: autopkgtest failures

[Gianfranco Costamagna]

Hello,


> 
> Interesting, this might explain also why I cannot replicate it under a 
> pbuilder environment...
> Can we try to lower the ninja parallelism to see if the build ends correctly?
> I suspect this might be an issue with Debian too, in the near future (e.g. 
> new gcc-10 defaults)
> 

I asked in Ubuntu to move the meson autopkgtests to a machine with more ram 
memory, and
now the test passes.
The Ubuntu VMs have 1536MB of ram, probably not enough for the testsuite to 
pass.

I hope Debian won't have the same problem in the near future, but for now the 
problem in Ubuntu is solved.

G.

Processed: closing 960353

[Debian Bug Tracking System]

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

> close 960353
Bug #960353 [src:haskell-hindent] haskell-hindent: Failed to migrate to testing 
for too long
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: Bug#963682: booth: build-depends on removed package.

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 booth 1.0-174-gce9f821-1
Bug #963682 [booth.] booth: build-depends on removed package.
Warning: Unknown package 'booth.'
Bug reassigned from package 'booth.' to 'booth'.
No longer marked as found in versions 1.0-174-gce9f821-2.
Ignoring request to alter fixed versions of bug #963682 to the same values 
previously set
Bug #963682 [booth] booth: build-depends on removed package.
Marked as found in versions booth/1.0-174-gce9f821-1.

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

Bug#963682: booth: build-depends on removed package.

[Andrei POPESCU]

Control: reassign -1 booth 1.0-174-gce9f821-1

On Jo, 25 iun 20, 09:35:37, Peter Green wrote:
> Package: booth.
> Version: 1.0-174-gce9f821-2
> Severity: serious
> 
> Booth build-depends on libcrmservice-dev which is no longer built by the 
> pacemaker source package.
> It is still present in unstable as a cruft package but is completely gone 
> from testing.
> 
> Since libcrmservice-dev was a transitional package that was empty (apart from 
> a few Debian
> documenation files) it should be safe to simply change the build-dependency 
> to pacemaker-dev.
> The attached debdiff does that.
> 
> If I get no response to this bug report I will likely upload the change as a 
> NMU.
> 

> diff -Nru booth-1.0-174-gce9f821/debian/changelog 
> booth-1.0-174-gce9f821/debian/changelog
> --- booth-1.0-174-gce9f821/debian/changelog   2020-04-18 12:23:20.0 
> +
> +++ booth-1.0-174-gce9f821/debian/changelog   2020-06-25 08:26:43.0 
> +
> @@ -1,3 +1,11 @@
> +booth (1.0-174-gce9f821-2.1) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Change build-dependency from libcrmservice-dev to pacemaker-dev
> +(Closes: ??)
> +
> + -- Peter Michael Green   Thu, 25 Jun 2020 08:26:43 
> +
> +
>  booth (1.0-174-gce9f821-2) unstable; urgency=medium
>  
>* d/patches: try to fix flaky lock file test
> diff -Nru booth-1.0-174-gce9f821/debian/control 
> booth-1.0-174-gce9f821/debian/control
> --- booth-1.0-174-gce9f821/debian/control 2020-04-18 12:17:18.0 
> +
> +++ booth-1.0-174-gce9f821/debian/control 2020-06-25 08:26:43.0 
> +
> @@ -10,7 +10,7 @@
>   debhelper-compat (= 12),
>   docbook-xml,
>   docbook-xsl,
> - libcrmservice-dev,
> + pacemaker-dev,
>   libgcrypt20-dev,
>   libglib2.0-dev,
>   libplumb2-dev,


-- 
Looking after bugs filled against unknown packages


signature.asc
Description: PGP signature