Processed: [Help] Re: python-envisage: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #1002325 [src:python-envisage] python-envisage: FTBFS: dh_auto_test: error: 
pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13
Added tag(s) help.

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

Bug#1002325: [Help] Re: python-envisage: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13

[Andreas Tille]

Control: tags -1 help

Hi,

I've updated python-envisage in Salsa[1] to the latest upstream version
and bumped its failing predepends to their according latest upstream and
fixed all bugs in those.  For envisage I'm stumbling upon a Python3.10
related bug I'd like to ask for help:

...
==
ERROR: test_exclude_multiple 
(envisage.tests.test_egg_plugin_manager.EggPluginManagerTestCase)
exclude multiple
--
Traceback (most recent call last):
  File 
"/build/python-envisage-6.0.1/.pybuild/cpython3_3.10_envisage/build/envisage/tests/test_egg_plugin_manager.py",
 line 115, in test_exclude_multiple
self._add_eggs_on_path([self.egg_dir])
  File 
"/build/python-envisage-6.0.1/.pybuild/cpython3_3.10_envisage/build/envisage/tests/test_egg_based.py",
 line 59, in _add_eggs_on_path
raise SystemError("Cannot find eggs %s" % errors)
SystemError: Cannot find eggs {}

==
ERROR: test_exclude_specific 
(envisage.tests.test_egg_plugin_manager.EggPluginManagerTestCase)
exclude specific
--
Traceback (most recent call last):
  File 
"/build/python-envisage-6.0.1/.pybuild/cpython3_3.10_envisage/build/envisage/tests/test_egg_plugin_manager.py",
 line 91, in test_exclude_specific
self._add_eggs_on_path([self.egg_dir])
  File 
"/build/python-envisage-6.0.1/.pybuild/cpython3_3.10_envisage/build/envisage/tests/test_egg_based.py",
 line 59, in _add_eggs_on_path
raise SystemError("Cannot find eggs %s" % errors)
SystemError: Cannot find eggs {}


Any idea to deal with this issue in
   envisage/tests/test_egg_based.py", line 59
?

Kind regards

  Andreas.


[1] https://salsa.debian.org/python-team/packages/python-envisage


-- 
http://fam-tille.de

Bug#1005266: xserver-xorg-core-udeb: uninstallable: depends on non-udeb libxcvt0

[Cyril Brulebois]

Package: xserver-xorg-core-udeb
Version: 2:21.1.3-2
Severity: serious
Tags: d-i
Justification: not installable
X-Debbugs-Cc: debian-b...@lists.debian.org

Hi,

Your package is no longer installable as it depends on a non-udeb
package: libxcvt0. This breaks d-i builds on architectures featuring the
graphical installer:

Building dependency tree...
  xserver-xorg-core-udeb:amd64 Depends on libxcvt0:amd64 < none @un H > (>= 
0.1.1) can't be satisfied!
…
The following packages have unmet dependencies:
 xserver-xorg-core-udeb : Depends: libxcvt0 (>= 0.1.1) but it is not 
installable

Please let us (debian-boot@) / me know if you need help investigating
this.


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

Bug#1003578: hash-slinger: diff for NMU version 3.1-1.1

[Adrian Bunk]

Control: tags 1003578 + pending

Dear maintainer,

I've prepared an NMU for hash-slinger (versioned as 3.1-1.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should cancel it.

