Processed: Re: Bug#1008189: meson: gnome module incorrectly requires gtk4-update-icon-cache

[Debian Bug Tracking System]

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

> affects 1008189 src:polari
Bug #1008189 [src:meson] meson: gnome module incorrectly requires 
gtk4-update-icon-cache
Added indication that 1008189 affects src:polari
>
End of message, stopping processing here.

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

Bug#1007992: marked as done (libigdgmm12: new version causes segfaults)

[Debian Bug Tracking System]

Your message dated Thu, 24 Mar 2022 23:19:09 +
with message-id 
and subject line Bug#1007992: fixed in intel-gmmlib 22.1.2+ds1-1
has caused the Debian Bug report #1007992,
regarding libigdgmm12: new version causes segfaults
to be marked as done.

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

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


-- 
1007992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007992
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libigdgmm12
Version: 22.1.1+ds1-1
Severity: critical
Justification: breaks unrelated software


Hey.


This version breaks e.g. video playback with mpv (also vlc):
$ mpv test.mp4
 (+) Video --vid=1 (h264 720x300 23.976fps)
 (+) Audio --aid=1 (aac 2ch 44100Hz)
Segmentation fault


With:
Mar 20 04:30:17 heisenberg kernel: mpv/vo[292810]: segfault at 30200 ip 
7f93a01e49ae sp 7f93ab2514b0 error 4 in 
libigdgmm.so.12.1.0[7f93a017b000+78000]
Mar 20 04:30:17 heisenberg kernel: Code: ff 4c 8b 55 c8 31 c0 b9 40 00 00 00 4c 
8b 45 b8 4c 89 fe 49 8d 92 b0 33 00 00 48 89 d7 f3 41 0f 6f 00 ba c4 06 00 00 
f3 48 ab <49> 8b 06 49 8d 7a 44 41 c7 82 b8 35 00 00 0a 00 00 00 f3 41 0f 6f
Mar 20 04:30:22 heisenberg kernel: mpv/vo[292830]: segfault at 30200 ip 
7fb5381d49ae sp 7fb53b4564b0 error 4 in 
libigdgmm.so.12.1.0[7fb53816b000+78000]
Mar 20 04:30:22 heisenberg kernel: Code: ff 4c 8b 55 c8 31 c0 b9 40 00 00 00 4c 
8b 45 b8 4c 89 fe 49 8d 92 b0 33 00 00 48 89 d7 f3 41 0f 6f 00 ba c4 06 00 00 
f3 48 ab <49> 8b 06 49 8d 7a 44 41 c7 82 b8 35 00 00 0a 00 00 00 f3 41 0f 6f
Mar 20 04:30:23 heisenberg kernel: mpv/vo[292850]: segfault at 30200 ip 
7f57901de9ae sp 7f579ea9f4b0 error 4 in 
libigdgmm.so.12.1.0[7f5790175000+78000]
Mar 20 04:30:23 heisenberg kernel: Code: ff 4c 8b 55 c8 31 c0 b9 40 00 00 00 4c 
8b 45 b8 4c 89 fe 49 8d 92 b0 33 00 00 48 89 d7 f3 41 0f 6f 00 ba c4 06 00 00 
f3 48 ab <49> 8b 06 49 8d 7a 44 41 c7 82 b8 35 00 00 0a 00 00 00 f3 41 0f 6f
Mar 20 04:30:30 heisenberg kernel: vlc[292895]: segfault at 30200 ip 
7f94f12fb9ae sp 7f94f105bb00 error 4 in 
libigdgmm.so.12.1.0[7f94f1292000+78000]
Mar 20 04:30:30 heisenberg kernel: Code: ff 4c 8b 55 c8 31 c0 b9 40 00 00 00 4c 
8b 45 b8 4c 89 fe 49 8d 92 b0 33 00 00 48 89 d7 f3 41 0f 6f 00 ba c4 06 00 00 
f3 48 ab <49> 8b 06 49 8d 7a 44 41 c7 82 b8 35 00 00 0a 00 00 00 f3 41 0f 6f
Mar 20 04:31:20 heisenberg kernel: mpv/vo[293088]: segfault at 30200 ip 
7f923547a9ae sp 7f925251a4b0 error 4 in 
libigdgmm.so.12.1.0[7f9235411000+78000]
Mar 20 04:31:20 heisenberg kernel: Code: ff 4c 8b 55 c8 31 c0 b9 40 00 00 00 4c 
8b 45 b8 4c 89 fe 49 8d 92 b0 33 00 00 48 89 d7 f3 41 0f 6f 00 ba c4 06 00 00 
f3 48 ab <49> 8b 06 49 8d 7a 44 41 c7 82 b8 35 00 00 0a 00 00 00 f3 41 0f 6f


Downgrading to 22.0.2+ds1-1 fixes the issue.


Cheers,
Chris.


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

Kernel: Linux 5.16.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libigdgmm12 depends on:
ii  libc6   2.33-7
ii  libgcc-s1   12-20220319-1
ii  libstdc++6  12-20220319-1

libigdgmm12 recommends no packages.

libigdgmm12 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: intel-gmmlib
Source-Version: 22.1.2+ds1-1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated intel-gmmlib 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 25 Mar 2022 00:04:41 +0100
Source: intel-gmmlib
Architecture: source
Version: 22.1.2+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Closes: 1007992
Changes:
 intel-gmmlib (22.1.2+ds1-1) unstable; 

Bug#1005465: marked as done (malcontent: FTBFS: cc: error: unrecognized command-line option '-Wincompatible-pointer-types-discards-qualifiers')

[Debian Bug Tracking System]

Your message dated Thu, 24 Mar 2022 22:36:38 +
with message-id 
and subject line Bug#1005465: fixed in malcontent 0.10.4-1
has caused the Debian Bug report #1005465,
regarding malcontent: FTBFS:  cc: error: unrecognized command-line option 
'-Wincompatible-pointer-types-discards-qualifiers'
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.)


-- 
1005465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: malcontent
Version: 0.10.3-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm

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_configure -- -Dprivileged_group=sudo 
> -Dpamlibdir=/lib/x86_64-linux-gnu/security -Dui=enabled
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dprivileged_group=sudo 
> -Dpamlibdir=/lib/x86_64-linux-gnu/security -Dui=enabled
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: malcontent
> Project version: 0.10.3
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency dbus-1 found: YES 1.12.20
> Run-time dependency polkit-gobject-1 found: YES 0.105
> Configuring config.h using configuration
> Compiler for C supports arguments -fno-strict-aliasing: YES 
> Compiler for C supports arguments -fstack-protector-strong: YES 
> Compiler for C supports arguments -Waggregate-return: YES 
> Compiler for C supports arguments -Wall: YES 
> Compiler for C supports arguments -Wunused: YES 
> Compiler for C supports arguments -Warray-bounds: YES 
> Compiler for C supports arguments -Wcast-align: YES 
> Compiler for C supports arguments -Wclobbered: YES 
> Compiler for C supports arguments -Wno-declaration-after-statement: YES 
> Compiler for C supports arguments -Wdiscarded-qualifiers: YES 
> Compiler for C supports arguments -Wduplicated-branches: YES 
> Compiler for C supports arguments -Wduplicated-cond: YES 
> Compiler for C supports arguments -Wempty-body: YES 
> Compiler for C supports arguments -Wformat=2: YES 
> Compiler for C supports arguments -Wformat-nonliteral: YES 
> Compiler for C supports arguments -Wformat-security: YES 
> Compiler for C supports arguments -Wformat-signedness: YES 
> Compiler for C supports arguments -Wignored-qualifiers: YES 
> Compiler for C supports arguments -Wimplicit-function-declaration: YES 
> Compiler for C supports arguments -Wincompatible-pointer-types: YES 
> Compiler for C supports arguments 
> -Wincompatible-pointer-types-discards-qualifiers: NO 
> Compiler for C supports arguments -Winit-self: YES 
> Compiler for C supports arguments -Wint-conversion: YES 
> Compiler for C supports arguments -Wlogical-op: YES 
> Compiler for C supports arguments -Wmisleading-indentation: YES 
> Compiler for C supports arguments -Wmissing-declarations: YES 
> Compiler for C supports arguments -Wmissing-format-attribute: YES 
> Compiler for C supports arguments -Wmissing-include-dirs: YES 
> Compiler for C supports arguments -Wmissing-noreturn: YES 
> Compiler for C supports arguments -Wmissing-parameter-type: YES 
> Compiler for C supports arguments -Wmissing-prototypes: YES 
> Compiler for C supports arguments -Wnested-externs: YES 
> Compiler for C supports arguments -Wno-error=cpp: YES 
> Compiler for C supports arguments -Wmissing-field-initializers: YES 
> Compiler for C supports arguments -Wno-suggest-attribute=format: YES 
> Compiler for C supports arguments -Wno-unused-parameter: YES 
> Compiler for C supports arguments -Wnull-dereference: YES 
> Compiler for C supports arguments -Wold-style-definition: YES 
> Compiler for C supports arguments -Woverflow: YES 
> Compiler for C supports arguments -Woverride-init: YES 
> Compiler for C supports arguments -Wparentheses: YES 
> Compiler for C supports arguments -Wpointer-arith: YES 
> Compiler for C supports arguments -Wredundant-decls: YES 
> Compiler for C supports arguments -Wreturn-type: YES 
> Compiler for C supports arguments -Wshadow: YES 
> Compiler for C supports arguments -Wsign-compare: YES 
> Compiler 

Bug#1007248: nodejs trying to overwrite /usr/share/systemtap/tapset/node.stp

[Jérémy Lal]

On Thu, Mar 24, 2022 at 11:15 PM Daniel Leidert  wrote:

> reopen 1007248
> thanks
>
> I just got hit by this bug as well:
>
> Entpacken von nodejs (16.13.2+really14.19.1~dfsg-5) über (12.22.9~dfsg-1)
> ...
> dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-DvPfq0/442-
> nodejs_16.13.2+really14.19.1~dfsg-5_amd64.deb (--unpack):
>  Versuch, »/usr/share/systemtap/tapset/node.stp« zu überschreiben, welches
> auch
> in Paket libnode72:amd64 12.22.9~dfsg-1 ist
>
> It seems this issue is not yet fixed or this is a regression.
>

Can you try by updating to 12.22.10~dfsg-2 before ?

Jérémy

Processed: nodejs trying to overwrite /usr/share/systemtap/tapset/node.stp

[Debian Bug Tracking System]

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

> reopen 1007248
Bug #1007248 {Done: Jérémy Lal } [nodejs] nodejs: Tries to 
overwrite a file in a different 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 nodejs/12.22.10~dfsg-2.
> thanks
Stopping processing here.

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

Bug#1007248: nodejs trying to overwrite /usr/share/systemtap/tapset/node.stp

[Daniel Leidert]

reopen 1007248
thanks

I just got hit by this bug as well:

