Bug#1001764: More info

[Graham Inggs]

Hi Dima

On Mon, 20 Dec 2021 at 22:40, Dima Kogan  wrote:
> I installed python3.10, and asked the build system to use it. Instead of
> the error you're reporting, I get a build error: it can't find the numpy
> headers because python3-numpy is built for python3.9. This makes sense.

numpy 1:1.21.4-2 in testing is already built for python3.9 and 3.10
[1].  Search for 'cpython-3' and you should find files like:

/usr/lib/python3/dist-packages/numpy/core/_multiarray_tests.cpython-310-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/numpy/core/_multiarray_tests.cpython-39-x86_64-linux-gnu.so

> What do I need to install to reproduce this bug?

You should be able to reproduce this with all packages from unstable,
or all packages from testing and only packages built from
src:python3-defaults from unstable, e.g. python3, python3-all ,etc.
Follow the links in the unstable and testing columns [2], and note the
'Trigger/Pinned packages' column on the testing page.

Regards
Graham


[1] https://packages.debian.org/bookworm/amd64/python3-numpy/filelist
[2] https://ci.debian.net/packages/m/mrgingham/

Bug#1002061: libjxl-dev: ships files already in libhwy-dev

[Andreas Beckmann]

Package: libjxl-dev
Version: 0.6.1+ds-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

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

  Preparing to unpack .../libjxl-dev_0.6.1+ds-5_amd64.deb ...
  Unpacking libjxl-dev (0.6.1+ds-5) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libjxl-dev_0.6.1+ds-5_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libhwy.a', which is also in 
package libhwy-dev 0.15.0-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libjxl-dev_0.6.1+ds-5_amd64.deb

The following files are already shipped by libhwy-dev:

usr/lib/x86_64-linux-gnu/libhwy.a
usr/lib/x86_64-linux-gnu/libhwy_contrib.a
usr/lib/x86_64-linux-gnu/pkgconfig/libhwy-contrib.pc
usr/lib/x86_64-linux-gnu/pkgconfig/libhwy-test.pc
usr/lib/x86_64-linux-gnu/pkgconfig/libhwy.pc


cheers,

Andreas


libhwy-dev=0.15.0-1_libjxl-dev=0.6.1+ds-5.log.gz
Description: application/gzip

Bug#1002060: liblunar-date-doc: missing Breaks+Replaces: liblunar-date-dev (<< 3)

[Andreas Beckmann]

Package: liblunar-date-doc
Version: 3.0.1-1
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...):

  Preparing to unpack .../liblunar-date-doc_3.0.1-1_all.deb ...
  Unpacking liblunar-date-doc (3.0.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/liblunar-date-doc_3.0.1-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/liblunar-date-dev/changelog.gz', which 
is also in package liblunar-date-dev:amd64 2.4.0-8
  Errors were encountered while processing:
   /var/cache/apt/archives/liblunar-date-doc_3.0.1-1_all.deb


cheers,

Andreas


liblunar-date-dev=2.4.0-8_liblunar-date-doc=3.0.1-1.log.gz
Description: application/gzip

Bug#991610: marked as done (postfix: TLS_LICENSE is not included in /usr/share/doc/postfix/copyright)

[Debian Bug Tracking System]

Your message dated Tue, 21 Dec 2021 05:34:10 +
with message-id 
and subject line Bug#991610: fixed in postfix 3.6.3-1
has caused the Debian Bug report #991610,
regarding postfix: TLS_LICENSE is not included in 
/usr/share/doc/postfix/copyright
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.)


-- 
991610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postfix
Version: 3.5.6-1+b1
Severity: serious

/usr/share/doc/postfix/copyright includes the LICENSE file, but
not TLS_LICENSE (about Postfix/TLS support). I suppose that this
file should be included in some form.

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

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

Versions of packages postfix depends on:
ii  adduser3.118
ii  cpio   2.13+dfsg-4
ii  debconf [debconf-2.0]  1.5.77
ii  dpkg   1.20.9
ii  e2fsprogs  1.46.2-2
ii  libc6  2.31-13
ii  libdb5.3   5.3.28+dfsg1-0.8
ii  libicu67   67.1-7
ii  libnsl21.3.0-2
ii  libsasl2-2 2.1.27+dfsg-2.1
ii  libssl1.1  1.1.1k-1
ii  lsb-base   11.1.0
ii  netbase6.3
ii  ssl-cert   1.1.0+nmu1

Versions of packages postfix recommends:
ii  ca-certificates  20210119
ii  python3  3.9.2-3

Versions of packages postfix suggests:
ii  bsd-mailx [mail-reader]  8.1.2-0.20180807cvs-2
ii  emacs-gtk [mail-reader]  1:27.1+1-3.1
ii  libsasl2-modules 2.1.27+dfsg-2.1
ii  mailutils [mail-reader]  1:3.11.1-5
ii  mutt [mail-reader]   2.0.5-4.1
pn  postfix-cdb  
ii  postfix-doc  3.5.6-1
pn  postfix-ldap 
pn  postfix-lmdb 
pn  postfix-mysql
ii  postfix-pcre 3.5.6-1+b1
pn  postfix-pgsql
pn  postfix-sqlite   
ii  procmail 3.22-26
pn  resolvconf   
pn  ufw  

-- debconf information excluded

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: postfix
Source-Version: 3.6.3-1
Done: Scott Kitterman 

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated postfix package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 21 Dec 2021 00:13:25 -0500
Source: postfix
Architecture: source
Version: 3.6.3-1
Distribution: unstable
Urgency: medium
Maintainer: LaMont Jones 
Changed-By: Scott Kitterman 
Closes: 991610
Changes:
 postfix (3.6.3-1) unstable; urgency=medium
 .
   [Scott Kitterman]
 .
   * Add license information from TLS_LICENSE.  Closes: #991610
   * Additional debian/copyright updates
   * Refresh patches
   * Add Pre-Depends on init-system-helpers (>= 1.54~) due to use of
 --skip-systemd-native flag
   * Update lintian overrides
   * Bump standards-version to 4.6.0 without further change
 .
   [Wietse Venema]
 .
   * 3.6.3
Checksums-Sha1:
 e5f9be2aeb6b2c8de952ed780cabf217654f82f6 2997 postfix_3.6.3-1.dsc
 20b06c0d8858106bc4efec24ba1d19d2ba1b4178 4750833 postfix_3.6.3.orig.tar.gz
 235885d08aad5b4fbf5f964e0d3a04d2c3baed4b 220 postfix_3.6.3.orig.tar.gz.asc
 eb7a269770dd62ae7f894db712a38082351e1e60 204312 postfix_3.6.3-1.debian.tar.xz
 7b8daa22a31de686f0b505165bef365738552da3 

Bug#965656: marked as done (libjpf-java: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Tue, 21 Dec 2021 05:18:46 +
with message-id 
and subject line Bug#965656: fixed in libjpf-java 1.5.1+dfsg-5
has caused the Debian Bug report #965656,
regarding libjpf-java: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


-- 
965656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965656
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libjpf-java
Version: 1.5.1+dfsg-4
Severity: normal
Usertags: compat-5-6-removal

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: libjpf-java
Source-Version: 1.5.1+dfsg-5
Done: Bas Couwenberg 

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

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

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated libjpf-java package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 21 Dec 2021 05:55:23 +0100
Source: libjpf-java
Architecture: source
Version: 1.5.1+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Bas Couwenberg 
Closes: 965656
Changes:
 libjpf-java (1.5.1+dfsg-5) unstable; urgency=medium
 .
   * Team upload.
 .
   [ gregor herrmann ]
   * Remove myself from Uploaders.
 .
   [ Bas Couwenberg ]
   * Add gbp.conf to use pristine-tar & --source-only-changes by default.
   * Update Vcs-* URLs for Salsa.
   * Use Files-Excluded instead of repack.sh.
   * Bump debhelper compat to 13.
 (closes: #965656)
   * Change priority to optional.
   * Add doc-base registration.
   * Update lintian overrides.
   * Mark patches as Forwarded: not-needed.
   * Bump Standards-Version to 4.6.0, changes:
 - Vcs-* fields
 - Priority
Checksums-Sha1:
 e4563b4fbd5d51ad8692345607da87c478b1a064 2140 libjpf-java_1.5.1+dfsg-5.dsc
 9c0884b60ebd4dd3d2446eb4c6a70f913e91cb02 5216 
libjpf-java_1.5.1+dfsg-5.debian.tar.xz
 6972438c8a87a20c8af17ec6257d16cddffdb44e 11848 
libjpf-java_1.5.1+dfsg-5_amd64.buildinfo
Checksums-Sha256:
 94c786aeabcc6fe74b606b452afc8b29bd0a0009f4ec8ec01d85c8130498af2f 2140 
libjpf-java_1.5.1+dfsg-5.dsc
 c0b9a5b1ce48eb391dcfd1c0a65d24d8f03311a82611196de661be698fe7f029 5216 
libjpf-java_1.5.1+dfsg-5.debian.tar.xz
 8ec3ec34a78344de888533c6dd91b449be3d9bf9a38436be0ca6a5a983d9e60b 11848 
libjpf-java_1.5.1+dfsg-5_amd64.buildinfo
Files:
 d92c47499bc1b1fdd9543e700f239688 2140 java optional 
libjpf-java_1.5.1+dfsg-5.dsc
 fea108fe6679af9cdf75ba0c4736895c 5216 java optional 
libjpf-java_1.5.1+dfsg-5.debian.tar.xz
 3e3931e9cc3da328a579b9c322da9929 11848 java optional 
libjpf-java_1.5.1+dfsg-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmHBX/8ACgkQZ1DxCuiN
SvHwxA//cuahJ9dL8U1eTKYXeUGff7pwKL5fQw1HL34yD7g/Ny39ZXswIQB3TAwr
OtA1OmxvJtAwynXwIO4/4n99aw49ASvaQravf8EZvSmg/QWfVT4IgQE59e8xtIGu
n3JIbpgoypgJvrtTo1AinAs2SSt2DnN3GMhEX9kWeCLiu+ZRLaBgSDRp1QxDHgEP
DGBjATtDmW8VKc6z5oB8lzePZMWpl+rSHItZNWtHDPP48B+x1yP0ntjyIHHW/I2o

Bug#1001934: marked as done (tkrzw-python: b-d on libpython3-all-dev, but not built for all supported Python3 versions)

[Debian Bug Tracking System]

Your message dated Tue, 21 Dec 2021 04:33:27 +
with message-id 
and subject line Bug#1001934: fixed in tkrzw-python 0.1.28-2
has caused the Debian Bug report #1001934,
regarding tkrzw-python: b-d on libpython3-all-dev, but not built for all 
supported Python3 versions
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.)


-- 
1001934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tkrzw-python
Version: 0.1.28-1
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10 python3-all-dev

Hi Maintainer

This package build-depends on libpython3-all-dev, but does not build
extensions/libraries for all supported python3 versions.  This is seen
on the transition tracker for adding python3.10 support [1] and
creates false positives.

Please either replace the b-d libpython3-all-dev with libpython3-dev,
or build for all supported Python3 versions.  With the former solution
yet get later exposure to a new python3 version, with the latter
solution you get early exposure.

Regards
Graham


[1] https://release.debian.org/transitions/html/python3.10-add.html
--- End Message ---
--- Begin Message ---
Source: tkrzw-python
Source-Version: 0.1.28-2
Done: Boyuan Yang 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Dec 2021 23:15:20 -0500
Source: tkrzw-python
Architecture: source
Version: 0.1.28-2
Distribution: unstable
Urgency: high
Maintainer: Debian Python Team 
Changed-By: Boyuan Yang 
Closes: 1001934
Changes:
 tkrzw-python (0.1.28-2) unstable; urgency=high
 .
   * debian/control:
 + Build-depends on libpython3-dev instead of libpython3-all-dev.
   (Closes: #1001934).
Checksums-Sha1:
 58efb096be0a23ba53e6a0478e0ee5964be24f31 2117 tkrzw-python_0.1.28-2.dsc
 3f368b11c5d0142f838024f267c60bb1f958db77 48542 tkrzw-python_0.1.28.orig.tar.gz
 028fd603444a0d461162c43b8ee55e7e02a062a0 2036 
tkrzw-python_0.1.28-2.debian.tar.xz
 108132e1453e0323515ad5b30a4edc800255524a 7018 
tkrzw-python_0.1.28-2_amd64.buildinfo
Checksums-Sha256:
 68ee20b86b1e81410d463de357aff4529d488710888e1392bfd6db0606db7f5c 2117 
tkrzw-python_0.1.28-2.dsc
 64358e03a2f6ebb8069dbc5143bd1fb3825c94c4289abd3c279137683aa3cd79 48542 
tkrzw-python_0.1.28.orig.tar.gz
 32e6b6a01c60cb29bbed413057a5eada5bbf71c98b4bb27342066add60e405c2 2036 
tkrzw-python_0.1.28-2.debian.tar.xz
 964369120ee5f98937264fac1f76b03eb209acda4e39c8701b74c6d3da5f0121 7018 
tkrzw-python_0.1.28-2_amd64.buildinfo
Files:
 37f14e7844ae7a45d2b4b4d506954341 2117 python optional tkrzw-python_0.1.28-2.dsc
 b5447de0b53d02a281234bbafab00dd1 48542 python optional 
tkrzw-python_0.1.28.orig.tar.gz
 b81486db06de701cb885fae679df9c9f 2036 python optional 
tkrzw-python_0.1.28-2.debian.tar.xz
 5a0b74ffe4882fc4a2eb616bf2518333 7018 python optional 
tkrzw-python_0.1.28-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmHBVWYACgkQwpPntGGC
Ws7Ivw//bE6U0NVJ/sjEuMvWtNJv4Oq3U8ibdxVychb3UpSSKfYiNp9lJxKJYFG2
puhM2VLjQB50AkkB5yyprKbjWRFF7/aFMtxOgo+RLM9pXGP0UFMinaqvb3+wZ5nf
Hg7mW6aOUyrBgIrq1OgUa03btHrOhMh3AP7/lCDgviYrXgrxLWepwJTBrqqs/9AT
PEulKye9YgBXi+9YdpfRhCDqgMDIxUoAVr1vNh0OcKFIy1Cz9MNi5U1YGk5Xc6ic
5Cz1MugjaBIhwitdQhp3KJIKBc+EOFmNKZSprgqGrTe7uqtPT4IlORyIdY3Qnvh8
GbOFJQmln7p6pdxbnKaQ0pIrTr1YDVguSVGQCFTKDgdvAyo5DEbLqsyQ8wWxn+l6
0SRf3do8wga7GUzPutyhjKJX/qMTycpqezR/chWIENB6P3JfPrGBBv3/9wK7CdPj
6im0jQ6KJ86aOigcvFQtZlBjDcCNm2AZhIFyBdbkKdX+VNsMSiazaXWaFaRd7Kq+
ym7jLub1XRfHVOv2/gMmN/JZ59JzZgKxikbhafq5adx5plKCe3KbePlMP6fukoUF
uu1Qnj9ZPoAV40NpX5y3/BYbO5DlFUCPc/ximHPqddyqlP5b5dv4gLSPpXyIx0Ic
tL8faR1iIiCJmnkqQIBaw5k8GCXAMot04/8K1ZOzsN/XlC8iDxg=
=zCue
-END PGP SIGNATURE End Message ---

Processed: Adjust bug fix version

[Debian Bug Tracking System]

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

> notfixed 1001728 3.8.1-3
Bug #1001728 {Done: Boyuan Yang } [src:python-aiohttp] 
python-aiohttp breaks dask autopkgtest: 'async_timeout' has no attribute 
'Timeout'
No longer marked as fixed in versions 3.8.1-3.
> found 1001728 3.8.1-3
Bug #1001728 {Done: Boyuan Yang } [src:python-aiohttp] 
python-aiohttp breaks dask autopkgtest: 'async_timeout' has no attribute 
'Timeout'
Did not alter found versions and reopened.
> fixed 1001728 3.8.1-4
Bug #1001728 [src:python-aiohttp] python-aiohttp breaks dask autopkgtest: 
'async_timeout' has no attribute 'Timeout'
Marked as fixed in versions python-aiohttp/3.8.1-4.
> close 1001728 3.8.1-4
Bug #1001728 [src:python-aiohttp] python-aiohttp breaks dask autopkgtest: 
'async_timeout' has no attribute 'Timeout'
Ignoring request to alter fixed versions of bug #1001728 to the same values 
previously set
Bug #1001728 [src:python-aiohttp] python-aiohttp breaks dask autopkgtest: 
'async_timeout' has no attribute 'Timeout'
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1001728: marked as done (python-aiohttp breaks dask autopkgtest: 'async_timeout' has no attribute 'Timeout')

[Debian Bug Tracking System]

Your message dated Mon, 20 Dec 2021 22:56:13 -0500
with message-id <3898ebb1e5caab9c381beb8309115aeffaade0f6.ca...@debian.org>
and subject line Re: python-aiohttp breaks dask autopkgtest: 'async_timeout' 
has no attribute 'Timeout'
has caused the Debian Bug report #1001728,
regarding python-aiohttp breaks dask autopkgtest: 'async_timeout' has no 
attribute 'Timeout'
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.)


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