cu
Adrian
diff -Nru hash-slinger-3.1/debian/changelog hash-slinger-3.1/debian/changelog
--- hash-slinger-3.1/debian/changelog	2021-02-14 18:40:02.0 +0200
+++ hash-slinger-3.1/debian/changelog	2022-02-10 08:03:46.0 +0200
@@ -1,3 +1,11 @@
+hash-slinger (3.1-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Remove the unused dependency on python3-ipaddr. (Closes: #1003578)
+  * debian/control: Add Homepage.
+
+ -- Adrian Bunk   Thu, 10 Feb 2022 08:03:46 +0200
+
 hash-slinger (3.1-1) unstable; urgency=medium
 
   * Update d/control (Closes: #899533)
diff -Nru hash-slinger-3.1/debian/control hash-slinger-3.1/debian/control
--- hash-slinger-3.1/debian/control	2021-02-14 18:40:02.0 +0200
+++ hash-slinger-3.1/debian/control	2022-02-10 08:03:46.0 +0200
@@ -8,6 +8,7 @@
python3,
xmlto
 Standards-Version: 4.5.1
+Homepage: https://github.com/letoams/hash-slinger
 Vcs-Git: https://salsa.debian.org/dns-team/hash-slinger.git
 Vcs-Browser: https://salsa.debian.org/dns-team/hash-slinger
 
@@ -18,7 +19,6 @@
  openssh-client,
  python3-dnspython,
  python3-gnupg (>= 0.3.7),
- python3-ipaddr,
  python3-m2crypto (>= 0.24.0),
  python3-unbound,
  ${misc:Depends},

Processed: hash-slinger: diff for NMU version 3.1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1003578 + pending
Bug #1003578 [hash-slinger] hash-slinger: Unnecessary dependency on 
python3-ipaddr
Added tag(s) pending.

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

Bug#1005263: dnswire FTBFS: rm: cannot remove 'src/dnstap.pb': Is a directory

[Adrian Bunk]

Source: dnswire
Version: 0.2.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=dnswire&ver=0.2.0-1

...
dh clean
   debian/rules execute_after_dh_auto_clean
make[1]: Entering directory '/<>'
rm -f src/dnstap.pb
rm: cannot remove 'src/dnstap.pb': Is a directory
make[1]: *** [debian/rules:9: execute_after_dh_auto_clean] Error 1

Bug#1005261: odil ftbfs in unstable

[Matthias Klose]

Package: src:odil
Version: 0.12.1-4
Severity: serious
Tags: sid bookworm

odil ftbfs in unstable:

where is the -std=gnu++14 picked up from?

[...]
[  9%] Building CXX object
src/CMakeFiles/libodil.dir/odil/dcmtk/ElementAccessor.cpp.o
cd /packages/tmp/odil-0.12.1/build/src && /usr/bin/c++ -DBOOST_ALL_DYN_LINK
-DBOOST_ALL_NO_LIB -DBOOST_ASIO_SEPARATE_COMPILATION -DBOOST_ATOMIC_DYN_LINK
-DBOOST_CHRONO_DYN_LINK -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK
-DBOOST_LOG_DYN_LINK -DBOOST_REGEX_DYN_LINK -DBOOST_THREAD_DYN_LINK
-DODIL_VERSION_MAJOR=0 -Dlibodil_EXPORTS -I/packages/tmp/odil-0.12.1/src
-isystem /usr/include/jsoncpp -g -O2
-ffile-prefix-map=/packages/tmp/odil-0.12.1=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -std=gnu++14 -MD
-MT src/CMakeFiles/libodil.dir/odil/dcmtk/ElementAccessor.cpp.o -MF
CMakeFiles/libodil.dir/odil/dcmtk/ElementAccessor.cpp.o.d -o
CMakeFiles/libodil.dir/odil/dcmtk/ElementAccessor.cpp.o -c
/packages/tmp/odil-0.12.1/src/odil/dcmtk/ElementAccessor.cpp
In file included from 
/packages/tmp/odil-0.12.1/src/odil/dcmtk/ElementAccessor.h:14,
 from
/packages/tmp/odil-0.12.1/src/odil/dcmtk/ElementAccessor.cpp:9:
/usr/include/dcmtk/config/osconfig.h:1144:2: error: invalid preprocessing
directive #errorDCMTK
 1144 | #error\
  |  ^~
 1145 | DCMTK was configured to use C++17 features, but your compiler does not
or was not configured to provide them.
  | ~
make[4]: *** [src/CMakeFiles/libodil.dir/build.make:541:
src/CMakeFiles/libodil.dir/odil/dcmtk/ElementAccessor.cpp.o] Error 1
make[4]: Leaving directory '/packages/tmp/odil-0.12.1/build'
make[3]: *** [CMakeFiles/Makefile2:1169: src/CMakeFiles/libodil.dir/all] Error 2
make[3]: Leaving directory '/packages/tmp/odil-0.12.1/build'
make[2]: *** [Makefile:149: all] Error 2
make[2]: Leaving directory '/packages/tmp/odil-0.12.1/build'
dh_auto_build: error: cd build && make -j1 "INSTALL=install
--strip-program=true" VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:25: override_dh_auto_build-nopy] Error 25
make[1]: Leaving directory '/packages/tmp/odil-0.12.1'
make: *** [debian/rules:16: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subp

Bug#1002781: marked as done (org-roam: FTBFS: Cannot open load file: No such file or directory, ox-extra)

[Debian Bug Tracking System]

Your message dated Thu, 10 Feb 2022 01:20:36 +
with message-id 
and subject line Bug#1002781: fixed in org-roam 2.2.0-1
has caused the Debian Bug report #1002781,
regarding org-roam: FTBFS: Cannot open load file: No such file or directory, 
ox-extra
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.)


-- 
1002781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: org-roam
Version: 2.1.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211228 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with elpa
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> rm -f doc/org-roam.texi
> make -C doc texi
> make[2]: Entering directory '/<>/doc'
> Loading /etc/emacs/site-start.d/00debian.el (source)...
> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> Cannot open load file: No such file or directory, ox-extra
> make[2]: *** [Makefile:84: texi] Error 255


The full build log is available from:
http://qa-logs.debian.net/2021/12/28/org-roam_2.1.0-2_unstable.log

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

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 ---
Source: org-roam
Source-Version: 2.2.0-1
Done: Sean Whitton 

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated org-roam 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, 09 Feb 2022 17:36:50 -0700
Source: org-roam
Architecture: source
Version: 2.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: Sean Whitton 
Closes: 1002781
Changes:
 org-roam (2.2.0-1) unstable; urgency=medium
 .
   * Update to new upstream version 2.2.0.
   * Add b-d on elpa-org-contrib for ox-extra.el (Closes: #1002781).
   * Drop reference to makem.sh from d/copyright.
Checksums-Sha1:
 62768084efd061cb208a495a2c291c1078ebd200 2324 org-roam_2.2.0-1.dsc
 c47ec46c68e836d354b9bbe9b91de7c325b1b117 34427728 org-roam_2.2.0.orig.tar.xz
 b6223a4f6e3c629bbb379cb1e5ed7f77e50975d1 3868 org-roam_2.2.0-1.debian.tar.xz
Checksums-Sha256:
 30e16fa05ca97d9c26e2c08f0cef5b9ace026dc37f51b8d6a6e4579beaf2ddb7 2324 
org-roam_2.2.0-1.dsc
 22c37212788e25da716dd67197c15337d8f91aa54a2a7b28245e76f1d6cf7a03 34427728 
org-roam_2.2.0.orig.tar.xz
 52c7915663840c476f77ac94d70bb95af9485325efec31dad849cf00ef8a9cf3 3868 
org-roam_2.2.0-1.debian.tar.xz
Files:
 96254439d8aaed47098d2176c1386ab6 2324 editors optional org-roam_2.2.0-1.dsc
 574a1cb9b12a740af54c68b29180c367 34427728 editors optional 
org-roam_2.2.0.orig.tar.xz
 d14fe476611356c1d0d332fe8aecd8b2 3868 editors optional 
org-roam_2.2.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmIEXkYACgkQaVt65L8G
YkAnbhAAkY9jwyrVtMQWFl5vJlcJRBvN3pH1BO9t9e4ia25xPfWXQmJJXVNwOHYW
S9vPMsKOG3WUfoSgXr5Xrul53Ekyh9m9MJHERH9yBhJ8Ei4/s/xtDidAgILtnOMN
kAuKFSD+W45asViQ/e4lJkros1AoXWWzbGp5ZBojCZqB0u/bmYRywn330uGChKDI
dViJ5/FN93I4NUTV69VevQ29k8Tjy9Dr6gyHIDKry3ukMnW9SYP/nNsy0vKxDvc1
PWQtqhTeDbq+A4xChfL3ttmM4k2p19SOpFteR1DR1O4rXlEtrD8+7UrEzBF33M/a
3g+dn6SfV7n6u8zj9oIUvabJD8YdUqKps4ZxmsXEsQ7YvFrr4D9XlVpRVGwgWk3o
fYSpnICxEzHMG+oRw7QFlJVzrVtNa9of2R9mDEuaXh072pTLnj8kyLdXZVQWKa1B
QI2/K4/jZaF1fXEWXAd3CRr80ahOXVTqbo+50q7f7Iby58PqiGg5K1mlp4H4GhP4
4cWw1wS+gTf/Q/TIHOuWRPIcbacjh9885tQjXEEkUrvbbtkwwGpNbtGwR8xtjNCU
YOgovH7Rs

Bug#1005113: marked as done (fwupd: Please tighten the version of libfwupd2)

[Debian Bug Tracking System]

Your message dated Thu, 10 Feb 2022 00:48:34 +
with message-id 
and subject line Bug#1003664: fixed in fwupd 1.7.4-2
has caused the Debian Bug report #1003664,
regarding fwupd: Please tighten the version of libfwupd2
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.)


-- 
1003664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fwupd
Version: 1.5.7-5
Severity: serious

Hello,

fwupd package should tighten the version of the libfwupd2 dependency
(and probably libfwupdplugin as well)

Mixing fwupd version 1.5.7-5 and libfwupd2 version 1.7.4-1 makes fwupd crash

Kind regards,
Laurent Bigonville

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

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

Versions of packages fwupd depends on:
ii  libc6  2.33-5
ii  libcurl3-gnutls7.81.0-1
ii  libefiboot137-6
ii  libelf10.186-1
ii  libflashrom1   1.2-5
ii  libfwupd2  1.5.7-5
ii  libfwupdplugin11.5.7-5
ii  libglib2.0-0   2.70.3-1
ii  libgnutls303.7.3-4+b1
ii  libgudev-1.0-0 237-2
ii  libgusb2   0.3.8-1
ii  libjcat1   0.1.9-1
ii  libjson-glib-1.0-0 1.6.6-1
ii  libpolkit-gobject-1-0  0.105-31.1+b1
ii  libsmbios-c2   2.4.3-1
ii  libsqlite3-0   3.37.2-2
ii  libsystemd0250.3-2
ii  libtss2-esys-3.0.2-0   3.1.0-3
ii  libxmlb2   0.3.6-2
ii  shared-mime-info   2.1-2

Versions of packages fwupd recommends:
ii  bolt   0.9.1-2
ii  dbus   1.12.20-3
ii  fwupd-amd64-signed [fwupd-signed]  1.5.7+5
ii  python33.9.8-1
pn  secureboot-db  
ii  udisks22.9.4-1

Versions of packages fwupd suggests:
pn  gir1.2-fwupd-2.0  

-- Configuration Files:
/etc/dbus-1/system.d/org.freedesktop.fwupd.conf [Errno 2] Aucun fichier ou 
dossier de ce type: '/etc/dbus-1/system.d/org.freedesktop.fwupd.conf'
/etc/fwupd/remotes.d/fwupd.conf [Errno 2] Aucun fichier ou dossier de ce type: 
'/etc/fwupd/remotes.d/fwupd.conf'

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fwupd
Source-Version: 1.7.4-2
Done: Steve McIntyre <93...@debian.org>

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

Debian distribution maintenance software
pp.
Steve McIntyre <93...@debian.org> (supplier of updated fwupd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 10 Feb 2022 00:13:57 +
Source: fwupd
Architecture: source
Version: 1.7.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian EFI 
Changed-By: Steve McIntyre <93...@debian.org>
Closes: 1003664
Changes:
 fwupd (1.7.4-2) unstable; urgency=medium
 .
   * Add hard dependencies on libfwupd2 and libfwupdplugin5 built with
 us. Symbols suggest things should work, but maybe not. :-(
 Closes: #1003664
Checksums-Sha1:
 c8007e970d2ba207061d92bbce102477c5fd6a25 3836 fwupd_1.7.4-2.dsc
 bdceae698e6b53b3490e9a401b5b3a166c8d21ca 29192 fwupd_1.7.4-2.debian.tar.xz
 5f5054562e844d5d53322db45842016a6d91a366 15062 fwupd_1.7.4-2_source.buildinfo
Checksums-Sha256:
 1a7ee01a6d941dce64e92577f74fdc3e0a3b703915442b62e218dafa22b2d300 3836 
fwupd_1.7.4-2.dsc
 b16045d39805df907f0e69d20724273475f7f1d6018b7616134916f6bcf0a332 29192 
fwupd_1.7.4-2.debian.tar.xz
 248496e7f038cbec14409b9aedc6ccc9342cf7cbfac622fbf1f2504a54773c1e 15062 
fwupd_1.7.4-2_source.buildinfo
Files:
 b597062151cddf57a8250ea5e32ab109 3836 admin optional fwupd_1.7.4-2.dsc
 3e1a43f850eaec8

Bug#1003664: marked as done (fwupd: Too loose dependency on libfwupdN)

[Debian Bug Tracking System]

Your message dated Thu, 10 Feb 2022 00:48:34 +
with message-id 
and subject line Bug#1003664: fixed in fwupd 1.7.4-2
has caused the Debian Bug report #1003664,
regarding fwupd: Too loose dependency on libfwupdN
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.)


-- 
1003664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fwupd
Version: 1.5.7-5
Severity: serious

Hi!

This package seems to use a too loose dependency on at least
libfwupdN, but I suspect the same applies to libfwupdpluginM (or even
libfwupdN from libfwupdpluginM).

These are encoded as >=, which causes them to be upgradable on new
upstream releases, and do break partial upgrades. Right now I've got
fwupd held due to the signed version not being yet available, and
libfwupdplugin1 is not upgraded as that bumped its SONAME, but libfwupd2
did, and now the daemon is segfaulting. This is not the first time
this has happened, but I guess I forgot to file the other time, which
means this seems to be consistent behavior as with requiring exact
versions of the library:

  fwupd[108906]: 21:12:16:0092 GLib-GIO g_file_new_for_path: 
assertion 'path != NULL' failed
  fwupd[108906]: 21:12:16:0092 GLib-GIO g_file_query_file_type: 
assertion 'G_IS_FILE(file)' failed
  fwupd[108906]: 21:12:16:0092 GLib-GIO g_file_monitor_file: 
assertion 'G_IS_FILE (file)' failed
  kernel: fwupd[108906]: segfault at 8 ip 559242c78109 sp 7ffe4df24910 
error 4 in fwupd[559242c73000+26000]
  kernel: Code: ff 85 c0 0f 85 97 02 00 00 48 8b 7c 24 30 e8 5e d5 ff ff e9 67 
01 00 00 48 8b 44 24 28 48 8d 3d dc 14 02 00 41 be 01 00 00 00 <48> 8b 70 08 31 
c0 e8 4c f4 ff ff 4d 85 e4 74 08 4c 89 e7 e8 5f db

So it looks like all the intra library dependencies should be changed
to «libfwup.* (= )».

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: fwupd
Source-Version: 1.7.4-2
Done: Steve McIntyre <93...@debian.org>

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

Debian distribution maintenance software
pp.
Steve McIntyre <93...@debian.org> (supplier of updated fwupd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 10 Feb 2022 00:13:57 +
Source: fwupd
Architecture: source
Version: 1.7.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian EFI 
Changed-By: Steve McIntyre <93...@debian.org>
Closes: 1003664
Changes:
 fwupd (1.7.4-2) unstable; urgency=medium
 .
   * Add hard dependencies on libfwupd2 and libfwupdplugin5 built with
 us. Symbols suggest things should work, but maybe not. :-(
 Closes: #1003664
Checksums-Sha1:
 c8007e970d2ba207061d92bbce102477c5fd6a25 3836 fwupd_1.7.4-2.dsc
 bdceae698e6b53b3490e9a401b5b3a166c8d21ca 29192 fwupd_1.7.4-2.debian.tar.xz
 5f5054562e844d5d53322db45842016a6d91a366 15062 fwupd_1.7.4-2_source.buildinfo
Checksums-Sha256:
 1a7ee01a6d941dce64e92577f74fdc3e0a3b703915442b62e218dafa22b2d300 3836 
fwupd_1.7.4-2.dsc
 b16045d39805df907f0e69d20724273475f7f1d6018b7616134916f6bcf0a332 29192 
fwupd_1.7.4-2.debian.tar.xz
 248496e7f038cbec14409b9aedc6ccc9342cf7cbfac622fbf1f2504a54773c1e 15062 
fwupd_1.7.4-2_source.buildinfo
Files:
 b597062151cddf57a8250ea5e32ab109 3836 admin optional fwupd_1.7.4-2.dsc
 3e1a43f850eaec8de338c68da44b575f 29192 admin optional 
fwupd_1.7.4-2.debian.tar.xz
 66d3b532c838e41b49bf6f9157ff649a 15062 admin optional 
fwupd_1.7.4-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEzrtSMB1hfpEDkP4WWHl5VzRCaE4FAmIEXVARHDkzc2FtQGRl
Ymlhbi5vcmcACgkQWHl5VzRCaE6x8Q//cn8/pP4VYS+n/6whBfuLQoAQkG1OOd6s
xRjrokDrPNV/6OoBNq7ndvckJ2zQu78SB69RoaIvfPNwlB/jehrc0OsLYTCk/OiK
OTG4wekEiitGjGaCn6atesgE0pfie3Lad7sPFH4qLvvGwNcqIFvxF7LawI+ocdqA
ksArvWPyDLbsN4rJvy3wbv6tEyNqsKCWGhjinAE+Q2UADZITA2CDFO6iaZ6IupGv
aguMuBQFRRfVTgilVxTDmwC8MfguGQjP5n9VTfwdE4WjxfhK1nK/BlJW/StM5kUX
RppNeTfgMhHtasHZSpS46y5jSfmzXMgNO15yp1ek1ueIS3ETQsYL8fv78MgH5NSy
K4n37Td8kM0gRpxL2dJFBX2fZm8kxqxAjHhZaIkpp5rIXdOudrswYh/Qgbt/iM1a
LnuLeV0ftlzau3

Bug#1005144: marked as done (fwupd-*-signed-template: Build-Depends missing epoch)

[Debian Bug Tracking System]

Your message dated Wed, 09 Feb 2022 23:48:43 +
with message-id 
and subject line Bug#1005144: fixed in fwupd-efi 1:1.2-3
has caused the Debian Bug report #1005144,
regarding fwupd-*-signed-template: Build-Depends missing epoch
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.)


-- 
1005144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fwupd-efi
Version: 1:1.2-2
Severity: serious

The generated fwupd-amd64-signed 1:1.2+2 source package has:

+---
| Build-Depends: [...] fwupd-unsigned (>= 1.2-2) [amd64], fwupd-unsigned (<< 
1.2-3) [amd64]
+---

This is not satisfiable as the current version of fwupd-unsigned is
1:1.2-2. The build dependency is missing the epoch.

Ansgar
--- End Message ---
--- Begin Message ---
Source: fwupd-efi
Source-Version: 1:1.2-3
Done: Steve McIntyre <93...@debian.org>

We believe that the bug you reported is fixed in the latest version of
fwupd-efi, 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.
Steve McIntyre <93...@debian.org> (supplier of updated fwupd-efi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 09 Feb 2022 23:05:46 +
Source: fwupd-efi
Architecture: source
Version: 1:1.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian EFI 
Changed-By: Steve McIntyre <93...@debian.org>
Closes: 1005144
Changes:
 fwupd-efi (1:1.2-3) unstable; urgency=medium
 .
   [ Mario Limonciello ]
   * Rebuild to fix Build-Depends in the signed-template
 packages. Closes: #1005144
Checksums-Sha1:
 5cd8fc8c9f7a03024667291b1bb89007aa5fa9df 2535 fwupd-efi_1.2-3.dsc
 3b384ba0041c9dee82280dae40fd5df667b96216 8700 fwupd-efi_1.2-3.debian.tar.xz
 7db7ae7b1195391ce457bd792c0b9688bf4e2a17 6524 fwupd-efi_1.2-3_source.buildinfo
Checksums-Sha256:
 66ba87f1b52d2e2b616d09040d91c089c38a1a861cc9c7f348c9e8559396d246 2535 
fwupd-efi_1.2-3.dsc
 586784753fd008b26c3fd137afe6843679c9930a336d99ce974eb0dab1af74cf 8700 
fwupd-efi_1.2-3.debian.tar.xz
 7e2f9a88664dee250d8885f55241dd985786c01e42d0c6588c6c2e50e3451549 6524 
fwupd-efi_1.2-3_source.buildinfo
Files:
 8149ab7ce253416b7527ab1630aa189e 2535 admin optional fwupd-efi_1.2-3.dsc
 07859e91cd65934efcb699156eb51b77 8700 admin optional 
fwupd-efi_1.2-3.debian.tar.xz
 2673b56ad0a4da62bd11d9dfd6288540 6524 admin optional 
fwupd-efi_1.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEzrtSMB1hfpEDkP4WWHl5VzRCaE4FAmIET2QRHDkzc2FtQGRl
Ymlhbi5vcmcACgkQWHl5VzRCaE7m1g/+IVrbxm1qtB3AOXpjOwoR1BUonc0brCHq
aJnZujfyIXkzW7FzqXbIsEB8tsdsJJQyz69kEAVn+qu1TWcX+/r4LPGpKqi6eYi0
1H1yYnznJNN9uLMZL8nJDMkaFDHc+C88m0k5b29dOQz9K3odZy/Ay+cLIHf2JlpN
0VFJvHMgHjcjPXSaYt399sIXlkChKTUhQ/623/8H+RE6Y5mZmp1bG7svBM+0uWKE
/jj2TTmK08P8R6Fr8z/b7t5Rd11j3uc00PBV4KVn9Vr8mALE9xJXwpLbICUoPwXe
EauzqWJN86D1IpHbltjzHbdNkVZHHjVCYrClnDScGnERuLXQo6XYz8SxWnHUGK1b
O3eiE9EuimNbtY9h1jSNdkKTlo6g4G56SeEAP5TbnXiocZFuKbk7Zvl5GSB78pkI
XHjhnxAoECeZQBxxfEbfrIYnoUsoSUQqTrrX0N77yT2/ESAenMPIkpLMA8vrGlQA
2qc78aWX76WpxO7zFuYhQxUyjYudCvCBoHG0U3f+ydiclbtquQAGUwYfaMmakmpW
p+3MDQJL+FtJrFuOpkPK7snTJXk66/kOnG5LTBHf2WPvVxBvNdRJY0fYLyuOE317
crvn1+osKOFb1KC8rC0w2c8X3w4x2xewcNXQ1k/ZA5Li+zVPXmalMKoDEcrbuBml
30WSDZuPPOc=
=84eH
-END PGP SIGNATURE End Message ---

Processed: bug 1005044 is forwarded to https://github.com/zeek/pysubnettree/issues/29

[Debian Bug Tracking System]

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

> forwarded 1005044 https://github.com/zeek/pysubnettree/issues/29
Bug #1005044 [python3-subnettree] python3-subnettree: package completely 
broken, module won't load
Set Bug forwarded-to-address to 
'https://github.com/zeek/pysubnettree/issues/29'.
> thanks
Stopping processing here.

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

Bug#1005255: telegram-desktop: error: ‘Config’ is not a member of ‘webrtc’

[Sebastian Ramacher]

Source: telegram-desktop
Version: 3.4.8+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

telegram-desktop FTBFS:
| cd /<>/obj-x86_64-linux-gnu/Telegram && /usr/bin/c++ 
-DBWE_TEST_LOGGING_COMPILE_TIME_ENABLE=0 -DDESKTOP_APP_DISABLE_CRASH_REPORTS 
-DDESKTOP_APP_USE_PACKAGED -DDESKTOP_APP_USE_PACKAGED_FONTS 
-DDESKTOP_APP_USE_PACKAGED_RLOTTIE -DDESKTOP_APP_USE_PACKED_RESOURCES 
-DHAVE_WEBRTC_VIDEO -DNO_MAIN_THREAD_WRAPPING -DQT_IMPLICIT_QCHAR_CONSTRUCTION 
-DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_KEYWORDS -DRTC_DISABLE_TRACE_EVENTS 
-DRTC_ENABLE_VP9 -DTGCALLS_USE_STD_OPTIONAL -DUSE_RNNOISE=0 
-DWEBRTC_APM_DEBUG_DUMP=0 -DWEBRTC_APP_TDESKTOP -DWEBRTC_DUMMY_AUDIO_BUILD 
-DWEBRTC_ENABLE_PROTOBUF=0 -DWEBRTC_HAVE_USRSCTP 
-DWEBRTC_INCLUDE_INTERNAL_AUDIO_DEVICE -DWEBRTC_LIBRARY_IMPL -DWEBRTC_LINUX 
-DWEBRTC_NON_STATIC_TRACE_EVENT_HANDLERS=1 -DWEBRTC_OPUS_SUPPORT_120MS_PTIME=1 
-DWEBRTC_OPUS_VARIABLE_COMPLEXITY=0 -DWEBRTC_POSIX 
-DWEBRTC_USE_BUILTIN_ISAC_FLOAT -DWEBRTC_USE_H264 -DWEBRTC_USE_PIPEWIRE 
-DWEBRTC_USE_X11 -D_FORTIFY_SOURCE=2 -D_GLIBCXX_ASSERTIONS -D_GNU_SOURCE 
-I/<>/Telegram/ThirdParty/tgcalls 
-I/<>/Telegram/ThirdParty/tgcalls/tgcalls -isystem 
/usr/include/tg_owt -isystem /usr/include/tg_owt/third_party/libyuv/include -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -ftemplate-backtrace-limit=0 -Wdate-time 
-D_FORTIFY_SOURCE=2 -Werror=invalid-pch -fstack-protector-all 
-fstack-clash-protection -fPIC -fno-strict-aliasing -pipe -Wall -W 
-Wno-unused-parameter -Wno-switch -Wno-missing-field-initializers 
-Wno-sign-compare -Wno-deprecated -Wno-maybe-uninitialized -std=gnu++20 -MD -MT 
Telegram/CMakeFiles/lib_tgcalls.dir/ThirdParty/tgcalls/tgcalls/CodecSelectHelper.cpp.o
 -MF 
CMakeFiles/lib_tgcalls.dir/ThirdParty/tgcalls/tgcalls/CodecSelectHelper.cpp.o.d 
-o 
CMakeFiles/lib_tgcalls.dir/ThirdParty/tgcalls/tgcalls/CodecSelectHelper.cpp.o 
-c /<>/Telegram/ThirdParty/tgcalls/tgcalls/CodecSelectHelper.cpp
| /<>/Telegram/ThirdParty/libtgvoip/EchoCanceller.cpp: In 
constructor ‘tgvoip::EchoCanceller::EchoCanceller(bool, bool, bool)’:
| /<>/Telegram/ThirdParty/libtgvoip/EchoCanceller.cpp:31:17: 
error: ‘Config’ is not a member of ‘webrtc’
|31 | webrtc::Config extraConfig;
|   | ^~
| /<>/Telegram/ThirdParty/libtgvoip/EchoCanceller.cpp:36:53: 
error: ‘extraConfig’ was not declared in this scope
|36 | apm=webrtc::AudioProcessingBuilder().Create(extraConfig);
|   | ^~~
| make[3]: *** [Telegram/CMakeFiles/lib_tgvoip_bundled.dir/build.make:121: 
Telegram/CMakeFiles/lib_tgvoip_bundled.dir/ThirdParty/libtgvoip/EchoCanceller.cpp.o]
 Error 1

See
https://buildd.debian.org/status/fetch.php?pkg=telegram-desktop&arch=amd64&ver=3.4.8%2Bds-1%2Bb1&stamp=161066&raw=0

Cheers
-- 
Sebastian Ramacher

Bug#1005254: libcoq-mathcomp,libcoq-mathcomp-*: missing Breaks+Replaces: libssreflect-coq (<< 1.14.0-4)

[Andreas Beckmann]

Source: ssreflect
Version: 1.14.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package libcoq-mathcomp-ssreflect.
  Preparing to unpack .../0-libcoq-mathcomp-ssreflect_1.14.0-5_all.deb ...
  Unpacking libcoq-mathcomp-ssreflect (1.14.0-5) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-QHGYI4/0-libcoq-mathcomp-ssreflect_1.14.0-5_all.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/ocaml/coq/user-contrib/mathcomp/ssreflect/all_ssreflect.glob', which 
is also in package libssreflect-coq 1.14.0-3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Selecting previously unselected package libcoq-mathcomp-fingroup.
  Preparing to unpack .../1-libcoq-mathcomp-fingroup_1.14.0-5_all.deb ...
  Unpacking libcoq-mathcomp-fingroup (1.14.0-5) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-QHGYI4/1-libcoq-mathcomp-fingroup_1.14.0-5_all.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/ocaml/coq/user-contrib/mathcomp/fingroup/action.glob', which is also 
in package libssreflect-coq 1.14.0-3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Selecting previously unselected package libcoq-mathcomp-algebra.
  Preparing to unpack .../2-libcoq-mathcomp-algebra_1.14.0-5_all.deb ...
  Unpacking libcoq-mathcomp-algebra (1.14.0-5) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-QHGYI4/2-libcoq-mathcomp-algebra_1.14.0-5_all.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/ocaml/coq/user-contrib/mathcomp/algebra/all_algebra.glob', which is 
also in package libssreflect-coq 1.14.0-3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Selecting previously unselected package libcoq-mathcomp-solvable.
  Preparing to unpack .../3-libcoq-mathcomp-solvable_1.14.0-5_all.deb ...
  Unpacking libcoq-mathcomp-solvable (1.14.0-5) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-QHGYI4/3-libcoq-mathcomp-solvable_1.14.0-5_all.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/ocaml/coq/user-contrib/mathcomp/solvable/abelian.glob', which is also 
in package libssreflect-coq 1.14.0-3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Selecting previously unselected package libcoq-mathcomp-field.
  Preparing to unpack .../4-libcoq-mathcomp-field_1.14.0-5_all.deb ...
  Unpacking libcoq-mathcomp-field (1.14.0-5) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-QHGYI4/4-libcoq-mathcomp-field_1.14.0-5_all.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/ocaml/coq/user-contrib/mathcomp/field/algC.glob', which is also in 
package libssreflect-coq 1.14.0-3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Selecting previously unselected package libcoq-mathcomp-character.
  Preparing to unpack .../5-libcoq-mathcomp-character_1.14.0-5_all.deb ...
  Unpacking libcoq-mathcomp-character (1.14.0-5) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-QHGYI4/5-libcoq-mathcomp-character_1.14.0-5_all.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/ocaml/coq/user-contrib/mathcomp/character/all_character.glob', which 
is also in package libssreflect-coq 1.14.0-3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Selecting previously unselected package libcoq-mathcomp.
  Preparing to unpack .../6-libcoq-mathcomp_1.14.0-5_all.deb ...
  Unpacking libcoq-mathcomp (1.14.0-5) ...
  Replacing files in old package libssreflect-coq (1.14.0-3) ...
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-QHGYI4/0-libcoq-mathcomp-ssreflect_1.14.0-5_all.deb
   /tmp/apt-dpkg-install-QHGYI4/1-libcoq-mathcomp-fingroup_1.14.0-5_all.deb
   /tmp/apt-dpkg-install-QHGYI4/2-libcoq-mathcomp-algebra_1.14.0-5_all.deb
   /tmp/apt-dpkg-install-QHGYI4/3-libcoq-mathcomp-solvable_1.14.0-5_all.deb
   /tmp/apt-dpkg-install-QHGYI4/4-libcoq-mathcomp-field_1.14.0-5_all.deb
   /tmp/apt-dpkg-install-QHGYI4/5-libcoq-mathcomp-character_1.14.0-5_all.deb


The packages seem to have
  Breaks: libssreflect-coq (<= 1.14.0-2)
which does not match the version in testing (1.14.0-3)
but they are also missing the corresponding Replaces.


cheers,

Andreas


libssreflect-coq=1.14.0-3_libcoq-mathcomp=1.14.0-5.log.gz
Description: application/gzip

Bug#1005044: python3-subnettree: package completely broken, module won't load

[Michael Stone]

On Wed, Feb 09, 2022 at 04:32:43PM -0500, Scott Kitterman wrote:

On Sat, 5 Feb 2022 17:28:04 -0500 Michael Stone  wrote:

It seems to be some kind of incompatibility in swig. Upstream .cc files
are built with swig 3, debian has swig 4. If the package is built with
the upstream .cc files (ditching the associated lines in debian/rules)
it seems to work fine.


Thanks.  I agree.  The bad news is that would trade a DFSG issue for a
technical issue, which might be considered progress (since the generated files
can't be regenerated within Main anymore).


I'd argue that's the least-bad option right now for a fix in bullseye. 
It's IMO a DFSG-pedantic issue as the files can be regenerated with free 
software, just not with anything currently packaged in debian (e.g., 
with the buster version of swig). Would definitely be better than a 
completely unusable package. (A change to the .i that makes everything 
work would be even better obviously, but I have no idea how swig is 
supposed to work.)

Bug#1005044: python3-subnettree: package completely broken, module won't load

[Scott Kitterman]

On Sat, 5 Feb 2022 17:28:04 -0500 Michael Stone  wrote:
> It seems to be some kind of incompatibility in swig. Upstream .cc files 
> are built with swig 3, debian has swig 4. If the package is built with 
> the upstream .cc files (ditching the associated lines in debian/rules) 
> it seems to work fine.

Thanks.  I agree.  The bad news is that would trade a DFSG issue for a 
technical issue, which might be considered progress (since the generated files 
can't be regenerated within Main anymore).  I have experimented with the 
available knobs provided by swig and not found anything that works.

I'll talk with upstream and see if they have any suggestions.

Scott K

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

Bug#1005250: r-cran-rlang breaks r-cran-tidyselect autopkgtest: catch_cnd(vars_select(letters, starts_with("1"))) inherits from `'lifecycle_soft_deprecated'/'condition'` not `'character'`.

[Paul Gevers]

Source: r-cran-rlang, r-cran-tidyselect
Control: found -1 r-cran-rlang/1.0.0-1
Control: found -1 r-cran-tidyselect/1.1.1+dfsg-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
r-cran-rlang   from testing1.0.0-1
r-cran-tidyselect  from testing1.1.1+dfsg-1
all others from testingfrom testing

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

Currently this regression is blocking the migration of r-cran-rlang 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=r-cran-rlang

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-tidyselect/19094216/log.gz

BEGIN TEST testthat.R

R version 4.1.2 (2021-11-01) -- "Bird Hippie"
Copyright (C) 2021 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.


library("testthat")
library("rlang")


Attaching package: 'rlang'

The following objects are masked from 'package:testthat':

is_false, is_null, is_true


library("tidyselect")


Attaching package: 'tidyselect'

The following object is masked from 'package:testthat':

matches



test_check("tidyselect")

[ FAIL 1 | WARN 2 | SKIP 18 | PASS 452 ]

== Skipped tests 
===

* FIXME (1)
* Non-deterministic failures (1)
* On CRAN (16)

== Failed tests 

-- Failure (test-lifecycle-deprecated.R:73:3): empty selection signals a 
condition --
catch_cnd(vars_select(letters, starts_with("1"))) inherits from 
`'lifecycle_soft_deprecated'/'condition'` not `'character'`.


[ FAIL 1 | WARN 2 | SKIP 18 | PASS 452 ]
Error: Test failures
Execution halted
autopkgtest [18:11:58]: test run-unit-test



OpenPGP_signature
Description: OpenPGP digital signature

Processed: r-cran-rlang breaks r-cran-tidyselect autopkgtest: catch_cnd(vars_select(letters, starts_with("1"))) inherits from `'lifecycle_soft_deprecated'/'condition'` not `'character'`.

[Debian Bug Tracking System]

Processing control commands:

> found -1 r-cran-rlang/1.0.0-1
Bug #1005250 [src:r-cran-rlang, src:r-cran-tidyselect] r-cran-rlang breaks 
r-cran-tidyselect autopkgtest: catch_cnd(vars_select(letters, 
starts_with("1"))) inherits from `'lifecycle_soft_deprecated'/'condition'` not 
`'character'`.
Marked as found in versions r-cran-rlang/1.0.0-1.
> found -1 r-cran-tidyselect/1.1.1+dfsg-1
Bug #1005250 [src:r-cran-rlang, src:r-cran-tidyselect] r-cran-rlang breaks 
r-cran-tidyselect autopkgtest: catch_cnd(vars_select(letters, 
starts_with("1"))) inherits from `'lifecycle_soft_deprecated'/'condition'` not 
`'character'`.
Marked as found in versions r-cran-tidyselect/1.1.1+dfsg-1.

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

Processed: Re: Bug#1005016: libobject-pad-slotattr-final-perl: Object::Pad::SlotAttr::Final is replaced by Object::Pad::FieldAttr::Final

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1005016 [src:libobject-pad-slotattr-final-perl] 
libobject-pad-slotattr-final-perl: Object::Pad::SlotAttr::Final is replaced by 
Object::Pad::FieldAttr::Final
Severity set to 'serious' from 'normal'
> tag -1 + sid bookworm
Bug #1005016 [src:libobject-pad-slotattr-final-perl] 
libobject-pad-slotattr-final-perl: Object::Pad::SlotAttr::Final is replaced by 
Object::Pad::FieldAttr::Final
Added tag(s) bookworm and sid.
> clone -1 -2
Bug #1005016 [src:libobject-pad-slotattr-final-perl] 
libobject-pad-slotattr-final-perl: Object::Pad::SlotAttr::Final is replaced by 
Object::Pad::FieldAttr::Final
Bug 1005016 cloned as bug 1005245
> reassign -2 src:libobject-pad-slotattr-isa-perl 0.02-2
Bug #1005245 [src:libobject-pad-slotattr-final-perl] 
libobject-pad-slotattr-final-perl: Object::Pad::SlotAttr::Final is replaced by 
Object::Pad::FieldAttr::Final
Bug reassigned from package 'src:libobject-pad-slotattr-final-perl' to 
'src:libobject-pad-slotattr-isa-perl'.
No longer marked as found in versions libobject-pad-slotattr-final-perl/0.04-2.
Ignoring request to alter fixed versions of bug #1005245 to the same values 
previously set
Bug #1005245 [src:libobject-pad-slotattr-isa-perl] 
libobject-pad-slotattr-final-perl: Object::Pad::SlotAttr::Final is replaced by 
Object::Pad::FieldAttr::Final
Marked as found in versions libobject-pad-slotattr-isa-perl/0.02-2.
> retitle -2 Object::Pad::SlotAttr::Isa is replaced by 
> Object::Pad::FieldAttr::Isa
Bug #1005245 [src:libobject-pad-slotattr-isa-perl] 
libobject-pad-slotattr-final-perl: Object::Pad::SlotAttr::Final is replaced by 
Object::Pad::FieldAttr::Final
Changed Bug title to 'Object::Pad::SlotAttr::Isa is replaced by 
Object::Pad::FieldAttr::Isa' from 'libobject-pad-slotattr-final-perl: 
Object::Pad::SlotAttr::Final is replaced by Object::Pad::FieldAttr::Final'.
> severity -2 serious
Bug #1005245 [src:libobject-pad-slotattr-isa-perl] Object::Pad::SlotAttr::Isa 
is replaced by Object::Pad::FieldAttr::Isa
Ignoring request to change severity of Bug 1005245 to the same value.
> tag -2 + sid bookworm
Bug #1005245 [src:libobject-pad-slotattr-isa-perl] Object::Pad::SlotAttr::Isa 
is replaced by Object::Pad::FieldAttr::Isa
Ignoring request to alter tags of bug #1005245 to the same tags previously set
> clone -1 -3
Bug #1005016 [src:libobject-pad-slotattr-final-perl] 
libobject-pad-slotattr-final-perl: Object::Pad::SlotAttr::Final is replaced by 
Object::Pad::FieldAttr::Final
Bug 1005016 cloned as bug 1005246
> reassign -3 src:libobject-pad-slotattr-lazyinit-perl 0.04-2
Bug #1005246 [src:libobject-pad-slotattr-final-perl] 
libobject-pad-slotattr-final-perl: Object::Pad::SlotAttr::Final is replaced by 
Object::Pad::FieldAttr::Final
Bug reassigned from package 'src:libobject-pad-slotattr-final-perl' to 
'src:libobject-pad-slotattr-lazyinit-perl'.
No longer marked as found in versions libobject-pad-slotattr-final-perl/0.04-2.
Ignoring request to alter fixed versions of bug #1005246 to the same values 
previously set
Bug #1005246 [src:libobject-pad-slotattr-lazyinit-perl] 
libobject-pad-slotattr-final-perl: Object::Pad::SlotAttr::Final is replaced by 
Object::Pad::FieldAttr::Final
Marked as found in versions libobject-pad-slotattr-lazyinit-perl/0.04-2.
> retitle -3 Object::Pad::SlotAttr::LazyInit is replaced by 
> Object::Pad::FieldAttr::LazyInit
Bug #1005246 [src:libobject-pad-slotattr-lazyinit-perl] 
libobject-pad-slotattr-final-perl: Object::Pad::SlotAttr::Final is replaced by 
Object::Pad::FieldAttr::Final
Changed Bug title to 'Object::Pad::SlotAttr::LazyInit is replaced by 
Object::Pad::FieldAttr::LazyInit' from 'libobject-pad-slotattr-final-perl: 
Object::Pad::SlotAttr::Final is replaced by Object::Pad::FieldAttr::Final'.
> severity -3 serious
Bug #1005246 [src:libobject-pad-slotattr-lazyinit-perl] 
Object::Pad::SlotAttr::LazyInit is replaced by Object::Pad::FieldAttr::LazyInit
Ignoring request to change severity of Bug 1005246 to the same value.
> tag -2 + sid bookworm
Bug #1005245 [src:libobject-pad-slotattr-isa-perl] Object::Pad::SlotAttr::Isa 
is replaced by Object::Pad::FieldAttr::Isa
Ignoring request to alter tags of bug #1005245 to the same tags previously set
> clone -1 -4
Bug #1005016 [src:libobject-pad-slotattr-final-perl] 
libobject-pad-slotattr-final-perl: Object::Pad::SlotAttr::Final is replaced by 
Object::Pad::FieldAttr::Final
Bug 1005016 cloned as bug 1005247
> reassign -4 src:libobject-pad-slotattr-trigger-perl 0.05-2
Bug #1005247 [src:libobject-pad-slotattr-final-perl] 
libobject-pad-slotattr-final-perl: Object::Pad::SlotAttr::Final is replaced by 
Object::Pad::FieldAttr::Final
Bug reassigned from package 'src:libobject-pad-slotattr-final-perl' to 
'src:libobject-pad-slotattr-trigger-perl'.
No longer marked as found in versions libobject-pad-slotattr-final-perl/0.04-2.
Ignoring request to alter fixed versions of bug #1005247 to the same values 
previously set
Bug #1005247 [src:libobject-pad-slotattr-trigger-p

Processed: src:liblouis: fails to migrate to testing for too long: unresolved RC bug

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.20.0-1
Bug #1005244 [src:liblouis] src:liblouis: fails to migrate to testing for too 
long: unresolved RC bug
Marked as fixed in versions liblouis/3.20.0-1.
Bug #1005244 [src:liblouis] src:liblouis: fails to migrate to testing for too 
long: unresolved RC bug
Marked Bug as done
> block -1 by 1001841
Bug #1005244 {Done: Paul Gevers } [src:liblouis] 
src:liblouis: fails to migrate to testing for too long: unresolved RC bug
1005244 was not blocked by any bugs.
1005244 was not blocking any bugs.
Added blocking bug(s) of 1005244: 1002097 and 1001841

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

Bug#1005244: src:liblouis: fails to migrate to testing for too long: unresolved RC bug

[Paul Gevers]

Source: liblouis
Version: 3.19.0-2
Severity: serious
Control: close -1 3.20.0-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1001841

Dear all, Samuel,

I already discussed this issue on IRC with Samuel, but I'm going to file 
this bug nevertheless. The following paragraphs are templated, but I 
aligned with Samuel that the RC bug is a genuine issue that correctly 
prevents migration. We're waiting for a solution upstream. If it's not 
coming in the next months or two, we'll probably revert liblouis. 
liblouis is a key package, so it can't be removed from testing.


 bug template 

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:liblouis has been trying to migrate for 64 
days [2]. Hence, I am filing this bug.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=liblouis


OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:pygments: fails to migrate to testing for too long: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.10.0+dfsg-1
Bug #1005243 [src:pygments] src:pygments: fails to migrate to testing for too 
long: autopkgtest regression
Marked as fixed in versions pygments/2.10.0+dfsg-1.
Bug #1005243 [src:pygments] src:pygments: fails to migrate to testing for too 
long: autopkgtest regression
Marked Bug as done

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

Bug#1005243: src:pygments: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: pygments
Version: 2.7.1+dfsg-2.1
Severity: serious
Control: close -1 2.10.0+dfsg-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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:pygments has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. The upload causes an autopkgtest 
regression in djangorestframework.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=pygments



OpenPGP_signature
Description: OpenPGP digital signature

Bug#984031: marked as done (diagnostics: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Wed, 09 Feb 2022 19:34:12 +
with message-id 
and subject line Bug#984031: fixed in diagnostics 0.3.3-12.2
has caused the Debian Bug report #984031,
regarding diagnostics: ftbfs with GCC-11
to be marked as done.

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

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


-- 
984031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:diagnostics
Version: 0.3.3-12.1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/diagnostics_0.3.3-12.1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
libtool: link: x86_64-linux-gnu-g++ -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic 
-Wno-unused-function -Wl,-z -Wl,relro -o .libs/test_case_cstr 
test_case_cstr.t.o  ../../diagnostics/.libs/libdiagnostics.so 
test_system/.libs/libtest_system_ts.a ../util/.libs/libutil_ts.a -lACE -lpthread
x86_64-linux-gnu-g++ -DHAVE_CONFIG_H   -I../.. -DDEBUG__LEVEL__=2 -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic 
-Wno-unused-function -MT test_suite.t.o -MD -MP -MF .deps/test_suite.t.Tpo -c 
-o test_suite.t.o test_suite.t.cpp
mv -f .deps/test_suite.t.Tpo .deps/test_suite.t.Po
/bin/bash ../../libtool  --tag=CXX   --mode=link x86_64-linux-gnu-g++  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pedantic -Wno-unused-function  -Wl,-z,relro 
-lACE -lpthread -o test_suite test_suite.t.o 
../../diagnostics/libdiagnostics.la test_system/libtest_system_ts.la 
../util/libutil_ts.la 
libtool: link: x86_64-linux-gnu-g++ -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic 
-Wno-unused-function -Wl,-z -Wl,relro -o .libs/test_suite test_suite.t.o  
../../diagnostics/.libs/libdiagnostics.so test_system/.libs/libtest_system_ts.a 
../util/.libs/libutil_ts.a -lACE -lpthread
make[9]: Leaving directory '/<>/diagnostics/unittest'
/usr/bin/make  check-TESTS
make[9]: Entering directory '/<>/diagnostics/unittest'
make[10]: Entering directory '/<>/diagnostics/unittest'
PASS: func_test_case
PASS: name_separators
PASS: std_test_case
PASS: test_case_cstr
PASS: test_suite

Testsuite summary for diagnostics 0.3.3

# TOTAL: 5
# PASS:  5
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0

make[10]: Leaving directory '/<>/diagnostics/unittest'
make[9]: Leaving directory '/<>/diagnostics/unittest'
make[8]: Leaving directory '/<>/diagnostics/unittest'
make[7]: Leaving directory '/<>/diagnostics/unittest'
make[6]: Leaving directory '/<>/diagnostics/unittest'
Making check in util
make[6]: Entering directory '/<>/diagnostics/util'
/usr/bin/make  check-recursive
make[7]: Entering directory '/<>/diagnostics/util'
make[8]: Entering directory '/<>/diagnostics/util'
/usr/bin/make  diff diff_generator
make[9]

Bug#1005151: marked as done (xtpcpp FTBFS with libpappsomspp-dev 0.8.48-1)

[Debian Bug Tracking System]

Your message dated Wed, 09 Feb 2022 19:10:13 +
with message-id 
and subject line Bug#1005151: fixed in xtpcpp 0.4.51-1
has caused the Debian Bug report #1005151,
regarding xtpcpp FTBFS with libpappsomspp-dev 0.8.48-1
to be marked as done.

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

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


-- 
1005151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005151
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xtpcpp
Version: 0.4.43-1.1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=xtpcpp&ver=0.4.43-1.1

...
/<>/src/core/msrun.cpp:44:10: fatal error: 
pappsomspp/processing/filters/filterpseudocentroid.h: No such file or directory
   44 | #include 
  |  ^~
compilation terminated.
make[4]: *** [src/CMakeFiles/xtpcpp.dir/build.make:690: 
src/CMakeFiles/xtpcpp.dir/core/msrun.cpp.o] Error 1
--- End Message ---
--- Begin Message ---
Source: xtpcpp
Source-Version: 0.4.51-1
Done: Filippo Rusconi 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 09 Feb 2022 15:33:40 +0100
Source: xtpcpp
Binary: xtpcpp xtpcpp-dbgsym xtpcpp-doc xtpcpp-tandemwrapper 
xtpcpp-tandemwrapper-dbgsym
Architecture: source amd64 all
Version: 0.4.51-1
Distribution: unstable
Urgency: medium
Maintainer: The Debichem Group 
Changed-By: Filippo Rusconi 
Description:
 xtpcpp - C++ version of X!TandemPipeline
 xtpcpp-doc - C++ version of X!TandemPipeline (user manual)
 xtpcpp-tandemwrapper - X!Tandem wrapper for timsTOF pro and modern mzML data
Closes: 1005151
Changes:
 xtpcpp (0.4.51-1) unstable; urgency=medium
 .
   * New upstream release now building on top of libpappsomspp 0.8.48 (Closes:
 #1005151, thanks to Adrian Bunk ).
 .
   [ Filippo Rusconi ]
 .
   * betterment of the whole manual
   * rename the binary package from tandemwrapper to xtpcpp-tandemwrapper
 .
   [ Olivier Langella ]
 .
   * replacement of old sax based XML parsers for tandem presets and HTCondor
   * new test on XML parsers
   * new formula column added in the peptide ODS output
Checksums-Sha1:
 400874de8d3376ddb67dbc32c94b38a0d3172205 2276 xtpcpp_0.4.51-1.dsc
 6caf832d15deb280393a00a73528a4df68b371e3 23450318 xtpcpp_0.4.51.orig.tar.gz
 ad0d322d6abe985a9abd09f043763ccfa96a6a86 274044 xtpcpp_0.4.51-1.debian.tar.xz
 78205ad513ed1b8a0a0c07fec562cd53ddad991c 32875920 
xtpcpp-dbgsym_0.4.51-1_amd64.deb
 b643775f009edbea681144e2da20b57fb5d11817 29801984 xtpcpp-doc_0.4.51-1_all.deb
 81bba4bab73920c32bda69825eccbfd2ebbf238d 207720 
xtpcpp-tandemwrapper-dbgsym_0.4.51-1_amd64.deb
 1db27acb211bcc30c1aaac83b2b0ea48f003bcef 22596 
xtpcpp-tandemwrapper_0.4.51-1_amd64.deb
 8db652963e649babbee7370519761507aebc805a 19131 xtpcpp_0.4.51-1_amd64.buildinfo
 7edcc5b19020bc563a8a6c016a812e058344e38e 1167228 xtpcpp_0.4.51-1_amd64.deb
Checksums-Sha256:
 2fb5d61c6c4c2ca552cee45cef9d9b1a8d30204377eac9165a48542b95c226f0 2276 
xtpcpp_0.4.51-1.dsc
 8c9f8f39636d86fc6e4f1a8a118de8544a205ee3419ea87018c6731f30e4ccf7 23450318 
xtpcpp_0.4.51.orig.tar.gz
 1ffc527364a3c59a7b3ef3a9270f195b744c90255c2b1adcd3e3265739365262 274044 
xtpcpp_0.4.51-1.debian.tar.xz
 5c3e92bf9a70de86266ab70815cc0c13a4f579190921b685e51cb9c1a70106c3 32875920 
xtpcpp-dbgsym_0.4.51-1_amd64.deb
 7e25d025c409c464044a6df3bd1107af28db4ae821b3f7b319e151f9a8c430ff 29801984 
xtpcpp-doc_0.4.51-1_all.deb
 b3fa0fe3b673b5e8ad7c16eb49de0d33ad51b6891a7a5d55485f6bf8a88016ff 207720 
xtpcpp-tandemwrapper-dbgsym_0.4.51-1_amd64.deb
 8d69bd8516e3f64d58f204ac551c8b524ee8b2f431631929fd4da5a179cd001a 22596 
xtpcpp-tandemwrapper_0.4.51-1_amd64.deb
 0948ef9396cb363134fe69ec6a48f1039aecc9024c203e571a9842c0ec85a151 19131 
xtpcpp_0.4.51-1_amd64.buildinfo
 92ed3b4d5b8e5667f9aca57caba79a491c37fb87ce1533afd36a79d9290a2696 1167228 
xtpcpp_0.4.51-1_amd64.deb
Files:
 3c2acb4e14f281736ff632025d1d121c 2276 science optional xtpcpp_0.4.51-1.dsc
 66446b4c72a

Bug#1004566: marked as done (wesnoth-1.16-data: '/usr/share/icons/HighContrast/scalable/apps/wesnoth-icon.svg', which is also in package wesnoth-1.14-data 1:1.14.17-2)

[Debian Bug Tracking System]

Your message dated Wed, 09 Feb 2022 18:05:45 +
with message-id 
and subject line Bug#1004566: fixed in wesnoth-1.16 1:1.16.2-2
has caused the Debian Bug report #1004566,
regarding wesnoth-1.16-data: 
'/usr/share/icons/HighContrast/scalable/apps/wesnoth-icon.svg', which is also 
in package wesnoth-1.14-data 1:1.14.17-2
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.)


-- 
1004566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wesnoth-1.16-data
Version: 1:1.16.1-1
Severity: grave
Tags: a11y
Justification: renders package unusable

Dear Maintainer,

During the upgrade from wesnoth-1.14 to wesnoth-1.16 in sid, I got the 
following message:

Unpacking wesnoth-1.16-data (1:1.16.1-1) ...
dpkg: error processing archive 
/var/cache/apt/archives/wesnoth-1.16-data_1%3a1.16.1-1_all.deb (--unpack):
 trying to overwrite 
'/usr/share/icons/HighContrast/scalable/apps/wesnoth-icon.svg', which is also 
in package wesnoth-1.14-data 1:1.14.17-2
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

It broke the upgrade in the middle.

I guess it will be solved in first removing wesnoth-1.14* packages and running 
an 'apt --fix-broken install'.

Regards,

Jean-Marc


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

Kernel: Linux 5.15.0-3-amd64 (SMP w/8 CPU threads)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wesnoth-1.16-data depends on:
ii  fonts-adf-oldania 0.20190904-2
ii  fonts-dejavu-core 2.37-2
ii  fonts-dejavu-extra2.37-2
ii  fonts-droid-fallback  1:6.0.1r16-1.1
ii  fonts-lato2.0-2.1

wesnoth-1.16-data recommends no packages.

Versions of packages wesnoth-1.16-data suggests:
iu  wesnoth-1.16-music  1:1.16.1-1
--- End Message ---
--- Begin Message ---
Source: wesnoth-1.16
Source-Version: 1:1.16.2-2
Done: Rhonda D'Vine 

We believe that the bug you reported is fixed in the latest version of
wesnoth-1.16, 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.
Rhonda D'Vine  (supplier of updated wesnoth-1.16 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Feb 2022 17:33:17 +0100
Source: wesnoth-1.16
Architecture: source
Version: 1:1.16.2-2
Distribution: unstable
Urgency: low
Maintainer: Debian Games Team 
Changed-By: Rhonda D'Vine 
Closes: 1004566
Changes:
 wesnoth-1.16 (1:1.16.2-2) unstable; urgency=low
 .
   * Fix icon renaming for avoiding filename conflict with other wesnoth
 releases (closes: #1004566)
Checksums-Sha1:
 45dac0b1ce89361b4551345f55771719cfae454a 4011 wesnoth-1.16_1.16.2-2.dsc
 abbede3bd06e15d9dd54f7285f13d773f6b97d9f 68376 
wesnoth-1.16_1.16.2-2.debian.tar.xz
 c81c10151373d05c693b5984cb858558b5862654 22563 
wesnoth-1.16_1.16.2-2_amd64.buildinfo
Checksums-Sha256:
 bd619a14a0c3bfd0d200d81417bedf8628a74216da5a314a68697a07ecb97d9f 4011 
wesnoth-1.16_1.16.2-2.dsc
 bfc16672cdb769966ea15d5c89cbf85b6df6907baef142861ba8379e09a64758 68376 
wesnoth-1.16_1.16.2-2.debian.tar.xz
 6353c9dc878db6bd6de0f57e69831ce736564ca4801591924d5e1a3b790a6c6a 22563 
wesnoth-1.16_1.16.2-2_amd64.buildinfo
Files:
 e3a959fa143cc0d52e58fc0ed2d84bd9 4011 games optional wesnoth-1.16_1.16.2-2.dsc
 d93c5e7cbcaef432a44906c7f0b7884c 68376 games optional 
wesnoth-1.16_1.16.2-2.debian.tar.xz
 1559fe78d664ce4e2ee68fda587f90c2 22563 games optional 
wesnoth-1.16_1.16.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEELHLzKO0XByBPs0mU3ugEPuF+uzAFAmID/JcACgkQ3ugEPuF+
uzBAIBAAkso0O8g/K7TQYqpyZD8XtCHXUeM6UGichagd+FCTolJtqn3cwzw4GSNa
EiSGqqnNaXn7B8Plzjs3K5rVy3DOYeW2aCOQFeeQyFfAARh30NswEQ56+8L+m8lj
ya1TwvlqvCv1OIHIKEWnxT5KJBobz/ch37hek8JANXdUrxleNhtNC7YWlydU752O
8pMEWljGQUMZffEkCl/62LFfSSp8/lA7mOULCs2U6DjVSmzcEWq+8NLP6P23flOa
qgIbF0Nn3sAaVGXeu0qjzLLMhVwQgAvuNWKEHl0MQIg+whtRvXEWxgQTIBYlLK9I
w/OMI

Processed: bug 1003810 is forwarded to https://github.com/shlomif/perl-XML-LibXML/pull/69

[Debian Bug Tracking System]

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

> forwarded 1003810 https://github.com/shlomif/perl-XML-LibXML/pull/69
Bug #1003810 [libxml-libxml-perl] libxml-libxml-perl: when XML::LibXML::Parser 
validation is set to 1, the DTD is not read; entities not expanded
Changed Bug forwarded-to-address to 
'https://github.com/shlomif/perl-XML-LibXML/pull/69' from 
'https://github.com/shlomif/perl-XML-LibXML/pull/48'.
> thanks
Stopping processing here.

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

Bug#716386: [Mayhem] Bug report on tetradraw: tetraview crashes with exit status 139

[Lee Garrett]

Package: tetradraw
Version: 2.0.3-9+b2
Followup-For: Bug #716386
X-Debbugs-Cc: deb...@rocketjump.eu

Hi Rhonda,

sorry to grave dig this bug report, but it seems that tetradraw might be broken
for a couple of releases now. On bullseye it segfaults with rc 139. A few people
in #debian reported the same issue, so it looks like it's 100% reproducible.
Since I'd love to make some nice ascii art for my /etc/motd, it would be nice if
you could find the time to fix it. Thanks in advance!

Kind regards,
Lee


-- System Information:
Debian Release: 11.2
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.16.1 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tetradraw depends on:
ii  libc6 2.31-13+deb11u2
ii  libncursesw6  6.2+20201114-2
ii  libtinfo6 6.2+20201114-2

tetradraw recommends no packages.

tetradraw suggests no packages.

-- no debconf information

Processed: severity of 716386 is grave

[Debian Bug Tracking System]

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

> severity 716386 grave
Bug #716386 [tetradraw] [Mayhem] Bug report on tetradraw: tetraview crashes 
with exit status 139
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Processed: found 716386 in 2.0.3-9+b2

[Debian Bug Tracking System]

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

> found 716386 2.0.3-9+b2
Bug #716386 [tetradraw] [Mayhem] Bug report on tetradraw: tetraview crashes 
with exit status 139
Marked as found in versions tetradraw/2.0.3-9.
> thanks
Stopping processing here.

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

Processed: limit source to wesnoth-1.16, tagging 1004566

[Debian Bug Tracking System]

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

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

> tags 1004566 + pending
Bug #1004566 [wesnoth-1.16-data] wesnoth-1.16-data: 
'/usr/share/icons/HighContrast/scalable/apps/wesnoth-icon.svg', which is also 
in package wesnoth-1.14-data 1:1.14.17-2
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1004693: marked as pending in samba

[Salvatore Bonaccorso]

Control: tag -1 pending

Hello,

Bug #1004693 in samba 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/samba-team/samba/-/commit/27979f306a6f3f995d96fb7f6d3616c5a056ffd1


Add patches for CVE-2021-44142 (Closes: #1004693)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1004693

Processed: Bug#1004693 marked as pending in samba

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1004693 [src:samba] samba: CVE-2021-44142
Added tag(s) pending.

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

Processed: ansible: misbuilds with two supported Python versions

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:ansible 2.10.7+merged+base+2.10.8+dfsg-1
Bug #1005149 [dh-python] pybuild not cleanly removing 
/usr/lib/python3.10/dist-packages
Bug reassigned from package 'dh-python' to 'src:ansible'.
No longer marked as found in versions dh-python/5.20220119.
Ignoring request to alter fixed versions of bug #1005149 to the same values 
previously set
Bug #1005149 [src:ansible] pybuild not cleanly removing 
/usr/lib/python3.10/dist-packages
Marked as found in versions ansible/2.10.7+merged+base+2.10.8+dfsg-1.
> severity -1 serious
Bug #1005149 [src:ansible] pybuild not cleanly removing 
/usr/lib/python3.10/dist-packages
Severity set to 'serious' from 'normal'
> affects -1 + src:dh-python
Bug #1005149 [src:ansible] pybuild not cleanly removing 
/usr/lib/python3.10/dist-packages
Added indication that 1005149 affects src:dh-python
> tags -1 + ftbfs
Bug #1005149 [src:ansible] pybuild not cleanly removing 
/usr/lib/python3.10/dist-packages
Added tag(s) ftbfs.
> retitle -1 ansible: misbuilds with two supported Python versions
Bug #1005149 [src:ansible] pybuild not cleanly removing 
/usr/lib/python3.10/dist-packages
Changed Bug title to 'ansible: misbuilds with two supported Python versions' 
from 'pybuild not cleanly removing /usr/lib/python3.10/dist-packages'.

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

Bug#991036: Bug#993849: [Debian-on-mobile-maintainers] Bug#991036: libhandy: Should this package be removed in bookworm?

[Henry-Nicolas Tourneur]

Le mercredi 09 février 2022 à 09:32 +0100, Guido Günther a écrit :
> Hi,

Hello Adrian, Guido,


> On Wed, Feb 09, 2022 at 06:27:50AM +0200, Adrian Bunk wrote:
> > Control: severity -1 serious
> > 
> > libhandy is about to be removed from bookworm due to this,
> > gnome-authenticator and gnome-metronome need to be updated.
> 
> Just to confirm: I think removal is fine, this API version is
> unmaintained upstream and libhandy-1 and libadwaita are in Debian.
> Cheers,

Regarding gnome-authenticator (which I maintain through DPT), the
application has been rewritten in Rust and it now uses GTK4 and
libadwaita.

All the dependencies (rust crates) of the updated gnome-authenticator
are unfortunately not yet all packaged and available in the archive.

I am working together with the Rust team to get those dependencies
available in the archive, although since there are many new packages,
those need a trip through NEW which adds some overall delay regarding
their availability.

This means that most likely gnome-authenticator will get removed before
the new version could be uploaded. 
I certainly aim for the updated gnome-authenticator to be available for
the bookworm release.


>  -- Guido
> 

Henry-Nicolas


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

Bug#973816: marked as done (qemu-sbuild-utils)

[Debian Bug Tracking System]

Your message dated Wed, 09 Feb 2022 14:56:14 +
with message-id 
and subject line Bug#1004997: Removed package(s) from unstable
has caused the Debian Bug report #973816,
regarding qemu-sbuild-utils
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.)


-- 
973816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qemu-sbuild-utils
Version: 0.1
Severity: serious
X-Debbugs-CC: jo...@debian.org

The sbuild maintainers raised the valid point that it might be better to
incorporate large parts of this software in src:sbuild, in which case
this package should not enter bullseye.

So until this question is resolved, an RC bug is filed so that this
package does not migrate.
--- End Message ---
--- Begin Message ---
Version: 0.2.1+rm

Dear submitter,

as the package qemu-sbuild-utils has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1004997

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: reassign 1005172 to wnpp, tagging 1005175, tagging 1000980, tagging 1005174

[Debian Bug Tracking System]

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

> reassign 1005172 wnpp
Bug #1005172 [snipe-it] ITP:snipe-it - Open Source Asset Management System
Warning: Unknown package 'snipe-it'
Bug reassigned from package 'snipe-it' to 'wnpp'.
Ignoring request to alter found versions of bug #1005172 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1005172 to the same values 
previously set
> tags 1005175 + sid bookworm
Bug #1005175 [libtest-harness-perl] libtest-harness-perl: uninstallable, older 
than Perl 5.34 bundled version
Added tag(s) bookworm and sid.
> tags 1000980 + sid bookworm
Bug #1000980 [src:kubernetes] kubernetes: Please upgrade to golang-1.17
Added tag(s) sid and bookworm.
> tags 1005174 + sid bookworm
Bug #1005174 {Done: gregor herrmann } [libio-compress-perl] 
libio-compress-perl: uninstallable, older than 5.34 bundled version
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

Bug#997451: marked as done (tracker: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Wed, 09 Feb 2022 13:36:29 +
with message-id 
and subject line Bug#997451: fixed in tracker 3.1.2-4
has caused the Debian Bug report #997451,
regarding tracker: FTBFS: dpkg-gensymbols: error: some new symbols appeared in 
the symbols file: see diff output below
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.)


-- 
997451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tracker
Version: 3.1.2-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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_makeshlibs -V -X/usr/lib/x86_64-linux-gnu/tracker-3.0/ -- -c4
> dpkg-gensymbols: error: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: warning: debian/libtracker-sparql-3.0-0/DEBIAN/symbols 
> doesn't match completely debian/libtracker-sparql-3.0-0.symbols
> --- debian/libtracker-sparql-3.0-0.symbols 
> (libtracker-sparql-3.0-0_3.1.2-3_amd64)
> +++ dpkg-gensymbols_TaVYf 2021-10-23 07:20:13.656941270 +
> @@ -7,6 +7,21 @@
>   tracker_batch_execute_finish@Base 3.1.1
>   tracker_batch_get_connection@Base 3.1.1
>   tracker_batch_get_type@Base 3.1.1
> + tracker_bus_connection_construct@Base 3.1.2-3
> + tracker_bus_connection_construct_finish@Base 3.1.2-3
> + tracker_bus_connection_get_bus_name@Base 3.1.2-3
> + tracker_bus_connection_get_bus_object_path@Base 3.1.2-3
> + tracker_bus_connection_get_type@Base 3.1.2-3
> + tracker_bus_connection_new@Base 3.1.2-3
> + tracker_bus_connection_new_finish@Base 3.1.2-3
> + tracker_bus_connection_perform_query_call@Base 3.1.2-3
> + tracker_bus_connection_perform_query_call_finish@Base 3.1.2-3
> + tracker_bus_fd_cursor_construct@Base 3.1.2-3
> + tracker_bus_fd_cursor_get_type@Base 3.1.2-3
> + tracker_bus_fd_cursor_new@Base 3.1.2-3
> + tracker_bus_statement_construct@Base 3.1.2-3
> + tracker_bus_statement_get_type@Base 3.1.2-3
> + tracker_bus_statement_new@Base 3.1.2-3
>   tracker_check_version@Base 3.1.1
>   tracker_endpoint_dbus_get_type@Base 3.1.1
>   tracker_endpoint_dbus_new@Base 3.1.1
> @@ -31,6 +46,15 @@
>   tracker_notifier_get_type@Base 1.12.0
>   tracker_notifier_signal_subscribe@Base 3.1.1
>   tracker_notifier_signal_unsubscribe@Base 3.1.1
> + tracker_remote_connection_construct@Base 3.1.2-3
> + tracker_remote_connection_get_type@Base 3.1.2-3
> + tracker_remote_connection_new@Base 3.1.2-3
> + tracker_remote_json_cursor_construct@Base 3.1.2-3
> + tracker_remote_json_cursor_get_type@Base 3.1.2-3
> + tracker_remote_json_cursor_new@Base 3.1.2-3
> + tracker_remote_xml_cursor_construct@Base 3.1.2-3
> + tracker_remote_xml_cursor_get_type@Base 3.1.2-3
> + tracker_remote_xml_cursor_new@Base 3.1.2-3
>   tracker_resource_add_boolean@Base 1.9.1
>   tracker_resource_add_double@Base 1.9.1
>   tracker_resource_add_gvalue@Base 1.9.1
> dh_makeshlibs: error: failing due to earlier errors
> make[1]: *** [debian/rules:28: override_dh_makeshlibs] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/tracker_3.1.2-3_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 ---
Source: tracker
Source-Version: 3.1.2-4
Done: Jeremy Bicha 

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated tracker 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, 

Processed: Bug#997451 marked as pending in tracker

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997451 [src:tracker] tracker: FTBFS: dpkg-gensymbols: error: some new 
symbols appeared in the symbols file: see diff output below
Added tag(s) pending.

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

Bug#997451: marked as pending in tracker

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #997451 in tracker 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/tracker/-/commit/2cdb8bb4794d61f78a6c36894834a00111298692


debian/libtracker-sparql-3.0-0.symbols: Add new symbols

Closes: #997451


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997451

Bug#1002143: marked as done (xserver-xorg-video-qxl: FTBFS: xf86Opt.h:44:10: error: two or more data types in declaration specifiers)

[Debian Bug Tracking System]

Your message dated Wed, 09 Feb 2022 12:40:05 +
with message-id 
and subject line Bug#1002143: fixed in xserver-xorg-video-qxl 
0.1.5+git20200331-2
has caused the Debian Bug report #1002143,
regarding xserver-xorg-video-qxl: FTBFS: xf86Opt.h:44:10: error: two or more 
data types in declaration specifiers
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.)


-- 
1002143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xserver-xorg-video-qxl
Version: 0.1.5+git20200331-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I../../src -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -DXSPICE 
> -I/usr/include/spice-1 -fvisibility=hidden -I/usr/include/xorg 
> -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/freetype2 
> -I/usr/include/libpng16 -I/usr/include/X11/dri  -Wall -Wpointer-arith 
> -Wmissing-declarations -Wformat=2 -Wstrict-prototypes -Wmissing-prototypes 
> -Wnested-externs -Wbad-function-cast -Wold-style-definition 
> -Wdeclaration-after-statement -Wunused -Wuninitialized -Wshadow 
> -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls -Wlogical-op 
> -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main 
> -Werror=missing-braces -Werror=sequence-point -Werror=return-type 
> -Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address 
> -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing 
> -I/usr/include/libdrm  -I/usr/include/spice-server -I/usr/include/spice-1 -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o spiceqxl_drv_la-spiceqxl_util.lo `test -f 
> 'spiceqxl_util.c' || echo '../../src/'`spiceqxl_util.c
> In file included from /usr/include/xf86drmMode.h:45,
>  from ../../src/qxl_drmmode.h:33,
>  from ../../src/qxl_drmmode.c:36:
> /usr/include/xorg/xf86Opt.h:44:10: error: two or more data types in 
> declaration specifiers
>44 | Bool bool;
>   |  ^~~~
> In file included from /usr/include/xorg/xf86str.h:43,
>  from ../../src/qxl_drmmode.h:34,
>  from ../../src/qxl_drmmode.c:36:
> /usr/include/xorg/xf86Opt.h:44:14: warning: declaration does not declare 
> anything
>44 | Bool bool;
>   |  ^
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -DXSPICE -I/usr/include/spice-1 -fvisibility=hidden 
> -I/usr/include/xorg -I/usr/include/pixman-1 -I/usr/include/libdrm 
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/X11/dri -Wall 
> -Wpointer-arith -Wmissing-declarations -Wformat=2 -Wstrict-prototypes 
> -Wmissing-prototypes -Wnested-externs -Wbad-function-cast 
> -Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized 
> -Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls 
> -Wlogical-op -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main 
> -Werror=missing-braces -Werror=sequence-point -Werror=return-type 
> -Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address 
> -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing 
> -I/usr/include/libdrm -I/usr/include/spice-server -I/usr/include/spice-1 -g 
> -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c ../../src/spiceqxl_util.c  -fPIC -DPIC -o 
> .libs/spiceqxl_drv_la-spiceqxl_util.o
> make[5]: *** [Makefile:798: qxl_drmmode.lo] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/xserver-xorg-video-qxl_0.1.5+git20200331-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 ---
Source: xserver-xorg-video-qxl
Source-Version: 0.1.5+git20200331-2
Done: Timo Aaltonen 

We believe that the bug you reported is fixed in the lates

Bug#997738: marked as done (ipywidgets: FTBFS: src/ui/vdom.ts(92,23): error TS2304: Cannot find name 'MouseWheelEvent'.)

[Debian Bug Tracking System]

Your message dated Wed, 09 Feb 2022 10:03:53 +
with message-id 
and subject line Bug#997738: fixed in ipywidgets 6.0.0-9
has caused the Debian Bug report #997738,
regarding ipywidgets: FTBFS: src/ui/vdom.ts(92,23): error TS2304: Cannot find 
name 'MouseWheelEvent'.
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.)


-- 
997738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ipywidgets
Version: 6.0.0-8
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 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_build
>   pybuild --build --test-pytest -i python{version} -p 3.9
> I: pybuild base:232: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/ipywidgets
> copying ipywidgets/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets
> copying ipywidgets/_version.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets
> creating /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_color.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_controller.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/domwidget.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_link.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_selectioncontainer.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_image.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/valuewidget.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_bool.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_layout.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_string.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_core.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_float.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_style.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_button.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_output.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_date.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/interaction.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_selection.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/trait_types.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_int.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> copying ipywidgets/widgets/widget_box.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets
> creating /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets/tests
> copying ipywidgets/widgets/tests/test_link.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets/tests
> copying ipywidgets/widgets/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets/tests
> copying ipywidgets/widgets/tests/test_interaction.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets/tests
> copying ipywidgets/widgets/tests/test_traits.py -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets/widgets/tests
> copying ipywidgets/state.schema.json -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets
> copying ipywidgets/view.schema.json -> 
> /<>/.pybuild/cpython3_3.9/build/ipywidgets
> dh_auto_build --buildsystem nodejs
> Found debian/nodejs/additional_components
> Adding component(s): jupyter-js-widgets
> Adding component(s): jupyter-widgets-schema
> Adding component(s): phosphor
> Adding component(s): scriptjs
> Adding component(s): widgetsnbextension
> No build command found, searching known files
> Found 

Bug#1001343: marked as done (ipywidgets: (autopkgtest) needs update for python3.10: 'Mapping' from 'collections' is removed)

[Debian Bug Tracking System]

Your message dated Wed, 09 Feb 2022 10:03:53 +
with message-id 
and subject line Bug#1001343: fixed in ipywidgets 6.0.0-9
has caused the Debian Bug report #1001343,
regarding ipywidgets: (autopkgtest) needs update for python3.10: 'Mapping' from 
'collections' is removed
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.)


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

Source: ipywidgets
Version: 6.0.0-8
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),

With a recent upload of python3-defaults the autopkgtest of ipywidgets 
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
ipywidgets from testing6.0.0-8
all others from testingfrom testing

I copied some of the output at the bottom of this report. 
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.

Currently this regression is blocking the migration of python3-defaults 
to testing [1].


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/i/ipywidgets/17376872/log.gz

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

from .widgets import *
  File "/usr/lib/python3/dist-packages/ipywidgets/widgets/__init__.py", 
line 20, in 
from .widget_selection import RadioButtons, ToggleButtons, 
Dropdown, Select, SelectionSlider, SelectMultiple
  File 
"/usr/lib/python3/dist-packages/ipywidgets/widgets/widget_selection.py", 
line 9, in 

from collections import Mapping
ImportError: cannot import name 'Mapping' from 'collections' 
(/usr/lib/python3.10/collections/__init__.py)

autopkgtest [21:41:38]: test autodep8-python3



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ipywidgets
Source-Version: 6.0.0-9
Done: Graham Inggs 

We believe that the bug you reported is fixed in the latest version of
ipywidgets, 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.
Graham Inggs  (supplier of updated ipywidgets 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, 09 Feb 2022 09:33:43 +
Source: ipywidgets
Built-For-Profiles: noudeb
Architecture: source
Version: 6.0.0-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Graham Inggs 
Closes: 997738 1001343
Changes:
 ipywidgets (6.0.0-9) unstable; urgency=medium
 .
   * Team upload
   * debian/missing-sources/phosphor/src/ui/vdom.ts: MouseWheelEvent is
 WheelEvent since TypeScript 2.0 (Closes: #997738)
   * debian/patches/python3.10.patch: compatibility with Python 3.10
 (Closes: #1001343)
Checksums-Sha1:
 73d1c925d47e489eb8deafc915e0b06fb1b9be22 2964 ipywidgets_6.0.0-9.dsc
 3de5615c62aee3127d254d07d9cbe3c0476cc5bb 136976 
ipywidgets_6.0.0-9.debian.tar.xz
Checksums-Sha256:
 dcf2e973a0049b8a8253c6ee1815f32d3a63dafe2ab5f27dad00d25fe022ddb5 2964 
ipywidgets_6.0.0-9.dsc
 5f0d5709e22907fdceb4375862dc1e3d715719efac09e0b0ce9ee4c492baba32 136976 
ipywidgets_6.0.0-9.debian.tar.xz
Files:
 d45723ba5b20a12a714a9d1299058a54 2964 python optional ipywidgets_6.0.0-9.dsc
 5e873d48cb4b8eca5888f6489ca37f9f 136976 python optiona

Bug#1005120: marked as done (wpewebkit: Fails to build with gstreamer 1.20)

[Debian Bug Tracking System]

Your message dated Wed, 9 Feb 2022 10:13:52 +0100
with message-id <20220209091352.ga23...@igalia.com>
and subject line 
has caused the Debian Bug report #1005120,
regarding wpewebkit: Fails to build with gstreamer 1.20
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.)


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

wpewebkit fails to build from source, apparently because of the recent
gstreamer 1.20 uploads.

-- Checking for module 'gstreamer-codecparsers-1.0 >= 1.14.0'
--   No package 'gstreamer-codecparsers-1.0' found

That .pc file is provided by libgstreamer-plugins-bad1.0-dev so maybe
you just need to Build-Depend on that.

I get a similar warning when building webkit2gtk 2.34.4-1 but it
doesn't fail the build like it does for wpewebkit

Full build logs at https://launchpad.net/ubuntu/+source/wpewebkit/2.34.4-1build1

Thank you,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
fixed 1005120 gst-plugins-base1.0/1.20.0-2
thanks

I accidentally reopened the bug, sorry for the noise. It should be fine
now.--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 1005120 gst-plugins-base1.0/1.20.0-2
Bug #1005120 [gst-plugins-base1.0] wpewebkit: Fails to build with gstreamer 1.20
Marked as fixed in versions gst-plugins-base1.0/1.20.0-2.
> thanks
Stopping processing here.

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

Bug#1001823: Ping?

[Markus Koschany]

Hello Jens,

thanks for reporting this issue and for your patch! Unfortunately nobody had
time to look at it yet. There might be more issues due to the Python 3 port but
I could apply your patch for a start after some play testing. I try to do this
at the weekend.

Regards,

Markus


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

Bug#1005152: marked as done (pythonmagick: Misbuild when multiple supported python versions and default is newer)

[Debian Bug Tracking System]

Your message dated Wed, 09 Feb 2022 09:05:05 +
with message-id 
and subject line Bug#1005152: fixed in pythonmagick 0.9.19-8
has caused the Debian Bug report #1005152,
regarding pythonmagick: Misbuild when multiple supported python versions and 
default is newer
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.)


-- 
1005152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pythonmagick
Version: 0.9.19-7
Severity: serious
Tags: patch
Justification: misbuilt
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch

Dear maintainers,

Well it's me again ;)  Ubuntu has switched python3.10 to be the default
python, which is *again* causing pythonmagick to misbuild.  The reason is
that the upstream configure script has a --with-python-min-version option,
but not a --with-python-max-version option; so when the version returned by
the bare 'python3' command satisfies the min constraint, that's what the
build uses.

So python3 returns 3.10, which satisfies the >= 3.9 constraint, and both
binary builds try to install to the python3.10 path by mistake (despite the
python3.9 build having used the correct libboost-python).

The attached patch addresses this by explicitly telling configure in its
environment what python command to use for each build.  I've confirmed that
this fixes the build in Ubuntu, so it should also let pythonmagick rebuild
correctly when python3.10 becomes the default in Debian (soon).

You can probably also drop the use of --with-python-min-version, which is
now redundant.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru pythonmagick-0.9.19/debian/rules pythonmagick-0.9.19/debian/rules
--- pythonmagick-0.9.19/debian/rules2022-01-28 05:42:27.0 -0800
+++ pythonmagick-0.9.19/debian/rules2022-02-07 16:11:55.0 -0800
@@ -8,7 +8,8 @@
 export PYBUILD_NAME=pythonmagick
 export PYBUILD_SYSTEM=custom
 export PYBUILD_CLEAN_ARGS=dh_auto_clean $d;
-export PYBUILD_CONFIGURE_ARGS=dh_auto_configure $d -- \
+export PYBUILD_CONFIGURE_ARGS=PYTHON=python{version.major}.{version.minor} \
+   dh_auto_configure $d -- \
--disable-silent-rules --disable-static \
--with-python-min-version={version.major}.{version.minor} \
--with-boost-python=boost_python{version.major}{version.minor}
--- End Message ---
--- Begin Message ---
Source: pythonmagick
Source-Version: 0.9.19-8
Done: Jeroen Ploemen 

We believe that the bug you reported is fixed in the latest version of
pythonmagick, 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.
Jeroen Ploemen  (supplier of updated pythonmagick 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, 09 Feb 2022 07:44:11 +
Source: pythonmagick
Architecture: source
Version: 0.9.19-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Jeroen Ploemen 
Closes: 1005152
Changes:
 pythonmagick (0.9.19-8) unstable; urgency=medium
 .
   * Team upload.
   * Rules: explicitly set the Python version for configure; patch once
 again courtesy of Steve Langasek. (Closes: #1005152)
Checksums-Sha1:
 507c22119ad90bd6e4845e88c18dab51fd2810ee 2321 pythonmagick_0.9.19-8.dsc
 7373e4cfe06e49488d783cfa5836212de9565fb2 21244 
pythonmagick_0.9.19-8.debian.tar.xz
 8a19989480fe430a950e78ccecf3d4abaed4222d 7989 
pythonmagick_0.9.19-8_source.buildinfo
Checksums-Sha256:
 f34b8f75213c6a7052e66d6c4dd192a20eb3c24222754fe0070c45263cfd71bf 2321 
pythonmagick_0.9.19-8.dsc
 d3d130a80ddf4d1d788737b53eb1527e706acef6719128a0c394da713ef9b1aa 21244 
pythonmagick_0.9.19-8.debian.tar.xz
 b3865be6885c55496f40af197117a6062ea2da229b3fa2804c77181d7fe96e59 7989 
pythonmagick_0.9.19-8_source.buildinfo
Files:
 6e2ab83e80b74902e9fcaa05f93d896

Bug#1005141: marked as done (linux-perf: Removes diversions on upgrade breaking it)

[Debian Bug Tracking System]

Your message dated Wed, 09 Feb 2022 09:04:51 +
with message-id 
and subject line Bug#1005141: fixed in linux 5.16.7-2
has caused the Debian Bug report #1005141,
regarding linux-perf: Removes diversions on upgrade breaking it
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.)


-- 
1005141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-perf
Version: 5.16.3-1~exp1
Severity: serious

Hi!

This package has code in its postrm maintscript, which unconditionally
removes the diversion, which breaks as the rename cannot be performed
due to linux-base owning the file, and dpkg-divert refusing to
overwrite it. This is the error shown:

  ,---
  # dpkg -i linux-perf_5.16.7-1_amd64.deb
  (Reading database ... 280997 files and directories currently installed.)
  Preparing to unpack linux-perf_5.16.7-1_amd64.deb ...
  Leaving 'diversion of /usr/bin/perf to /usr/bin/perf.wrapper by linux-perf'
  Leaving 'diversion of /usr/share/bash-completion/completions/perf to 
/usr/share/bash-completion/completions/perf.wrapper by linux-perf'
  Leaving 'diversion of /usr/share/man/man1/perf.1.gz to 
/usr/share/man/man1/perf.wrapper.1.gz by linux-perf'
  Unpacking linux-perf (5.16.7-1) over (5.16.7-1) ...
  Removing 'diversion of /usr/bin/perf to /usr/bin/perf.wrapper by linux-perf'
  dpkg-divert: error: rename involves overwriting '/usr/bin/perf' with
different file '/usr/bin/perf.wrapper', not allowed
  dpkg: warning: old linux-perf package post-removal script subprocess returned 
error exit status 2
  dpkg: trying script from the new package instead ...
  Removing 'diversion of /usr/bin/perf to /usr/bin/perf.wrapper by linux-perf'
  dpkg-divert: error: rename involves overwriting '/usr/bin/perf' with
different file '/usr/bin/perf.wrapper', not allowed
  dpkg: error processing archive linux-perf_5.16.7-1_amd64.deb (--install):
   new linux-perf package post-removal script subprocess returned error exit 
status 2
  Leaving 'diversion of /usr/bin/perf to /usr/bin/perf.wrapper by linux-perf'
  Leaving 'diversion of /usr/share/bash-completion/completions/perf to 
/usr/share/bash-completion/completions/perf.wrapper by linux-perf'
  Leaving 'diversion of /usr/share/man/man1/perf.1.gz to 
/usr/share/man/man1/perf.wrapper.1.gz by linux-perf'
  Removing 'diversion of /usr/bin/perf to /usr/bin/perf.wrapper by linux-perf'
  dpkg-divert: error: rename involves overwriting '/usr/bin/perf' with
different file '/usr/bin/perf.wrapper', not allowed
  dpkg: error while cleaning up:
   new linux-perf package post-removal script subprocess returned error exit 
status 2
  Processing triggers for man-db (2.10.0-2) ...
  [main a8458e04] Commit dpkg db updates
   1 file changed, 2 insertions(+), 1 deletion(-)
  Errors were encountered while processing:
   linux-perf_5.16.7-1_amd64.deb
  `---

The dpkg-divert calls should be protected to run only on the relevant
actions on all maintscripts.

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.16.7-2
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
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.
Salvatore Bonaccorso  (supplier of updated 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, 09 Feb 2022 09:35:55 +0100
Source: linux
Architecture: source
Version: 5.16.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 1005141
Changes:
 linux (5.16.7-2) unstable; urgency=medium
 .
   * linux-perf: Protect invocation of dpkg-divert to run only on relevant
 actions in maintscripts. Thanks to Guillem Jover (Closes: #1005141)
Checksums-Sha1:
 29821782203b32a5a36ed88fa26d8fe7320a4cfb 248954 linux_5.16.7-2.dsc
 a8b87b1cf4684ac5db307bb334192869148d173d 1299916 linux_5.16.7-2.debian.tar.xz
 32a8a83ed7683e5f485f49cfd852f51765cdbaa9 6469 linux_5.16.7-2_source.buildinfo
Checksums-Sha256:
 06b0a60d6cc5074378

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 1005120 gst-plugins-base1.0
Bug #1005120 {Done: Sebastian Dröge } [src:wpewebkit] 
wpewebkit: Fails to build with gstreamer 1.20
Bug reassigned from package 'src:wpewebkit' to 'gst-plugins-base1.0'.
No longer marked as found in versions wpewebkit/2.34.4-1.
No longer marked as fixed in versions gst-plugins-base1.0/1.20.0-2.
> found 1005120 gst-plugins-base1.0/1.20.0-1
Bug #1005120 {Done: Sebastian Dröge } [gst-plugins-base1.0] 
wpewebkit: Fails to build with gstreamer 1.20
Marked as found in versions gst-plugins-base1.0/1.20.0-1 and reopened.
> notfound 1005120 wpewebkit/2.34.4-1
Bug #1005120 [gst-plugins-base1.0] wpewebkit: Fails to build with gstreamer 1.20
Ignoring request to alter found versions of bug #1005120 to the same values 
previously set
> affects 1005120 wpewebkit
Bug #1005120 [gst-plugins-base1.0] wpewebkit: Fails to build with gstreamer 1.20
Added indication that 1005120 affects wpewebkit
> thanks
Stopping processing here.

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

Bug#991036: [Debian-on-mobile-maintainers] Bug#991036: libhandy: Should this package be removed in bookworm?

[Guido Günther]

Hi,
On Wed, Feb 09, 2022 at 06:27:50AM +0200, Adrian Bunk wrote:
> Control: severity -1 serious
> 
> libhandy is about to be removed from bookworm due to this,
> gnome-authenticator and gnome-metronome need to be updated.

Just to confirm: I think removal is fine, this API version is
unmaintained upstream and libhandy-1 and libadwaita are in Debian.
Cheers,
 -- Guido