Entpacken von nodejs (16.13.2+really14.19.1~dfsg-5) über (12.22.9~dfsg-1) ...
dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-DvPfq0/442-
nodejs_16.13.2+really14.19.1~dfsg-5_amd64.deb (--unpack):
 Versuch, »/usr/share/systemtap/tapset/node.stp« zu überschreiben, welches auch
in Paket libnode72:amd64 12.22.9~dfsg-1 ist

It seems this issue is not yet fixed or this is a regression.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#1003907: fails to successfully associate

[Masashi Honma]

> Masashi, if I understand you correctly, you argue that this is an issue
> with the AP (or its firmware).

> If so, should the company AVM be contacted about this?
> I'm afraid I'm not too knowledgeable in that regard.

Michael, Hans-Peter Jansen already reported to AVM at 2022-02-06
(https://bugzilla.opensuse.org/show_bug.cgi?id=1195395).

According to his latest comment,
"Just a heads up: AVM is still investigating on this. Some tests with
newer hardware confirmed, that WPA3 is working well there."


2022年3月25日(金) 2:48 Michael Biebl :
>
> Some more data points:
>
> Disabling NetworkManager completely and using wpasupplicant alone with
> the following config:
>
> network={
>  ssid="wgrouter"
>  psk=""
>  key_mgmt=WPA-PSK
>  id_str="wgrouter"
> }
>
> does indeed work.
>
> As soon as I enable NetworkManager though, my connection fails, even
> though /etc/NetworkManager/system-connections/wgrouter.nmconnection
> contains
>
> [wifi-security]
> key-mgmt=wpa-psk
> psk=
>
> In journalctl -u NetworkManager I see
>
> Mär 21 11:15:07 pluto NetworkManager[2450]:   [1647857707.7752]
> Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
>
>
> Ľubomír, is there a way how I can tell NetworkManager to *not* use SAE?
>
>
>
> Am 21.03.22 um 09:38 schrieb Andrej Shadura:
> > Hi,
> >
> > On Sun, 20 Mar 2022, at 00:23, Masashi Honma wrote:
> >> In my opinion, this issue could be closed.
> >>
> >> These are reasons.
> >> 1) It is not wpa_supplicant issue but AP issue.
> >> 2) Users affected by this issue have some workarounds.
> >
> > It’s true, but I’m not quite happy about not being able to fix this.
> >
> > Ľubomír (cc'ed), how did you deal with this issue in Fedora? I assume you 
> > must also have received reports from Fritzbox users.
> >
> >> Details of the 1)
> >> The investigation has revealed that the AP is in violation of "2.3
> >> WPA3-Personal transition mode" of the "WPA3 Specification v3.0", which
> >> is causing the issue. Specifically, the target AP is setting MFPR to 1
> >> even though it implicitly requires IEEE 802.11w. By "implicitly" we
> >> mean that the Assocation Request fails with WLAN_STATUS_INVALID_IE
> >> when using a Wi-Fi NIC with IEEE 802.11w disabled.
> >>
> >>
> >> Details of the 2)
> >> We know that users who meet the following conditions are affected by this 
> >> issue.
> >> - Using FRITZ!Box 7580/7590 with WPA2+WPA3 mode
>
> I've tested it with both 7490 and 7530 AX, fwiw.
>
> >> - Using wpa_supplicant with wpa_key_mgmt=SAE WPA-PSK
> >> - Local Wi-Fi NIC does not support IEEE802.11w
> >>
> >> Users affected by this issue can work around the issue in one of the
> >> following ways.
> >> - Use wpa_supplicant with WPA2 only mode (specify wpa_key_mgmt=WPA-PSK)
> >> - Use FRITZ!Box 7580/7590 with WPA2 only mode
> >> - Use IEEE 802.11w supporting Wi-Fi NIC
> >
>
> Masashi, if I understand you correctly, you argue that this is an issue
> with the AP (or its firmware).
>
> If so, should the company AVM be contacted about this?
> I'm afraid I'm not too knowledgeable in that regard.
> ___
> Hostap mailing list
> hos...@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/hostap

Bug#1001367: marked as done (pyeapi: (autopkgtest) needs update for python3.10: 'collections' has no attribute 'Iterable')

[Debian Bug Tracking System]

Your message dated Thu, 24 Mar 2022 20:41:51 +
with message-id 
and subject line Bug#1001367: fixed in pyeapi 0.8.4-1
has caused the Debian Bug report #1001367,
regarding pyeapi: (autopkgtest) needs update for python3.10: 'collections' has 
no attribute 'Iterable'
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.)


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

Source: pyeapi
Version: 0.8.1-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python2.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of pyeapi fails in testing when that autopkgtest is run with the binary 
packages of python3-defaults from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.9.8-1
pyeapi from testing0.8.1-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists 
what's new in Python2.10, it may help to identify what needs to be updated.

https://docs.python.org/3.9/library/collections.html says:
"""
Deprecated since version 3.3, will be removed in version 3.10: Moved 
Collections Abstract Base Classes to the collections.abc module. For 
backwards compatibility, they continue to be visible in this module 
through Python 3.9.

"""
Time to move on.

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pyeapi/17393446/log.gz

Testing with python3.10:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/pyeapi/__init__.py", line 36, in 


from .client import load_config, connect, connect_to, config_for
  File "/usr/lib/python3/dist-packages/pyeapi/client.py", line 315, in 


config = Config()
  File "/usr/lib/python3/dist-packages/pyeapi/client.py", line 145, in 
__init__

self.autoload()
  File "/usr/lib/python3/dist-packages/pyeapi/client.py", line 173, in 
autoload

path = make_iterable(path)
  File "/usr/lib/python3/dist-packages/pyeapi/utils.py", line 190, in 
make_iterable

if not isinstance(value, collections.Iterable):
AttributeError: module 'collections' has no attribute 'Iterable'
autopkgtest [12:12:26]: test autodep8-python3



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pyeapi
Source-Version: 0.8.4-1
Done: Stefano Rivera 

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated pyeapi 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: Thu, 24 Mar 2022 15:50:16 -0400
Source: pyeapi
Architecture: source
Version: 0.8.4-1
Distribution: unstable
Urgency: medium
Maintainer: Vincent Bernat 
Changed-By: Stefano Rivera 
Closes: 1001367
Changes:
 pyeapi (0.8.4-1) unstable; urgency=medium
 .
   [ Stefano Rivera ]
   * Team upload.
   * New upstream release.
   * Patch: Python 3.10 support. (Closes: #1001367)
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Sandro Tosi ]
   * Use the new Debian Python Team contact name and address
Checksums-Sha1:
 891a1b0f7d33a413a2a53f045d81c6616bbe9b72 1562 pyeapi_0.8.4-1.dsc
 fb60e2e7be2a68c209b4c4c6e79d643ca1a1051e 138140 pyeapi_0.8.4.orig.tar.gz
 

Processed: stimfit: diff for NMU version 0.16.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 948020 + patch
Bug #948020 [src:stimfit] stimfit: b-d on python3-all-dev, but not built for 
all supported Python3 versions
Bug #972423 [src:stimfit] b-d's on python3-all-dev, but only builds for the 
default python3
Added tag(s) patch.
Added tag(s) patch.

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

Bug#1004509: marked as done (pyfai: autopkgtest regression on armhf: images have different dimensions)

[Debian Bug Tracking System]

Your message dated Thu, 24 Mar 2022 19:34:03 +
with message-id 
and subject line Bug#1004509: fixed in pyfai 0.21.3+dfsg1-1
has caused the Debian Bug report #1004509,
regarding pyfai: autopkgtest regression on armhf: images have different 
dimensions
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.)


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

Source: pyfai
Version: 0.21.0+dfsg1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
pyfai  from testing0.21.0+dfsg1-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/armhf/p/pyfai/18797397/log.gz

==
FAIL: test_count_csr (pyFAI.test.test_histogram.TestHistogram2d)
Test that the pixel count and the total intensity is conserved
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pyFAI/test/test_histogram.py", 
line 337, in test_count_csr

self.assertTrue(delta == 0, msg="check all pixels were counted")
AssertionError: False is not true : check all pixels were counted

==
FAIL: test_numpy_vs_cython_vs_csr_2d 
(pyFAI.test.test_histogram.TestHistogram2d)

