Bug#923500: snapd: non-classic snap not confined

[intrigeri]

Hi,

James Henstridge (2021-02-16):
> 2. As for why Debian is not being considered for "full" support,
> I suspect this is down to the out-of-tree patches to enable access
> control for unix domain sockets. This will likely resolve itself
> when snapd moves to use the new AppArmor 3.0 network features (which
> does not rely on out of tree patches).

FTR, according to Jamie Strandboge [1], even with AppArmor 3 some
network features are missing until support is added to the upstream
kernel:

Jamie Strandboge  (Mon, 5 Oct 2020 12:42:50 -0500):
> AppArmor 3 allows use of networkv8 rules (ie, what is in the upstream
> kernel) so apparmor 3 in Debian would allow for this to work.
>
> The upstream kernel does not yet support AF_UNIX rules, so anonymous
> sockets, abstract sockets and dbus won't be available. Work has picked
> up to get this into the upstream kernel (perhaps 5.11).

[1] https://bugs.debian.org/712451#126

Cheers!

Bug#982890: marked as done (php-redis: Should depend on php-igbinary)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 07:49:52 +
with message-id 
and subject line Bug#982890: fixed in php-redis 5.3.2+4.3.0-2+deb11u1
has caused the Debian Bug report #982890,
regarding php-redis: Should depend on php-igbinary
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.)


-- 
982890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-memcached
Version: 3.1.5+2.2.0-5
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: grun...@ololo.cc

Dear Maintainer,

Package php-memcached in version 3.1.5+2.2.0-5 no longer depends on php-
igbinary and php-msgpack, but in fact it does, despite ldd could say.
Dependencies of previous version, 3.1.4+2.2.0-1+b1, specified in deb
package, are fine.

If one tries to load this module without that dependands, it would lead
to following errors:

PHP Warning:  PHP Startup: Unable to load dynamic library 'memcached.so'
(tried: /usr/lib/php/20190902/memcached.so
(/usr/lib/php/20190902/memcached.so:
undefined symbol: php_msgpack_serialize),
/usr/lib/php/20190902/memcached.so.so
(/usr/lib/php/20190902/memcached.so.so: cannot open shared object file:
No such file or directory)) in Unknown on line 0

in case of php-msgpack absence, and

PHP Warning:  PHP Startup: Unable to load dynamic library 'memcached.so'
(tried: /usr/lib/php/20190902/memcached.so
(/usr/lib/php/20190902/memcached.so:
undefined symbol: igbinary_serialize), /usr/lib/php/20190902/memcached.so.so
(/usr/lib/php/20190902/memcached.so.so: cannot open shared object file:
No such file or directory)) in Unknown on line 0

in case of php-igbinary absence.

So this module would not load and would not be available for PHP.

If one installs such dependencies manually, module would work fine.

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

Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages php-memcached depends on:
ii  libapache2-mod-php7.4 [phpapi-20190902]  7.4.15-3
ii  libc62.31-9
ii  libmemcached11   1.0.18-4.2
ii  libsasl2-2   2.1.27+dfsg-2.1
hi  php-common   2:76
ii  php7.4-cli [phpapi-20190902] 7.4.15-3
ii  ucf  3.0043
ii  zlib1g   1:1.2.11.dfsg-2

php-memcached recommends no packages.

php-memcached suggests no packages.
--- End Message ---
--- Begin Message ---
Source: php-redis
Source-Version: 5.3.2+4.3.0-2+deb11u1
Done: Ondřej Surý 

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated php-redis package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 16 Feb 2021 08:33:23 +0100
Source: php-redis
Architecture: source
Version: 5.3.2+4.3.0-2+deb11u1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PECL Maintainers 
Changed-By: Ondřej Surý 
Closes: 982890
Changes:
 php-redis (5.3.2+4.3.0-2+deb11u1) unstable; urgency=medium
 .
   * Explicitly add php-igbinary to Depends for dh-php (<< 2.0)
 (Closes: #982890)
Checksums-Sha1:
 7f2fffe71f145eb82f0a6467387c7c32e320dda6 2197 
php-redis_5.3.2+4.3.0-2+deb11u1.dsc
 7877022f5f238625a2cbd5f6683052d91b530585 5528 
php-redis_5.3.2+4.3.0-2+deb11u1.debian.tar.xz
 7fd1cfc09b1ad754dbc523ce10af78f558afa0fb 7594 
php-redis_5.3.2+4.3.0-2+deb11u1_amd64.buildinfo
Checksums-Sha256:
 

Bug#982886: marked as done (php-memcached: Should depend on php-igbinary and php-msgpack)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 07:49:41 +
with message-id 
and subject line Bug#982886: fixed in php-memcached 3.1.5+2.2.0-5+deb11u1
has caused the Debian Bug report #982886,
regarding php-memcached: Should depend on php-igbinary and php-msgpack
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.)


-- 
982886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-memcached
Version: 3.1.5+2.2.0-5
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: grun...@ololo.cc

Dear Maintainer,

Package php-memcached in version 3.1.5+2.2.0-5 no longer depends on php-
igbinary and php-msgpack, but in fact it does, despite ldd could say.
Dependencies of previous version, 3.1.4+2.2.0-1+b1, specified in deb
package, are fine.

If one tries to load this module without that dependands, it would lead
to following errors:

PHP Warning:  PHP Startup: Unable to load dynamic library 'memcached.so'
(tried: /usr/lib/php/20190902/memcached.so
(/usr/lib/php/20190902/memcached.so:
undefined symbol: php_msgpack_serialize),
/usr/lib/php/20190902/memcached.so.so
(/usr/lib/php/20190902/memcached.so.so: cannot open shared object file:
No such file or directory)) in Unknown on line 0

in case of php-msgpack absence, and

PHP Warning:  PHP Startup: Unable to load dynamic library 'memcached.so'
(tried: /usr/lib/php/20190902/memcached.so
(/usr/lib/php/20190902/memcached.so:
undefined symbol: igbinary_serialize), /usr/lib/php/20190902/memcached.so.so
(/usr/lib/php/20190902/memcached.so.so: cannot open shared object file:
No such file or directory)) in Unknown on line 0

in case of php-igbinary absence.

So this module would not load and would not be available for PHP.

If one installs such dependencies manually, module would work fine.

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

Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages php-memcached depends on:
ii  libapache2-mod-php7.4 [phpapi-20190902]  7.4.15-3
ii  libc62.31-9
ii  libmemcached11   1.0.18-4.2
ii  libsasl2-2   2.1.27+dfsg-2.1
hi  php-common   2:76
ii  php7.4-cli [phpapi-20190902] 7.4.15-3
ii  ucf  3.0043
ii  zlib1g   1:1.2.11.dfsg-2

php-memcached recommends no packages.

