Bug#1039968: marked as done (python3-tvdb-api: Incompatible with requests-cache version in repositories)

[Debian Bug Tracking System]

Your message dated Tue, 08 Aug 2023 05:51:56 +
with message-id 
and subject line Bug#1039968: fixed in tvdb-api 3.1-3
has caused the Debian Bug report #1039968,
regarding python3-tvdb-api: Incompatible with requests-cache version in 
repositories
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.)


-- 
1039968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-tvdb-api
Version: 3.1-2
Severity: serious
Tags: upstream newcomer
Justification: Policy 2.2.1

Dear Maintainer,

This bug renders the package tvnamer completely useless. It always fails with
this error when trying to connect remotely to TVDB:

Traceback (most recent call last):
  File "/usr/bin/tvnamer", line 6, in 
tvnamer.main.main()
  File "/usr/share/tvnamer/main.py", line 474, in main
tvnamer(paths = sorted(args))
  File "/usr/share/tvnamer/main.py", line 370, in tvnamer
processFile(tvdb_instance, episode)
  File "/usr/share/tvnamer/main.py", line 175, in processFile
episode.populateFromTvdb(tvdb_instance, force_name=Config['force_name'],
series_id=Config['series_id'])
  File "/usr/share/tvnamer/utils.py", line 641, in populateFromTvdb
show = tvdb_instance[force_name or self.seriesname]
   ~^^^
  File "/usr/lib/python3/dist-packages/tvdb_api.py", line 1152, in __getitem__
sid = self._nameToSid(key)
  
  File "/usr/lib/python3/dist-packages/tvdb_api.py", line 1136, in _nameToSid
selected_series = self._getSeries(name)
  ^
  File "/usr/lib/python3/dist-packages/tvdb_api.py", line 935, in _getSeries
all_series = self.search(series)
 ^^^
  File "/usr/lib/python3/dist-packages/tvdb_api.py", line 914, in search
series_resp = self._getetsrc(self.config['url_getSeries'] % (series))
  ^^^
  File "/usr/lib/python3/dist-packages/tvdb_api.py", line 874, in _getetsrc
src = self._loadUrl(url, language=language)
  ^
  File "/usr/lib/python3/dist-packages/tvdb_api.py", line 811, in _loadUrl
self.authorize()
  File "/usr/lib/python3/dist-packages/tvdb_api.py", line 859, in authorize