Source: python-aiohttp
Control: found -1 python-aiohttp/3.8.1-3
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks

Dear maintainer(s),

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


   passfail
python-aiohttp from testing3.8.1-3
dask   from testing2021.09.1+dfsg-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. To me it looks 
like this is all python-aiohttp code path, so I *suspect* the issue is 
with python-aiohttp itself.


Currently this regression is blocking the migration of python-aiohttp 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=python-aiohttp

https://ci.debian.net/data/autopkgtest/testing/amd64/d/dask/17553992/log.gz

Testing with python3.9:
= test session starts 
==
platform linux -- Python 3.9.9, pytest-6.2.5, py-1.10.0, pluggy-0.13.0 
-- /usr/bin/python3.9

cachedir: .pytest_cache
rootdir: /tmp/autopkgtest-lxc.eom7aakg/downtmp/autopkgtest_tmp
collecting ... collected 9095 items / 1 error / 3 deselected / 21 
skipped / 9070 selected


 ERRORS 

__ ERROR collecting bytes/tests/test_http.py 
___

/usr/lib/python3/dist-packages/dask/bytes/tests/test_http.py:18: in 
aiohttp = pytest.importorskip("aiohttp")
/usr/lib/python3/dist-packages/aiohttp/__init__.py:6: in 
from .client import (
/usr/lib/python3/dist-packages/aiohttp/client.py:36: in 
from . import hdrs, http, payload
/usr/lib/python3/dist-packages/aiohttp/http.py:7: in 
from .http_parser import (
/usr/lib/python3/dist-packages/aiohttp/http_parser.py:29: in 
from .helpers import NO_EXTENSIONS, BaseTimerContext
/usr/lib/python3/dist-packages/aiohttp/helpers.py:732: in 
def ceil_timeout(delay: Optional[float]) -> async_timeout.Timeout:
E   AttributeError: module 'async_timeout' has no attribute 'Timeout'


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 3.8.1-3

I believe this is solved with the most recent upload.

Thanks,
Boyuan

On Tue, 14 Dec 2021 21:36:00 +0100 Paul Gevers  wrote:
> Source: python-aiohttp
> Control: found -1 python-aiohttp/3.8.1-3
> Severity: serious
> Tags: sid bookworm
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: breaks
> 
> Dear maintainer(s),
> 
> With a recent upload of python-aiohttp the autopkgtest of dask fails in 
> testing when that autopkgtest is run with the binary packages of 
> python-aiohttp from unstable. It passes when run with only packages from 
> testing. In tabular form:
> 
> pass    fail
> python-aiohttp from testing    3.8.1-3
> dask   from testing    2021.09.1+dfsg-1
> all others from testing    from testing
> 
> I copied some of the output at the bottom of this report. To me it looks 
> like this is all python-aiohttp code path, so I *suspect* the issue is 
> with python-aiohttp itself.
> 
> Currently this regression is blocking the migration of python-aiohttp 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=python-aiohttp
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/d/dask/17553992/log.gz
> 
> Testing with python3.9:
> 

Bug#978441: marked as done (singularity-container: FTBFS: cannot find package "github.com/kr/pty")

[Debian Bug Tracking System]

Your message dated Tue, 21 Dec 2021 03:03:55 +
with message-id 
and subject line Bug#978441: fixed in singularity-container 3.5.2+ds2-1
has caused the Debian Bug report #978441,
regarding singularity-container: FTBFS: cannot find package "github.com/kr/pty"
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.)


-- 
978441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: singularity-container
Version: 3.5.2+ds1
Severity: serious
Justification: FTBFS

Hi,

While trying to update the golang-github-gin-gonic-gin-dev package, ratt
picked up 35 packages, and yours triggers 1 of the 3 resulting failures.
Trying to build it in a pristine unstable chroot led to the same results:

cd 
/build/singularity-container-3.5.2+ds1/_build/src/github.com/sylabs/singularity/internal/pkg/buildcfg
 && 
/build/singularity-container-3.5.2+ds1/_build/src/github.com/sylabs/singularity/scripts/go-generate
config_gen.go
command-line-arguments
 GO singularity
[+] GO_TAGS "containers_image_openpgp sylog imgbuild_engine oci_engine 
singularity_engine fakeroot_engine apparmor selinux seccomp"
/usr/bin/go build -mod=vendor -buildmode=default -tags 
"containers_image_openpgp sylog imgbuild_engine oci_engine singularity_engine 
fakeroot_engine apparmor selinux seccomp" -ldflags="-B 0x`head -c20 
/dev/urandom|od -An -tx1|tr -d ' \n'`"   \
-o ./singularity 
/build/singularity-container-3.5.2+ds1/_build/src/github.com/sylabs/singularity/cmd/singularity
../internal/app/singularity/oci_attach_linux.go:20:2: cannot find package 
"github.com/kr/pty" in any of:

/build/singularity-container-3.5.2+ds1/_build/src/github.com/sylabs/singularity/vendor/github.com/kr/pty
 (vendor tree)
/usr/lib/go-1.15/src/github.com/kr/pty (from $GOROOT)
/build/singularity-container-3.5.2+ds1/_build/src/github.com/kr/pty 
(from $GOPATH)
make[2]: *** [Makefile:162: singularity] Error 1
make[2]: Leaving directory 
'/build/singularity-container-3.5.2+ds1/_build/src/github.com/sylabs/singularity/builddir'
make[1]: *** [debian/rules:54: override_dh_auto_build] Error 2


This is trivially reproducible with:

sudo cowbuilder --build singularity-container_3.5.2+ds1-1.dsc


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/
--- End Message ---
--- Begin Message ---
Source: singularity-container
Source-Version: 3.5.2+ds2-1
Done: Benda Xu 

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

Debian distribution maintenance software
pp.
Benda Xu  (supplier of updated singularity-container package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Dec 2021 21:03:39 +0800
Source: singularity-container
Architecture: source
Version: 3.5.2+ds2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HPC Team 
Changed-By: Benda Xu 
Closes: 964779 978441
Changes:
 singularity-container (3.5.2+ds2-1) unstable; urgency=medium
 .
   * Repack the source tarball to remove vendored containers/image.
 * Fix FTBFS by backporting upstream patches. (Closes: #964779)
   * Append myself to the Uploaders.
   * Add dependency on golang-github-kr-pty-dev. (Closes: #978441)
   * Drop source-contains-empty-directory lintian tag.
Checksums-Sha1:
 7eba54b985c369630f42d7510647dcf8c297d1a4 3643 
singularity-container_3.5.2+ds2-1.dsc
 bbd6246413de64b2b8a5315122f0775374e5027f 2128832 
singularity-container_3.5.2+ds2.orig.tar.xz
 6025f822066607d6d3d5cadc8c01859852b2d53f 18236 
singularity-container_3.5.2+ds2-1.debian.tar.xz
 45f497e24ab15839be973a355820ad9e71801275 24608 
singularity-container_3.5.2+ds2-1_source.buildinfo
Checksums-Sha256:
 a785beed16d796ad29f7906cd2b07f7fa1c6151a150ecea29c2cd5f00d6ac69e 3643 
singularity-container_3.5.2+ds2-1.dsc
 4594d22ecf19609e673c90e5613db8dca38467826e79e92283b4ae3fffc170c7 2128832 
singularity-container_3.5.2+ds2.orig.tar.xz
 0dea74baca4207ed3cf5a952b8fb3391011420643dbd2ef35f92ca6b15106dbc 

Bug#966993: marked as done (singularity-container: FTBFS)

[Debian Bug Tracking System]

Your message dated Tue, 21 Dec 2021 03:03:55 +
with message-id 
and subject line Bug#964779: fixed in singularity-container 3.5.2+ds2-1
has caused the Debian Bug report #964779,
regarding singularity-container: FTBFS
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.)


-- 
964779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: singularity-container
Version: 3.5.2+ds1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory 
> '/<>/_build/src/github.com/sylabs/singularity/builddir'
>  GEN 
> /<>/_build/src/github.com/sylabs/singularity/scripts/go-generate
> /usr/bin/go run -mod=vendor 
> /<>/_build/src/github.com/sylabs/singularity/scripts/expand-env.go
>  < 
> /<>/_build/src/github.com/sylabs/singularity/scripts/go-generate.in
>  > 
> /<>/_build/src/github.com/sylabs/singularity/scripts/go-generate
> command-line-arguments
> chmod +x 
> /<>/_build/src/github.com/sylabs/singularity/scripts/go-generate
> rm -f 
> /<>/_build/src/github.com/sylabs/singularity/internal/pkg/buildcfg/config.go
> cd 
> /<>/_build/src/github.com/sylabs/singularity/internal/pkg/buildcfg
>  && 
> /<>/_build/src/github.com/sylabs/singularity/scripts/go-generate
> config_gen.go
> command-line-arguments
>  GO singularity
> [+] GO_TAGS "containers_image_openpgp sylog imgbuild_engine oci_engine 
> singularity_engine fakeroot_engine apparmor selinux seccomp"
> /usr/bin/go build -mod=vendor -buildmode=default -tags 
> "containers_image_openpgp sylog imgbuild_engine oci_engine singularity_engine 
> fakeroot_engine apparmor selinux seccomp" -ldflags="-B 0x`head -c20 
> /dev/urandom|od -An -tx1|tr -d ' \n'`"   \
>   -o ./singularity 
> /<>/_build/src/github.com/sylabs/singularity/cmd/singularity
> github.com/sylabs/singularity/vendor/golang.org/x/sys/internal/unsafeheader
> github.com/sylabs/singularity/vendor/github.com/go-log/log
> runtime/cgo
> github.com/sylabs/singularity/docs
> github.com/sylabs/singularity/vendor/github.com/hashicorp/errwrap
> github.com/sylabs/singularity/vendor/github.com/opencontainers/go-digest
> github.com/sylabs/singularity/vendor/github.com/opencontainers/image-spec/specs-go
> github.com/sylabs/singularity/vendor/github.com/opencontainers/runtime-spec/specs-go
> github.com/sylabs/singularity/vendor/github.com/blang/semver
> github.com/sylabs/singularity/vendor/github.com/opencontainers/runtime-tools/generate/seccomp
> github.com/sylabs/singularity/vendor/github.com/containers/image/docker/reference
> github.com/sylabs/singularity/vendor/github.com/opencontainers/image-spec/specs-go/v1
> github.com/sylabs/singularity/vendor/github.com/hashicorp/go-multierror
> github.com/sylabs/singularity/vendor/github.com/containers/image/types
> github.com/sylabs/singularity/vendor/github.com/opencontainers/runtime-tools/filepath
> github.com/sylabs/singularity/vendor/github.com/opencontainers/runtime-tools/error
> github.com/sylabs/singularity/vendor/github.com/pkg/errors
> github.com/sylabs/singularity/vendor/golang.org/x/sys/unix
> github.com/sylabs/singularity/vendor/github.com/opencontainers/runtime-tools/specerror
> github.com/sylabs/singularity/vendor/github.com/opencontainers/selinux/pkg/pwalk
> github.com/sylabs/singularity/vendor/github.com/syndtr/gocapability/capability
> github.com/sylabs/singularity/vendor/github.com/xeipuuv/gojsonpointer
> github.com/sylabs/singularity/vendor/github.com/xeipuuv/gojsonreference
> github.com/sylabs/singularity/vendor/golang.org/x/sync/errgroup
> github.com/sylabs/singularity/vendor/github.com/kr/pty
> github.com/sylabs/singularity/vendor/github.com/apex/log
> github.com/sylabs/singularity/vendor/google.golang.org/grpc/codes
> github.com/sylabs/singularity/internal/pkg/sylog
> github.com/sylabs/singularity/vendor/github.com/golang/protobuf/proto
> github.com/sylabs/singularity/vendor/google.golang.org/grpc/grpclog
> github.com/sylabs/singularity/vendor/google.golang.org/grpc/connectivity
> github.com/sylabs/singularity/vendor/google.golang.org/grpc/internal
> github.com/sylabs/singularity/vendor/golang.org/x/sync/semaphore
> os/user
> net
> github.com/sylabs/singularity/vendor/github.com/opencontainers/selinux/go-selinux
> github.com/sylabs/singularity/vendor/github.com/sirupsen/logrus
> github.com/sylabs/singularity/vendor/github.com/containerd/containerd/log
> 

Bug#964779: marked as done (singularity-container: FTBFS against golang-github-vbauerster-mpb-dev 5.0.3-2 (experimental))

[Debian Bug Tracking System]

Your message dated Tue, 21 Dec 2021 03:03:55 +
with message-id 
and subject line Bug#964779: fixed in singularity-container 3.5.2+ds2-1
has caused the Debian Bug report #964779,
regarding singularity-container: FTBFS against golang-github-vbauerster-mpb-dev 
5.0.3-2 (experimental)
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.)


-- 
964779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: singularity-container
Severity: normal

I'm pondering to upload the version of package
golang-github-vbauerster-mpb-dev currently in experimental to unstable
and did a test rebuild of all dependent packages.

Turns out that singularity-container fails with this error:

# github.com/sylabs/singularity/vendor/github.com/containers/image/copy
../vendor/github.com/containers/image/copy/copy.go:580:71: undefined: 
mpb.WithContext
../vendor/github.com/containers/image/copy/copy.go:605:4: undefined: 
mpb.BarClearOnComplete
../vendor/github.com/containers/image/copy/copy.go:607:15: cannot use 
"github.com/sylabs/singularity/vendor/github.com/vbauerster/mpb/decor".Name(prefix)
 (type 
"github.com/sylabs/singularity/vendor/github.com/vbauerster/mpb/decor".Decorator)
 as type "github.com/vbauerster/mpb/decor".Decorator in argument to 
mpb.PrependDecorators:

"github.com/sylabs/singularity/vendor/github.com/vbauerster/mpb/decor".Decorator
 does not implement "github.com/vbauerster/mpb/decor".Decorator (wrong type for 
Decor method)
have 
Decor(*"github.com/sylabs/singularity/vendor/github.com/vbauerster/mpb/decor".Statistics)
 string
want Decor(*"github.com/vbauerster/mpb/decor".Statistics) string
../vendor/github.com/containers/image/copy/copy.go:610:21: cannot use 
"github.com/sylabs/singularity/vendor/github.com/vbauerster/mpb/decor".OnComplete("github.com/sylabs/singularity/vendor/github.com/vbauerster/mpb/decor".CountersKibiByte("%.1f
 / %.1f"), " " + onComplete) (type 
"github.com/sylabs/singularity/vendor/github.com/vbauerster/mpb/decor".Decorator)
 as type "github.com/vbauerster/mpb/decor".Decorator in argument to 
mpb.AppendDecorators:

"github.com/sylabs/singularity/vendor/github.com/vbauerster/mpb/decor".Decorator
 does not implement "github.com/vbauerster/mpb/decor".Decorator (wrong type for 
Decor method)
have 
Decor(*"github.com/sylabs/singularity/vendor/github.com/vbauerster/mpb/decor".Statistics)
 string
want Decor(*"github.com/vbauerster/mpb/decor".Statistics) string
../vendor/github.com/containers/image/copy/copy.go:616:4: undefined: 
mpb.BarClearOnComplete
../vendor/github.com/containers/image/copy/copy.go:619:15: cannot use 
"github.com/sylabs/singularity/vendor/github.com/vbauerster/mpb/decor".Name(prefix)
 (type 
"github.com/sylabs/singularity/vendor/github.com/vbauerster/mpb/decor".Decorator)
 as type "github.com/vbauerster/mpb/decor".Decorator in argument to 
mpb.PrependDecorators:

"github.com/sylabs/singularity/vendor/github.com/vbauerster/mpb/decor".Decorator
 does not implement "github.com/vbauerster/mpb/decor".Decorator (wrong type for 
Decor method)
have 
Decor(*"github.com/sylabs/singularity/vendor/github.com/vbauerster/mpb/decor".Statistics)
 string
want Decor(*"github.com/vbauerster/mpb/decor".Statistics) string
../vendor/github.com/containers/image/copy/copy.go:622:21: cannot use 
"github.com/sylabs/singularity/vendor/github.com/vbauerster/mpb/decor".OnComplete("github.com/sylabs/singularity/vendor/github.com/vbauerster/mpb/decor".Name(""),
 " " + onComplete) (type 
"github.com/sylabs/singularity/vendor/github.com/vbauerster/mpb/decor".Decorator)
 as type "github.com/vbauerster/mpb/decor".Decorator in argument to 
mpb.AppendDecorators:

"github.com/sylabs/singularity/vendor/github.com/vbauerster/mpb/decor".Decorator
 does not implement "github.com/vbauerster/mpb/decor".Decorator (wrong type for 
Decor method)
have 
Decor(*"github.com/sylabs/singularity/vendor/github.com/vbauerster/mpb/decor".Statistics)
 string
want Decor(*"github.com/vbauerster/mpb/decor".Statistics) string


It seems that singularity-container is vendoring in a copy of the
package golang-github-containers-storage (another package that this
update breaks, but the next upstream version will fix it). This means
that in order to fix this bug, the following option come to mind:

 1. coordinate the version update of new upstream versions of
singularity-container and vbauerster/mbp to unstable

Bug#997426: marked as done (python-aioxmpp: FTBFS: Could not import extension aioxmppspecific (exception: cannot import name 'PyModulelevel' from 'sphinx.domains.python' (/usr/lib/python3/dist-package

[Debian Bug Tracking System]

Your message dated Mon, 20 Dec 2021 23:48:56 +
with message-id 
and subject line Bug#997426: fixed in python-aioxmpp 0.13.1-1
has caused the Debian Bug report #997426,
regarding python-aioxmpp: FTBFS: Could not import extension aioxmppspecific 
(exception: cannot import name 'PyModulelevel' from 'sphinx.domains.python' 
(/usr/lib/python3/dist-packages/sphinx/domains/python.py))
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.)


-- 
997426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-aioxmpp
Version: 0.12.2-1
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[3]: Entering directory '/<>/docs'
> /usr/share/sphinx/scripts/python3/sphinx-build -b html -d 
> sphinx-data/build/doctrees   . sphinx-data/build/html
> Running Sphinx v4.2.0
> 
> Extension error:
> Could not import extension aioxmppspecific (exception: cannot import name 
> 'PyModulelevel' from 'sphinx.domains.python' 
> (/usr/lib/python3/dist-packages/sphinx/domains/python.py))
> make[3]: *** [Makefile:45: html] Error 2


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-aioxmpp_0.12.2-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: python-aioxmpp
Source-Version: 0.13.1-1
Done: Jonas Schäfer 

We believe that the bug you reported is fixed in the latest version of
python-aioxmpp, 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.
Jonas Schäfer  (supplier of updated python-aioxmpp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Dec 2021 19:31:25 +0100
Source: python-aioxmpp
Architecture: source
Version: 0.13.1-1
Distribution: unstable
Urgency: medium
Maintainer: Jonas Schäfer 
Changed-By: Jonas Schäfer 
Closes: 997426
Changes:
 python-aioxmpp (0.13.1-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fixes critical bug which broke message reception with XEP-0359 stanza
   IDs.
 .
 python-aioxmpp (0.13.0-1) unstable; urgency=medium
 .
   * New upstream release.
 - Sphinx compatibility (Closes: #997426)
   * Follow upstream on using pytest for testing
Checksums-Sha1:
 fb6c0d32397ffb95ef58169caa9c4683fc7572c2 2276 python-aioxmpp_0.13.1-1.dsc
 4419f35c847147400d125c118ca530c5256c2d73 808276 
python-aioxmpp_0.13.1.orig.tar.gz
 693a9e06eab58971357bfd61000b5e47d1dc 3244 
python-aioxmpp_0.13.1-1.debian.tar.xz
 1e93765d8c15a764696be1ae484d9ffc8a3cb202 8324 
python-aioxmpp_0.13.1-1_amd64.buildinfo
Checksums-Sha256:
 b20ff89c4f8ce53c82ab92e39a6c5fe2184a10759a4a132ca50377ee5824456f 2276 
python-aioxmpp_0.13.1-1.dsc
 f462d3e2a76c2406694b9adec7ead154bd15274f65c4b57c808f2ae562419341 808276 
python-aioxmpp_0.13.1.orig.tar.gz
 729d4d1581018026a85d2b312df64909bd674b8b768922716ad38fd8238079be 3244 
python-aioxmpp_0.13.1-1.debian.tar.xz
 33e7f0ecdd4b7095bdfb50a19a3981bf6e9fbc214add7d342057cc1807d49e3c 8324 
python-aioxmpp_0.13.1-1_amd64.buildinfo
Files:
 cf0008ebb3b56aa336ba66e4b00bb6df 2276 python optional 
python-aioxmpp_0.13.1-1.dsc
 983ce0dfbc8b4f2f3904fb360e70b00e 808276 python optional 
python-aioxmpp_0.13.1.orig.tar.gz
 381d64e332488814b74c6b29ac552f67 3244 python optional 
python-aioxmpp_0.13.1-1.debian.tar.xz
 21b3094d684770fd5401a9f85faba2d5 8324 python optional 
python-aioxmpp_0.13.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEftHeo0XZoKEY1KdA4+Chwoa5Y+oFAmHBD7MACgkQ4+Chwoa5

Processed: forcibly merging 1000234 1002050, severity of 1000234 is serious

[Debian Bug Tracking System]

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

> forcemerge 1000234 1002050
Bug #1000234 [lintian] lintian: Compare Debhelper prerequisites accurately 
w/r/t multiarch acceptor
Bug #1000610 [lintian] lintian: FP for missing-build-dependency-for-dh-addon 
with Build-Depends: debhelper (>= 11)
Bug #1001552 [lintian] Improper detection of tag satisfaction cases in 
missing-build-dependency-for-dh-addon tag
Bug #1001552 [lintian] Improper detection of tag satisfaction cases in 
missing-build-dependency-for-dh-addon tag
There is no source info for the package 'lintian' at version '2.111.44' with 
architecture ''
Unable to make a source version for version '2.111.44'
Marked as found in versions lintian/2.114.0.
Marked as found in versions lintian/2.114.0.
Marked as found in versions lintian/2.114.0.
Bug #1002050 [lintian] dh-addon dependency test false positive
Severity set to 'important' from 'normal'
There is no source info for the package 'lintian' at version '2.111.44' with 
architecture ''
Unable to make a source version for version '2.111.44'
Marked as found in versions 2.111.44 and lintian/2.111.0.
Bug #1000610 [lintian] lintian: FP for missing-build-dependency-for-dh-addon 
with Build-Depends: debhelper (>= 11)
Merged 1000234 1000610 1001552 1002050
> severity 1000234 serious
Bug #1000234 [lintian] lintian: Compare Debhelper prerequisites accurately 
w/r/t multiarch acceptor
Bug #1000610 [lintian] lintian: FP for missing-build-dependency-for-dh-addon 
with Build-Depends: debhelper (>= 11)
Bug #1001552 [lintian] Improper detection of tag satisfaction cases in 
missing-build-dependency-for-dh-addon tag
Bug #1002050 [lintian] dh-addon dependency test false positive
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: tagging 991610

[Debian Bug Tracking System]

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

> tags 991610 + pending
Bug #991610 [postfix] postfix: TLS_LICENSE is not included in 
/usr/share/doc/postfix/copyright
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: closing 928175

[Debian Bug Tracking System]

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

> # Problem not reported in two years with this version.
> close 928175 3.1.15-0+deb9u1
Bug #928175 [postfix] postfix: [Regression/Stretch] No more delivers mails to 
mailboxes > ca. 500 MB via procmail since upgrade from 3.1.9-0+deb9u2 to 
3.1.12-0+deb9u1
Marked as fixed in versions postfix/3.1.15-0+deb9u1.
Bug #928175 [postfix] postfix: [Regression/Stretch] No more delivers mails to 
mailboxes > ca. 500 MB via procmail since upgrade from 3.1.9-0+deb9u2 to 
3.1.12-0+deb9u1
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Bug#965662 marked as pending in libmp3-info-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #965662 [src:libmp3-info-perl] libmp3-info-perl: Removal of obsolete 
debhelper compat 5 and 6 in bookworm
Added tag(s) pending.

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

Bug#965662: marked as pending in libmp3-info-perl

[Damyan Ivanov]

Control: tag -1 pending

Hello,

Bug #965662 in libmp3-info-perl 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/perl-team/modules/packages/libmp3-info-perl/-/commit/0fd4fa610e25b3860e775b26101ab000e2b1f4b6


bump debhelper compatibility level to 13

Closes: #965662


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/965662

Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14

[Christoph Berg]

Re: Sébastien Villemot
> I’ve uploaded a new cl-esrap. It seems pgloader builds again.

Merci! I'll try to polish the package over the next days.

Christoph

Bug#1001373: marked as done (python-attrs: (autopkgtest) needs update for python3.10: error text changed)

[Debian Bug Tracking System]

Your message dated Mon, 20 Dec 2021 21:33:43 +
with message-id 
and subject line Bug#1001373: fixed in python-attrs 21.2.0-1
has caused the Debian Bug report #1001373,
regarding python-attrs: (autopkgtest) needs update for python3.10: error text 
changed
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.)


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

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

Dear maintainer(s),

We are in the transition of adding python2.10 to the supported Python 
versions [0]. With a recent upload of python3-defaults the autopkgtest 
of python-attrs 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
python-attrs   from testing20.3.0-1
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-attrs/17393460/log.gz


=== FAILURES 
===
 TestAddInit.test_init 
_


self = 

@given(booleans(), booleans())

  def test_init(self, slots, frozen):


tests/test_dunders.py:612: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = , slots 
= False

frozen = False

@given(booleans(), booleans())
def test_init(self, slots, frozen):
"""
If `init` is False, ignore that attribute.
"""
C = make_class(
"C",
{"a": attr.ib(init=False), "b": attr.ib()},
slots=slots,
frozen=frozen,
)
with pytest.raises(TypeError) as e:
C(a=1, b=2)
>   assert (
"__init__() got an unexpected keyword argument 'a'"
== e.value.args[0]
)
E   assert "__init__() g... argument 'a'" == "C.__init__()... 
argument 'a'"

E - C.__init__() got an unexpected keyword argument 'a'
E ? --
E + __init__() got an unexpected keyword argument 'a'

tests/test_dunders.py:625: AssertionError
-- Hypothesis 
--

Falsifying example: test_init(
self=,
slots=False,
frozen=False,
)
___ TestEvolve.test_unknown 



self = 

@given(simple_classes())

  def test_unknown(self, C):


tests/test_funcs.py:539: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = 
C = 

@given(simple_classes())
def test_unknown(self, C):
"""
Wanting to change an unknown attribute raises an
AttrsAttributeNotFoundError.
"""
# No generated class will have a four letter attribute.
with pytest.raises(TypeError) as e:
evolve(C(), =2)
expected = "__init__() got an unexpected keyword argument ''"

  assert (expected,) == e.value.args
E   assert ("__init__() ...ment ''",) == ("HypClass.__...ment 
''",)
E At index 0 diff: "__init__() got an unexpected keyword 
argument ''" != "HypClass.__init__() got an unexpected keyword 
argument ''"

E Use -v to get the full diff

tests/test_funcs.py:548: AssertionError
-- Hypothesis 
--

Falsifying example: test_unknown(
self=,
C=tests.strategies.HypClass,
)


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-attrs
Source-Version: 21.2.0-1
Done: Jochen Sprickerhof 

We believe that the bug you reported is fixed in the latest version of
python-attrs, which is due to be 

Processed: Bug#965656 marked as pending in libjpf-java

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #965656 [src:libjpf-java] libjpf-java: Removal of obsolete debhelper compat 
5 and 6 in bookworm
Added tag(s) pending.

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

Bug#965656: marked as pending in libjpf-java

[Bas Couwenberg]

Control: tag -1 pending

Hello,

Bug #965656 in libjpf-java 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/java-team/libjpf-java/-/commit/588689ced24d62e8b72c0c90d88279d0e2c54712


Bump debhelper compat to 13. (closes: #965656)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/965656

Bug#1002045: marked as done (python3-aioresponses: Failed to import: No module named 'pkg_resources')

[Debian Bug Tracking System]

Your message dated Mon, 20 Dec 2021 21:05:40 +
with message-id 
and subject line Bug#1002045: fixed in python-aioresponses 0.7.2-1.1
has caused the Debian Bug report #1002045,
regarding python3-aioresponses: Failed to import: No module named 
'pkg_resources'
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.)


-- 
1002045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-aioresponses
Version: 0.7.2-1
Severity: grave
X-Debbugs-CC: d...@jones.dk
Tags: sid bookworm

Dear python-aioresponses maintainer,

After installing your package, the package cannot work when using "install
aioresponses":

% sudo apt install python3-aioresponses
% python3
Python 3.9.9 (main, Dec 16 2021, 23:13:29) 
[GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import aioresponses
Traceback (most recent call last):
  File "", line 1, in 
  File "/dev/shm/python-aioresponses/aioresponses/__init__.py", line 2, in

from .core import CallbackResult, aioresponses
  File "/dev/shm/python-aioresponses/aioresponses/core.py", line 21, in

from pkg_resources import parse_version
ModuleNotFoundError: No module named 'pkg_resources'
>>>

This error is also present in autopkgtest:
https://ci.debian.net/packages/p/python-aioresponses .

I believe this issue can be easily solved by explicitly adding python3-pkg-
resources into running dependency.

Since you are listed in the lowNMU list, I will upload a 0-day NMU shortly.
Let me know if you have any other issues.

-- 
Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: python-aioresponses
Source-Version: 0.7.2-1.1
Done: Boyuan Yang 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Dec 2021 15:38:15 -0500
Source: python-aioresponses
Architecture: source
Version: 0.7.2-1.1
Distribution: unstable
Urgency: high
Maintainer: Jonas Smedegaard 
Changed-By: Boyuan Yang 
Closes: 1002045
Changes:
 python-aioresponses (0.7.2-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * debian/control: Explicitly add runtime dependency:
 python3-pkg-resources. (Closes: #1002045)
Checksums-Sha1:
 cb2afb7c9fdbc1fc9daed3156e794eb2791d5c8f 2267 python-aioresponses_0.7.2-1.1.dsc
 e1d0f947a00c3cc4c1da53e320f5af0108877f8a 23006 
python-aioresponses_0.7.2.orig.tar.gz
 9ff7612460706a6f54bfc5b2f660a4e0b71d159c 4732 
python-aioresponses_0.7.2-1.1.debian.tar.xz
 29e9e58b008876c52ad4626216f7e873197048e5 8202 
python-aioresponses_0.7.2-1.1_amd64.buildinfo
Checksums-Sha256:
 7b26f136bfa6486ee9ed11c64a724833f62463fd038c493bd4d0bd978cb563af 2267 
python-aioresponses_0.7.2-1.1.dsc
 1bef1328f6732cd10b6d9c4ce02bd0198ffd491728d3c57f8e47fef1e427c5d3 23006 
python-aioresponses_0.7.2.orig.tar.gz
 852f0fed1e5aeea7bff791511eda72983711167baf573b7ac5058dd6c3506012 4732 
python-aioresponses_0.7.2-1.1.debian.tar.xz
 3a390b7bb163c24090ed92d9f8e8ed8af5f13d61c68f89fd7f059e5458900987 8202 
python-aioresponses_0.7.2-1.1_amd64.buildinfo
Files:
 d93ce3d2e1e74896978eca9ff8fa04f9 2267 python optional 
python-aioresponses_0.7.2-1.1.dsc
 5b2c7e986a3ba5114e30d8d3ff2ce5e1 23006 python optional 
python-aioresponses_0.7.2.orig.tar.gz
 af9166a851b59d39f37e4445d5defac6 4732 python optional 
python-aioresponses_0.7.2-1.1.debian.tar.xz
 a55d9a9410b2954515f8ee4f91724783 8202 python optional 
python-aioresponses_0.7.2-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmHA63AACgkQwpPntGGC
Ws5B2hAAjr1aTV6Acj4PVp2VBEYSfS+cwKUzx9lanz+G5VLkyHHoy0l0tjDdo9Rz
YaIioOSfAi+bwXN92eU7v5zH24IKd6xFY+uJW03P/iAlYc3OG6nUcsAOkniIC24W
as0eoJSlygJbWShswEo/2qksGHcEvedoDZWlLb6LWeXMfszEnKGq6IPStMWsBqdi

Processed: tags 1001667 + pending

[Debian Bug Tracking System]

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

> tags 1001667 + pending
Bug #1001667 [src:flam3] flam3: flaky autopkgtest on ppc64el
Added tag(s) pending.
>
End of message, stopping processing here.

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

Bug#1001764: More info

[Dima Kogan]

Hi. Thanks for the bug report. I'm not clear on how to reproduce this so
that I can fix it.

I installed python3.10, and asked the build system to use it. Instead of
the error you're reporting, I get a build error: it can't find the numpy
headers because python3-numpy is built for python3.9. This makes sense.

What do I need to install to reproduce this bug?

Thanks.

Bug#1002045: python3-aioresponses: Failed to import: No module named 'pkg_resources'

[Boyuan Yang]

Package: python3-aioresponses
Version: 0.7.2-1
Severity: grave
X-Debbugs-CC: d...@jones.dk
Tags: sid bookworm

Dear python-aioresponses maintainer,

After installing your package, the package cannot work when using "install
aioresponses":

% sudo apt install python3-aioresponses
% python3
Python 3.9.9 (main, Dec 16 2021, 23:13:29) 
[GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import aioresponses
Traceback (most recent call last):
  File "", line 1, in 
  File "/dev/shm/python-aioresponses/aioresponses/__init__.py", line 2, in

from .core import CallbackResult, aioresponses
  File "/dev/shm/python-aioresponses/aioresponses/core.py", line 21, in

from pkg_resources import parse_version
ModuleNotFoundError: No module named 'pkg_resources'
>>>

This error is also present in autopkgtest:
https://ci.debian.net/packages/p/python-aioresponses .

I believe this issue can be easily solved by explicitly adding python3-pkg-
resources into running dependency.

Since you are listed in the lowNMU list, I will upload a 0-day NMU shortly.
Let me know if you have any other issues.

-- 
Thanks,
Boyuan Yang


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

Bug#1001961: No longer properly hooks the stat call

[Christoph Biedl]

Control: tags 1001961 patch

Christoph Biedl wrote...

> it seems recent changes in libc6 caused the stat() call in C applications
> to be expanded in a different way, a way fakeroot does not properly
> handle, resulting in the real user-id, not 0.

Fix appended (inline, not a patch) for better readability. Tested
successfully on the following archs: amd64, i386, armel, armhf, arm64;
with both fakeroot(-sysv) and fakeroot-tcp.

Cheers,

Christoph

Subject: Also wrap the "stat" library call
Author: Christoph Biedl 
Date: 2021-12-20
Bug-Debian: https://bugs.debian.org/1001961

Seems changes in glibc 2.33 caused the stat() function to be mapped
into a stat() library call instead of __xstat() as it used to be.

However, fakeroot does not wrap this, causing files to be reported
with the real owner, not 0 as expected.

The fix for this got more ugly than wished as the abstraction in
configure.ac would not allow wrapping both "stat" and "__xstat". So
enhance the search list capabilities with an optional symbol how the
wrapped function is named internally. Also hack the parser so
"state" gets actually probed.

Using "realstat" is not the best choice as it might be confusing,
but "statstat" seemed even worse.

--- a/configure.ac
+++ b/configure.ac
@@ -353,9 +353,13 @@
 
 :>fakerootconfig.h.tmp
 
-for SEARCH in %stat f%stat l%stat f%statat %stat64 f%stat64 l%stat64 
f%statat64 %mknod %mknodat; do
-  FUNC=`echo $SEARCH|sed -e 's/.*%//'`
+for SEARCH in %stat s%tat@realstat f%stat l%stat f%statat %stat64 f%stat64 
l%stat64 f%statat64 %mknod %mknodat; do
+  FUNC=`echo $SEARCH|sed -e 's/.*%// ; s/@.*//'`
   PRE=`echo $SEARCH|sed -e 's/%.*//'`
+  PF_PRE=`echo $SEARCH|sed -e 's/.*@//'`
+  if test "$PF_PRE" = "$SEARCH" ; then
+PF_PRE="${PRE}${FUNC}"
+  fi
   FOUND=
   for WRAPPED in __${PRE}x${FUNC} _${PRE}x${FUNC} __${PRE}${FUNC}13 
${PRE}${FUNC}; do
 AC_CHECK_FUNCS($WRAPPED,FOUND=$WRAPPED)
@@ -366,8 +370,8 @@
 dnl  for WRAPPED in _${PRE}${FUNC}; do
 dnlFOUND=$WRAPPED
 if test -n "$FOUND"; then
-  PF=[`echo ${PRE}${FUNC}| tr '[a-z]' '[A-Z]'`]
-  DEFINE_WRAP=[`echo wrap_${PRE}${FUNC}| tr '[a-z]' '[A-Z]'`]
+  PF=[`echo $PF_PRE | tr '[a-z]' '[A-Z]'`]
+  DEFINE_WRAP=[`echo wrap_${PF_PRE}| tr '[a-z]' '[A-Z]'`]
   DEFINE_NEXT=[`echo wrap_${FOUND}| tr '[a-z]' '[A-Z]'`]
   DEFINE_ARG=[`echo wrap_${FOUND}| tr '[a-z]' '[A-Z]'`]
   AC_DEFINE_UNQUOTED(WRAP_${PF}, $FOUND)
@@ -509,6 +513,12 @@
 #define TMP_STAT  __astat
 #define NEXT_STAT_NOARG  next___astat
 
+#define WRAP_REALSTAT  __astat
+#define WRAP_REALSTAT_QUOTE  __astat
+#define WRAP_REALSTAT_RAW  __astat
+#define TMP_REALSTAT  __astat
+#define NEXT_REALSTAT_NOARG  next___astat
+
 #define WRAP_LSTAT_QUOTE  __astat
 #define WRAP_LSTAT  __astat
 #define WRAP_LSTAT_RAW  __astat


signature.asc
Description: PGP signature

Processed: Re: No longer properly hooks the stat call

[Debian Bug Tracking System]

Processing control commands:

> tags 1001961 patch
Bug #1001961 [fakeroot] No longer properly hooks the stat call
Added tag(s) patch.

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

Processed: src:python-lupa: fails to migrate to testing for too long: FTBFS on mipsel

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.10+dfsg-1
Bug #1002040 [src:python-lupa] src:python-lupa: fails to migrate to testing for 
too long: FTBFS on mipsel
Marked as fixed in versions python-lupa/1.10+dfsg-1.
Bug #1002040 [src:python-lupa] src:python-lupa: fails to migrate to testing for 
too long: FTBFS on mipsel
Marked Bug as done
> block -1 by 1001239
Bug #1002040 {Done: Paul Gevers } [src:python-lupa] 
src:python-lupa: fails to migrate to testing for too long: FTBFS on mipsel
1002040 was not blocked by any bugs.
1002040 was not blocking any bugs.
Added blocking bug(s) of 1002040: 1001239

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

Bug#1002040: src:python-lupa: fails to migrate to testing for too long: FTBFS on mipsel

[Paul Gevers]

Source: python-lupa
Version: 1.9+dfsg-1
Severity: serious
Control: close -1 1.10+dfsg-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1001239

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:python-lupa has been trying to migrate for 
61 days [2]. Hence, I am filing this bug. Your package FTBFS on mipsel, 
which I reported two weeks ago.


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=python-lupa



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#996051: extension compatibility with GNOME Shell 41

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - fixed-upstream
Bug #996051 [gnome-shell-extension-desktop-icons] 
gnome-shell-extension-desktop-icons: does not declare compatibility with GNOME 
Shell 41
Removed tag(s) fixed-upstream.

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

Bug#996051: extension compatibility with GNOME Shell 41

[Gunnar Hjalmarsson]

Control: tags -1 - fixed-upstream

It's not clear to me why the upstream issue was closed. I see nothing 
which indicates that the bug has been fixed.


--
Gunnar Hjalmarsson

Bug#965846: ufiformat: diff for NMU version 0.9.9-1.1

[Stephen Kitt]

You’re very welcome! I hope the changes aren’t too invasive; since short 
dh “just worked”, including cross-compilation, I went with that.


Regards,

Stephen


Le 20/12/2021 17:44, David Given a écrit :

Thank you for fixing these; I completely missed both of these bugs when 
they got filed.


On Mon, 20 Dec 2021 at 15:33, Stephen Kitt  wrote:


Package: ufiformat
Version: 0.9.9-1
Severity: normal
Tags: patch  pending

Dear maintainer,

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

Regards,

Stephen

Bug#997478: bug 997478 is forwarded to https://github.com/rupert/pyls-black/issues/36

[Julian Gilbey]

On Mon, Dec 06, 2021 at 11:14:06PM +0200, Adrian Bunk wrote:
> forwarded 997478 https://github.com/rupert/pyls-black/issues/36
> thanks

Thanks Adrian!

The way we're going to resolve this bug, though, is to upgrade Spyder
to version 5.2.0, which depends on pylsp-black instead, and then
request the removal of this package from Debian.

Best wishes,

   Julian

Bug#999524: python-language-server: FTBFS with numpy 1.21 (in experimental): dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

[Julian Gilbey]

On Thu, Nov 25, 2021 at 09:35:24PM +0100, Drew Parsons wrote:
> Source: python-language-server
> Followup-For: Bug #999524
> 
> Upstream lost write access to the python-language-server repo
> https://github.com/palantir/python-language-server/issues/935
> so have forked the project to python-lsp-server at
> https://github.com/python-lsp/python-lsp-server
> 
> As part of the move they renamed the module from pyls to pylsp.
> 
> The new version is packaged and available (python3-pylsp,
> src:python-lsp-server).
> 
> python-language-server can be removed once spyder is updated for pylsp.

Indeed!

Spyder is waiting for three packages to migrate from NEW, and then it
can be upgraded to 5.2.0; most of my packaging work is already in
salsa, and I'm just working on the autopkgtest suite at the moment.

Best wishes,

   Julian

Processed: [bts-link] source package libtoxcore

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package libtoxcore
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1001711 (http://bugs.debian.org/1001711)
> # Bug title: libtoxcore2: Stack-based buffer overflow vulnerability in UDP 
> packet handling in Toxcore (CVE-2021-44847)
> #  * https://github.com/TokTok/c-toxcore/pull/1718
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1001711 + fixed-upstream
Bug #1001711 [libtoxcore2] libtoxcore2: Stack-based buffer overflow 
vulnerability in UDP packet handling in Toxcore (CVE-2021-44847)
Added tag(s) fixed-upstream.
> usertags 1001711 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package gnome-shell-extension-desktop-icons

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package 
> gnome-shell-extension-desktop-icons
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #996051 (http://bugs.debian.org/996051)
> # Bug title: gnome-shell-extension-desktop-icons: does not declare 
> compatibility with GNOME Shell 41
> #  * https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/244
> #  * remote status changed: opened -> closed
> #  * closed upstream
> tags 996051 + fixed-upstream
Bug #996051 [gnome-shell-extension-desktop-icons] 
gnome-shell-extension-desktop-icons: does not declare compatibility with GNOME 
Shell 41
Added tag(s) fixed-upstream.
> usertags 996051 - status-opened
Usertags were: status-opened.
There are now no usertags set.
> usertags 996051 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#997333: marked as done (wifite: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: 'pyrit')

[Debian Bug Tracking System]

Your message dated Mon, 20 Dec 2021 16:48:55 +
with message-id 
and subject line Bug#997333: fixed in wifite 2.5.8-2
has caused the Debian Bug report #997333,
regarding wifite: FTBFS: FileNotFoundError: [Errno 2] No such file or 
directory: 'pyrit'
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.)


-- 
997333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wifite
Version: 2.5.8-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 -m unittest discover tests -v
> test_airmon_start (test_Airmon.TestAirmon) ... ok
> test_airodump_weird_characters (test_Airodump.TestAirodump) ... ok
> testAnalyze (test_Handshake.TestHandshake) ... ERROR
> testHandshakeAircrack (test_Handshake.TestHandshake) ... skipped 
> 'https://github.com/derv82/wifite2/issues/189'
> testHandshakeCowpatty (test_Handshake.TestHandshake) ... skipped 
> 'https://github.com/derv82/wifite2/issues/105'
> testHandshakePyrit (test_Handshake.TestHandshake) ... skipped 
> 'https://github.com/derv82/wifite2/issues/105'
> testHandshakeTshark (test_Handshake.TestHandshake) ... ok
> testTargetClients (test_Target.TestTarget)
> Asserts target parsing captures clients properly ... ok
> testTargetParsing (test_Target.TestTarget)
> Asserts target parsing finds targets ... ok
> 
> ==
> ERROR: testAnalyze (test_Handshake.TestHandshake)
> --
> Traceback (most recent call last):
>   File "/<>/tests/test_Handshake.py", line 27, in testAnalyze
> hs.analyze()
>   File "/<>/wifite/model/handshake.py", line 127, in analyze
> self.divine_bssid_and_essid()
>   File "/<>/wifite/model/handshake.py", line 38, in 
> divine_bssid_and_essid
> pairs = self.pyrit_handshakes()  # Find bssid/essid pairs that have 
> handshakes in Pyrit
>   File "/<>/wifite/model/handshake.py", line 109, in 
> pyrit_handshakes
> return Pyrit.bssid_essid_with_handshakes(
>   File "/<>/wifite/tools/pyrit.py", line 28, in 
> bssid_essid_with_handshakes
> pyrit = Process(command, devnull=False)
>   File "/<>/wifite/util/process.py", line 93, in __init__
> self.pid = Popen(command, stdout=sout, stderr=serr, stdin=stdin, cwd=cwd, 
> bufsize=bufsize)
>   File "/usr/lib/python3.9/subprocess.py", line 951, in __init__
> self._execute_child(args, executable, preexec_fn, close_fds,
>   File "/usr/lib/python3.9/subprocess.py", line 1821, in _execute_child
> raise child_exception_type(errno_num, err_msg, err_filename)
> FileNotFoundError: [Errno 2] No such file or directory: 'pyrit'
> 
> During handling of the above exception, another exception occurred:
> 
> Traceback (most recent call last):
>   File "/<>/tests/test_Handshake.py", line 29, in testAnalyze
> exit()
>   File "/usr/lib/python3.9/_sitebuiltins.py", line 26, in __call__
> raise SystemExit(code)
> SystemExit: None
> 
> --
> Ran 9 tests in 0.329s
> 
> FAILED (errors=1, skipped=3)
> make[1]: *** [debian/rules:9: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/wifite_2.5.8-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: wifite
Source-Version: 2.5.8-2
Done: Sophie Brun 

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

(This message was generated automatically at their request; if you

Bug#965846: ufiformat: diff for NMU version 0.9.9-1.1

[David Given]

Thank you for fixing these; I completely missed both of these bugs when
they got filed.

On Mon, 20 Dec 2021 at 15:33, Stephen Kitt  wrote:

> Package: ufiformat
> Version: 0.9.9-1
> Severity: normal
> Tags: patch  pending
>
> Dear maintainer,
>
> I've prepared an NMU for ufiformat (versioned as 0.9.9-1.1) and
> uploaded it to DELAYED/10. Please feel free to tell me if I
> should delay it longer.
>
> Regards,
>
> Stephen
>

Bug#1001447: marked as done (missing Depends on cl-esrap and cl-ppcre)

[Debian Bug Tracking System]

Your message dated Mon, 20 Dec 2021 16:33:28 +
with message-id 
and subject line Bug#1001447: fixed in cl-abnf 20200229.gitba1fbb1-1
has caused the Debian Bug report #1001447,
regarding missing Depends on cl-esrap and cl-ppcre
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.)


-- 
1001447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cl-abnf
Version: 20150608-1.1
Severity: serious
Tags: patch

The subject says it all. The abnf system requires the esrap and cl-ppcre
systems, but this is not reflected at the level of Debian dependencies.

--
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org
--- End Message ---
--- Begin Message ---
Source: cl-abnf
Source-Version: 20200229.gitba1fbb1-1
Done: Sébastien Villemot 

We believe that the bug you reported is fixed in the latest version of
cl-abnf, 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.
Sébastien Villemot  (supplier of updated cl-abnf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Dec 2021 16:48:20 +0100
Source: cl-abnf
Architecture: source
Version: 20200229.gitba1fbb1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Common Lisp Team 
Changed-By: Sébastien Villemot 
Closes: 909552 1001447
Changes:
 cl-abnf (20200229.gitba1fbb1-1) unstable; urgency=medium
 .
   * New upstream snapshot
   * Add d/watch
   * d/copyright: reflect upstream changes
   * Move under Debian Common Lisp Team maintenance. Thanks to Dimitri Fontaine
 for his work on this package.
   * Bump to debhelper 13
   * Bump Standards-Version to 4.6.0
   * Remove Build-Depends on dh-lisp
   * Add Rules-Requires-Root: no
   * Update Vcs-* fields for move to salsa
   * Mark as M-A foreign (Closes: #909552)
   * Add Depends on cl-esrap and cl-ppcre (Closes: #1001447)
   * Add supeficial autopkgtest that tries to load the package under sbcl,
 ecl, clisp and abcl
Checksums-Sha1:
 797fe6e4d983e432d9baca199e20117dfdf7a270 2070 cl-abnf_20200229.gitba1fbb1-1.dsc
 3da17e33be19b5c09fd8389db8ee82b8bfa64f2f 7868 
cl-abnf_20200229.gitba1fbb1.orig.tar.xz
 b47da8a7eab5807c55b71ded725c92f87ff29b4a 2604 
cl-abnf_20200229.gitba1fbb1-1.debian.tar.xz
 b00a26fec360eb5745d43f8bd738c1f92a1ad940 5860 
cl-abnf_20200229.gitba1fbb1-1_amd64.buildinfo
Checksums-Sha256:
 ebef3d01b864710dd6c4679cd08d75793ba300609e7efe0d00b5294e793e7706 2070 
cl-abnf_20200229.gitba1fbb1-1.dsc
 f492cd9f7b6466f3635789041c03f9838f4f122ebff9bcfeb49b67e359ede5c2 7868 
cl-abnf_20200229.gitba1fbb1.orig.tar.xz
 2055d0780c2df5ed3fac4b0dc11bcc9a49a073d7ffe3c7b54ac21c9e9e3dc19d 2604 
cl-abnf_20200229.gitba1fbb1-1.debian.tar.xz
 d2ae4a26753eee09878dc6cfdd8ccda30d6268983e4fc594e5629b35221365c0 5860 
cl-abnf_20200229.gitba1fbb1-1_amd64.buildinfo
Files:
 fb46f7622ef9407187ec92c826e939ea 2070 lisp optional 
cl-abnf_20200229.gitba1fbb1-1.dsc
 d9133e8a861e27235ae0abdf23fc0e9c 7868 lisp optional 
cl-abnf_20200229.gitba1fbb1.orig.tar.xz
 30e1b68e13d96ae209c1309a0b108f7b 2604 lisp optional 
cl-abnf_20200229.gitba1fbb1-1.debian.tar.xz
 3b93a2859030f0416f7f96785e34b2ad 5860 lisp optional 
cl-abnf_20200229.gitba1fbb1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAmHAqgsACgkQLOzpNQ7O
vkqPBg//U22ZHwIr/FXp1sXnXCj82K9N4QoRt9mRfB8EiH3j8ywwEHLYKIBQ4v+e
Dbp+IBl4+v1vfuXeUBx0JRaHoV3wUV12aHuR5UIiQhfOhfqi7IP7iSZ1zWe3o9Dq
85s1bQC4IwUgL0kWIzECcH1oSTQ9LPjUgZR4RWXA4PLvbWTgYoganlflEmQuNkqn
YcOiJSB8MVXVfJOJkD0QYCLG4uRtS6Bteu7/4aKIX0y+vr52f6eA2xoAMP4ggtUl
MRCUjlGqV25rhX+Yqxr0fk6AfkI1Se5KtmcnUW04vSlEJeY53sHQoqGYpDoJHZWs
QctEB8TKQtP/3xt+J4sR8jGVKUjFm22jLxkcp8fCHHUU+ef3bfMNnO/8CdXF0XqD
5K2J3pXw84mdb76DCiCNZQFTdvV4iZ5v1c2cfGVLEURD1ar3JWc2PiCJOC0Vkl/z
iARu0GzkFnR7vRN47iFyVPQoYPZIc8bprgDZCIfFziYSMYhDd7VzQQ27WYzebm+V
qVTiOh5dHpA72t3/ZsoDonVRnKmRYX/epyWeGxF/+b1ZWK7VON0ERiJMYKYseGDn
NakKV/bhnsP2Yz8y+Si5QkxbTHeFHyPoU+J24oaDDIXV83NPQeX1vWu9Ucoedf2N
997bgCP2xy8t8avY+o/d9nYDBrD34Z+0/wZwdpRlgUUlSGNmAc8=
=t2d3

Bug#1002026: python3-fabric is missing python3-decorator when fabric package is not installed

[Bolesław Tokarski]

Package: python3-fabric
Version: 2.5.0-0.3
Severity: serious
Justification: Policy 3.5
X-Debbugs-Cc: boleslaw.tokar...@gmail.com

Dear Maintainer,

This is a follow-up on bug 956320.

I installed python3-fabric, and created some simple code using the library. I 
got:

Traceback (most recent call last):
  File "script.py", line 2, in 
from fabric import Connection
  File "/usr/lib/python3/dist-packages/fabric/__init__.py", line 3, in 
from .connection import Config, Connection
  File "/usr/lib/python3/dist-packages/fabric/connection.py", line 10, in 

from decorator import decorator
ModuleNotFoundError: No module named 'decorator'

I do not need the 'fabric' package to use python3-fabric as a library. The
dependency should not be in the fabric package, but in the python3-fabric
package. Actually, just like the bug description says, "python3-fabric:
Missing dependency on python3-decorator".

Installing python3-decorator solves the problem, thus it should be a
dependency of python3-fabric, and cleared from the 'fabric' package
dependencies, since it will get pulled with python3-fabric.

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

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

Versions of packages python3-fabric depends on:
ii  python3   3.9.2-3
ii  python3-invoke1.4.1+ds-0.1
ii  python3-paramiko  2.7.2-1

python3-fabric recommends no packages.

python3-fabric suggests no packages.

-- no debconf information

Processed: Bug#997333 marked as pending in wifite

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997333 [src:wifite] wifite: FTBFS: FileNotFoundError: [Errno 2] No such 
file or directory: 'pyrit'
Added tag(s) pending.

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

Bug#997333: marked as pending in wifite

[Sophie Brun]

Control: tag -1 pending

Hello,

Bug #997333 in wifite 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/pkg-security-team/wifite/-/commit/5f5a7249d2b1875c1ae9d81ed9def4a4aa67bebc


Add a patch to be compatible with which / debianutils >=5.0 (Closes: #997333)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997333

Processed: Re: Bug#1001995: libcrypto++: ftbfs on armhf

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +confirmed
Bug #1001995 [libcrypto++] libcrypto++: ftbfs on armhf
Added tag(s) confirmed.
> forwarded -1 https://github.com/weidai11/cryptopp/issues/1094
Bug #1001995 [libcrypto++] libcrypto++: ftbfs on armhf
Set Bug forwarded-to-address to 
'https://github.com/weidai11/cryptopp/issues/1094'.

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

Bug#1001995: libcrypto++: ftbfs on armhf

[GCS]

Control: tags -1 +confirmed
Control: forwarded -1 https://github.com/weidai11/cryptopp/issues/1094

Hi Steve,

On Mon, Dec 20, 2021 at 1:03 AM Steve Langasek
 wrote:
> Libcrypto++ is failing to build on armhf because gcc there defaults to an
> implied -mfloat-abi=hard, which conflicts with -march=armv7-a because
> armv7-a does not guarantee floating-point support, and libcrypto++
> hard-codes -march=armv7-a in its makefile:
 Thanks, confirmed the problem and the fix as well on armhf in a Sid
chroot. Still need to check it on armel.

Cheers,
Laszlo/GCS

Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14

[Sébastien Villemot]

Le vendredi 10 décembre 2021 à 10:27 +0100, Sébastien Villemot a
écrit :
> 
> The problem seems again related to cl-esrap. I noticed that the Debian
> package tracks an old (dead) upstream, while there is a new alive fork.
> I’ll take over that package and hopefully fix the problem.

I’ve uploaded a new cl-esrap. It seems pgloader builds again.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org



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

Bug#997257: marked as done (snapd: FTBFS: libsnap-confine-private/test-utils.c:63:9: error: ‘g_spawn_check_exit_status’ is deprecated: Use 'g_spawn_check_wait_status' instead [-Werror=deprecated-decla

[Debian Bug Tracking System]

Your message dated Mon, 20 Dec 2021 14:43:39 +
with message-id 
and subject line Bug#997257: fixed in snapd 2.54.1-1
has caused the Debian Bug report #997257,
regarding snapd: FTBFS: libsnap-confine-private/test-utils.c:63:9: error: 
‘g_spawn_check_exit_status’ is deprecated: Use 'g_spawn_check_wait_status' 
instead [-Werror=deprecated-declarations]
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.)


-- 
997257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: snapd
Version: 2.51.7-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra 
> -Wmissing-prototypes -Wstrict-prototypes -Wno-missing-field-initializers 
> -Wno-unused-parameter -Werror -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -D_ENABLE_FAULT_INJECTION -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -MT 
> libsnap-confine-private/libsnap_confine_private_unit_tests-test-utils.o -MD 
> -MP -MF 
> libsnap-confine-private/.deps/libsnap_confine_private_unit_tests-test-utils.Tpo
>  -c -o 
> libsnap-confine-private/libsnap_confine_private_unit_tests-test-utils.o `test 
> -f 'libsnap-confine-private/test-utils.c' || echo 
> './'`libsnap-confine-private/test-utils.c
> libsnap-confine-private/test-utils.c: In function ‘rm_rf_tmp’:
> libsnap-confine-private/test-utils.c:63:9: error: ‘g_spawn_check_exit_status’ 
> is deprecated: Use 'g_spawn_check_wait_status' instead 
> [-Werror=deprecated-declarations]
>63 | g_assert_true(g_spawn_check_exit_status(exit_status, NULL));
>   | ^
> In file included from /usr/include/glib-2.0/glib.h:81,
>  from libsnap-confine-private/test-utils.c:24:
> /usr/include/glib-2.0/glib/gspawn.h:280:10: note: declared here
>   280 | gboolean g_spawn_check_exit_status (gint  wait_status,
>   |  ^
> cc1: all warnings being treated as errors
> make[3]: *** [Makefile:2704: 
> libsnap-confine-private/libsnap_confine_private_unit_tests-test-utils.o] 
> Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/snapd_2.51.7-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: snapd
Source-Version: 2.54.1-1
Done: Michael Vogt 

We believe that the bug you reported is fixed in the latest version of
snapd, 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.
Michael Vogt  (supplier of updated snapd 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, 20 Dec 2021 15:15:32 +0100
Source: snapd
Built-For-Profiles: noudeb
Architecture: source
Version: 2.54.1-1
Distribution: unstable
Urgency: medium
Maintainer: Michael Hudson-Doyle 
Changed-By: Michael Vogt 
Closes: 934372 940782 993233 997257
Launchpad-Bugs-Fixed: 1955137
Changes:
 snapd (2.54.1-1) unstable; urgency=medium
 .
   * New upstream release, LP: #1955137
 - buid-aux: set version before calling ./generate-packaging-dir
   This fixes the "dirty" suffix in the auto-generated version
 .
   * Upstream fixes for Debian bugs:
 - cgroups v2 are now supported (closes: #934372)
 - transitional package golang-github-ubuntu-core-snappy-dev
   dropped (closes: #940782)
 - support squashfs-tools 4.5 properly (closes: #993233)
 - fix FTBFS (closes: #997257)
 .
   * Updated the debian packaging:
 - add myself to 

Bug#965846: ufiformat: diff for NMU version 0.9.9-1.1

[Stephen Kitt]

Package: ufiformat
Version: 0.9.9-1
Severity: normal
Tags: patch  pending

Dear maintainer,

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

Regards,

Stephen
diff -u ufiformat-0.9.9/debian/changelog ufiformat-0.9.9/debian/changelog
--- ufiformat-0.9.9/debian/changelog
+++ ufiformat-0.9.9/debian/changelog
@@ -1,3 +1,14 @@
+ufiformat (0.9.9-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch to debhelper compatibility level 13 and short dh rules.
+Closes: #965846, #727021.
+  * Switch to libext2fs-dev.
+  * Watch https://github.com/tedigh/ufiformat instead of the dead
+GeoCities page.
+
+ -- Stephen Kitt   Mon, 20 Dec 2021 15:23:36 +0100
+
 ufiformat (0.9.9-1) unstable; urgency=low
 
   * New upstream release
reverted:
--- ufiformat-0.9.9/debian/compat
+++ ufiformat-0.9.9.orig/debian/compat
@@ -1 +0,0 @@
-5
diff -u ufiformat-0.9.9/debian/control ufiformat-0.9.9/debian/control
--- ufiformat-0.9.9/debian/control
+++ ufiformat-0.9.9/debian/control
@@ -2,8 +2,8 @@
 Section: utils
 Priority: optional
 Maintainer: David Given 
-Build-Depends: debhelper (>= 5), autotools-dev, automake, e2fslibs-dev
-Homepage: http://www.geocities.jp/tedi_world/format_usbfdd_e.html
+Build-Depends: debhelper-compat (= 13), libext2fs-dev
+Homepage: https://github.com/tedigh/ufiformat
 Standards-Version: 3.9.4
 
 Package: ufiformat
reverted:
--- ufiformat-0.9.9/debian/dirs
+++ ufiformat-0.9.9.orig/debian/dirs
@@ -1 +0,0 @@
-usr/bin
diff -u ufiformat-0.9.9/debian/rules ufiformat-0.9.9/debian/rules
--- ufiformat-0.9.9/debian/rules
+++ ufiformat-0.9.9/debian/rules
@@ -1,79 +1,7 @@
 #!/usr/bin/make -f
 # -*- makefile -*-
-# debian/rules file for ufiformat.
-# This file was originally written by Joey Hess and Craig Small.
-# As a special exception, when this file is copied by dh-make into a
-# dh-make output file, you may use that output file without restriction.
-# This special exception was added by Craig Small in version 0.37 of dh-make.
 
-# Uncomment this to turn on verbose mode.
-#export DH_VERBOSE=1
+export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
-
-# These are used for cross-compiling and for saving the configure script
-# from having to guess our platform (since we know it already)
-DEB_HOST_GNU_TYPE   ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
-DEB_BUILD_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
-
-export CPPFLAGS = $(shell dpkg-buildflags --get CPPFLAGS)
-export CFLAGS = $(shell dpkg-buildflags --get CFLAGS)
-export CXXFLAGS = $(shell dpkg-buildflags --get CXXFLAGS)
-export LDFLAGS = $(shell dpkg-buildflags --get LDFLAGS)
-
-configure:
-	dh_testdir
-	autoreconf -i
-	
-config.status: configure
-	dh_testdir
-	./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info CFLAGS="$(CFLAGS)" LDFLAGS="$(LDFLAGS)"
-
-
-build: build-arch build-indep
-build-arch: build-stamp
-build-indep: build-stamp
-
-build-stamp:  config.status
-	dh_testdir
-	$(MAKE)
-	touch $@
-
-clean:
-	dh_testdir
-	dh_testroot
-	
-	rm -f build-stamp
-	[ ! -f Makefile ] || $(MAKE) distclean
-	rm -f aclocal.m4 Makefile.in
-	rm -f config.sub config.guess config.status config.status.lineno
-	rm -f config.log configure config.h.in
-
-	dh_clean 
-
-install: build
-	dh_testdir
-	dh_testroot
-	dh_clean -k 
-	dh_installdirs
-	$(MAKE) DESTDIR=$(CURDIR)/debian/ufiformat install
-
-binary-indep: build install
-	# none
-
-binary-arch: build install
-	dh_testdir
-	dh_testroot
-	dh_installchangelogs ChangeLog
-	dh_installdocs
-	dh_installman ufiformat.man
-	dh_strip
-	dh_compress
-	dh_fixperms
-	dh_installdeb
-	dh_shlibdeps
-	dh_gencontrol
-	dh_md5sums
-	dh_builddeb
-
-binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install 
+%:
+	dh $@
diff -u ufiformat-0.9.9/debian/watch ufiformat-0.9.9/debian/watch
--- ufiformat-0.9.9/debian/watch
+++ ufiformat-0.9.9/debian/watch
@@ -1,6 +1,4 @@
-# Check upstream for a new version
-
-# Compulsory line, this is a version 3 file
-version=3
-
-http://www.geocities.jp/tedi_world/format_usbfdd_e.html  ufiformat-(.*)\.tar\.gz
+version=4
+opts="filenamemangle=s%(?:.*?)?v?(\d[\d.]*)\.tar\.gz%@PACKAGE@-$1.tar.gz%" \
+https://github.com/tedigh/ufiformat/releases \
+(?:.*?/)?v?(\d[\d.]*)\.tar\.gz debian uupdate


signature.asc
Description: PGP signature

Bug#999620: pktanon: autopkgtest regression on armhf

[Sascha Steinbiss]

Hi Paul,

sorry for the delay in replying, I was quite busy and now I have some
free time over the holidays to follow up.

>> I am puzzled. The recent upload only changed the watchfile and updated
>> Standards-Version, compat level etc -- packaging things. Nothing touched
>> the code or build rules.
> 
> Well, but maybe your build dependencies have. Also, compat level isn't
> totally safe either in general (although the issue here doesn't
> obviously look like it).

Yes, I agree it's likely not that.

[...]>> I must admit that being unfamiliar with these architectures and not
>> really having an idea of where to start, I am tempted to just remove
>> armhf from the list of supported architectures and have the version with
>> the broken autopkgtest removed from unstable. Do you probably know
>> someone who might be more knowledgeable with such architecture-specific
>> issues?
> 
> We have porters for architecture specific support. However, I'm not
> totally convinced yet it's architecture specific.

Maybe. You noted that it seems to work fine on a machine with the same
architecture but different specs.

> Is there anything I can try out for you on our armhf host to help debug
> the issue? Run the command with more debug options? Grab an output file
> from somewhere? 
Hmmm. Since I am pretty unfamiliar with the source and/or any
assumptions that are being made in the code, a good start would be to
get an idea of where in the code the bus error is triggered. You could
try the -v option but I am not sure it would help much.
I think a real stack trace would help, by running the tests with
valgrind or via gdb. Nothing one would do in a generic test suite :/
How much customization would be possible in the test run?

> I could try to run the test in testing with a rebuild of
> the package in testing, would that help?

Maybe, if that does not cost much then please try.

Cheers
Sascha

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

[Debian Bug Tracking System]

Your message dated Mon, 20 Dec 2021 13:33:47 +
with message-id 
and subject line Bug#999163: fixed in pagodacf 0.10-6
has caused the Debian Bug report #999163,
regarding pagodacf: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: pagodacf
Source-Version: 0.10-6
Done: Stéphane Glondu 

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

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

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

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated pagodacf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Dec 2021 14:07:02 +0100
Source: pagodacf
Architecture: source
Version: 0.10-6
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Closes: 999163
Changes:
 pagodacf (0.10-6) unstable; urgency=medium
 .
   [ Stéphane Glondu ]
   * Team upload
   * Switch to dh (Closes: #999163)
   * Bump debhelper compat level to 13
   * Bump Standards-Version to 4.6.0
   * Bump debian/watch version to 4
   * Add Rules-Requires-Root: no
   * Remove Samuel from Uploaders
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * Add missing ${misc:Depends} to Depends for libcf-ocaml-dev, libcf-ocaml.
   * Set debhelper-compat version in Build-Depends.
Checksums-Sha1:
 a92c196f50a1354deaf490ae6a0cf6a2afa0 1732 pagodacf_0.10-6.dsc
 4adabc4edd64e29f1d689af4fd11e98b2bcc361d 8472 pagodacf_0.10-6.debian.tar.xz
Checksums-Sha256:
 123f7ba852d927078cbc8ece3aecdfdde8eebad760d97b2e17c7fe63b19784a3 1732 
pagodacf_0.10-6.dsc
 5fea7cfa94085459590fc7951f387e58275cadc021c80edb95c2a72e28ce1f35 8472 
pagodacf_0.10-6.debian.tar.xz
Files:
 ccf758fd1b9272a19e631bdbe8d4fa54 1732 ocaml optional pagodacf_0.10-6.dsc
 315210d77098a6c746c0e31a4720ec61 8472 ocaml optional 
pagodacf_0.10-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmHAgbUACgkQIbju8bGJ
MIEPlwgAmA3ZRDldh2wb9ibK++7danRxwQ1vj3FLwGzXmKQWc5CtkyuYEfeBwa60
iS02ds0C66LlVte4DxrBtYtD2/Bdi2KTisZfYk2eGjVc7afbRV3tg6Whizulq5nm
LN/+ra0fHs/Ac9gQAIuNV/nmb3YB4lY6tl+5HQDHtUWb0rt71UONdPc8g0zdivBJ
qqLLtksTeHleDylpjsDnA6DKAix1EG61Te+aL+38N7J3uP5ggmiXyyqB4DEYb1jf
7cH+NFJzrWFmZQDO4PB4+WCkDq8i7LMyi8tPv3gTRuixVuAaClVs+oeD9BMID2mH
/8uGmaQoD9Di+jJahPXIJx+ME8NnKw==
=dZj5
-END PGP SIGNATURE End Message ---

Bug#1001936: marked as done (r-cran-rbibutils: Failing autopkgtests on !x86)

[Debian Bug Tracking System]

Your message dated Mon, 20 Dec 2021 13:34:00 +
with message-id 
and subject line Bug#1001936: fixed in r-cran-rbibutils 2.2.7-2
has caused the Debian Bug report #1001936,
regarding r-cran-rbibutils: Failing autopkgtests on !x86
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.)


-- 
1001936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-rbibutils
Version: 2.2.4-1
Severity: serious
Control: forwarded -1 https://github.com/GeoBosh/rbibutils/issues/8

Dear Maintainer,

rbibutils fails its autopkgtests as given below.
I have fwded this to upstream.

══ Failed tests 
── Failure (test-convert.R:338:5): bibConvert works ok ─
readLines(tmp_ads) has changed from known value recorded in 'xampl_bib2ads.rds'.
2/313 mismatches
x[293]: "%R ..."
y[293]: "%R ..U"

x[300]: "%R 1988..."
y[300]: "%R 1988..U"

[ FAIL 1 | WARN 0 | SKIP 0 | PASS 86 ]
Error: Test failures

--
Full log:
https://ci.debian.net/data/autopkgtest/testing/arm64/r/r-cran-rbibutils/17705516/log.gz

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

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

Versions of packages r-cran-rbibutils depends on:
ii  libc62.32-4
ii  r-base-core [r-api-4.0]  4.1.2-1

Versions of packages r-cran-rbibutils recommends:
ii  r-cran-testthat  3.1.0-2

r-cran-rbibutils suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: r-cran-rbibutils
Source-Version: 2.2.7-2
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
r-cran-rbibutils, 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.
Nilesh Patra  (supplier of updated r-cran-rbibutils package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Dec 2021 18:55:04 +0530
Source: r-cran-rbibutils
Architecture: source
Version: 2.2.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Nilesh Patra 
Closes: 1001936
Changes:
 r-cran-rbibutils (2.2.7-2) unstable; urgency=medium
 .
   * Team Upload.
   * Pull upstream patch to fix arm64 CI problem (Closes: #1001936)
Checksums-Sha1:
 2500276a35f2b7ff757d4d293246acd0dc4bc436 2126 r-cran-rbibutils_2.2.7-2.dsc
 3eabb827f061b5d124cbbea85786be3d4f6bad50 3268 
r-cran-rbibutils_2.2.7-2.debian.tar.xz
 c5ed30f2da613c64a5125bfe7087ed919c6fdfd1 10486 
r-cran-rbibutils_2.2.7-2_amd64.buildinfo
Checksums-Sha256:
 8931482b96b6543e2d022ec9bc78c168b7105d66c010ca44b2eba9f0370dc2cd 2126 
r-cran-rbibutils_2.2.7-2.dsc
 8a1532baef59255150ff465a95b6189760125a487ff8ffb9e1fb517497c267d8 3268 
r-cran-rbibutils_2.2.7-2.debian.tar.xz
 60b062f6121d5261fc1cd871cee57aa0be3bccc7ec6a260eb79c00bffd982322 10486 
r-cran-rbibutils_2.2.7-2_amd64.buildinfo
Files:
 683c1cc0d914657b4a35ccf66c02e598 2126 gnu-r optional 
r-cran-rbibutils_2.2.7-2.dsc
 931c262540d434d0757e459c6fc7c6cb 3268 gnu-r optional 
r-cran-rbibutils_2.2.7-2.debian.tar.xz
 9154eed824d1634177e263fe09086453 10486 gnu-r optional 
r-cran-rbibutils_2.2.7-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmHAhSESHG5pbGVzaEBk
ZWJpYW4ub3JnAAoJEAC650s0M2nxgTAQAK2bbEtCzcK8JGD5ZhrTIWTg8C9GtTRx
C9eUKmB+16zyAXPndKzWvKmqxSu3zJCFNX9SH5wbnTDZyPdwlv//Frd3WPScNXWs
ay5eX3hGMKzpAyh1j0lYuoYqQrvj7Cs0+HONCfWYQ7ztdsMmPB/lY70kSABDblgk
D2qtZGPZIKk9V0J5j63vZOAXbxO2HB1iKlLXX+FUiUUeIVnpTDlCIRXOnHJ5h4XH
3IHQD/gDPRVAWs/1pHJ2obblucnIfM9unidEzbCUTJ4toxn9FURXWTpSHFU/R88W
Rm3A+BmjP6J50JjeRkFeEL5t39Hc/mtZniyG3a2UN+NB+SzjyvnQahLYyfcdQzs2

Bug#1001936: marked as pending in r-cran-rbibutils

[Nilesh Patra]

Control: tag -1 pending

Hello,

Bug #1001936 in r-cran-rbibutils 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/r-pkg-team/r-cran-rbibutils/-/commit/37cb39c75f793b2fa01a476b61d4ecfb0fdc64bb


Pull upstream patch to fix arm64 CI problem (Closes: #1001936)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1001936

Processed: Bug#1001936 marked as pending in r-cran-rbibutils

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1001936 [r-cran-rbibutils] r-cran-rbibutils: Failing autopkgtests on !x86
Added tag(s) pending.

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

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

[Debian Bug Tracking System]

Your message dated Mon, 20 Dec 2021 13:19:11 +
with message-id 
and subject line Bug#999238: fixed in xdelta 1.1.3-9.4
has caused the Debian Bug report #999238,
regarding xdelta: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: xdelta
Source-Version: 1.1.3-9.4
Done: Colin Watson 

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

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

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

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated xdelta 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, 15 Dec 2021 12:15:05 +
Source: xdelta
Architecture: source
Version: 1.1.3-9.4
Distribution: unstable
Urgency: medium
Maintainer: LaMont Jones 
Changed-By: Colin Watson 
Closes: 999238
Changes:
 xdelta (1.1.3-9.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/rules: Add build-arch and build-indep targets (closes: #999238).
Checksums-Sha1:
 35b3c979e880429b502c18dbd06e1f529fd261f8 1896 xdelta_1.1.3-9.4.dsc
 adcdada05f0211269b69abb1eb73403a6c745f3c 392393 xdelta_1.1.3-9.4.diff.gz
 5472abc68f7c0bdbe5d895fbcfb36f84a0d37409 7590 xdelta_1.1.3-9.4_source.buildinfo
Checksums-Sha256:
 9c2e5aedc3b37ff8b2d1645ac42e9cefdc1bb1ccd534493acb6c83642b6df87e 1896 
xdelta_1.1.3-9.4.dsc
 1b76de3bfa65caabc06ac014a7759a23c61ff8bf18c700fa2aef026458eb3c8d 392393 
xdelta_1.1.3-9.4.diff.gz
 3318a7bbb5ea4a4dda0db8c678fb151a70b7584f285396cee3f5fa50b3d0c9dc 7590 
xdelta_1.1.3-9.4_source.buildinfo
Files:
 b6e5e7dfd30a4311af91bb0cf4a0423a 1896 utils optional xdelta_1.1.3-9.4.dsc
 bf6a84350f926ec1d651cafc9113570e 392393 utils optional xdelta_1.1.3-9.4.diff.gz
 a68483cc6b6633fa6935348df057ae43 7590 utils optional 
xdelta_1.1.3-9.4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmG55E0ACgkQOTWH2X2G
UAvcRw/9ERjDW1yAc1e2OZ7AxLRFBbU59lP/M2vV3QiZvTBga6LN+mdX8dpHDNsQ
m+eTIlTwHVKzrPdvmMOX2K4cTBLdMRY3/qXRdc5jpeSr/0nLEoBbG1bPOgn3K6Fs
wphvGYpwpZ1ekBMGt48q2aCv/V0mgUYqXRmC/TeCJxMICXvXFdcNHNYl3GKjya+m
b9RwAEk3bt62dF1tfp/EEfb2xzqcnUvN2P+1x32fr/14zSljvFpOzcPYlwD6z41r
75KVA/LAro3sU0NEfPD+MBDMkPdzK/QJ9apMYLnVxXbVZhXFVcMWWjkp88OBQtnt
tAUpB2qiA2Sr5mTQzG+H557iDAhn/JQ/m/gnUXvhiVSekBdwBDICbtXFjTUxzzuO
nKu+/o+g1f9x7M/FRhnJqecMx+XCUYd7Opvxv0TcLKTrLShWT+L3zPw+nsG4tiP3
mT/5TS6rLwjb6Byi1/BC/2I6oupguFkJbNQu0Aj6T1GFeV8c+tzRofpFmaDOe6/G
NU/V345mAbc2RKhkApTFJJj1oWuNapExZbP1Wbn1VPF6Tr7NSjf3j6MSFNmynrLM
PtofPhKF7UZWBKw7zwMkmoEyg8AzhT5N0zqtIE4e7EG0hk3T5mdOIWzdGHnpdA08
5a/QduLnmdTMar7Gk4VOBoTlfwGb9ljOiuJQMfoveEVKtrbDurg=
=Phnk
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Mon, 20 Dec 2021 12:33:36 +
with message-id 
and subject line Bug#999184: fixed in osdclock 0.5-25
has caused the Debian Bug report #999184,
regarding osdclock: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: osdclock
Source-Version: 0.5-25
Done: Håvard Flaget Aasen 

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

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

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

Debian distribution maintenance software
pp.
Håvard Flaget Aasen  (supplier of updated osdclock 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Dec 2021 09:30:14 +0100
Source: osdclock
Architecture: source
Version: 0.5-25
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Håvard Flaget Aasen 
Closes: 941435 999184
Changes:
 osdclock (0.5-25) unstable; urgency=medium
 .
   * QA upload.
   * Change to dh sequencer.
 - This includes target build-arch and build-indep.  Closes: #999184
 - Makes it possible to cross-build. Closes: #941435
 - Using default Debian CFLAGS when compiling.
   * New patch: Use destdir, create directories and place man-page
 in correct path. This also makes d/manpages and d/install unnecessary.
   * Change to debhelper-compat.
   * Bump debhelper to 13.
   * Document Rules-Requires-Root.
   * Update Standards-Version to 4.6.0
   * d/copyright:
 - Update to be DEP5 compliant.
 - Add year to upstream copyright holder.
Checksums-Sha1:
 c52ea17b9b8fed02466b0baa528f255a0478c390 1713 osdclock_0.5-25.dsc
 fa254cc98bc48baf503734fbfe45df2b3b643fc0 6040 osdclock_0.5-25.debian.tar.xz
 430402ac6a52880b3bff003254d0f8e2cb96c542 6195 osdclock_0.5-25_source.buildinfo
Checksums-Sha256:
 c6c4632f01e2b9c1b58fc736c9bd5dd590ed49bffabb219405099f496652321d 1713 
osdclock_0.5-25.dsc
 f3f3f0a85b7589a740ac45bff664e192a85a7111db11581b3d30fd4f39555db9 6040 
osdclock_0.5-25.debian.tar.xz
 d343a9c8f2d812fda4a8a9c56f387bf129617efba3e5b70e5db646deaf7765c5 6195 
osdclock_0.5-25_source.buildinfo
Files:
 c33328ac63afb099cf85882536c70932 1713 utils optional osdclock_0.5-25.dsc
 e53363d69b61d92b494e7676cdeabba6 6040 utils optional 
osdclock_0.5-25.debian.tar.xz
 023acabd4395a9b840cbc4f207302c78 6195 utils optional 
osdclock_0.5-25_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmHAdTsACgkQweDZLphv
fH4lZRAA60k3RR1On7ANBqtts50KPCrOHHqbGu3Vd2HP6iQ9zBUOOPtOGtGsnH2a
2ccbgC3BGPNLOSGG5vigEv/kLqFGOmwb6ozDT88I9MDjoQOfeaLBBjmqOOhjNh3b
YGHJRvtAgUkM2SdrTfdSoWqqbE5mXEMuH5kxZ6lp1OAmKqldFtPFvtI5KICrrAvC
fs9oeb0u72KJY3m//cpWvW5JJB7J9dAMrJbuRLlPsHwVYcAZaZi/wz6ctlROpJiW
A7EU2ISMMdDgbYjuxybArzR2/S+o1gXF0pLf1kINl8Wtk5ntT8eSjTpYtvGVUZdf
S/+6khfP+plltm+z7La6eyGu9kEC/cNIx3eROaS1mLmw8ASDoVu6VBj32qPIpYfX
UuQlM7dvaq9dSQXbw80WexaH0qZhY6pweXP2HVNy5VYVNOlGG/q8gOvj4veStnjy
ImHmWGDmygU9AFLDwU14AMRImzL2hc51LQgFz4egHXESxSAvBfoK18wVejTupuHd
VVMWMxLZmittd06PDdlJXZlLnhWL92QPoENfd9Iun8LXA8BC0gOuBNpVt4fw3DsN
W8bi9za+h3NXYDviqhFy+yL4okipHHMNJohK3uKLznj+vt0UeikBEkHzQ+jPasnW

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

[Debian Bug Tracking System]

Your message dated Mon, 20 Dec 2021 12:33:26 +
with message-id 
and subject line Bug#998931: fixed in crip 3.9-3
has caused the Debian Bug report #998931,
regarding crip: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: crip
Source-Version: 3.9-3
Done: Håvard Flaget Aasen 

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

Debian distribution maintenance software
pp.
Håvard Flaget Aasen  (supplier of updated crip package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Dec 2021 10:00:37 +0100
Source: crip
Architecture: source
Version: 3.9-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Håvard Flaget Aasen 
Closes: 998931
Changes:
 crip (3.9-3) unstable; urgency=medium
 .
   * QA upload.
   * Change to dh sequencer.
 - This includes target build-arch and build-indep. Closes: #998931
   * Drop d/compat.
   * Bump to debhelper 13.
   * Update source format to 3.0 (quilt).
   * d/watch: Bump to version 4.
   * Add runtime dependency on sensible-util.
   * Drop version constraint on flac, not needed.
   * Drop build-depend on quilt.
   * Document Rules-Requires-Root.
   * Update Standards-Version to 4.6.0.
Checksums-Sha1:
 1374f63bdebb6d2ee32b5471bd7796e5473a8487 1687 crip_3.9-3.dsc
 535601cf1835d3b6c54b2eea9a11afe948d97e19 7932 crip_3.9-3.debian.tar.xz
 f9d938abcd5f824af5f3f00140b1524cc21948fa 5410 crip_3.9-3_source.buildinfo
Checksums-Sha256:
 80d18a7b6a1264b3b916f6750b89df9f4cf98d01eb5dd41b56d935f100430f7e 1687 
crip_3.9-3.dsc
 1a6e7aadc9e0f5219df2da45941755fa0c8612a9758779ec5b631e33235e84da 7932 
crip_3.9-3.debian.tar.xz
 eef38938a540fccb2d2d30fb303a9eaec5259f01d63075c4681b6ba4403195bc 5410 
crip_3.9-3_source.buildinfo
Files:
 75f58b38c962ea57344461b065abd0c2 1687 sound optional crip_3.9-3.dsc
 6bac11dbe07d4b284abddcbf2527d194 7932 sound optional crip_3.9-3.debian.tar.xz
 74bdd9d9538838dcdaf1cc10920e4fa1 5410 sound optional 
crip_3.9-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmHAdGQACgkQweDZLphv
fH67IxAAo5gxUaZ+RX56Tx09Sfe8SRHec3aH0i18x2U7ZAL4HNx5p0SklSh+f309
4NB2hMagygv7zxLf9Aidw5JieL8isnkt/hl8uopPeQ8GcO+oTjJaw2mRIeIQ7m9y
Fj3yySQwSQpLobstlITR7iMD9EVblWWqYRGzpfENwvFoAYHRVaCJlJxsRpOYAKwK
2l8sbdsEJ09lW+9R+35jJA4l9CseuQCkya3GNzxkr7vkSmpDs4qsetbAaeKhgZYP
zP8cRWnI1MgAnyuZ3B15qx16r4X8IjobhySEYTWLknRUgJ6UnW1xVUQGvXlTesZm
N9hlgmgFKC/F39WGnYhlD2bApsfzkyrLEgGCQE7VJq06ZSAN+5zn6KsOjg7ryrT6
YrOCNK48cOnBaVPuSvAjwu5vcE6337VPT0OiNDpAqzmsShEceumU3GeGu4aFN8/l
mn5QDwdZAKLbAvZwOs7Qah6aLJuYR8hMOnCR6k1GL/NxIRRDNITzKrzHIDFD2ae/
RiiuLMPe6lmhAvybml18rRLvHgKmvmYWpnMVcsVf/6zYWxp0jUaANRlG0fbpEjfv
t1tcnK2qnBVXsEJ1bQ0+uZX0EIY+tl5w6s9f9WgIMR4f/4GjZFpdQo1tN7UTKESK
CV1JPP7Kvop0xdCk7+I9TybxOCTjGcXUKrIFGxwE8C/c3CnR0q8=
=TEqU
-END PGP SIGNATURE End Message ---

Bug#1001527: FTBFS with fmtlib 8

[Sascha Steinbiss]

Hi,

> I have uploaded fmtlib/8 to experimental, and plan to start this transition.
> 
> You package FTBFS with fmtlib/8, it has been fixed in version 2021.08.26.
> Please package the new version or backport the relevant commits.

Unfortunately never versions than the one currently in testing
(2021.05.27) can not be easily packaged, since new versions require
Apache Arrow which is not (yet) available in Debian [0]. A package for
Arrow has been prepared [1] but I am not willing to maintain this large
software dependency -- which is very actively developed with potentially
breaking API/ABI changes -- on my own so I am currently refraining from
uploading it. I have handed my preliminary work over to the Debian
Science Team.

The backport of the libfmt support update is too much of a hassle to
port to an old version that is unlikely to be used by anyone as VAST
development also moves too fast to be OK with Debian's update routine.

I suggest to let VAST drop out of testing until Apache Arrow is
available, so it does not block your transition.

Cheers
Sascha

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970021
[1] https://salsa.debian.org/science-team/arrow

Bug#1001999: snapd: packaging not up to Debian standards

[Michael Vogt]

Thanks for reaching out and reporting this bug. Fwiw, I did reply to the 
original mail too bug for some reason it seems that the reply did not made it 
to you, not sure what happened here, sorry for that.

I am preparing an upload of the latest 2.54.1 release of snapd that partly 
addresses the points you raised. Unfortunately I won't be able to fix it all in 
this upload (time constraints) but it should improve the situation quite a bit.

Thanks,
 Michael

Bug#996154: marked as done (libopenobex2-dev: openobex-target-release.cmake forces static linking)

[Debian Bug Tracking System]

Your message dated Mon, 20 Dec 2021 11:33:28 +
with message-id 
and subject line Bug#996154: fixed in libopenobex 1.7.2-2.1
has caused the Debian Bug report #996154,
regarding libopenobex2-dev: openobex-target-release.cmake forces static linking
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.)


-- 
996154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: obexftp
Version: 0.24-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0

Hi,

We are about to enable building against ruby3.0 on unstable. During a test
rebuild, obexftp was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot. This, however, looks unrelated to
ruby3.0.

Relevant part (hopefully):
> /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libopenobex.a(api.c.o): relocation 
> R_X86_64_PC32 against symbol `stderr@@GLIBC_2.2.5' can not be used when 
> making a shared object; recompile with -fPIC
> /usr/bin/ld: final link failed: bad value
> collect2: error: ld returned 1 exit status


The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/obexftp/obexftp_0.24-6+rebuild1633373966_amd64.build.txt


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libopenobex
Source-Version: 1.7.2-2.1
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated libopenobex package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 20 Dec 2021 12:00:45 +0100
Source: libopenobex
Architecture: source
Version: 1.7.2-2.1
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu 
Changed-By: Jonas Smedegaard 
Closes: 996154
Changes:
 libopenobex (1.7.2-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   * fix install shared libriaries (not static ones)
 when file paths clash;
 closes: bug#996154,
 thanks to Antonio Terceiro, Lucas Kanashiro, and Adrian Bunk,
 and to Patrick Ohly for raising awareness of the issue
Checksums-Sha1:
 b1394d0c2eeb787e3a4d345a6c688915f3441b54 2160 libopenobex_1.7.2-2.1.dsc
 4a0941e5ec3389f32d4d5ef757bb299a45d60004 7732 
libopenobex_1.7.2-2.1.debian.tar.xz
 9a4fb377ea627a8278f08c7d7a60ac22d4984c51 9667 
libopenobex_1.7.2-2.1_amd64.buildinfo
Checksums-Sha256:
 16de99f0aecbaf5e228bee6fa205013ebf31fd689172f57ddef0579b4ff60749 2160 
libopenobex_1.7.2-2.1.dsc
 7441405236e31b60d5896c14debf7681f3ae74b2d611faec0d1858616be10bfb 7732 
libopenobex_1.7.2-2.1.debian.tar.xz
 435cf899971b50132c0d5186843524d4137d8f1df88aef480d7f35a959e97275 9667 
libopenobex_1.7.2-2.1_amd64.buildinfo
Files:
 9bf9a90cfee028fae3291eb1fe2a7b53 2160 comm optional libopenobex_1.7.2-2.1.dsc
 cf75049f288db73000d441aade99c3ad 7732 comm optional 
libopenobex_1.7.2-2.1.debian.tar.xz
 9c78e21b087c5722921f48620bb69297 9667 comm optional 
libopenobex_1.7.2-2.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmHAZ1kACgkQLHwxRsGg
ASEUchAAntt1itJnMkLJI8/WlhjrWR7XpxKGXD7qut+WVlqS/K5yX/Ru7XIK+r7X
plgK560H2rdSbQAdJXFgSKhNyBzHdA6oK63nQ82EitFjUGkSrqUy7QJSEk92YwLp
GQaRnbbEeBJXaED6QVlNcnUOC4DLpWZXQSLzFGbtFxsfHaRUSX4Y8dXyQk7QyoxZ
ufiZgs9rKW48WBUW3LILP9HFUM1ia8qP8NzekLAzj40zBcMO0x8/+sBtswcfq0IF
on3QJ//96CLJbNbbWSeIUPTM9nN3vCuat23aFs9R/txJcE7oIkKM7wjt5mX6XmIH
7qGuV/A7Ok+uqOpKgMID8DIC8D+jjBdabrD+XuGeN5vmaWJYB5a6rV2VznyWKnIM
q1hD/wqPF8A29XKJRdfI0clCSoLt5p5jb/YrxYRuTlnZnHheYapJdEpoIdIhSd+A
XjputYY3PLCCY/GyDOuXk5vSUVQ3L6qsbQ55c2rgyahhM0TlRK+k1rt6LnA2hLRl
eaFG6fudFvYp1OFjuxAGDLjH6ssyzA0CUZQR4Ipa89WRGArcH6DTc9gki1J6hV35
O5iOvncw0abz2WXd67R9aKXO6nAz3RFspXKvEHApXsHY/WToHO0YIkw/yRhiUuGE
EqHzYuuiwiX0Mu+BHz68KsGf11PALbdIhWxwCSW9FQnHVP61yPM=
=geK4
-END PGP SIGNATURE End Message ---

Bug#997736:

[Daniel Swarbrick]

I noticed in the debian/rules that rebuilding the timezone JS data from the
tzdata package is *optional*, and only occurs if the moment-timezone
package has a +x suffix, e.g. +2021e. If not, the timezone JS data from
the upstream moment-timezone source will be used.

I just tried building v0.5.34 *without* the tzdata suffix, and all tests
passed. I suspect that in order to build against tzdata 2021e, despite it
allegedly already being included in the upstream v0.5.34 source, it would
require some manipulation of the tests. I suppose the question is how far
down the rabbit hole we want to go. I'm sure that this issue will arise
again as soon as tzdata 2022a is released, and we will need another patch
in moment-timezone, such as was contributed by Martina Ferrari in the past.

Perhaps we could instead just move forward with moment-timezone v0.5.34,
sans tzdata 2021e, in the interests of closing this bug and unblocking a
bunch of testing package transitions.

Bug#996154: libopenobex: diff for NMU version 1.7.2-2.1

[Jonas Smedegaard]

Control: tags 996154 + pending

Dear maintainer,

I've released an NMU for libopenobex (versioned as 1.7.2-2.1) and
uploaded it to unstable.
I took the liberty of uploading directly instead of via a delayed queue,
due to fixing a release-critical bug.


Regards,

 - Jonas

diff -Nru libopenobex-1.7.2/debian/changelog libopenobex-1.7.2/debian/changelog
--- libopenobex-1.7.2/debian/changelog  2021-10-04 02:37:56.0 +0200
+++ libopenobex-1.7.2/debian/changelog  2021-12-20 12:00:45.0 +0100
@@ -1,3 +1,15 @@
+libopenobex (1.7.2-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  * fix install shared libriaries (not static ones)
+when file paths clash;
+closes: bug#996154,
+thanks to Antonio Terceiro, Lucas Kanashiro, and Adrian Bunk,
+and to Patrick Ohly for raising awareness of the issue
+
+ -- Jonas Smedegaard   Mon, 20 Dec 2021 12:00:45 +0100
+
 libopenobex (1.7.2-2) unstable; urgency=medium
 
   [ Helmut Grohne ]
diff -Nru libopenobex-1.7.2/debian/rules libopenobex-1.7.2/debian/rules
--- libopenobex-1.7.2/debian/rules  2021-10-04 02:37:56.0 +0200
+++ libopenobex-1.7.2/debian/rules  2021-12-20 11:57:51.0 +0100
@@ -37,6 +37,6 @@
dh_auto_build -B $(BUILDDIR)-static
 
 override_dh_auto_install:
-   dh_auto_install -B $(BUILDDIR)
dh_auto_install -B $(BUILDDIR)-static
+   dh_auto_install -B $(BUILDDIR)
cp -v $(BUILDDIR)-static/lib/*.a 
debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/

Processed: libopenobex: diff for NMU version 1.7.2-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 996154 + pending
Bug #996154 [libopenobex2-dev] libopenobex2-dev: openobex-target-release.cmake 
forces static linking
Added tag(s) pending.

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

Processed: your mail

[Debian Bug Tracking System]

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

> found 1001596 0~20200923.3-2
Bug #1001596 [libabsl-dev] libabsl-dev: please do not override the --as-needed 
linker flag
Marked as found in versions abseil/0~20200923.3-2.
> affects 1001596 src:telegram-desktop
Bug #1001596 [libabsl-dev] libabsl-dev: please do not override the --as-needed 
linker flag
Added indication that 1001596 affects src:telegram-desktop
> notfixed 1001016 2.9.2+ds-1
Bug #1001016 [telegram-desktop] telegram-desktop: Version in stable (2.6.1) 
becoming unusable
No longer marked as fixed in versions telegram-desktop/2.9.2+ds-1.
> fixed 1001016 3.1.1+ds-1
Bug #1001016 [telegram-desktop] telegram-desktop: Version in stable (2.6.1) 
becoming unusable
Marked as fixed in versions telegram-desktop/3.1.1+ds-1.
>
End of message, stopping processing here.

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

Bug#996154: syncevolution is marked for autoremoval from testing

[Patrick Ohly]

Debian testing autoremoval watch  writes:
> syncevolution 2.0.0-3 is marked for autoremoval from testing on 2021-12-27
>
> It (build-)depends on packages with these RC bugs:
> 996154: libopenobex2-dev: openobex-target-release.cmake forces static linking
>  https://bugs.debian.org/996154

If libopenobex gets removed from Debian, SyncEvolution either has to be
removed as well or direct synchronization with phones via SyncML must be
disabled in it. I know that some people still use it for that, although
the phones that support SyncML over Bluetooth of course are slowly dying
out.

libopenobex is still needed for that because I have not found a way to
do the same with some other library or service. obexd only supports some
higher level OBEX protocols, but not SyncML - at least not as far as I
can tell.

Bye, Patrick (SyncEvolution developer)

Bug#1001291: marked as done (binoculars: autopkgtest tests for all supported python3 versions but vtk7 extensions don't exist for all)

[Debian Bug Tracking System]

Your message dated Mon, 20 Dec 2021 09:03:28 +
with message-id 
and subject line Bug#1001291: fixed in binoculars 0.0.10-1
has caused the Debian Bug report #1001291,
regarding binoculars: autopkgtest tests for all supported python3 versions but 
vtk7 extensions don't exist for all
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.)


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

Source: binoculars
Version: 0.0.6-1
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 binoculars 
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
binoculars from testing0.0.6-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems 
you're testing for all supported Python3 version in Debian, but one of 
your dependencies doesn't provide the required extensions (bug #951300). 
Either convince the maintainer of that package to build the extensions, 
or only test with the default Python3 version.


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/b/binoculars/17344284/log.gz

Testing with python3.10:
test_IO (test_cfg.TestCase) ... ok
test_id03 (unittest.loader._FailedTest) ... ERROR
test_metadata (unittest.loader._FailedTest) ... ERROR

==
ERROR: test_id03 (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: test_id03
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/vtk/vtkCommonCore.py", line 5, 
in 

from .vtkCommonCorePython import *
ModuleNotFoundError: No module named 'vtk.vtkCommonCorePython'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.10/unittest/loader.py", line 436, in 
_find_test_path

module = self._get_module_from_name(name)
  File "/usr/lib/python3.10/unittest/loader.py", line 377, in 
_get_module_from_name

__import__(name)
  File 
"/tmp/autopkgtest-lxc.73x5fv_7/downtmp/autopkgtest_tmp/tests/test_id03.py", 
line 1, in 

from binoculars.backends import id03
  File "/usr/lib/python3/dist-packages/binoculars/backends/id03.py", 
line 10, in 

from .. import backend, errors, util
  File "/usr/lib/python3/dist-packages/binoculars/backend.py", line 1, 
in 

from . import util, errors, dispatcher
  File "/usr/lib/python3/dist-packages/binoculars/dispatcher.py", line 
9, in 

from . import util, errors, space
  File "/usr/lib/python3/dist-packages/binoculars/space.py", line 13, 
in 

from vtk import vtkImageData, vtkXMLImageDataWriter
  File "/usr/lib/python3/dist-packages/vtk/__init__.py", line 41, in 


from .vtkCommonCore import *
  File "/usr/lib/python3/dist-packages/vtk/vtkCommonCore.py", line 9, 
in 

from vtkCommonCorePython import *
ModuleNotFoundError: No module named 'vtkCommonCorePython'


==
ERROR: test_metadata (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: test_metadata
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/vtk/vtkCommonCore.py", line 5, 
in 

from .vtkCommonCorePython import *
ModuleNotFoundError: No module named 'vtk.vtkCommonCorePython'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.10/unittest/loader.py", line 436, in 
_find_test_path

module = self._get_module_from_name(name)
  File "/usr/lib/python3.10/unittest/loader.py", line 377, in 
_get_module_from_name

__import__(name)
  File 

Bug#994286: marked as done (r-bioc-destiny: Orphaned upstream, marked for removal in next BioConductor release)

[Debian Bug Tracking System]

Your message dated Mon, 20 Dec 2021 09:59:55 +0100
with message-id 
and subject line Upstream has updated the package thus closing the bug
has caused the Debian Bug report #994286,
regarding r-bioc-destiny: Orphaned upstream, marked for removal in next 
BioConductor release
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.)


-- 
994286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-bioc-destiny
Severity: critical
Justification: breaks unrelated software
X-Debbugs-Cc: 991...@bugs.debian.org, debia...@lists.debian.org

Hi,

as it was discussed on the debian-r mailing list[1] r-bioc-destiny
should not block the BioConductor transition.  The relevant statement
from upstream is:

  On Tue, Sep 14, 2021 at 7:28 AM Kern, Lori  
wrote:

  Destiny is currently marked as deprecated and scheduled to be
  removed in the next Bioconductor release as the maintainers were
  unresponsive to our requests to fix their package.  The package is
  failing in both release and devel version of Bioconductor and we tried
  numerous times to reach the maintainer. If you know the maintainer we
  encourage you to reach out to them to fix the package.  

  Lori Shepherd
  Bioconductor Core Team

This bug should remove r-bioc-destiny from testing to enable the
transition of all other r-bioc-* packages.

Kind regards

Andreas.

[1] https://lists.debian.org/debian-r/2021/09/msg00065.html
https://lists.debian.org/debian-r/2021/09/msg00067.html

-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 
'experimental'), (1, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages r-bioc-destiny depends on:
ii  libc62.31-13
ii  libgcc-s110.2.1-6
ii  libstdc++6   10.2.1-6
pn  r-api-bioc-3.12  
ii  r-base-core [r-api-4.0]  4.1.1-2
pn  r-bioc-biobase   
pn  r-bioc-biocgenerics  
pn  r-bioc-pcamethods
pn  r-bioc-singlecellexperiment  
pn  r-bioc-summarizedexperiment  
pn  r-cran-ggplot.multistats 
ii  r-cran-ggplot2   3.3.3+dfsg-1
pn  r-cran-ggthemes  
pn  r-cran-irlba 
pn  r-cran-knn.covertree 
ii  r-cran-matrix1.3-2-1
pn  r-cran-proxy 
ii  r-cran-rcpp  1.0.6-1
pn  r-cran-rcppeigen 
pn  r-cran-rcpphnsw  
pn  r-cran-rspectra  
ii  r-cran-scales1.1.1-1
pn  r-cran-scatterplot3d 
pn  r-cran-smoother  
ii  r-cran-tidyr 1.1.2-1
ii  r-cran-tidyselect1.1.0+dfsg-1
pn  r-cran-vim   

Versions of packages r-bioc-destiny recommends:
ii  r-cran-testthat  3.0.1-1

Versions of packages r-bioc-destiny suggests:
ii  r-cran-fnn 1.1.3-2
pn  r-cran-igraph  
--- End Message ---
--- Begin Message ---

-- 
http://fam-tille.de--- End Message ---

Bug#984158: grfcodec: diff for NMU version 6.0.6-5.1

[Matthijs Kooijman]

Hi Adrian,

It took a while longer than anticipated, because of a problem with last
month's keyring update, but that has now been resolved, so my uploads
have come through.

> packages without valid signature are usually silently dropped,
> expect that you might have to reupload.
Maybe packages with an expired signature are handled differently, since
my packages were processed without reupload now.

Thanks again for your interest and time!

Gr.

Matthijs


signature.asc
Description: PGP signature