php-memcached suggests no packages.
--- End Message ---
--- Begin Message ---
Source: php-memcached
Source-Version: 3.1.5+2.2.0-5+deb11u1
Done: Ondřej Surý 

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated php-memcached package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 16 Feb 2021 08:33:12 +0100
Source: php-memcached
Architecture: source
Version: 3.1.5+2.2.0-5+deb11u1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PECL Maintainers 
Changed-By: Ondřej Surý 
Closes: 982886
Changes:
 php-memcached (3.1.5+2.2.0-5+deb11u1) unstable; urgency=medium
 .
   * Explicitly add php-igbinary and php-msgpack to Depends for
 dh-php (<< 2.0) (Closes: #982886)
Checksums-Sha1:
 fcd17847833e5c7388986a9c97a8cf65d2260a1b 2286 
php-memcached_3.1.5+2.2.0-5+deb11u1.dsc
 3f267caa740dbf8b7f6cb9a7e0bbfc1b3d36516a 14204 
php-memcached_3.1.5+2.2.0-5+deb11u1.debian.tar.xz
 e6c50207b8569cdb9d19723c39b4768bd7310ec1 7984 
php-memcached_3.1.5+2.2.0-5+deb11u1_amd64.buildinfo

Bug#982886: php-memcached: Should depend on php-igbinary and php-msgpack

[Ondřej Surý]

Done. Fixed php-redis, php-memcached, php-solr, php-pecl-http, and php-msgpack 
in one go.

Thanks for noticing this and sorry for the trouble,
Ondrej
--
Ondřej Surý (He/Him)
ond...@sury.org

> On 15. 2. 2021, at 20:32, Grigory Ivanov  wrote:
> 
> Package: php-memcached
> Version: 3.1.5+2.2.0-5
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: grun...@ololo.cc
> 
> Dear Maintainer,
> 
> Package php-memcached in version 3.1.5+2.2.0-5 no longer depends on php-
> igbinary and php-msgpack, but in fact it does, despite ldd could say.
> Dependencies of previous version, 3.1.4+2.2.0-1+b1, specified in deb
> package, are fine.
> 
> If one tries to load this module without that dependands, it would lead
> to following errors:
> 
> PHP Warning:  PHP Startup: Unable to load dynamic library 'memcached.so'
> (tried: /usr/lib/php/20190902/memcached.so
> (/usr/lib/php/20190902/memcached.so:
> undefined symbol: php_msgpack_serialize),
> /usr/lib/php/20190902/memcached.so.so
> (/usr/lib/php/20190902/memcached.so.so: cannot open shared object file:
> No such file or directory)) in Unknown on line 0
> 
> in case of php-msgpack absence, and
> 
> PHP Warning:  PHP Startup: Unable to load dynamic library 'memcached.so'
> (tried: /usr/lib/php/20190902/memcached.so
> (/usr/lib/php/20190902/memcached.so:
> undefined symbol: igbinary_serialize), /usr/lib/php/20190902/memcached.so.so
> (/usr/lib/php/20190902/memcached.so.so: cannot open shared object file:
> No such file or directory)) in Unknown on line 0
> 
> in case of php-igbinary absence.
> 
> So this module would not load and would not be available for PHP.
> 
> If one installs such dependencies manually, module would work fine.
> 
> -- System Information:
> Debian Release: bullseye/sid
>  APT prefers stable-updates
>  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'),
> (500, 'stable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE
> not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages php-memcached depends on:
> ii  libapache2-mod-php7.4 [phpapi-20190902]  7.4.15-3
> ii  libc62.31-9
> ii  libmemcached11   1.0.18-4.2
> ii  libsasl2-2   2.1.27+dfsg-2.1
> hi  php-common   2:76
> ii  php7.4-cli [phpapi-20190902] 7.4.15-3
> ii  ucf  3.0043
> ii  zlib1g   1:1.2.11.dfsg-2
> 
> php-memcached recommends no packages.
> 
> php-memcached suggests no packages.
> 



signature.asc
Description: Message signed with OpenPGP

Bug#982757: firmware-brcm80211: [REGRESSION] brcm/brcmfmac43340-sdio.bin missing in sid (20210208-1)

[maximilian attems]

severity 982757 critical
stop

> Version: 20201218-3
> Severity: normal

thank you for the report, oh boy this one is opens a can of trouble.
It seems I was blissfully unaware that the Debian packaging did not
take into account the symlinks of upstream linux-firmware WHENCE file.
So this means we are missing a *lot* - all the symlinks!?!?
 
> after latest update wifi stopped working and I saw that 
> brcm/brcmfmac43340-sdio.bin was missing,

right it was replaced by newer cypress version and there should be
a symlink of that guy from the older name:

 Link: brcm/brcmfmac43340-sdio.bin -> ../cypress/cyfmac43340-sdio.bin

Could you please test latest 2021 upstream package with this symlink?

kind regards,

-- 
maks


signature.asc
Description: PGP signature

Processed: Re: Bug#982757: firmware-brcm80211: [REGRESSION] brcm/brcmfmac43340-sdio.bin missing in sid (20210208-1)

[Debian Bug Tracking System]

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

> severity 982757 critical
Bug #982757 [firmware-brcm80211] firmware-brcm80211: [REGRESSION] 
brcm/brcmfmac43340-sdio.bin missing in sid (20210208-1)
Severity set to 'critical' from 'normal'
> stop
Stopping processing here.

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

Bug#982766: Chai no more depends on node-uglifyjs-webpack-plugin

[Yadd]

Hi,

for the record, I removed build dependency to
node-uglifyjs-webpack-plugin from chai (src:node-chai). The browser
package is no more minified but this is not important: libjs-chai has no
reverse dependency.

Cheers,
Xavier

Bug#982886: php-memcached: Should depend on php-igbinary and php-msgpack

[Ondřej Surý]

Right, I have a new mechanism for defining the dependencies in dh-php >= 2.0, 
but I wasn’t able to finish it in time for bullseye, but the memcached has been 
already updated.

I’ll fix this and other affected PECL packages today.

Thanks for the report.

Ondřej 
--
Ondřej Surý  (He/Him)

> On 15. 2. 2021, at 21:24, Grigory Ivanov  wrote:
> 
> Package: php-memcached
> Version: 3.1.5+2.2.0-5
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: grun...@ololo.cc
> 
> Dear Maintainer,
> 
> Package php-memcached in version 3.1.5+2.2.0-5 no longer depends on php-
> igbinary and php-msgpack, but in fact it does, despite ldd could say.
> Dependencies of previous version, 3.1.4+2.2.0-1+b1, specified in deb
> package, are fine.
> 
> If one tries to load this module without that dependands, it would lead
> to following errors:
> 
> PHP Warning:  PHP Startup: Unable to load dynamic library 'memcached.so'
> (tried: /usr/lib/php/20190902/memcached.so
> (/usr/lib/php/20190902/memcached.so:
> undefined symbol: php_msgpack_serialize),
> /usr/lib/php/20190902/memcached.so.so
> (/usr/lib/php/20190902/memcached.so.so: cannot open shared object file:
> No such file or directory)) in Unknown on line 0
> 
> in case of php-msgpack absence, and
> 
> PHP Warning:  PHP Startup: Unable to load dynamic library 'memcached.so'
> (tried: /usr/lib/php/20190902/memcached.so
> (/usr/lib/php/20190902/memcached.so:
> undefined symbol: igbinary_serialize), /usr/lib/php/20190902/memcached.so.so
> (/usr/lib/php/20190902/memcached.so.so: cannot open shared object file:
> No such file or directory)) in Unknown on line 0
> 
> in case of php-igbinary absence.
> 
> So this module would not load and would not be available for PHP.
> 
> If one installs such dependencies manually, module would work fine.
> 
> -- System Information:
> Debian Release: bullseye/sid
>  APT prefers stable-updates
>  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'),
> (500, 'stable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE
> not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages php-memcached depends on:
> ii  libapache2-mod-php7.4 [phpapi-20190902]  7.4.15-3
> ii  libc62.31-9
> ii  libmemcached11   1.0.18-4.2
> ii  libsasl2-2   2.1.27+dfsg-2.1
> hi  php-common   2:76
> ii  php7.4-cli [phpapi-20190902] 7.4.15-3
> ii  ucf  3.0043
> ii  zlib1g   1:1.2.11.dfsg-2
> 
> php-memcached recommends no packages.
> 
> php-memcached suggests no packages.
> 

Bug#982786: marked as done (growlight: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 04:03:45 +
with message-id 
and subject line Bug#982786: fixed in growlight 1.2.30-1
has caused the Debian Bug report #982786,
regarding growlight: autopkgtest regression
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.)


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

https://ci.debian.net/data/autopkgtest/testing/amd64/g/growlight/10443325/log.gz

...
autopkgtest [11:04:28]: test blockdev: echo "blockdev -v" | growlight-readline 
-v
autopkgtest [11:04:28]: test blockdev: [---
growlight 1.2.27
libblkid 2.36.1, libpci 0x30700, libdm 1.02.175 (2021-01-08)
No ZFS support in this build.
Watching /sys/class/block/ on fd 1
scanning /sys/class/block/ on 8...
sdd -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:3/end_device-0:3/target0:0:3/0:0:3:0/block/sdd
sdf -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:5/end_device-0:5/target0:0:5/0:0:5:0/block/sdf
Numa node 1 (/sys/devices/pci:80/:80:01.0/:82:00.0//numa_node)
Controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3
Controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3
Model: Micron_5100_MTFD revision U037 S/N n/a type 0
Model: Micron_5100_MTFD revision U037 S/N n/a type 0
Partition 1 at sdd1
Partition 1 at sdf1
Couldn't open /dev/sdd (No such file or directory)
Couldn't open /dev/sdf (No such file or directory)
sdg3 -> 
../../devices/pci:00/:00:1f.2/ata5/host5/target5:0:0/5:0:0:0/block/sdg/sdg3
sdb -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:1/end_device-0:1/target0:0:1/0:0:1:0/block/sdb
sdg -> 
../../devices/pci:00/:00:1f.2/ata5/host5/target5:0:0/5:0:0:0/block/sdg
sdg1 -> 
../../devices/pci:00/:00:1f.2/ata5/host5/target5:0:0/5:0:0:0/block/sdg/sdg1
Numa node 0 (/sys/devices/pci:00/:00:1f.2//numa_node)
/sys/class/block/ blocks on 15 devices for up to 1s
Controller: Intel Corporation C610/X99 series chipset 6-Port SATA 
Controller [AHCI mode]
Not recursing on partition sdg3
Controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3
Controller: Intel Corporation C610/X99 series chipset 6-Port SATA 
Controller [AHCI mode]
Not recursing on partition sdg1
Model: Micron_5100_MTFD revision U037 S/N n/a type 0
Controller: Intel Corporation C610/X99 series chipset 6-Port SATA 
Controller [AHCI mode]
sdf1 -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:5/end_device-0:5/target0:0:5/0:0:5:0/block/sdf/sdf1
dm-0 -> ../../devices/virtual/block/dm-0
Controller: Virtual devices
sde -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:4/end_device-0:4/target0:0:4/0:0:4:0/block/sde
Partition 1 at sdb1
Model: INTEL SSDSCKJB15 revision 0121 S/N n/a type 0
sdd1 -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:3/end_device-0:3/target0:0:3/0:0:3:0/block/sdd/sdd1
Couldn't open /dev/sdb (No such file or directory)
sdc1 -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:2/end_device-0:2/target0:0:2/0:0:2:0/block/sdc/sdc1
Partition 3 at sdg3
sdb1 -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:1/end_device-0:1/target0:0:1/0:0:1:0/block/sdb/sdb1
sdc -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:2/end_device-0:2/target0:0:2/0:0:2:0/block/sdc
Couldn't get blkid probe for /dev/dm-0 (No such file or directory), retrying...
sde1 -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:4/end_device-0:4/target0:0:4/0:0:4:0/block/sde/sde1
Partition 1 at sdg1
sda -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:0/end_device-0:0/target0:0:0/0:0:0:0/block/sda
sdg2 -> 
../../devices/pci:00/:00:1f.2/ata5/host5/target5:0:0/5:0:0:0/block/sdg/sdg2
Partition 2 at sdg2
Controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3
Couldn't open /dev/sdg (No such file or directory)
Model: Micron_5100_MTFD revision U037 S/N n/a type 0
Controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3
Not recursing on partition sdf1
Controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3
Controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3
Model: Micron_5100_MTFD revision U037 S/N n/a type 0
Not recursing on partition sdd1

Bug#982503: marked as done (neurodebian: Build-Depends on xcftools which should not be released with bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 03:34:26 +
with message-id 
and subject line Bug#982503: fixed in neurodebian 0.41.0
has caused the Debian Bug report #982503,
regarding neurodebian: Build-Depends on xcftools which should not be released 
with 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.)


-- 
982503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: neurodebian
Version: 0.40.1
Severity: serious
Justification: Depends on xcftools unfit for bullseye release
X-Debbugs-Cc: car...@debian.org,t...@security.debian.org
Control: block 982499 by -1

neurodebian Build-Depends on xcftools which ideally should not be
released with bullseye. As it looks xcftools is used for calling
xcf2png. This can be equivalently be done with convert from
imagemagick, can you please check to switch away from xcftools for
this conversions?

game-data-packager for instance has already the casing to use convert
if xcf2png is not available. So you could do similarly.

Ivo De Decker confirmed to fill those bugs with serious severity to
make it possible to release bullseye without xcftools:

< ivodd> carnil: I suggest you file serious bugs against the 3 rdeps asking 
them to switch
< ivodd> if it's as easy as it looks from the bug report, it shouldn't be a big 
issue
< ivodd> if it turn out it's more complicated, we can still revisit the issue

if it turns out to not be feasible we later on can revisit the severity and
postpone it for bookworm.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: neurodebian
Source-Version: 0.41.0
Done: Yaroslav Halchenko 

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

Debian distribution maintenance software
pp.
Yaroslav Halchenko  (supplier of updated neurodebian 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Feb 2021 22:04:45 -0500
Source: neurodebian
Architecture: source
Version: 0.41.0
Distribution: unstable
Urgency: medium
Maintainer: NeuroDebian Team 
Changed-By: Yaroslav Halchenko 
Closes: 855392 925492 972742 982503
Changes:
 neurodebian (0.41.0) unstable; urgency=medium
 .
   [ Juhani Numminen ]
   * Replace xcf2png (xcftools) with convert (imagemagick). (Closes: #982503)
 .
   [ Yaroslav Halchenko ]
   * Python3 and recent sphinx compatibility fixes throughout helper scripts
   * Fixed up elderly sphinx/blog/2011/2011-12-12_schroot_fslview.rst to
 point to squeeze not stable. Thanks Paul Wise for the attention to detail
 (Closes: #972742)
   * debian/po/sv.po - minor updates. Thanks Jonatan Nyberg
 (Closes: #855392, #925492) - took version of #925492
Checksums-Sha1:
 4aa44f5bf01554c1084ee65bd6d2d47d42d7a32a 2136 neurodebian_0.41.0.dsc
 9dd1c55f73ada42d870596736157ba36bb461a5f 8318388 neurodebian_0.41.0.tar.xz
 83ccc786a656a17e7c3921c45156a2336dfafc60 11769 
neurodebian_0.41.0_source.buildinfo
Checksums-Sha256:
 16e9b1b9b1b172b636a11dd70de5de544e618b59d2d077f926032d67cdf5c770 2136 
neurodebian_0.41.0.dsc
 95f3c3109e4a65094b7478529e58dd316aed9fb9d7c7daa3bd15e6b47c68bee1 8318388 
neurodebian_0.41.0.tar.xz
 4feab0419c25f6207ef63ee9c61fdc879e8cc48c8a5fea06e01908fb3d828a45 11769 
neurodebian_0.41.0_source.buildinfo
Files:
 be793dfd82e6e9fa2f1b6bba2614210b 2136 science optional neurodebian_0.41.0.dsc
 acef1cdbb5f93086c5f37eb0242e0707 8318388 science optional 
neurodebian_0.41.0.tar.xz
 965d5c33bb2f5799747399135c0d2ed7 11769 science optional 
neurodebian_0.41.0_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEExbkF8OjZ/ZZo/zZvot4jUGLaM/oFAmArNmEACgkQot4jUGLa
M/o/9w/+KhZkzyrdTZ//kssRaArFn0zIZojoXP860lDOfCRJCM7tmepcFxUiZF1f
DOvjAgpu81e51D9UoUwBYEsL9iaaejBpPjwTKek0dVE9CrT6VOr/JIhYaNbjmFYk
3TYkZ7ZMW6W+C0d19nn5JZJgtjtkUbuCJQg1dG97asaNoRePqfhDAORBcY5D7wAz
FxYkYTig0v78566msHdXNBJhc94ntGRcOYDEQBhm4yyZpIAihRs6YvrQBzUUiv1j
ciR1yGh47TcSY39f1XrK74Sf+Zsl54MwVJdcVdNTUoR+P6kPZYroj6J2MYmfOqPv
wvocXI6hzGikr2MPVoFKLzWO9HO7BCYSkNICMVwmnJ0CRsCMikrOkpY7bMzgSb+Y

Bug#982786: growlight: autopkgtest regression

[Nick Black]

alright, with 1.2.30 (1.2.29 was never released), we pass the
autopkgtests, huzzah.

Processed: Bug#982503 marked as pending in neurodebian

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #982503 [src:neurodebian] neurodebian: Build-Depends on xcftools which 
should not be released with bullseye
Ignoring request to alter tags of bug #982503 to the same tags previously set

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

Bug#982503: marked as pending in neurodebian

[Yaroslav Halchenko]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/neurodebian-team/neurodebian/-/commit/6480c19a1e13b72ead571230019995fc55c1b4f9


Merge remote-tracking branch 'salsa/master'

* salsa/master:
  Replace xcf2png (xcftools) with convert (imagemagick). (Closes: #982503)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/982503

Bug#923500: snapd: non-classic snap not confined

[James Henstridge]

I work on some parts of snapd at Canonical, so thought I'd weigh in.
I've got a few of points to add:

1. In the "snap debug confinement" output, it says
"policy:downgraded".  This indicates that snapd didn't detect enough
AppArmor features to enforce the full "strict confinement" sandbox, so
it switches to a permissive policy.  This was done because the
generated policies would sometimes malfunction on such systems.

We do have a system to prevent the downgrade on some systems where
we've verified that the sandbox behaves correctly:

https://github.com/snapcore/snapd/blob/cc398c14fe13c70d14b9cb2eef9873cd4b8eda1e/interfaces/apparmor/backend.go#L614-L629

I suspect current Debian probably meets this standard, so we should
add it to the exceptions list.

2. As for why Debian is not being considered for "full" support, I
suspect this is down to the out-of-tree patches to enable access
control for unix domain sockets.  This will likely resolve itself when
snapd moves to use the new AppArmor 3.0 network features (which does
not rely on out of tree patches).

3. Even on systems where the full strict confined sandbox is enabled,
acess to the root directory is granted in the base template:

https://github.com/snapcore/snapd/blob/3173439195f62eacd6493cd49f257480811ed7a7/interfaces/apparmor/template.go#L444-L445

Note however that the root directory as seen within a snap's sandbox
is not the same as the root directory of the host system.  Instead,
the contents of the "base snap" used by the snap.  In the case of the
"hello-world" snap, the base is "core".  For example, this is the
output on my system:

james@scruffy:/$ ls
bin   cdrom  etc   liblib64   lost+found  mnt  proc  run   snap  sys  usr
boot  devhome  lib32  libx32  media   opt  root  sbin  srv   tmp  var
james@scruffy:/$ snap run --shell hello-world
To run a command as administrator (user "root"), use "sudo ".
See "man sudo_root" for details.

james@scruffy:/$ ls
bin   dev  home  lib64meta  opt   root  sbinsrv  tmp  var
boot  etc  lib mediamnt   proc  run   snapsys  usr  writable

You should find that the non-AppArmor parts of the sandbox are still in effect.

James.

Processed: Bug#982503 marked as pending in neurodebian

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #982503 [src:neurodebian] neurodebian: Build-Depends on xcftools which 
should not be released with bullseye
Ignoring request to alter tags of bug #982503 to the same tags previously set

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

Bug#982503: marked as pending in neurodebian

[Yaroslav Halchenko]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/neurodebian-team/neurodebian/-/commit/d0e0f642ed2010677d98f23253afad5097de7ec1


Merge branch 'rm-xcftools' into 'master'

Replace xcf2png (xcftools) with convert (imagemagick). (Closes: #982503)

See merge request neurodebian-team/neurodebian!1


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/982503

Bug#982503: marked as pending in neurodebian

[Yaroslav Halchenko]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/neurodebian-team/neurodebian/-/commit/34808c4aa5c77d811234d379470772d2a8355049


Replace xcf2png (xcftools) with convert (imagemagick). (Closes: #982503)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/982503

Processed: Bug#982503 marked as pending in neurodebian

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #982503 [src:neurodebian] neurodebian: Build-Depends on xcftools which 
should not be released with bullseye
Added tag(s) pending.

-- 
982503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982503
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:

> forwarded 982699 https://github.com/intake/intake/issues/550
Bug #982699 [src:intake] intake: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p 3.9 returned exit code 13
Set Bug forwarded-to-address to 'https://github.com/intake/intake/issues/550'.
>
End of message, stopping processing here.

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

Bug#982786: growlight: autopkgtest regression

[Nick Black]

not so fast! while this does indeed fix the segfault when run
without TERM, i still get an autopkgtest failure, this one
tracked down to stdout being redirected =[. so i'm gonna address
that as well. how embarrassing.

Bug#982786: growlight: autopkgtest regression

[Nick Black]

Here's the upstream bug: https://github.com/dankamongmen/growlight/issues/139
Here's the (obvious, trivial) fix:
https://github.com/dankamongmen/growlight/commit/297f487a8be84441ff75a22b5fa63305931cae70

A real brown-bagger =[.

I'm going to cut 1.2.29 and upload it to unstable. If I ought
prepare this patch as a debian patch for testing, as said, I can
do that as well. Otherwise, I'm perfectly content to let this
flow through unstable->testing.

Bug#982623: marked as done (apktool needs source-only upload for testing migration)

[Debian Bug Tracking System]

Your message dated Mon, 15 Feb 2021 23:33:25 +
with message-id 
and subject line Bug#982623: fixed in apktool 2.5.0+dfsg.1-2
has caused the Debian Bug report #982623,
regarding apktool needs source-only upload for testing migration
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.)


-- 
982623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apktool
Version: 2.5.0+dfsg.1-1
Severity: serious

https://tracker.debian.org/pkg/apktool

Migration status for apktool (2.4.1-1 to 2.5.0+dfsg.1-1): BLOCKED: 
Rejected/violates migration policy/introduces a regression
Issues preventing migration:
Not built on buildd: arch all binaries uploaded by chirayudes...@gmail.com, a 
new source-only upload is needed to allow migration
--- End Message ---
--- Begin Message ---
Source: apktool
Source-Version: 2.5.0+dfsg.1-2
Done: Markus Koschany 

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated apktool package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 15 Feb 2021 23:31:34 +0100
Source: apktool
Architecture: source
Version: 2.5.0+dfsg.1-2
Distribution: unstable
Urgency: medium
Maintainer: Android Tools Maintainers 

Changed-By: Markus Koschany 
Closes: 982623
Changes:
 apktool (2.5.0+dfsg.1-2) unstable; urgency=medium
 .
   * Source-only upload to allow the migration to testing. (Closes: #982623)
   * Declare compliance with Debian Policy 4.5.1.
Checksums-Sha1:
 53dd01a8ab8804bf2b845409614996dbf253cb0d 2408 apktool_2.5.0+dfsg.1-2.dsc
 86817b070b4107532ee0abee42ef188191d6077e 8788 
apktool_2.5.0+dfsg.1-2.debian.tar.xz
 c4819bab3484d48985702d422fc31b6b6d44e8bc 12332 
apktool_2.5.0+dfsg.1-2_amd64.buildinfo
Checksums-Sha256:
 83520b1d4361612afc1a5f03d381b90cd02f6a686483308f3a72376418245395 2408 
apktool_2.5.0+dfsg.1-2.dsc
 d8100ad85f5dd9a9e4cc66a4582ffa3c56a14f4b86e5aeca4623824762171fc5 8788 
apktool_2.5.0+dfsg.1-2.debian.tar.xz
 6ba1a81f915271c38b1ed779e73f7c179ec7d47862251fdeb932de9fbddd4c75 12332 
apktool_2.5.0+dfsg.1-2_amd64.buildinfo
Files:
 7ebd0724ca1ec7452448ffc25a51a410 2408 devel optional apktool_2.5.0+dfsg.1-2.dsc
 04ffe9a2bf8a6df8960688802117d1f7 8788 devel optional 
apktool_2.5.0+dfsg.1-2.debian.tar.xz
 b108429e96499b4070c7856305f9b150 12332 devel optional 
apktool_2.5.0+dfsg.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAmAq/OVfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkfAYQAJq0uuObREKs9TNS/q0r6+L74O0wSbhlR7xS
YhXTfZJMZLSNZMV++BcYk3WmSMKzhd14nQbKrpSfL0wGTYS/8J7TjaOZ7Q4Z5WQ1
Y1s8r6nwvjIYuITtFH57H3GOOe+zZRQ/ftYPhnbgcBggRMM+3kLJLl1495gt/KSM
mscLBFcPnnlJBuXgwCvs1yM00JtBo92fGXDLAkr3soYC4Gu1g0NnRfLMzQ138/8m
SU2pbNAdhcBQYY7n4AQT3HFsRD++Wunqlpc3Od1tNJQ9UCQ/he2hpSV6ua3NZKFm
NmOryAf/rZGgheznmItbrlKiJAJ6i8kzcH4Q9Yo1GVBNvMmo70sznvWo8atKPdfs
ejXP1ERKlOPMQ846SNUYEqqfJF2sVIfFDw9tJC2RrNsYR/u9l2JHc86+x9dTrord
d6kffUVeJPNB3ixXtvzYr1K6agw4OGDZ+g6w+PlxkvnryyPpc9k4kXdb1ipDLtk1
M6Rn+koIVmr5VUwt4T0X6ruR2RKRnGCHGCvpinmUZTdq2xwKC4aBzTk2A/pJ7HDd
4jK6FmD2+r7QJ3s+C2OX2pgyKdvh78XzV+LoxYYeRW223g2r5fOeqQzO6PCSegfo
BzGSG9v1Ntn3OwFtxuX2iXeWuWdfbLmqGn8tJEIB/qQ30QAsWU3lTkHk9QOePiMb
t2WdZP57
=q76C
-END PGP SIGNATURE End Message ---

Bug#982786: growlight: autopkgtest regression

[Nick Black]

Alright, I've got it locked down to the absence of a TERM
environment variable in the autopkgtest environment. If I run
the same command outside of autopkgtest, after running
`unset TERM`, i get the exact same failure.

So, this failure is IMHO definitely worth fixing, and I intend
to do so now, but this is also a very atypical configuration.
Users will generally have a TERM environment variable. I.e., I
do not think this would have been reported as a bug were it not
for the test. So hopefully this won't be a problem despite soft
freeze. I'm preparing the fix now.

Thanks to Antonio Terceiro and Daniel Leidert for their
assistance on debian-devel in working with autopkgtest/debci!
I really appreciate it.

Bug#982786: growlight: autopkgtest regression

[Nick Black]

I can now reproduce this locally, and expect to have a fix this
evening. I've looked over the rules for the Soft Freeze, and
understand that it'll be acceptable to cut a new upstream
release (I'm the upstream author) with this fix only (there have
been no other changes since this release), upload that to
unstable, and let it proceed (possibly slowly) to testing.

If I instead need to make a debian-specific patch against
1.2.28-1, and release it as 1.2.28-2, that's also fine.

Bug#980565: marked as done (php-enum: FTBFS with phpunit 9.5)

[Debian Bug Tracking System]

Your message dated Mon, 15 Feb 2021 22:18:26 +
with message-id 
and subject line Bug#980565: fixed in php-enum 4.4.0-1
has caused the Debian Bug report #980565,
regarding php-enum: FTBFS with phpunit 9.5
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.)


-- 
980565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-enum
Version: 4.2.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

php-enum/experimental recently started to FTBFS:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/php-enum-4.2.0'
php --define zend.assertions=1 /usr/bin/phpunit
PHPUnit 9.5.0 by Sebastian Bergmann and contributors.

  Warning - The configuration file did not pass validation!
  The following problems have been detected:

  Line 15:
  - Element 'phpunit', attribute 'syntaxCheck': The attribute 'syntaxCheck' is 
not allowed.
  - Element 'phpunit', attribute 'beStrictAboutTestSize': The attribute 
'beStrictAboutTestSize' is not allowed.

  Line 19:
  - Element 'filter': This element is not expected.

  Test results may not be as expected.


EE...E.  63 / 172 ( 36%)
... 126 / 172 ( 73%)
..  172 / 172 (100%)

Time: 00:00.014, Memory: 6.00 MB

There were 3 errors:

1) MabeEnumTest\EnumSerializableTraitTest::testSerializeSerializableEnum
Error: Call to undefined method 
MabeEnumTest\EnumSerializableTraitTest::assertInternalType()

/build/php-enum-4.2.0/tests/MabeEnumTest/EnumSerializableTraitTest.php:26

2) 
MabeEnumTest\EnumSerializableTraitTest::testUnserializeFirstWillHoldTheSameInstance
Error: Call to undefined method 
MabeEnumTest\EnumSerializableTraitTest::assertInternalType()

/build/php-enum-4.2.0/tests/MabeEnumTest/EnumSerializableTraitTest.php:35

3) MabeEnumTest\EnumSerializableTraitTest::testInheritence
Error: Call to undefined method 
MabeEnumTest\EnumSerializableTraitTest::assertInternalType()

/build/php-enum-4.2.0/tests/MabeEnumTest/EnumSerializableTraitTest.php:77

ERRORS!
Tests: 172, Assertions: 3440, Errors: 3.
make[1]: *** [debian/rules:10: override_dh_auto_test] Error 2
make[1]: Leaving directory '/build/php-enum-4.2.0'


Andreas


php-enum_4.2.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: php-enum
Source-Version: 4.4.0-1
Done: David Prévot 

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

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated php-enum package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 15 Feb 2021 17:35:28 -0400
Source: php-enum
Architecture: source
Version: 4.4.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Closes: 980565
Changes:
 php-enum (4.4.0-1) experimental; urgency=medium
 .
   [ Marco Pivetta ]
   * Upgraded to `phpunit/phpunit` 7.x (Closes: #980565)
 .
   [ Marc Bennewitz ]
   * Copyright (c) 2020
   * Require php ^7.1 or ^8.0
 .
   [ David Prévot ]
   * Document gbp import-orig usage
   * Update watch file format version to 4.
   * Set Rules-Requires-Root: no.
   * Update standards version to 4.5.1, no changes needed.
   * Use dh-sequence-phpcomposer instead of pkg-php-tools
   * Use debhelper-compat 13
   * Simplify override_dh_auto_test
   * Update copyright (years)
   * Install /u/s/p/autoloaders file
   * Install /u/s/p/overrides file
Checksums-Sha1:
 b9f836e4035fd143f50c2bfdf01d5f3a3cc87bc0 1700 php-enum_4.4.0-1.dsc
 7d0d869b8df11906043b41acf1340c47473de8a5 27472 php-enum_4.4.0.orig.tar.xz
 07857830bd3c26092a9805403970683df9a9278e 7888 php-enum_4.4.0-1.debian.tar.xz
 86193a56022e93d45ddf2b47eeb206712fdbea93 7426 php-enum_4.4.0-1_amd64.buildinfo
Checksums-Sha256:
 175c026256a8a33d4a666eddfb2a9969386db1e5b933e9406b0a16cc274098da 1700 
php-enum_4.4.0-1.dsc
 

Processed: cloning 982886, reassign 982886 to php-memcached ...

[Debian Bug Tracking System]

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

> clone 982886 -1
Bug #982886 [php-redis] php-redis: Should depend on php-igbinary
Bug 982886 cloned as bug 982890
> reassign 982886 php-memcached 3.1.5+2.2.0-5
Bug #982886 [php-redis] php-redis: Should depend on php-igbinary
Bug reassigned from package 'php-redis' to 'php-memcached'.
No longer marked as found in versions php-redis/5.3.2+4.3.0-2.
Ignoring request to alter fixed versions of bug #982886 to the same values 
previously set
Bug #982886 [php-memcached] php-redis: Should depend on php-igbinary
Marked as found in versions php-memcached/3.1.5+2.2.0-5.
> retitle 982886 php-memcached: Should depend on php-igbinary and php-msgpack
Bug #982886 [php-memcached] php-redis: Should depend on php-igbinary
Changed Bug title to 'php-memcached: Should depend on php-igbinary and 
php-msgpack' from 'php-redis: Should depend on php-igbinary'.
> thanks
Stopping processing here.

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

Processed: limit source to php-enum, tagging 980565

[Debian Bug Tracking System]

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

> limit source php-enum
Limiting to bugs with field 'source' containing at least one of 'php-enum'
Limit currently set to 'source':'php-enum'

> tags 980565 + pending
Bug #980565 [php-enum] php-enum: FTBFS with phpunit 9.5
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: Bug#982886: php-memcached: Should depend on php-igbinary and php-msgpack

[Debian Bug Tracking System]

Processing control commands:

> clone -1
Unknown command or malformed arguments to command.

> reassign -1 php-redis 5.3.2+4.3.0-2
Bug #982886 [php-memcached] php-memcached: Should depend on php-igbinary and 
php-msgpack
Bug reassigned from package 'php-memcached' to 'php-redis'.
No longer marked as found in versions php-memcached/3.1.5+2.2.0-5.
Ignoring request to alter fixed versions of bug #982886 to the same values 
previously set
Bug #982886 [php-redis] php-memcached: Should depend on php-igbinary and 
php-msgpack
Marked as found in versions php-redis/5.3.2+4.3.0-2.
> retitle -1 php-redis: Should depend on php-igbinary
Bug #982886 [php-redis] php-memcached: Should depend on php-igbinary and 
php-msgpack
Changed Bug title to 'php-redis: Should depend on php-igbinary' from 
'php-memcached: Should depend on php-igbinary and php-msgpack'.

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

Bug#982886: php-memcached: Should depend on php-igbinary and php-msgpack

[David Prévot]

Control: clone -1
Control: reassign -1 php-redis 5.3.2+4.3.0-2
Control: retitle -1 php-redis: Should depend on php-igbinary

Le Mon, Feb 15, 2021 at 10:32:19PM +0300, Grigory Ivanov a écrit :
> Package: php-memcached
> Version: 3.1.5+2.2.0-5
> Severity: grave
> Justification: renders package unusable
[…]
> Package php-memcached in version 3.1.5+2.2.0-5 no longer depends on php-
> igbinary and php-msgpack, but in fact it does, despite ldd could say.
> Dependencies of previous version, 3.1.4+2.2.0-1+b1, specified in deb
> package, are fine.

Ditto for php-redis and php-igbinary.

Regards

David


signature.asc
Description: PGP signature

Bug#982865: meson: diff for NMU version 0.57.0+really0.56.2-0.1

[Jussi Pakkanen]

On Mon, 15 Feb 2021 at 23:21, Sebastian Ramacher  wrote:

> Silently breaking hardening build flags of roughly 430 packages is
> definitely a large and disruptive change.

The rc was uploaded to experimental a week ago so that people could
use it to flush out problems like these. Apparently no-one did. Would
it be possible to set up an automatic gating system of some kind for
build-essential packages so these sort of things will never happen
again in the future?

Processed: cdparanoia: diff for NMU version 3.10.2+debian-13.1

[Debian Bug Tracking System]

Processing control commands:

> tags 982321 + pending
Bug #982321 [libcdparanoia-dev] libcdparanoia-dev: overly generic header name: 
/usr/include/utils.h
Added tag(s) pending.

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

Bug#982321: cdparanoia: diff for NMU version 3.10.2+debian-13.1

[Sebastian Ramacher]

Control: tags 982321 + pending

Dear maintainer,

I've prepared an NMU for cdparanoia (versioned as 3.10.2+debian-13.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru cdparanoia-3.10.2+debian/debian/changelog cdparanoia-3.10.2+debian/debian/changelog
--- cdparanoia-3.10.2+debian/debian/changelog	2018-01-30 06:28:04.0 +0100
+++ cdparanoia-3.10.2+debian/debian/changelog	2021-02-15 22:37:56.0 +0100
@@ -1,3 +1,11 @@
+cdparanoia (3.10.2+debian-13.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/libcdparanoia-dev.install: Do not install unused utils.h (Closes:
+#982321)
+
+ -- Sebastian Ramacher   Mon, 15 Feb 2021 22:37:56 +0100
+
 cdparanoia (3.10.2+debian-13) unstable; urgency=medium
 
   * debian/control: Update Vcs-*.
diff -Nru cdparanoia-3.10.2+debian/debian/libcdparanoia-dev.install cdparanoia-3.10.2+debian/debian/libcdparanoia-dev.install
--- cdparanoia-3.10.2+debian/debian/libcdparanoia-dev.install	2018-01-30 06:28:04.0 +0100
+++ cdparanoia-3.10.2+debian/debian/libcdparanoia-dev.install	2021-02-15 22:37:23.0 +0100
@@ -1,3 +1,3 @@
-/usr/include
+/usr/include/cdda_*
 /usr/lib/*/*.a
 /usr/lib/*/*.so


signature.asc
Description: PGP signature

Bug#982865: marked as done (meson: meson ignores CPPFLAGS)

[Debian Bug Tracking System]

Your message dated Mon, 15 Feb 2021 21:33:29 +
with message-id 
and subject line Bug#982865: fixed in meson 0.57.0+really0.56.2-0.1
has caused the Debian Bug report #982865,
regarding meson: meson ignores CPPFLAGS
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.)


-- 
982865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: meson
Version: 0.57.0-1

When packaging https://salsa.debian.org/yangfl-guest/sequeler , I got
blhc warning about CPPFLAGS missing (-D_FORTIFY_SOURCE=2) after
upgrading meson from 0.56.2-1 to 0.57.0-1.

Log attached.


meson-old
Description: Binary data


meson-new
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: meson
Source-Version: 0.57.0+really0.56.2-0.1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated meson package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 15 Feb 2021 21:17:44 +0100
Source: meson
Architecture: source
Version: 0.57.0+really0.56.2-0.1
Distribution: unstable
Urgency: medium
Maintainer: Jussi Pakkanen 
Changed-By: Sebastian Ramacher 
Closes: 982865
Changes:
 meson (0.57.0+really0.56.2-0.1) unstable; urgency=medium
 .
   * Revert to 0.56.2 (Closes: #982865)
 0.57.0 no longer honors CPPFLAGS and therefore silently drops
 -D_FORTIFY_SOURCE=2 during package builds.
Checksums-Sha1:
 ea6c74c324a9afa068ba81a8bffadb133a990584 3528 meson_0.57.0+really0.56.2-0.1.dsc
 a62199aca12eb69d4df7e828a8d11cc241ecff73 1794847 
meson_0.57.0+really0.56.2.orig.tar.gz
 e69a2a47fdbf33b97fbdf2bf66fed83e3ae2ce56 14308 
meson_0.57.0+really0.56.2-0.1.debian.tar.xz
Checksums-Sha256:
 0b5e1d5d0a9c898d24455da060db1dc1ab96a56839299693e934bbb62b73b233 3528 
meson_0.57.0+really0.56.2-0.1.dsc
 3cb8bdb91383f7f8da642f916e4c44066a29262caa499341e2880f010edb87f4 1794847 
meson_0.57.0+really0.56.2.orig.tar.gz
 44023ff687e6ed8832fd4922bc4f03e6ea6e9cb1a02c95d508b96b5139cbeed4 14308 
meson_0.57.0+really0.56.2-0.1.debian.tar.xz
Files:
 774cf1a037ace740bb31337a5b24d4bf 3528 devel optional 
meson_0.57.0+really0.56.2-0.1.dsc
 52b57dc223e39ae8d84f23a74296a89a 1794847 devel optional 
meson_0.57.0+really0.56.2.orig.tar.gz
 bcfea2e80226b3d5e81dd98a1a6ae2a5 14308 devel optional 
meson_0.57.0+really0.56.2-0.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmAq5RgACgkQafL8UW6n
GZOaTA/8DXXaFvbd14HoxIZPLJFJoAigi3ur6MCCfTwKR1N4zoiCnxrtgF9TFbHS
HVB5YYpZWdkdGW/GFeGJTkaUBOVosyL/pu7WvBjQdbuxQHmSC5xOAw/1Puxig7FK
Wbk12DldwcsH/19bsfgfqIW95h9Upt9Z2c5XOtlADjuZmZ3hKGHY6OzVXzy2l/oq
/HwgCaijgxc+OM9eYHXrKmF0k2ifK50/NXo9md70DT+nBrf95vdbaRBHNHBgNupm
0CRHnN12OMamZ/SYl8uR3E+yxdIp1ZYGpWms9bxMeA67b5Aalheccsj75TQypQVa
KQrIwNwRZMR4OFzE+ItriCCIfeU3/DE/8NTCn3qF2VGj7iM/VvDurLIn91z68eRW
l4qUnF/uZBV24DIVeGnq1Ex+dWQ/KBTJmidCUKWKiuSWbH6spPfoAPoq8vpYjHqF
6V0n1+DyH9gw4grLEe4ZDIepPlilsCWkwuFHYQAPx15t8URtKkSg9wOTyHU8MJ/e
tSXCefuyGxJCBZxq8WU9WgD+N92l78tEqyAiCvYtz3Z+0o6wBb3x3SUKhZovVbk2
iPhFaT9ZvZnHGshjUhwZiuwGu/s3xyjwT0zr3qyUwuSeSHsr2xMS1XP/+M0Ao9a7
MfpuyCQGIWWwxwiEYfbP7LwfSOJMAeJB+24eUs1VHTpDmeNdT3o=
=IidJ
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#982868: dpkg-cross generates erronous conflicts on like libc6-amd64:x32-i386-cross

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #982868 [dpkg-cross] dpkg-cross generates erronous conflicts on like 
libc6-amd64:x32-i386-cross
Added tag(s) patch.
> severity -1 serious
Bug #982868 [dpkg-cross] dpkg-cross generates erronous conflicts on like 
libc6-amd64:x32-i386-cross
Severity set to 'serious' from 'important'
> clone -1 -2
Bug #982868 [dpkg-cross] dpkg-cross generates erronous conflicts on like 
libc6-amd64:x32-i386-cross
Bug 982868 cloned as bug 982888
> reassign -2 src:cross-toolchain-base
Bug #982888 [dpkg-cross] dpkg-cross generates erronous conflicts on like 
libc6-amd64:x32-i386-cross
Bug reassigned from package 'dpkg-cross' to 'src:cross-toolchain-base'.
Ignoring request to alter found versions of bug #982888 to the same values 
previously set
Ignoring request to alter fixed versions of bug #982888 to the same values 
previously set

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

Processed: meson: diff for NMU version 0.57.0+really0.56.2-0.1

[Debian Bug Tracking System]

Processing control commands:

> tags 982865 + patch
Bug #982865 [meson] meson: meson ignores CPPFLAGS
Added tag(s) patch.

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

Bug#980211: libextractor: FTBFS (flaky tests)

[John Scott]

On Wed, 10 Feb 2021 21:02:47 +0100 Bertrand Marc 
wrote:
> Indeed, the original issue reported in this bug was fixed in 1.11-1.
> However, the general issue of flaky tests is still there: 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libextractor.html
> 
> Would you consider this bug as fixed?

I hadn't seen the failure at reproducible builds; indeed that's not
looking good.

I've built libextractor about a dozen times and can't reproduce the
test_html failure. Perhaps it happens so seldom that it won't happen on
a buildd, or is specific to the Reproducible Builds environment.

I personally regard the issue fixed, since the original issue was
mitigated and the test_html failure seems to be within other margins of
failure. Usually a second build is tried before an FTBFS bug is
warranted, and none of the applicable dependencies have had any change.

Note that the bug submitter was not filing a conventional FTBFS on
behalf of QA or the Release Team, but instead was concerned with the
librpm9 transition.

Let me know if there's anything particular I can do to help, and thanks
for your careful maintainership.


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

Bug#982886: php-memcached: Should depend on php-igbinary and php-msgpack

[Grigory Ivanov]

Package: php-memcached
Version: 3.1.5+2.2.0-5
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: grun...@ololo.cc

Dear Maintainer,

Package php-memcached in version 3.1.5+2.2.0-5 no longer depends on php-
igbinary and php-msgpack, but in fact it does, despite ldd could say.
Dependencies of previous version, 3.1.4+2.2.0-1+b1, specified in deb
package, are fine.

If one tries to load this module without that dependands, it would lead
to following errors:

PHP Warning:  PHP Startup: Unable to load dynamic library 'memcached.so'
(tried: /usr/lib/php/20190902/memcached.so
(/usr/lib/php/20190902/memcached.so:
undefined symbol: php_msgpack_serialize),
/usr/lib/php/20190902/memcached.so.so
(/usr/lib/php/20190902/memcached.so.so: cannot open shared object file:
No such file or directory)) in Unknown on line 0

in case of php-msgpack absence, and

PHP Warning:  PHP Startup: Unable to load dynamic library 'memcached.so'
(tried: /usr/lib/php/20190902/memcached.so
(/usr/lib/php/20190902/memcached.so:
undefined symbol: igbinary_serialize), /usr/lib/php/20190902/memcached.so.so
(/usr/lib/php/20190902/memcached.so.so: cannot open shared object file:
No such file or directory)) in Unknown on line 0

in case of php-igbinary absence.

So this module would not load and would not be available for PHP.

If one installs such dependencies manually, module would work fine.

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

Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages php-memcached depends on:
ii  libapache2-mod-php7.4 [phpapi-20190902]  7.4.15-3
ii  libc62.31-9
ii  libmemcached11   1.0.18-4.2
ii  libsasl2-2   2.1.27+dfsg-2.1
hi  php-common   2:76
ii  php7.4-cli [phpapi-20190902] 7.4.15-3
ii  ucf  3.0043
ii  zlib1g   1:1.2.11.dfsg-2

php-memcached recommends no packages.

php-memcached suggests no packages.

Processed: regina-rexx bug handling for debhelper migration

[Debian Bug Tracking System]

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

> clone 930005 -1
Bug #930005 {Done: Agustin Martin Domingo } [regina-rexx] 
regina-rexx: rexxutil error
Bug 930005 cloned as bug 982884
> retitle -1 regina-rexx: Consider migration to debhelper
Bug #982884 {Done: Agustin Martin Domingo } [regina-rexx] 
regina-rexx: rexxutil error
Changed Bug title to 'regina-rexx: Consider migration to debhelper' from 
'regina-rexx: rexxutil error'.
> reassign -1 src:regina-rexx
Bug #982884 {Done: Agustin Martin Domingo } [regina-rexx] 
regina-rexx: Consider migration to debhelper
Bug reassigned from package 'regina-rexx' to 'src:regina-rexx'.
No longer marked as found in versions regina-rexx/3.6-2.1 and 
regina-rexx/3.6-2.2.
Ignoring request to alter fixed versions of bug #982884 to the same values 
previously set
> found -1 regina-rexx/3.6-2.2
Bug #982884 {Done: Agustin Martin Domingo } 
[src:regina-rexx] regina-rexx: Consider migration to debhelper
Marked as found in versions regina-rexx/3.6-2.2 and reopened.
> severity -1 wishlist
Bug #982884 [src:regina-rexx] regina-rexx: Consider migration to debhelper
Severity set to 'wishlist' from 'grave'
> thanks
Stopping processing here.

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

Bug#982122: redis: experimental package OOMs s390x buildds

[Adam D. Barratt]

Hi Chris,

On Mon, 2021-02-15 at 18:28 +, Chris Lamb wrote:
> Ah, indeed, the failure mode means that the log never made it to
> > buildd.d.o.
> 
> Curious, not heard of that failure mode — is there someplace I can
> learn about that? No worries if not.

I'm not sure if it's documented, but in this case I think enough of the
system was unresponsive or killed to make the connection back to
buildd.d.o fail.

> > I've attached a copy of the log from zani.
> 
> Ah, thanks. Unfortunately, it does not point us straight to the
> solution. I note that you titled this bug "package OOMs" — I point
> this out because the "OOM" text the log is actually the name of the
> test. As in, here is tests/integration/corrupt-dump.tcl:
> 
[...]
> Do we have confirmation somewhere that the build is actually OOMing,
> rather than it just timing out on a test that was designed to test
> *for* an OOM condition. This OOM-related bug *should* be fixed by
> virtue of them adding the test to begin with (!) but if we can show
> that it is still OOMing, I suspect that upstream will be able to
> address it quickly.

I don't know how much context would be needed, but the machine
definitely OOMed:

Feb  3 20:45:22 zani/zani kernel: redis-server invoked oom-killer: 
gfp_mask=0x6000c0(GFP_KERNEL), nodemask=(null), order=0, oom_score_adj=0
Feb  3 20:45:22 zani/zani kernel: redis-server cpuset=/ mems_allowed=0
Feb  3 20:45:22 zani/zani kernel: CPU: 0 PID: 45952 Comm: redis-server Not 
tainted 4.19.0-14-s390x #1 Debian 4.19.171-2
Feb  3 20:45:22 zani/zani kernel: Hardware name: IBM 8561 LT1 400 (z/VM 7.1.0)
Feb  3 20:45:22 zani/zani kernel: Call Trace:
Feb  3 20:45:22 zani/zani kernel: ([<00113f2a>] show_stack+0x5a/0x78)
Feb  3 20:45:22 zani/zani kernel:  [<00802d1a>] dump_stack+0x8a/0xb8 
Feb  3 20:45:22 zani/zani kernel:  [<00800962>] dump_header+0x82/0x2c0 
Feb  3 20:45:22 zani/zani kernel:  [<002b46fe>] 
oom_kill_process+0xde/0x380 
Feb  3 20:45:22 zani/zani kernel:  [<002b550c>] 
out_of_memory+0x24c/0x3b8 
Feb  3 21:07:50 zani/zani kernel:  [<002bd032>] 
__alloc_pages_nodemask+0x10b2/0x1160 
Feb  3 21:07:50 zani/zani kernel:  [<0012b0c6>] 
page_table_alloc+0x15e/0x2c8 
Feb  3 21:07:50 zani/zani kernel:  [<002f8b76>] __pte_alloc+0x2e/0xf8 
Feb  3 21:07:50 zani/zani kernel:  [<002ff258>] 
__handle_mm_fault+0xfc0/0x11c0 
Feb  3 21:07:50 zani/zani kernel:  [<002ff584>] 
handle_mm_fault+0x12c/0x298 
Feb  3 21:07:50 zani/zani kernel:  [<00123a12>] 
do_dat_exception+0x182/0x440 
Feb  3 21:07:50 zani/zani kernel:  [<0080d9d4>] 
pgm_check_handler+0x190/0x1e4 
...
Feb  3 21:07:50 zani/zani kernel: sshd invoked oom-killer: 
gfp_mask=0x7080c0(GFP_KERNEL_ACCOUNT|__GFP_ZERO), nodemask=(null), order=2, 
oom_score_adj=-1000
Feb  3 21:07:50 zani/zani kernel: sshd cpuset=/ mems_allowed=0
Feb  3 21:07:50 zani/zani kernel: CPU: 0 PID: 1463 Comm: sshd Not tainted 
4.19.0-14-s390x #1 Debian 4.19.171-2
Feb  3 21:07:50 zani/zani kernel: Hardware name: IBM 8561 LT1 400 (z/VM 7.1.0)
Feb  3 21:07:50 zani/zani kernel: Call Trace:
Feb  3 21:07:50 zani/zani kernel: ([<00113f2a>] show_stack+0x5a/0x78)
Feb  3 21:07:50 zani/zani kernel:  [<00802d1a>] dump_stack+0x8a/0xb8 
Feb  3 21:07:50 zani/zani kernel:  [<00800962>] dump_header+0x82/0x2c0 
Feb  3 21:07:50 zani/zani kernel:  [<002b46fe>] 
oom_kill_process+0xde/0x380 
Feb  3 21:07:50 zani/zani kernel:  [<002b550c>] 
out_of_memory+0x24c/0x3b8 
Feb  3 21:07:50 zani/zani kernel:  [<002bd032>] 
__alloc_pages_nodemask+0x10b2/0x1160 
Feb  3 21:07:50 zani/zani kernel:  [<0013e414>] 
copy_process.part.4+0x24c/0x1fb0 
Feb  3 21:07:50 zani/zani kernel:  [<00140550>] _do_fork+0xf0/0x430 
Feb  3 21:07:50 zani/zani kernel:  [<001409ce>] sys_clone+0x3e/0x50 
Feb  3 21:07:50 zani/zani kernel:  [<0080d630>] system_call+0xd8/0x2bc 
...
Feb  3 21:07:50 zani/zani kernel: oom_reaper: reaped process 45952 
(redis-server), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
...
Feb  3 21:07:50 zani/zani kernel: sshd invoked oom-killer: 
gfp_mask=0x6200ca(GFP_HIGHUSER_MOVABLE), nodemask=(null), order=0, 
oom_score_adj=0
...
Feb  3 21:07:50 zani/zani kernel: munin-node invoked oom-killer: 
gfp_mask=0x6200ca(GFP_HIGHUSER_MOVABLE), nodemask=(null), order=0, 
oom_score_adj=0
...
Feb  3 21:07:50 zani/zani kernel: oom_reaper: reaped process 36654 (schroot), 
now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
...
Feb  3 21:07:50 zani/zani kernel: oom_reaper: reaped process 34994 (sbuild), 
now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
...
Feb  3 21:07:50 zani/zani kernel: oom_reaper: reaped process 1508 (syslog-ng), 
now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
...
Feb  3 21:07:50 zani/zani kernel: oom_reaper: reaped process 1863 (samhain), 
now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
...
Feb  3 21:07:50 zani/zani kernel: dpkg-buildpackage invoked oom-killer: 

Bug#930005: regina-rexx: rexxutil error

[Agustin Martin]

Package: regina-rexx
Version: 3.6-2.2
Severity: wishlist

El lun, 15 feb 2021 a las 13:40, Alen Zekulic () escribió:
>
> On Mon, Feb 15, 2021 at 13:16:58 +0100, Agustin Martin wrote:
>
> > I think I have something close to be ready for migration to debhelper.
>
> Me too. :)
>
> > ¿What do you prefer, a commit to salsa or a patch in the BTS?
>
> For now I prefer a patch in the BTS.

FIne, Alen,

I am filing a new bug report about this with wishlist severity, and
attaching a git patch with my changes. This is only about migration to
old-style debhelper from 3.5-2.2. It includes the migration itself and
making most of the package multiarch ready. As a bonus this fixes the
timestamp issues in #854294.

There is a pending thing about multiarch, the handling of
regina-config is not yet multiarch friendly. An $arch version should
be installed in an arch dependent dir and /usr/bin/regina-config be
made a wrapper to it, considering the architecture for which the
package is built (this is important e.g. when building for amd64/i386
from the other arch). Once I have something ready I will submit an
additional patch to this bug report, to be appplied after debhelper
migration changes.

Regards,

-- 
Agustin
From 389c9685789a9799477c09285c378b784f87bd51 Mon Sep 17 00:00:00 2001
From: Agustin Martin 
Date: Mon, 15 Feb 2021 20:29:39 +0100
Subject: [PATCH] Migrate to old-style debhelper from regina-rexx 3.6-2.2

* Migration to old-style debhelper. This also includes:
  - Make package multiarch.
  - Fix the timestamp issues in #854294.
* Remove autotools-dev Build-Dep, it is pulled by debhelper.

Signed-off-by: Agustin Martin 
---
 debian/control|  20 +-
 debian/libregina3-dev.install |   5 +
 debian/libregina3-dev.manpages|   1 +
 debian/libregina3.install |   2 +
 debian/md5_sums   |  19 --
 debian/patches/_Makefile.in_libdir.diff   |  32 +++
 .../patches/_Makefile.in_set-DESTDIR.diff |  17 ++
 debian/patches/_Makefile.in_sharedir.diff |  25 +++
 debian/patches/az-patch-01|  18 --
 debian/patches/series |   4 +
 debian/postinst   |   8 -
 debian/postrm |   8 -
 debian/postrm-dev |   8 -
 debian/regina-rexx.examples   |   2 +
 debian/regina-rexx.install|   5 +
 debian/regina-rexx.links  |   1 +
 debian/regina-rexx.manpages   |   3 +
 debian/rules  | 190 +++---
 18 files changed, 186 insertions(+), 182 deletions(-)
 create mode 100644 debian/libregina3-dev.install
 create mode 100644 debian/libregina3-dev.manpages
 create mode 100644 debian/libregina3.install
 delete mode 100644 debian/md5_sums
 create mode 100644 debian/patches/_Makefile.in_libdir.diff
 create mode 100644 debian/patches/_Makefile.in_set-DESTDIR.diff
 create mode 100644 debian/patches/_Makefile.in_sharedir.diff
 delete mode 100644 debian/postinst
 delete mode 100644 debian/postrm
 delete mode 100644 debian/postrm-dev
 create mode 100644 debian/regina-rexx.examples
 create mode 100644 debian/regina-rexx.install
 create mode 100644 debian/regina-rexx.links
 create mode 100644 debian/regina-rexx.manpages

diff --git a/debian/control b/debian/control
index 0413a05..bc66464 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,8 @@ Source: regina-rexx
 Section: libs
 Priority: optional
 Maintainer: Alen Zekulic 
-Build-Depends: libncurses5-dev, autotools-dev
+Build-Depends: libncurses5-dev,
+	   debhelper-compat (=12)
 Standards-Version: 4.4.1
 Homepage: http://regina-rexx.sourceforge.net/
 Vcs-Git: https://salsa.debian.org/debian/regina-rexx.git
@@ -10,7 +11,8 @@ Vcs-Browser: https://salsa.debian.org/debian/regina-rexx
 
 Package: libregina3
 Architecture: any
-Depends: ${shlibs:Depends}
+Depends: ${shlibs:Depends},
+	 ${misc:Depends} 
 Conflicts: regina3
 Replaces: regina3
 Description: Regina REXX interpreter, run-time library
@@ -25,9 +27,14 @@ Description: Regina REXX interpreter, run-time library
 Package: libregina3-dev
 Section: libdevel
 Architecture: any
-Depends: ${regver:Depends}, libc6-dev, cpp
-Conflicts: regina2-dev, regina3-dev
-Replaces: regina2-dev, regina3-dev
+Depends: ${misc:Depends},
+	 libregina3 (= ${binary:Version}),
+	 libc6-dev,
+	 cpp
+Conflicts: regina2-dev,
+	   regina3-dev
+Replaces: regina2-dev,
+	  regina3-dev
 Description: Regina REXX interpreter, development files
  Regina is an ANSI compliant REXX interpreter for multiple platforms.
  .
@@ -41,7 +48,8 @@ Description: Regina REXX interpreter, development files
 Package: regina-rexx
 Section: interpreters
 Architecture: any
-Depends: ${shlibs:Depends}
+Depends: ${shlibs:Depends},
+	 ${misc:Depends} 
 Description: Regina REXX interpreter
  Regina is an ANSI compliant REXX interpreter for 

Bug#982882: stellarium FTBFS on armel and mipsel

[Paul Gevers]

Source: stellarium
Version: 0.20.4-1
Severity: serious
Tags: ftbfs

Hi Maintainer,

Your last upload FTBFS on mipsel and armel.

Paul

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

make[3]: Leaving directory '/<>/obj-arm-linux-gnueabi'
[ 24%] Built target translations-stellarium
[ 24%] Generating ../../translations/stellarium-skycultures/zh_CN.qm
cd /<>/obj-arm-linux-gnueabi/po/stellarium-skycultures &&
/usr/lib/qt5/bin/lconvert -i
/<>/po/stellarium-skycultures/zh_CN.po -o
/<>/obj-arm-linux-gnueabi/translations/stellarium-skycultures/zh_CN.qm
[ 24%] Generating ../../translations/stellarium-skycultures/zh_HK.qm
cd /<>/obj-arm-linux-gnueabi/po/stellarium-skycultures &&
/usr/lib/qt5/bin/lconvert -i
/<>/po/stellarium-skycultures/zh_HK.po -o
/<>/obj-arm-linux-gnueabi/translations/stellarium-skycultures/zh_HK.qm
[ 24%] Generating ../../translations/stellarium-skycultures/zh_TW.qm
cd /<>/obj-arm-linux-gnueabi/po/stellarium-skycultures &&
/usr/lib/qt5/bin/lconvert -i
/<>/po/stellarium-skycultures/zh_TW.po -o
/<>/obj-arm-linux-gnueabi/translations/stellarium-skycultures/zh_TW.qm
make[3]: Leaving directory '/<>/obj-arm-linux-gnueabi'
[ 24%] Built target translations-stellarium-skycultures
make[2]: Leaving directory '/<>/obj-arm-linux-gnueabi'
make[1]: *** [Makefile:174: all] Error 2
make[1]: Leaving directory '/<>/obj-arm-linux-gnueabi'
dh_auto_build: error: cd obj-arm-linux-gnueabi && make -j4
"INSTALL=install --strip-program=true" VERBOSE=1 returned exit code 2
make: *** [debian/rules:7: build-arch] Error 25



OpenPGP_signature
Description: OpenPGP digital signature

Bug#952367: marked as done (uglifyjs: FTBFS: test failed)

[Debian Bug Tracking System]

Your message dated Mon, 15 Feb 2021 19:48:34 +
with message-id 
and subject line Bug#952367: fixed in uglifyjs 2.8.29-8
has caused the Debian Bug report #952367,
regarding uglifyjs: FTBFS: test failed
to be marked as done.

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

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


-- 
952367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uglifyjs
Version: 2.8.29-6
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 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 '/<>'
> NODE_PATH=lib nodejs test/run-tests.js \
>   
> *** Entering [compress]
> --- angular-inject.js
> Running test [ng_inject_defun]
> Running test [ng_inject_assignment]
> Running test [ng_inject_inline]
> --- arrays.js
> Running test [holes_and_undefined]
> Running test [constant_join]
> Running test [constant_join_2]
> Running test [constant_join_3]
> Running test [for_loop]
> --- ascii.js
> Running test [ascii_only_true]
> Running test [ascii_only_false]
> --- asm.js
> Running test [asm_mixed]
> --- assignment.js
> Running test [op_equals_left_local_var]
> Running test [op_equals_right_local_var]
> Running test [op_equals_left_global_var]
> Running test [op_equals_right_global_var]
> --- blocks.js
> Running test [remove_blocks]
> Running test [keep_some_blocks]
> --- collapse_vars.js
> Running test [collapse_vars_side_effects_1]
> Running test [collapse_vars_side_effects_2]
> Running test [collapse_vars_issue_721]
> Running test [collapse_vars_properties]
> Running test [collapse_vars_if]
> Running test [collapse_vars_while]
> Running test [collapse_vars_do_while]
> Running test [collapse_vars_do_while_drop_assign]
> Running test [collapse_vars_seq]
> Running test [collapse_vars_throw]
> Running test [collapse_vars_switch]
> Running test [collapse_vars_assignment]
> Running test [collapse_vars_lvalues]
> Running test [collapse_vars_lvalues_drop_assign]
> Running test [collapse_vars_misc1]
> Running test [collapse_vars_self_reference]
> Running test [collapse_vars_repeated]
> Running test [collapse_vars_closures]
> Running test [collapse_vars_unary]
> Running test [collapse_vars_try]
> Running test [collapse_vars_array]
> Running test [collapse_vars_object]
> Running test [collapse_vars_eval_and_with]
> Running test [collapse_vars_constants]
> Running test [collapse_vars_arguments]
> Running test [collapse_vars_short_circuit]
> Running test [collapse_vars_short_circuited_conditions]
> Running test [collapse_vars_regexp]
> Running test [issue_1537]
> Running test [issue_1562]
> Running test [issue_1605_1]
> Running test [issue_1605_2]
> Running test [issue_1631_1]
> Running test [issue_1631_2]
> Running test [issue_1631_3]
> Running test [var_side_effects_1]
> Running test [var_side_effects_2]
> Running test [var_side_effects_3]
> Running test [reassign_const_1]
> Running test [reassign_const_2]
> --- comparing.js
> Running test [keep_comparisons]
> Running test [keep_comparisons_with_unsafe_comps]
> Running test [dont_change_in_or_instanceof_expressions]
> --- concat-strings.js
> Running test [concat_1]
> Running test [concat_2]
> Running test [concat_3]
> Running test [concat_4]
> Running test [concat_5]
> Running test [concat_6]
> Running test [concat_7]
> Running test [concat_8]
> --- conditionals.js
> Running test [ifs_1]
> Running test [ifs_2]
> Running test [ifs_3_should_warn]
> Running test [ifs_4]
> Running test [ifs_5]
> Running test [ifs_6]
> Running test [cond_1]
> Running test [cond_2]
> Running test [cond_3]
> Running test [cond_4]
> Running test [cond_5]
> Running test [cond_7]
> Running test [cond_7_1]
> Running test [cond_8]
> Running test [cond_8b]
> Running test [cond_8c]
> Running test [ternary_boolean_consequent]
> Running test [ternary_boolean_alternative]
> Running test [trivial_boolean_ternary_expressions]
> Running test [issue_1154]
> Running test [no_evaluate]
> Running test [equality_conditionals_false]
> Running test [equality_conditionals_true]
> Running test [issue_1645_1]
> Running test [issue_1645_2]
> Running test 

Bug#982865: meson: meson ignores CPPFLAGS

[Sebastian Ramacher]

On 2021-02-15 20:34:20 +0100, Sebastian Ramacher wrote:
> Control: severity -1 serious
> 
> On 2021-02-15 23:43:24 +0800, Yangfl wrote:
> > Package: meson
> > Version: 0.57.0-1
> > 
> > When packaging https://salsa.debian.org/yangfl-guest/sequeler , I got
> > blhc warning about CPPFLAGS missing (-D_FORTIFY_SOURCE=2) after
> > upgrading meson from 0.56.2-1 to 0.57.0-1.
> > 
> > Log attached.
> 
> Thanks for reporting this issue. Attached is a very simple reproducer.
> The package builds fine in bullseye, but fails to build in unstable.

Link to the package https://people.debian.org/~sramacher/bug_1.0-1.dsc

Cheers

> 
> This will cause builds of reverse build dependencies of meson to
> silently drop flags from dpkg-buildflags. Since this also includes
> hardening options, I'm raising the severity to serious.
> 
> Also note that we are in the middle of getting bullseye released.
> Such changes are no longer suitable for bullseye. Please see
> https://release.debian.org/bullseye/freeze_policy.html#soft



-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#952367: marked as pending in uglifyjs

[Paul Gevers]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/uglifyjs/-/commit/1d34ed600793b1f3c5749cd0b5712c0e4c22e6c9


Add adapt-test-to-status-quo.patch to fix FTBFS on test suite

Closes: #952367


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952367

Processed: Re: Bug#982865: meson: meson ignores CPPFLAGS

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #982865 [meson] meson: meson ignores CPPFLAGS
Severity set to 'serious' from 'normal'

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

Processed: Bug#952367 marked as pending in uglifyjs

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952367 [src:uglifyjs] uglifyjs: FTBFS: test failed
Added tag(s) pending.

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

Bug#980967: closed by Debian FTP Masters (reply to Yaroslav Halchenko ) (Bug#980967: fixed in bats 1.2.1-2)

[Yaroslav Halchenko]

On Mon, 15 Feb 2021, Paul Gevers wrote:

> Hi Yaroslav,

> On 15-02-2021 05:51, Debian Bug Tracking System wrote:
> >  bats (1.2.1-2) unstable; urgency=medium
> >  .
> >* debian/patches
> >  - adopted patch from https://github.com/bats-core/bats-core/pull/387 to
> >resolve "bats-exec-test: command not found" (Closes: #980967)

> This seems to be not enough. The test now fails with:

yeah, earlier this morning I was told that the failing test was not a
red herring... ;)  I have uploaded -3 few hours back which should
have address this :

> /usr/lib/bats-core/preprocessing.bash: line 16: bats-preprocess: command
> not found

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
WWW:   http://www.linkedin.com/in/yarik

Bug#982122: redis: experimental package OOMs s390x buildds

[Chris Lamb]

Hi Adam,

> Ah, indeed, the failure mode means that the log never made it to
> buildd.d.o.

Curious, not heard of that failure mode — is there someplace I can
learn about that? No worries if not.

> I've attached a copy of the log from zani.

Ah, thanks. Unfortunately, it does not point us straight to the
solution. I note that you titled this bug "package OOMs" — I point
this out because the "OOM" text the log is actually the name of the
test. As in, here is tests/integration/corrupt-dump.tcl:

447 test {corrupt payload: OOM in rdbGenericLoadStringObject} {
448 start_server [list overrides [list loglevel verbose use-exit-on-panic 
yes crash-memcheck-enabled no] ] {
449 r config set sanitize-dump-payload no
450 catch { r RESTORE x 0 "\x0A\x81\x7F\xFF\xFF\xFF\xFF\xFF\xFF\xFF […]
451 assert_match "*Bad data format*" $err
452 r ping
453 }
454 }

Do we have confirmation somewhere that the build is actually OOMing,
rather than it just timing out on a test that was designed to test
*for* an OOM condition. This OOM-related bug *should* be fixed by
virtue of them adding the test to begin with (!) but if we can show
that it is still OOMing, I suspect that upstream will be able to
address it quickly.

If it helps, this test was added in this commit:

  
https://github.com/antirez/redis/commit/7ca00d694d44be13a3ff9ff1c96b49222ac9463b

... which was in:

  $ git tag --contains 7ca00d694d44be13a3ff9ff1c96b49222ac9463b
  6.2-rc1
  6.2-rc2
  6.2-rc3

Not sure if previous s390x builds were failing, which might be another
route to fixing this.


Regards,

--
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

Bug#980967: closed by Debian FTP Masters (reply to Yaroslav Halchenko ) (Bug#980967: fixed in bats 1.2.1-2)

[Paul Gevers]

Hi Yaroslav,

On 15-02-2021 05:51, Debian Bug Tracking System wrote:
>  bats (1.2.1-2) unstable; urgency=medium
>  .
>* debian/patches
>  - adopted patch from https://github.com/bats-core/bats-core/pull/387 to
>resolve "bats-exec-test: command not found" (Closes: #980967)

This seems to be not enough. The test now fails with:
autopkgtest [09:10:20]: test command1: [---
1..100
/usr/lib/bats-core/preprocessing.bash: line 16: bats-preprocess: command
not found
/usr/lib/bats-core/preprocessing.bash: line 16: bats-preprocess: command
not found
/usr/lib/bats-core/preprocessing.bash: line 16: bats-preprocess: command
not found

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#982684: subversion: FTBFS on armhf, mips64el: test failure

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 subversion: frequent FTBFS due to flaky test
Bug #982684 [src:subversion] subversion: FTBFS on armhf, mips64el: test failure
Changed Bug title to 'subversion: frequent FTBFS due to flaky test' from 
'subversion: FTBFS on armhf, mips64el: test failure'.

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

Bug#982684: subversion: FTBFS on armhf, mips64el: test failure

[Adrian Bunk]

Control: retitle -1 subversion: frequent FTBFS due to flaky test

On Sat, Feb 13, 2021 at 10:29:31AM -0500, James McCoy wrote:
> Control: forwarded -1 
> https://mail-archives.apache.org/mod_mbox/subversion-dev/202102.mbox/%3C20210212173613.2qji5xpfmcybulyl%40localhost%3E
> 
> On Sat, Feb 13, 2021 at 01:23:05PM +, Ivo De Decker wrote:
> > The latest upload of subversion to unstable fails on armhf and mips64el:
> > 
> > https://buildd.debian.org/status/package.php?p=subversion
> > 
> > On the first try, it failed on mipsel as well. Maybe the failing test is
> > unreliable?
> 
> Thanks for the report.  I've already raised the issue upstream.  If I
> can't get traction on it soon, I may just disable the test.

This failure does not seem to be specific to any architectures,
here is the same on i386:
https://tests.reproducible-builds.org/debian/logs/unstable/i386/subversion_1.14.1-1.build2.log.gz

> Cheers,

cu
Adrian

Bug#982870: hotspot FTBFS on mips*

[Adrian Bunk]

Source: hotspot
Version: 1.3.0-1
Severity: serious
Tags: ftbfs patch fixed-upstream
Forwarded: 
https://github.com/KDAB/perfparser/commit/834db4506d1aeae02d32fe41065d558300491d84

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

...
/<>/3rdparty/perfparser/app/perfregisterinfo.cpp:55:12: error: 
expected unqualified-id before numeric constant
   55 | static int mips[] = { 32,  1,  2,  3,  4,  5,  6,  7,  8,  9, 10, 11, 
12, 13, 14, 15, 16, 17,
  |^~~~
...

Bug#982869: datamash FTBFS on !x86 32bit: FAIL: tests/decorate-errors

[Adrian Bunk]

Source: datamash
Version: 1.7-1
Severity: serious
Tags: ftbfs

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

...
FAIL: tests/decorate-errors
===

decorate (GNU datamash) 1.7
Copyright (C) 2020 Assaf Gordon
License GPLv3+: GNU GPL version 3 or later .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Assaf Gordon.
e1...
e2...
e3...
e4...
e5...
e6...
e7...
e8...
e9...
e10...
e11...
e12...
e13...
e14...
e20...
e21...
e22...
e23...
e24...
e25...
e26...
e27...
e28...
e29...
e40...
e41...
e42...
e50...
e51...
e52...
e60...
e61...
e62...
e70...
c1...
decorate-errors.pl: test c1: stderr mismatch, comparing c1.3 (expected) and 
c1.E (actual)
*** c1.3Mon Feb 15 16:11:31 2021
--- c1.EMon Feb 15 16:11:31 2021
***
*** 1,2 
  decorate: invalid empty roman numeral
! decorate: conversion failed in line 1
--- 1,2 
  decorate: invalid empty roman numeral
! decorate: conversion failed in line 0
c2...
decorate-errors.pl: test c2: stderr mismatch, comparing c2.3 (expected) and 
c2.E (actual)
*** c2.3Mon Feb 15 16:11:31 2021
--- c2.EMon Feb 15 16:11:31 2021
***
*** 1,2 
  decorate: invalid empty roman numeral
! decorate: conversion failed in line 1
--- 1,2 
  decorate: invalid empty roman numeral
! decorate: conversion failed in line 0
c3...
decorate-errors.pl: test c3: stderr mismatch, comparing c3.3 (expected) and 
c3.E (actual)
*** c3.3Mon Feb 15 16:11:31 2021
--- c3.EMon Feb 15 16:11:31 2021
***
*** 1,2 
  decorate: invalid dot-decimal IPv4 address 'FOO'
! decorate: conversion failed in line 1
--- 1,2 
  decorate: invalid dot-decimal IPv4 address 'FOO'
! decorate: conversion failed in line 0
c4...
decorate-errors.pl: test c4: stderr mismatch, comparing c4.3 (expected) and 
c4.E (actual)
*** c4.3Mon Feb 15 16:11:31 2021
--- c4.EMon Feb 15 16:11:31 2021
***
*** 1,2 
  decorate: invalid IPv4 address 'FOO'
! decorate: conversion failed in line 1
--- 1,2 
  decorate: invalid IPv4 address 'FOO'
! decorate: conversion failed in line 0
c5...
decorate-errors.pl: test c5: stderr mismatch, comparing c5.3 (expected) and 
c5.E (actual)
*** c5.3Mon Feb 15 16:11:31 2021
--- c5.EMon Feb 15 16:11:31 2021
***
*** 1,2 
  decorate: invalid IPv6 address 'FOO'
! decorate: conversion failed in line 1
--- 1,2 
  decorate: invalid IPv6 address 'FOO'
! decorate: conversion failed in line 0
FAIL tests/decorate-errors.pl (exit status: 1)


Testsuite summary for GNU datamash 1.7

# TOTAL: 23
# PASS:  20
# SKIP:  2
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to assafgor...@gmail.com

make[5]: *** [Makefile:3686: test-suite.log] Error 1



(m68k and sh4 are building with nocheck)

Processed: [PATCH] Re: Bug#982717: udfclient: FTBFS: bmake[1]: no target to make.

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch confirmed
Bug #982717 [src:udfclient] udfclient: FTBFS: bmake[1]: no target to make.
Added tag(s) patch and confirmed.

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

Bug#982717: [PATCH] Re: Bug#982717: udfclient: FTBFS: bmake[1]: no target to make.

[Dennis Filder]

Control: tag -1 patch confirmed

The current bmake backend for debhelper no longer inherits from the
autoconf backend.  The attached patch devises an override that
restores the old behaviour, and I've verified that it works.

Regards,
Dennis.

udfclient-0.8.11-dhoverride.patch.gz
Description: application/gzip

Processed: bug 966935 is forwarded to https://github.com/nichtich/Pandoc-Wrapper/issues/43, tagging 966935

[Debian Bug Tracking System]

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

> forwarded 966935 https://github.com/nichtich/Pandoc-Wrapper/issues/43
Bug #966935 [src:libpandoc-wrapper-perl] libpandoc-wrapper-perl: FTBFS: 
dh_auto_test: error: perl Build test --verbose 1 returned exit code 1
Set Bug forwarded-to-address to 
'https://github.com/nichtich/Pandoc-Wrapper/issues/43'.
> tags 966935 + patch
Bug #966935 [src:libpandoc-wrapper-perl] libpandoc-wrapper-perl: FTBFS: 
dh_auto_test: error: perl Build test --verbose 1 returned exit code 1
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#980809: Matrix package default tolerance on s390x (Re: Bug#980809: rmatrix: breaks autopkgtest of r-cran-glmmtmb on s390x)

[Dirk Eddelbuettel]

Martin,

I have this long-running bug report against Matrix, triggered by glmmTMB on
s390x.  Graham has been chasing this patiently and we are now at the level of
checking on a shell account on the appropriate hardware. 

We validated that everything does in fact "still break" with CRAN-current
packages of everything (and R 4.0.3, I guess by tomorrow we'd have 4.0.4).

glmmTMB does indeed fail in an example -- but so does Matrix 1.3-2 when I run

  _R_CHECK_FORCE_SUGGESTS_=false R CMD check \
 --no-manual --no-vignettes Matrix_1.3-2.tar.gz

and I see

  [...]
  Running 'factorizing.R'
 ERROR
Running the tests in 'tests/factorizing.R' failed.
Last 13 lines of output:
  + inherits(qrZ, "sparseQR")
  + inherits(Rz, "sparseMatrix")
  + isTriangular(Rz)
  + isDiagonal(Rz) # even though formally a "dtCMatrix"
  + qr2rankMatrix(qrZ, do.warn=FALSE) == 6
  + })
  > options(oo)
  > 
  > ## problematic rank deficient rankMatrix() case -- only seen in large cases 
??
  > Z. <- readRDS(system.file("external", "Z_NA_rnk.rds", package="Matrix"))
  > tools::assertWarning(rnkZ. <- rankMatrix(Z., method = "qr")) # gave errors
  Error in assertCondition(expr, classes, .exprString = d.expr) : 
Failed to get warning in evaluating rnkZ. <- rankMatrix(Z., method  ...
  Calls:  -> assertCondition
  Execution halted
* checking for unstated dependencies in vignettes ... OK

Can you advise if I should dive into a particular routine or comparison to
see what is up here?

Best,  Dirk

-- 
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#982724: marked as done (panicparse: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/maruel/panicparse github.com/maruel/panicparse/cmd/panic github.com/maruel/panicpar

[Debian Bug Tracking System]

Your message dated Mon, 15 Feb 2021 15:48:48 +
with message-id 
and subject line Bug#982724: fixed in golang-1.15 1.15.8-4
has caused the Debian Bug report #982724,
regarding panicparse: FTBFS: dh_auto_test: error: cd _build && go test -vet=off 
-v -p 4 github.com/maruel/panicparse github.com/maruel/panicparse/cmd/panic 
github.com/maruel/panicparse/cmd/panic/internal 
github.com/maruel/panicparse/cmd/pp github.com/maruel/panicparse/internal 
github.com/maruel/panicparse/stack 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.)


-- 
982724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: panicparse
Version: 1.3.0-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package panicparse
> dpkg-buildpackage: info: source version 1.3.0-4
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Shengjing Zhu 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --builddirectory=_build --buildsystem=golang --with=golang
>dh_auto_clean -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf_clean -O--builddirectory=_build -O--buildsystem=golang
>dh_clean -O--builddirectory=_build -O--buildsystem=golang
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building panicparse using existing 
> ./panicparse_1.3.0.orig.tar.gz
> dpkg-source: info: building panicparse in panicparse_1.3.0-4.debian.tar.xz
> dpkg-source: info: building panicparse in panicparse_1.3.0-4.dsc
>  debian/rules binary
> dh binary --builddirectory=_build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
>   cd _build && go install -trimpath -v -p 4 github.com/maruel/panicparse 
> github.com/maruel/panicparse/cmd/panic 
> github.com/maruel/panicparse/cmd/panic/internal 
> github.com/maruel/panicparse/cmd/pp github.com/maruel/panicparse/internal 
> github.com/maruel/panicparse/stack
> runtime/internal/sys
> internal/unsafeheader
> internal/cpu
> runtime/internal/atomic
> math/bits
> runtime/internal/math
> unicode/utf8
> internal/race
> sync/atomic
> unicode
> internal/bytealg
> math
> internal/testlog
> runtime
> runtime/cgo
> golang.org/x/sys/internal/unsafeheader
> encoding
> unicode/utf16
> github.com/maruel/panicparse/cmd/panic/internal
> internal/reflectlite
> sync
> errors
> sort
> io
> strconv
> internal/oserror
> syscall
> strings
> bytes
> reflect
> regexp/syntax
> bufio
> html
> internal/syscall/unix
> time
> internal/syscall/execenv
> regexp
> context
> internal/poll
> internal/fmtsort
> encoding/binary
> os
> encoding/base64
> golang.org/x/sys/unix
> os/signal
> path/filepath
> fmt
> io/ioutil
> os/exec
> go/token
> log
> flag
> net/url
> go/scanner
> os/user
> go/ast
> encoding/json
> github.com/mattn/go-isatty
> github.com/mattn/go-colorable
> github.com/mgutz/ansi
> text/template/parse
> go/parser
> github.com/maruel/panicparse/cmd/panic
> text/template
> html/template
> github.com/maruel/panicparse/stack
> github.com/maruel/panicparse/internal
> github.com/maruel/panicparse
> github.com/maruel/panicparse/cmd/pp
> # github.com/maruel/panicparse/cmd/panic
> loadinternal: cannot find runtime/cgo
>dh_auto_test -O--builddirectory=_build -O--buildsystem=golang
>   cd _build && go test -vet=off -v -p 4 github.com/maruel/panicparse 
> github.com/maruel/panicparse/cmd/panic 
> github.com/maruel/panicparse/cmd/panic/internal 
> github.com/maruel/panicparse/cmd/pp github.com/maruel/panicparse/internal 
> github.com/maruel/panicparse/stack
> # github.com/maruel/panicparse/cmd/panic.test
> loadinternal: cannot find runtime/cgo
> ? github.com/maruel/panicparse[no test files]
> === RUN   TestMain
> === RUN   TestMain/locked
> === RUN   TestMain/stack_cut_off_named
> === RUN   TestMain/stdlib_and_other
> === RUN   TestMain/args_elided
> === RUN   TestMain/chan_send
> === RUN   TestMain/str
> 

Bug#982720: marked as done (snapd: FTBFS: dh_auto_test fails)

[Debian Bug Tracking System]

Your message dated Mon, 15 Feb 2021 15:48:48 +
with message-id 
and subject line Bug#982720: fixed in golang-1.15 1.15.8-4
has caused the Debian Bug report #982720,
regarding snapd: FTBFS: dh_auto_test fails
to be marked as done.

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

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


-- 
982720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: snapd
Version: 2.48.2-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 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 '/<>'
> dh_auto_test -- -pkgdir=/<>/_build/std -buildmode=pie -tags 
> "nosecboot" 
> dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 
> in use)
>   cd _build && go test -vet=off -v -p 1 
> -pkgdir=/<>/_build/std -buildmode=pie -tags nosecboot 
> github.com/snapcore/snapd/advisor github.com/snapcore/snapd/arch 
> github.com/snapcore/snapd/asserts 
> github.com/snapcore/snapd/asserts/assertstest 
> github.com/snapcore/snapd/asserts/internal 
> github.com/snapcore/snapd/asserts/signtool 
> github.com/snapcore/snapd/asserts/snapasserts 
> github.com/snapcore/snapd/asserts/sysdb 
> github.com/snapcore/snapd/asserts/systestkeys github.com/snapcore/snapd/boot 
> github.com/snapcore/snapd/boot/boottest github.com/snapcore/snapd/bootloader 
> github.com/snapcore/snapd/bootloader/androidbootenv 
> github.com/snapcore/snapd/bootloader/assets 
> github.com/snapcore/snapd/bootloader/assets/genasset 
> github.com/snapcore/snapd/bootloader/bootloadertest 
> github.com/snapcore/snapd/bootloader/efi 
> github.com/snapcore/snapd/bootloader/grubenv 
> github.com/snapcore/snapd/bootloader/lkenv 
> github.com/snapcore/snapd/bootloader/ubootenv 
> github.com/snapcore/snapd/client github.com/snapcore/snapd/client/clientutil 
> github.com/snapcore/snapd/cmd/snap github.com/snapcore/snapd/cmd/snap-exec 
> github.com/snapcore/snapd/cmd/snap-failure 
> github.com/snapcore/snapd/cmd/snap-preseed 
> github.com/snapcore/snapd/cmd/snap-recovery-chooser 
> github.com/snapcore/snapd/cmd/snap-repair 
> github.com/snapcore/snapd/cmd/snap-seccomp 
> github.com/snapcore/snapd/cmd/snap-seccomp/syscalls 
> github.com/snapcore/snapd/cmd/snap-update-ns 
> github.com/snapcore/snapd/cmd/snapctl github.com/snapcore/snapd/cmd/snapd 
> github.com/snapcore/snapd/cmd/snaplock 
> github.com/snapcore/snapd/cmd/snaplock/runinhibit 
> github.com/snapcore/snapd/daemon github.com/snapcore/snapd/dbusutil 
> github.com/snapcore/snapd/dbusutil/dbustest 
> github.com/snapcore/snapd/desktop/notification github.com/snapcore/snapd/dirs 
> github.com/snapcore/snapd/docs github.com/snapcore/snapd/errtracker 
> github.com/snapcore/snapd/features github.com/snapcore/snapd/gadget 
> github.com/snapcore/snapd/gadget/edition 
> github.com/snapcore/snapd/gadget/install 
> github.com/snapcore/snapd/gadget/internal 
> github.com/snapcore/snapd/gadget/quantity github.com/snapcore/snapd/httputil 
> github.com/snapcore/snapd/i18n github.com/snapcore/snapd/i18n/xgettext-go 
> github.com/snapcore/snapd/image github.com/snapcore/snapd/interfaces 
> github.com/snapcore/snapd/interfaces/apparmor 
> github.com/snapcore/snapd/interfaces/backends 
> github.com/snapcore/snapd/interfaces/builtin 
> github.com/snapcore/snapd/interfaces/dbus 
> github.com/snapcore/snapd/interfaces/hotplug 
> github.com/snapcore/snapd/interfaces/ifacetest 
> github.com/snapcore/snapd/interfaces/kmod 
> github.com/snapcore/snapd/interfaces/mount 
> github.com/snapcore/snapd/interfaces/policy 
> github.com/snapcore/snapd/interfaces/seccomp 
> github.com/snapcore/snapd/interfaces/systemd 
> github.com/snapcore/snapd/interfaces/udev 
> github.com/snapcore/snapd/interfaces/utils github.com/snapcore/snapd/jsonutil 
> github.com/snapcore/snapd/jsonutil/safejson github.com/snapcore/snapd/kernel 
> github.com/snapcore/snapd/logger github.com/snapcore/snapd/metautil 
> github.com/snapcore/snapd/netutil github.com/snapcore/snapd/osutil 
> github.com/snapcore/snapd/osutil/disks github.com/snapcore/snapd/osutil/mount 
> github.com/snapcore/snapd/osutil/squashfs 
> github.com/snapcore/snapd/osutil/strace github.com/snapcore/snapd/osutil/sys 
> github.com/snapcore/snapd/osutil/udev/crawler 
> github.com/snapcore/snapd/osutil/udev/netlink 
> github.com/snapcore/snapd/overlord 
> github.com/snapcore/snapd/overlord/assertstate 
> github.com/snapcore/snapd/overlord/assertstate/assertstatetest 
> 

Bug#982714: marked as done (golang-github-jacobsa-ogletest: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/jacobsa/ogletest github.com/jacobsa/ogletest/srcu

[Debian Bug Tracking System]

Your message dated Mon, 15 Feb 2021 15:48:48 +
with message-id 
and subject line Bug#982714: fixed in golang-1.15 1.15.8-4
has caused the Debian Bug report #982714,
regarding golang-github-jacobsa-ogletest: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/jacobsa/ogletest 
github.com/jacobsa/ogletest/srcutil github.com/jacobsa/ogletest/test_cases 
github.com/jacobsa/ogletest/test_cases/mock_image 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.)


-- 
982714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-jacobsa-ogletest
Version: 0.0~git20170503.80d50a7-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> github.com/jacobsa/ogletest github.com/jacobsa/ogletest/srcutil 
> github.com/jacobsa/ogletest/test_cases 
> github.com/jacobsa/ogletest/test_cases/mock_image
> internal/unsafeheader
> runtime/internal/sys
> internal/cpu
> internal/race
> runtime/internal/atomic
> runtime/internal/math
> sync/atomic
> unicode
> unicode/utf8
> math/bits
> internal/testlog
> internal/bytealg
> image/color
> math
> runtime
> internal/reflectlite
> sync
> errors
> sort
> io
> strconv
> internal/oserror
> syscall
> bytes
> strings
> reflect
> path
> regexp/syntax
> bufio
> image
> internal/syscall/unix
> time
> internal/syscall/execenv
> regexp
> context
> internal/poll
> golang.org/x/net/context
> internal/fmtsort
> os
> runtime/debug
> path/filepath
> fmt
> io/ioutil
> github.com/jacobsa/ogletest/srcutil
> log
> flag
> github.com/jacobsa/oglematchers
> runtime/trace
> github.com/jacobsa/reqtrace
> testing
> github.com/jacobsa/oglemock
> github.com/jacobsa/ogletest/test_cases/mock_image
> github.com/jacobsa/ogletest
> github.com/jacobsa/ogletest/test_cases
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
> github.com/jacobsa/ogletest github.com/jacobsa/ogletest/srcutil 
> github.com/jacobsa/ogletest/test_cases 
> github.com/jacobsa/ogletest/test_cases/mock_image
> # github.com/jacobsa/ogletest/srcutil.test
> loadinternal: cannot find runtime/cgo
> # github.com/jacobsa/ogletest.test
> loadinternal: cannot find runtime/cgo
> === RUN   TestNoCurrentTest
> --- PASS: TestNoCurrentTest (0.00s)
> === RUN   TestNoFailure
> --- PASS: TestNoFailure (0.00s)
> === RUN   TestInvalidFormatString
> --- PASS: TestInvalidFormatString (0.00s)
> === RUN   TestNoMatchWithoutErrorText
> --- PASS: TestNoMatchWithoutErrorText (0.00s)
> === RUN   TestNoMatchWithErrorTExt
> --- PASS: TestNoMatchWithErrorTExt (0.00s)
> === RUN   TestFailureWithUserMessage
> --- PASS: TestFailureWithUserMessage (0.00s)
> === RUN   TestAdditionalFailure
> --- PASS: TestAdditionalFailure (0.00s)
> === RUN   TestGoldenFiles
> integration_test.go:265: Output for test case passing doesn't match 
> golden file.
> integration_test.go:265: Output for test case stop doesn't match golden 
> file.
> integration_test.go:265: Output for test case no_cases doesn't match 
> golden file.
> integration_test.go:265: Output for test case filtered doesn't match 
> golden file.
> integration_test.go:265: Output for test case run_twice doesn't match 
> golden file.
> integration_test.go:265: Output for test case mock doesn't match golden 
> file.
> integration_test.go:265: Output for test case panicking doesn't match 
> golden file.
> integration_test.go:265: Output for test case failing doesn't match 
> golden file.
> integration_test.go:265: Output for test case unexported doesn't match 
> golden file.
> --- FAIL: TestGoldenFiles (4.05s)
> FAIL
> FAIL  github.com/jacobsa/ogletest 4.057s
> === RUN   TestRegisterMethodsTest
> [--] Running tests from MethodsTest
> [ RUN  ] MethodsTest.NoMethods
> [   OK ] MethodsTest.NoMethods
> [ RUN  ] MethodsTest.OneMethod
> [   OK ] MethodsTest.OneMethod
> [ RUN  ] MethodsTest.MultipleMethods
> [   OK ] MethodsTest.MultipleMethods
> [--] Finished with tests from MethodsTest
> 

Bug#982701: marked as done (golang-github-pkg-profile: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/pkg/profile returned exit code 1)

[Debian Bug Tracking System]

Your message dated Mon, 15 Feb 2021 15:48:48 +
with message-id 
and subject line Bug#982701: fixed in golang-1.15 1.15.8-4
has caused the Debian Bug report #982701,
regarding golang-github-pkg-profile: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/pkg/profile 
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.)


-- 
982701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-pkg-profile
Version: 1.2.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> github.com/pkg/profile
> internal/unsafeheader
> runtime/internal/sys
> internal/cpu
> runtime/internal/atomic
> internal/race
> runtime/internal/math
> sync/atomic
> unicode
> internal/bytealg
> unicode/utf8
> internal/testlog
> math/bits
> math
> runtime
> internal/reflectlite
> sync
> errors
> sort
> internal/oserror
> io
> strconv
> syscall
> strings
> bytes
> reflect
> hash
> bufio
> hash/crc32
> text/tabwriter
> internal/syscall/unix
> time
> internal/syscall/execenv
> context
> internal/poll
> encoding/binary
> internal/fmtsort
> os
> path/filepath
> os/signal
> fmt
> io/ioutil
> log
> runtime/trace
> compress/flate
> compress/gzip
> runtime/pprof
> github.com/pkg/profile
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
> github.com/pkg/profile
> # github.com/pkg/profile.test
> loadinternal: cannot find runtime/cgo
> === RUN   TestProfile
> profile_test.go:200: default profile (cpu)
> profile_test.go:220: stderr: wanted '[profile: cpu profiling enabled]', 
> got '# command-line-arguments
> loadinternal: cannot find runtime/cgo
> 2021/02/13 05:50:35 profile: cpu profiling enabled, 
> /tmp/profile867216648/cpu.pprof
> 2021/02/13 05:50:35 profile: cpu profiling disabled, 
> /tmp/profile867216648/cpu.pprof
> '
> profile_test.go:200: memory profile
> profile_test.go:220: stderr: wanted '[profile: memory profiling 
> enabled]', got '# command-line-arguments
> loadinternal: cannot find runtime/cgo
> 2021/02/13 05:50:36 profile: memory profiling enabled (rate 4096), 
> /tmp/profile525680101/mem.pprof
> 2021/02/13 05:50:36 profile: memory profiling disabled, 
> /tmp/profile525680101/mem.pprof
> '
> profile_test.go:200: memory profile (rate 2048)
> profile_test.go:220: stderr: wanted '[profile: memory profiling enabled 
> (rate 2048)]', got '# command-line-arguments
> loadinternal: cannot find runtime/cgo
> 2021/02/13 05:50:36 profile: memory profiling enabled (rate 2048), 
> /tmp/profile086753360/mem.pprof
> 2021/02/13 05:50:36 profile: memory profiling disabled, 
> /tmp/profile086753360/mem.pprof
> '
> profile_test.go:200: double start
> profile_test.go:220: stderr: wanted '[cpu profiling enabled profile: 
> Start() already called]', got '# command-line-arguments
> loadinternal: cannot find runtime/cgo
> 2021/02/13 05:50:36 profile: cpu profiling enabled, 
> /tmp/profile306850439/cpu.pprof
> 2021/02/13 05:50:36 profile: Start() already called
> exit status 1
> '
> profile_test.go:200: block profile
> profile_test.go:220: stderr: wanted '[profile: block profiling enabled]', 
> got '# command-line-arguments
> loadinternal: cannot find runtime/cgo
> 2021/02/13 05:50:36 profile: block profiling enabled, 
> /tmp/profile814120833/block.pprof
> 2021/02/13 05:50:37 profile: block profiling disabled, 
> /tmp/profile814120833/block.pprof
> '
> profile_test.go:200: mutex profile
> profile_test.go:220: stderr: wanted '[profile: mutex profiling enabled]', 
> got '# command-line-arguments
> loadinternal: cannot find runtime/cgo
> 2021/02/13 05:50:37 profile: mutex profiling enabled, 
> /tmp/profile626939674/mutex.pprof
> 2021/02/13 05:50:37 profile: mutex profiling disabled, 
> /tmp/profile626939674/mutex.pprof
> '
> 

Processed: Bug#982734 marked as pending in golang

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #982734 [src:golang-1.15] delve: FTBFS: failed test
Added tag(s) pending.

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

Bug#982734: marked as pending in golang

[Shengjing Zhu]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/go-team/compiler/golang/-/commit/25ddd5c4616e7a12316875d339771e72906e2b9a


Revert 
"d/patches/0007-cmd-link-check-CGO_CFLAGS-for-non-g-I-O-options-befo.patch"

This reverts commit fd15b45c27f0f63538db3763e44f0efc7d57edab.

This patch causes:

1. unexpected error message, which makes some packages FTBFS

   loadinternal: cannot find runtime/cgo

   Closes: #982701, #982714, #982720, #982724, #982734

2. unable to build package on riscv64

   external linking not supported for linux/riscv64


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/982734

Processed: Bug#982701 marked as pending in golang

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #982701 [src:golang-1.15] golang-github-pkg-profile: FTBFS: dh_auto_test: 
error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
github.com/pkg/profile returned exit code 1
Added tag(s) pending.

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

Bug#982701: marked as pending in golang

[Shengjing Zhu]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/go-team/compiler/golang/-/commit/25ddd5c4616e7a12316875d339771e72906e2b9a


Revert 
"d/patches/0007-cmd-link-check-CGO_CFLAGS-for-non-g-I-O-options-befo.patch"

This reverts commit fd15b45c27f0f63538db3763e44f0efc7d57edab.

This patch causes:

1. unexpected error message, which makes some packages FTBFS

   loadinternal: cannot find runtime/cgo

   Closes: #982701, #982714, #982720, #982724, #982734

2. unable to build package on riscv64

   external linking not supported for linux/riscv64


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/982701

Bug#982864: perceptualdiff FTBFS with test failure on several architectures

[Adrian Bunk]

Source: perceptualdiff
Version: 2.1-3
Severity: serious
Tags: ftbfs

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

Bug#971129: shim-signed: FTBFS: build-dependency not installable: shim-unsigned (= 15+1533136590.3beb971-7)

[Ivo De Decker]

Hi Steve,

Thanks for the info.

On Mon, Feb 15, 2021 at 12:43:33AM +, Steve McIntyre wrote:
> >Could you clarify the timing for this, especially the timeline for getting 
> >the
> >signature from Microsoft (as far as that can be predicted)? I'm trying to
> >assess if this could become a blocker wrt the actual release. Is it an option
> >to release with the current version of shim-signed (ie the one that's also in
> >buster) if we don't get the signature in time?
> 
> It's not really an option to release with the old shim at this point,
> I'm afraid.

That's good to know. I tagged this bug 'is-blocker', to make sure we keep an
eye on it.

> But there are newer processes in place around getting new
> builds signed, so I'm not worrying too much here about delaying the
> release.

OK. That's encouraging :)

> I expect to have things sorted soon.

Make sure to let is know if you encounter any issues.

Cheers,

Ivo

Bug#982862: nagios-plugins-contrib autopkgtest regression on several architectures: check_ssl_cert: unable to write certificate

[Adrian Bunk]

Source: nagios-plugins-contrib
Version: 29.20210204
Severity: serious

https://tracker.debian.org/pkg/nagios-plugins-contrib

Migration status for nagios-plugins-contrib (28.20201207 to 29.20210204): 
BLOCKED: Rejected/violates migration policy/introduces a regression
Issues preventing migration:
autopkgtest for nagios-plugins-contrib/29.20210204: amd64: Regression ♻ 
(reference ♻), arm64: Regression ♻ (reference ♻), armhf: Pass, i386: Regression 
♻ (reference ♻), ppc64el: Pass


https://ci.debian.net/data/autopkgtest/testing/amd64/n/nagios-plugins-contrib/10465947/log.gz

...
autopkgtest [16:53:05]: test command7: /usr/lib/nagios/plugins/check_ssl_cert 
-H www.debian.org
autopkgtest [16:53:05]: test command7: [---
unable to write certificate
139631578813760:error:09072007:PEM routines:PEM_write_bio:BUF 
lib:../crypto/pem/pem_lib.c:658:
SSL_CERT OK - x509 certificate 'www.debian.org' from 'R3' valid until Mar 30 
00:17:56 2021 GMT (expires in 43 days)|days_chain_elem1=43;20;15;; 
days_chain_elem2=227;20;15;;
autopkgtest [16:53:07]: test command7: ---]
autopkgtest [16:53:07]: test command7:  - - - - - - - - - - results - - - - - - 
- - - -
command7 FAIL stderr: unable to write certificate

Bug#982859: libcmis-dev: allowable-actions.hxx uses non-existing file boost/shared_ptr.hpp

[Vincent Lefevre]

Package: libcmis-dev
Version: 0.5.2-2+b2
Severity: serious

Configuring upstream's LibreOffice fails with an obscure error:

checking whether g++ supports C++17... configure: error: no
Error running configure at ./autogen.sh line 316.

In the config.log file:

configure:18900: checking whether g++ supports C++17
configure:18962: g++ -c  -std=c++17 -Werror -DSYSTEM_LIBCMIS -isystem 
/usr/include/libcmis-0.5 -isystem /usr/include/x86_64-linux-gnu -isystem 
/usr/include/libxml2  conftest.cpp >&5
In file included from /usr/include/libcmis-0.5/libcmis/libcmis.hxx:33,
 from conftest.cpp:93:
/usr/include/libcmis-0.5/libcmis/allowable-actions.hxx:34:10: fatal error: 
boost/shared_ptr.hpp: No such file or directory
   34 | #include 
  |  ^~

Indeed, /usr/include/libcmis-0.5/libcmis/allowable-actions.hxx
from libcmis-dev has:

#include 

and there's no such file.

Now, I don't know whether this file is really needed, in which case
I suppose that there is a missing dependency on libboost1.74-dev
(currently).

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

Kernel: Linux 5.10.0-1-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libcmis-dev depends on:
ii  libcmis-0.5-5v5  0.5.2-2+b2
ii  libcurl4-gnutls-dev  7.74.0-1.1
ii  libxml2-dev  2.9.10+dfsg-6.3+b1

libcmis-dev recommends no packages.

libcmis-dev suggests no packages.

-- no debconf information

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

Bug#982857: All pages cut off due to IFRAME closing tag bungle

[積丹尼 Dan Jacobson]

Package: imagemagick-6-common
Version: 8:6.9.11.60+dfsg-1
Severity: grave

In
$ rgrep 'iframe.*/>' /usr/share/doc/imagemagick-6-common|wc -l
127
pages like
file:///usr/share/doc/imagemagick-6-common/html/www/command-line-processing.html
please replace

https://github.com/sponsors/ImageMagick/button; 
title="Sponsor ImageMagick" height="35" width="107" style="border: 0;"/>
with
https://github.com/sponsors/ImageMagick/button; 
title="Sponsor ImageMagick" height="35" width="107" style="border: 0;">

else, as in
https://stackoverflow.com/questions/27545757/why-is-a-self-closing-iframe-tag-preventing-further-dom-elements-to-be-displayed
the rest of the page is cutoff!

Yes, already fixed upstream, e.g., 
https://imagemagick.org/script/command-line-processing.php .

P.S.,
GET file:///usr/share/doc/imagemagick-6-common/html/www/css/magick.css 
net::ERR_FILE_NOT_FOUND

Bug#981976: icingaweb2-module-businessprocess is uninstallable: dependency on nonexistent package

[David Kunz]

... sorry i found im.

On 2/15/21 2:22 PM, Andreas Beckmann wrote:
> Control: reopen -1
> Control: severity -1 serious
> Control: retitle -1 icingaweb2-module-businessprocess: depends on nonexistent 
> icingaweb2-ipl
> 
> On Mon, 15 Feb 2021 10:58:40 +0100 David Kunz  wrote:
>> this bug has been fixed in above version, hence closing.
> 
> I cannot find any trace of icingaweb2-ipl in the archive (including NEW).
> 
> Andreas
> 

-- 
Berner Fachhochschule / Bern University of Applied Sciences
IT-Services / Team Linux & Infrastructure Services
David Kunz
IT System Engineer
___
Dammweg 3, CH-3013 Bern
Telefon direkt +41 31 848 48 82
Telefon Servicedesk +41 31 848 48 48
david.k...@bfh.ch
https://bfh.ch
https://bfh.science

Processed: Re: Bug#982613: NetworkManager triggers assert in python-dbusmock test suite

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 network-manager 1.29.90-1
Bug #982613 [network-manager] NetworkManager triggers assert in python-dbusmock 
test suite
Ignoring request to reassign bug #982613 to the same package
Bug #982613 [network-manager] NetworkManager triggers assert in python-dbusmock 
test suite
Ignoring request to alter found versions of bug #982613 to the same values 
previously set
> tag -1 upstream fixed-upstream
Bug #982613 [network-manager] NetworkManager triggers assert in python-dbusmock 
test suite
Added tag(s) fixed-upstream and upstream.
> forwarded -1 
> https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/662
Bug #982613 [network-manager] NetworkManager triggers assert in python-dbusmock 
test suite
Ignoring request to change the forwarded-to-address of bug#982613 to the same 
value

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

Bug#982613: NetworkManager triggers assert in python-dbusmock test suite

[Martin Pitt]

Control: reassign -1 network-manager 1.29.90-1
Control: tag -1 upstream fixed-upstream
Control: forwarded -1 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/662

This eventually *did* turn out to be a bug in NetworkManager itself, and only
became visible now because of the beta version number.

I validated that the fix

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/e1e9abdf041b4cc

backports cleanly on top of 1.29.90 and fixes the assertion and the
python-dbusmock tests. Thus moving this bug back to NM.

I don't think this beta version should move into testing, as it's prone to
cause assertion crashes in real-life situations as well. But of course Michael
has the last word on this.

Thanks Thomas and Michael for your help here!

Martin

Bug#977542: golang-github-revel-revel: Depends on network in tests

[Reinhard Tartler]

Control: severity -1 important

Dear release team,

I'm writing as a member of the pkg-go team and am mostly concerned about
potential removal of depending packages.

The package itself appears to be fine. The tests fail if and only if the
test setup doesn't provide (proper) internet connectivity. In fact, it
tries at test time to reach http://httpbin.org/get - a service aimed at
developing and debugging programs that do HTTP/REST calls.

Based on this, I'm not convinced about removing a significant amount of
packages from the buster release because of this issue. I'm therefore
downgrading the issue to important and would recommend fixing it right
after buster release.

I'm reaching out to you to confirm this thinking. If you do believe this is
something that ought to be fixed for buster, I'd be happy to upload the
proposed patch to sid right away, as it seems appropriate to disable the
test -- the additional test coverage that it could provide is in no
relationship compared to the effort it would take to fake out the internet
service.

--
regards,
Reinhard

Processed: golang-github-revel-revel: Depends on network in tests

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #977542 [golang-github-revel-revel] golang-github-revel-revel: Depends on 
network in tests
Severity set to 'important' from 'serious'

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

Processed: gmsh

[Debian Bug Tracking System]

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

> affects 982616 + src:pygmsh
Bug #982616 [libvoro++1] libvoro++1: ABI break without soname change
Bug #982729 [libvoro++1] octave-msh: FTBFS: msh2m_gmsh: the gmsh subprocess 
exited abnormally
Added indication that 982616 affects src:pygmsh
Added indication that 982729 affects src:pygmsh
>
End of message, stopping processing here.

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

Processed: Re: Bug#981976: icingaweb2-module-businessprocess is uninstallable: dependency on nonexistent package

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #981976 {Done: David Kunz } 
[icingaweb2-module-businessprocess] icingaweb2-module-businessprocess is 
uninstallable: dependency on nonexistent package
'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 icingaweb2-module-businessprocess/2.3.0-1.
> severity -1 serious
Bug #981976 [icingaweb2-module-businessprocess] 
icingaweb2-module-businessprocess is uninstallable: dependency on nonexistent 
package
Severity set to 'serious' from 'normal'
> retitle -1 icingaweb2-module-businessprocess: depends on nonexistent 
> icingaweb2-ipl
Bug #981976 [icingaweb2-module-businessprocess] 
icingaweb2-module-businessprocess is uninstallable: dependency on nonexistent 
package
Changed Bug title to 'icingaweb2-module-businessprocess: depends on nonexistent 
icingaweb2-ipl' from 'icingaweb2-module-businessprocess is uninstallable: 
dependency on nonexistent package'.

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

Processed: Re: Bug#981975: icingaweb2-module-director is uninstallable: dependency on nonexistent package

[Debian Bug Tracking System]

Processing control commands:

> notfixed -1 1.8.0-1
Bug #981975 {Done: David Kunz } [icingaweb2-module-director] 
icingaweb2-module-director is uninstallable: dependency on nonexistent package
No longer marked as fixed in versions icingaweb2-module-director/1.8.0-1.

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

Bug#981975: icingaweb2-module-director is uninstallable: dependency on nonexistent package

[Andreas Beckmann]

Control: notfixed -1 1.8.0-1

On Mon, 15 Feb 2021 11:20:18 +0100 David Kunz  wrote:
> this bug has been fixed in above version, hence closing.

icingaweb2-module-incubator 0.6.0-1 is in NEW.

notfixed to not confuse the BTS with found and fixed in the same version.

Andreas

Bug#930005: regina-rexx: rexxutil error

[Alen Zekulic]

On Mon, Feb 15, 2021 at 13:16:58 +0100, Agustin Martin wrote:

> I think I have something close to be ready for migration to debhelper.

Me too. :)

> ¿What do you prefer, a commit to salsa or a patch in the BTS?

For now I prefer a patch in the BTS.

Thanks,

-- 
Alen Zekulic 

Processed: tagging 980071

[Debian Bug Tracking System]

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

> tags 980071 + moreinfo
Bug #980071 [gnome-shell] gnome-shell: Using suspend in the gnome-shell power 
off/log out menu does log out and suspend in the wrong order
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#930005: regina-rexx: rexxutil error

[Agustin Martin]

El lun, 15 feb 2021 a las 0:05, Agustin Martin () escribió:
>
> El vie, 12 feb 2021 a las 23:05, Alen Zekulic () 
> escribió:
> >
> > I agree, please go ahead!
>
> Uploaded.

Hi,

Seems this upload has been late for two days, so regina-rexx will not
hit bullseye because of soft freeze (see
https://release.debian.org/bullseye/freeze_policy.html#soft),

"Packages that are not in testing will not be allowed to migrate to
testing. This applies to new packages as well as to packages that were
removed from testing (either manually or by auto-removals). Packages
that are not in bullseye at the start of the soft freeze will not be
in the release."

> > I planed to migrate my debian/rules to debhelper too.
>
> When I was playing with this there were still some issues. Once I find
> time to continue and consider things in good shape, I will let you
> know. Another thing I think may be interesting is to split the a-z
> patch into smaller chunks for better handling.

I think I have something close to be ready for migration to debhelper.
¿What do you prefer, a commit to salsa or a patch in the BTS?

Regards,

-- 
Agustin

Bug#982700: marked as done (pygmsh: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Mon, 15 Feb 2021 13:08:09 +0100
with message-id 
and subject line voronoicell
has caused the Debian Bug report #982700,
regarding pygmsh: FTBFS: dh_auto_test: error: pybuild --test -i python{version} 
-p 3.9 returned exit code 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.)


-- 
982700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygmsh
Version: 7.1.5-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 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 '/<>'
> dh_auto_build
> I: pybuild base:232: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh
> copying pygmsh/__about__.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh
> copying pygmsh/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh
> copying pygmsh/_cli.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh
> copying pygmsh/helpers.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh
> copying pygmsh/_optimize.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh
> creating /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/geo
> copying pygmsh/geo/geometry.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/geo
> copying pygmsh/geo/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/geo
> copying pygmsh/geo/dummy.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/geo
> creating /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/common
> copying pygmsh/common/geometry.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/common
> copying pygmsh/common/curve_loop.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/common
> copying pygmsh/common/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/common
> copying pygmsh/common/plane_surface.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/common
> copying pygmsh/common/line.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/common
> copying pygmsh/common/bspline.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/common
> copying pygmsh/common/surface.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/common
> copying pygmsh/common/ellipse_arc.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/common
> copying pygmsh/common/polygon.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/common
> copying pygmsh/common/dummy.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/common
> copying pygmsh/common/line_base.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/common
> copying pygmsh/common/volume.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/common
> copying pygmsh/common/spline.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/common
> copying pygmsh/common/circle_arc.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/common
> copying pygmsh/common/point.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/common
> copying pygmsh/common/surface_loop.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/common
> creating /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/occ
> copying pygmsh/occ/torus.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/occ
> copying pygmsh/occ/rectangle.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/occ
> copying pygmsh/occ/geometry.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/occ
> copying pygmsh/occ/wedge.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/occ
> copying pygmsh/occ/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/occ
> copying pygmsh/occ/ball.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/occ
> copying pygmsh/occ/box.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/occ
> copying pygmsh/occ/cone.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/occ
> copying pygmsh/occ/cylinder.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/occ
> copying pygmsh/occ/dummy.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/occ
> copying pygmsh/occ/disk.py -> 
> /<>/.pybuild/cpython3_3.9_pygmsh/build/pygmsh/occ
> PYTHONPATH=. python3 -m sphinx -N -bhtml doc/ build/html # HTML generator
> Running Sphinx v3.4.3
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 4 source files that are out of date
> updating environment: [new config] 4 added, 0 changed, 0 removed
> reading sources... [ 25%] common
> reading 

Processed: Re: Bug#969537: epdfinfo crashing with mismatched libpoppler102 and libpoppler-glib8

[Debian Bug Tracking System]

Processing control commands:

> retitle 969907 epdfinfo crashing with mismatched libpoppler102 and 
> libpoppler-glib8
Bug #969907 [libpoppler-glib8] libpoppler-glib8: introduces new ABI without 
bumping shlibs version
Changed Bug title to 'epdfinfo crashing with mismatched libpoppler102 and 
libpoppler-glib8' from 'libpoppler-glib8: introduces new ABI without bumping 
shlibs version'.
> tags 969907 + patch
Bug #969907 [libpoppler-glib8] epdfinfo crashing with mismatched libpoppler102 
and libpoppler-glib8
Added tag(s) patch.

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

Bug#969907: Bug#969537: epdfinfo crashing with mismatched libpoppler102 and libpoppler-glib8

[Simon McVittie]

Control: retitle 969907 epdfinfo crashing with mismatched libpoppler102 and 
libpoppler-glib8
Control: tags 969907 + patch

Sorry, this reply should have gone to the clone in libpoppler-glib8,
not to the archived original bug in epdfinfo (which I don't think was
ever really an epdfinfo bug).

On Mon, 15 Feb 2021 at 12:03:35 +, Simon McVittie wrote:
> I don't think this is actually about whether libpoppler-glib added new ABI
> without bumping the shlibs version - it has a .symbols file that tracks
> the version in which each public symbol was added.
>
> Instead, I think this is about private symbols and partial
> upgrades. libpoppler102 and libpoppler-glib8 come from the same
> source package, so libpoppler-glib8 is very likely to make assumptions
> about private implementation details of the corresponding version of
> libpoppler102; many of the source files glib/*.cc that get compiled into
> libpoppler-glib8 have #include "poppler-private.h". This is fine if
> everyone does an `apt upgrade` with no pinning, but breaks down if people
> do arbitrary partial upgrades with pinning or interactively (leading to a
> "Frankendebian" system).
> 
> If the upstream developers of poppler are asked to support a system where
> libpoppler102 and libpoppler-glib8 are at different versions, I'm pretty
> sure the first thing they will say is "don't". I think the same is
> appropriate for downstreams.
> 
> In Cairo and Pango (which have a similar structure with multiple binary
> packages making use of each other's implementation details), I added a
> debian/shlibs.local to make sure the binary packages all get lockstep
> dependencies. I think the same technique would be appropriate here. See
> attached.
> 
> I'm increasingly tempted to open a debhelper feature request asking for
> dh_shlibdeps to strengthen intra-source-package dependencies to be in
> lockstep by default, because this seems to be more common than strict
> separation.
>From bc7c009360869d8985462bab43fc24b1685df08a Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Mon, 15 Feb 2021 11:53:51 +
Subject: [PATCH] d/shlibs.local: Upgrade all binary packages in lockstep

Like many projects where one source package builds multiple binary
packages, poppler has private headers that share non-public interfaces
between its binary packages. Upgrading one binary package from this
source without upgrading the others is not something that its upstream
developers are ever going to test or support, and neither should we.

Closes: #969537
---
 debian/changelog| 12 
 debian/shlibs.local |  4 
 2 files changed, 16 insertions(+)
 create mode 100644 debian/shlibs.local

diff --git a/debian/changelog b/debian/changelog
index d65fa9f..54c96af 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+poppler (20.09.0-3.2) UNRELEASED; urgency=medium
+
+  * d/shlibs.local: Upgrade all binary packages in lockstep.
+Like many projects where one source package builds multiple binary
+packages, poppler has private headers that share non-public interfaces
+between its binary packages. Upgrading one binary package from this
+source without upgrading the others is not something that its upstream
+developers are ever going to test or support, and neither should we.
+(Closes: #969537)
+
+ -- Simon McVittie   Mon, 15 Feb 2021 11:44:22 +
+
 poppler (20.09.0-3.1) unstable; urgency=medium
 
   * debian/tests: make autopkgtests cross-test-friendly (Closes: #969726)
diff --git a/debian/shlibs.local b/debian/shlibs.local
new file mode 100644
index 000..af3275a
--- /dev/null
+++ b/debian/shlibs.local
@@ -0,0 +1,4 @@
+libpoppler 102 libpoppler102 (= ${binary:Version})
+libpoppler-cpp 0 libpoppler-cpp0v5 (= ${binary:Version})
+libpoppler-glib 8 libpoppler-glib8 (= ${binary:Version})
+libpoppler-qt5 1 libpoppler-qt5-1 (= ${binary:Version})
-- 
2.30.0

Processed: reassign 982613 to network-manager, found 982613 in 1.29.90-1, affects 982613

[Debian Bug Tracking System]

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

> reassign 982613 network-manager
Bug #982613 [python3-dbusmock] NetworkManager triggers assert in 
python-dbusmock test suite
Bug reassigned from package 'python3-dbusmock' to 'network-manager'.
No longer marked as found in versions python-dbusmock/0.22.0-1.
Ignoring request to alter fixed versions of bug #982613 to the same values 
previously set
> found 982613 1.29.90-1
Bug #982613 [network-manager] NetworkManager triggers assert in python-dbusmock 
test suite
Marked as found in versions network-manager/1.29.90-1.
> affects 982613 = src:python-dbusmock
Bug #982613 [network-manager] NetworkManager triggers assert in python-dbusmock 
test suite
Removed indication that 982613 affects network-manager
Added indication that 982613 affects src:python-dbusmock
> thanks
Stopping processing here.

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

Processed: tagging 982838

[Debian Bug Tracking System]

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

> # this bug is just an archive workaround - not relevant for the release
> tags 982838 + bullseye-ignore
Bug #982838 [src:win32-loader] RoM: win32-loader must not migrate automatically
Added tag(s) bullseye-ignore.
> thanks
Stopping processing here.

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

Bug#982850: duperemove: first run fails errror 13?

[Don Alex]

Package: duperemove
Version: 0.11.2-3
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: de...@roosoft.ltd.uk

Dear Maintainer,

So running duperemove for the first run.

duperemove -r -A -h --skip-zeroes --hashfile=/var/cache/duperemove-home-user
/home/user/

At the end this happened.

Total files: 2261918 Total extent hashes: 4666300 create_indexes()/45330:
Database error 13 while creating database index: database or disk is full

the folder is not full

 df -h /var

Filesystem Size  Used Avail Use% Mounted on
/dev/mapper/pulseforn--vg-var  9.4G  7.4G  1.8G  81% /var

ls -lah /var/cache/duperemove-home-user*

-rw-r--r-- 1 root root 5.0G Feb 13 17:04 /var/cache/duperemove-home-user
-rw-r--r-- 1 root root 4.6K Feb 13 17:03 /var/cache/duperemove-home-user-
journal

EDIT: For reference.

Platform: Debian 10/Testing
Kernel: 5.10.0-3-amd64 #1 SMP Debian 5.10.13-1 (2021-02-06) x86_64 GNU/Linux
duperemove v0.11.2
btrfs-progs v5.10.1



-- System Information:
Debian Release: bullseye/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-3-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages duperemove depends on:
ii  libc6 2.31-9
ii  libglib2.0-0  2.66.6-2
ii  libsqlite3-0  3.34.1-1

duperemove recommends no packages.

duperemove suggests no packages.

-- debconf-show failed

Bug#981100: marked as done (FTBFS with bind9 >= 9.16.10)

[Debian Bug Tracking System]

Your message dated Mon, 15 Feb 2021 11:03:25 +
with message-id 
and subject line Bug#981100: fixed in bind-dyndb-ldap 11.6-2
has caused the Debian Bug report #981100,
regarding FTBFS with bind9 >= 9.16.10
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.)


-- 
981100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981100
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bind-dyndb-ldap
Version: 11.6-1
Severity: normal
Tags: upstream patch ftbfs
X-Debbugs-Cc: su...@debian.org

Bind9 9.16.10 and 9.16.11 introduced API changes which break existing
installations of bind9-dyndb-ldap when bind9 gets updated and also
prevent bind9-dyndb-ldap to be built from source.

Patches are available upstream:

https://pagure.io/bind-dyndb-ldap/c/2ddd4bf55e325071566aa1c78e3681c3239895da
https://pagure.io/bind-dyndb-ldap/pull-request/202

-- 
ceterum censeo microsoftem esse delendam


pgpcbENNke9xY.pgp
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: bind-dyndb-ldap
Source-Version: 11.6-2
Done: Timo Aaltonen 

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated bind-dyndb-ldap 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 15 Feb 2021 12:47:06 +0200
Source: bind-dyndb-ldap
Architecture: source
Version: 11.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Closes: 981100
Changes:
 bind-dyndb-ldap (11.6-2) unstable; urgency=medium
 .
   * support-bind-9.16.11.diff: Fix build against bind9 9.16.11 and .11.
 (Closes: #981100)
Checksums-Sha1:
 7a36bd60903c0223fdcc0c8770428dc89c9f2a24 2045 bind-dyndb-ldap_11.6-2.dsc
 f1f6e573c9816bddc4f294dc5679950ca9eb6249 5528 
bind-dyndb-ldap_11.6-2.debian.tar.xz
 e9ceb6cfe603bfeaa43ac92939d659cea772d15a 7887 
bind-dyndb-ldap_11.6-2_source.buildinfo
Checksums-Sha256:
 a4d0743b97dc581b9eb72ac3a0da7f799f65f06df82943803cffa8c2208c5669 2045 
bind-dyndb-ldap_11.6-2.dsc
 dae33d87dacad529270203ca5398ea543a85e8e7c0dcd71d7afd85f11b77415c 5528 
bind-dyndb-ldap_11.6-2.debian.tar.xz
 d788665b02b7f295867c8a8e6323656a56862b7b82f4c9f5c779218110f52ad1 7887 
bind-dyndb-ldap_11.6-2_source.buildinfo
Files:
 31cfc95ef95a182a0e19f4bdd00d5010 2045 net optional bind-dyndb-ldap_11.6-2.dsc
 701fd6d90b712d6ebfa70e6add6aecfc 5528 net optional 
bind-dyndb-ldap_11.6-2.debian.tar.xz
 452b4e1c9508b434c76cd20360878f49 7887 net optional 
bind-dyndb-ldap_11.6-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmAqUToACgkQy3AxZaiJ
hNwuRBAAqkXAF5c2a9SFA7va8u1hHVnLBEuyvM8gAV7+4i5PpbntW/LjvebOOw6g
OlldWxkMKNYGgFyk2LZUYEE39YuByfROkHv1HwpSQnW5uCHbYFSOmnVh59e7nrRO
CsTksnCtqytJ1/5aoFi3xH8TQBN5Ue2YaZX2+Zm9ShgStfdFa+D/+RScQgkUKR6+
gQUQJzKyWWMaGtKJpm7AyITEo126od68LHt43TXVd98FnjsFXY84ReKiWpSL/vZJ
yWv+vxiB+OpG6dLxfI5m1x87xCmV5slE2qWfyN39fMeORNGJvFNUu+5B6Z9VLJZt
kJMBh/NhVjmIy+c4iIn522fCXUD0iLoc75UVxMbuHvGs5SKw4jQceVhF9Y32AVq9
LFUEtflQqhAFSewXOlmurU8bYIuCChMPAGvcqGXp9fAQtuCouqv2jTMbF5mNe/yr
hf+bDD6rpU08duYWgG3wRrTHfC9+tO8rZ5ifItvkyGaYijDHem4gOOWwMFjeXsIp
RBJgEucL8MreJ1NGyEvoVBTVrzVMucB0kHJLgSCIV93Bir60IMS8nQ00WeqKhGJx
qndmljfB4s79S/07ELoXPbo/501ZS70PIs/SQdShy4zW0uOvUcUkn3ev+8WlAboj
UnkNSfv13LwHdfWiHTKI1urS4EZepAee0hQB6UO22RiaxUx4+Qg=
=Qw+I
-END PGP SIGNATURE End Message ---

Bug#982705: marked as done (openssh: FTBFS: sha2.h:57:16: error: redefinition of ‘struct _SHA2_CTX’)

[Debian Bug Tracking System]

Your message dated Mon, 15 Feb 2021 10:48:48 +
with message-id 
and subject line Bug#982705: fixed in openssh 1:8.4p1-4
has caused the Debian Bug report #982705,
regarding openssh: FTBFS: sha2.h:57:16: error: redefinition of ‘struct 
_SHA2_CTX’
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.)


-- 
982705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openssh
Version: 1:8.4p1-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -pipe -Wno-error=format-truncation -Wall 
> -Wextra -Wpointer-arith -Wuninitialized -Wsign-compare -Wformat-security 
> -Wsizeof-pointer-memaccess -Wno-pointer-sign -Wno-unused-parameter 
> -Wno-unused-result -Wimplicit-fallthrough -fno-strict-aliasing 
> -D_FORTIFY_SOURCE=2 -ftrapv -fno-builtin-memset -fstack-protector-strong 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -DSSH_EXTRAVERSION=\"Debian-3\"   -I. -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 
> -D_XOPEN_SOURCE=600 -D_BSD_SOURCE -D_DEFAULT_SOURCE -I/usr/include/editline  
> -isystem /usr/include/mit-krb5 -isystem /usr/include/mit-krb5  
> -DSSHDIR=\"/etc/ssh\" -D_PATH_SSH_PROGRAM=\"/usr/bin/ssh\" 
> -D_PATH_SSH_ASKPASS_DEFAULT=\"/usr/bin/ssh-askpass\" 
> -D_PATH_SFTP_SERVER=\"/usr/lib/openssh/sftp-server\" 
> -D_PATH_SSH_KEY_SIGN=\"/usr/lib/openssh/ssh-keysign\" 
> -D_PATH_SSH_PKCS11_HELPER=\"/usr/lib/openssh/ssh-pkcs11-helper\" 
> -D_PATH_SSH_SK_HELPER=\"/usr/lib/openssh/ssh-sk-helper\" 
> -D_PATH_SSH_PIDDIR=\"/run\" -D_PATH_PRIVSEP_CHROOT_DIR=\"/run/sshd\" 
> -DHAVE_CONFIG_H -c ../../sk-usbhid.c -o sk-usbhid.o
> In file included from ../../sk-usbhid.c:30:
> /usr/include/sha2.h:57:16: error: redefinition of ‘struct _SHA2_CTX’
>57 | typedef struct _SHA2_CTX {
>   |^
> In file included from ../../openbsd-compat/openbsd-compat.h:46,
>  from ../../includes.h:174,
>  from ../../sk-usbhid.c:19:
> ../../openbsd-compat/sha2.h:66:16: note: originally defined here
>66 | typedef struct _SHA2_CTX {
>   |^
> In file included from ../../sk-usbhid.c:30:
> /usr/include/sha2.h:64:3: error: conflicting types for ‘SHA2_CTX’
>64 | } SHA2_CTX;
>   |   ^~~~
> In file included from ../../openbsd-compat/openbsd-compat.h:46,
>  from ../../includes.h:174,
>  from ../../sk-usbhid.c:19:
> ../../openbsd-compat/sha2.h:73:3: note: previous declaration of ‘SHA2_CTX’ 
> was here
>73 | } SHA2_CTX;
>   |   ^~~~
> In file included from ../../sk-usbhid.c:30:
> /usr/include/sha2.h:70:6: error: conflicting types for ‘SHA256Init’
>70 | void SHA256Init(SHA2_CTX *);
>   |  ^~
> In file included from ../../openbsd-compat/openbsd-compat.h:46,
>  from ../../includes.h:174,
>  from ../../sk-usbhid.c:19:
> ../../openbsd-compat/sha2.h:96:6: note: previous declaration of ‘SHA256Init’ 
> was here
>96 | void SHA256Init(SHA2_CTX *);
>   |  ^~
> In file included from ../../sk-usbhid.c:30:
> /usr/include/sha2.h:72:6: error: conflicting types for ‘SHA256Update’
>72 | void SHA256Update(SHA2_CTX *, const uint8_t *, size_t);
>   |  ^~~~
> In file included from ../../openbsd-compat/openbsd-compat.h:46,
>  from ../../includes.h:174,
>  from ../../sk-usbhid.c:19:
> ../../openbsd-compat/sha2.h:98:6: note: previous declaration of 
> ‘SHA256Update’ was here
>98 | void SHA256Update(SHA2_CTX *, const u_int8_t *, size_t)
>   |  ^~~~
> In file included from ../../sk-usbhid.c:30:
> /usr/include/sha2.h:73:6: error: conflicting types for ‘SHA256Pad’
>73 | void SHA256Pad(SHA2_CTX *);
>   |  ^
> In file included from ../../openbsd-compat/openbsd-compat.h:46,
>  from ../../includes.h:174,
>  from ../../sk-usbhid.c:19:
> ../../openbsd-compat/sha2.h:100:6: note: previous declaration of ‘SHA256Pad’ 
> was here
>   100 | void SHA256Pad(SHA2_CTX *);
>   |  ^
> In file included from ../../sk-usbhid.c:30:
> /usr/include/sha2.h:74:6: error: conflicting types for ‘SHA256Final’
>74 | void SHA256Final(uint8_t 

Bug#980677: marked as done (espresso: FTBFS: Error: #error No fft_scalar backend selected!)

[Debian Bug Tracking System]

Your message dated Mon, 15 Feb 2021 10:48:30 +
with message-id 
and subject line Bug#980677: fixed in espresso 6.7-2
has caused the Debian Bug report #980677,
regarding espresso: FTBFS: Error: #error No fft_scalar backend selected!
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.)


-- 
980677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: espresso
Version: 6.7-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/FFTXlib'
> mpif90 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -cpp -fallow-argument-mismatch -frelease   -I/<>//include 
> -I/<>//FoX/finclude   -c fft_param.f90
> f951: Warning: command-line option ‘-frelease’ is valid for D but not for 
> Fortran
> mpif90 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -cpp -fallow-argument-mismatch -frelease   -I/<>//include 
> -I/<>//FoX/finclude   -c fft_support.f90
> f951: Warning: command-line option ‘-frelease’ is valid for D but not for 
> Fortran
> mpif90 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -cpp -fallow-argument-mismatch -frelease   -I/<>//include 
> -I/<>//FoX/finclude   -c stick_base.f90
> f951: Warning: command-line option ‘-frelease’ is valid for D but not for 
> Fortran
> mpif90 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -cpp -fallow-argument-mismatch -frelease   -I/<>//include 
> -I/<>//FoX/finclude   -c fft_types.f90
> f951: Warning: command-line option ‘-frelease’ is valid for D but not for 
> Fortran
> mpif90 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -cpp -fallow-argument-mismatch -frelease   -I/<>//include 
> -I/<>//FoX/finclude   -c scatter_mod.f90
> f951: Warning: command-line option ‘-frelease’ is valid for D but not for 
> Fortran
> mpif90 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -cpp -fallow-argument-mismatch -frelease   -I/<>//include 
> -I/<>//FoX/finclude   -c fft_scatter_2d.f90
> f951: Warning: command-line option ‘-frelease’ is valid for D but not for 
> Fortran
> mpif90 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -cpp -fallow-argument-mismatch -frelease   -I/<>//include 
> -I/<>//FoX/finclude   -c fft_buffers.f90
> f951: Warning: command-line option ‘-frelease’ is valid for D but not for 
> Fortran
> mpif90 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -cpp -fallow-argument-mismatch -frelease   -I/<>//include 
> -I/<>//FoX/finclude   -c fft_scatter_gpu.f90
> f951: Warning: command-line option ‘-frelease’ is valid for D but not for 
> Fortran
> mpif90 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -cpp -fallow-argument-mismatch -frelease   -I/<>//include 
> -I/<>//FoX/finclude   -c fft_scatter_2d_gpu.f90
> f951: Warning: command-line option ‘-frelease’ is valid for D but not for 
> Fortran
> mpif90 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -cpp -fallow-argument-mismatch -frelease   -I/<>//include 
> -I/<>//FoX/finclude   -c fft_ggen.f90
> f951: Warning: command-line option ‘-frelease’ is valid for D but not for 
> Fortran
> mpif90 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -cpp -fallow-argument-mismatch -frelease   -I/<>//include 
> -I/<>//FoX/finclude   -c fftw_interfaces.f90
> f951: Warning: command-line option ‘-frelease’ is valid for D but not for 
> Fortran
> mpif90 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -cpp -fallow-argument-mismatch -frelease   -I/<>//include 
> -I/<>//FoX/finclude   -c fft_scalar.ARM_LIB.f90
> f951: Warning: command-line option ‘-frelease’ is valid for D but not for 
> Fortran
> mpif90 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -cpp -fallow-argument-mismatch -frelease   -I/<>//include 
> -I/<>//FoX/finclude   -c fft_scalar.DFTI.f90
> f951: Warning: command-line option ‘-frelease’ is valid for D but not for 
> Fortran
> mpif90 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -cpp -fallow-argument-mismatch -frelease   -I/<>//include 
> -I/<>//FoX/finclude   -c fft_scalar.ESSL.f90
> f951: Warning: command-line option ‘-frelease’ is valid for D but not for 
> Fortran
> mpif90 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -cpp -fallow-argument-mismatch -frelease   -I/<>//include 
> -I/<>//FoX/finclude   -c fft_scalar.FFTW.f90
> f951: Warning: command-line option ‘-frelease’ is valid for D but not 

Bug#980042: Upstream has fixed the problem

[Lieven Marchand]

http://git.savannah.gnu.org/cgit/mailutils.git/commit/?id=07ee21c2db558106c8537600698db75e51ac1090

Bug#982705: openssh: FTBFS: sha2.h:57:16: error: redefinition of ‘struct _SHA2_CTX’

[Colin Watson]

On Mon, Feb 15, 2021 at 11:31:45AM +0100, Andreas Henriksson wrote:
> On Mon, Feb 15, 2021 at 09:41:30AM +, Colin Watson wrote:
> > FWIW, I think your patch in
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982705#25 is correct
> > (even if I prefer to take a different approach as a workaround for the
> > packaging) and could be forwarded upstream.  Would you mind doing that?
> > I normally prefer people to forward their own patches where possible so
> > that there's no doubt about copyright/licensing intent or whatever.
> 
> Agreed. The patch is fixing stuff in the non-portable version though
> and I couldn't figure out how to contribute to that. The only
> contribution info I could find lead to donating money to openbsd.

IME: just send it as a bug on bugzilla.mindrot.org and they sort out
which branch to apply it to.

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Bug#953093: reopen

[David Kunz]

close 953093 20190125-2
thanks

Hi,

this bug has been fixed in above version, hence closing.

Regards,
David

Processed: Re: Bug#953093: reopen

[Debian Bug Tracking System]

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

> close 953093 20190125-2
Bug #953093 [icingaweb2-module-x509] icingaweb2-module-x509 is uninstallable, 
dependency on nonexistent package
Marked as fixed in versions icingaweb2-module-x509/20190125-2.
Bug #953093 [icingaweb2-module-x509] icingaweb2-module-x509 is uninstallable, 
dependency on nonexistent package
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#982705: openssh: FTBFS: sha2.h:57:16: error: redefinition of ‘struct _SHA2_CTX’

[Andreas Henriksson]

On Mon, Feb 15, 2021 at 09:41:30AM +, Colin Watson wrote:
[...]
> FWIW, I think your patch in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982705#25 is correct
> (even if I prefer to take a different approach as a workaround for the
> packaging) and could be forwarded upstream.  Would you mind doing that?
> I normally prefer people to forward their own patches where possible so
> that there's no doubt about copyright/licensing intent or whatever.

Agreed. The patch is fixing stuff in the non-portable version though
and I couldn't figure out how to contribute to that. The only
contribution info I could find lead to donating money to openbsd.

I did however send a mail yesterday with the patch attached directly to
https://github.com/djmdjm who's seems to have been the one touching the
relevant code according to
https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/sk-usbhid.c
(and seems also being active in
https://github.com/openssh/openssh-portable ). YOLO and I'm moving on.

Regards,
Andreas Henriksson

Bug#981975: icingaweb2-module-director is uninstallable: dependency on nonexistent package

[David Kunz]

close 981975 1.8.0-1
thanks

Hi,

this bug has been fixed in above version, hence closing.

Regards,

Processed: Re: Bug#981975: icingaweb2-module-director is uninstallable: dependency on nonexistent package

[Debian Bug Tracking System]

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

> close 981975 1.8.0-1
Bug #981975 [icingaweb2-module-director] icingaweb2-module-director is 
uninstallable: dependency on nonexistent package
Marked as fixed in versions icingaweb2-module-director/1.8.0-1.
Bug #981975 [icingaweb2-module-director] icingaweb2-module-director is 
uninstallable: dependency on nonexistent package
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#977990: os-autoinst: FTBFS on i386: 3/3 Test #3: test-perl-testsuite ..............***Failed 332.81 sec

[Frédéric Bonnard]

Hi,
indeed Paul, the test is flaky, probably a timing issue. I had already
changed some related parameter that made the tests pass reliably on
my i386 builder, but saw afterward that it still failed on debian's
builder and couldn't reproduce it :
https://salsa.debian.org/debian/os-autoinst/-/commit/38b2f4aefafbdf7ab59ce223ef208c540409a001
I guess, we could increase CI related timeouts here and there but that's
what I tried to avoid when changing CI variable, and I was happy to see
things work.. but not on all i386 builders :)
May we close that bug for now ?

F.


signature.asc
Description: PGP signature

Bug#982705: marked as pending in openssh

[Colin Watson]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ssh-team/openssh/-/commit/d0cee71ebcde7400f7caa1fcbf0f997302d1528f


Avoid using libmd's  even if it's installed

Closes: #982705


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/982705