r = self.session.post(
^^
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 635, in post
return self.request("POST", url, data=data, json=json, **kwargs)
   ^
  File "/usr/lib/python3/dist-packages/requests_cache/session.py", line 115, in
request
return super().request(method, url, *args, **kwargs)
   ^
  File "/usr/lib/python3/dist-packages/requests/sessions.py", line 587, in
request
resp = self.send(prep, **send_kwargs)
   ^^
  File "/usr/lib/python3/dist-packages/requests_cache/session.py", line 127, in
send
cache_key = self.cache.create_key(request, **kwargs)

TypeError: create_key() got an unexpected keyword argument 'timeout'

This is due to changes in the API to requests-cache. It seems upstream isn't
updating the code anymore but I've created a PR anyway:
https://github.com/dbr/tvdb_api/pull/105

I've tried these changes in Debian Boookworm and they fix this issue and others
related to changes in requests-cache.

I hope someone can patch these changes into the Debian sources.

Thanks.
Cheers.


-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-9-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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-tvdb-api depends on:
ii  python3 3.11.2-1+b1
ii  python3-requests2.28.1+dfsg-1
ii  python3-requests-cache  0.9.8-1

python3-tvdb-api recommends no packages.

python3-tvdb-api suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: tvdb-api
Source-Version: 3.1-3
Done: Sandro Tosi 

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

A 

Bug#1039968: marked as pending in tvdb-api

[Sandro Tosi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/tvdb-api/-/commit/e8880ab208a52e0204ff24297796b6b108bd5b07


add patch to make this module compatible with recent requests_cache releaess;  
Closes: #1039968


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1039968

Processed: Bug#1039968 marked as pending in tvdb-api

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1039968 [python3-tvdb-api] python3-tvdb-api: Incompatible with 
requests-cache version in repositories
Added tag(s) pending.

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

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

[Debian Bug Tracking System]

Your message dated Tue, 08 Aug 2023 05:33:57 +
with message-id 
and subject line Bug#999001: fixed in xdiskusage 1.48-11
has caused the Debian Bug report #999001,
regarding xdiskusage: 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.)


-- 
999001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xdiskusage
Version: 1.48-10.1
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: xdiskusage
Source-Version: 1.48-11
Done: Boyuan Yang 

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated xdiskusage 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, 08 Aug 2023 01:15:18 -0400
Source: xdiskusage
Architecture: source
Version: 1.48-11
Distribution: unstable
Urgency: medium
Maintainer: Boyuan Yang 
Changed-By: Boyuan Yang 
Closes: 965891 999001 1041420
Changes:
 xdiskusage (1.48-11) unstable; urgency=medium
 .
   * Take over package maintenance via ITS process. (Closes: #1041420)
   * debian/control:
 + Use debhelper compat v13. (Closes: #965891)
 + Bump Standards-Version to 4.6.2.
 + Add Vcs-* fields.
   * debian/rules:
 + Migrate to dh. (Closes: #999001)
   * debian/clean: Manually add files to clean.
   * debian/patches/11_patch_makefile_use_destdir.patch: Add patch
 so that installation recognizes DESTDIR variable.
Checksums-Sha1:
 7b4e3d6ba6ab80b33ae28522c1c26ab57f2d5fe8 1911 xdiskusage_1.48-11.dsc
 8069d521beec27004baa1f534559cdc7ff99e27f 37332 xdiskusage_1.48.orig.tar.gz
 b9f9b3d199e16987e3592487273a16195381d5f4 8560 xdiskusage_1.48-11.debian.tar.xz
 3af0eb3063b65770a8eb599b4e83ddf8b2128d34 8029 
xdiskusage_1.48-11_amd64.buildinfo
Checksums-Sha256:
 d5705f7735af0c95583e67d4424bd9619b9ebb1695cdab5d3995c57ac5eca8a8 1911 
xdiskusage_1.48-11.dsc
 7842aa42510bf52c367164d44a977915ad9f070864d5175157738f8d6894274b 37332 
xdiskusage_1.48.orig.tar.gz
 77595c452d323629857789b6df035626399cbf986a52b3fda5ce8a8290f596c5 8560 
xdiskusage_1.48-11.debian.tar.xz
 5a21a94b5b8886a3b312c6696b420048fa9a856ad6856d649584c163088f091a 8029 
xdiskusage_1.48-11_amd64.buildinfo
Files:
 28057e0a7676bc9f4110ab97a602bea5 1911 x11 optional xdiskusage_1.48-11.dsc
 a902aa9d73761ade98256c3cd5c1f533 37332 x11 optional xdiskusage_1.48.orig.tar.gz
 192291f37abc4757a9e138e397eb518f 8560 x11 optional 
xdiskusage_1.48-11.debian.tar.xz
 e5c187f8b6186e350edb3d05453302fc 8029 x11 optional 
xdiskusage_1.48-11_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmTR0GwACgkQwpPntGGC
Ws5wFA/8DbTcW2fErRqvbwPX+pkyRpyE9acNWUs+ZGCCCyxHWoC1jYpdxG41Us0q
+ZfEhjPOl7agRAB2vZPFVVNJwIw7LWSDIL184nHvrGGux64TbKsnm+v6J7kNboGY
s00deWCtyxLZe0nj5zr7bLdqR/TGqhM3vS7fki610ReeiPQJ99G185DcOgGhIl4j
woRCgr/CxHe9Bk7NrSrcNxiLaud1fkT89DvpdKwW4TAxAzXIuV/LpOV2AnlAUZ0P
t2nk3jWJZVAiiXGh3oKiMvFv7TJUyux6Ddza+F/0Vq9oRHlZJg+j5zwmMN2JvG5K
koaJ9MMwwVXBuQSzPYDNYhp62enT8u8zlMfs93ug2y0ocW6w3PaMllsri0HZLyds
zWh++3wL1ies1XsAys64BP0ZiSAPK120wZ2WO4BYCqzwC3PUFHZkH6sxIDxUb0Oe
+eEkn3aqZCCDTDS1G4Ddqala+VZ0Z5+Gwa87ixA6yZcRh/cojYDvThw/fFwlcxRL

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

[Debian Bug Tracking System]

Your message dated Tue, 08 Aug 2023 05:33:57 +
with message-id 
and subject line Bug#965891: fixed in xdiskusage 1.48-11
has caused the Debian Bug report #965891,
regarding xdiskusage: 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.)


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

Hi,

The package xdiskusage 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: xdiskusage
Source-Version: 1.48-11
Done: Boyuan Yang 

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated xdiskusage 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, 08 Aug 2023 01:15:18 -0400
Source: xdiskusage
Architecture: source
Version: 1.48-11
Distribution: unstable
Urgency: medium
Maintainer: Boyuan Yang 
Changed-By: Boyuan Yang 
Closes: 965891 999001 1041420
Changes:
 xdiskusage (1.48-11) unstable; urgency=medium
 .
   * Take over package maintenance via ITS process. (Closes: #1041420)
   * debian/control:
 + Use debhelper compat v13. (Closes: #965891)
 + Bump Standards-Version to 4.6.2.
 + Add Vcs-* fields.
   * debian/rules:
 + Migrate to dh. (Closes: #999001)
   * debian/clean: Manually add files to clean.
   * debian/patches/11_patch_makefile_use_destdir.patch: Add patch
 so that installation recognizes DESTDIR variable.
Checksums-Sha1:
 7b4e3d6ba6ab80b33ae28522c1c26ab57f2d5fe8 1911 xdiskusage_1.48-11.dsc
 8069d521beec27004baa1f534559cdc7ff99e27f 37332 xdiskusage_1.48.orig.tar.gz
 b9f9b3d199e16987e3592487273a16195381d5f4 8560 xdiskusage_1.48-11.debian.tar.xz
 3af0eb3063b65770a8eb599b4e83ddf8b2128d34 8029 
xdiskusage_1.48-11_amd64.buildinfo
Checksums-Sha256:
 d5705f7735af0c95583e67d4424bd9619b9ebb1695cdab5d3995c57ac5eca8a8 1911 
xdiskusage_1.48-11.dsc
 7842aa42510bf52c367164d44a977915ad9f070864d5175157738f8d6894274b 37332 
xdiskusage_1.48.orig.tar.gz
 77595c452d323629857789b6df035626399cbf986a52b3fda5ce8a8290f596c5 8560 
xdiskusage_1.48-11.debian.tar.xz
 5a21a94b5b8886a3b312c6696b420048fa9a856ad6856d649584c163088f091a 8029 
xdiskusage_1.48-11_amd64.buildinfo
Files:
 28057e0a7676bc9f4110ab97a602bea5 1911 x11 optional xdiskusage_1.48-11.dsc
 a902aa9d73761ade98256c3cd5c1f533 37332 x11 optional xdiskusage_1.48.orig.tar.gz
 192291f37abc4757a9e138e397eb518f 8560 x11 optional 
xdiskusage_1.48-11.debian.tar.xz
 e5c187f8b6186e350edb3d05453302fc 8029 x11 optional 
xdiskusage_1.48-11_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmTR0GwACgkQwpPntGGC
Ws5wFA/8DbTcW2fErRqvbwPX+pkyRpyE9acNWUs+ZGCCCyxHWoC1jYpdxG41Us0q
+ZfEhjPOl7agRAB2vZPFVVNJwIw7LWSDIL184nHvrGGux64TbKsnm+v6J7kNboGY
s00deWCtyxLZe0nj5zr7bLdqR/TGqhM3vS7fki610ReeiPQJ99G185DcOgGhIl4j

Bug#1000085: marked as done (dnshistory: depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Your message dated Tue, 08 Aug 2023 04:08:04 +
with message-id 
and subject line Bug#1043150: Removed package(s) from unstable
has caused the Debian Bug report #185,
regarding dnshistory: depends on obsolete pcre3 library
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.)


-- 
185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dnshistory
Severity: important
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---
Version: 1.3-3+rm

Dear submitter,

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

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

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

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

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

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

Bug#957230: marked as done (freebsd-buildutils: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Tue, 08 Aug 2023 02:48:56 +
with message-id 
and subject line Bug#957230: fixed in freebsd-buildutils 10.3~svn296373-7.1
has caused the Debian Bug report #957230,
regarding freebsd-buildutils: ftbfs with GCC-10
to be marked as done.

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

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


-- 
957230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:freebsd-buildutils
Version: 10.3~svn296373-7
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/freebsd-buildutils_10.3~svn296373-7_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_GNU_SOURCE -pipe 
-Wall -DMACHINE_ARCH='"amd64"' -DMACHINE_MULTIARCH='"x86_64-linux-gnu"' 
-I/<>/build-tree/src/sys -isystem /usr/include/freebsd -fPIC 
-Wdate-time -D_FORTIFY_SOURCE=2-std=gnu99  -fstack-protector   -c file2c.c 
-o file2c.o
--- file2c.1.gz ---
gzip -cn -9 file2c.1 > file2c.1.gz
--- file2c ---
x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_GNU_SOURCE -pipe 
-Wall -DMACHINE_ARCH='"amd64"' -DMACHINE_MULTIARCH='"x86_64-linux-gnu"' 
-I/<>/build-tree/src/sys -isystem /usr/include/freebsd -fPIC 
-Wdate-time -D_FORTIFY_SOURCE=2-std=gnu99  -fstack-protector   -Wl,-z,relro 
-Wl,-z,now -o file2c file2c.o -lbsd
CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -D_GNU_SOURCE -pipe -Wall 
-DMACHINE_ARCH='\"amd64\"' -DMACHINE_MULTIARCH='\"x86_64-linux-gnu\"' 
-I/<>/build-tree/src/sys -isystem /usr/include/freebsd -fPIC 
-Wdate-time -D_FORTIFY_SOURCE=2 " MAKEFLAGS=-j4 NO_WERROR=1 NOGCCERROR=1 
NOSHARED=NO NO_SHARED=NO NO_PROFILE=1 bmake CC=x86_64-linux-gnu-gcc -m 
/<>/src/share/mk  -C build-tree/src/usr.bin/brandelf
--- objwarn ---
Warning: Object directory not changed from original 
/<>/build-tree/src/usr.bin/brandelf
--- brandelf.o ---
--- brandelf.1.gz ---
--- brandelf.o ---
x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_GNU_SOURCE -pipe 
-Wall -DMACHINE_ARCH='"amd64"' -DMACHINE_MULTIARCH='"x86_64-linux-gnu"' 
-I/<>/build-tree/src/sys -isystem /usr/include/freebsd -fPIC 
-Wdate-time -D_FORTIFY_SOURCE=2-std=gnu99  -fstack-protector   -c 
brandelf.c -o brandelf.o
--- brandelf.1.gz ---
gzip -cn -9 brandelf.1 > brandelf.1.gz
--- brandelf ---
x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -D_GNU_SOURCE -pipe 
-Wall -DMACHINE_ARCH='"amd64"' -DMACHINE_MULTIARCH='"x86_64-linux-gnu"' 
-I/<>/build-tree/src/sys -isystem /usr/include/freebsd -fPIC 
-Wdate-time -D_FORTIFY_SOURCE=2-std=gnu99  -fstack-protector   -Wl,-z,relro 
-Wl,-z,now -o brandelf brandelf.o -lbsd
CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -D_GNU_SOURCE -pipe -Wall 
-DMACHINE_ARCH='\"amd64\"' -DMACHINE_MULTIARCH='\"x86_64-linux-gnu\"' 
-I/<>/build-tree/src/sys -isystem /usr/include/freebsd -fPIC 
-Wdate-time -D_FORTIFY_SOURCE=2 " MAKEFLAGS=-j4 NO_WERROR=1 NOGCCERROR=1 
NOSHARED=NO NO_SHARED=NO NO_PROFILE=1 bmake CC=x86_64-linux-gnu-gcc -m 
/<>/src/share/mk  -C build-tree/src/sys/dev/aic7xxx/aicasm
--- objwarn ---
Warning: Object directory not changed from original 
/<>/build-tree/src/sys/dev/aic7xxx/aicasm
--- 

Bug#1043065: marked as done (gr-limesdr: autopkgtest regression with gnuradio 3.10.7)

[Debian Bug Tracking System]

Your message dated Tue, 08 Aug 2023 02:49:04 +
with message-id 
and subject line Bug#1043065: fixed in gr-limesdr 3.0.1.10.69-3
has caused the Debian Bug report #1043065,
regarding gr-limesdr: autopkgtest regression with gnuradio 3.10.7
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.)


-- 
1043065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gr-limesdr
Version: 3.0.1-5
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gr-limesdr/36447655/log.gz

117s Testing python3.11 ...
117s Traceback (most recent call last):
117s   File "", line 1, in 
117s   File "/usr/lib/python3/dist-packages/limesdr/__init__.py", line 18, in 

117s from .limesdr_python import *
117s ImportError: generic_type: type "sink" referenced unknown base type 
"gr::block"
118s autopkgtest [17:12:35]: test python: ---]
118s python   FAIL non-zero exit status 1

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: gr-limesdr
Source-Version: 3.0.1.10.69-3
Done: A. Maitland Bottoms 

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated gr-limesdr 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Aug 2023 21:52:51 -0400
Source: gr-limesdr
Architecture: source
Version: 3.0.1.10.69-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: A. Maitland Bottoms 
Closes: 1043065
Changes:
 gr-limesdr (3.0.1.10.69-3) unstable; urgency=medium
 .
   * upload to unstable
   * autopkgtest superficial tests passing again (Closes: #1043065)
Checksums-Sha1:
 44df23086c791011f40564d7afe87da910398b36 2394 gr-limesdr_3.0.1.10.69-3.dsc
 d02ebda6791f0123a2b5f28de00e831c6ba42699 5292 
gr-limesdr_3.0.1.10.69-3.debian.tar.xz
 733fede429d2bd4e4a5fa7db71223bb82f6f72d7 19723 
gr-limesdr_3.0.1.10.69-3_amd64.buildinfo
Checksums-Sha256:
 4b163b65f3688eb57d80821f2a2aeb4a7c26fffea8adc59f10b0de8ec7dd2261 2394 
gr-limesdr_3.0.1.10.69-3.dsc
 319a53ad6115180e685877447db98d5b60c2ecca0516751868a9b5ba53b5117c 5292 
gr-limesdr_3.0.1.10.69-3.debian.tar.xz
 9acf09959a7ecc067cf88be75ed44c0d4bb6eb7029044bb952a97c8978beab02 19723 
gr-limesdr_3.0.1.10.69-3_amd64.buildinfo
Files:
 3f23b62372b9d224b013241c01116ca5 2394 hamradio optional 
gr-limesdr_3.0.1.10.69-3.dsc
 e72ca069bdbb2d9182056c47fb4cb2d0 5292 hamradio optional 
gr-limesdr_3.0.1.10.69-3.debian.tar.xz
 3ef51527877baa51713a69b148e87f70 19723 hamradio optional 
gr-limesdr_3.0.1.10.69-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAmTRolYACgkQUEHxiR9E
4JBBXA/8D27WKDALOjT24jpPuK19Qb05r+1HAhh3SZblCXPR7nKnl/BSQDukZ/XN
8jFgBo9nJvnDIP0CLS53pSgY0YEzX3arrhzVfONkyJmd/VNHi9I2Yiz4vUQFaAAY
pQI3cm4zNup8a+LDDdF0vbAIHvwBL98hVAakf7Ng2RA6GzhqaKkPcoqwlUxTleWe
qufwy3pznrNTKcTrzQGlUw+6dEjsV8hGqFz9wVj2afk4H7/8aCLP//nnkuSpNxM0
Ft8Pomsq9+u6SIUwGYX7fBVddUV5gbZ1QhTvQYV/CLYnpDfPjWdc8Qgz2CzE1IHv
nPKDORZk96m4pjRFXWI5VHO/MGu1h7lJNYNcLoc2nO98OSSLDdwxwFiafxguQx/R
CbMcKCdweiRb7xgp25SOGM9+O0aZbm18QDolOPOVcn8/Whv6vsFp0j0/zSlLhZh5
L7FEgFDrLn3CW0SwvAOPWi8td/nJe6B91dw0QYUh1Wff/X/OzSPpXmZhGyIVpSLw
9UuA8bjbXxvg7AtHg2pEhJ3Zo22SoRDfxugUa7KACuosO44plZ1MDtrcVBK0523i
ugo3HFHjlBJVkiLWwuBMl0VDs/VRXlPjpOVqK44N4/XM5/4dxXbQs20KnnnIVSm8
3HzptQu04bE7MJ9cIU+wloNzVkqQl87krmQFpxdVIXsSeqRMWMw=
=SZON
-END PGP SIGNATURE End Message ---

Processed: block 1043255 with 1042869 1042965 1043002

[Debian Bug Tracking System]

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

> block 1043255 with 1042869 1042965 1043002
Bug #1043255 [ftp.debian.org] RM: pep517 -- ROM; Obsolete, replaced by 
python-pyproject-hooks
1043255 was not blocked by any bugs.
1043255 was not blocking any bugs.
Added blocking bug(s) of 1043255: 1043002, 1042869, and 1042965
> thanks
Stopping processing here.

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

Processed: severity of 1043002 is serious

[Debian Bug Tracking System]

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

> severity 1043002 serious
Bug #1043002 [src:pdm] pdm: Please replace python3-pep517 with 
python3-pyproject-hooks in Depends/Build-Depends
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1042965 is serious

[Debian Bug Tracking System]

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

> severity 1042965 serious
Bug #1042965 [src:py7zr] py7zr: Remove unneeded build-depends on deprecate 
pep517
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 1042869 is serious

[Debian Bug Tracking System]

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

> severity 1042869 serious
Bug #1042869 [src:sniffles] sniffles: Please update to newer version without 
python3-pep517 requirement
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1039710: debian-installer: Grub installation fails and /var/log/syslog is empty

[Philip Hands]

Steve McIntyre  writes:

> On Wed, Jul 12, 2023 at 11:15:57AM +0200, Cyril Brulebois wrote:
>>Hi Michael,
>>
>>Cyril Brulebois  (2023-06-28):
>>> Control: reassign -1 busybox-udeb 1:1.36.1-3
>>
>>[…]
>>
>>> With a local build, confirmed -3 is buggy, and that reverting only
>>> busybox-udeb to -1 is sufficient to restore syslog support in the
>>> installer.
>>> 
>>> Reassigning there; the GRUB thing can be filed separately once we have
>>> actual information via syslog.
>>
>>A fix would be appreciated, we've got reports piling up about things we
>>have no logs for.
>
> After weeks with this breakage, I've just uploaded a minimal NMU to
> fix it, reverting the syslog changes since -1. I've buit and tested
> successfully locally.

Thanks -- and I agree, it works :-)

  https://openqa.debian.net/tests/178534/logfile?filename=DI_syslog.txt

As it happens, over the weekend it occurred to me that I might be able
to pave the way to a fix for this bug by coming up with a test for the
failure.

Awkwardly, syslogd wants to open /dev/log and bails out if it's already
in use, so I resorted to (the somewhat disgusting hack of) using podman:

   
https://salsa.debian.org/philh/busybox/-/commit/2697f7cce81d1a70de202a30e7062dc9f64a94b1

At least it allows syslogd to run well enough to succeed or fail
similarly to the behaviour seen in the bug.

Here it is going wrong with the -3 code:

  https://salsa.debian.org/philh/busybox/-/jobs/4523822#L3963
  (lines 3969-3975, with the last line showing the entire syslog)

and here is an example of it going right:

  https://salsa.debian.org/philh/busybox/-/jobs/4523808#L3668

  Line 3668 here, saying "PASS: syslogd-works" indicates that we
  succeeded in grepping the test string in /var/log/syslog

The difference between these two is simply disabling
CONFIG_FEATURE_REMOTE_LOG, as seen here:

  
https://salsa.debian.org/philh/busybox/-/commit/89c253f75690dd41487b6fd6f9356a1e890a6ac2

I'm not proposing that as a fix, but it does seem to indicate where the
problem may be located. I'm afraid I've failed to work out what's
actually going wrong here (my C's pretty rusty).

BTW At one point I thought I'd narrowed it down to the while loop here:

  
https://salsa.debian.org/philh/busybox/-/commit/328fdfbe43cd8d9e4425c3ee1c68aadfa44ee434

but if that did work, it does no longer. Either I was mistaken about it
having worked earlier (I'm at least 80% sure that's not the case) or
something non-deterministic is going on ... which makes me wonder if the
underlying cause might be something to do with using uninitialised data
somewhere.

Hopefully this will be of some use to those more familiar with the code.

Cheers, Phil.
-- 
Philip Hands -- https://hands.com/~phil


signature.asc
Description: PGP signature

Bug#1043173: marked as done (wlgreet: Fails to start sway due to incorrect configuration)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2023 23:49:12 +0200
with message-id <2694225.mvXUDI8C0e@bagend>
and subject line Re: Bug closing
has caused the Debian Bug report #1043173,
regarding wlgreet: Fails to start sway due to incorrect configuration
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.)


-- 
1043173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043173
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wlgreet
Version: 0.4.1-1
Severity: grave
Tags: patch
Justification: renders package unusable

If you switch greetd's config to start wlgreet, you get presented a
screen to input your username and the next screen is for the password.
When you then press enter sway is supposed to start and it appears that
'something' is happening, but then you get thrown back to wlgreet's
login screen. It appears that the configuration is incorrect. After I
fixed that, I did login and a sway session (?) was started.

I'm preparing a MR on Salsa and once I have a bug number for this bug,
I'll submit it.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 6.4.0-1-arm64 (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 wlgreet depends on:
ii  libc6  2.37-6
ii  libgcc-s1  13.2.0-1
ii  sway   1.8.1-2

wlgreet recommends no packages.

wlgreet suggests no packages.

-- Configuration Files:
/etc/greetd/sway-config changed:
exec "/usr/sbin/wlgreet --command sway; swaymsg exit"
bindsym Mod4+shift+e exec swaynag \
-t warning \
-m 'What do you want to do?' \
-b 'Poweroff' 'systemctl poweroff -i' \
-b 'Reboot' 'systemctl reboot -i'
output * bg 
/usr/share/desktop-base/active-theme/lockscreen/contents/images/3840x2160.svg 
fill
include /etc/sway/config.d/*
include /etc/greetd/sway-config.d/*

/etc/greetd/wlgreet.tom [Errno 2] No such file or directory: 
'/etc/greetd/wlgreet.tom'

-- no debconf information
--- End Message ---
--- Begin Message ---
Probably PEBKAC

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

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

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2023 21:18:59 +
with message-id 
and subject line Bug#999317: fixed in itop 0.1-4.1
has caused the Debian Bug report #999317,
regarding itop: 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.)


-- 
999317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: itop
Version: 0.1-4
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: itop
Source-Version: 0.1-4.1
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
itop, 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.
Bastian Germann  (supplier of updated itop 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, 07 Aug 2023 22:48:00 +0200
Source: itop
Architecture: source
Version: 0.1-4.1
Distribution: unstable
Urgency: medium
Maintainer: Jose Parrella 
Changed-By: Bastian Germann 
Closes: 965601 999317
Changes:
 itop (0.1-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove unavailable Homepage.
   * Update debhelper to compat 10. (Closes: #965601)
   * Split build target into build-{indep,arch}. (Closes: #999317)
   * Convert to source format 3.0.
Checksums-Sha1:
 25b81e67442dfc26d8b52db407fc5a1268e3037a 1472 itop_0.1-4.1.dsc
 a971d3e1666aec2be9f31e4d44584edf0deafa99 3020 itop_0.1-4.1.debian.tar.xz
 9720cb4139755a2f546ea2d3ca16d8172418ad0f 5584 itop_0.1-4.1_source.buildinfo
Checksums-Sha256:
 b133680de887804e6820c5e7c20da802bc12a9f20f1aa0cdd0f6625a49123112 1472 
itop_0.1-4.1.dsc
 fd95caec0decea9725f2938500a9410c06070b23788f93e6475d20acd71f3212 3020 
itop_0.1-4.1.debian.tar.xz
 c3c49376211bc87649890e9076da2063d6c8402b6779b7ec17df6ed85caf041b 5584 
itop_0.1-4.1_source.buildinfo
Files:
 ea2ef72c4684c38691a54fd6a3710975 1472 admin optional itop_0.1-4.1.dsc
 6c2767865d56d7de0d85b4ab9111e5d1 3020 admin optional itop_0.1-4.1.debian.tar.xz
 74ac59790f4cc0672d1c14882f17dc0a 5584 admin optional 
itop_0.1-4.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTRXBMQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFN2PDACymOSghjl8w9Z2+mJgZEX+28TewATJ+DoF
3UQDcxFIsW5aIECaTrfY85nk8eHO7bh/WmXN+mSIdWF4a6cdInrF4Wsi8xkM9py9
1UyFuWrv6FQNGyfxBWhpq77hkT/JsaBL1rNX4fQXofEo1e7IfFwBOFn0Qq4qqv1R
KDVOWy5E4pijlQasbQzolQ6ESdxCsRipC8SZCc6rcioXZb7s1IH33AQVPA9AAsKy
qDpZD27f+sD9hSEJaOrOVwWwjEWdChnE9/3pjLXmSZsDSXJiYaIf3NDDn9D1ZDOT
R1mIKlVm/SJmWqbXfVYr2B3pWcm4XapHA1QKpTBcvImonTFtGHz64iJy6COhS6sD
5+/HIfJOWv/wnKcdXX3YWJRJfvHfG+OeJNn157R7l656Yz3M4Qd/TGlv67e2vB8r
uGOdcMCZxpkHYzt9qeXi3SbMcWNo8JUhlvbHXCgAg3J6HLWhTHEcf3QmwguecEMt
flYeRyD2y6arpFPha7iGvzM04WVI3x0=
=Z6Ae
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2023 21:18:59 +
with message-id 
and subject line Bug#965601: fixed in itop 0.1-4.1
has caused the Debian Bug report #965601,
regarding itop: 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.)


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

Hi,

The package itop 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: itop
Source-Version: 0.1-4.1
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
itop, 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.
Bastian Germann  (supplier of updated itop 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, 07 Aug 2023 22:48:00 +0200
Source: itop
Architecture: source
Version: 0.1-4.1
Distribution: unstable
Urgency: medium
Maintainer: Jose Parrella 
Changed-By: Bastian Germann 
Closes: 965601 999317
Changes:
 itop (0.1-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove unavailable Homepage.
   * Update debhelper to compat 10. (Closes: #965601)
   * Split build target into build-{indep,arch}. (Closes: #999317)
   * Convert to source format 3.0.
Checksums-Sha1:
 25b81e67442dfc26d8b52db407fc5a1268e3037a 1472 itop_0.1-4.1.dsc
 a971d3e1666aec2be9f31e4d44584edf0deafa99 3020 itop_0.1-4.1.debian.tar.xz
 9720cb4139755a2f546ea2d3ca16d8172418ad0f 5584 itop_0.1-4.1_source.buildinfo
Checksums-Sha256:
 b133680de887804e6820c5e7c20da802bc12a9f20f1aa0cdd0f6625a49123112 1472 
itop_0.1-4.1.dsc
 fd95caec0decea9725f2938500a9410c06070b23788f93e6475d20acd71f3212 3020 
itop_0.1-4.1.debian.tar.xz
 c3c49376211bc87649890e9076da2063d6c8402b6779b7ec17df6ed85caf041b 5584 
itop_0.1-4.1_source.buildinfo
Files:
 ea2ef72c4684c38691a54fd6a3710975 1472 admin optional itop_0.1-4.1.dsc
 6c2767865d56d7de0d85b4ab9111e5d1 3020 admin optional itop_0.1-4.1.debian.tar.xz
 74ac59790f4cc0672d1c14882f17dc0a 5584 admin optional 
itop_0.1-4.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTRXBMQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFN2PDACymOSghjl8w9Z2+mJgZEX+28TewATJ+DoF
3UQDcxFIsW5aIECaTrfY85nk8eHO7bh/WmXN+mSIdWF4a6cdInrF4Wsi8xkM9py9
1UyFuWrv6FQNGyfxBWhpq77hkT/JsaBL1rNX4fQXofEo1e7IfFwBOFn0Qq4qqv1R
KDVOWy5E4pijlQasbQzolQ6ESdxCsRipC8SZCc6rcioXZb7s1IH33AQVPA9AAsKy
qDpZD27f+sD9hSEJaOrOVwWwjEWdChnE9/3pjLXmSZsDSXJiYaIf3NDDn9D1ZDOT
R1mIKlVm/SJmWqbXfVYr2B3pWcm4XapHA1QKpTBcvImonTFtGHz64iJy6COhS6sD
5+/HIfJOWv/wnKcdXX3YWJRJfvHfG+OeJNn157R7l656Yz3M4Qd/TGlv67e2vB8r
uGOdcMCZxpkHYzt9qeXi3SbMcWNo8JUhlvbHXCgAg3J6HLWhTHEcf3QmwguecEMt
flYeRyD2y6arpFPha7iGvzM04WVI3x0=
=Z6Ae
-END PGP SIGNATURE End Message ---

Bug#965601: itop: Removal of obsolete debhelper compat 5 and 6 in bookworm

[Bastian Germann]

I am uploading a NMU to fix this. The debdiff is attached.diff -Nru itop-0.1/debian/changelog itop-0.1/debian/changelog
--- itop-0.1/debian/changelog   2023-08-07 23:04:36.0 +0200
+++ itop-0.1/debian/changelog   2023-08-07 22:48:00.0 +0200
@@ -1,3 +1,13 @@
+itop (0.1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove unavailable Homepage.
+  * Update debhelper to compat 10. (Closes: #965601)
+  * Split build target into build-{indep,arch}. (Closes: #999317)
+  * Convert to source format 3.0.
+
+ -- Bastian Germann   Mon, 07 Aug 2023 22:48:00 +0200
+
 itop (0.1-4) unstable; urgency=low
 
   * Removed debian/docs, hello Ubuntu! (Closes: #489956)
diff -Nru itop-0.1/debian/compat itop-0.1/debian/compat
--- itop-0.1/debian/compat  2023-08-07 23:04:36.0 +0200
+++ itop-0.1/debian/compat  1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-5
diff -Nru itop-0.1/debian/control itop-0.1/debian/control
--- itop-0.1/debian/control 2023-08-07 23:04:36.0 +0200
+++ itop-0.1/debian/control 2023-08-07 22:48:00.0 +0200
@@ -1,10 +1,9 @@
 Source: itop
 Section: admin
-Priority: extra
+Priority: optional
 Maintainer: Jose Parrella 
-Build-Depends: debhelper (>= 5)
+Build-Depends: debhelper-compat (= 10)
 Standards-Version: 3.8.0
-Homepage: http://www.hunz.org/
 
 Package: itop
 Architecture: any
diff -Nru itop-0.1/debian/patches/debian.patch 
itop-0.1/debian/patches/debian.patch
--- itop-0.1/debian/patches/debian.patch1970-01-01 01:00:00.0 
+0100
+++ itop-0.1/debian/patches/debian.patch2023-08-07 22:48:00.0 
+0200
@@ -0,0 +1,17 @@
+Description: Add a Makefile
+---
+--- /dev/null
 itop-0.1/Makefile
+@@ -0,0 +1,12 @@
++CC=gcc
++
++all: itop
++
++itop:
++  (cd src/ ; make)
++
++clean:
++  rm -f src/itop src/*.o src/*~
++
++install: itop
++  cp src/itop $(DESTDIR)/usr/bin
diff -Nru itop-0.1/debian/patches/max_ints.patch 
itop-0.1/debian/patches/max_ints.patch
--- itop-0.1/debian/patches/max_ints.patch  1970-01-01 01:00:00.0 
+0100
+++ itop-0.1/debian/patches/max_ints.patch  2023-08-07 22:48:00.0 
+0200
@@ -0,0 +1,9 @@
+Description: Increased MAX_INTS from 256 to 1024, thanks David Futcher
+Bug-Debian: https://bugs.debian.org/449246
+---
+--- itop-0.1.orig/src/config.h
 itop-0.1/src/config.h
+@@ -1,2 +1,2 @@
+ #define MAX_NAME_LEN 18
+-#define MAX_INTS 256
++#define MAX_INTS 1024
diff -Nru itop-0.1/debian/patches/series itop-0.1/debian/patches/series
--- itop-0.1/debian/patches/series  1970-01-01 01:00:00.0 +0100
+++ itop-0.1/debian/patches/series  2023-08-07 22:48:00.0 +0200
@@ -0,0 +1,2 @@
+debian.patch
+max_ints.patch
diff -Nru itop-0.1/debian/rules itop-0.1/debian/rules
--- itop-0.1/debian/rules   2023-08-07 23:04:36.0 +0200
+++ itop-0.1/debian/rules   2023-08-07 22:48:00.0 +0200
@@ -13,9 +13,9 @@
dh_testdir
touch configure-stamp
 
-build: build-stamp
+build: build-indep build-arch
 
-build-stamp: configure-stamp 
+build-arch: configure-stamp 
dh_testdir
$(MAKE)
touch $@
@@ -34,9 +34,9 @@
dh_installdirs
$(MAKE) DESTDIR=$(CURDIR)/debian/itop install
 
-binary-indep: build install
+binary-indep: build-indep install
 
-binary-arch: build install
+binary-arch: build-arch install
dh_testdir
dh_testroot
dh_installchangelogs CHANGELOG
@@ -53,5 +53,6 @@
dh_md5sums
dh_builddeb
 
+build-indep:
 binary: binary-indep binary-arch
-.PHONY: build clean binary-indep binary-arch binary install configure
+.PHONY: build build-indep clean binary-indep binary-arch binary install 
configure
diff -Nru itop-0.1/debian/source/format itop-0.1/debian/source/format
--- itop-0.1/debian/source/format   1970-01-01 01:00:00.0 +0100
+++ itop-0.1/debian/source/format   2023-08-07 22:48:00.0 +0200
@@ -0,0 +1 @@
+3.0 (quilt)
diff -Nru itop-0.1/debian/watch itop-0.1/debian/watch
--- itop-0.1/debian/watch   2023-08-07 23:04:36.0 +0200
+++ itop-0.1/debian/watch   1970-01-01 01:00:00.0 +0100
@@ -1,3 +0,0 @@
-version=3
-http://www.hunz.org/ itop/itop-(.*)\.tar\.bz2
-
diff -Nru itop-0.1/Makefile itop-0.1/Makefile
--- itop-0.1/Makefile   2023-08-07 23:04:36.0 +0200
+++ itop-0.1/Makefile   1970-01-01 01:00:00.0 +0100
@@ -1,12 +0,0 @@
-CC=gcc
-
-all: itop
-
-itop:
-   (cd src/ ; make)
-
-clean:
-   rm -f src/itop src/*.o src/*~
-
-install: itop
-   cp src/itop $(DESTDIR)/usr/bin
diff -Nru itop-0.1/src/config.h itop-0.1/src/config.h
--- itop-0.1/src/config.h   2023-08-07 23:04:36.0 +0200
+++ itop-0.1/src/config.h   2001-08-26 15:55:05.0 +0200
@@ -1,2 +1,2 @@
 #define MAX_NAME_LEN 18
-#define MAX_INTS 1024
+#define MAX_INTS 256

Processed: libdbus-c++-glib-1-0/experimental: undeclared file conflict with libdbus-c++-1-0v5/unsable

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libdbus-c++-1-0v5
Bug #1043246 [libdbus-c++-glib-1-0] libdbus-c++-glib-1-0/experimental: 
undeclared file conflict with libdbus-c++-1-0v5/unsable
Added indication that 1043246 affects libdbus-c++-1-0v5

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

Bug#1043246: libdbus-c++-glib-1-0/experimental: undeclared file conflict with libdbus-c++-1-0v5/unsable

[Helmut Grohne]

Package: libdbus-c++-glib-1-0
Version: 0.9.0-13
Severity: serious
Control: affects -1 + libdbus-c++-1-0v5
User: debian...@lists.debian.org
Usertags: fileconflict

Both libdbus-c++-glib-1-0/experimental and libdbus-c++-1-0v5/unstable
contain the files /usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so.0 and
/usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so.0.0.0 without resolving
this conflict via Conflicts, Replaces or diversions. This may result in
an unpack error from dpkg and is a serious issue.

I guess that you meant to restructure the library and that these files
are supposed to be moved between packages. In this case, please add
Breaks and Replaces declarations for libdbus-c++-1-0v5 to
libdbus-c++-glib-1-0.

Helmut

Processed: libdbus-c++-ecore-1-0/experimental: undeclared file conflict with libdbus-c++-1-0v5/unsable

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libdbus-c++-1-0v5
Bug #1043245 [libdbus-c++-ecore-1-0] libdbus-c++-ecore-1-0/experimental: 
undeclared file conflict with libdbus-c++-1-0v5/unsable
Added indication that 1043245 affects libdbus-c++-1-0v5

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

Bug#1043245: libdbus-c++-ecore-1-0/experimental: undeclared file conflict with libdbus-c++-1-0v5/unsable

[Helmut Grohne]

Package: libdbus-c++-ecore-1-0
Version: 0.9.0-13
Severity: serious
Control: affects -1 + libdbus-c++-1-0v5
User: debian...@lists.debian.org
Usertags: fileconflict

Both libdbus-c++-ecore-1-0/experimental and libdbus-c++-1-0v5/unstable
contain the files /usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0 and
/usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1.so.0.0.0 without resolving
this conflict via Conflicts, Replaces or diversions. This may result in
an unpack error from dpkg and is a serious issue.

I guess that you meant to restructure the library and that these files
are supposed to be moved between packages. In this case, please add
Breaks and Replaces declarations for libdbus-c++-1-0v5 to
libdbus-c++-ecore-1-0.

Helmut

Bug#1043244: libflatbuffers-dev/experimental: undeclared file conflict with libflatbuffers2/trixie

[Helmut Grohne]

Package: libflatbuffers-dev
Version: 23.5.26+dfsg-1~exp0
Severity: serious
Control: affects -1 + libflatbuffers2
User: debian...@lists.debian.org
Usertags: fileconflict

libflatbuffers-dev/experimental and libflatbuffers2/trixie both contain
/usr/lib/x86_64-linux-gnu/pkgconfig/flatbuffers.pc. Since this conflict
is not addressed with Conflicts, Replaces or diversions, an unpack error
may result. This is a serious bug.

I guess that you meant to restructure the package and move the file from
libflatbuffers2 to libflatbuffers-dev. If this is accurate, please add
versioned Breaks and Replaces for libflatbuffers2 to libflatbuffers-dev.

Helmut

Processed: libflatbuffers-dev/experimental: undeclared file conflict with libflatbuffers2/trixie

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libflatbuffers2
Bug #1043244 [libflatbuffers-dev] libflatbuffers-dev/experimental: undeclared 
file conflict with libflatbuffers2/trixie
Added indication that 1043244 affects libflatbuffers2

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

Bug#1000021: marked as done (aircrack-ng: depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2023 19:49:41 +
with message-id 
and subject line Bug#121: fixed in aircrack-ng 1:1.7+git20230807.4bf83f1a-1
has caused the Debian Bug report #121,
regarding aircrack-ng: depends on obsolete pcre3 library
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.)


-- 
121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aircrack-ng
Severity: important
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---
Source: aircrack-ng
Source-Version: 1:1.7+git20230807.4bf83f1a-1
Done: Samuel Henrique 

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

Debian distribution maintenance software
pp.
Samuel Henrique  (supplier of updated aircrack-ng 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, 07 Aug 2023 19:48:54 +0100
Source: aircrack-ng
Architecture: source
Version: 1:1.7+git20230807.4bf83f1a-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Samuel Henrique 
Closes: 121
Changes:
 aircrack-ng (1:1.7+git20230807.4bf83f1a-1) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Update standards version to 4.6.1, no changes needed.
 .
   [ Samuel Henrique ]
   * New upstream version 1.7+git20230807.4bf83f1a
   * d/control: Build with pcre2 instead of pcre3 (Closes: #121)
   * d/p/s390x_ftbfs.patch: Drop patch, merged upstream
   * d/p/add_missing_import_airodump.patch: New patch to fix FTBFS
Checksums-Sha1:
 05808c6ea1de0bb2b281926a7f6714b906ebf738 2415 
aircrack-ng_1.7+git20230807.4bf83f1a-1.dsc
 9f85c20b77f79e9ae83ed353a82b35638d7384c4 4772848 
aircrack-ng_1.7+git20230807.4bf83f1a.orig.tar.xz
 2027de32ae818be1c11d69a13cd70bce7092b72a 15352 
aircrack-ng_1.7+git20230807.4bf83f1a-1.debian.tar.xz
 2dc23a62da18e81f2b64a5671c97ff923c243a7a 8373 
aircrack-ng_1.7+git20230807.4bf83f1a-1_amd64.buildinfo
Checksums-Sha256:
 86b1f0616aae2d30f4ba69c5763bbaf94267da247b6029289b673770b67a9398 2415 
aircrack-ng_1.7+git20230807.4bf83f1a-1.dsc
 517e3e6be8f4e2ad17024b64179ad2e78695d0ea375a337ffaeef98d75b4cb8c 4772848 
aircrack-ng_1.7+git20230807.4bf83f1a.orig.tar.xz
 84d729c47afff063cb6b554ca3c0082e1ff41d469a3286e49d722951f075fa20 15352 
aircrack-ng_1.7+git20230807.4bf83f1a-1.debian.tar.xz
 bdb164b040c13630da9082e357ef455ceeaef81c3cee0406f7f563f904c195fb 8373 
aircrack-ng_1.7+git20230807.4bf83f1a-1_amd64.buildinfo
Files:
 b4264dd6b89e2cb2bd90eb1149f5bd0f 2415 net optional 
aircrack-ng_1.7+git20230807.4bf83f1a-1.dsc
 5ce7f3a83fb02f5fa46428849a6b0a39 4772848 net optional 
aircrack-ng_1.7+git20230807.4bf83f1a.orig.tar.xz
 e4ec834f288fd26e814a15a00efb3a0b 15352 net optional 
aircrack-ng_1.7+git20230807.4bf83f1a-1.debian.tar.xz
 c31bc0a7ff038db36938bfa897ec5d1a 8373 net optional 
aircrack-ng_1.7+git20230807.4bf83f1a-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEBdtqg34QX0sdAsVfu6n6rcz7RwcFAmTRRHsACgkQu6n6rcz7
RwevCg//YYwvuwMGFSepAnc7qWvDlY3yTEiXduNwg1O+gKpdtoSl5p9POYahGIdw

Processed: block 1040963 with 1043238

[Debian Bug Tracking System]

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

> block 1040963 with 1043238
Bug #1040963 {Done: Paul Gevers } [src:starpu] src:starpu: 
fails to migrate to testing for too long: unsatisfiable dependency on armel, 
mipsel and s390x + segfault
1040963 was not blocked by any bugs.
1040963 was not blocking any bugs.
Added blocking bug(s) of 1040963: 1043238
> thanks
Stopping processing here.

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

Processed: Bug#1000021 marked as pending in aircrack-ng

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #121 [src:aircrack-ng] aircrack-ng: depends on obsolete pcre3 library
Added tag(s) pending.

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

Bug#1000021: marked as pending in aircrack-ng

[Samuel Henrique]

Control: tag -1 pending

Hello,

Bug #121 in aircrack-ng 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/aircrack-ng/-/commit/5fdd835f9e6dfd7c110cecdda41eb973320809a2


d/control: Build with pcre2 instead of pcre3 (Closes: #121)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/121

Bug#1043048: Please give back statsmodels on mips64el Re: (Bug#1043048: fixed in openblas 0.3.23+ds-3)

[Sébastien Villemot]

Le lundi 07 août 2023 à 19:13 +0100, Rebecca N. Palmer a écrit :
> This does seem to have worked: the openblas build log no longer contains 
> FATAL ERROR.
> 
> Hence, please give back statsmodels on mips64el.  (DMs aren't allowed to 
> use the self-service link.)

Done.

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




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

Bug#1043048: Please give back statsmodels on mips64el Re: (Bug#1043048: fixed in openblas 0.3.23+ds-3)

[Rebecca N. Palmer]

This does seem to have worked: the openblas build log no longer contains 
FATAL ERROR.


Hence, please give back statsmodels on mips64el.  (DMs aren't allowed to 
use the self-service link.)

Bug#1043120: marked as done (gr-limesdr: breaks ABI without SONAME bump)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2023 18:00:09 +
with message-id 
and subject line Bug#1043120: fixed in gr-limesdr 3.0.1.10.69-2
has caused the Debian Bug report #1043120,
regarding gr-limesdr: breaks ABI without SONAME bump
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.)


-- 
1043120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gr-limesdr
Version: 3.0.1.10.69-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gnss-sdr/36539433/log.gz

31s (Reading database ... 13556 files and directories currently installed.)
 31s Removing autopkgtest-satdep (0) ...
 31s autopkgtest [04:58:26]: test testgnsssdr: [---
 31s gnss-sdr: symbol lookup error: gnss-sdr: undefined symbol: 
_ZN2gr7limesdr6source4makeENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiRKS7_
 31s autopkgtest [04:58:26]: test testgnsssdr: ---]
 32s testgnsssdr  FAIL non-zero exit status 127

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: gr-limesdr
Source-Version: 3.0.1.10.69-2
Done: A. Maitland Bottoms 

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

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated gr-limesdr 
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: Sun, 06 Aug 2023 12:58:30 -0400
Source: gr-limesdr
Binary: gr-limesdr libgnuradio-limesdr3.0.2 libgnuradio-limesdr3.0.2-dbgsym
Architecture: source amd64
Version: 3.0.1.10.69-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: A. Maitland Bottoms 
Description:
 gr-limesdr - LimeSDR blocks for GnuRadio
 libgnuradio-limesdr3.0.2 - LimeSDR blocks for GnuRadio (runtime library)
Closes: 1043120
Changes:
 gr-limesdr (3.0.1.10.69-2) experimental; urgency=medium
 .
   * Bump SONAME due to ABI changes (Closes: 1043120)
   * Upload to experimental for new libgnuradio-limesdr3.0.2 package
Checksums-Sha1:
 1416bcadf69aaab2ca6f0fa0b17a4d35cdf3e8df 2394 gr-limesdr_3.0.1.10.69-2.dsc
 9240db02f79e6dce7eb96ddf53dd9ca419f2f434 5256 
gr-limesdr_3.0.1.10.69-2.debian.tar.xz
 090fe4ca397d24a2c8ce5a01d64b09028df7f463 19678 
gr-limesdr_3.0.1.10.69-2_amd64.buildinfo
 ba29e0832f67bed7187a46756e60c266e8a4b7b9 289196 
gr-limesdr_3.0.1.10.69-2_amd64.deb
 1b977013d431c89673aa9404afe1cb14c3708d13 2198920 
libgnuradio-limesdr3.0.2-dbgsym_3.0.1.10.69-2_amd64.deb
 a542a1a600171064846b6469c38d90d0ed4eb36d 115436 
libgnuradio-limesdr3.0.2_3.0.1.10.69-2_amd64.deb
Checksums-Sha256:
 ec2eca0b7661d70d8e1d317e4b385771d3b3f8878e2e9059e42a0f25f8b6a031 2394 
gr-limesdr_3.0.1.10.69-2.dsc
 12ec10c2ed4ed0b05dddff86ce42d611611c967e40cc635d16a91fecdbdb8fda 5256 
gr-limesdr_3.0.1.10.69-2.debian.tar.xz
 6e69201942fcc48c18c24d081c5f72b23b45b542d11c5ca49f309d369da69b88 19678 
gr-limesdr_3.0.1.10.69-2_amd64.buildinfo
 eb2fccdc5ad1db83969dc15b79c36f18ec6d6cb33013acd1fbb63ba065c0c0b5 289196 
gr-limesdr_3.0.1.10.69-2_amd64.deb
 28a13eaad3d96d34a2c8ac79425562fe3565b8bad0eaa2daf340b31b3f14a071 2198920 
libgnuradio-limesdr3.0.2-dbgsym_3.0.1.10.69-2_amd64.deb
 daff5473fb2d44e2343c648d8d048e0a79e3adedce05da962f9a08ed5dba2a3a 115436 
libgnuradio-limesdr3.0.2_3.0.1.10.69-2_amd64.deb
Files:
 b754d0f1c36d19f5fff53bb4239fedc0 2394 hamradio optional 
gr-limesdr_3.0.1.10.69-2.dsc
 6b73a5a4871c7e7a9d6800cc1a6d5444 5256 hamradio optional 
gr-limesdr_3.0.1.10.69-2.debian.tar.xz
 39167dee06db998367b4bf98eecf4fe7 19678 hamradio optional 
gr-limesdr_3.0.1.10.69-2_amd64.buildinfo
 d5b4ea72c2b6d62aaca88d3edffbd15d 289196 hamradio optional 
gr-limesdr_3.0.1.10.69-2_amd64.deb
 f57628716de8b22def8a729c9608e1ee 2198920 debug optional 
libgnuradio-limesdr3.0.2-dbgsym_3.0.1.10.69-2_amd64.deb
 67cf7bc5be2d5ade92fc5cf8da12fd29 115436 libs optional 
libgnuradio-limesdr3.0.2_3.0.1.10.69-2_amd64.deb

-BEGIN PGP SIGNATURE-

Processed: [bts-link] source package libheif

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package libheif
> # 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 #1041242 (http://bugs.debian.org/1041242)
> # Bug title: libheif1: 1.16.2-1+b1 breaks displaying any pictures
> #  * https://github.com/strukturag/libheif/issues/933
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1041242 + fixed-upstream
Bug #1041242 [libheif1] libheif1: 1.16.2-1+b1 breaks displaying any pictures
Added tag(s) fixed-upstream.
> usertags 1041242 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:freeorion

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:freeorion
> # 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 #1037667 (http://bugs.debian.org/1037667)
> # Bug title: freeorion: ftbfs with GCC-13
> #  * https://github.com/freeorion/freeorion/pull/4364
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1037667 + fixed-upstream
Bug #1037667 [src:freeorion] freeorion: ftbfs with GCC-13
Added tag(s) fixed-upstream.
> usertags 1037667 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package meson

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package meson
> # 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 #1041454 (http://bugs.debian.org/1041454)
> # Bug title: naev: FTBFS on mips64el
> #  * https://github.com/mesonbuild/meson/issues/12017
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1041454 + fixed-upstream
Bug #1041454 [meson] naev: FTBFS on mips64el
Bug #1041499 [meson] meson: glib2.0 FTBFS on mips64el: "native build" but then 
"Can not run test applications in this cross environment"
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> usertags 1041454 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1041454 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #1041499 (http://bugs.debian.org/1041499)
> # Bug title: meson: glib2.0 FTBFS on mips64el: "native build" but then "Can 
> not run test applications in this cross environment"
> #  * https://github.com/mesonbuild/meson/issues/12017
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1041499 + fixed-upstream
Bug #1041499 [meson] meson: glib2.0 FTBFS on mips64el: "native build" but then 
"Can not run test applications in this cross environment"
Bug #1041454 [meson] naev: FTBFS on mips64el
Ignoring request to alter tags of bug #1041499 to the same tags previously set
Ignoring request to alter tags of bug #1041454 to the same tags previously set
> usertags 1041499 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1041499 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#1040801: mcomix: pillow 10.0.0 not recognized as higher than 6.0.0

[Roy Clark (kralcyor)]

Package: mcomix
Version: 2.1.0-2
Followup-For: Bug #1040801

Dear Maintainer,

This bug was fixed in the upstream commit [04785a], which was included in the 
new upstream version 2.2.0(and 2.2.1, of course):
https://sourceforge.net/p/mcomix/git/ci/2.2.0/tree/ChangeLog

[04785a]: 
https://sourceforge.net/p/mcomix/git/ci/04785a835b6c0e0782c9d0689686b0c1139febb1/

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

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

Versions of packages mcomix depends on:
ii  gir1.2-gtk-3.03.24.38-2
ii  python3   3.11.4-5
ii  python3-cairo 1.24.0-1
ii  python3-gi3.44.1-2
ii  python3-gi-cairo  3.44.1-2
ii  python3-pil   10.0.0-1

Versions of packages mcomix recommends:
ii  python3-chardet  5.1.0+dfsg-2

Versions of packages mcomix suggests:
pn  lhasa
pn  mupdf-tools  
ii  p7zip16.02+dfsg-8
ii  unrar1:6.2.9-1
ii  unzip6.0-28

-- debconf-show failed

Bug#1039472: marked as done (ca-certificates-java: openjdk-17 update caused install regressions)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2023 16:47:08 +
with message-id 
and subject line Bug#1039472: fixed in ca-certificates-java 20230620~deb12u1
has caused the Debian Bug report #1039472,
regarding ca-certificates-java: openjdk-17 update caused install regressions
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.)


-- 
1039472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ca-certificates-java
Version: 20230103
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
X-Debbugs-Cc: t...@security.debian.org
Control: fixed -1 20230620

The openjdk-17 upload to bookworm-security caused regressions when
installing openjdk/ca-certificates-java similar to 
https://bugs.debian.org/1035416
This has been fixed in ca-certificates-java 20230620 in sid (as well as
for openjdk-21 in experimental) and I veryfied that rebuilding that
package for bookworm fixes the issue there, too.

So far I did't see that this regression affects bullseye as well.


Andreas
--- End Message ---
--- Begin Message ---
Source: ca-certificates-java
Source-Version: 20230620~deb12u1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated ca-certificates-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: SHA256

Format: 1.8
Date: Sun, 06 Aug 2023 16:24:13 +0200
Source: ca-certificates-java
Architecture: source
Version: 20230620~deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Andreas Beckmann 
Closes: 1039472
Changes:
 ca-certificates-java (20230620~deb12u1) bookworm; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild for bookworm.  (Closes: #1039472)
 .
 ca-certificates-java (20230620) unstable; urgency=medium
 .
   [ Matthias Klose ]
   * Bump standards version.
   * Build-depend on default-jdk-headless instead of default-jdk.
 .
   [ Vladimir Petko ]
   * d/ca-certificates-java.postinst: Work-around not yet configured jre.
Checksums-Sha1:
 6b96a600d5ce1273f515a2ad081a5ed0a8379c05 1849 
ca-certificates-java_20230620~deb12u1.dsc
 fc523afac223a0f9442ce70398fae26e936e9aff 17328 
ca-certificates-java_20230620~deb12u1.tar.xz
 6b23c3c718fdfb5d1ec9be2d5b5500029510b0a3 9357 
ca-certificates-java_20230620~deb12u1_source.buildinfo
Checksums-Sha256:
 a7f160d4395333dd0d1ef0d8d7a1233f81285da3b8e1a04f5340edfdf6a5946f 1849 
ca-certificates-java_20230620~deb12u1.dsc
 d2d6147ed9b0dfa07c67780cb88f6b5006656ae80bcb3bc1a859a542a1fc4bd7 17328 
ca-certificates-java_20230620~deb12u1.tar.xz
 6a0d45e9db01f66fdeb3943f106f5dd67385bb6884dfe64aaeed00a2596d59c0 9357 
ca-certificates-java_20230620~deb12u1_source.buildinfo
Files:
 7792f7681304784fdae325d313d2228e 1849 java optional 
ca-certificates-java_20230620~deb12u1.dsc
 90fd82a7c9444b0c265a6e75e79249cc 17328 java optional 
ca-certificates-java_20230620~deb12u1.tar.xz
 1c06921b5071ab02c84d41ee3c8bb30e 9357 java optional 
ca-certificates-java_20230620~deb12u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmTPrxUQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCKNxD/4ksDPAolPXpeygzWylD8ZRbfaJb3+WGM2q
scGQJfbKfv8c9DsilerOuRji/oy3P0aWVrtIPvDSaLcjYUMpISi+6SJUqIEqATqz
U4UDGvLrWfJxBvowV2iFd85ft/rBHeTvgr3D9EsPm8KysllfysV05UVHQMUuKrLJ
MBXHqkgSa5f86gcRZ8KlYjjv2zWS5EvLI9Qp0QLGIKSkfhqNRagaVT6bN5ldjnCv
0Cnc8WUDnRgJgWs+/R6dREwdYv3+MMlYnJVJSPcRD03bsBKdXyyOsLc8vzphOfmu
RasdqmsMQsoV0lnzeyMp8AIwwJ7/vZBdtCBD7zyo/L6C3vRmQghKfwpVtAE/u4IW
Agz4EJeI+wUnhaBWAAt8ZS94xdtth6e+18DcRya5LMJ63TuEj2O8fUF46reol8YQ
v8U4g5b2uIMPfcU2vX41VThE/zxslIGV2k+LTmWON4Nn7xnWmoX5970XejFyzjTq
qqdUc6Ws9Qvcd1qVeu12DAK1pa+erBKt3zHOyz/tGpnT7Umi9kTYhHbEuhlCq+U/
bdrMUWlSwnErbicmK6z4rzQaJ4S6Pbk1oIsp4u8Sz2W47LPW7tP/721O6zugQkpx
LEQhi5aQSQGypwaaTTBbleHH95SGeKFu7TjxTP62c+0M/kg7cysTzmT90x4UOIrR
kucjexzN1Q==
=wqLq
-END PGP SIGNATURE End Message ---

Bug#1030129: ca-certificates-java: openjdk-17 update caused install regressions

[Volker Theile]

This bug is still active in Debian 12, e.g. it is not possible to
install collectd. Please backport ca-certificates-java (20230710) from
Trixie/Sid.

Bug#1041211: marked as done (libsdl-perl: FTBFS and autopkgtest failure with sdl12-compat, especially on 32-bit)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2023 16:04:57 +
with message-id 
and subject line Bug#1041211: fixed in libsdl-perl 2.548-4
has caused the Debian Bug report #1041211,
regarding libsdl-perl: FTBFS and autopkgtest failure with sdl12-compat, 
especially on 32-bit
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.)


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

Source: libsdl-perl, sdl12-compat
Control: found -1 libsdl-perl/2.548-3
Control: found -1 sdl12-compat/1.2.64-5
Control: block 1039911 by -1
Severity: serious
Tags: trixie sid ftbfs
User: debian...@lists.debian.org
Usertags: breaks needs-update

Since sdl12-compat took over the libsdl1.2debian and libsdl1.2-dev
packages from the old libsdl1.2, the test suite from libsdl-perl is
sometimes crashing in t/core_video.t. It seems to be failing consistently
on 32-bit architectures, and intermittently on some 64-bit architectures
(arm64 and s390x). I didn't see this before starting the transition
because I had used amd64 for my test-rebuilds, and amd64 seems to be
consistently unaffected.

I originally saw this in the autopkgtest runs on ci.debian.net, but I was
able to reproduce a similar failure during build-time testing on i386.
I didn't see a similar crash when testing real games, so I don't know
whether this is a crash that can affect games in practice, or just a
test issue.

It is not yet clear to me whether this is a libsdl-perl bug or a
sdl12-compat bug, so for now the bug is reported as affecting both
packages. It can be reassigned to either libsdl-perl or sdl12-compat
when a root cause is found.

In the cases where it fails, there are two failure modes that I've seen.
One failure mode is that t/core_video.t crashes with signal 11 (SIGSEGV)
during testing, usually (perhaps always?) after test point 65, for
example in
:


147s t/core_video.t ..
147s ok 1 - SDL::Video->can(...)
147s ok 2 - SDL_SWSURFACE should be imported

...

147s ok 63 - '[get_video_surface] Checking if we get a surface ref back' isa 
'SDL::Surface'
147s ok 64 - [video_driver_name] This is your driver name: dummy
147s ok 65 - [video_mode_ok] Checking if an integer was return
147s All 65 subtests passed
147s(2 TODO tests unexpectedly succeeded)

...

289s t/core_video.t(Wstat: 11 (Signal: SEGV) Tests: 65 Failed: 
0)
289s   TODO passed:   57, 59
289s   Non-zero wait status: 11
289s   Parse errors: No plan found in TAP output


The other failure mode is that t/core_video.t completes testing and calls
done_testing(), but then crashes with SIGSEGV during exit, for example in
:


369s t/core_video.t ..
369s ok 1 - SDL::Video->can(...)
369s ok 2 - SDL_SWSURFACE should be imported
...
369s ok 108 # skip No window manager available
369s ok 109 # skip No window manager available
369s ok 110 - Are we still alive? Checking for segfaults
369s 1..110
369s All 110 subtests passed
369s(less 39 skipped subtests: 71 okay)
369s(2 TODO tests unexpectedly succeeded)

...

499s t/core_video.t(Wstat: 11 (Signal: SEGV) Tests: 110 Failed: 
0)
499s   TODO passed:   57, 59
499s   Non-zero wait status: 11


In the s390x log

we can also see an error message from glibc's malloc implementation
indicating memory corruption, perhaps a double-free or something like
that:


130s ok 64 - [video_driver_name] This is your driver name: dummy
130s ok 65 - [video_mode_ok] Checking if an integer was return
130s corrupted size vs. prev_size


This is blocking migration of sdl12-compat to testing (#1039911).

smcv
--- End Message ---
--- Begin Message ---
Source: libsdl-perl
Source-Version: 2.548-4
Done: gregor herrmann 

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libsdl-perl package)

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

Processed: Bug#1041211 marked as pending in libsdl-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1041211 [src:libsdl-perl] libsdl-perl: FTBFS and autopkgtest failure with 
sdl12-compat, especially on 32-bit
Added tag(s) pending.

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

Bug#1041211: marked as pending in libsdl-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #1041211 in libsdl-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/libsdl-perl/-/commit/65656c28d4fac19a7ce055d6adc93b71cbc970a0


Add patch from Simon McVittie to fix errors with sdl12-compat.

Closes: #1041211


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1041211

Bug#1042161: marked as done (python-pytest-xprocess: FTBFS: ImportError: cannot import name 'std' from 'py' (/usr/lib/python3/dist-packages/py.py))

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2023 15:50:52 +
with message-id 
and subject line Bug#1042161: fixed in python-pytest-xprocess 0.22.2-1
has caused the Debian Bug report #1042161,
regarding python-pytest-xprocess: FTBFS: ImportError: cannot import name 'std' 
from 'py' (/usr/lib/python3/dist-packages/py.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.)


-- 
1042161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pytest-xprocess
Version: 0.22.2-0.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_install --no-py2 --in-tmp
> + PKGOS_IN_TMP=no
> + echo WARNING: --no-py2 is deprecated and always on.
> WARNING: --no-py2 is deprecated and always on.
> + shift
> + PKGOS_IN_TMP=yes
> + shift
> + dpkg-parsechangelog -SSource
> + SRC_PKG_NAME=python-pytest-xprocess
> + echo python-pytest-xprocess
> + sed s/python-//
> + PY_MODULE_NAME=pytest-xprocess
> + py3versions -vr
> + PYTHON3S=3.11
> + [ yes = yes ]
> + TARGET_DIR=tmp
> + pwd
> + python3.11 setup.py install --install-layout=deb --root 
> /<>/debian/tmp
> running install
> /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated.
> !!
> 
> 
> 
> Please avoid running ``setup.py`` directly.
> Instead, use pypa/build, pypa/installer or other
> standards-based tools.
> 
> See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html 
> for details.
> 
> 
> 
> !!
>   self.initialize_options()
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/xprocess
> copying xprocess/xprocess.py -> build/lib/xprocess
> copying xprocess/pytest_xprocess.py -> build/lib/xprocess
> copying xprocess/__init__.py -> build/lib/xprocess
> running install_lib
> creating /<>/debian/tmp
> creating /<>/debian/tmp/usr
> creating /<>/debian/tmp/usr/lib
> creating /<>/debian/tmp/usr/lib/python3
> creating /<>/debian/tmp/usr/lib/python3/dist-packages
> creating /<>/debian/tmp/usr/lib/python3/dist-packages/xprocess
> copying build/lib/xprocess/xprocess.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/xprocess
> copying build/lib/xprocess/pytest_xprocess.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/xprocess
> copying build/lib/xprocess/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/xprocess
> byte-compiling 
> /<>/debian/tmp/usr/lib/python3/dist-packages/xprocess/xprocess.py
>  to xprocess.cpython-311.pyc
> byte-compiling 
> /<>/debian/tmp/usr/lib/python3/dist-packages/xprocess/pytest_xprocess.py
>  to pytest_xprocess.cpython-311.pyc
> byte-compiling 
> /<>/debian/tmp/usr/lib/python3/dist-packages/xprocess/__init__.py
>  to __init__.cpython-311.pyc
> running install_egg_info
> running egg_info
> writing pytest_xprocess.egg-info/PKG-INFO
> writing dependency_links to pytest_xprocess.egg-info/dependency_links.txt
> writing entry points to pytest_xprocess.egg-info/entry_points.txt
> writing requirements to pytest_xprocess.egg-info/requires.txt
> writing top-level names to pytest_xprocess.egg-info/top_level.txt
> reading manifest file 'pytest_xprocess.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'CHANGELOG'
> warning: no directories found matching 'example'
> adding license file 'LICENSE'
> writing manifest file 'pytest_xprocess.egg-info/SOURCES.txt'
> Copying pytest_xprocess.egg-info to 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pytest_xprocess-0.22.2.egg-info
> Skipping SOURCES.txt
> running install_scripts
> + pwd
> + rm -rf /<>/debian/python*/usr/lib/python*/dist-packages/*.pth
> + pwd
> + rm -rf /<>/debian/tmp/usr/lib/python*/dist-packages/*.pth
> set -e ; for pyvers in 3.11; do \
>   PYTHONPATH=/<>/debian/tmp/usr/lib/python3/dist-packages 
> python$pyvers -m pytest -v -k "not test_interruption_cleanup and not 
> test_interruption_does_not_cleanup"; \
> done
> Traceback (most recent call last):
>   File "", line 198, in 

Bug#1042328: marked as done (jaraco.classes: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2023 15:49:33 +
with message-id 
and subject line Bug#1042328: fixed in jaraco.classes 3.2.1-4
has caused the Debian Bug report #1042328,
regarding jaraco.classes: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p 3.11 returned exit code 13
to be marked as done.

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

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


-- 
1042328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jaraco.classes
Version: 3.2.1-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_jaraco.classes/build/jaraco
> creating 
> /<>/.pybuild/cpython3_3.11_jaraco.classes/build/jaraco/classes
> copying jaraco/classes/meta.py -> 
> /<>/.pybuild/cpython3_3.11_jaraco.classes/build/jaraco/classes
> copying jaraco/classes/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_jaraco.classes/build/jaraco/classes
> copying jaraco/classes/ancestry.py -> 
> /<>/.pybuild/cpython3_3.11_jaraco.classes/build/jaraco/classes
> copying jaraco/classes/properties.py -> 
> /<>/.pybuild/cpython3_3.11_jaraco.classes/build/jaraco/classes
> running egg_info
> creating jaraco.classes.egg-info
> writing jaraco.classes.egg-info/PKG-INFO
> writing dependency_links to jaraco.classes.egg-info/dependency_links.txt
> writing requirements to jaraco.classes.egg-info/requires.txt
> writing top-level names to jaraco.classes.egg-info/top_level.txt
> writing manifest file 'jaraco.classes.egg-info/SOURCES.txt'
> reading manifest file 'jaraco.classes.egg-info/SOURCES.txt'
> adding license file 'LICENSE'
> writing manifest file 'jaraco.classes.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd 
> /<>/.pybuild/cpython3_3.11_jaraco.classes/build; python3.11 -m 
> pytest 
> = test session starts 
> ==
> platform linux -- Python 3.11.4, pytest-7.4.0, pluggy-1.2.0
> rootdir: /<>
> configfile: pytest.ini
> collected 4 items / 1 error
> 
>  ERRORS 
> 
> _ ERROR collecting 
> .pybuild/cpython3_3.11_jaraco.classes/build/jaraco/classes/ancestry.py _
> /usr/lib/python3/dist-packages/_pytest/runner.py:341: in from_call
> result: Optional[TResult] = func()
> /usr/lib/python3/dist-packages/_pytest/runner.py:372: in 
> call = CallInfo.from_call(lambda: list(collector.collect()), "collect")
> /usr/lib/python3/dist-packages/_pytest/doctest.py:547: in collect
> module = import_path(
> /usr/lib/python3/dist-packages/_pytest/pathlib.py:565: in import_path
> importlib.import_module(module_name)
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> :1204: in 

Bug#1043224: r-bioc-decoupler: autopkgtest regression

[Graham Inggs]

Source: r-bioc-decoupler
Version: 2.6.0+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

The upload of r-bioc-decoupler 2.6.0+dfsg-1 is failing its own
autopkgtest [1].  I've copied what I hope is the relevant part of the
log below.  It seems r-bioc-decoupler has an autopkgtest dependency on
r-cran-glmnet (>= 4.1.0), but we have 4.1-7-1 in the archive.  Note
the hyphen in the 4.1-7 version.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-bioc-decoupler/testing/amd64/


 17s Broken autopkgtest-satdep:amd64 Depends on r-cran-glmnet:amd64 <
none -> 4.1-7-1 @un uN > (>= 4.1.0)
 17s Done
 17s Some packages could not be installed. This may mean that you have
 17s requested an impossible situation or if you are using the unstable
 17s distribution that some required packages have not yet been created
 17s or been moved out of Incoming.
 17s The following information may help to resolve the situation:
 17s
 17s The following packages have unmet dependencies:
 18s  autopkgtest-satdep : Depends: r-cran-glmnet (>= 4.1.0) but
4.1-7-1 is to be installed
 18s E: Unable to correct problems, you have held broken packages.

Processed: Bug#1042161 marked as pending in python-pytest-xprocess

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042161 [src:python-pytest-xprocess] python-pytest-xprocess: FTBFS: 
ImportError: cannot import name 'std' from 'py' 
(/usr/lib/python3/dist-packages/py.py)
Added tag(s) pending.

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

Bug#1042161: marked as pending in python-pytest-xprocess

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-pytest-xprocess/-/commit/d2c897b03286a6e6da07f5eb7c059dcd2275d52f


Add missing python3-py (build-)depends (Closes: #1042161).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042161

Bug#1040940: marked as done (rmlint-gui fails to start: SyntaxError: source code cannot contain null bytes)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2023 15:25:35 +
with message-id 
and subject line Bug#1040940: fixed in rmlint 2.9.0-2.5
has caused the Debian Bug report #1040940,
regarding rmlint-gui fails to start: SyntaxError: source code cannot contain 
null bytes
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.)


-- 
1040940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040940
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rmlint-gui
Version: 2.9.0-2.4
Severity: grave

euler:~ $ rmlint --gui
  File "/tmp/.shredder-bootstrap.py.KFWS71", line 23

SyntaxError: source code cannot contain null bytes


The generated temporary source file has a null byte at the end of the
file.  This is quite possibly already fixed upstream.
--- End Message ---
--- Begin Message ---
Source: rmlint
Source-Version: 2.9.0-2.5
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated rmlint package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 05 Aug 2023 17:16:05 +0300
Source: rmlint
Architecture: source
Version: 2.9.0-2.5
Distribution: unstable
Urgency: high
Maintainer: Carlos Maddela 
Changed-By: Adrian Bunk 
Closes: 1040940
Changes:
 rmlint (2.9.0-2.5) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Add upstream fix for GUI startup failure with recent python3.11.
 (Closes: #1040940)
Checksums-Sha1:
 cd86b2df1b38c4db0a68c6e0a7d66e908366db10 2272 rmlint_2.9.0-2.5.dsc
 f0715b87a7d9a50fd3150c1ee95abc350c460e2c 2483457 rmlint_2.9.0.orig.tar.gz
 d3f56b8a2e84941efed0169e55f45be54cb16520 23076 rmlint_2.9.0-2.5.debian.tar.xz
Checksums-Sha256:
 c33968272104dd2c84a1f8b009f79149e646738877b6f2fde5a50350a596acc4 2272 
rmlint_2.9.0-2.5.dsc
 a2d26863e0018efad60f0b1123e7cffd8ef764c8fb574a7987a49260e4e51c8f 2483457 
rmlint_2.9.0.orig.tar.gz
 af6db454c77aa3ad856c1f6a1d0b6235966a5ca4198380a539083ca7c246cd95 23076 
rmlint_2.9.0-2.5.debian.tar.xz
Files:
 4fb636f431501762d8515aa6122cf3ba 2272 utils optional rmlint_2.9.0-2.5.dsc
 b2a0ba67c3f6914e584354a173537ca9 2483457 utils optional 
rmlint_2.9.0.orig.tar.gz
 e686686b31abef24bac26a1b969c87f2 23076 utils optional 
rmlint_2.9.0-2.5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmTOX2gACgkQiNJCh6LY
mLGm9Q//ZwyMIKPtjzuDDFjx3ds4ufYlSTglMUxPeQTz/3jWEXlkM24JXz5kr1jx
lJaiP1rEM9xI3n/SDedZTu8BSMFPks8jv3nJkfCNwcVUAiofKPqI4KDtVQBTyg/Y
t/abC4suzZBX0UnyCJcYKzpVeKrUgS9FyCd3mmrdO8psCAQ1y1+zNQ/x/auJgP4u
E6vTLpzya1kjTb4sWmnri+BCx4F8HHPAlsvKvQLYXorz1ZeDuOC/Jk2KqEEh1PQR
QTTKRISh1WV58XGrJLjXMVqqjJvCoCz4+b6FDJl3gzkBiA2S7Y/wMmNUGtXQ8T+e
C1Mpp6XLV87alFj3T49moZxDRmrENM4YNpdSU8pH8uuq4cR8s+3qv8In/IK2vuoP
ArSOwFfm/kpcv5ETBSnWoYIKlFnHJDycecY1wMn8ItxpI3AfSkUhm00UtBwiYrYD
9BvddcttTaex2US28dKtWht6VO8cEBhPHIahuYBUXHHegJHpi2yeeTPlyGB1lcnI
UFMQEHjD/lrabpOoP0mAAVW6JKuSEtW9SVNmkXP0xtii4sT80ErAXIOZ+c4nxyTb
0pRR6LHmaVeUEAD9k3jYuLYFja7ixt7Cm74Z9Xdsj1cs/45CE7a5phN/k7pc+tRb
DAm518yhlzPtaCszatvxi4cbeCjQVCAJ38ULR9LcO5VH/ecqmro=
=bzLR
-END PGP SIGNATURE End Message ---

Processed: Bug#1042328 marked as pending in jaraco.classes

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042328 [src:jaraco.classes] jaraco.classes: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) pending.

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

Bug#1042328: marked as pending in jaraco.classes

[jcfp]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/jaraco.classes/-/commit/8dc55b5705b8071b2bede1b73043590e195225e8


Control: add build-dep on python3-more-itertools. (Closes: #1042328)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042328

Bug#1043223: r-cran-biocmanager: autopkgtest needs update for r-bioc-biocversion

[Graham Inggs]

Source: r-cran-biocmanager
Version: 1.30.21.1+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: needs-update

Hi Maintainer

Since the upload of r-bioc-biocversion 3.17.1-1, the autopkgtests of
r-cran-biocmanager are failing [1].  I've copied what I hope is the
relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-biocmanager/testing/amd64/


 38s > test_check("BiocManager")
 58s [ FAIL 1 | WARN 1 | SKIP 24 | PASS 84 ]
 58s
 58s == Skipped tests (24)
==
 59s * On CRAN (23): 'test_install.R:27:5', 'test_install.R:45:5',
 59s   'test_install.R:204:5', 'test_repositories.R:5:5',
 59s   'test_repositories.R:14:5', 'test_repositories.R:20:5',
 59s   'test_repositories.R:26:5', 'test_repositories.R:33:5',
 59s   'test_repositories.R:43:5', 'test_repositories.R:118:5',
 59s   'test_repositories.R:127:5', 'test_repositories.R:165:5',
 59s   'test_version.R:17:5', 'test_version.R:39:5', 'test_version.R:92:5',
 59s   'test_version.R:107:5', 'test_version.R:147:5', 'test_version.R:194:5',
 59s   'test_version.R:235:5', 'test_version.R:246:5', 'test_version.R:277:5',
 59s   'test_version.R:328:5', 'test_version.R:387:5'
 59s * too idiosyncratic for standardized testing (1): 'test_install.R:164:5'
 59s
 59s == Failed tests

 59s -- Failure ('test_install.R:355:5'): install() without package
names passes ... to install.packages --
 59s `object` is not TRUE
 59s
 59s `actual`:   FALSE
 59s `expected`: TRUE
 59s
 59s [ FAIL 1 | WARN 1 | SKIP 24 | PASS 84 ]

Processed: Bug#1042358 marked as pending in openvswitch

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042358 [src:openvswitch] openvswitch: FTBFS: make[3]: *** [Makefile:6743: 
manpage-check] Error 1
Added tag(s) pending.

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

Bug#1042358: marked as pending in openvswitch

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1042358 in openvswitch 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/openstack-team/third-party/openvswitch/-/commit/51628d292653ff5712b705f156e86f23d121b57f


* Add patches from Colin Watson to repair the docs (Closes: #1042358):
- docs-1-Wrap_more_table_entries_in_text_blocks.patch
- docs-2-Shorten_overly-wide_table_heading.patch
- docs-3-Tweak_width_of_name_column_in_field_property.patch
- docs-4-Fix_rendering_of_VLAN_Comparison_Chart.patch
- docs-5-Run_tbl_preprocessor_in_manpage-check_rule.patch


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042358

Bug#1042358: openvswitch: FTBFS: make[3]: *** [Makefile:6743: manpage-check] Error 1

[Colin Watson]

On Mon, Aug 07, 2023 at 04:45:30PM +0200, Thomas Goirand wrote:
> Ok, so if there's only 5 patches, not 6, then I should be able to manage
> (even though it's not the best convenient way). Thanks for your patches.

I think I possibly understand what you meant now.  Is this more
convenient?

-- 
Colin Watson (he/him)  [cjwat...@debian.org]
>From 45a2a2245f6c73dc6898f63c8d30ffd138920066 Mon Sep 17 00:00:00 2001
From: Colin Watson 
Date: Fri, 4 Aug 2023 18:22:31 +0100
Subject: [PATCH v2 0/5] docs: Fix manpage-check warnings with groff 1.23.0

https://bugs.debian.org/1042358 reported a manpage-check failure with
groff 1.23.0 in Debian testing/unstable.  Fixing the immediate mistake
here exposed a few other issues in how the tables in ovs-fields(7) are
rendered.

Colin Watson (5):
  docs: Wrap more table entries in text blocks
  docs: Shorten overly-wide table heading
  docs: Tweak width of name column in field property tables
  docs: Fix rendering of VLAN Comparison Chart
  docs: Run tbl preprocessor in manpage-check rule

 Makefile.am  |  2 +-
 build-aux/extract-ofp-fields | 20 ++--
 lib/meta-flow.xml| 25 +
 3 files changed, 28 insertions(+), 19 deletions(-)

--
2.39.2

>From 97fb673b2b09747beabe8625ac86dbfc5aa0c023 Mon Sep 17 00:00:00 2001
From: Colin Watson 
Date: Fri, 4 Aug 2023 11:19:06 +0100
Subject: [PATCH v2 1/5] docs: Wrap more table entries in text blocks

This fixes a number of "table wider than line length minus indentation"
warnings from tbl.  The table cells are too narrow for centered text to
look good, so left-align the contents of the text blocks.

Reported-by: Lucas Nussbaum 
Reported-at: https://bugs.debian.org/1042358
Signed-off-by: Colin Watson 
---
 build-aux/extract-ofp-fields | 12 
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/build-aux/extract-ofp-fields b/build-aux/extract-ofp-fields
index efec59c25..2f566d2b9 100755
--- a/build-aux/extract-ofp-fields
+++ b/build-aux/extract-ofp-fields
@@ -189,12 +189,14 @@ def field_to_xml(field_node, f, body, summary):
 ovs_version = [int(x) for x in ovs_version_s.split(".")]
 if min_ovs_version is None or ovs_version < min_ovs_version:
 min_ovs_version = ovs_version
-summary += ["\\fB%s\\fR" % f["name"]]
+summary += ["T{\n.ad l\n\\fB%s\\fR" % f["name"]]
 if f["extra_name"]:
 summary += [" aka \\fB%s\\fR" % f["extra_name"]]
-summary += [";%d" % f["n_bytes"]]
+summary += ["\nT}"]
+summary += [";T{\n.ad l\n%d" % f["n_bytes"]]
 if f["n_bits"] != 8 * f["n_bytes"]:
 summary += [" (low %d bits)" % f["n_bits"]]
+summary += ["\nT}"]
 summary += [";%s;" % {"MFM_NONE": "no", "MFM_FULLY": "yes"}[f["mask"]]]
 summary += ["%s;" % {True: "yes", False: "no"}[f["writable"]]]
 summary += ["%s;" % f["prereqs"]]
@@ -203,7 +205,7 @@ def field_to_xml(field_node, f, body, summary):
 support += ["OF %s+" % VERSION_REVERSE[min_of_version]]
 if min_ovs_version is not None:
 support += ["OVS %s+" % ".".join([str(x) for x in min_ovs_version])]
-summary += " and ".join(support)
+summary += ["T{\n.ad l\n", " and ".join(support), "\nT}"]
 summary += ["\n"]
 
 # Full description.
@@ -230,8 +232,10 @@ l lx.
 body += ["Width:;"]
 if f["n_bits"] != 8 * f["n_bytes"]:
 body += [
+"T{\n",
 "%d bits (only the least-significant %d bits "
-"may be nonzero)" % (f["n_bytes"] * 8, f["n_bits"])
+"may be nonzero)" % (f["n_bytes"] * 8, f["n_bits"]),
+"\nT}",
 ]
 elif f["n_bits"] <= 128:
 body += ["%d bits" % f["n_bits"]]
-- 
2.39.2

>From 36207097b0c3de75d562b93e666c54f954da763c Mon Sep 17 00:00:00 2001
From: Colin Watson 
Date: Fri, 4 Aug 2023 18:01:55 +0100
Subject: [PATCH v2 2/5] docs: Shorten overly-wide table heading

Using "NXM/OXM Support" makes these tables a little too wide to fit well
when rendered in 80 columns, causing warnings from groff.  There's
already some abbreviation going on here (e.g. "RW?"), so "NXM/OXM?"
seems acceptable.

Reported-by: Lucas Nussbaum 
Reported-at: https://bugs.debian.org/1042358
Signed-off-by: Colin Watson 
---
 build-aux/extract-ofp-fields | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/build-aux/extract-ofp-fields b/build-aux/extract-ofp-fields
index 2f566d2b9..808c6527d 100755
--- a/build-aux/extract-ofp-fields
+++ b/build-aux/extract-ofp-fields
@@ -323,7 +323,7 @@ def group_xml_to_nroff(group_node, fields):
 ".TS\n",
 "tab(;);\n",
 "l l l l l l l.\n",
-"Name;Bytes;Mask;RW?;Prereqs;NXM/OXM Support\n",
+"Name;Bytes;Mask;RW?;Prereqs;NXM/OXM?\n",
 "\_;\_;\_;\_;\_;\_\n",
 ]
 content += summary
-- 
2.39.2

>From 7622daa80dad932cab11febfc8afa6a78b1f84ac Mon Sep 17 00:00:00 2001
From: Colin Watson 
Date: Fri, 4 Aug 2023 18:18:01 +0100
Subject: 

Bug#1042358: openvswitch: FTBFS: make[3]: *** [Makefile:6743: manpage-check] Error 1

[Thomas Goirand]

On 8/7/23 12:10, Colin Watson wrote:

On Mon, Aug 07, 2023 at 10:54:52AM +0200, Thomas Goirand wrote:

I very much appreciate that you've sent patches for this bug, thanks for
this. However, it is difficult to apply your patches because they are sent
inline, and therefore hard to save on disk. Also, I would have done the work
by  hand to avoid annoying you, but your "Message part 2" doesn't contain
the patch at all, only a diffstat.

Could you send me the 6 patches as separate files, so I could more easily
add them to debian/patches? Or at least send the first patch that's
completely missing...


I don't mind sending you patches in a different format if it's helpful,
but I'm confused; I _did_ send them as separate files,
MIME-encapsulated.  How else would I have sent them as separate files?

The "PATCH v2 0/5" message is a cover letter for the patch set.  It's
not supposed to contain a patch itself.

Cheers,


Hi,

Ok, so if there's only 5 patches, not 6, then I should be able to manage 
(even though it's not the best convenient way). Thanks for your patches.


Cheers,

Thomas Goirand (zigo)

Processed: Re: gimp: Missing gir dependencies

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1014420 [src:gimp] gimp: Missing gir dependencies
Severity set to 'important' from 'serious'

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

Bug#1014420: gimp: Missing gir dependencies

[Jeremy Bícha]

Control: severity -1 important

I'm downgrading the severity because the app does still run. But if
you run it from the command line, there are lots of errors like this:

Traceback (most recent call last):
  File 
"/usr/lib/x86_64-linux-gnu/gimp/2.99/plug-ins/python-console/python-console.py",
line 20, in 
gi.require_version('Gimp', '3.0')
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 126, in
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Gimp not available
GIMP-WARNING: gimp: gimp_wire_read(): error


Also, see my suggestion about whether it makes sense to reintroduce
the gimp-python binary package and then we could likely move this
dependency there.

Also, there are now JavaScript and Lua plugins. I explicitly disabled
them with my recent upload, in part because I don't know if we want
Gimp to depend on gjs and Lua or whether those plugins should be in a
separate binary package. (This should be a separate bug report but I'm
mentioning it here since it could be related.)

Thank you,
Jeremy Bícha

Processed: Update 1042253 tag

[Debian Bug Tracking System]

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

> tags 1042253 - experimental
Bug #1042253 {Done: Boyuan Yang } [src:libxlsxwriter] 
libxlsxwriter: FTBFS: make[1]: *** [debian/rules:12: 
override_dh_auto_configure] Error 2
Removed tag(s) experimental.
> thanks
Stopping processing here.

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

Bug#992341: Acknowledgement (bird2: does not properly take over /etc/bird/bird.conf)

[Jakub Ružička]

Hello,

I'm the new bird2 maintainer and I'm happy to help with this.


On 23-08-04 11:08, Jonathan Wiltshire wrote:
> Control: retitle -1 bird2: does not properly take over from bird package
> Control: severity -1 serious

This results in

Version 2.0.12-7 of bird2 is marked for autoremoval from testing on Sat 19 Aug 
2023.

I think this help noone.

If any of the two packages should be dropped from testing, it's bird as it's
nearing upstream EOL at the end of 2023.


> Control: affects -1 + src:bird
> 
> Hi,
> 
> I have just run into this again on the upgrade from bullseye to bookworm.

bullseye contains bird_1.6.8-2.1 which is the same as bookworm,
so I tested on bookworm as it should be equivalent.


> In fact it's worse than just the config files now: bird in its postrm does
> things like disabling and masking the systemd units bird2 uses, and attempts
> to remove the 'bird' user.

I'm unable to reproduce the error on purge after upgrade on my machine, in VM,
or in a container:

$ apt install bird
Setting up bird (1.6.8-2.1+b1) ...

$ apt install bird2
Removing bird (1.6.8-2.1+b1) ...
Setting up bird2 (2.0.12-7) ...

$ apt purge bird
Purging configuration files for bird (1.6.8-2.1+b1) ...

$ grep bird /etc/passwd
bird:x:105:110::/run/bird:/usr/sbin/nologin

$ ls /etc/bird
bird.conf
envvars

$ ls /run/bird
bird.ctl
   
$ systemctl status bird
● bird.service - BIRD Internet Routing Daemon
Loaded: loaded (/lib/systemd/system/bird.service; disabled; preset: 
enabled)
Active: active (running) since Mon 2023-08-07 12:29:43 UTC; 3min 45s ago


On further investigation, the collision you describe is fixed by a patch
included in bird_1.6.7-1 (2019):

https://salsa.debian.org/debian/bird/-/commit/7738791be2

It checks for the ownership of /etc/bird/bird.conf using ucf and only performs
actual purging (including the removal of bird user) when it should.


> disabling and masking the systemd units bird2 uses

I don't see such thing happening in current bird/bird2 package sources:

https://salsa.debian.org/debian/bird/-/blob/master/debian/bird.postrm


The problems you describe imply upgrading from older bird package than 1.6.7,
for example buster 1.6.6-1 but that that's old-old-stable now.

This seems fixed both in bookworm and bullseye. IOW upgrading from a fully
upgraded bullseye system bird_1.6.8 to bookworm bird2_2.0.12 seems to work.

Are you sure you upgraded from latest bullseye bird package?

If so, I'm afraid you might be a victim of a fallout from previous package
versions.


> Please work together to make these two packages cooperate better.

They cooperated just fine in my testing with current bullseye/bookworm
versions and the above-described patch seems to have addressed exactly this 
issue.

Please provide a reproducer with current (bookworm/bullseye) packages,
otherwise I think this was fixed in bird_1.6.7-1.


Cheers,
Jakub Ružička


signature.asc
Description: PGP signature

Bug#1032092: asterisk: CVE-2022-23537 CVE-2022-23547 CVE-2022-39269

[Faidon Liambotis]

Dear maintainer, security team,

(See #1036697 for a similar bug with an almost equivalent response)

The changelog for the asterisk 1:20.4.0~dfsg+~cs6.13.40431414-1 upload
dated 2023-08-04, currently in unstable, mentions:
>+ fixate component pjproject at upstream release 2.13.1

The sources seem to indeed indicate that the version shipped for
pjproject (aka PJSIP) is 2.13.1, which seems to have resolved the
vulnerabilities listed below. 

Specifically:

On Mon, Feb 27, 2023 at 08:48:36PM +0100, Moritz Mühlenhoff wrote:
> CVE-2022-23537[0]:
> | PJSIP is a free and open source multimedia communication library
> | written in C language implementing standard based protocols such as
> | SIP, SDP, RTP, STUN, TURN, and ICE. Buffer overread is possible when
> | parsing a specially crafted STUN message with unknown attribute. The
> | vulnerability affects applications that uses STUN including PJNATH and
> | PJSUA-LIB. The patch is available as a commit in the master branch
> | (2.13.1).
> 
> https://github.com/pjsip/pjproject/security/advisories/GHSA-9pfh-r8x4-w26w
> https://github.com/pjsip/pjproject/commit/d8440f4d711a654b511f50f79c0445b26f9dd1e1

Upstream says "Patched versions: 2.13.1" in the GitHub GHSA URL above.

> CVE-2022-23547[1]:
> | PJSIP is a free and open source multimedia communication library
> | written in C language implementing standard based protocols such as
> | SIP, SDP, RTP, STUN, TURN, and ICE. This issue is similar to
> | GHSA-9pfh-r8x4-w26w. Possible buffer overread when parsing a certain
> | STUN message. The vulnerability affects applications that uses STUN
> | including PJNATH and PJSUA-LIB. The patch is available as commit in
> | the master branch.
> 
> https://github.com/pjsip/pjproject/security/advisories/GHSA-cxwq-5g9x-x7fr
> https://github.com/pjsip/pjproject/commit/bc4812d31a67d5e2f973fbfaf950d6118226cf36

Upstream says "Patched versions: 2.13.1" in the GitHub GHSA URL above.

> CVE-2022-39269[2]:
> | PJSIP is a free and open source multimedia communication library
> | written in C. When processing certain packets, PJSIP may incorrectly
> | switch from using SRTP media transport to using basic RTP upon SRTP
> | restart, causing the media to be sent insecurely. The vulnerability
> | impacts all PJSIP users that use SRTP. The patch is available as
> | commit d2acb9a in the master branch of the project and will be
> | included in version 2.13. Users are advised to manually patch or to
> | upgrade. There are no known workarounds for this vulnerability.
> 
> https://github.com/pjsip/pjproject/security/advisories/GHSA-wx5m-cj97-4wwg
> https://github.com/pjsip/pjproject/commit/d2acb9af4e27b5ba75d658690406cec9c274c5cc

Upstream says "Patched versions: 2.13" in the GitHub GHSA URL above.

> If you fix the vulnerabilities please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.
>
> [...]
>
> Please adjust the affected versions in the BTS as needed.

As I'm neither the maintainer nor in the security team, I'm leaving
these actions to you. Hopefully simple enough, once you confirm my
findings :)

Regards,
Faidon

Bug#1036697: asterisk: CVE-2023-27585

[Faidon Liambotis]

Dear maintainer, security team,

(See #1032092 for a similar bug with an almost equivalent response)

The changelog for the asterisk 1:20.4.0~dfsg+~cs6.13.40431414-1 upload
dated 2023-08-04, currently in unstable, mentions:
>+ fixate component pjproject at upstream release 2.13.1

The sources seem to indeed indicate that the version shipped for
pjproject (aka PJSIP) is 2.13.1, which seems to have resolved the
vulnerabilities listed below.

Specifically:

On Wed, May 24, 2023 at 02:51:41PM +0200, Moritz Mühlenhoff wrote:
> CVE-2023-27585[0]:
> | PJSIP is a free and open source multimedia communication library
> | written in C. A buffer overflow vulnerability in versions 2.13 and
> | prior affects applications that use PJSIP DNS resolver. It doesn't
> | affect PJSIP users who do not utilise PJSIP DNS resolver. This
> | vulnerability is related to CVE-2022-24793. The difference is that
> | this issue is in parsing the query record `parse_query()`, while the
> | issue in CVE-2022-24793 is in `parse_rr()`. A patch is available as
> | commit `d1c5e4d` in the `master` branch. A workaround is to disable
> | DNS resolution in PJSIP config (by setting `nameserver_count` to zero)
> | or use an external resolver implementation instead.
> 
> https://github.com/pjsip/pjproject/security/advisories/GHSA-q9cp-8wcq-7pfr
> https://github.com/pjsip/pjproject/security/advisories/GHSA-p6g5-v97c-w5q4
> https://github.com/pjsip/pjproject/commit/d1c5e4da5bae7f220bc30719888bb389c905c0c5

Upstream says "Patched versions: 2.13.1" in the first GitHub GHSA URL
above (for CVE-2023-27585), and "Patched versions: 2.12.1 or later" for
the second one (for CVE-2022-24793).

> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> 
> [...]
> 
> Please adjust the affected versions in the BTS as needed.

As I'm neither the maintainer nor in the security team, I'm leaving
these actions to you. Hopefully simple enough, once you confirm my
findings :)

Regards,
Faidon

Bug#1040777: marked as done (libcrypt-xxhash-perl: Baseline violation on x86 and FTBFS everywhere else)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2023 11:51:45 +
with message-id 
and subject line Bug#1040777: fixed in libcrypt-xxhash-perl 0.06-3
has caused the Debian Bug report #1040777,
regarding libcrypt-xxhash-perl: Baseline violation on x86 and FTBFS everywhere 
else
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.)


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

https://buildd.debian.org/status/logs.php?pkg=libcrypt-xxhash-perl=0.06-1

...
   dh_auto_build -a
/usr/bin/perl Build
Building Crypt-xxHash
c++ -I. -Isrc -Iext/xxHash -I. -Isrc 
-I/usr/lib/powerpc64le-linux-gnu/perl/5.36/CORE -fPIC -D_REENTRANT 
-D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include 
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O3 -msse2 -msse4.2 -DCPP=1 
-std=c++17 -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing 
-pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -o ./ext/xxHash/xxh_x86dispatch.o 
./ext/xxHash/xxh_x86dispatch.c
c++: error: unrecognized command-line option ‘-msse2’
c++: error: unrecognized command-line option ‘-msse4.2’
error building ./ext/xxHash/xxh_x86dispatch.o from 
'./ext/xxHash/xxh_x86dispatch.c' at 
/usr/share/perl/5.36/ExtUtils/CBuilder/Base.pm line 185.
dh_auto_build: error: /usr/bin/perl Build returned exit code 2
make: *** [debian/rules:6: binary-arch] Error 25


Please remove the -msse parameters from Build.PL.
--- End Message ---
--- Begin Message ---
Source: libcrypt-xxhash-perl
Source-Version: 0.06-3
Done: Wouter Verhelst 

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

Debian distribution maintenance software
pp.
Wouter Verhelst  (supplier of updated libcrypt-xxhash-perl 
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: SHA384

Format: 1.8
Date: Mon, 07 Aug 2023 13:40:39 +0200
Source: libcrypt-xxhash-perl
Architecture: source
Version: 0.06-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Wouter Verhelst 
Closes: 1040777
Changes:
 libcrypt-xxhash-perl (0.06-3) unstable; urgency=medium
 .
   * Build.PL: drop all the custom compiler flag manglings that won't
 work on anything that isn't x86-based. Closes: #1040777
Checksums-Sha1:
 a9bc1576254402c06d74273540b74561687e60cf 1729 libcrypt-xxhash-perl_0.06-3.dsc
 83900bc8c1b842f37d55692fb49cde39eab127b1 3336 
libcrypt-xxhash-perl_0.06-3.debian.tar.xz
 bec4c8150e2459b6bfd36d96719c6fa2f94a259f 6005 
libcrypt-xxhash-perl_0.06-3_source.buildinfo
Checksums-Sha256:
 3524fe31014bb5812684025eb703a00f5e5ac84cf996119237cf1ad979f7a8b7 1729 
libcrypt-xxhash-perl_0.06-3.dsc
 acf81ac348236a9e0ab6600e9c448c3d2a6b925d34bdd1c54dcacbbeef902f9a 3336 
libcrypt-xxhash-perl_0.06-3.debian.tar.xz
 94adaa52b4baef94d7833624b0e038980e6978eb65141eed91bc0ccf4e38fcd0 6005 
libcrypt-xxhash-perl_0.06-3_source.buildinfo
Files:
 3a925b875f82a4069bf392bdfca6f90b 1729 perl optional 
libcrypt-xxhash-perl_0.06-3.dsc
 7bb2629c58f941eec9decc50a9896b89 3336 perl optional 
libcrypt-xxhash-perl_0.06-3.debian.tar.xz
 040feadbc82ea0a3360c35fc29dac915 6005 perl optional 
libcrypt-xxhash-perl_0.06-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iKgEARMJADAWIQQZhIYJILYM7Y0TCTdH038p5i64/wUCZNDZDBIcd291dGVyQGRl
Ymlhbi5vcmcACgkQR9N/KeYuuP/icQGAzqLUbfjRGZ1hl+eHNEyJ697ywvIajcEj
7wZHQgR60ffpwCTOy7W0YVJRUW3BFSELAX0S+g3i+mvT+tWDg6mYaEykHK7s1DAd
VAhuV0mBU8o/TloFB2RwNguyePaHRJ2Pagk=
=adu/
-END PGP SIGNATURE End Message ---

Processed: tagging 1037790

[Debian Bug Tracking System]

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

> tags 1037790 + fixed
Bug #1037790 {Done: Jordan Justen } [src:nix] nix: ftbfs 
with GCC-13
Added tag(s) fixed.
> thanks
Stopping processing here.

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

Bug#1042892: fixed in nvidia-graphics-drivers-legacy-390xx 390.157-4

[Ian Abbott]

Has the build server had problems building the updated packages for all 
the relevant architectures?  So far, they have only been built for armhf.


--
-=( Ian Abbott  || MEV Ltd. is a company  )=-
-=( registered in England & Wales.  Regd. number: 02862268.  )=-
-=( Regd. addr.: S11 & 12 Building 67, Europa Business Park, )=-
-=( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || www.mev.co.uk )=-

Bug#1042207: marked as done (geophar: FTBFS: ImportError: cannot import name 'BasicMeta' from 'sympy.core.core' (/usr/lib/python3/dist-packages/sympy/core/core.py))

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2023 10:34:02 +
with message-id 
and subject line Bug#1042207: fixed in geophar 18.09+dfsg1-2
has caused the Debian Bug report #1042207,
regarding geophar: FTBFS: ImportError: cannot import name 'BasicMeta' from 
'sympy.core.core' (/usr/lib/python3/dist-packages/sympy/core/core.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.)


-- 
1042207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geophar
Version: 18.09+dfsg1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=pybuild --with python3
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
> /<>/setup.py:3: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils.core import setup
> Traceback (most recent call last):
>   File "/<>/setup.py", line 4, in 
> from wxgeometrie.param import version
>   File "/<>/wxgeometrie/__init__.py", line 64, in 
> from .geolib import *
>   File "/<>/wxgeometrie/geolib/__init__.py", line 21, in 
> from .angles import (Angle_generique, Secteur_angulaire, Angle_oriente, 
> Angle,
>   File "/<>/wxgeometrie/geolib/angles.py", line 31, in 
> from .labels import Label_angle
>   File "/<>/wxgeometrie/geolib/labels.py", line 27, in 
> from .objet import Objet, Argument, Ref
>   File "/<>/wxgeometrie/geolib/objet.py", line 36, in 
> from .routines import nice_display
>   File "/<>/wxgeometrie/geolib/routines.py", line 35, in 
> from ..mathlib.printers import custom_str
>   File "/<>/wxgeometrie/mathlib/printers.py", line 29, in 
> 
> from sympy.core.core import BasicMeta
> ImportError: cannot import name 'BasicMeta' from 'sympy.core.core' 
> (/usr/lib/python3/dist-packages/sympy/core/core.py)
> E: pybuild pybuild:388: configure: plugin distutils failed with: exit code=1: 
> python3.11 setup.py config 
> dh_auto_configure: error: pybuild --configure -i python{version} -p 3.11 
> returned exit code 13
> make: *** [debian/rules:12: build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/07/26/geophar_18.09+dfsg1-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results

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 mark 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: geophar
Source-Version: 18.09+dfsg1-2
Done: Georges Khaznadar 

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated geophar package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Aug 2023 11:51:08 +0200
Source: geophar
Architecture: source
Version: 18.09+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Closes: 1042207
Changes:
 geophar (18.09+dfsg1-2) unstable; urgency=medium
 .
   * Removed uses of BasicMeta class which as this class no longer
 exists in the current version of 

Bug#1042358: openvswitch: FTBFS: make[3]: *** [Makefile:6743: manpage-check] Error 1

[Colin Watson]

On Mon, Aug 07, 2023 at 10:54:52AM +0200, Thomas Goirand wrote:
> I very much appreciate that you've sent patches for this bug, thanks for
> this. However, it is difficult to apply your patches because they are sent
> inline, and therefore hard to save on disk. Also, I would have done the work
> by  hand to avoid annoying you, but your "Message part 2" doesn't contain
> the patch at all, only a diffstat.
> 
> Could you send me the 6 patches as separate files, so I could more easily
> add them to debian/patches? Or at least send the first patch that's
> completely missing...

I don't mind sending you patches in a different format if it's helpful,
but I'm confused; I _did_ send them as separate files,
MIME-encapsulated.  How else would I have sent them as separate files?

The "PATCH v2 0/5" message is a cover letter for the patch set.  It's
not supposed to contain a patch itself.

Cheers,

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

Bug#1040447: odbc-mariadb cannot set up odcb-mariadb

[Tuukka Pasanen]

Hello,

I've just tried to replicate this on Debian 12 and with isql command and 
can't re-crete this problem. What kind of configuration do you use or 
can you provide more info about you setup?

Bug#1042349: marked as done (python-wsgi-intercept: FTBFS: failed tests)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2023 09:21:23 +
with message-id 
and subject line Bug#1042349: fixed in python-wsgi-intercept 1.9.3-3
has caused the Debian Bug report #1042349,
regarding python-wsgi-intercept: FTBFS: failed tests
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.)


-- 
1042349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042349
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-wsgi-intercept
Version: 1.9.3-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> set -e ; set -x ; for i in 3.11 ; do \
>   PYMAJOR=`echo $i | cut -d'.' -f1` ; \
>   echo "===> Testing with python$i (python$PYMAJOR)" ; \
>   WSGI_INTERCEPT_SKIP_NETWORK=true PYTHON=$i PYTHONPATH=. python$i -m 
> pytest wsgi_intercept/tests ; \
> done
> + echo 3.11
> + cut -d. -f1
> + PYMAJOR=3
> + echo ===> Testing with python3.11 (python3)
> ===> Testing with python3.11 (python3)
> + WSGI_INTERCEPT_SKIP_NETWORK=true PYTHON=3.11 PYTHONPATH=. python3.11 -m 
> pytest wsgi_intercept/tests
> = test session starts 
> ==
> platform linux -- Python 3.11.4, pytest-7.4.0, pluggy-1.2.0
> rootdir: /<>
> collected 2 items / 8 errors
> 
>  ERRORS 
> 
> __ ERROR collecting wsgi_intercept/tests/test_http_client.py 
> ___
> ImportError while importing test module 
> '/<>/wsgi_intercept/tests/test_http_client.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> wsgi_intercept/tests/test_http_client.py:1: in 
> import py.test
> E   ModuleNotFoundError: No module named 'py.test'; 'py' is not a package
>  ERROR collecting wsgi_intercept/tests/test_httplib2.py 
> 
> ImportError while importing test module 
> '/<>/wsgi_intercept/tests/test_httplib2.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> wsgi_intercept/tests/test_httplib2.py:1: in 
> import py.test
> E   ModuleNotFoundError: No module named 'py.test'; 'py' is not a package
> __ ERROR collecting wsgi_intercept/tests/test_interceptor.py 
> ___
> ImportError while importing test module 
> '/<>/wsgi_intercept/tests/test_interceptor.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> wsgi_intercept/tests/test_interceptor.py:10: in 
> import py.test
> E   ModuleNotFoundError: No module named 'py.test'; 'py' is not a package
>  ERROR collecting wsgi_intercept/tests/test_requests.py 
> 
> ImportError while importing test module 
> '/<>/wsgi_intercept/tests/test_requests.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> wsgi_intercept/tests/test_requests.py:2: in 
> import py.test
> E   ModuleNotFoundError: No module named 'py.test'; 'py' is not a package
>  ERROR collecting wsgi_intercept/tests/test_response_headers.py 
> 
> ImportError while importing test module 
> '/<>/wsgi_intercept/tests/test_response_headers.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.11/importlib/__init__.py:126: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> wsgi_intercept/tests/test_response_headers.py:11: in 
> import py.test
> E   ModuleNotFoundError: No module named 'py.test'; 'py' is not a package
> _ ERROR collecting wsgi_intercept/tests/test_urllib.py 
> _
> ImportError while importing test module 
> '/<>/wsgi_intercept/tests/test_urllib.py'.
> Hint: make sure your test modules/packages have valid 

Bug#1042358: openvswitch: FTBFS: make[3]: *** [Makefile:6743: manpage-check] Error 1

[Thomas Goirand]

Hi Colin,

I very much appreciate that you've sent patches for this bug, thanks for 
this. However, it is difficult to apply your patches because they are 
sent inline, and therefore hard to save on disk. Also, I would have done 
the work by  hand to avoid annoying you, but your "Message part 2" 
doesn't contain the patch at all, only a diffstat.


Could you send me the 6 patches as separate files, so I could more 
easily add them to debian/patches? Or at least send the first patch 
that's completely missing...


Cheers,

Thomas Goirand (zigo)

Processed: Bug#1042349 marked as pending in python-wsgi-intercept

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042349 [src:python-wsgi-intercept] python-wsgi-intercept: FTBFS: failed 
tests
Added tag(s) pending.

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

Bug#1042349: marked as pending in python-wsgi-intercept

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1042349 in python-wsgi-intercept 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/openstack-team/python/python-wsgi-intercept/-/commit/7a68fcb59966319b0bfc6dfd59a67cbf7cadc387


Add refer_to_pytest_not_py.test_in_tests.patch (Closes: #1042349).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042349

Bug#1043182: odr-dabmux FTBFS with gcc 13

[Adrian Bunk]

Source: odr-dabmux
Version: 4.4.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=odr-dabmux=riscv64=4.4.0-1=1691389622=0

...
lib/ReedSolomon.cpp: In member function ‘int ReedSolomon::encode(void*, void*, 
size_t)’:
lib/ReedSolomon.cpp:81:5: error: ‘uint8_t’ was not declared in this scope
   81 | uint8_t* input = reinterpret_cast(data);
  | ^~~
lib/ReedSolomon.cpp:39:1: note: ‘uint8_t’ is defined in header ‘’; did 
you forget to ‘#include ’?
   38 | #include 
  +++ |+#include 
   39 | 
...

Processed: closing 1037571

[Debian Bug Tracking System]

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

> close 1037571 1.1.2-4
Bug #1037571 [src:aghermann] aghermann: ftbfs with GCC-13
The source 'aghermann' and version '1.1.2-4' do not appear to match any binary 
packages
Marked as fixed in versions aghermann/1.1.2-4.
Bug #1037571 [src:aghermann] aghermann: ftbfs with GCC-13
Marked Bug as done
> thanks
Stopping processing here.

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