Compare numpy histogram with cython simple implementation
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pyFAI/test/test_histogram.py", 
line 370, in test_numpy_vs_cython_vs_csr_2d
self.assertTrue(delta_max <= self.err_max_cnt, "pixel count 
difference numpy/csr : max delta=%s" % delta_max)
AssertionError: False is not true : pixel count difference numpy/csr : 
max delta=8.0


==
FAIL: test_2d_nosplit (pyFAI.test.test_csr.TestCSR)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pyFAI/test/test_csr.py", line 
193, in test_2d_nosplit

self.assertLess(error.mean(), 1e-3, "img are almost the same")
AssertionError: 244.15215998872887 not less than 0.001 : img are almost 
the same


--
Ran 375 tests in 138.562s

FAILED (failures=3, skipped=9)
60
44
23
autopkgtest [08:17:51]: test command1



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pyfai
Source-Version: 0.21.3+dfsg1-1
Done: Picca Frédéric-Emmanuel 

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated pyfai 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: Thu, 24 Mar 2022 20:11:09 +0100
Source: pyfai
Architecture: source
Version: 0.21.3+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PaN Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Closes: 1004509
Changes:
 pyfai (0.21.3+dfsg1-1) unstable; urgency=medium
 .
   * New upstream version 0.21.3+dfsg1
   * Bug fix: 

Bug#948020: stimfit: diff for NMU version 0.16.0-1.1

[Stefano Rivera]

Control: tags 948020 + patch

Dear maintainer,

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

Regards.

SR
diff -Nru stimfit-0.16.0/debian/changelog stimfit-0.16.0/debian/changelog
--- stimfit-0.16.0/debian/changelog	2019-11-26 03:35:41.0 -0400
+++ stimfit-0.16.0/debian/changelog	2022-03-24 15:29:58.0 -0400
@@ -1,3 +1,11 @@
+stimfit (0.16.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build-depend on python3-dev instead of python3-all-dev (Closes: #948020)
+  * Patch: Avoid a deprecation warning breaking autoconf with Python 3.10.
+
+ -- Stefano Rivera   Thu, 24 Mar 2022 15:29:58 -0400
+
 stimfit (0.16.0-1) unstable; urgency=low
 
   * Upgrade to Python 3 (Closes: #938572)
diff -Nru stimfit-0.16.0/debian/control stimfit-0.16.0/debian/control
--- stimfit-0.16.0/debian/control	2019-11-26 03:35:41.0 -0400
+++ stimfit-0.16.0/debian/control	2022-03-24 15:29:25.0 -0400
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Christoph Schmidt-Hieber 
 Uploaders: Yaroslav Halchenko 
-Build-Depends: debhelper (>= 9), dh-python, libboost-dev (>= 1.40.0), python3-all-dev, python3-numpy, libhdf5-dev, swig, python3-sip-dev, python3-wxgtk4.0 (>= 4.0.7), libwxgtk3.0-gtk3-dev, libfftw3-dev, liblapack-dev, chrpath, help2man, libsuitesparse-dev, zlib1g-dev, dh-autoreconf, pkg-config
+Build-Depends: debhelper (>= 9), dh-python, libboost-dev (>= 1.40.0), python3-dev, python3-numpy, libhdf5-dev, swig, python3-sip-dev, python3-wxgtk4.0 (>= 4.0.7), libwxgtk3.0-gtk3-dev, libfftw3-dev, liblapack-dev, chrpath, help2man, libsuitesparse-dev, zlib1g-dev, dh-autoreconf, pkg-config
 Standards-Version: 3.9.8
 Homepage: http://www.stimfit.org
 
diff -Nru stimfit-0.16.0/debian/patches/python3.10.patch stimfit-0.16.0/debian/patches/python3.10.patch
--- stimfit-0.16.0/debian/patches/python3.10.patch	1969-12-31 20:00:00.0 -0400
+++ stimfit-0.16.0/debian/patches/python3.10.patch	2022-03-24 15:29:54.0 -0400
@@ -0,0 +1,16 @@
+Description: check success of import by return code rather than by stderr
+Origin: upstream, https://github.com/autoconf-archive/autoconf-archive/commit/883a2abd5af5c96be894d5ef7ee6e9a2b8e64307
+Author: Igor Gnatenko 
+Last-Update: 2017-03-14
+
+--- a/m4/acsite.m4
 b/m4/acsite.m4
+@@ -66,7 +66,7 @@
+ #
+ AC_MSG_CHECKING([for the distutils Python package])
+ ac_distutils_result=`$PYTHON -c "import distutils" 2>&1`
+-if test -z "$ac_distutils_result"; then
++if test $? -eq 0; then
+ AC_MSG_RESULT([yes])
+ else
+ AC_MSG_RESULT([no])
diff -Nru stimfit-0.16.0/debian/patches/series stimfit-0.16.0/debian/patches/series
--- stimfit-0.16.0/debian/patches/series	1969-12-31 20:00:00.0 -0400
+++ stimfit-0.16.0/debian/patches/series	2022-03-24 15:29:54.0 -0400
@@ -0,0 +1 @@
+python3.10.patch

Bug#1001367: marked as pending in pyeapi

[Stefano Rivera]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/pyeapi/-/commit/2cb8b816a5c05fdc269ebba84d689558c1f9cc40


Patch: Python 3.10 support. (Closes: #1001367)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1001367

Processed: Bug#1001367 marked as pending in pyeapi

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1001367 [src:pyeapi] pyeapi: (autopkgtest) needs update for python3.10: 
'collections' has no attribute 'Iterable'
Ignoring request to alter tags of bug #1001367 to the same tags previously set

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

Processed: bug 1001367 is forwarded to https://github.com/arista-eosplus/pyeapi/issues/195

[Debian Bug Tracking System]

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

> forwarded 1001367 https://github.com/arista-eosplus/pyeapi/issues/195
Bug #1001367 [src:pyeapi] pyeapi: (autopkgtest) needs update for python3.10: 
'collections' has no attribute 'Iterable'
Set Bug forwarded-to-address to 
'https://github.com/arista-eosplus/pyeapi/issues/195'.
> thanks
Stopping processing here.

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

Bug#999209: marked as done (mp3burn: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Thu, 24 Mar 2022 18:34:40 +
with message-id 
and subject line Bug#999209: fixed in mp3burn 0.4.2-3
has caused the Debian Bug report #999209,
regarding mp3burn: missing required debian/rules targets build-arch and/or 
build-indep
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.)


-- 
999209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999209
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mp3burn
Version: 0.4.2-2.3
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: mp3burn
Source-Version: 0.4.2-3
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated mp3burn 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: Thu, 24 Mar 2022 14:18:04 -0400
Source: mp3burn
Architecture: source
Version: 0.4.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Boyuan Yang 
Closes: 965731 999209
Changes:
 mp3burn (0.4.2-3) unstable; urgency=medium
 .
   * QA upload.
   * Orphan the package.
   * debian/: Apply wrap-and-sort -abst.
   * debian/control:
 + Add SourceForge homepage.
 + Use correct Vcs-* URLs.
 + Bump debhelper compat to v13. (Closes: #965731)
   * debian/source/format: Use "3.0 (quilt)".
   * debian/patches: Include all debian patches.
   * debian/rules: Rewrite with dh. (Closes: #999209)
Checksums-Sha1:
 b92cfc464694717f70234765687a1cb12d7659b4 1825 mp3burn_0.4.2-3.dsc
 ee0b9047a22606719f7a0931df106d91af1c9aef 17166 mp3burn_0.4.2.orig.tar.gz
 3cf68a9f0235e768dc6a95bfe50c7b3baac760e0 13452 mp3burn_0.4.2-3.debian.tar.xz
 d2e48dc4001991d630a3231f957e4af9a3733487 5722 mp3burn_0.4.2-3_amd64.buildinfo
Checksums-Sha256:
 5f383f8bef65734e7aa92900ca88e671c58d69e29634130adb0ef29bbedba974 1825 
mp3burn_0.4.2-3.dsc
 062f214dbd93636e0787cd2cff50344422b28ad56b399b11c0d7e737a245b901 17166 
mp3burn_0.4.2.orig.tar.gz
 d0aa0812e92b85e1591587ea880b52fda11690f953663bb50bf9483b8e14ffb4 13452 
mp3burn_0.4.2-3.debian.tar.xz
 5696aa106915b78d9996d98fb94ca3282ead5050abe6e71bd2622772d5f1d436 5722 
mp3burn_0.4.2-3_amd64.buildinfo
Files:
 c1acb7a7387ddeb484d87efa7a29fd40 1825 sound optional mp3burn_0.4.2-3.dsc
 7e9f47227e67d6f756288e796dc3f22b 17166 sound optional mp3burn_0.4.2.orig.tar.gz
 b6f2365a299c7d49ab006a7d418af96c 13452 sound optional 
mp3burn_0.4.2-3.debian.tar.xz
 48bd7c01f6c83f32b5bf4f6bce292af8 5722 sound optional 
mp3burn_0.4.2-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmI8tiIACgkQwpPntGGC
Ws6aIg/+IlkddVJyuS7v2P1Xy5HVnSCSxgiTvDQi4KtWzuBlQed5ptflMJd+ZWPo
mRoofPZp7ZG5B3uGTjtep/Ee/mzX8drZKNY/SiEWB4bw58eIQ6Msgl+pNgGcEKXT
VvUBmREmHXl3ruKWA5ba4NSzCqY++Y81QvZZjUirwXQbSTyjDU1rjOXJyKMpBoPJ
4Owrt91PvoCh71NV72blD0ssXtWxHkXM04P0kBYjsWeALj3yth5ELiS7RDEI0T+j
gAk/Kgs/5DMgXnXpl/sv8AZWh+98Yf0a2y/0JEVs1a6IyeVlgp/ZgYDaHkrmZopg
D6Ah3IAqUoZiSimdK0NxJWc6mhCdOAS2FQKO8h0fhgEsrvQGYuyRlSjV9ulb18BK
gesxgudxCBpIdUxXrF8YNN3kBx0uYRjGL141NpLu5qrwLJ7WERcTddqu+9ZSkIaM
0adnCrx2sAbTZbxQ3viENOR7d6jsVmDSXaagmxiiZRQC9/yqktp3i1IYZkZAsA5D
9R0PIsIH7JDi9n+3JWOo6WKNvhLrLBRFUR1IJBwjrp2msmltfIOvNe16EgMOoMxE
v9Cy3BQ6p/RrECw+J7gS0/DLK1uIrPFdlzZ+fxJAMI1hb9J0LM/FEKjIAfmm4vJq

Bug#965731: marked as done (mp3burn: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Thu, 24 Mar 2022 18:34:40 +
with message-id 
and subject line Bug#965731: fixed in mp3burn 0.4.2-3
has caused the Debian Bug report #965731,
regarding mp3burn: Removal of obsolete debhelper compat 5 and 6 in bookworm
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.)


-- 
965731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mp3burn
Version: 0.4.2-2.3
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package mp3burn uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: mp3burn
Source-Version: 0.4.2-3
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated mp3burn 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: Thu, 24 Mar 2022 14:18:04 -0400
Source: mp3burn
Architecture: source
Version: 0.4.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Boyuan Yang 
Closes: 965731 999209
Changes:
 mp3burn (0.4.2-3) unstable; urgency=medium
 .
   * QA upload.
   * Orphan the package.
   * debian/: Apply wrap-and-sort -abst.
   * debian/control:
 + Add SourceForge homepage.
 + Use correct Vcs-* URLs.
 + Bump debhelper compat to v13. (Closes: #965731)
   * debian/source/format: Use "3.0 (quilt)".
   * debian/patches: Include all debian patches.
   * debian/rules: Rewrite with dh. (Closes: #999209)
Checksums-Sha1:
 b92cfc464694717f70234765687a1cb12d7659b4 1825 mp3burn_0.4.2-3.dsc
 ee0b9047a22606719f7a0931df106d91af1c9aef 17166 mp3burn_0.4.2.orig.tar.gz
 3cf68a9f0235e768dc6a95bfe50c7b3baac760e0 13452 mp3burn_0.4.2-3.debian.tar.xz
 d2e48dc4001991d630a3231f957e4af9a3733487 5722 mp3burn_0.4.2-3_amd64.buildinfo
Checksums-Sha256:
 5f383f8bef65734e7aa92900ca88e671c58d69e29634130adb0ef29bbedba974 1825 
mp3burn_0.4.2-3.dsc
 062f214dbd93636e0787cd2cff50344422b28ad56b399b11c0d7e737a245b901 17166 
mp3burn_0.4.2.orig.tar.gz
 d0aa0812e92b85e1591587ea880b52fda11690f953663bb50bf9483b8e14ffb4 13452 
mp3burn_0.4.2-3.debian.tar.xz
 5696aa106915b78d9996d98fb94ca3282ead5050abe6e71bd2622772d5f1d436 5722 
mp3burn_0.4.2-3_amd64.buildinfo
Files:
 c1acb7a7387ddeb484d87efa7a29fd40 1825 sound optional mp3burn_0.4.2-3.dsc
 7e9f47227e67d6f756288e796dc3f22b 17166 sound optional mp3burn_0.4.2.orig.tar.gz
 b6f2365a299c7d49ab006a7d418af96c 13452 sound optional 
mp3burn_0.4.2-3.debian.tar.xz
 48bd7c01f6c83f32b5bf4f6bce292af8 5722 sound optional 
mp3burn_0.4.2-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmI8tiIACgkQwpPntGGC
Ws6aIg/+IlkddVJyuS7v2P1Xy5HVnSCSxgiTvDQi4KtWzuBlQed5ptflMJd+ZWPo
mRoofPZp7ZG5B3uGTjtep/Ee/mzX8drZKNY/SiEWB4bw58eIQ6Msgl+pNgGcEKXT
VvUBmREmHXl3ruKWA5ba4NSzCqY++Y81QvZZjUirwXQbSTyjDU1rjOXJyKMpBoPJ
4Owrt91PvoCh71NV72blD0ssXtWxHkXM04P0kBYjsWeALj3yth5ELiS7RDEI0T+j
gAk/Kgs/5DMgXnXpl/sv8AZWh+98Yf0a2y/0JEVs1a6IyeVlgp/ZgYDaHkrmZopg

Bug#1001372: marked as pending in python-aiosmtpd

[Stefano Rivera]

Hi 1001372-submitter (2022.03.24_14:27:17_-0400)
> 
> Depend on python3-all for the autopkgtest. (Closes: #1001372)
> 

That was the easy bit. Then the package FTBFS because of incompatibility
with 3.10: https://github.com/aio-libs/aiosmtpd/issues/277

There are a few PRs upstream claiming to fix this, but none of them
looks obviously correct. This needs more investigation.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Processed: Bug#1001372 marked as pending in python-aiosmtpd

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1001372 [src:python-aiosmtpd] python-aiosmtpd: autopkgtest tests for all 
supported python3s but fails to install them
Added tag(s) pending.

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

Bug#1001372: marked as pending in python-aiosmtpd

[Stefano Rivera]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-aiosmtpd/-/commit/2abdee511d672a18983db4ae9039386b52929fc0


Depend on python3-all for the autopkgtest. (Closes: #1001372)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1001372

Bug#1001291: binoculars: diff for NMU version 0.0.10-1.1

[Stefano Rivera]

Control: tags 1001291 + patch
Control: tags 1001291 + pending

Dear maintainer,

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

Also filed as: 
https://salsa.debian.org/science-team/binoculars/-/merge_requests/1

Regards.

SR
diff -Nru binoculars-0.0.10/debian/changelog binoculars-0.0.10/debian/changelog
--- binoculars-0.0.10/debian/changelog	2021-12-20 04:48:28.0 -0400
+++ binoculars-0.0.10/debian/changelog	2022-03-24 14:00:50.0 -0400
@@ -1,3 +1,11 @@
+binoculars (0.0.10-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Bug fix: Run the autopkgtest only against the supported version of
+Python 3 (Closes: #1001291).
+
+ -- Stefano Rivera   Thu, 24 Mar 2022 14:00:50 -0400
+
 binoculars (0.0.10-1) unstable; urgency=medium
 
   [ Neil Williams ]
diff -Nru binoculars-0.0.10/debian/tests/control binoculars-0.0.10/debian/tests/control
--- binoculars-0.0.10/debian/tests/control	2021-12-20 04:48:28.0 -0400
+++ binoculars-0.0.10/debian/tests/control	2022-03-24 14:00:50.0 -0400
@@ -1,10 +1,7 @@
 Test-Command: set -efu
  ; cp -r tests examples "$AUTOPKGTEST_TMP"
- ; for py in $(py3versions -r 2>/dev/null)
- ; do cd "$AUTOPKGTEST_TMP"
- ; echo "Testing with $py:"
- ; $py -m unittest discover -s tests -v
- ; done
+ ; cd "$AUTOPKGTEST_TMP"
+ ; python3 -m unittest discover -s tests -v
 Depends:
  python3,
  python3-binoculars,

Processed: binoculars: diff for NMU version 0.0.10-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1001291 + patch
Bug #1001291 [src:binoculars] binoculars: autopkgtest tests for all supported 
python3 versions but vtk7 extensions don't exist for all
Added tag(s) patch.
> tags 1001291 + pending
Bug #1001291 [src:binoculars] binoculars: autopkgtest tests for all supported 
python3 versions but vtk7 extensions don't exist for all
Added tag(s) pending.

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

Bug#1001484: sfepy: (autopkgtest) needs update for python3.10: Sequence' from 'collections' is removed

[Anton Gladky]

I will do it ASAP

Anton

Am Do., 24. März 2022 um 18:54 Uhr schrieb Stefano Rivera :
>
> Control: tag -1 + pending
>
> I see a commit fixing this in git, just waiting to be uploaded.
> https://salsa.debian.org/science-team/sfepy/-/commit/f6a4f8d2435e8406a629a75ee89891a24631233a
>
> SR
>
> --
> Stefano Rivera
>   http://tumbleweed.org.za/
>   +1 415 683 3272

Processed: Re: Bug#1001484: sfepy: (autopkgtest) needs update for python3.10: Sequence' from 'collections' is removed

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending
Bug #1001484 [src:sfepy] sfepy: (autopkgtest) needs update for python3.10: 
Sequence' from 'collections' is removed
Added tag(s) pending.

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

Bug#1001484: sfepy: (autopkgtest) needs update for python3.10: Sequence' from 'collections' is removed

[Stefano Rivera]

Control: tag -1 + pending

I see a commit fixing this in git, just waiting to be uploaded.
https://salsa.debian.org/science-team/sfepy/-/commit/f6a4f8d2435e8406a629a75ee89891a24631233a

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#1008225: dolfin: autopkgtest failure: timeout

[Sebastian Ramacher]

Source: dolfin
Version: 2019.2.0~git20210928.3eacdb4-3
Severity: serious
Tags: sid bookworm

dolfin's autopkgtest fail with a timeout:

python/demo/test.py::test_demos[path45-demo_meshview-3D1D.py] autopkgtest 
[15:52:40]: ERROR: timed out on command "su -s /bin/bash debci -c set -e; 
export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || true;  . ~/.profile 
>/dev/null 2>&1 || true; 
buildtree="/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/build.bBU/src"; mkdir -p -m 
1777 -- 
"/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/test-dolfin-python-demo-artifacts"; 
export 
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/test-dolfin-python-demo-artifacts";
 export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 
"/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/autopkgtest_tmp"; export 
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/autopkgtest_tmp"; export 
ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; export 
LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=56; unset LANGUAGE LC_CTYPE 
LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME 
LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION LC_ALL;rm -f 
/tmp/autopkgtest_script_pid; set -C; echo $$ > /tmp/autopkgtest_script_pid; set 
+C; trap "rm -f /tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd 
"$buildtree"; chmod +x 
/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/build.bBU/src/debian/tests/test-dolfin-python-demo;
 touch /tmp/autopkgtest-lxc.1ddrdd8w/downtmp/test-dolfin-python-demo-stdout 
/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/test-dolfin-python-demo-stderr; 
/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/build.bBU/src/debian/tests/test-dolfin-python-demo
 2> >(tee -a 
/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/test-dolfin-python-demo-stderr >&2) > 
>(tee -a 
/tmp/autopkgtest-lxc.1ddrdd8w/downtmp/test-dolfin-python-demo-stdout);" (kind: 
test)
autopkgtest [15:52:40]: test test-dolfin-python-demo: ---]
autopkgtest [15:52:40]: test test-dolfin-python-demo:  - - - - - - - - - - 
results - - - - - - - - - -
test-dolfin-python-demo FAIL timed out


See
https://ci.debian.net/data/autopkgtest/testing/amd64/d/dolfin/20301057/log.gz

Cheers
-- 
Sebastian Ramacher

Processed: severity of 1008222 is important, fixed 1008222 in 1:2.2.7-1~bpo11+1

[Debian Bug Tracking System]

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

> severity 1008222 important
Bug #1008222 [keepalived] bind unicast_src x.y.z.w failed 99 - Cannot assign 
requested address
Severity set to 'important' from 'grave'
> fixed 1008222 1:2.2.7-1~bpo11+1
Bug #1008222 [keepalived] bind unicast_src x.y.z.w failed 99 - Cannot assign 
requested address
Marked as fixed in versions keepalived/1:2.2.7-1~bpo11+1.
> thanks
Stopping processing here.

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

Bug#1008222: bind unicast_src x.y.z.w failed 99 - Cannot assign requested address

[Vincent Bernat]

severity -1 important
fixed -1 1:2.2.7-1~bpo11+1
thanks

 ❦ 24 March 2022 17:24 +01, Arturo Borrero Gonzalez:

> This exact same setup was previously working, and actually, the next version 
> works just fine.
> Not sure if this has anything to do with the kernel version warning at the 
> beginning.
>
> In summary:
>
> | keepalived version  | Debian   | Works? |
> | |--||
> | 1:2.0.10-1  | buster   | yes|
> | 1:2.1.5-0.2+deb11u1 | bullseye | no |
> | 1:2.2.7-1~bpo11+1   | bullseye-bpo | yes|
>
> I'm opeining this bug report mostly so others can find it.
> Raelly appreciated the bpo package is ready to use.

Glad that the backport solves this issue. Unfortunately, I don't think
it's worth reporting the issue upstream as they don't like us lagging so
many versions late. I have used it myself with unicast_src, so it is not
broken for everyone.

After looking twice, I notice the VIP is in the same subnet as the peer.
If you don't have any other address on the subnet, I don't see how this
could work. If you have, maybe it would be better to use a /32 for the
VIP.
-- 
If one cannot enjoy reading a book over and over again, there is no use
in reading it at all.
-- Oscar Wilde

Bug#1007826: marked as done (asdf-astropy: autopkgtest regression: 'cannot represent an object',

[Debian Bug Tracking System]

Your message dated Thu, 24 Mar 2022 16:48:48 +
with message-id 
and subject line Bug#1007826: fixed in asdf-astropy 0.2.0-2
has caused the Debian Bug report #1007826,
regarding asdf-astropy: autopkgtest regression: 'cannot represent an object', 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: asdf-astropy
Version: 0.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
asdf-astropy   from testing0.2.0-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/a/asdf-astropy/20034163/log.gz


=== FAILURES 
===
__ test_single_model[model35] 
__


tmpdir = local('/tmp/pytest-of-debci/pytest-0/test_single_model_model35_0')
model = 

@pytest.mark.parametrize("model", create_single_models())
def test_single_model(tmpdir, model):

  assert_model_roundtrip(model, tmpdir)


/usr/lib/python3/dist-packages/asdf_astropy/converters/transform/tests/test_transform.py:383: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ 
/usr/lib/python3/dist-packages/asdf_astropy/converters/transform/tests/test_transform.py:37: 
in assert_model_roundtrip

af.write_to(path)
/usr/lib/python3/dist-packages/asdf/asdf.py:1313: in write_to
self._serial_write(fd, pad_blocks, include_block_index)
/usr/lib/python3/dist-packages/asdf/asdf.py:1065: in _serial_write
self._write_tree(self._tree, fd, pad_blocks)
/usr/lib/python3/dist-packages/asdf/asdf.py:1038: in _write_tree
yamlutil.dump_tree(
/usr/lib/python3/dist-packages/asdf/yamlutil.py:402: in dump_tree
yaml.dump_all(
/usr/lib/python3/dist-packages/yaml/__init__.py:278: in dump_all
dumper.represent(data)
/usr/lib/python3/dist-packages/yaml/representer.py:27: in represent
node = self.represent_data(data)
/usr/lib/python3/dist-packages/asdf/yamlutil.py:43: in represent_data
node = super(AsdfDumper, self).represent_data(data)
/usr/lib/python3/dist-packages/yaml/representer.py:48: in represent_data
node = self.yaml_representers[data_types[0]](self, data)
/usr/lib/python3/dist-packages/asdf/yamlutil.py:63: in represent_mapping
node = super(AsdfDumper, dumper).represent_mapping(None, 
mapping.data, flow_style)

/usr/lib/python3/dist-packages/yaml/representer.py:118: in represent_mapping
node_value = self.represent_data(item_value)
/usr/lib/python3/dist-packages/asdf/yamlutil.py:43: in represent_data
node = super(AsdfDumper, self).represent_data(data)
/usr/lib/python3/dist-packages/yaml/representer.py:58: in represent_data
node = self.yaml_representers[None](self, data)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

self = 
data = 

def represent_undefined(self, data):

  raise RepresenterError("cannot represent an object", data)
E   yaml.representer.RepresenterError: ('cannot represent an 
object', )


/usr/lib/python3/dist-packages/yaml/representer.py:231: RepresenterError
__ test_single_model[model36] 
__


tmpdir = local('/tmp/pytest-of-debci/pytest-0/test_single_model_model36_0')
model = 

@pytest.mark.parametrize("model", create_single_models())
def test_single_model(tmpdir, model):

  assert_model_roundtrip(model, tmpdir)


/usr/lib/python3/dist-packages/asdf_astropy/converters/transform/tests/test_transform.py:383: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ 
/usr/lib/python3/dist-packages/asdf_astropy/converters/transform/tests/test_transform.py:37: 
in assert_model_roundtrip

af.write_to(path)
/usr/lib/python3/dist-packages/asdf/asdf.py:1313: in write_to
self._serial_write(fd, pad_blocks, include_block_index)
/usr/lib/python3/dist-packages/asdf/asdf.py:1065: in _serial_write
self._write_tree(self._tree, fd, pad_blocks)
/usr/lib/python3/dist-packages/asdf/asdf.py:1038: in _write_tree
yamlutil.dump_tree(
/usr/lib/python3/dist-packages/asdf/yamlutil.py:402: in dump_tree
yaml.dump_all(

Bug#1008222: bind unicast_src x.y.z.w failed 99 - Cannot assign requested address

[Arturo Borrero Gonzalez]

Package: keepalived
Version: 1:2.1.5-0.2+deb11u1
Severity: grave
Tags: upstream
X-Debbugs-Cc: art...@debian.org

Dear maintainer,

thanks for your work with this package, really appreciated.

Today I tried upgrading a Debian 10 Buster system to Debian 11 Bullseye.

Keepalived refused to work with a previously working setup, error message:

=== 8< ===
aborrero@cloudgw2001-dev:~ $ sudo /usr/sbin/keepalived -lD --dont-fork
Thu Mar 24 15:59:24 2022: Starting Keepalived v2.1.5 (07/13,2020)
Thu Mar 24 15:59:24 2022: WARNING - keepalived was build for newer Linux 
5.10.70, running on Linux 5.10.0-12-amd64 #1 SMP Debian 5.10.103-1 (2022-03-07)
Thu Mar 24 15:59:24 2022: Command line: '/usr/sbin/keepalived' '-lD' 
'--dont-fork'
Thu Mar 24 15:59:24 2022: Opening file '/etc/keepalived/keepalived.conf'.
Thu Mar 24 15:59:24 2022: NOTICE: setting config option max_auto_priority 
should result in better keepalived performance
Thu Mar 24 15:59:24 2022: Starting VRRP child process, pid=17238
Thu Mar 24 15:59:24 2022: Registering Kernel netlink reflector
Thu Mar 24 15:59:24 2022: Registering Kernel netlink command channel
Thu Mar 24 15:59:24 2022: Opening file '/etc/keepalived/keepalived.conf'.
Thu Mar 24 15:59:24 2022: (/etc/keepalived/keepalived.conf: Line 25) Warning - 
cannot track route 185.15.57.0/29 with no interface specified, not tracking
Thu Mar 24 15:59:24 2022: (/etc/keepalived/keepalived.conf: Line 26) Warning - 
cannot track route 172.16.128.0/24 with no interface specified, not tracking
Thu Mar 24 15:59:24 2022: Assigned address 208.80.153.188 for interface 
eno2.2120
Thu Mar 24 15:59:24 2022: Assigned address fe80::32e1:71ff:fe60:e97d for 
interface eno2.2120
Thu Mar 24 15:59:24 2022: Registering gratuitous ARP shared channel
Thu Mar 24 15:59:24 2022: (VRRP1) removing Virtual Routes
Thu Mar 24 15:59:24 2022: (VRRP1) removing VIPs.
Thu Mar 24 15:59:24 2022: bind unicast_src 208.80.153.188 failed 99 - Cannot 
assign requested address
Thu Mar 24 15:59:24 2022: (VRRP1): entering FAULT state (src address not 
configured)
Thu Mar 24 15:59:24 2022: (VRRP1) Entering FAULT STATE
Thu Mar 24 15:59:24 2022: (VRRP1) removing Virtual Routes
Thu Mar 24 15:59:24 2022: VRRP sockpool: [ifindex(  8), family(IPv4), 
proto(112), fd(-1,-1), unicast, address(208.80.153.188)]
^CThu Mar 24 16:00:05 2022: Stopping
Thu Mar 24 16:00:06 2022: Stopped - used 0.002007 user time, 0.00 system 
time
Thu Mar 24 16:00:06 2022: CPU usage (self/children) user: 0.008240/0.003615 
system: 0.004120/0.00
Thu Mar 24 16:00:06 2022: Stopped Keepalived v2.1.5 (07/13,2020)
=== 8< ===

The config file is pretty straigt forward:

=== 8< ===
aborrero@cloudgw2001-dev:~ $ cat /etc/keepalived/keepalived.conf
global_defs {
}

vrrp_instance VRRP1 {
  state BACKUP
  interface eno2.2120
  virtual_router_id 52
  nopreempt
  priority 6
  advert_int 1
  authentication {
auth_type PASS
auth_pass 
  }
  track_interface {
eno2.2107
  }
  virtual_routes {
185.15.57.0/29 table 10 nexthop via 185.15.57.10 dev eno2.2107 onlink
172.16.128.0/24 table 10 nexthop via 185.15.57.10 dev eno2.2107 onlink
  }
  virtual_ipaddress {
185.15.57.9/30 dev eno2.2107
208.80.153.190/29 dev eno2.2120
  }
  unicast_peer {
208.80.153.189
  }
}
=== 8< ===

This exact same setup was previously working, and actually, the next version 
works just fine.
Not sure if this has anything to do with the kernel version warning at the 
beginning.

In summary:

| keepalived version  | Debian   | Works? |
| |--||
| 1:2.0.10-1  | buster   | yes|
| 1:2.1.5-0.2+deb11u1 | bullseye | no |
| 1:2.2.7-1~bpo11+1   | bullseye-bpo | yes|

I'm opeining this bug report mostly so others can find it.
Raelly appreciated the bpo package is ready to use.

regards.

Processed: Re: Bug#1008189: meson: gnome module incorrectly requires gtk4-update-icon-cache

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +ftbfs
Bug #1008189 [src:meson] meson: gnome module incorrectly requires 
gtk4-update-icon-cache
Added tag(s) ftbfs.
> affects -1 src:gnome-contacts
Bug #1008189 [src:meson] meson: gnome module incorrectly requires 
gtk4-update-icon-cache
Added indication that 1008189 affects src:gnome-contacts
> affects -1 src:gtksourceview5
Bug #1008189 [src:meson] meson: gnome module incorrectly requires 
gtk4-update-icon-cache
Added indication that 1008189 affects src:gtksourceview5

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

Bug#1008189: meson: gnome module incorrectly requires gtk4-update-icon-cache

[Jeremy Bicha]

Control: tags -1 +ftbfs
Control: affects -1 src:gnome-contacts
Control: affects -1 src:gtksourceview5

On Thu, Mar 24, 2022 at 10:13 AM Jussi Pakkanen  wrote:
> This has already been tagged for the .1 release:
>
> https://github.com/mesonbuild/meson/milestone/79?closed=1
>
> Is that sufficient or do you need an interim distropatch upload?

I think it's only a fairly small number of Debian apps affected. I can
manually add the extra Build-Depends if I need to do a quicker upload
of affected packages.

Thank you,
Jeremy Bicha

Bug#1008189: meson: gnome module incorrectly requires gtk4-update-icon-cache

[Jussi Pakkanen]

On Thu, 24 Mar 2022 at 05:03, Jeremy Bicha  wrote:

> Therefore, please cherry-pick this commit:
> https://github.com/mesonbuild/meson/commit/dac212e1bba7

This has already been tagged for the .1 release:

https://github.com/mesonbuild/meson/milestone/79?closed=1

Is that sufficient or do you need an interim distropatch upload?

Bug#1005621: marked as done (coq-hierarchy-builder: FTBFS: dh_install: error: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Thu, 24 Mar 2022 14:52:15 +0100
with message-id <073e0b548306496e887d7f66c585e65bcae1b601.ca...@gmail.com>
and subject line Should be closed
has caused the Debian Bug report #1005621,
regarding coq-hierarchy-builder: FTBFS: dh_install: error: missing files, 
aborting
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.)


-- 
1005621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: coq-hierarchy-builder
Version: 1.2.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> install -d /<>/debian/tmp/bin
> install -m 0755 coq.hb /<>/debian/tmp/bin
> make[1]: Leaving directory '/<>'
>dh_install
> dh_install: warning: Cannot find (any matches for) 
> "usr/lib/coq/user-contrib/HB" (tried in ., debian/tmp)
> 
> dh_install: warning: libhierarchy-builder-coq missing files: 
> usr/lib/coq/user-contrib/HB
> dh_install: error: missing files, aborting
> make: *** [debian/rules:7: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/02/12/coq-hierarchy-builder_1.2.1-1_unstable.log

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

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Hi,

this report should be closed already: the version it was reported as
fixed has been in testing since long.

Cheers,

J.Puydt--- End Message ---

Bug#1005563: marked as done (nautilus-sendto: FTBFS: ../src/meson.build:10:5: ERROR: Function does not take positional arguments.)

[Debian Bug Tracking System]

Your message dated Thu, 24 Mar 2022 13:19:50 +
with message-id 
and subject line Bug#1005563: fixed in nautilus-sendto 3.8.6-4
has caused the Debian Bug report #1005563,
regarding nautilus-sendto: FTBFS: ../src/meson.build:10:5: ERROR: Function does 
not take positional arguments.
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.)


-- 
1005563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nautilus-sendto
Version: 3.8.6-3.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with gnome
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: nautilus-sendto
> Project version: 3.8.6
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) 
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency gio-2.0 found: YES 2.70.3
> Configuring config.h using configuration
> Compiler for C supports arguments -fno-strict-aliasing: YES 
> Compiler for C supports arguments -Wpointer-arith: YES 
> Compiler for C supports arguments -Wmissing-declarations: YES 
> Compiler for C supports arguments -Wimplicit-function-declaration: YES 
> Compiler for C supports arguments -Wformat=2: YES 
> Compiler for C supports arguments -Wformat-nonliteral: YES 
> Compiler for C supports arguments -Wformat-security: YES 
> Compiler for C supports arguments -Wstrict-prototypes: YES 
> Compiler for C supports arguments -Wmissing-prototypes: YES 
> Compiler for C supports arguments -Wnested-externs: YES 
> Compiler for C supports arguments -Wold-style-definition: YES 
> Compiler for C supports arguments -Wundef: YES 
> Compiler for C supports arguments -Wunused: YES 
> Compiler for C supports arguments -Wcast-align: YES 
> Compiler for C supports arguments -Wmissing-noreturn: YES 
> Compiler for C supports arguments -Wmissing-format-attribute: YES 
> Compiler for C supports arguments -Wmissing-include-dirs: YES 
> Compiler for C supports arguments -Wlogical-op: YES 
> Compiler for C supports arguments -Wno-uninitialized: YES 
> Compiler for C supports arguments -Wno-shadow: YES 
> Compiler for C supports arguments -Wno-int-conversion: YES 
> Compiler for C supports arguments -Wno-discarded-qualifiers: YES 
> Compiler for C supports arguments -Werror=redundant-decls: YES 
> Compiler for C supports arguments -Werror=implicit: YES 
> Compiler for C supports arguments -Werror=nonnull: YES 
> Compiler for C supports arguments -Werror=init-self: YES 
> Compiler for C supports arguments -Werror=main: YES 
> Compiler for C supports arguments -Werror=missing-braces: YES 
> Compiler for C supports arguments -Werror=sequence-point: YES 
> Compiler for C supports arguments -Werror=return-type: YES 
> Compiler for C supports arguments -Werror=trigraphs: YES 
> Compiler for C supports arguments -Werror=array-bounds: YES 
> Compiler for C supports arguments -Werror=write-strings: YES 
> Compiler for C supports arguments -Werror=address: YES 
> Compiler for C supports arguments -Werror=int-to-pointer-cast: YES 
> Compiler for C supports arguments -Werror=pointer-to-int-cast: YES 
> Compiler for C supports arguments -Werror=empty-body: YES 
> Compiler for C supports arguments -Werror=write-strings: YES (cached)
> 
> ../src/meson.build:10:5: ERROR: Function does not take positional arguments.
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2022-02-12T22:52:26.941256
> Main binary: /usr/bin/python3
> Build Options: -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu 
> -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain 
> -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.61.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: 

Processed: Bug#1005563 marked as pending in nautilus-sendto

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1005563 [src:nautilus-sendto] nautilus-sendto: FTBFS: 
../src/meson.build:10:5: ERROR: Function does not take positional arguments.
Added tag(s) pending.

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

Bug#1005563: marked as pending in nautilus-sendto

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #1005563 in nautilus-sendto 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/gnome-team/nautilus-sendto/-/commit/357b10fe852133ae8e0368935cd84979be7366ba


Add patch to fix build with latest meson

Closes: #1005563


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1005563

Bug#1008214: ruby-simplecov: autopkgtest regression: error output changed

[Paul Gevers]

Source: ruby-simplecov
Version: 0.21.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
ruby-simplecov from testing0.21.2-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-simplecov/20267102/log.gz


Failures:

  1) return codes inside fixtures/frameworks when running 
testunit_bad.rb behaves like bad tests with default configuration prints 
a message to STDERR
 Failure/Error: expect(@stderr).to 
match(/stopped.+SimpleCov.+previous.+error/i)


   expected 
":85:in 
`require': cannot 
loa...r_ruby/rubygems/core_ext/kernel_require.rb>:85:in 
`require'\n\tfrom testunit_bad.rb:2:in `'\n" to match 
/stopped.+SimpleCov.+previous.+error/i

   Diff:
   @@ -1,3 +1,5 @@
   -/stopped.+SimpleCov.+previous.+error/i

+:85:in 
`require': cannot load such file -- lib/simplecov (LoadError)
   +	from 
:85:in 
`require'

   +from testunit_bad.rb:2:in `'
 Shared Example Group: "bad tests" called from 
./spec/return_codes_spec.rb:66
 # ./spec/return_codes_spec.rb:37:in `block (5 levels) in (required)>'
 # ./spec/return_codes_spec.rb:12:in `block (4 levels) in (required)>'

 # ./spec/return_codes_spec.rb:10:in `chdir'
 # ./spec/return_codes_spec.rb:10:in `block (3 levels) in (required)>'


  2) return codes inside fixtures/frameworks when running 
testunit_bad.rb behaves like bad tests when print_error_status is 
disabled does not print anything to STDERR

 Failure/Error: expect(@stderr).to be_empty
   expected 
`":85:in 
`require': cannot 
loa...r_ruby/rubygems/core_ext/kernel_require.rb>:85:in 
`require'\n\tfrom testunit_bad.rb:2:in `'\n".empty?` to be truthy, 
got false
 Shared Example Group: "bad tests" called from 
./spec/return_codes_spec.rb:66
 # ./spec/return_codes_spec.rb:49:in `block (5 levels) in (required)>'
 # ./spec/return_codes_spec.rb:12:in `block (4 levels) in (required)>'

 # ./spec/return_codes_spec.rb:10:in `chdir'
 # ./spec/return_codes_spec.rb:10:in `block (3 levels) in (required)>'


  3) return codes inside fixtures/frameworks when running rspec_good.rb 
behaves like good tests has a zero exit status

 Failure/Error: expect(@status.exitstatus).to be_zero
   expected `1.zero?` to be truthy, got false
 Shared Example Group: "good tests" called from 
./spec/return_codes_spec.rb:61
 # ./spec/return_codes_spec.rb:22:in `block (4 levels) in (required)>'
 # ./spec/return_codes_spec.rb:12:in `block (4 levels) in (required)>'

 # ./spec/return_codes_spec.rb:10:in `chdir'
 # ./spec/return_codes_spec.rb:10:in `block (3 levels) in (required)>'


  4) return codes inside fixtures/frameworks when running 
testunit_good.rb behaves like good tests has a zero exit status

 Failure/Error: expect(@status.exitstatus).to be_zero
   expected `1.zero?` to be truthy, got false
 Shared Example Group: "good tests" called from 
./spec/return_codes_spec.rb:56
 # ./spec/return_codes_spec.rb:22:in `block (4 levels) in (required)>'
 # ./spec/return_codes_spec.rb:12:in `block (4 levels) in (required)>'

 # ./spec/return_codes_spec.rb:10:in `chdir'
 # ./spec/return_codes_spec.rb:10:in `block (3 levels) in (required)>'


  5) return codes inside fixtures/frameworks when running 
testunit_good.rb behaves like good tests prints nothing to STDERR

 Failure/Error: expect(@stderr).to be_empty
   expected 
`":85:in 
`require': cannot loa..._ruby/rubygems/core_ext/kernel_require.rb>:85:in 
`require'\n\tfrom testunit_good.rb:2:in `'\n".empty?` to be 
truthy, got false
 Shared Example Group: "good tests" called from 
./spec/return_codes_spec.rb:56
 # ./spec/return_codes_spec.rb:26:in `block (4 levels) in (required)>'
 # ./spec/return_codes_spec.rb:12:in `block (4 levels) in (required)>'

 # ./spec/return_codes_spec.rb:10:in `chdir'
 # ./spec/return_codes_spec.rb:10:in `block (3 levels) in (required)>'


  6) return codes inside fixtures/frameworks when running rspec_bad.rb 
behaves like bad tests with default configuration prints a message to STDERR
 Failure/Error: expect(@stderr).to 
match(/stopped.+SimpleCov.+previous.+error/i)


   expected "" to match 

Bug#1008213: nix: autopkgtest regression on armhf, i386 and ppc64el: not supported on ‘arm-linux’, refusing to evaluate.

[Paul Gevers]

Source: nix
Version: 2.7.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
nixfrom testing2.7.0+dfsg-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/armhf/n/nix/20297030/log.gz

+ read item
+ eval export NIX_REMOTE=daemon
+ export NIX_REMOTE=daemon
+ read item
+ eval export 
PATH="$HOME/.nix-profile/bin:/nix/var/nix/profiles/default/bin:$PATH"
+ export 
PATH=/root/.nix-profile/bin:/nix/var/nix/profiles/default/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

+ read item
+ eval export 
NIX_PATH="nixpkgs=/nix/var/nix/profiles/per-user/$USER/channels/nixpkgs:/nix/var/nix/profiles/per-user/$USER/channels"
+ export 
NIX_PATH=nixpkgs=/nix/var/nix/profiles/per-user/root/channels/nixpkgs:/nix/var/nix/profiles/per-user/root/channels

+ read item
+ mkdir -p /etc/nix/
+ echo sandbox = false
+ service nix-daemon restart
+ nix-channel --add https://nixos.org/channels/nixpkgs-unstable nixpkgs
+ nix-channel --update
unpacking channels...
+ nix-shell -p nix-du --run nix-du --help 
error: Package ‘shell’ in 
/nix/store/nnkkd8gzr4wn1r3jjcxsjn69gyj5mwf1-nixpkgs/nixpkgs/pkgs/build-support/trivial-builders.nix:73 
is not supported on ‘arm-linux’, refusing to evaluate.


   a) To temporarily allow packages that are unsupported for this 
system, you can use an environment variable

  for a single invocation of the nix tools.

$ export NIXPKGS_ALLOW_UNSUPPORTED_SYSTEM=1

Note: For `nix shell`, `nix build`, `nix develop` or any other 
Nix 2.4+

(Flake) command, `--impure` must be passed in order to read this
environment variable.

   b) For `nixos-rebuild` you can set
 { nixpkgs.config.allowUnsupportedSystem = true; }
   in configuration.nix to override this.

   c) For `nix-env`, `nix-build`, `nix-shell` or any other Nix 
command you can add

 { allowUnsupportedSystem = true; }
   to ~/.config/nixpkgs/config.nix.
(use '--show-trace' to show detailed location information)
autopkgtest [07:14:29]: test nix-env-and-shell



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008212: openmolcas: autopkgtest regression: SIGABRT

[Paul Gevers]

Source: openmolcas
Version: 22.02-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
openmolcas from testing22.02-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/o/openmolcas/20265826/log.gz

Running test standard: 000... (5%) OK
Running test standard: 001... (10%) Failed! (scf)
Running test standard: 002... (15%) Failed! (scf)
Running test standard: 004... (21%) OK
Running test standard: 005... (26%) OK
Running test standard: 006... (31%) OK
Running test standard: 009... (36%) OK
Running test standard: 010... (42%) OK
Running test standard: 011... (47%) OK
Running test standard: 012... (52%) OK
Running test standard: 014... (57%) OK
Running test standard: 015... (63%) OK
Running test standard: 016... (68%) OK
Running test standard: 019... (73%) OK
Running test standard: 023... (78%) OK
Running test standard: 025... (84%) OK
Running test standard: 026... (89%) OK
Running test standard: 028... (94%) OK
Running test standard: 029... (100%) OK

A total of 2 test(s) failed, with 2 critical failure(s).

Please check the directory:
  failed
for the .out/.err files of the failed tests,
and check the submit directory:
  tmp
for the working directories of the last run.

> 001.err:
Note: The following floating-point exceptions are signalling: 
IEEE_INVALID_FLAG IEEE_DIVIDE_BY_ZERO IEEE_UNDERFLOW_FLAG IEEE_DENORMAL
scf.exe: functionals.c:287: xc_func_init: Assertion 
`nspin==XC_UNPOLARIZED || nspin==XC_POLARIZED' failed.


Program received signal SIGABRT: Process abort signal.

Backtrace for this error:
#0  0x7feb89b378d2 in ???
#1  0x7feb89b36a65 in ???
#2  0x7feb897c691f in ???
#3  0x7feb897c68a1 in raise
#4  0x7feb897b0545 in abort
#5  0x7feb897b042e in ???
#6  0x7feb897bf221 in __assert_fail
#7  0x7feb88c71692 in xc_func_init
#8  0x7feb89de64ed in __xc_f03_lib_m_MOD_xc_f03_func_init
#9  0x5648b32a5b76 in ???
#10  0x5648b32a666a in ???
#11  0x5648b32a66e8 in ???
#12  0x5648b3192cca in ???
#13  0x5648b317b80c in ???
#14  0x5648b3156f46 in ???
#15  0x5648b3156cf6 in ???
#16  0x7feb897b17fc in __libc_start_main
#17  0x5648b3156d49 in ???
#18  0x in ???
> 001.out:
  Basis functions   114   114


  Input file to MOLDEN was generated!

--- Stop Module: seward at Wed Mar 23 07:16:03 2022 /rc=_RC_ALL_IS_WELL_ ---
--- Module seward spent 1 second ---
--- Start Module: check at Wed Mar 23 07:16:03 2022 ---
--- Stop Module: check at Wed Mar 23 07:16:03 2022 
/rc=_RC_NOT_AVAILABLE_ ---


Checking results:
All values match the reference


EXPORT DFT = BLYP


*** symbolic link created: INPORB -> standard__001.GssOrb
--- Start Module: scf at Wed Mar 23 07:16:03 2022 ---

-- Input validation for scf
lxml python module not found, no validation possible
--
The total execution time is limited to 600 seconds.

()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()



   only a single process is used
  available to each process: 2.0 GB of memory, 56 
threads

 pid: 2065
()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()()


###

###
 ### 
  ###
 ### 
  ###
 ### Minimized-density-differences option turned off! 
  ###
 ### 
  ###
 ### 
  ###


###

###
--- Stop Module: scf at Wed Mar 23 07:16:03 2022 /rc=-6 ---


END FOREACH


..
.# Non-zero return code #.
..

Timing: Wall=2.06 User=9.06 System=10.82
autopkgtest [07:18:59]: test testsuite.sh



OpenPGP_signature
Description: OpenPGP digital signature

Processed: libobject-pad-perl breaks libtickit-widget-tabbed-perl autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> found -1 libobject-pad-perl/0.63-1
Bug #1008211 [src:libobject-pad-perl, src:libtickit-widget-tabbed-perl] 
libobject-pad-perl breaks libtickit-widget-tabbed-perl autopkgtest
Marked as found in versions libobject-pad-perl/0.63-1.
> found -1 libtickit-widget-tabbed-perl/0.026-1
Bug #1008211 [src:libobject-pad-perl, src:libtickit-widget-tabbed-perl] 
libobject-pad-perl breaks libtickit-widget-tabbed-perl autopkgtest
Marked as found in versions libtickit-widget-tabbed-perl/0.026-1.

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

Bug#1008211: libobject-pad-perl breaks libtickit-widget-tabbed-perl autopkgtest

[Paul Gevers]

Source: libobject-pad-perl, libtickit-widget-tabbed-perl
Control: found -1 libobject-pad-perl/0.63-1
Control: found -1 libtickit-widget-tabbed-perl/0.026-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of libobject-pad-perl the autopkgtest of 
libtickit-widget-tabbed-perl fails in testing when that autopkgtest is 
run with the binary packages of libobject-pad-perl from unstable. It 
passes when run with only packages from testing. In tabular form:


  passfail
libobject-pad-perlfrom testing0.63-1
libtickit-widget-tabbed-perl  from testing0.026-1
all othersfrom testingfrom testing

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

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


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

Paul

[1] https://qa.debian.org/excuses.php?package=libobject-pad-perl

https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libtickit-widget-tabbed-perl/20265825/log.gz


#   Failed test ' /usr/bin/perl -w -M"Tickit::Widget::Tabbed" -e 1 2>&1 
produced no (non-whitelisted) output'

#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 107.

#   Failed test 'env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"Tickit::Widget::Tabbed" -e 1 2>&1 produced no (non-whitelisted) output'

#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 107.
# Looks like you failed 2 tests of 4.
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t .. 1..4
# field initialiser expression is experimental and may be changed or 
removed without notice at 
/usr/share/perl5/Tickit/Widget/Tabbed/Ribbon.pm line 302.
ok 1 -  /usr/bin/perl -w -M"Tickit::Widget::Tabbed" -e 1 2>&1 exited 
successfully
not ok 2 -  /usr/bin/perl -w -M"Tickit::Widget::Tabbed" -e 1 2>&1 
produced no (non-whitelisted) output
# field initialiser expression is experimental and may be changed or 
removed without notice at 
/usr/share/perl5/Tickit/Widget/Tabbed/Ribbon.pm line 302.
ok 3 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"Tickit::Widget::Tabbed" -e 1 2>&1 exited successfully
not ok 4 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"Tickit::Widget::Tabbed" -e 1 2>&1 produced no (non-whitelisted) output

Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/4 subtests
Test Summary Report
---
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t (Wstat: 512 Tests: 
4 Failed: 2)

  Failed tests:  2, 4
  Non-zero exit status: 2
Files=1, Tests=4,  0 wallclock secs ( 0.02 usr  0.00 sys +  0.22 cusr 
0.01 csys =  0.25 CPU)

Result: FAIL
autopkgtest [07:15:45]: test autodep8-perl



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1001595: src:gcc-defaults-mipsen: fails to migrate to testing for too long

[YunQiang Su]

Paul Gevers  于2022年3月24日周四 19:26写道：
>
> Hi YunQiang,
>
> On 22-03-2022 07:06, YunQiang Su wrote:
> > Paul Gevers  于2022年3月22日周二 04:04写道：
> >> On Sun, 12 Dec 2021 21:51:28 +0100 Paul Gevers  wrote:
> >>> The Release Team considers packages that are out-of-sync between testing
> >>> and unstable for more than 60 days as having a Release Critical bug in
> >>> testing [1]. Your package src:gcc-defaults-mipsen has been trying to
> >>> migrate for 62 days [2].
> >>
> >> It's been 161 days now. We expect from you to solve these kind of
> >> issues, especially if they have been brought to your attention.
> >>
> >
> > ohh. sorry for it. I upload gcc-11-cross-mipsen some days ago.
> > I thought that gcc-defaults-mipsen will migrate ok.
> >
> > I will fix it just now.
>
> You are aware that gcc-12-cross-mipsen needs another source-only upload
> because it's new and you needed to upload all binaries but non-buildd
> built binaries are not allowed to migrate. Unfortunately on the current
> infrastructure binNMU's of arch:all binaries don't work.
> gcc-12-cross-mipsen needs to be able to migrate together with
> gcc-11-cross-mipsen (and gcc-defaults-mipsen).
>

Yes. I am aware of it. And I am waiting for gcc-12-cross-mipsen to finish
building on all of these architectures.

> Paul



-- 
YunQiang Su

Bug#1001595: src:gcc-defaults-mipsen: fails to migrate to testing for too long

[Paul Gevers]

Hi YunQiang,

On 22-03-2022 07:06, YunQiang Su wrote:

Paul Gevers  于2022年3月22日周二 04:04写道：

On Sun, 12 Dec 2021 21:51:28 +0100 Paul Gevers  wrote:

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:gcc-defaults-mipsen has been trying to
migrate for 62 days [2].


It's been 161 days now. We expect from you to solve these kind of
issues, especially if they have been brought to your attention.



ohh. sorry for it. I upload gcc-11-cross-mipsen some days ago.
I thought that gcc-defaults-mipsen will migrate ok.

I will fix it just now.


You are aware that gcc-12-cross-mipsen needs another source-only upload 
because it's new and you needed to upload all binaries but non-buildd 
built binaries are not allowed to migrate. Unfortunately on the current 
infrastructure binNMU's of arch:all binaries don't work. 
gcc-12-cross-mipsen needs to be able to migrate together with 
gcc-11-cross-mipsen (and gcc-defaults-mipsen).


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1005715: marked as done (dahdi-linux: autopkgtest suggests breakage due to new linux kernel)

[Debian Bug Tracking System]

Your message dated Thu, 24 Mar 2022 10:48:43 +
with message-id 
and subject line Bug#1005715: fixed in dahdi-linux 1:2.11.1.0.20170917~dfsg-7.5
has caused the Debian Bug report #1005715,
regarding dahdi-linux: autopkgtest suggests breakage due to new linux kernel
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.)


-- 
1005715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dahdi-linux
Version: 1:2.11.1.0.20170917~dfsg-7.4
Severity: serious
Tags: sid bookworm

Dear maintainer,

The latest src:linux upload to unstable caused the autopkgtest of
dahdi-linux to fail. The test was added "to tell us if the modules are
broken by newer kernel versions". So, that's probably the case.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/d/dahdi-linux/19188684/log.gz

Setting up dahdi-dkms (1:2.11.1.0.20170917~dfsg-7.4) ...
Loading new dahdi-2.11.1.0.20170917~dfsg-7.4 DKMS files...
It is likely that 4.19.0-18-amd64 belongs to a chroot's host
Building for 5.16.0-1-amd64
Building initial module for 5.16.0-1-amd64
Error! Bad return status for module build on kernel: 5.16.0-1-amd64 (x86_64)
Consult /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.4/build/make.log for more 
information.
dpkg: error processing package dahdi-dkms (--configure):
 installed dahdi-dkms package post-installation script subprocess returned 
error exit status 10


https://ci.debian.net/data/autopkgtest/testing/i386/d/dahdi-linux/19177982/log.gz

Setting up dahdi-dkms (1:2.11.1.0.20170917~dfsg-7.4) ...
Loading new dahdi-2.11.1.0.20170917~dfsg-7.4 DKMS files...
It is likely that 5.10.0-11-cloud-amd64 belongs to a chroot's host
Building for 5.16.0-1-686-pae
Building initial module for 5.16.0-1-686-pae
Error! Bad return status for module build on kernel: 5.16.0-1-686-pae (i686)
Consult /var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.4/build/make.log for more 
information.
dpkg: error processing package dahdi-dkms (--configure):
 installed dahdi-dkms package post-installation script subprocess returned 
error exit status 10
--- End Message ---
--- Begin Message ---
Source: dahdi-linux
Source-Version: 1:2.11.1.0.20170917~dfsg-7.5
Done: Thorsten Alteholz 

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated dahdi-linux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 23 Mar 2022 19:03:02 +0100
Source: dahdi-linux
Architecture: source
Version: 1:2.11.1.0.20170917~dfsg-7.5
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Thorsten Alteholz 
Closes: 1005390 1005715
Changes:
 dahdi-linux (1:2.11.1.0.20170917~dfsg-7.5) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * add patch for: Do not use  in kernel modules
 There was an intentional change in Linux 5.16 removing user-space
 headers from the kernel include path:
 .
 Kernel code must use  instead of .
 Thanks a lot to Ben Hutchings for providing the patch.
 Tzafrir Cohen provided a similar patch upstream.
 (Closes: #1005715, #1005390)
Checksums-Sha1:
 aaeb1323e2d0f1e8a16e2fcb1d66a85eeb695b45 2616 
dahdi-linux_2.11.1.0.20170917~dfsg-7.5.dsc
 cd74db4d6c8704fa94621b4573ee91e50abc152a 95220 
dahdi-linux_2.11.1.0.20170917~dfsg-7.5.debian.tar.xz
 1f037238462f5ba5027ed70e8368306e75185ce6 7698 
dahdi-linux_2.11.1.0.20170917~dfsg-7.5_amd64.buildinfo
Checksums-Sha256:
 9c74967c7cfede32aa70ad7543bafd7d46596781b9e98435fc64899edaa74d05 2616 
dahdi-linux_2.11.1.0.20170917~dfsg-7.5.dsc
 686fa81afcdc94c60a0df58f1b134840933df525537ae1f64ed87620ab51e893 95220 
dahdi-linux_2.11.1.0.20170917~dfsg-7.5.debian.tar.xz
 d4f63f9efefc60eb4ae728e30337640f254489482abcbd7d21e2768d6a82445d 7698 
dahdi-linux_2.11.1.0.20170917~dfsg-7.5_amd64.buildinfo
Files:
 5956a4e6bfbe9c8f1d344544e5699735 2616 comm optional 

Bug#1005390: marked as done (Fails to build with Linux 5.16 onward)

[Debian Bug Tracking System]

Your message dated Thu, 24 Mar 2022 10:48:43 +
with message-id 
and subject line Bug#1005390: fixed in dahdi-linux 1:2.11.1.0.20170917~dfsg-7.5
has caused the Debian Bug report #1005390,
regarding Fails to build with Linux 5.16 onward
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.)


-- 
1005390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dahdi-linux
Version: 1:2.11.1.0.20170917~dfsg-7.4
Severity: grave
Tags: patch

The dahdi modules fail to build, with thqis error:

/var/lib/dkms/dahdi/2.11.1.0.20170917~dfsg-7.4/build/drivers/dahdi/wct4xxp/base.c:45:10:
 fatal error: stdbool.h: No such file or directory
   45 | #include 
  |  ^~~

This is due to an intentional change in Linux 5.16 removing user-space
headers from the kernel include path:
.

Kernel code must use  instead of .

The attached patch fixes this and allows the build to complete, but
there are still a lot of compiler warnings.

Ben.

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

Kernel: Linux 5.15.0-3-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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
From: Ben Hutchings 
Date: Sat, 12 Feb 2022 19:32:52 +0100
Subject: dahdi: Do not use  in kernel modules

There was an intentional change in Linux 5.16 removing user-space
headers from the kernel include path:
.

Kernel code must use  instead of .

---
--- a/drivers/dahdi/dahdi-base.c
+++ b/drivers/dahdi/dahdi-base.c
@@ -86,7 +86,7 @@
 
 #include "hpec/hpec_user.h"
 
-#include 
+#include 
 
 #if defined(EMPULSE) && defined(EMFLASH)
 #error "You cannot define both EMPULSE and EMFLASH"
--- a/drivers/dahdi/wcaxx-base.c
+++ b/drivers/dahdi/wcaxx-base.c
@@ -34,7 +34,7 @@
 #include 
 #include 
 
-#include 
+#include 
 
 
 #if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 30)
--- a/drivers/dahdi/wct4xxp/base.c
+++ b/drivers/dahdi/wct4xxp/base.c
@@ -42,7 +42,7 @@
 #include 
 #include 
 
-#include 
+#include 
 #include 
 
 #include "wct4xxp.h"
--- a/drivers/dahdi/wctc4xxp/base.c
+++ b/drivers/dahdi/wctc4xxp/base.c
@@ -39,7 +39,7 @@
 #include 
 #include 
 
-#include 
+#include 
 
 #include 
 
--- a/drivers/dahdi/wctdm24xxp/base.c
+++ b/drivers/dahdi/wctdm24xxp/base.c
@@ -58,7 +58,7 @@ Tx Gain - W/Pre-Emphasis: -23.99 to 0.00
 #include 
 #include 
 
-#include 
+#include 
 
 #if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 30)
 /* Define this if you would like to load the modules in parallel.  While this
--- a/drivers/dahdi/wcte12xp/base.c
+++ b/drivers/dahdi/wcte12xp/base.c
@@ -43,7 +43,7 @@
 
 #include 
 
-#include 
+#include 
 #include 
 
 #if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 11, 0)
--- a/drivers/dahdi/wcte13xp-base.c
+++ b/drivers/dahdi/wcte13xp-base.c
@@ -35,7 +35,7 @@
 #include 
 #include 
 
-#include 
+#include 
 #include 
 
 #include "wct4xxp/wct4xxp.h"   /* For certain definitions */
--- a/drivers/dahdi/wcte43x-base.c
+++ b/drivers/dahdi/wcte43x-base.c
@@ -43,7 +43,7 @@
 #include 
 #include 
 
-#include 
+#include 
 #include 
 
 #if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 11, 0)
--- a/drivers/dahdi/wcxb.c
+++ b/drivers/dahdi/wcxb.c
@@ -38,7 +38,7 @@
 
 #include 
 
-#include 
+#include 
 
 #include "wcxb.h"
 #include "wcxb_spi.h"
--- a/drivers/dahdi/wct4xxp/vpm450m.c
+++ b/drivers/dahdi/wct4xxp/vpm450m.c
@@ -28,7 +28,7 @@
 #include 
 
 #include 
-#include 
+#include 
 
 #include "vpm450m.h"
 #include 
--- a/drivers/dahdi/voicebus/vpmoct.h
+++ b/drivers/dahdi/voicebus/vpmoct.h
@@ -30,7 +30,7 @@
 #include 
 #include "dahdi/kernel.h"
 
-#include 
+#include 
 
 #define VPMOCT_FIRM_HEADER_LEN 32
 #define VPMOCT_BOOT_RAM_LEN 128
--- a/drivers/dahdi/wcxb_spi.h
+++ b/drivers/dahdi/wcxb_spi.h
@@ -24,7 +24,7 @@
 #define __WCXB_SPI_H
 
 #include 
-#include 
+#include 
 
 struct wcxb_spi_transfer {
const void  *tx_buf;
--- End Message ---
--- Begin Message ---
Source: dahdi-linux
Source-Version: 1:2.11.1.0.20170917~dfsg-7.5
Done: Thorsten Alteholz 

We believe that the bug you reported is fixed in the latest version of
dahdi-linux, which is due to be installed in the Debian FTP 

Bug#1007992:

[Michael Ott]

Bug is already fixed

https://github.com/intel/gmmlib/issues/95#issuecomment-1077397564

Bug#1008197: at-spi2-core: move gsettings-desktop-schemas to package Depends

[Julian Andres Klode]

Package: at-spi2-core
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
X-Debbugs-Cc: juli...@ubuntu.com

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

  * Move the gsettings-desktop-schemas from tests/control to the main
package Depends. This package is absolutely necessary for the bus
service to start.

You can see the same issue in other tests, adding the dependency for
the tests only, when it is required for the service to start does not
make much sense - it's still a missing Depends.

Thanks for considering the patch.

-- System Information:
Debian Release: bookworm/sid
  APT prefers jammy
  APT policy: (500, 'jammy'), (500, 'impish-security'), (500, 'impish')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-2022-generic (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_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

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en
diff -Nru at-spi2-core-2.44.0/debian/control at-spi2-core-2.44.0/debian/control
--- at-spi2-core-2.44.0/debian/control  2022-03-20 17:30:24.0 +0100
+++ at-spi2-core-2.44.0/debian/control  2022-03-24 10:21:06.0 +0100
@@ -24,7 +24,7 @@
 Package: at-spi2-core
 Architecture: any
 Multi-Arch: foreign
-Depends: ${misc:Depends}, ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}, gsettings-desktop-schemas
 Description: Assistive Technology Service Provider Interface (dbus core)
  This package contains the core components of GNOME Accessibility.
 
diff -Nru at-spi2-core-2.44.0/debian/tests/control 
at-spi2-core-2.44.0/debian/tests/control
--- at-spi2-core-2.44.0/debian/tests/control2022-03-20 18:03:41.0 
+0100
+++ at-spi2-core-2.44.0/debian/tests/control2022-03-24 10:19:58.0 
+0100
@@ -1,2 +1,2 @@
 Tests: memory dbind
-Depends: libatspi2.0-dev, build-essential, xauth, xvfb, dbus, at-spi2-core, 
gsettings-desktop-schemas
+Depends: libatspi2.0-dev, build-essential, xauth, xvfb, dbus, at-spi2-core

Processed: closing 1007761

[Debian Bug Tracking System]

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

> close 1007761 2.33.5+ds1-2
Bug #1007761 [src:prometheus] prometheus FTBFS on !amd64
Marked as fixed in versions prometheus/2.33.5+ds1-2.
Bug #1007761 [src:prometheus] prometheus FTBFS on !amd64
Marked Bug as done
> thanks
Stopping processing here.

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