Bug#1057950: marked as done (dask.distributed: FTBFS: TypeError: not all arguments converted during string formatting)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2024 06:53:23 +
with message-id 
and subject line Bug#1057950: fixed in dask.distributed 2023.12.1+ds-1
has caused the Debian Bug report #1057950,
regarding dask.distributed: FTBFS: TypeError: not all arguments converted 
during string formatting
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.)


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

Package: src:dask.distributed
Version: 2023.8.0+ds.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
 debian/rules binary
dh binary --with python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
rm -f distributed/comm/tests/__init__.py
set -e; \
for p in distributed/http/static/js/anime.js 
distributed/http/static/js/reconnecting-websocket.js; do \
uglifyjs -o $p debian/missing-sources/$p ; \
done
chmod a-x distributed/tests/test_utils_test.py
dh_auto_build

[... snipped ...]

copying build/lib/distributed/cli/tests/__init__.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli/tests
copying build/lib/distributed/cli/tests/test_dask_spec.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli/tests
copying build/lib/distributed/cli/tests/test_dask_worker.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli/tests
copying build/lib/distributed/cli/tests/test_dask_scheduler.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli/tests
copying build/lib/distributed/cli/tests/test_dask_ssh.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli/tests
copying build/lib/distributed/cli/tests/test_tls_cli.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli/tests
copying build/lib/distributed/cli/dask_worker.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli
copying build/lib/distributed/cli/dask_scheduler.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli
copying build/lib/distributed/cli/dask_spec.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli
copying build/lib/distributed/cli/dask_ssh.py -> 
build/bdist.linux-x86_64/wheel/distributed/cli
copying build/lib/distributed/active_memory_manager.py -> 
build/bdist.linux-x86_64/wheel/distributed
copying build/lib/distributed/versions.py -> 
build/bdist.linux-x86_64/wheel/distributed
copying build/lib/distributed/lock.py -> 
build/bdist.linux-x86_64/wheel/distributed
creating build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/local.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/utils.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/__init__.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
creating build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_cluster.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_adaptive_core.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_ssh.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_spec_cluster.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_local.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_slow_adaptive.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_deploy_utils.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_subprocess.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_old_ssh.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/tests/test_adaptive.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy/tests
copying build/lib/distributed/deploy/adaptive.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/cluster.py -> 
build/bdist.linux-x86_64/wheel/distributed/deploy
copying build/lib/distributed/deploy/adaptive_core.py -> 

Bug#1055021: marked as done (linux: mips64el loongson3 kernel crashes when running cmake)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2024 06:47:08 +
with message-id 
and subject line Bug#1055021: fixed in linux 6.1.69-1
has caused the Debian Bug report #1055021,
regarding linux: mips64el loongson3 kernel crashes when running cmake
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.)


-- 
1055021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 5.10.197-1
Severity: grave
Tags: upstream patch
X-Debbugs-Cc: d...@debian.org, debian-m...@lists.debian.org

The loongson3 flavour of the mips64el kernel crash when running cmake:

| [ 4390.501529] do_cpu invoked from kernel context![#1]:
| [ 4390.506483] CPU: 3 PID: 24061 Comm: iou-sqp-22284 Not tainted 
5.10.0-26-loongson-3 #1 Debian 5.10.197-1
| [ 4390.515820] Hardware name: Loongson 
Lemote-3A4000-7A-1w-V1.00-A1901/Lemote-3A4000-7A-1w-V1.00-A1901, BIOS 
Loongson-PMON-V3.3-20201222 12/22/2020
| [ 4390.528699] $ 0 :  80bf9030 0001 
98020f844000
| [ 4390.536669] $ 4 : 9801017bb2c0 80dbc0b8 0008 
02008200
| [ 4390.544634] $ 8 : 0001 0001  
02e27c19
| [ 4390.552600] $12 : 5400cce0 80199c00 01ea 
01ea
| [ 4390.560565] $16 : 980100253700 80ecc740  
9800023cb8c0
| [ 4390.568530] $20 : 80ecdce0 9801017bb2c0 9801017bb8e0 

| [ 4390.576495] $24 : 0028 98020f847e58
| [ 4390.584461] $28 : 98020f844000 98020f847d40 9800023cb8c0 
80bf925c
| [ 4390.592426] Hi : 00de
| [ 4390.595974] Lo : d70a40ec
| [ 4390.599532] epc : 802177c0 _save_fp+0x10/0xa0
| [ 4390.604727] ra : 80bf925c __schedule+0x804/0xe08
| [ 4390.610263] Status: 5400cce2 KX SX UX KERNEL EXL
| [ 4390.614949] Cause : 102c (ExcCode 0b)
| [ 4390.618930] PrId : 0014c004 (ICT Loongson-3)
| [ 4390.623257] Modules linked in: asix usbnet mii sg ip6t_REJECT 
nf_reject_ipv6 ip6table_filter ip6_tables nfnetlink_log nfnetlink xt_hashlimit 
ipt_REJECT nf_reject_ipv4 xt_NFLOG xt_multiport xt_tcpudp xt_state xt_conntrack 
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c iptable_filter sch_fq 
tcp_bbr fuse drm drm_panel_orientation_quirks configfs ip_tables x_tables 
autofs4 ext4 crc16 mbcache jbd2 crc32c_generic ohci_pci dm_mod r8169 realtek 
mdio_devres ohci_hcd ehci_pci of_mdio xhci_pci xhci_hcd ehci_hcd fixed_phy 
libphy usbcore usb_common
| [ 4390.671116] Process iou-sqp-22284 (pid: 24061, 
threadinfo=743a6e5b, task=63cca72a, tls=00fff0de98e0)
| [ 4390.681930] Stack : 80ed  80ed 
98020f6e8c40
| [ 4390.689897] 98020004 d37c8307c148dccb 9801017bb2c0 

| [ 4390.697863]  0001 90
| [ 4390.721759] 980104957480 98020f6e8c00  
80ed
| [ 4390.729724] 98020f6e8c40 98020f6e8c08  

| [ 4390.737689]  9801017bb2c0 802c61f8 
98020f6e8c48
| [ 4390.745655] 98020f6e8c48 2d7071732d756f69 003438323232 
d37c8307c148dccb
| [ 4390.753621] 807106e0 98020f6e8c00 9801097e90c8 
7400cce0
| [ 4390.761588] ...
| [ 4390.764017] Call Trace:
| [ 4390.766453] [] _save_fp+0x10/0xa0
| [ 4390.771306] [] __schedule+0x804/0xe08
| [ 4390.776497] [] schedule+0x58/0x150
| [ 4390.781432] [] io_sq_thread+0x550/0x578
| [ 4390.786798] [] ret_from_kernel_thread+0x14/0x1c
| [ 4390.792856]
| [ 4390.794330] Code: 000c6940 05a10011   f4830b10 f4850b30 
f4870b50 f4890b70 f48b0b90
| [ 4390.804038]
| [ 4411.502993] rcu: INFO: rcu_preempt self-detected stall on CPU
| [ 4411.508728] rcu: 1-...!: (5250 ticks this GP) 
idle=2c6/1/0x4002 softirq=1149627/1149627 fqs=4
| [ 4411.518413] (t=5254 jiffies g=735145 q=4914963)
| [ 4411.522999] rcu: rcu_preempt kthread starved for 5248 jiffies! g735145 
f0x2 RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=2
| [ 4411.533458] rcu: Unless rcu_preempt kthread gets sufficient CPU time, OOM 
is now expected behavior.
| [ 4411.542535] rcu: RCU grace-period kthread stack dump:
| [ 4411.547552] task:rcu_preempt state:R stack: 0 pid: 13 ppid: 2 
flags:0x0010
| [ 4411.555860] Stack : 80ed 80bff978 80ed 
8031bbd4
| [ 4411.563826] 0004 d37c8307c148dccb 98010025 
00208040
| [ 4411.571791] 80ed 9801002c7c98 

Processed: Bug#1057950 marked as pending in dask.distributed

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1057950 [src:dask.distributed] dask.distributed: FTBFS: TypeError: not all 
arguments converted during string formatting
Added tag(s) pending.

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

Bug#1057347: marked as done (vips: increase the timeout further and make it unconditional)

[Debian Bug Tracking System]

Your message dated Wed, 03 Jan 2024 06:34:08 +
with message-id 
and subject line Bug#1057347: fixed in vips 8.15.1-1
has caused the Debian Bug report #1057347,
regarding vips: increase the timeout further and make it unconditional
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.)


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

1. Make the timeout much larger

The current timeout is not sufficient on all MIPS buildds:
https://buildd.debian.org/status/package.php?p=vips

A generous timeout is cheap, since it only has any negative
effect in the rare case where the test actually hangs.

For passing tests and even for test failures a timeout has no effect.


2. Make the timeout unconditional

As noted above a more generous timeout is cheap,
an unconditional increase is less hassle than manually
tracking buildd speed for every architecture
(e.g. Alpha also has slow qemu buildds where the tests
currently time out).


--- vips-8.15.0/debian/rules.old2023-12-03 20:32:41.049820544 +
+++ vips-8.15.0/debian/rules2023-12-03 20:05:30.918121415 +
@@ -12,11 +12,7 @@
 DESTDIR = $(CURDIR)/debian/tmp
 
 override_dh_auto_test:
-ifeq (, $(filter hppa hurd-i386 mips64el mipsel sparc64, $(DEB_BUILD_ARCH)))
-   LD_LIBRARY_PATH=$(CURDIR)/obj-$(DEB_BUILD_GNU_TYPE)/libvips dh_auto_test
-else
-   LD_LIBRARY_PATH=$(CURDIR)/obj-$(DEB_BUILD_GNU_TYPE)/libvips 
dh_auto_test -- --timeout-multiplier=3
-endif
+   LD_LIBRARY_PATH=$(CURDIR)/obj-$(DEB_BUILD_GNU_TYPE)/libvips 
dh_auto_test -- --timeout-multiplier=10
 
 override_dh_auto_configure:
dh_auto_configure -- \
--- End Message ---
--- Begin Message ---
Source: vips
Source-Version: 8.15.1-1
Done: Laszlo Boszormenyi (GCS) 

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated vips package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 03 Jan 2024 06:58:38 +0100
Source: vips
Architecture: source
Version: 8.15.1-1
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 1057347
Changes:
 vips (8.15.1-1) unstable; urgency=medium
 .
   * New upstream release.
 .
   [ Adrian Bunk  ]
   * Increase the self-testing timeout further and make it unconditional
 (closes: #1057347).
Checksums-Sha1:
 055a6465997ce4fd66e79b2f0f9c7a3893d5f8af 2462 vips_8.15.1-1.dsc
 6cb406ebd00d9736277d19e3147c87641e765627 21175035 vips_8.15.1.orig.tar.gz
 aecd9b3a4f6cff3faaa7ec36156f65a6e392f643 10356 vips_8.15.1-1.debian.tar.xz
Checksums-Sha256:
 632d4feea105c5f07e0e28b1e4386ce6cde772b26acfbdadd5cf8bf4786bcc52 2462 
vips_8.15.1-1.dsc
 5701445a076465a3402a135d13c0660d909beb8efc4f00fbbe82392e243497f2 21175035 
vips_8.15.1.orig.tar.gz
 9a7e1cfe72187530754b859ecf298ca46e04bb35ca80ea32931b28a15ca405f8 10356 
vips_8.15.1-1.debian.tar.xz
Files:
 4b4d3b49dce0c8f134fea091dac5bfad 2462 libs optional vips_8.15.1-1.dsc
 e4bf7ef499179d8c95b0e1c4b538bd37 21175035 libs optional vips_8.15.1.orig.tar.gz
 72655f8ee89867660e8f0ec524dff24c 10356 libs optional 
vips_8.15.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmWU+8AACgkQ3OMQ54ZM
yL+UVw/8C8V7NtcHBEBgl1iz4kImxR/n5ZptNNiUnCzy3BTukIffwhmcDAN2IkKy
uQggkNhWXliau2GvbINWDUsfabAU24DAhVgRo9sDgexas2EgTHEqjvoTRhgO316b
mK2WxRbfznge7Ey4RxCHUJBv6ACraOaxloPQ1S0F89I5hU+lgO3+2tD0wNv1GXzf
OKdJlhi6sp1huXPBVus4cfL3NDCSLpPUNkgpEf+2fCp5XTqdbcsNwKfmzSY1lizo
KTJK381tBDlBwlog/tEsgCMUCwdYa5lthc5rB3Pucs/RLnPLyhbi0f6l4zH+KiTF
gZHLU5veUc/ijnvhaA6uS6d6+PZdAjJVDqRUXk4nzfdCWXHo/cdtHH21E+bbRrZd
26rnPkPe+acv1VLeyM1Zk52d9AzfofKcjgwK+dll2Uy4Iy8NuCBfLa6w1LgLcR9R
Jar/4O6g5CCFHfN4cXhkJrLoIK/9YjAeO5VFTEKGYAbTl8VmKyEuymSOYRsw7OUe
aSEV6NSXVfQxq2GRUdDCUv5/AutvKwr9eLooCw0+O9OA5rjmd0AgCIDZdgzQxujM

Bug#1057950: marked as pending in dask.distributed

[Julian Gilbey]

Control: tag -1 pending

Hello,

Bug #1057950 in dask.distributed 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/dask.distributed/-/commit/3251532057218005ba71d408f080f7b56985835b


Fix sphinx config error (closes: #1057950)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1057950

Processed: retitle 1059829 to node-html5-qrcode: Network access during build

[Debian Bug Tracking System]

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

> retitle 1059829 node-html5-qrcode: Network access during build
Bug #1059829 [node-html5-qrcode] node-html5-qrcode: Build using libraries 
downloaded from Internet during build
Changed Bug title to 'node-html5-qrcode: Network access during build' from 
'node-html5-qrcode: Build using libraries downloaded from Internet during 
build'.
> thanks
Stopping processing here.

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

Processed: tagging 1059829

[Debian Bug Tracking System]

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

> tags 1059829 + patch
Bug #1059829 [node-html5-qrcode] node-html5-qrcode: Build using libraries 
downloaded from Internet during build
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1013395: Bug #1013395: mpdecimal

[Stefan Krah]

The patch was slightly messed up. Attaching a new version.
diff -Naur a/debian/README.Debian b/debian/README.Debian
--- a/debian/README.Debian	1970-01-01 01:00:00.0 +0100
+++ b/debian/README.Debian	2023-11-06 16:50:21.472367979 +0100
@@ -0,0 +1,4 @@
+Due to the Debian policy for prebuilt HTML documentation the mpdecimal
+documentation is no longer shipped in Debian.
+
+Please see https://www.bytereef.org/mpdecimal/ for the documentation.
diff -Naur a/debian/control b/debian/control
--- a/debian/control	2021-03-25 11:54:28.0 +0100
+++ b/debian/control	2023-11-06 16:50:21.472367979 +0100
@@ -2,7 +2,6 @@
 Priority: optional
 Maintainer: Matthias Klose 
 Build-Depends: debhelper (>= 12),
-Build-Depends-Indep: python3-sphinx
 Standards-Version: 4.5.1
 Section: libs
 Homepage: https://www.bytereef.org/mpdecimal/index.html
@@ -11,7 +10,7 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: libmpdec3 (= ${binary:Version}), ${sphinxdoc:Depends}, ${misc:Depends}
+Depends: libmpdec3 (= ${binary:Version}), ${misc:Depends}
 Suggests: libmpdec-doc
 Description: library for decimal floating point arithmetic (development files)
  mpdecimal is a package for correctly-rounded arbitrary precision decimal
@@ -27,12 +26,3 @@
 Description: library for decimal floating point arithmetic (runtime library)
  mpdecimal is a package for correctly-rounded arbitrary precision decimal
  floating point arithmetic.
-
-Package: libmpdec-doc
-Section: doc
-Architecture: all
-Multi-Arch: foreign
-Depends: ${misc:Depends}
-Description: library for decimal floating point arithmetic (documentation)
- mpdecimal is a package for correctly-rounded arbitrary precision decimal
- floating point arithmetic.
diff -Naur a/debian/copyright b/debian/copyright
--- a/debian/copyright	2021-01-10 18:00:58.0 +0100
+++ b/debian/copyright	2023-11-06 16:50:21.472367979 +0100
@@ -4,7 +4,7 @@
 
 Files: *
 Copyright: Copyright (c) 2008-2020 Stefan Krah. All rights reserved.
-License: BSD
+License: BSD-2-clause
  Redistribution and use in source and binary forms, with or without
  modification, are permitted provided that the following conditions
  are met:
diff -Naur a/debian/libmpdec-dev.docs b/debian/libmpdec-dev.docs
--- a/debian/libmpdec-dev.docs	2018-04-23 09:57:17.0 +0200
+++ b/debian/libmpdec-dev.docs	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-README.txt
diff -Naur a/debian/libmpdec3.symbols b/debian/libmpdec3.symbols
--- a/debian/libmpdec3.symbols	2021-03-25 11:54:10.0 +0100
+++ b/debian/libmpdec3.symbols	2023-11-06 16:50:21.472367979 +0100
@@ -346,146 +346,4 @@
  mpd_xor@Base 2.3
  mpd_zerocoeff@Base 2.3
 libmpdec++.so.3 libmpdec3 #MINVER#
- _ZN7decimal10MaxContextEv@Base 2.5
- (optional=lto)_ZN7decimal10ValueErrorD0Ev@Base 2.5
- (optional=lto)_ZN7decimal10ValueErrorD1Ev@Base 2.5
- (optional=lto)_ZN7decimal10ValueErrorD2Ev@Base 2.5
- _ZN7decimal11IEEEContextEi@Base 2.5
- (optional=lto)_ZN7decimal11MallocErrorD0Ev@Base 2.5
- (optional=lto)_ZN7decimal11MallocErrorD1Ev@Base 2.5
- (optional=lto)_ZN7decimal11MallocErrorD2Ev@Base 2.5
- (optional=lto)_ZN7decimal12RuntimeErrorD0Ev@Base 2.5
- (optional=lto)_ZN7decimal12RuntimeErrorD1Ev@Base 2.5
- (optional=lto)_ZN7decimal12RuntimeErrorD2Ev@Base 2.5
- (optional=lto)_ZN7decimal14DivisionByZeroD0Ev@Base 2.5
- (optional=lto)_ZN7decimal14DivisionByZeroD1Ev@Base 2.5
- (optional=lto)_ZN7decimal14DivisionByZeroD2Ev@Base 2.5
- (optional=lto)_ZN7decimal16ConversionSyntaxD0Ev@Base 2.5
- (optional=lto)_ZN7decimal16ConversionSyntaxD1Ev@Base 2.5
- (optional=lto)_ZN7decimal16ConversionSyntaxD2Ev@Base 2.5
- (optional=lto)_ZN7decimal16DecimalExceptionD0Ev@Base 2.5
- (optional=lto)_ZN7decimal16DecimalExceptionD1Ev@Base 2.5
- (optional=lto)_ZN7decimal16DecimalExceptionD2Ev@Base 2.5
- (optional=lto)_ZN7decimal16InvalidOperationD0Ev@Base 2.5
- (optional=lto)_ZN7decimal16InvalidOperationD1Ev@Base 2.5
- (optional=lto)_ZN7decimal16InvalidOperationD2Ev@Base 2.5
- _ZN7decimal16context_templateE@Base 2.5
- (optional=lto)_ZN7decimal17DivisionUndefinedD0Ev@Base 2.5
- (optional=lto)_ZN7decimal17DivisionUndefinedD1Ev@Base 2.5
- (optional=lto)_ZN7decimal17DivisionUndefinedD2Ev@Base 2.5
- (optional=lto)_ZN7decimal18DivisionImpossibleD0Ev@Base 2.5
- (optional=lto)_ZN7decimal18DivisionImpossibleD1Ev@Base 2.5
- (optional=lto)_ZN7decimal18DivisionImpossibleD2Ev@Base 2.5
- (optional=lto)_ZN7decimal20IEEEInvalidOperationD0Ev@Base 2.5
- (optional=lto)_ZN7decimal20IEEEInvalidOperationD1Ev@Base 2.5
- (optional=lto)_ZN7decimal20IEEEInvalidOperationD2Ev@Base 2.5
- (optional=lto)_ZN7decimal7ClampedD0Ev@Base 2.5
- (optional=lto)_ZN7decimal7ClampedD1Ev@Base 2.5
- (optional=lto)_ZN7decimal7ClampedD2Ev@Base 2.5
- _ZN7decimal7Context7raiseitEj@Base 2.5
- (arch=any-i386 armel armhf hppa m68k mips mipsel powerpc powerpcspe s390 sh4 sparc x32)_ZN7decimal7ContextC1Ejii@Base 2.5
- (arch=any-i386 armel armhf hppa m68k mips mipsel powerpc powerpcspe s390 sh4 sparc x32)_ZN7decimal7ContextC2Ejii@Base 

Bug#1056239: marked as done (dask's autopkg tests fail with Python 3.12)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2024 22:37:51 +
with message-id 
and subject line Bug#1056239: fixed in dask 2023.12.1+dfsg-1
has caused the Debian Bug report #1056239,
regarding dask's autopkg tests fail with Python 3.12
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.)


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

Package: src:dask
Version: 2023.8.0+dfsg-2
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

[...]
1331s === short test summary info 

1331s FAILED dataframe/io/tests/test_sql.py::test_division_or_partition 
- assert (T...
1331s = 1 failed, 10610 passed, 1565 skipped, 8 deselected, 49 xfailed, 
14 xpassed, 177 warnings in 918.35s (0:15:18) =



complete test log at
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/d/dask/20231118_184103_b5424@/log.gz
--- End Message ---
--- Begin Message ---
Source: dask
Source-Version: 2023.12.1+dfsg-1
Done: Julian Gilbey 

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

Debian distribution maintenance software
pp.
Julian Gilbey  (supplier of updated dask 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: Tue, 02 Jan 2024 21:51:10 +
Source: dask
Architecture: source
Version: 2023.12.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Julian Gilbey 
Closes: 1053947 1056239
Changes:
 dask (2023.12.1+dfsg-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream version (closes: #1053947, #1056239)
   * Skip test known to fail on Python 3.12
Checksums-Sha1:
 2aa74b40b0726d768b2c7e91c187d508eb226565 3179 dask_2023.12.1+dfsg-1.dsc
 4fc997c18ce680e857956200d0db74340312d150 8223696 
dask_2023.12.1+dfsg.orig.tar.xz
 bd96d183b915a6d09220be67056886ba79e4cb46 45480 
dask_2023.12.1+dfsg-1.debian.tar.xz
 14f2d083e4c823ed6263eecc3a27caf3da9bc90d 11628 
dask_2023.12.1+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 4ba6e34418effb35e69ea828071c1d728007aa889d0c56c82bb53c188b15e7bb 3179 
dask_2023.12.1+dfsg-1.dsc
 cbb5a2c6860116b2a08be2de3c01e30f3f47bbed172f53612fa6de94e0d1bd16 8223696 
dask_2023.12.1+dfsg.orig.tar.xz
 b074edc6dda685625d3714a493bee74ed1015c9ffcc6caa5b7e1854e6d2c1b1b 45480 
dask_2023.12.1+dfsg-1.debian.tar.xz
 970a89eb782853feae04f06c4629c75b88cf125fcb8947fcd5e5377d56371ce6 11628 
dask_2023.12.1+dfsg-1_amd64.buildinfo
Files:
 121f784f222180d91fc21c9963858c93 3179 python optional dask_2023.12.1+dfsg-1.dsc
 7919a4c03b15eb4cb28a20ddb6e75bcb 8223696 python optional 
dask_2023.12.1+dfsg.orig.tar.xz
 9d8da02af70b5d8f856ded67541f9102 45480 python optional 
dask_2023.12.1+dfsg-1.debian.tar.xz
 37feb237e5cbbe55bd70cef7a389fbea 11628 python optional 
dask_2023.12.1+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfhrD+iemSShMMj72aVxCkxbAe/4FAmWUi4gACgkQaVxCkxbA
e/4I5Q/9EzOzPWswrXMDdilQfEVrr/o4Nm0lfb0SE3W6msCQlvM/u0hQ+ZEJn0Bc
yQphAQmaQcyl/GOsbWSvUHKkjd7nXh4R+7OQh4puyfkFF9sxjql2imROmzuh39J6
rkul0EhjYeh9GzSRUuqaXeVHfQh1CtIpCCyce/87PfETFrLluNnJ6yY1+xDLXLK9
h4VdFHJJ/kZSDqR/AZdJCd57FOrO6UMAuNPCxvnbprps1XpB1OFn+2xdjnifl/z9
rS62SRnc/OKA9ktQD0TdtZ0kNSU1LCRbbO8LNYxek++OcPjLFKmzYfKanykPkapO
IlyOM8qjETiHJ1dRD3HgWjhCdF925CZMXEMdN1QBJuCQ1j1ONBX0+8Yqb9M18b1p
Xn8Px3rkV99la6+5QDWiCfhaf4wcraBqKXFqyKLQg7v8L4dS0BjJZ3eJaJLfUtPG
UhsjkyDH4celwJ08iw4qWzHO+ivvKFGNZLKC5rvRYcrgeMxPPP0jNHHhQBADphCw
rXT1rAqkLruB9pSKGzjMLUbxCSwONDJGxgGn2VhDo06qXaBNYNwIcjrzK4fzmhvp
nAXGHHCih2GgAAoBV1pZSv5q2YKOLk81KWbuH/ki6BCgDOpWl7QP1dxvYh8dzgmV
rz6xnnIJHOchD6EyGJs2pulexJwpSHAjACkzoSJM2fFrkRJBtbw=
=jJgb
-END PGP SIGNATURE End Message ---

Bug#1040092: marked as done (python-pyftpdlib: deprecation of Python libraries asyncore and asynchat)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2024 21:50:09 +
with message-id 
and subject line Bug#1040092: fixed in python-pyftpdlib 1.5.9-1
has caused the Debian Bug report #1040092,
regarding python-pyftpdlib: deprecation of Python libraries asyncore and 
asynchat
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.)


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

Source: python-pyftpdlib
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: asyncore-asynchat-deprecation

Dear maintainer(s),

In Python 3.6, asyncore and asynchat have been formally marked as 
deprecated. Code that imports these libraries will no longer work from 
Python 3.12, which is currently in Trixie.


Since python-pyftpdlib uses either of these Python libraries, please 
prepare for this removal and migrate away from them.


See this link for more details: 
https://peps.python.org/pep-0594/#deprecated-modules


Cheers,

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_0xE1E5457C8BAD4113.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-pyftpdlib
Source-Version: 1.5.9-1
Done: Alexandre Detiste 

We believe that the bug you reported is fixed in the latest version of
python-pyftpdlib, 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.
Alexandre Detiste  (supplier of updated python-pyftpdlib 
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, 02 Jan 2024 20:49:07 +0100
Source: python-pyftpdlib
Architecture: source
Version: 1.5.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Alexandre Detiste 
Closes: 1040092 1058974
Changes:
 python-pyftpdlib (1.5.9-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 1.5.9
   * add d/gbp.conf matching current Salsa setup
   * new release vendors a copy of old asyncore and asynchat (Closes: #1040092)
   * remove obsolete dependency on python3-unittest2 (Closes: #1058974)
   * refresh patch
Checksums-Sha1:
 37f37a937481d2bc022ed8ee2d1c5bb88f42e34b 2289 python-pyftpdlib_1.5.9-1.dsc
 978471c53aa94e50ebb7c03164b361f6ac2d65e5 260537 
python-pyftpdlib_1.5.9.orig.tar.gz
 faeb3167ca5cdfebe8902fe4aba976e6ad2505aa 6908 
python-pyftpdlib_1.5.9-1.debian.tar.xz
 0537ca7294ca3117ed1037857997949d082ab6eb 8343 
python-pyftpdlib_1.5.9-1_source.buildinfo
Checksums-Sha256:
 e7c563fe2edd649066d63d11b853a4cbbc850b0278fcd60baaf06eb584532867 2289 
python-pyftpdlib_1.5.9-1.dsc
 7403b762ea16e4c1e5805b81084c09cd099ba6a8f7dbbcaf3e331a889ea883fe 260537 
python-pyftpdlib_1.5.9.orig.tar.gz
 ec4f2a32ab638b010c113edeb616caeccea7dc0142b24ea370ac35c3fcc4492a 6908 
python-pyftpdlib_1.5.9-1.debian.tar.xz
 15607e5756434fd954ec9541cd6b59a9392c9452f3d1dad350bfd818b27e5444 8343 
python-pyftpdlib_1.5.9-1_source.buildinfo
Files:
 c7e58998811fc6fba3078a1ba493028d 2289 python optional 
python-pyftpdlib_1.5.9-1.dsc
 e1ce09ca9b3e2c108f1dff22fbc177c8 260537 python optional 
python-pyftpdlib_1.5.9.orig.tar.gz
 2b187ce1d228ade2abe98bb7aa66522b 6908 python optional 
python-pyftpdlib_1.5.9-1.debian.tar.xz
 22d6339de6074a2cebd6ee59a6ae2c74 8343 python optional 
python-pyftpdlib_1.5.9-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmWUaicRHHRjaGV0QGRl
Ymlhbi5vcmcACgkQMfMURUShdBohFQ/8DQnRRm4O7dvaxuJpmbrpvLC5svQ6obna
NwVuPiVKOBiRC/fNsvK6p/q55ZmkVBDuMxj/fWCIXU5tdSO281lHV3B8OXpgOV4d
MWd08nkjhEqjL59BOtBEwHhw/uMNmyDaLsQ932aWb1Mz0siikSt9Kkb7phkd+zWV
rXyv1qUjf/FPeoF7m65vDxH0T1utDDVBHFfJ/YDar8P4WyN/HDLz5Iwl6WLNB/lJ
Ozakib7SWiAQ3sYmDKZKEaGgFB/c8nIzWRQ/H7bSSQZdXaOuyvY5rwknhA6Jo1qO
xrNvC+ZgRZ5pR+aFPJazTw9CwvcSzXNnNALKFxUdr/osT8FwFxPqaxedlAIKtLvT
sOdnHL25gHbjkbytXZxSWRtKeidY48lL83t/Lg+iMBnyT+yjwqBnuU7Zeqju9sVq
ZbOT7PxSOA73UY/eVJF8SK/k8fSty9O8VlUrTXZ2OTlp+2Qx8y3RZKRlGKiK20Pw
XUXvqW+FtllA4OvHfnHjOG0JqlDEh8epwvu+jk9ow7eTR0ekRnC7URqc+WC54C9o

Bug#1013395: Bug #1013395: mpdecimal

[Stefan Krah]

Hi,

I think the solution is pretty simple, same as for libgmp, which ships without
documentation.

The patch removes the documentation, adds a note similar to the libgmp note,
fixes a couple of warnings.

For ease of maintenance it also removes the C++ symbol list. libmpdec++
is mostly a header library, so users will not have any heightened symbol
stability expectations.

The next mpdecimal release will have separate HTML documentation and
include small man pages that point to the documentation.

mpdecimal does not include the rst sources because new issues arise
with new Sphinx releases, which would then again not pass dh_sphinxdoc.

I might switch to man pages entirely in the future.


Stefan Krah




diff -Naur a/debian/README.Debian b/debian/README.Debian
--- a/debian/README.Debian  1970-01-01 01:00:00.0 +0100
+++ b/debian/README.Debian  2023-11-06 16:50:21.472367979 +0100
@@ -0,0 +1,4 @@
+Due to the Debian policy for prebuilt HTML documentation the mpdecimal
+documentation is no longer shipped in Debian.
+
+Please see https://www.bytereef.org/mpdecimal/ for the documentation.
diff -Naur a/debian/control b/debian/control
--- a/debian/control2021-03-25 11:54:28.0 +0100
+++ b/debian/control2023-11-06 16:50:21.472367979 +0100
@@ -2,7 +2,6 @@
 Priority: optional
 Maintainer: Matthias Klose 
 Build-Depends: debhelper (>= 12),
-Build-Depends-Indep: python3-sphinx
 Standards-Version: 4.5.1
 Section: libs
 Homepage: https://www.bytereef.org/mpdecimal/index.html
@@ -11,7 +10,7 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: libmpdec3 (= ${binary:Version}), ${sphinxdoc:Depends}, ${misc:Depends}
+Depends: libmpdec3 (= ${binary:Version}),   ${misc:Depends}
 Suggests: libmpdec-doc
 Description: library for decimal floating point arithmetic (development files)
  mpdecimal is a package for correctly-rounded arbitrary precision decimal
@@ -27,12 +26,3 @@
 Description: library for decimal floating point arithmetic (runtime library)
  mpdecimal is a package for correctly-rounded arbitrary precision decimal
  floating point arithmetic.
-
-Package: libmpdec-doc
-Section: doc
-Architecture: all
-Multi-Arch: foreign
-Depends: ${misc:Depends}
-Description: library for decimal floating point arithmetic (documentation)
- mpdecimal is a package for correctly-rounded arbitrary precision decimal
- floating point arithmetic.
diff -Naur a/debian/copyright b/debian/copyright
--- a/debian/copyright  2021-01-10 18:00:58.0 +0100
+++ b/debian/copyright  2023-11-06 16:50:21.472367979 +0100
@@ -4,7 +4,7 @@

 Files: *
 Copyright: Copyright (c) 2008-2020 Stefan Krah. All rights reserved.
-License: BSD
+License: BSD-2-clause
  Redistribution and use in source and binary forms, with or without
  modification, are permitted provided that the following conditions
  are met:
diff -Naur a/debian/libmpdec-dev.docs b/debian/libmpdec-dev.docs
--- a/debian/libmpdec-dev.docs  2018-04-23 09:57:17.0 +0200
+++ b/debian/libmpdec-dev.docs  1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-README.txt
diff -Naur a/debian/libmpdec3.symbols b/debian/libmpdec3.symbols
--- a/debian/libmpdec3.symbols  2021-03-25 11:54:10.0 +0100
+++ b/debian/libmpdec3.symbols  2023-11-06 16:50:21.472367979 +0100
@@ -346,146 +346,4 @@
  mpd_xor@Base 2.3
  mpd_zerocoeff@Base 2.3
 libmpdec++.so.3 libmpdec3 #MINVER#
- _ZN7decimal10MaxContextEv@Base 2.5
- (optional=lto)_ZN7decimal10ValueErrorD0Ev@Base 2.5
- (optional=lto)_ZN7decimal10ValueErrorD1Ev@Base 2.5
- (optional=lto)_ZN7decimal10ValueErrorD2Ev@Base 2.5
- _ZN7decimal11IEEEContextEi@Base 2.5
- (optional=lto)_ZN7decimal11MallocErrorD0Ev@Base 2.5
- (optional=lto)_ZN7decimal11MallocErrorD1Ev@Base 2.5
- (optional=lto)_ZN7decimal11MallocErrorD2Ev@Base 2.5
- (optional=lto)_ZN7decimal12RuntimeErrorD0Ev@Base 2.5
- (optional=lto)_ZN7decimal12RuntimeErrorD1Ev@Base 2.5
- (optional=lto)_ZN7decimal12RuntimeErrorD2Ev@Base 2.5
- (optional=lto)_ZN7decimal14DivisionByZeroD0Ev@Base 2.5
- (optional=lto)_ZN7decimal14DivisionByZeroD1Ev@Base 2.5
- (optional=lto)_ZN7decimal14DivisionByZeroD2Ev@Base 2.5
- (optional=lto)_ZN7decimal16ConversionSyntaxD0Ev@Base 2.5
- (optional=lto)_ZN7decimal16ConversionSyntaxD1Ev@Base 2.5
- (optional=lto)_ZN7decimal16ConversionSyntaxD2Ev@Base 2.5
- (optional=lto)_ZN7decimal16DecimalExceptionD0Ev@Base 2.5
- (optional=lto)_ZN7decimal16DecimalExceptionD1Ev@Base 2.5
- (optional=lto)_ZN7decimal16DecimalExceptionD2Ev@Base 2.5
- (optional=lto)_ZN7decimal16InvalidOperationD0Ev@Base 2.5
- (optional=lto)_ZN7decimal16InvalidOperationD1Ev@Base 2.5
- (optional=lto)_ZN7decimal16InvalidOperationD2Ev@Base 2.5
- _ZN7decimal16context_templateE@Base 2.5
- (optional=lto)_ZN7decimal17DivisionUndefinedD0Ev@Base 2.5
- (optional=lto)_ZN7decimal17DivisionUndefinedD1Ev@Base 2.5
- (optional=lto)_ZN7decimal17DivisionUndefinedD2Ev@Base 2.5
- 

Bug#1059875: src:rjava: fails to migrate to testing for too long: FTBFS on i386

[Dirk Eddelbuettel]

(Adrian: Added you to CCs per suggestion of Paul.)

Hi Paul,

On 2 January 2024 at 21:00, Paul Gevers wrote:
| Hi Dirk,
| 
| On 02-01-2024 20:42, Dirk Eddelbuettel wrote:
| > | The Release Team considers packages that are out-of-sync between testing
| > | and unstable for more than 30 days as having a Release Critical bug in
| > 
| > I noticed that too over the last few weeks as I tend to keep an eye on my
| > aggregation at https://qa.debian.org/developer.php?login=e...@debian.org
| 
| Nice. I wish every DD did that.
| 
| > | This bug will trigger auto-removal when appropriate. As with all new
| > | bugs, there will be at least 30 days before the package is auto-removed.
| > 
| > Sure. Though that might be harsh / might affect other packages.
| 
| They will be notified of the autoremoval automatically and can help you 
| fix the situation. If there's work in progress, you can delay the 
| autoremoval by pinging this bug, that resets the timer.
| 
| > We may want to consider exempting i386 as a build arch if that is possible.
| 
| Well, if you really can't support i386 anymore (we expect from DD to 
| support as many architectures as is *reasonably* possible), you should 
| arrange for the removal of the i386 package, including all reverse i386 
| dependencies. It would be good to coordinate this with your reverse 
| dependencies (at least inform them). In the end removal happens by 
| filing appropriate RM bugs against the ftp.debian.org pseudo package.

Ok. I can do that. I just look at 'rdepends' for r-cran-rjava and it is only
five packages. That seems fair.
 
| > | If you believe your package is unable to migrate to testing due to
| > | issues beyond your control, don't hesitate to contact the Release Team.
| > 
| > :wave:
| 
| FTBFS of your own package is what I consider to be in your control (this 
| text is part of the template I use). Either you fix the issue, or you 
| decide to no long support i386 with your package, but you'll need to 
| coordinate with your reverse dependencies. The removal happens by 
| ftp-master once you file the appropriate bugs.
| 
| > This is an R package, and R no longer releases on i386 meaning upstream may
| > not have checked / may not be receptive. See eg [1] for the CRAN state of 
the
| > package. No i386 there.
| > 
| > I am not sure what else to do besides simply saying 'no longer builds on 
i386'.
| 
| Maybe contact i386 porters for help creating a patch? (We have one: 
| Adrian Bunk).

Good idea. Have CC'ed Adrian to see if he wants to jump in.
 
| Having said all that, most of our upstreams don't support (for some 
| value of support) all the architectures that we support. Still we expect 
| from DD to put in *reasonable* effort to support their packages on our 
| architectures. So, the call to drop an architecture from the supported 
| list is yours to make as a maintainer.

It is not easy to strike the right balance, ie for m68k we 'hang on' for a
long time as we had motivated maintainers / porters / developers. Not sure we
had users :)

For i386 we have been patient too. The hardware has been EOL for some time
and most projects have ceased explicit support.  That is a fair sign.

If someone wants to help, I am happy to play along. But if not, I think for a
'somewhat marginal leaf-alike' dependency such as rJava aka r-cran-rjava
removing i386 support is defensible.  We only support approx 1k out 20k CRAN
packages so users are accustomed to having to go elsewhere anyway. I packaged
rJava nearly 20 years ago because it is a 'difficult' package for many users
and our integration helps. I still maintain it for the same reason, even if
Java is also way more marginal within R now. So for i386 the end may be coming.

Cheers, Dirk


| Paul
| x[DELETED ATTACHMENT OpenPGP_signature.asc, application/pgp-signature]

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1059875: src:rjava: fails to migrate to testing for too long: FTBFS on i386

[Paul Gevers]

Hi Dirk,

On 02-01-2024 20:42, Dirk Eddelbuettel wrote:

| The Release Team considers packages that are out-of-sync between testing
| and unstable for more than 30 days as having a Release Critical bug in

I noticed that too over the last few weeks as I tend to keep an eye on my
aggregation at https://qa.debian.org/developer.php?login=e...@debian.org


Nice. I wish every DD did that.


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

Sure. Though that might be harsh / might affect other packages.


They will be notified of the autoremoval automatically and can help you 
fix the situation. If there's work in progress, you can delay the 
autoremoval by pinging this bug, that resets the timer.



We may want to consider exempting i386 as a build arch if that is possible.


Well, if you really can't support i386 anymore (we expect from DD to 
support as many architectures as is *reasonably* possible), you should 
arrange for the removal of the i386 package, including all reverse i386 
dependencies. It would be good to coordinate this with your reverse 
dependencies (at least inform them). In the end removal happens by 
filing appropriate RM bugs against the ftp.debian.org pseudo package.



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

:wave:


FTBFS of your own package is what I consider to be in your control (this 
text is part of the template I use). Either you fix the issue, or you 
decide to no long support i386 with your package, but you'll need to 
coordinate with your reverse dependencies. The removal happens by 
ftp-master once you file the appropriate bugs.



This is an R package, and R no longer releases on i386 meaning upstream may
not have checked / may not be receptive. See eg [1] for the CRAN state of the
package. No i386 there.

I am not sure what else to do besides simply saying 'no longer builds on i386'.


Maybe contact i386 porters for help creating a patch? (We have one: 
Adrian Bunk).


Having said all that, most of our upstreams don't support (for some 
value of support) all the architectures that we support. Still we expect 
from DD to put in *reasonable* effort to support their packages on our 
architectures. So, the call to drop an architecture from the supported 
list is yours to make as a maintainer.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1059875: src:rjava: fails to migrate to testing for too long: FTBFS on i386

[Dirk Eddelbuettel]

On 2 January 2024 at 20:07, Paul Gevers wrote:
| Source: rjava
| Version: 1.0-6-1
| Severity: serious
| Control: close -1 1.0-10-1
| Tags: sid trixie ftbfs
| User: release.debian@packages.debian.org
| Usertags: out-of-sync
| 
| Dear maintainer(s),
| 
| The Release Team considers packages that are out-of-sync between testing 
| and unstable for more than 30 days as having a Release Critical bug in

I noticed that too over the last few weeks as I tend to keep an eye on my
aggregation at https://qa.debian.org/developer.php?login=e...@debian.org

| testing [1]. Your package src:rjava has been trying to migrate for 31 
| days [2]. Hence, I am filing this bug. The version in unstable failed to 
| build on i386.
| 
| If a package is out of sync between unstable and testing for a longer 
| period, this usually means that bugs in the package in testing cannot be 
| fixed via unstable. Additionally, blocked packages can have impact on 
| other packages, which makes preparing for the release more difficult. 
| Finally, it often exposes issues with the package and/or
| its (reverse-)dependencies. We expect maintainers to fix issues that 
| hamper the migration of their package in a timely manner.
| 
| This bug will trigger auto-removal when appropriate. As with all new 
| bugs, there will be at least 30 days before the package is auto-removed.

Sure. Though that might be harsh / might affect other packages.

We may want to consider exempting i386 as a build arch if that is possible.
 
| I have immediately closed this bug with the version in unstable, so if 
| that version or a later version migrates, this bug will no longer affect 
| testing. I have also tagged this bug to only affect sid and trixie, so 
| it doesn't affect (old-)stable.
| 
| If you believe your package is unable to migrate to testing due to 
| issues beyond your control, don't hesitate to contact the Release Team.

:wave:

This is an R package, and R no longer releases on i386 meaning upstream may
not have checked / may not be receptive. See eg [1] for the CRAN state of the
package. No i386 there.

I am not sure what else to do besides simply saying 'no longer builds on i386'.

Dirk

[1] https://cran.r-project.org/web/checks/check_results_rJava.html

| Paul
| 
| [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
| [2] https://qa.debian.org/excuses.php?package=rjava
| 
| x[DELETED ATTACHMENT OpenPGP_signature.asc, application/pgp-signature]

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#770171: marked as done (sshd jail fails when system solely relies on systemd journal for logging)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2024 19:34:24 +
with message-id 
and subject line Bug#770171: fixed in fail2ban 1.0.2-3
has caused the Debian Bug report #770171,
regarding sshd jail fails when system solely relies on systemd journal for 
logging
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.)


-- 
770171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fail2ban
Version: 0.9.1-1
Severity: important

Dear Maintainer,

when a system is configured to use the systemd journal as the
sole logging system, i.e. when none of the packages provided by
system-log-daemon are installed, the default sshd jail does not work.

When logging in the system is done by using the systemd journal, the
file /var/log/auth.log is not used anymore. While  fail2ban 0.9
can use the systemd journal for matching offending log entries, the
Debian package comes with a "backend = auto" statement that
effectively disables matching against entries in the journal. As the
log files in /var/log are not updated anymore, fail2ban becomes
useless.

In order to have the sshd jail to work correctly I had to:

1. install python3-systemd, which is right now only suggested by
   fail2ban, but given that systemd is going to be default in jessy
   it should probably become a Depends

2. activate the systemd backend by adding 
   [DEFAULT]
   backend = systemd
   to the jail.d/defaults-debian.conf file

3. modify filter.d/sshd.conf to use the correct name of the sshd
   systemd unit in Debian, which is ssh.service and not
   sshd.service:
   [Init]
   journalmatch = _SYSTEMD_UNIT=ssh.service + _COMM=sshd

I did not find a way to perform 3 in a way that is robust against future
upgrades of the fail2ban package...

With the above mentioned modifications in place fail2ban correctly
bans abusive hosts. I am not sure if syslog-ng or rsyslog are still
going to be installed by default in jessy (probably yes?), but
I would assume that a number of people would want to solely rely on
the systemd journal, as otherwise logging gets duplicated and would
be unhappy to discover that fail2ban has not been working for months
(like it happened to me ;).

I don't know if fail2ban should use the systemd backend by default,
but the steps needed to make it work that way should be at least
mentioned in NEWS.Debian or README.Debian *and* the sshd filter
should use the correct name of the systemd unit [maybe all filters
should be checked for wrong systemd unit names?].

As a side note, do you think that package systemd should Provide
system-log-daemon? Is this worth filing a bug against systemd?

Ciao,
Tiziano

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

Kernel: Linux 3.17-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages fail2ban depends on:
ii  init-system-helpers  1.21
ii  lsb-base 4.1+Debian13+nmu1
ii  python3  3.4.2-1
pn  python3:any  

Versions of packages fail2ban recommends:
ii  iptables   1.4.21-2+b1
pn  python3-pyinotify  
ii  whois  5.2.2

Versions of packages fail2ban suggests:
pn  mailx  
ii  python3-systemd215-6
pn  system-log-daemon  

-- Configuration Files:
/etc/fail2ban/filter.d/sshd.conf changed:
[INCLUDES]
before = common.conf
[Definition]
_daemon = sshd
failregex = ^%(__prefix_line)s(?:error: PAM: )?[aA]uthentication 
(?:failure|error) for .* from ( via \S+)?\s*$
^%(__prefix_line)s(?:error: PAM: )?User not known to the underlying 
authentication module for .* from \s*$
^%(__prefix_line)sFailed \S+ for .*? from (?: port \d*)?(?: 
ssh\d*)?(: (ruser .*|(\S+ ID \S+ \(serial \d+\) CA )?\S+ %(__md5hex)s(, client 
user ".*", client host ".*")?))?\s*$
^%(__prefix_line)sROOT LOGIN REFUSED.* FROM \s*$
^%(__prefix_line)s[iI](?:llegal|nvalid) user .* from \s*$
^%(__prefix_line)sUser .+ from  not allowed because not 
listed in AllowUsers\s*$
^%(__prefix_line)sUser .+ from  not allowed because listed in 
DenyUsers\s*$
^%(__prefix_line)sUser .+ from  not allowed because not in 
any group\s*$
^%(__prefix_line)srefused connect from \S+ \(\)\s*$
^%(__prefix_line)sReceived disconnect from : 3: \S+: Auth 
fail$
^%(__prefix_line)sUser .+ from  not allowed because a group 
is 

Bug#1037437: marked as done (From fresh bookworm install default sshd jail in fail2ban won’t work without rsyslog installed)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2024 19:34:24 +
with message-id 
and subject line Bug#1037437: fixed in fail2ban 1.0.2-3
has caused the Debian Bug report #1037437,
regarding From fresh bookworm install default sshd jail in fail2ban won’t work 
without rsyslog installed
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.)


-- 
1037437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fail2ban
Version: 1.0.2-2

>From fresh bookworm installation, In fail2ban, the sshd jail which is
enable by default won’t work without rsyslog installed. The fail2ban
service then fails to start.
--- End Message ---
--- Begin Message ---
Source: fail2ban
Source-Version: 1.0.2-3
Done: Sylvestre Ledru 

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated fail2ban 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: Tue, 19 Sep 2023 13:55:20 +0200
Source: fail2ban
Architecture: source
Version: 1.0.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Sylvestre Ledru 
Closes: 770171 1037437
Changes:
 fail2ban (1.0.2-3) unstable; urgency=medium
 .
   * Add banaction = nftables in the defaults-debian.conf default
 see 
https://github.com/fail2ban/fail2ban/discussions/3575#discussioncomment-7045315
   * Move python3-systemd as depend (Closes: #770171, #1037437)
   * Add backend = systemd to jail.d/defaults-debian.conf
Checksums-Sha1:
 a221158a81ce3906b05263c58fdaece56c57f8b0 2059 fail2ban_1.0.2-3.dsc
 d829392cc6f53fb56b982bb3ba7ab41803221ef0 29616 fail2ban_1.0.2-3.debian.tar.xz
 28f80e77797db56e03b1b4efc6e35301fe07bfe3 6938 fail2ban_1.0.2-3_amd64.buildinfo
Checksums-Sha256:
 7c7c70e55b8d0ddeb9e860053a4db66acd9a75e133d62e3f58e6be012c1bb9d7 2059 
fail2ban_1.0.2-3.dsc
 720d8c6fd124031f7c2488af6a6f86f4be0d407c45cd94b7220209e7cf4f93c0 29616 
fail2ban_1.0.2-3.debian.tar.xz
 ee98ac04f491e5ca921bd8f1742a917a72da11653229fd056acff92229fb92fc 6938 
fail2ban_1.0.2-3_amd64.buildinfo
Files:
 59fbaf232d2f678777e538b75286fe7c 2059 net optional fail2ban_1.0.2-3.dsc
 4e233c00e21527de7ae02c9b889e6fc5 29616 net optional 
fail2ban_1.0.2-3.debian.tar.xz
 0c83648e5ef62309e42a04768d375a28 6938 net optional 
fail2ban_1.0.2-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmWUX4kACgkQfmUo2nUv
G+FPSA//Qev+iTo3047na6J3er9NbuLg1k3IUoPfRE4VNlApapA7mEZsfQmmfqTg
1gUfBpeFN6qINdVVby7kB2zTel0z1dsyDkra+17WgoQJv8nTLiUEUdGq8JFuzYoq
a+gljp6HbYSry7bS3RnZMZD11wW+1JzkxJ2OtbKopfEcVyNe7FDa+Dm8W4NOudyl
7VFL93uC1Sb2I5hE5mWexdi8By8rk4fwTh4RQhcLbsd45gf9y4MB9S7Dk1S+k+n7
uRVFBZqzTY89gGULgpQboTewLiGqRQGAcNtF7jBZMElOe7Wy6eJSKA8oTloNZQHT
zIFlvt5XP+XbS4zi4DIGPmCTVmg3F90CSbzMJqsqU2tvPeIMo11OEG1+ZeBGkqD/
9jYV3xpkpYkp/emhOvxuq3Ll22ty3qa4PhoTT4W4zaTeb3eLsJev2iT4eQdzH1vI
GNayOQ5wGe2vSdqPwi4BjUjKsa6snLcrjXerpnaHzihrE22qajiKjxn1TOTd2lKN
eJR3a4O5BwIXyeR+03VqGIehEhaAXE6sfeQTvvk+pRLzZA8vXXzecXV+TmNPm6py
bmycYs2kg/KaLHBJAdevg0CYaSEauYltBPtk3mRPsltIZKIj+gK8mOx04ab3inni
f0z/mJ0TcuixKb3qMFvjEU+8k6XLafJvencJWfh+7HY/beFuB6A=
=DbGW
-END PGP SIGNATURE End Message ---

Bug#1059878: src:devicexlib: fails to migrate to testing for too long: FTBFS on ppc64el

[Paul Gevers]

Source: devicexlib
Version: 0.1.0-2
Severity: serious
Control: close -1 0.8.2-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:devicexlib has been trying to migrate for 
31 days [2]. Hence, I am filing this bug. The version in unstable failed 
to build on ppc64el.


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


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


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


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=devicexlib



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1059876: src:mopac: fails to migrate to testing for too long: FTBFS on i386

[Paul Gevers]

Source: mopac
Version: 22.0.6+dfsg-1
Severity: serious
Control: close -1 22.1.0-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:mopac has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The version in unstable failed to 
build on i386.


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


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


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


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=mopac



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:devicexlib: fails to migrate to testing for too long: FTBFS on ppc64el

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.8.2-1
Bug #1059878 [src:devicexlib] src:devicexlib: fails to migrate to testing for 
too long: FTBFS on ppc64el
Marked as fixed in versions devicexlib/0.8.2-1.
Bug #1059878 [src:devicexlib] src:devicexlib: fails to migrate to testing for 
too long: FTBFS on ppc64el
Marked Bug as done

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

Processed: src:mopac: fails to migrate to testing for too long: FTBFS on i386

[Debian Bug Tracking System]

Processing control commands:

> close -1 22.1.0-1
Bug #1059876 [src:mopac] src:mopac: fails to migrate to testing for too long: 
FTBFS on i386
Marked as fixed in versions mopac/22.1.0-1.
Bug #1059876 [src:mopac] src:mopac: fails to migrate to testing for too long: 
FTBFS on i386
Marked Bug as done

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

Processed: src:rjava: fails to migrate to testing for too long: FTBFS on i386

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.0-10-1
Bug #1059875 [src:rjava] src:rjava: fails to migrate to testing for too long: 
FTBFS on i386
Marked as fixed in versions rjava/1.0-10-1.
Bug #1059875 [src:rjava] src:rjava: fails to migrate to testing for too long: 
FTBFS on i386
Marked Bug as done

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

Bug#1059875: src:rjava: fails to migrate to testing for too long: FTBFS on i386

[Paul Gevers]

Source: rjava
Version: 1.0-6-1
Severity: serious
Control: close -1 1.0-10-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:rjava has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The version in unstable failed to 
build on i386.


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


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


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


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=rjava



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: Bug#770171 marked as pending in fail2ban

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #770171 [fail2ban] sshd jail fails when system solely relies on systemd 
journal for logging
Added tag(s) pending.

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

Bug#770171: marked as pending in fail2ban

[Sylvestre Ledru]

Control: tag -1 pending

Hello,

Bug #770171 in fail2ban 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/fail2ban/-/commit/47a2ffa95ac787382f439505a257468ea666d17d


Move python3-systemd as depend (Closes: #770171)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/770171

Bug#1058327: python-limits: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

[Carsten Schoenert]

Control: reassign -1 python3-protobuf 3.21.12-8
Control: affects -1 python-limits

Dear maintainer,

reassigning this issue as the current problem is happen in the package
python3-protobuf from my current POV. The relevant part seems to this:

> /usr/lib/python3/dist-packages/google/protobuf/internal/api_implementation.py:104:
>  in 
> from google.protobuf.pyext import _message
> E   SystemError:  returned a result with an 
> exception set

Trying to search for this error message got no useful findings. The only
reports about similar issue where about some missing linking in some C++
library that is used by python3-protobuf. Maybe now the current seen
issue is related to something similar.

I tried also the current version of python3-protobuf from experimental
3.25-1 but the output is completly the same as with the version from
unstable.
Is it possible to see waht is within the 'exception set' mentione din
the error output?

OTOH I can call the import within a running python3 shell in testing
without problems. So maybe some environment is missing or wrong withing
the package build setup?

Regards
Carsten

Am Tue, Dec 12, 2023 at 09:24:16AM +0100 schrieb Lucas Nussbaum:
> Source: python-limits
> Version: 3.6.0-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20231212 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 '/<>'
> > dh_auto_build
> > I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> > running build
> > running build_py
> > creating /<>/.pybuild/cpython3_3.12_limits/build/limits
> > copying limits/__init__.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits
> > copying limits/version.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits
> > copying limits/limits.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits
> > copying limits/_version.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits
> > copying limits/strategies.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits
> > copying limits/errors.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits
> > copying limits/util.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits
> > copying limits/typing.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits
> > creating /<>/.pybuild/cpython3_3.12_limits/build/limits/storage
> > copying limits/storage/__init__.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/storage
> > copying limits/storage/redis_sentinel.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/storage
> > copying limits/storage/etcd.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/storage
> > copying limits/storage/memory.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/storage
> > copying limits/storage/base.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/storage
> > copying limits/storage/memcached.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/storage
> > copying limits/storage/mongodb.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/storage
> > copying limits/storage/redis_cluster.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/storage
> > copying limits/storage/registry.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/storage
> > copying limits/storage/redis.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/storage
> > creating /<>/.pybuild/cpython3_3.12_limits/build/limits/aio
> > copying limits/aio/__init__.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/aio
> > copying limits/aio/strategies.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/aio
> > creating 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/aio/storage
> > copying limits/aio/storage/__init__.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/aio/storage
> > copying limits/aio/storage/etcd.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/aio/storage
> > copying limits/aio/storage/memory.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/aio/storage
> > copying limits/aio/storage/base.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/aio/storage
> > copying limits/aio/storage/memcached.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/aio/storage
> > copying limits/aio/storage/mongodb.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/aio/storage
> > copying limits/aio/storage/redis.py -> 
> > /<>/.pybuild/cpython3_3.12_limits/build/limits/aio/storage
> > running egg_info
> > creating limits.egg-info
> > writing limits.egg-info/PKG-INFO
> > writing dependency_links to limits.egg-info/dependency_links.txt
> > writing requirements to limits.egg-info/requires.txt
> > writing top-level names to limits.egg-info/top_level.txt
> > writing manifest file 'limits.egg-info/SOURCES.txt'
> > reading manifest file 'limits.egg-info/SOURCES.txt'
> > reading manifest template 'MANIFEST.in'

Processed: Re: Bug#1058327: python-limits: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3-protobuf 3.21.12-8
Bug #1058327 [src:python-limits] python-limits: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit 
code 13
Bug reassigned from package 'src:python-limits' to 'python3-protobuf'.
No longer marked as found in versions python-limits/3.6.0-1.
Ignoring request to alter fixed versions of bug #1058327 to the same values 
previously set
Bug #1058327 [python3-protobuf] python-limits: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit 
code 13
Marked as found in versions protobuf/3.21.12-8.
> affects -1 python-limits
Bug #1058327 [python3-protobuf] python-limits: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit 
code 13
Added indication that 1058327 affects python-limits

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

Processed: Re: Bug#1059869: autopkgtest fails

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1059869 [src:plakativ] autopkgtest fails
Severity set to 'serious' from 'important'

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

Bug#1000100: eiskaltdcpp: depends on obsolete pcre3 library

[Yavor Doganov]

Control: tags -1 + patch

Please find a patch attached; build-tested only.
Description: Port to PCRE2.
Bug-Debian: https://bugs.debian.org/1000100
Author: Yavor Doganov 
Forwarded: no
Last-Update: 2024-01-02
---

--- eiskaltdcpp-2.4.2.orig/cmake/FindPCRE.cmake
+++ eiskaltdcpp-2.4.2/cmake/FindPCRE.cmake
@@ -4,23 +4,22 @@
 #  PCRE_INCLUDE_DIR - the PCRE include directory
 #  PCRE_LIBRARIES - link these to use PCRE
 
-if(PCRE_INCLUDE_DIR AND PCRE_LIBRARY AND PCRECPP_LIBRARY)
+if(PCRE_INCLUDE_DIR AND PCRE_LIBRARY)
   set(PCRE_FIND_QUIETLY TRUE)
-endif(PCRE_INCLUDE_DIR AND PCRE_LIBRARY AND PCRECPP_LIBRARY)
+endif(PCRE_INCLUDE_DIR AND PCRE_LIBRARY)
 
 # Include dir
-find_path(PCRE_INCLUDE_DIR NAMES pcre.h)
+find_path(PCRE_INCLUDE_DIR NAMES pcre2.h)
 
 # Libraries
-find_library(PCRE_LIBRARY NAMES pcre)
-find_library(PCRECPP_LIBRARY NAMES pcrecpp)
+find_library(PCRE_LIBRARY NAMES pcre2-8)
 
-if(PCRE_LIBRARY AND PCRECPP_LIBRARY)
-  set(PCRE_LIBRARIES ${PCRECPP_LIBRARY} ${PCRE_LIBRARY})
-endif(PCRE_LIBRARY AND PCRECPP_LIBRARY)
+if(PCRE_LIBRARY)
+  set(PCRE_LIBRARIES ${PCRE_LIBRARY})
+endif(PCRE_LIBRARY)
 
 INCLUDE(FindPackageHandleStandardArgs)
 FIND_PACKAGE_HANDLE_STANDARD_ARGS(PCRE DEFAULT_MSG PCRE_LIBRARIES 
PCRE_INCLUDE_DIR)
 
-MARK_AS_ADVANCED(PCRE_LIBRARIES PCRE_INCLUDE_DIR PCRE_LIBRARY PCRECPP_LIBRARY)
+MARK_AS_ADVANCED(PCRE_LIBRARIES PCRE_INCLUDE_DIR PCRE_LIBRARY)
 
--- eiskaltdcpp-2.4.2.orig/dcpp/ADLSearch.cpp
+++ eiskaltdcpp-2.4.2/dcpp/ADLSearch.cpp
@@ -32,7 +32,8 @@
 #include "StringTokenizer.h"
 
 #ifdef USE_PCRE
-#include "pcrecpp.h"
+#define PCRE2_CODE_UNIT_WIDTH 8
+#include 
 #endif
 
 namespace dcpp {
@@ -172,11 +173,28 @@
 bool ADLSearch::searchAll(const string& s) {
 #ifdef USE_PCRE
 if(bUseRegexp){
-pcrecpp::RE_Options options;
-options.set_utf8(true);
-options.set_caseless(true);
-pcrecpp::RE regexp(regexpstring, options);
-if(regexp.FullMatch(s))
+pcre2_code *re;
+pcre2_match_data *md;
+PCRE2_SPTR pat, subj;
+PCRE2_SIZE offset;
+uint32_t utf = 0, options = 0;
+int rc;
+
+pcre2_config(PCRE2_CONFIG_UNICODE, );
+if(utf)
+options |= PCRE2_UTF;
+options |= PCRE2_CASELESS;
+pat = reinterpret_cast(regexpstring.c_str());
+subj = reinterpret_cast(s.c_str());
+re = pcre2_compile(pat, PCRE2_ZERO_TERMINATED, options,
+   , , nullptr);
+if(offset != 0)
+return false;
+md = pcre2_match_data_create_from_pattern(re, nullptr);
+rc = pcre2_match(re, subj, s.size(), 0, 0, md, nullptr);
+pcre2_code_free(re);
+pcre2_match_data_free(md);
+if(rc >= 0)
 return true;
 else
 return false;

Processed: Re: Bug#1000100: eiskaltdcpp: depends on obsolete pcre3 library

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1000100 [src:eiskaltdcpp] eiskaltdcpp: depends on obsolete pcre3 library
Added tag(s) patch.

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

Processed: closing 1055557

[Debian Bug Tracking System]

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

> close 107 2.3.2-1
Bug #107 [src:python-hiredis] python-hiredis ftbfs with Python 3.12
The source 'python-hiredis' and version '2.3.2-1' do not appear to match any 
binary packages
Marked as fixed in versions python-hiredis/2.3.2-1.
Bug #107 [src:python-hiredis] python-hiredis ftbfs with Python 3.12
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1052875: marked as done (borgbackup2: FTBFS: E FileNotFoundError: [Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.11/build/borg/testsuite/archiver/repo12.tar.g

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2024 16:34:53 +
with message-id 
and subject line Bug#1052875: fixed in borgbackup2 2.0.0b5-2
has caused the Debian Bug report #1052875,
regarding borgbackup2: FTBFS: E   FileNotFoundError: [Errno 2] No such 
file or directory: 
'/<>/.pybuild/cpython3_3.11/build/borg/testsuite/archiver/repo12.tar.gz'
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.)


-- 
1052875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: borgbackup2
Version: 2.0.0b5-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> === short test summary info 
> 
> FAILED 
> borg/testsuite/archiver/key_cmds.py::ArchiverTestCase::test_key_export_qr
> FAILED 
> borg/testsuite/archiver/key_cmds.py::RemoteArchiverTestCase::test_key_export_qr
> FAILED 
> borg/testsuite/archiver/transfer_cmd.py::ArchiverTestCase::test_transfer_upgrade
> === 3 failed, 790 passed, 193 skipped, 626 deselected in 1148.87s (0:19:08) 
> 
> /usr/lib/python3/dist-packages/_pytest/pathlib.py:95: PytestWarning: (rm_rf) 
> error removing 
> /tmp/pytest-of-user42/garbage-995a46fb-a614-4592-886a-6e1c5e8520b2/test_sysfind_no_permisson_igno0
> : [Errno 39] Directory not empty: 
> 'test_sysfind_no_permisson_igno0'
>   warnings.warn(
> /usr/lib/python3/dist-packages/_pytest/pathlib.py:95: PytestWarning: (rm_rf) 
> error removing 
> /tmp/pytest-of-user42/garbage-995a46fb-a614-4592-886a-6e1c5e8520b2
> : [Errno 39] Directory not empty: 
> '/tmp/pytest-of-user42/garbage-995a46fb-a614-4592-886a-6e1c5e8520b2'
>   warnings.warn(
> E: pybuild pybuild:395: test: plugin distutils failed with: exit code=1: cd 
> /<>/.pybuild/cpython3_3.11/build; python3.11 -m pytest --pyargs 
> borg.testsuite -k 'not fuse_mount and not test_fuse and not 
> test_readonly_mount and not test_migrate_lock_alive and not benchmark.py and 
> not cache.py and not checks.py and not key.py and not locking.py and not 
> patterns.py and not remote.py and not repository.py and not shellpattern.py'
> dh_auto_test: error: pybuild --test -i python{version} -p 3.11 --test-args 
> "--pyargs borg.testsuite -k 'not fuse_mount and not test_fuse and not 
> test_readonly_mount and not test_migrate_lock_alive and not benchmark.py and 
> not cache.py and not checks.py and not key.py and not locking.py and not 
> patterns.py and not remote.py and not repository.py and not shellpattern.py'" 
> returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2023/09/25/borgbackup2_2.0.0b5-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=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: borgbackup2
Source-Version: 2.0.0b5-2
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
borgbackup2 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: Tue, 02 Jan 2024 17:11:02 +0100
Source: borgbackup2
Built-For-Profiles: noudeb
Architecture: source
Version: 2.0.0b5-2
Distribution: unstable
Urgency: medium
Maintainer: 

Bug#1059375: marked as done (appstream: requires source-only upload for migration)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2024 16:34:28 +
with message-id 
and subject line Bug#1059375: fixed in appstream 1.0.1-3
has caused the Debian Bug report #1059375,
regarding appstream: requires source-only upload for migration
to be marked as done.

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

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


-- 
1059375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: appstream
Version: 1.0.1-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

>From appstream's excuses:

∙ ∙ Not built on buildd: arch amd64 binaries uploaded by matth...@tenstral.net
∙ ∙ Not built on buildd: arch all binaries uploaded by matth...@tenstral.net, a 
new source-only upload is needed to allow migration

See https://qa.debian.org/excuses.php?package=appstream

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: appstream
Source-Version: 1.0.1-3
Done: Matthias Klumpp 

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

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated appstream 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: Tue, 02 Jan 2024 14:48:42 +0100
Source: appstream
Architecture: source
Version: 1.0.1-3
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klumpp 
Changed-By: Matthias Klumpp 
Closes: 1059375
Changes:
 appstream (1.0.1-3) unstable; urgency=medium
 .
   * No-change source-only upload (Closes: #1059375)
Checksums-Sha1:
 618b954b695e9a5735ceeda35c8cf0b5d56dc6f9 4018 appstream_1.0.1-3.dsc
 374f63ed0a2d79707c1d83e03dd05279ea663c8a 2686244 appstream_1.0.1.orig.tar.xz
 93d6181047ce889756f6375bb24dcff85820a65f 19980 appstream_1.0.1-3.debian.tar.xz
 078ea116cac463abe0ac67ecc06259305d356010 16386 
appstream_1.0.1-3_source.buildinfo
Checksums-Sha256:
 c6ac63760e75c5b779e97bfe883c561a18345674a47581e7982ea090594b9f34 4018 
appstream_1.0.1-3.dsc
 fa4d5994e5c6f22e9b66cb0b52e8b5f5d96e7353ea5528b56436e0150829203b 2686244 
appstream_1.0.1.orig.tar.xz
 fad72c54b35c0c1ef974c78e1f2ef535df36670d11c09cd287cde0694c5eb1ec 19980 
appstream_1.0.1-3.debian.tar.xz
 925db525efea454a279fd552ce6bb68115382220090992590bae49fecf4b567f 16386 
appstream_1.0.1-3_source.buildinfo
Files:
 c22c723268a9fc00acf08d71bb03e9a1 4018 admin optional appstream_1.0.1-3.dsc
 a1122ba2d3c41ba694f00844c847 2686244 admin optional 
appstream_1.0.1.orig.tar.xz
 f2dcee3b675ebc6608057d6ced817135 19980 admin optional 
appstream_1.0.1-3.debian.tar.xz
 c22d7e555c2f1881caab79a36732ba7c 16386 admin optional 
appstream_1.0.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEE0zo/DKFrCsxRpgc4SUyKX79N7OsFAmWUNXAPHG1ha0BkZWJp
YW4ub3JnAAoJEElMil+/TezrRbIP/RZaDqVdVn6VyZYOwEgEHAkIvpmqCN0dNv0G
kjr8y/rHIchyZl8P6YnF+Zsc1hdbFcb0Ds0b9A6naxa7AzMAX3mpDhiOJOnm6I+9
VOQWwzXkyvkSihO8cIYr199aSje0cyCkG/tT6o0XQ1esnqRWkA3r9Zzh4riLAyVm
EDnFU0//GzVavvsLMXtaAHeBlFu989A4+zoBP/76n0gKb6wh1GG3MJg8bhjLNeIp
tQzIIfFHvPv7A7v3//bqxTdPs7d/33SeSb/2/aWvxTca3PBapJx7gEejhSeQ9x5X
MiydJ2wmS/6BoniB6zANgyhZOry285MEznFaWJOvwMoW7sTwQ4PqXk6BXPJWojo4
YBhZdrW4yRRMLoAOq2ocaInt0MonoPkRg3RSz2VyQPR/VAyOq75x+1zujp0S9Qaa
nAkI14LSGmCHJilWKi8uM0R6iXY4Avl9LLiKoej7cg5lj72oXHJHTRSI+P6fxPxR
XZj3bpAVZuTs0psS/jg/tJVTjv/9sr+KEEeN9X8nx24Ktsygf0iU5+033Rq70FBO
G/geztNoN+i6AlTr6aiOfpoM4qvuuRAMEiuLY5xuh+7/+RJ6mhq6RNfZKbZNJ1NP
MNerMspAZ8LrTBcsi8vkHEAir6TVofiMu7oEOefef0JArsqEsupUp5SZN4KPwMhh
CBAbTMsA
=htc1
-END PGP SIGNATURE End Message ---

Bug#1057197: marked as done (borgbackup2: Package cannot be installed due to an upper limit on the depedency 'python3-platformdirs')

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2024 16:34:53 +
with message-id 
and subject line Bug#1057197: fixed in borgbackup2 2.0.0b5-2
has caused the Debian Bug report #1057197,
regarding borgbackup2: Package cannot be installed due to an upper limit on the 
depedency 'python3-platformdirs'
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.)


-- 
1057197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: borgbackup2
Version: 2.0.0b5-1
Severity: grave
Tags: newcomer
Justification: renders package unusable

Dear Maintainer,

there is a version conflict in the dependencies:

$ apt install borgbackup2
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 borgbackup2 : Depends: python3-platformdirs (< 4.0.0) but 4.0.0-1 is 
to be installed
   Recommends: python3-llfuse (< 2.0) but it is 
not going to be installed
   Recommends: python3-pyfuse3 but it is not 
going to be installed
E: Unable to correct problems, you have held broken packages.

This is because `platformdirs` has a new version which borg is not yet allowing.
This has already been fixed upstream: 
https://github.com/borgbackup/borg/issues/7950

Please provide a suitable patch for the debian package. Thanks in advance!

Adrian


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

Kernel: Linux 6.1.0-8-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
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 borgbackup2 depends on:
ii  libacl12.3.1-3
ii  libc6  2.37-12
ii  liblz4-1   1.9.4-1
ii  libssl33.1.4-2
ii  libxxhash0 0.8.2-2
ii  libzstd1   1.5.5+dfsg2-2
ii  python33.11.4-5+b1
ii  python3-argon2 21.1.0-2
ii  python3-msgpack1.0.3-3
ii  python3-packaging  23.2-1
ii  python3-pkg-resources  68.1.2-2
ii  python3-platformdirs   4.0.0-1

Versions of packages borgbackup2 recommends:
ii  fuse3 [fuse] 3.14.0-4
pn  python3-llfuse   
pn  python3-pyfuse3  

Versions of packages borgbackup2 suggests:
pn  borgbackup2-doc  
--- End Message ---
--- Begin Message ---
Source: borgbackup2
Source-Version: 2.0.0b5-2
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
borgbackup2 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: Tue, 02 Jan 2024 17:11:02 +0100
Source: borgbackup2
Built-For-Profiles: noudeb
Architecture: source
Version: 2.0.0b5-2
Distribution: unstable
Urgency: medium
Maintainer: Freexian Packaging Team 
Changed-By: Gianfranco Costamagna 
Closes: 1052875 1057197 2039423
Changes:
 borgbackup2 (2.0.0b5-2) unstable; urgency=medium
 .
   [ Gianfranco Costamagna ]
   * Team upload (salsa.d.o/debian namespace)
   * Make pyfuse3 a suggested only package
   * Add patch to allow platformdirs up to version 5 (Closes: #1057197)
   * Refresh patches
   * Update upstream signing key from 1k to 4k
   * Bump copyright years
   * Bump std-version
   * Merge changes from borgbackup 1.2.4-3
 .
   [ Simon Chopin ]
   * d/p/manifest-data-files: fix FTBFS due to missing data files
 (Closes: 

Bug#1000005: passwordmaker-cli: depends on obsolete pcre3 library

[Yavor Doganov]

Control: tags -1 + patch

Please find a patch attached.
Description: Port to PCRE2.
Bug-Debian: https://bugs.debian.org/105
Bug: https://forums.passwordmaker.org/index.php?topic=1834.0
Author: Yavor Doganov 
Forwarded: no
Last-Update: 2024-01-02
---

--- passwordmaker-cli-1.5+dfsg.orig/unix.mak
+++ passwordmaker-cli-1.5+dfsg/unix.mak
@@ -34,7 +34,7 @@
 LDFLAGS += $(shell dpkg-buildflags --get LDFLAGS)
 CPPFLAGS += $(shell dpkg-buildflags --get CPPFLAGS)
 INCPATH = -I.
-LIBS = -lmhash -lpcrecpp
+LIBS = -lmhash -lpcre2-8
 
 ifeq ($(USE_MAC), 1)
CFLAGS := $(CFLAGS) -m32
--- passwordmaker-cli-1.5+dfsg.orig/urlsearch.cpp
+++ passwordmaker-cli-1.5+dfsg/urlsearch.cpp
@@ -24,7 +24,8 @@
 #include 
 #include 
 #include 
-#include 
+#define PCRE2_CODE_UNIT_WIDTH 8
+#include 
 #include "stdafx.h"
 #include "tinyxml.h"
 #include "urlsearch.h"
@@ -32,9 +33,24 @@
 using namespace std;
 
 int UrlSearch::regexCmp(const char *regexp, const char *string) {
-   pcrecpp::RE re(regexp);
+   pcre2_code *re;
+   pcre2_match_data *md;
+   PCRE2_SPTR pat, subj;
+   PCRE2_SIZE offset;
+   int rc;
 
-   if(re.FullMatch(string)) {
+   pat = reinterpret_cast(regexp);
+   subj = reinterpret_cast(string);
+   re = pcre2_compile(pat, PCRE2_ZERO_TERMINATED, 0,
+  , , nullptr);
+   if(offset != 0) {
+   return 0;
+   }
+   md = pcre2_match_data_create_from_pattern(re, nullptr);
+   rc = pcre2_match(re, subj, PCRE2_ZERO_TERMINATED, 0, 0, md, nullptr);
+   pcre2_code_free(re);
+   pcre2_match_data_free(md);
+   if(rc >= 0) {
return 1;
}
else {

Processed: Re: Bug#1000005: passwordmaker-cli: depends on obsolete pcre3 library

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #105 [src:passwordmaker-cli] passwordmaker-cli: depends on obsolete 
pcre3 library
Added tag(s) patch.

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

Processed: Re: Bug#1056303: pg_createcluster destroys data directory under certain conditions

[Debian Bug Tracking System]

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

> severity 1056303 important
Bug #1056303 [postgresql-common] pg_createcluster destroys data directory under 
certain conditions
Severity set to 'important' from 'critical'
> tags 1056303 +patch
Bug #1056303 [postgresql-common] pg_createcluster destroys data directory under 
certain conditions
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1056303: pg_createcluster destroys data directory under certain conditions

[Michael Banck]

severity 1056303 important
tags 1056303 +patch
thanks

Hi,

On Mon, Nov 20, 2023 at 09:49:34AM +0100, Max Kellermann wrote:
> When I tried to use "pg_createcluster" to configure my pre-existing
> PostgreSQL data directory with a new Debian install, it deleted the
> whole cluster with all databases instead.  (This serious data loss
> justifies "severity critical" according to
> https://www.debian.org/Bugs/Developer#severities)
 
> Steps to reproduce:
> 
>  pg_createcluster 15 test
>  cp /etc/postgresql/15/test/postgresql.conf /var/lib/postgresql/15/test/

You missed to copy the other configuration files, as cautioned in the
manpage:

| If the data directory already exists, it is integrated into the
| postgresql-common structure by moving the configuration file and
| setting the data_directory option. Please note that this only works
| for data directories which were created directly with initdb, i.e.
| all the configuration files (postgresql.conf etc.) must be present in
| the data directory.

>  rm -r /etc/postgresql/15/test
>  pg_createcluster 15 test
> 
> This creates a new cluster just for the demo, then deletes the
> configuration directory, after copying the postgresql.conf to the data
> directory.
> 
> I expect the second "pg_createcluster" call to find the existing data
> directory and configure it; and it tries to do so indeed:
> 
>  Configuring already existing cluster (configuration:
>  /etc/postgresql/15/test, data: /var/lib/postgresql/15/test, owner:
>  103:111)
> 
> After it finds and moves a "postgresql.conf", it however fails to find
> "pg_hba.conf"

Right, see above.
 
>  Error: move_conffile: required configuration file 
> /var/lib/postgresql/15/test/pg_hba.conf does not exist
 
> This fails the whole operation, and apparently, "pg_createcluster"
> tries to roll back by invoking "pg_dropcluster 15 test 2>/dev/null",
> destroying all pre-existing data.
> 
> If "postgresql.conf" does not exist (or is empty), "pg_dropcluster" is
> not invoked.

This is because pg_creatcluster copies postgresql.conf first, and gets
version and cluster from it - if those are set, the data directory is
removed in the cleanup phase on error.
 
I think it would be sensible to only remove the data directory if it
actually got created by pg_createcluster, so I propose the attached
patch; I have also opened a merge request on Salsa for this:
https://salsa.debian.org/postgresql/postgresql-common/-/merge_requests/19


Michael
>From c1e61705ab9384a005a009ed6327bb40d9027afb Mon Sep 17 00:00:00 2001
From: Michael Banck 
Date: Tue, 2 Jan 2024 15:54:04 +0100
Subject: [PATCH] pg_createcluster: Do not remove existing data directory on
 failure. (Closes: #105630)

---
 pg_createcluster | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/pg_createcluster b/pg_createcluster
index 66f0b82..0c36561 100755
--- a/pg_createcluster
+++ b/pg_createcluster
@@ -361,6 +361,8 @@ if (-f "$datadir/PG_VERSION") {
 ($owneruid, $ownergid) = (stat "$datadir/PG_VERSION")[4,5];
 if ($existingver == $version) {
 print "Configuring already existing cluster (configuration: $confdir, data: $datadir, owner: $owneruid:$ownergid)\n";
+# Do not remove already existing data directory on errors
+$cleanup_cruft = 0;
 } else {
 error "$datadir contains a version $existingver cluster, but $version was requested";
 }
-- 
2.39.2

Bug#1056822: marked as done (mpi4py-fft: ftbfs with cython 3.0.x)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2024 14:38:44 +
with message-id 
and subject line Bug#1056822: fixed in mpi4py-fft 2.0.5-2
has caused the Debian Bug report #1056822,
regarding mpi4py-fft: ftbfs with cython 3.0.x
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.)


-- 
1056822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mpi4py-fft
Version: 2.0.5-1
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: cython3

[This bug is targeted to the upcoming trixie release]

The package fails to build in a test rebuild on at least arm64 with
cython 3.0.5, but succeeds to build with cython 0.29.36.  Please
update the package to build with cython 3.0.5 (available in experimental).

If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable).  There is no replacement for cython3-dbg.

Build logs building with cython 3.0.5 can be found at
https://people.debian.org/~stefanor/cython3/cython-3.0.5/

See also https://lists.debian.org/debian-python/2023/11/msg00034.html
--- End Message ---
--- Begin Message ---
Source: mpi4py-fft
Source-Version: 2.0.5-2
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated mpi4py-fft 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: Tue, 02 Jan 2024 15:01:46 +0100
Source: mpi4py-fft
Architecture: source
Version: 2.0.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 1056822
Changes:
 mpi4py-fft (2.0.5-2) unstable; urgency=medium
 .
   * Build-Depends: cython3-legacy. Closes: #1056822.
Checksums-Sha1:
 01fc699f65978006af0036eae1a5d553e91d0232 2295 mpi4py-fft_2.0.5-2.dsc
 ed57b26feab79d972317476a0966ecd60d6ea23b 4728 mpi4py-fft_2.0.5-2.debian.tar.xz
Checksums-Sha256:
 77904c2dbc33a71719f81ad16cfc4db3e1b0bd3eaa807e40681030f4d8c50620 2295 
mpi4py-fft_2.0.5-2.dsc
 663bac6820ff3b1150f355003b6b1f22ec0a3dadb10891918bf81da4857c50f3 4728 
mpi4py-fft_2.0.5-2.debian.tar.xz
Files:
 496dedf5eed31faff06fca212e88d1d3 2295 python optional mpi4py-fft_2.0.5-2.dsc
 d47e6cb3372ad0a3f4fc294f23942e63 4728 python optional 
mpi4py-fft_2.0.5-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmWUGXYACgkQVz7x5L1a
AfpZFg/9Fi/f8nN22SPuMx/Hcs6rThh0WHWO8rMD5NpnD/BDt7pI+CexfEpIQ752
DWR++chbJUf6e3moS2XPgzn2x5PoNEGnoPlMCLfzCzVYnD1PXlVL+4RgfKKACUkW
WaA0eSATBvPnzeSgW4i3zu+nhSmmK7zvYpt2hPSLNbC9x4BIsnuVPetQioTGU9Yp
1yBcd+XgexonTR+rPMe249LACOhOKnjvhH1C+8MgQnLhkMKN67vodZ7qRHS8s1fM
V6RDfLzQt4UcK81CblwvbJUKu4vFpUiHWJzP/bSOxB9vuvJTgXgBj0/sTgbImAoo
KZyaEEoZfcYuO6AzGShzA7qNOi0C6JRrCl27m3DzOAtC7crWYk79bBewrTgoTUUU
Gw8kaqVBMAuXRXnNSp/oYJI3RFGDQnLN0iwTDtP3MFGfrott6mb6XA4O8KxnnmB+
3MuPrmMGv030nOAI4xXC0tdjgoAurUlreNfLcmi8YxXC+2/CnV+DoHkbkWAsZ3Jv
rI6pVkcYUvB365V0FnPv9WF+/ImY6ams9Q7/Vs1FBfsLIZYnyAkHuyExJ3Ag8H/9
2zYEP5m0KMA5jAzQ0wtpe9uIvn9GZ57jtdFCaFBg+DbsjZSb3hqAfxY5pK1iao+5
4v/MvqEFautmlKG0wk3lNEhSFKssp2+HmpAa2BczdJ8ByK4Gvcg=
=p5ME
-END PGP SIGNATURE End Message ---

Bug#999956: snort: depends on obsolete pcre3 library

[Yavor Doganov]

Control: tags -1 + patch

Please find attached a patch (it applies to the latest upstream
release 2.9.20 as well but not to the 3.x series).
Description: Port to PCRE2.
Bug-Debian: https://bugs.debian.org/56
Author: Yavor Doganov 
Forwarded: no
Last-Update: 2024-01-02
---

--- snort-2.9.15.1.orig/configure.in
+++ snort-2.9.15.1/configure.in
@@ -465,19 +465,21 @@
 CPPFLAGS="${CPPFLAGS} -I${with_libpcre_includes}"
 ICONFIGFLAGS="${ICONFIGFLAGS} -I${with_libpcre_includes}"
 else
-CPPFLAGS="${CPPFLAGS} `pcre-config --cflags`"
+CPPFLAGS="${CPPFLAGS} `pcre2-config --cflags`"
 fi
 
 if test "x$with_libpcre_libraries" != "xno"; then
 LDFLAGS="${LDFLAGS}  -L${with_libpcre_libraries}"
 else
-LDFLAGS="${LDFLAGS} `pcre-config --libs`"
+LDFLAGS="${LDFLAGS} `pcre2-config --libs8`"
 fi
 
 # PCRE configuration (required)
 # Verify that we have the headers
 PCRE_H=""
-AC_CHECK_HEADERS(pcre.h,, PCRE_H="no")
+AC_CHECK_HEADERS([pcre2.h], [], [PCRE_H="no"], [[
+#define PCRE2_CODE_UNIT_WIDTH 8
+]])
 if test "x$PCRE_H" = "xno"; then
   echo
   echo "   ERROR!  Libpcre header not found."
@@ -487,36 +489,13 @@
 
 # Verify that we have the library
 PCRE_L=""
-pcre_version_six=""
-AC_CHECK_LIB(pcre, pcre_compile, ,PCRE_L="no")
+AC_CHECK_LIB([pcre2-8], [pcre2_compile_8], [], [PCRE_L="no"])
 if test "x$PCRE_L" = "xno"; then
 echo
 echo "   ERROR!  Libpcre library not found."
 echo "   Get it from http://www.pcre.org;
 echo
 exit 1
-else
-AC_MSG_CHECKING(for libpcre version 6.0 or greater)
-AC_LINK_IFELSE([AC_LANG_PROGRAM([[#include ]], [[
-   #if (PCRE_MAJOR < 6)
-   #error "Version failure"
-   #else
-   int a, b = 0, c = 0, d = 0;
-   pcre *tmp = NULL;
-   a = pcre_copy_named_substring(tmp, "", , c, "", "", d);
-   #endif
-  ]])],[pcre_version_six="yes"],[pcre_version_six="no"])
-fi
-
-if test "x$pcre_version_six" != "xyes"; then
-AC_MSG_RESULT(no)
-echo
-echo "ERROR!  Libpcre library version >= 6.0 not found."
-echo "Get it from http://www.pcre.org;
-echo
-exit 1
-else
-AC_MSG_RESULT(yes)
 fi
 
 # OPENSSL SHA configuration (optional)
--- snort-2.9.15.1.orig/src/dynamic-plugins/sf_engine/sf_snort_plugin_api.h
+++ snort-2.9.15.1/src/dynamic-plugins/sf_engine/sf_snort_plugin_api.h
@@ -30,7 +30,8 @@
 #ifndef SF_SNORT_PLUGIN_API_H_
 #define SF_SNORT_PLUGIN_API_H_
 
-#include "pcre.h"
+#define PCRE2_CODE_UNIT_WIDTH 8
+#include 
 #include "stdio.h"
 
 #ifndef WIN32
@@ -226,7 +227,7 @@
 {
 char *expr;
 void *compiled_expr;
-void *compiled_extra;
+void *ctxt;
 uint32_t compile_flags;
 uint32_t flags; /* must include a CONTENT_BUF_X */
 int32_t   offset;
@@ -507,7 +508,7 @@
 ENGINE_LINKAGE void setAltDetect(uint8_t *buf, uint16_t altLen);
 
 ENGINE_LINKAGE int pcreExecWrapper(const PCREInfo *pcre_info, const char *buf, 
int len, int start_offset,
-int options, int *ovector, int ovecsize);
+int options, size_t *ovector, int 
ovecsize);
 
 static inline int invertMatchResult(int retVal)
 {
--- snort-2.9.15.1.orig/src/detection-plugins/sp_pcre.h
+++ snort-2.9.15.1/src/detection-plugins/sp_pcre.h
@@ -49,17 +49,18 @@
 
 void SetupPcre(void);
 
-#include 
+#define PCRE2_CODE_UNIT_WIDTH 8
+#include 
 typedef struct _PcreData
 {
-pcre *re;   /* compiled regex */
-pcre_extra *pe; /* studied regex foo */
-int options;/* sp_pcre specfic options (relative & inverse) */
+pcre2_code *re; /* compiled regex */
+pcre2_match_context *ctxt;
+uint32_t options;   /* sp_pcre specfic options (relative & inverse) */
 char *expression;
-uint32_t search_offset;
+PCRE2_SIZE search_offset;
 } PcreData;
 
-void PcreCapture(struct _SnortConfig *sc, const void *code, const void *extra);
+void PcreCapture(struct _SnortConfig *sc, const void *code);
 void PcreFree(void *d);
 uint32_t PcreHash(void *d);
 int PcreCompare(void *l, void *r);
--- snort-2.9.15.1.orig/src/detection-plugins/sp_pcre.c
+++ snort-2.9.15.1/src/detection-plugins/sp_pcre.c
@@ -46,7 +46,8 @@
 
 #include "sp_pcre.h"
 
-#include 
+#define PCRE2_CODE_UNIT_WIDTH 8
+#include 
 
 #include "snort.h"
 #include "profiler.h"
@@ -77,8 +78,8 @@
 PcreData *data = (PcreData *)d;
 
 free(data->expression);
-free(data->re);
-free(data->pe);
+pcre2_code_free(data->re);
+pcre2_match_context_free(data->ctxt);
 free(data);
 }
 
@@ -161,8 +162,8 @@
 pcre_dup->expression = pcre_src->expression;
 pcre_dup->options = pcre_src->options;
 pcre_dup->search_offset = 0;
-pcre_dup->pe = pcre_src->pe;
 pcre_dup->re = pcre_src->re;
+pcre_dup->ctxt = pcre_src->ctxt;
 }
 
 int PcreAdjustRelativeOffsets(PcreData *pcre, uint32_t search_offset)
@@ -207,8 +208,6 @@
 
 if (sc->pcre_ovector_size > s_ovector_max)
 s_ovector_max = sc->pcre_ovector_size;
-
-sc->pcre_ovector = (int 

Bug#1058752: marked as done (coreutils: cp/mv changed return code in incompatible way)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2024 14:36:42 +
with message-id 
and subject line Bug#1058752: fixed in coreutils 9.4-3
has caused the Debian Bug report #1058752,
regarding coreutils: cp/mv changed return code in incompatible way
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.)


-- 
1058752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058752
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: coreutils
Version: 9.4-1
Severity: serious
Tags: upstream
Control: affects -1 initramfs-tools scanbd

Hi,

cp and mv -n changed their behaviour with regard to their exit code
when doing nothing, and also now write to stderr.

This causes a few problems in existing packages:

1) initramfs-tools autopkgtests fail, and it is unclear if
initramfs images with busybox actually work. Compare #1058630 and
[1]

2) scanbd now fails to install, see #1058749

And maybe other, so far unreported problems.


The upstream bug report appears to be stalled:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62572

What will be done about this?


Should all affected packages (which are these?) workaround the
fallout?


Chris



[1] https://ci.debian.net/packages/i/initramfs-tools/testing/amd64/41037580/
--- End Message ---
--- Begin Message ---
Source: coreutils
Source-Version: 9.4-3
Done: Michael Stone 

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

Debian distribution maintenance software
pp.
Michael Stone  (supplier of updated coreutils 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, 02 Jan 2024 08:54:03 -0500
Source: coreutils
Binary: coreutils coreutils-dbgsym
Architecture: source amd64
Version: 9.4-3
Distribution: unstable
Urgency: low
Maintainer: Michael Stone 
Changed-By: Michael Stone 
Description:
 coreutils  - GNU core utilities
Closes: 1058752
Changes:
 coreutils (9.4-3) unstable; urgency=low
 .
   * remove arch restriction from libssl-dev build-depend
   * revert cp -n behavior to debian 12 & prior (Closes: #1058752)
   * add deprecation/compatibility warning for above
Checksums-Sha1:
 21349e63dcc1114be875611b9a9f0984360eb018 1860 coreutils_9.4-3.dsc
 820dad0b53fdbd38941ca21a4d7e953ec932c294 29716 coreutils_9.4-3.debian.tar.xz
 75f9b87d874cf3165ce93898f020bae893e11c46 6996564 
coreutils-dbgsym_9.4-3_amd64.deb
 1ecaedf62cb98d59f15b921a2dc3d06c1c206992 8362 coreutils_9.4-3_amd64.buildinfo
 a2943e2d642f274c6002ea23d7e3843d1d5b3ce3 2950596 coreutils_9.4-3_amd64.deb
Checksums-Sha256:
 ca3e625d24ed3983ec88b11d80ae0200e89eb70f719f6da352cfa28a64d8b6fe 1860 
coreutils_9.4-3.dsc
 a4b4a1ee99cf8114a438b592cd7ffcbb3eb17ff8b8b7ca717509112481527567 29716 
coreutils_9.4-3.debian.tar.xz
 10f1155ec6267f64352b2e616dc7e524da83bfc923c4066200b0d9e57a30f7f8 6996564 
coreutils-dbgsym_9.4-3_amd64.deb
 19b02edc87ebc73968716111f5a1eaf89826884d7f346361629b700dff815175 8362 
coreutils_9.4-3_amd64.buildinfo
 7d13d49e4b1454a680c60e28b08ee589ec8ec022bf9b8bd122eee19b185fd11b 2950596 
coreutils_9.4-3_amd64.deb
Files:
 23c32a4b5b4c509c28525523e2a9a589 1860 utils required coreutils_9.4-3.dsc
 55f996d3650ab9ce331f9eab2e84f08e 29716 utils required 
coreutils_9.4-3.debian.tar.xz
 5002c2925e520cd83d8f2cb536472b7f 6996564 debug optional 
coreutils-dbgsym_9.4-3_amd64.deb
 5ceeedaf8ee12bb5c7b0b502338157a4 8362 utils required 
coreutils_9.4-3_amd64.buildinfo
 7adffc2c2d42da93250befe88991851e 2950596 utils required 
coreutils_9.4-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAtUxX/EfDh4C9hqs3PoR/94FAmWUGPIACgkQ9hqs3PoR
/96k2w/+JWVIX+rMbzji6yUoKe3Rsxz2A29BkCoF/S27XAL2ngZWtoFkxD8/647k
ay5/rJeVHxBdNHUvOGhB/rD46ITok0oEATx+R8IGMvpN/my7OVQ3ZC7lU9WNSnGB
demG3+w1DZO+nwXAGVDqG+xNhfpB0hJTovxLixd3ConRDduyE7aItClDlgF7njkj
Ndpcyx6B3IEiT/reNe3vQPZXWBYW5Zp5HH/ccBm9EHDoPT6bnSNfyZhmcSn2sBrp
g6gazWnR6FWxrBz0Pl1ZmnbjF53Qflf9lMlX++o4gxf+1Bfelmo0Npv7ylEQ4Vhs
QVBJbZGdV4DVBW7qTSET6QSRczplp61r6pGDL2mQ2K83rzMe6LO1zJfbaMGDGgvE
jXOn3ozkoIA6CjS+o+nIpVN8FgxA2TV7gTulPCqGS/AC5k0N4CHdiyly/7KDL271
KNmzgO6BQ8BmJaVGMceetKEECaapzIE0TU8s4cfMIrJSKst+Sxu4X9qSq4PAI97t

Processed: Re: Bug#999956: snort: depends on obsolete pcre3 library

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #56 [src:snort] snort: depends on obsolete pcre3 library
Added tag(s) patch.

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

Processed: Re: Bug#1000126: gpt: depends on obsolete pcre3 library

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1000126 [src:gpt] gpt: depends on obsolete pcre3 library
Added tag(s) patch.

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

Bug#1000126: gpt: depends on obsolete pcre3 library

[Yavor Doganov]

Control: tags -1 + patch

Please find a patch attached.
Description: Port to PCRE2.
Bug-Debian: https://bugs.debian.org/1000126
Author: Yavor Doganov 
Forwarded: no
Last-Update: 2024-01-02
---

--- gpt.orig/configure.ac
+++ gpt/configure.ac
@@ -109,10 +109,10 @@
 
 # AC_MSG_CHECKING(for pcre)
 
-AC_CHECK_PROG(has_pcre, pcre-config, yes)
+AC_CHECK_PROG(has_pcre, pcre2-config, yes)
 
 if test "x$has_pcre" = "xyes"; then
-  PCRE_CONFIG="pcre-config"
+  PCRE_CONFIG="pcre2-config"
 else
   AC_MSG_ERROR(
   [
@@ -123,8 +123,8 @@
 
 #pcrecpp
 
-PCRE_INC=`${PCRE_CONFIG} --cglags`
-PCRE_LIB="-L`${PCRE_CONFIG} --prefix`/lib -lpcrecpp"
+PCRE_INC=`${PCRE_CONFIG} --cflags`
+PCRE_LIB=`${PCRE_CONFIG} --libs8`
 AC_SUBST(PCRE_INC)
 AC_SUBST(PCRE_LIB)
 
--- gpt.orig/src/modules/interpreter/InterpreterDBG.cpp
+++ gpt/src/modules/interpreter/InterpreterDBG.cpp
@@ -33,7 +33,8 @@
   #include 
 #endif
 
-#include 
+#define PCRE2_CODE_UNIT_WIDTH 8
+#include 
 #include 
 
 #ifndef WIN32
@@ -403,15 +404,40 @@
 void InterpreterDBG::processBreakpointCMD(string& bpcommand) {
  //cerr << "process breakpoint " << bpcommand << endl;
 
-  string cmd;
-  string file;
-  int line;
-  pcrecpp::RE re("breakpoint 
cmd=(add|remove).*file=\"([^\"]*)\".*line=(\\d+)");
-  if(!re.FullMatch(bpcommand, , , )) {
+  pcre2_code *re;
+  pcre2_match_data *md;
+  PCRE2_UCHAR *str;
+  PCRE2_SPTR pat, subj;
+  PCRE2_SIZE offset;
+  int line, rc;
+
+  pat = reinterpret_cast("breakpoint 
cmd=(add|remove).*file=\"([^\"]*)\".*line=(\\d+)");
+  subj = reinterpret_cast(bpcommand.c_str());
+  re = pcre2_compile(pat, PCRE2_ZERO_TERMINATED, 0, , , nullptr);
+  if(offset != 0) {
+return;
+  }
+
+  md = pcre2_match_data_create_from_pattern(re, nullptr);
+  rc = pcre2_match(re, subj, bpcommand.length(), 0, 0, md, nullptr);
+  pcre2_code_free(re);
+  if(rc != 4) {
 //cerr << PACKAGE << ": comando invalido (2): \"" << cmd << "\"" << endl;
+pcre2_match_data_free(md);
 return;
   }
 
+  pcre2_substring_get_bynumber(md, 1, , );
+  string cmd(reinterpret_cast(str));
+  pcre2_substring_free(str);
+  pcre2_substring_get_bynumber(md, 2, , );
+  string file(reinterpret_cast(str));
+  pcre2_substring_free(str);
+  pcre2_substring_get_bynumber(md, 3, , );
+  line = atoi((const char *)str);
+  pcre2_substring_free(str);
+  pcre2_match_data_free(md);
+
   //cerr << PACKAGE << ": capturado:" << cmd << ":" << file << ":" << line << 
endl;
 
   if(cmd == "add") {

Bug#1058221: marked as done (confusable-homoglyphs: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2024 13:49:26 +
with message-id 
and subject line Bug#1058221: fixed in confusable-homoglyphs 3.2.0-3
has caused the Debian Bug report #1058221,
regarding confusable-homoglyphs: FTBFS: AttributeError: module 'configparser' 
has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?
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.)


-- 
1058221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: confusable-homoglyphs
Version: 3.2.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py clean 
> /<>/versioneer.py:467: SyntaxWarning: invalid escape sequence 
> '\s'
>   LONG_VERSION_PY['git'] = '''
> Traceback (most recent call last):
>   File "/<>/setup.py", line 33, in 
> version=versioneer.get_version(),
> 
>   File "/<>/versioneer.py", line 1405, in get_version
> return get_versions()["version"]
>^^
>   File "/<>/versioneer.py", line 1339, in get_versions
> cfg = get_config_from_root(root)
>   ^^
>   File "/<>/versioneer.py", line 399, in get_config_from_root
> parser = configparser.SafeConfigParser()
>  ^
> AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. 
> Did you mean: 'RawConfigParser'?
> E: pybuild pybuild:395: clean: plugin distutils failed with: exit code=1: 
> python3.12 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.12 3.11" 
> returned exit code 13
> make: *** [debian/rules:7: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/12/12/confusable-homoglyphs_3.2.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231212;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231212=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: confusable-homoglyphs
Source-Version: 3.2.0-3
Done: Elena Grandi 

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

Debian distribution maintenance software
pp.
Elena Grandi  (supplier of updated confusable-homoglyphs 
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: Tue, 02 Jan 2024 14:09:51 +0100
Source: confusable-homoglyphs
Architecture: source
Version: 3.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Elena Grandi 
Closes: 1058221
Changes:
 confusable-homoglyphs (3.2.0-3) unstable; urgency=medium
 .
   * Update ConfigParser usage for python > 3.2. Closes: #1058221
   * Bump Standards-Version to 4.6.2 (no changes needed).
   * Bump copyright dates.
   * Added autopkgtests.
Checksums-Sha1:
 cc267b55f3395bfb6747a8d0f5838b9150b95406 1897 confusable-homoglyphs_3.2.0-3.dsc
 f227909b2d7d8941811cfcf64428658d254d23fd 3776 
confusable-homoglyphs_3.2.0-3.debian.tar.xz
 4400bfb004333b752a3ed1aa27b44aa1bf2c0e81 6713 
confusable-homoglyphs_3.2.0-3_amd64.buildinfo
Checksums-Sha256:
 c097ca078236edb8f41f00db664f89938a52e9562aa7478a45ce8d98ea00062b 1897 

Bug#1057693: marked as done (valgrind: i386 vex x86->IR: unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26)

[Debian Bug Tracking System]

Your message dated Tue, 2 Jan 2024 13:53:31 +0100
with message-id 
and subject line Re: valgrind: i386 vex x86->IR: unhandled instruction bytes: 
0x2E 0x8D 0xB4 0x26
has caused the Debian Bug report #1057693,
regarding valgrind: i386 vex x86->IR: unhandled instruction bytes: 0x2E 0x8D 
0xB4 0x26
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.)


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

Hi.  During debci autopkgtest of a new version of libgssglue on i386 I
got a failure like this, which is fatal and execution halts.

117s vex x86->IR: unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26
117s ==5711== valgrind: Unrecognised instruction at address 0x4d285c8.
117s ==5711==at 0x4D285C8: ??? (in 
/usr/lib/i386-linux-gnu/libgssglue.so.1.0.0)
117s ==5711==by 0x4D27893: ??? (in 
/usr/lib/i386-linux-gnu/libgssglue.so.1.0.0)
117s ==5711==by 0x4D27B0E: ??? (in 
/usr/lib/i386-linux-gnu/libgssglue.so.1.0.0)
117s ==5711==by 0x4D27069: gss_import_name (in 
/usr/lib/i386-linux-gnu/libgssglue.so.1.0.0)
117s ==5711==by 0x486BA0F: ??? (in 
/usr/lib/i386-linux-gnu/libgsasl.so.18.0.0)
117s ==5711==by 0x485757C: gsasl_step (in 
/usr/lib/i386-linux-gnu/libgsasl.so.18.0.0)
117s ==5711==by 0x4857623: gsasl_step64 (in 
/usr/lib/i386-linux-gnu/libgsasl.so.18.0.0)
117s ==5711==by 0x10B387: ??? (in /usr/bin/gsasl)
117s ==5711==by 0x4ADE7C4: (below main) (libc_start_call_main.h:58)
117s ==5711== Your program just tried to execute an instruction that Valgrind
117s ==5711== did not recognise.  There are two possible reasons for this.
117s ==5711== 1. Your program has a bug and erroneously jumped to a non-code
117s ==5711==location.  If you are running Memcheck and you just saw a
117s ==5711==warning about a bad jump, it's probably your program's fault.
117s ==5711== 2. The instruction is legitimate but Valgrind doesn't handle it,
117s ==5711==i.e. it's Valgrind's fault.  If you think this is the case or
117s ==5711==you are not sure, please let us know and we'll try to fix it.
117s ==5711== Either way, Valgrind will now raise a SIGILL signal which will
117s ==5711== probably kill your program.
117s ==5711== 
117s ==5711== Process terminating with default action of signal 4 (SIGILL)
117s ==5711==  Illegal opcode at address 0x4D285C8
117s ==5711==at 0x4D285C8: ??? (in 
/usr/lib/i386-linux-gnu/libgssglue.so.1.0.0)
117s ==5711==by 0x4D27893: ??? (in 
/usr/lib/i386-linux-gnu/libgssglue.so.1.0.0)
117s ==5711==by 0x4D27B0E: ??? (in 
/usr/lib/i386-linux-gnu/libgssglue.so.1.0.0)
117s ==5711==by 0x4D27069: gss_import_name (in 
/usr/lib/i386-linux-gnu/libgssglue.so.1.0.0)
117s ==5711==by 0x486BA0F: ??? (in 
/usr/lib/i386-linux-gnu/libgsasl.so.18.0.0)
117s ==5711==by 0x485757C: gsasl_step (in 
/usr/lib/i386-linux-gnu/libgsasl.so.18.0.0)
117s ==5711==by 0x4857623: gsasl_step64 (in 
/usr/lib/i386-linux-gnu/libgsasl.so.18.0.0)
117s ==5711==by 0x10B387: ??? (in /usr/bin/gsasl)
117s ==5711==by 0x4ADE7C4: (below main) (libc_start_call_main.h:58)

I can reproduce this in debian sid like this, on my amd64 laptop:

podman run --arch 386  -it --rm debian:unstable-slim
apt update
apt install valgrind gsasl
apt dist-upgrade
valgrind --error-exitcode=1 /usr/bin/gsasl -m GSSAPI -d --no-starttls --imap 
no-such-domain.example 143

Running it without valgrind works:

/usr/bin/gsasl -m GSSAPI -d --no-starttls --imap no-such-domain.example 143
/usr/bin/gsasl: no-such-domain.example: Name or service not known

However running it under gdb doesn't seem to work either:

root@65b9c363c623:/# gdb --silent /usr/bin/gsasl
Reading symbols from /usr/bin/gsasl...
(No debugging symbols found in /usr/bin/gsasl)
(gdb) r -m GSSAPI -d --no-starttls --imap no-such-domain.example 143
Starting program: /usr/bin/gsasl -m GSSAPI -d --no-starttls --imap 
no-such-domain.example 143

warning: Error disabling address space randomization: Success
warning: Could not trace the inferior process.
warning: ptrace: Operation not permitted
During startup program exited with code 127.

The build log for this libgssglue on i386 (built just a day ago in
debian sid) is here:

https://buildd.debian.org/status/fetch.php?pkg=libgssglue=i386=0.8-1=1701797253=0

Libgssglue is a simple C library with no dependencies, and no complexity
in the build system, but do you notice anything odd with the compiler
settings here that could cause it to generate unwanted instructions?

If the libgssglue library 

Bug#1057693: valgrind: i386 vex x86->IR: unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26

[Aurelien Jarno]

Hi,

I have done a NMU to fix this issue blocking the migration of many
packages to testing. Please find the debdiff attached.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net
diff -Nru valgrind-3.20.0/debian/changelog valgrind-3.20.0/debian/changelog
--- valgrind-3.20.0/debian/changelog2023-12-01 12:53:02.0 +0100
+++ valgrind-3.20.0/debian/changelog2024-01-02 13:09:38.0 +0100
@@ -1,3 +1,11 @@
+valgrind (1:3.20.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply fix from upstream to add support for new x86 nops patterns.  Closes
+#1057693.
+
+ -- Aurelien Jarno   Tue, 02 Jan 2024 12:09:38 +
+
 valgrind (1:3.20.0-2) unstable; urgency=medium
 
   * [armhf] default.supp: add suppression for memory accesses below the stack
diff -Nru valgrind-3.20.0/debian/patches/14-x86-new-nops.patch 
valgrind-3.20.0/debian/patches/14-x86-new-nops.patch
--- valgrind-3.20.0/debian/patches/14-x86-new-nops.patch1970-01-01 
01:00:00.0 +0100
+++ valgrind-3.20.0/debian/patches/14-x86-new-nops.patch2024-01-02 
11:53:58.0 +0100
@@ -0,0 +1,123 @@
+From: Paul Floyd 
+Date: Sun, 17 Dec 2023 13:18:51 + (+0100)
+Subject: Bug 478624 - Valgrind incompatibility with binutils-2.42 on x86 with 
new nop patterns... 
+X-Git-Url: 
https://sourceware.org/git/?p=valgrind.git;a=commitdiff_plain;h=d35005cef8ad8207542738812705ceabf137d7e0
+
+Bug 478624 - Valgrind incompatibility with binutils-2.42 on x86 with new nop 
patterns (unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26)
+
+It was a bit of a struggle to get the testcase to build
+with both clang and gcc (oddly enough gcc was more difficult) so
+I just resorted to using .byte arrays.
+---
+
+diff --git a/VEX/priv/guest_x86_toIR.c b/VEX/priv/guest_x86_toIR.c
+index 5d6e6dc64f..3b6efb3873 100644
+--- a/VEX/priv/guest_x86_toIR.c
 b/VEX/priv/guest_x86_toIR.c
+@@ -8198,7 +8198,7 @@ DisResult disInstr_X86_WRK (
+  delta += 5;
+  goto decode_success;
+   }
+-  /* Don't barf on recent binutils padding,
++  /* Don't barf on recent (2010) binutils padding,
+  all variants of which are: nopw %cs:0x0(%eax,%eax,1)
+  66 2e 0f 1f 84 00 00 00 00 00
+  66 66 2e 0f 1f 84 00 00 00 00 00
+@@ -8223,6 +8223,26 @@ DisResult disInstr_X86_WRK (
+  }
+   }
+ 
++  /* bug478624 GNU binutils uses a leal of esi into itself with
++ a zero offset and CS prefix as an 8 byte no-op (Dec 2023).
++ Since the CS prefix is hardly ever used we don't do much
++ to decode it, just a few cases for conditional branches.
++ So add handling here with other pseudo-no-ops.
++   */
++  if (code[0] == 0x2E && code[1] == 0x8D) {
++ if (code[2] == 0x74 && code[3] == 0x26 && code[4] == 0x00) {
++DIP("leal %%cs:0(%%esi,%%eiz,1),%%esi\n");
++delta += 5;
++goto decode_success;
++ }
++ if (code[2] == 0xB4 && code[3] == 0x26 && code[4] == 0x00
++ && code[5] == 0x00 && code[6] == 0x00 && code[7] == 0x00) {
++DIP("leal %%cs:0(%%esi,%%eiz,1),%%esi\n");
++delta += 8;
++goto decode_success;
++ }
++  }
++
+   // Intel CET requires the following opcodes to be treated as NOPs
+   // with any prefix and ModRM, SIB and disp combination:
+   // "0F 19", "0F 1C", "0F 1D", "0F 1E", "0F 1F"
+diff --git a/none/tests/x86/Makefile.am b/none/tests/x86/Makefile.am
+index 3ecd1ad3c2..dbae865712 100644
+--- a/none/tests/x86/Makefile.am
 b/none/tests/x86/Makefile.am
+@@ -52,6 +52,7 @@ EXTRA_DIST = \
+   fxtract.stdout.exp fxtract.stderr.exp fxtract.vgtest \
+   fxtract.stdout.exp-older-glibc \
+   getseg.stdout.exp getseg.stderr.exp getseg.vgtest \
++  gnu_binutils_nop.stderr.exp gnu_binutils_nop.vgtest \
+   incdec_alt.stdout.exp incdec_alt.stderr.exp incdec_alt.vgtest \
+   int.stderr.exp int.stdout.exp int.disabled \
+   $(addsuffix .stderr.exp,$(INSN_TESTS)) \
+@@ -100,6 +101,7 @@ check_PROGRAMS = \
+   fpu_lazy_eflags \
+   fxtract \
+   getseg \
++  gnu_binutils_nop \
+   incdec_alt \
+   $(INSN_TESTS) \
+   int \
+diff --git a/none/tests/x86/gnu_binutils_nop.c 
b/none/tests/x86/gnu_binutils_nop.c
+new file mode 100644
+index 00..412a4c2cbc
+--- /dev/null
 b/none/tests/x86/gnu_binutils_nop.c
+@@ -0,0 +1,34 @@
++int main(void)
++{
++// GNU binutils uses various opcodes as alternatives for nop
++// the idea is that it is faster to execute one large opcode
++// with no side-effects than multiple repetitions of the
++// single byte 'nop'. This gives more choice when code
++// needs to be padded.
++   
++   // the following is based on
++   // https://sourceware.org/cgit/binutils-gdb/tree/gas/config/tc-i386.c#n1256
++
++// one byte
++__asm__ 

Processed: tagging 1000087

[Debian Bug Tracking System]

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

> tags 187 + fixed-upstream
Bug #187 [src:evqueue-core] evqueue-core: depends on obsolete pcre3 library
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: tagging 1000130

[Debian Bug Tracking System]

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

> tags 1000130 + fixed-upstream
Bug #1000130 [src:condor] condor: depends on obsolete pcre3 library
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#1058383: marked as done (isbg: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2024 11:04:28 +
with message-id 
and subject line Bug#1056415: fixed in isbg 2.3.1-4
has caused the Debian Bug report #1056415,
regarding isbg: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p "3.12 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.)


-- 
1056415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: isbg
Version: 2.3.1-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231212 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,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:310: python3.12 setup.py config 
> running config
> I: pybuild base:310: python3.11 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:310: /usr/bin/python3.12 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_isbg/build/isbg
> copying isbg/utils.py -> 
> /<>/.pybuild/cpython3_3.12_isbg/build/isbg
> copying isbg/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_isbg/build/isbg
> copying isbg/imaputils.py -> 
> /<>/.pybuild/cpython3_3.12_isbg/build/isbg
> copying isbg/secrets.py -> 
> /<>/.pybuild/cpython3_3.12_isbg/build/isbg
> copying isbg/__main__.py -> 
> /<>/.pybuild/cpython3_3.12_isbg/build/isbg
> copying isbg/isbg.py -> 
> /<>/.pybuild/cpython3_3.12_isbg/build/isbg
> copying isbg/spamproc.py -> 
> /<>/.pybuild/cpython3_3.12_isbg/build/isbg
> copying isbg/sa_unwrap.py -> 
> /<>/.pybuild/cpython3_3.12_isbg/build/isbg
> I: pybuild base:310: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_isbg/build/isbg
> copying isbg/utils.py -> 
> /<>/.pybuild/cpython3_3.11_isbg/build/isbg
> copying isbg/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_isbg/build/isbg
> copying isbg/imaputils.py -> 
> /<>/.pybuild/cpython3_3.11_isbg/build/isbg
> copying isbg/secrets.py -> 
> /<>/.pybuild/cpython3_3.11_isbg/build/isbg
> copying isbg/__main__.py -> 
> /<>/.pybuild/cpython3_3.11_isbg/build/isbg
> copying isbg/isbg.py -> 
> /<>/.pybuild/cpython3_3.11_isbg/build/isbg
> copying isbg/spamproc.py -> 
> /<>/.pybuild/cpython3_3.11_isbg/build/isbg
> copying isbg/sa_unwrap.py -> 
> /<>/.pybuild/cpython3_3.11_isbg/build/isbg
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:310: cd /<>/.pybuild/cpython3_3.12_isbg/build; 
> python3.12 -m pytest -m "not spamassassin"
> = test session starts 
> ==
> platform linux -- Python 3.12.1, pytest-7.4.3, pluggy-1.3.0
> rootdir: /<>
> collected 0 items / 7 errors
> 
>  ERRORS 
> 
> __ ERROR collecting .pybuild/cpython3_3.12_isbg/build/tests/test___main__.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/python.py:531: in collect
> self._inject_setup_module_fixture()
> /usr/lib/python3/dist-packages/_pytest/python.py:545: in 
> _inject_setup_module_fixture
> self.obj, ("setUpModule", "setup_module")
> /usr/lib/python3/dist-packages/_pytest/python.py:310: in obj
> self._obj = obj = self._getobj()
> /usr/lib/python3/dist-packages/_pytest/python.py:528: in _getobj
> return self._importtestmodule()
> /usr/lib/python3/dist-packages/_pytest/python.py:617: in _importtestmodule
> mod = import_path(self.path, mode=importmode, root=self.config.rootpath)
> /usr/lib/python3/dist-packages/_pytest/pathlib.py:567: in import_path
> importlib.import_module(module_name)
> /usr/lib/python3.12/importlib/__init__.py:90: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> :1387: in _gcd_import
> ???
> :1360: in _find_and_load
> ???
> :1331: in _find_and_load_unlocked
> ???
> :935: in _load_unlocked
> ???
> /usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:186: in 
> exec_module
> exec(co, module.__dict__)
> tests/test___main__.py:39: in 
> from 

Bug#1056415: marked as done (isbg's autopkg tests fail with Python 3.12)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2024 11:04:28 +
with message-id 
and subject line Bug#1056415: fixed in isbg 2.3.1-4
has caused the Debian Bug report #1056415,
regarding isbg's autopkg tests fail with Python 3.12
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.)


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

Package: src:isbg
Version: 2.3.1-3
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

isbg's autopkg tests fail with Python 3.12:

[...]
376s === python3.12 ===
377s = test session starts 
==

377s platform linux -- Python 3.12.0+, pytest-7.4.3, pluggy-1.3.0
377s rootdir: /tmp/autopkgtest.P34bZy/autopkgtest_tmp
377s collected 0 items / 7 errors
377s
377s  ERRORS 

377s ___ ERROR collecting tests/test___main__.py 


377s /usr/lib/python3/dist-packages/_pytest/runner.py:341: in from_call
377s result: Optional[TResult] = func()
377s /usr/lib/python3/dist-packages/_pytest/runner.py:372: in 
377s call = CallInfo.from_call(lambda: list(collector.collect()), 
"collect")

377s /usr/lib/python3/dist-packages/_pytest/python.py:531: in collect
377s self._inject_setup_module_fixture()
377s /usr/lib/python3/dist-packages/_pytest/python.py:545: in 
_inject_setup_module_fixture

377s self.obj, ("setUpModule", "setup_module")
377s /usr/lib/python3/dist-packages/_pytest/python.py:310: in obj
377s self._obj = obj = self._getobj()
377s /usr/lib/python3/dist-packages/_pytest/python.py:528: in _getobj
377s return self._importtestmodule()
377s /usr/lib/python3/dist-packages/_pytest/python.py:617: in 
_importtestmodule
377s mod = import_path(self.path, mode=importmode, 
root=self.config.rootpath)

377s /usr/lib/python3/dist-packages/_pytest/pathlib.py:567: in import_path
377s importlib.import_module(module_name)
377s /usr/lib/python3.12/importlib/__init__.py:90: in import_module
377s return _bootstrap._gcd_import(name[level:], package, level)
377s :1381: in _gcd_import
377s ???
377s :1354: in _find_and_load
377s ???
377s :1325: in _find_and_load_unlocked
377s ???
377s :929: in _load_unlocked
377s ???
377s /usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:186: in 
exec_module

377s exec(co, module.__dict__)
377s tests/test___main__.py:39: in 
377s from isbg import __main__, isbg  # noqa: E402
377s /usr/lib/python3/dist-packages/isbg/__init__.py:10: in 
377s from .isbg import ISBG, ISBGError, __version__, __exitcodes__, 
__license__

377s /usr/lib/python3/dist-packages/isbg/isbg.py:23: in 
377s from isbg import imaputils
377s /usr/lib/python3/dist-packages/isbg/imaputils.py:40: in 
377s Email = TypeVar(email.message.Message)
377s E   TypeError: typevar() argument 'name' must be str, not type
377s ___ ERROR collecting tests/test_imaputils.py 
___

377s /usr/lib/python3/dist-packages/_pytest/runner.py:341: in from_call
377s result: Optional[TResult] = func()
377s /usr/lib/python3/dist-packages/_pytest/runner.py:372: in 
377s call = CallInfo.from_call(lambda: list(collector.collect()), 
"collect")

377s /usr/lib/python3/dist-packages/_pytest/python.py:531: in collect
377s self._inject_setup_module_fixture()
377s /usr/lib/python3/dist-packages/_pytest/python.py:545: in 
_inject_setup_module_fixture

377s self.obj, ("setUpModule", "setup_module")
377s /usr/lib/python3/dist-packages/_pytest/python.py:310: in obj
377s self._obj = obj = self._getobj()
377s /usr/lib/python3/dist-packages/_pytest/python.py:528: in _getobj
377s return self._importtestmodule()
377s /usr/lib/python3/dist-packages/_pytest/python.py:617: in 
_importtestmodule
377s mod = import_path(self.path, mode=importmode, 
root=self.config.rootpath)

377s /usr/lib/python3/dist-packages/_pytest/pathlib.py:567: in import_path
377s importlib.import_module(module_name)
377s /usr/lib/python3.12/importlib/__init__.py:90: in import_module
377s return _bootstrap._gcd_import(name[level:], package, level)
377s :1381: in _gcd_import
377s ???
377s :1354: in _find_and_load
377s ???
377s :1325: in _find_and_load_unlocked
377s ???
377s :929: in _load_unlocked
377s ???
377s /usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:186: in 
exec_module

377s exec(co, module.__dict__)
377s tests/test_imaputils.py:40: in 

Processed: bug 1056054 is forwarded to https://github.com/openpmix/prrte/issues/1836

[Debian Bug Tracking System]

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

> forwarded 1056054 https://github.com/openpmix/prrte/issues/1836
Bug #1056054 [openmpi-doc] openmpi-doc: /usr/share/man/man1/pterm.1.gz is 
already shipped by pterm
Set Bug forwarded-to-address to 'https://github.com/openpmix/prrte/issues/1836'.
> thanks
Stopping processing here.

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

Bug#1038603: libisl23 0.25-1: amd64/i386 baseline violation: uses BMI instructions)

[Matthias Klose]

On 02.01.24 11:50, Aurelien Jarno wrote:

Hi Matthias,

On 2023-07-23 02:34, Roman Lebedev wrote:

Package: libisl23
Followup-For: Bug #1038603
X-Debbugs-Cc: Debian GCC Maintainers , 
debian-rele...@lists.debian.org

While the issue has been resolved in isl 0.26-3,
which was uploaded to unstable on 2023-06-19,
nothing has been done for the stable release,
and Debian 12.1 still comes with a "miscompiled" isl 0.25-1,
and thus gcc is still somewhat unusable(*) on older hardware(**)


Would it be possible to schedule an upload with the same fix to
bookworm?


please go ahead

Matthias

Bug#1038603: libisl23 0.25-1: amd64/i386 baseline violation: uses BMI instructions)

[Aurelien Jarno]

Hi Matthias,

On 2023-07-23 02:34, Roman Lebedev wrote:
> Package: libisl23
> Followup-For: Bug #1038603
> X-Debbugs-Cc: Debian GCC Maintainers , 
> debian-rele...@lists.debian.org
> 
> While the issue has been resolved in isl 0.26-3,
> which was uploaded to unstable on 2023-06-19,
> nothing has been done for the stable release,
> and Debian 12.1 still comes with a "miscompiled" isl 0.25-1,
> and thus gcc is still somewhat unusable(*) on older hardware(**)

Would it be possible to schedule an upload with the same fix to
bookworm?

Thanks
Aurelien 

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net


signature.asc
Description: PGP signature

Bug#1059842: FTBFS: test fails: ZFP lib not compiled with -DBIT_STREAM_WORD_TYPE=uint8

[Drew Parsons]

Package: python3-hdf5plugin
Version: 4.0.1-3
Severity: serious
Justification: FTBFS

python3-hdf5plugin has started failing testZfp,
causing both FTBFS and debci failure.

The error message from debci is

 56s ERROR: testZfp (__main__.TestHDF5PluginRW.testZfp) (options={'lossless': 
False}, dtype=)
 56s Write/read test with zfp filter plugin
 56s --
 56s Traceback (most recent call last):
 56s   File "/usr/lib/python3/dist-packages/hdf5plugin/test.py", line 245, in 
testZfp
 56s self._test('zfp', dtype=dtype, **options)
 56s   File "/usr/lib/python3/dist-packages/hdf5plugin/test.py", line 86, in 
_test
 56s f.create_dataset("data", data=data, chunks=data.shape, **args)
 56s   File 
"/usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/_hl/group.py", line 
183, in create_dataset
 56s dsid = dataset.make_new_dset(group, shape, dtype, data, name, **kwds)
 56s^^
 56s   File 
"/usr/lib/python3/dist-packages/h5py/_debian_h5py_serial/_hl/dataset.py", line 
163, in make_new_dset
 56s dset_id = h5d.create(parent.id, name, tid, sid, dcpl=dcpl, dapl=dapl)
 56s   ^^^
 56s   File "h5py/_debian_h5py_serial/_objects.pyx", line 54, in 
h5py._debian_h5py_serial._objects.with_phil.wrapper
 56s   File "h5py/_debian_h5py_serial/_objects.pyx", line 55, in 
h5py._debian_h5py_serial._objects.with_phil.wrapper
 56s   File "h5py/_debian_h5py_serial/h5d.pyx", line 138, in 
h5py._debian_h5py_serial.h5d.create
 56s ValueError: Unable to create dataset (ZFP lib not compiled with 
-DBIT_STREAM_WORD_TYPE=uint8)
 
 
 
There is a "BIT_STREAM_WORD_TYPE uint8" build definition in
setup.py. Sounds like it might not have been activated but is needed.




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

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

Versions of packages python3-hdf5plugin depends on:
ii  python3   3.11.6-1
ii  python3-h5py  3.9.0-5

Versions of packages python3-hdf5plugin recommends:
ii  hdf5-filter-plugin [hdf5-filter-plugin-lz4-seria  0.0~git2022.49e3b65-4
l]
ii  hdf5-filter-plugin-blosc-serial   0.0~git20220616.9683f7d-5
pn  hdf5-filter-plugin-bz2-serial 
ii  hdf5-filter-plugin-zfp-serial 1.1.0+git20221021-4
ii  hdf5-plugin-lzf   3.9.0-5

python3-hdf5plugin suggests no packages.

-- no debconf information

Bug#1056415: marked as pending in isbg

[Jochen Sprickerhof]

Control: tag -1 pending

Hello,

Bug #1056415 in isbg 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/isbg/-/commit/4217495a213c64a3162c167f69900135120856d4


Drop extra TypeVar, fails in Python 3.12

Closes: #1056415


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1056415

Processed: Bug#1056415 marked as pending in isbg

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1056415 [src:isbg] isbg's autopkg tests fail with Python 3.12
Bug #1058383 [src:isbg] isbg: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Added tag(s) pending.
Added tag(s) pending.

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

Processed: tagging 770171

[Debian Bug Tracking System]

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

> tags 770171 + bookworm sid trixie
Bug #770171 [fail2ban] sshd jail fails when system solely relies on systemd 
journal for logging
Added tag(s) bookworm, sid, and trixie.
> thanks
Stopping processing here.

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

Processed: tagging 1056415, merging 1056415 1058383

[Debian Bug Tracking System]

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

> tags 1056415 + ftbfs
Bug #1056415 [src:isbg] isbg's autopkg tests fail with Python 3.12
Added tag(s) ftbfs.
> merge 1056415 1058383
Bug #1056415 [src:isbg] isbg's autopkg tests fail with Python 3.12
Bug #1058383 [src:isbg] isbg: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Merged 1056415 1058383
> thanks
Stopping processing here.

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

Bug#1058221: marked as pending in confusable-homoglyphs

[Elena Grandi]

Control: tag -1 pending

Hello,

Bug #1058221 in confusable-homoglyphs 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/confusable-homoglyphs/-/commit/440fd4286565c307610d351caf8b862cb5c75d4c


Update ConfigParser usage for python > 3.2. Closes: #1058221


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1058221

Processed: Bug#1058221 marked as pending in confusable-homoglyphs

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1058221 [src:confusable-homoglyphs] confusable-homoglyphs: FTBFS: 
AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did 
you mean: 'RawConfigParser'?
Added tag(s) pending.

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

Processed: Bug#1040092 marked as pending in python-pyftpdlib

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1040092 [src:python-pyftpdlib] python-pyftpdlib: deprecation of Python 
libraries asyncore and asynchat
Added tag(s) pending.

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

Bug#1040092: marked as pending in python-pyftpdlib

[Alexandre Detiste]

Control: tag -1 pending

Hello,

Bug #1040092 in python-pyftpdlib 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-pyftpdlib/-/commit/7f3582eda41a430e302f608d6b477ec764549ce1


new release vendor copy of old asyncore and asynchat

Closes: #1040092


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1040092

Bug#1059839: cython-legacy: autopkgtest regression with Python 3.12 on 32-bit

[Graham Inggs]

Source: cython-legacy
Version: 0.29.36-3
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

cython-legacy's autopkgtests fail with Python 3.12 on 32-bit architectures
[1][2][3].  I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/c/cython-legacy/testing/armel/
[2] https://ci.debian.net/packages/c/cython-legacy/testing/armhf/
[3] https://ci.debian.net/packages/c/cython-legacy/testing/i386/


3519s ==
3519s FAIL: test_raiseMemError (test_unicode.UnicodeTest.test_raiseMemError)
3519s --
3519s Traceback (most recent call last):
3519s File "tests/run/test_unicode.pyx", line 2356, in
test_unicode.UnicodeTest.test_raiseMemError (test_unicode.c:138318)
3519s self.assertRaises(MemoryError, alloc)
3519s AssertionError: MemoryError not raised by lambda
3519s
3519s ==
3519s FAIL: test_raiseMemError (test_unicode.UnicodeTest.test_raiseMemError)
3519s --
3519s Traceback (most recent call last):
3519s File "tests/run/test_unicode.pyx", line 2356, in
test_unicode.UnicodeTest.test_raiseMemError (test_unicode.cpp:138332)
3519s self.assertRaises(MemoryError, alloc)
3519s AssertionError: MemoryError not raised by lambda
3519s
3519s --
3519s Ran 5423 tests in 3411.871s
3519s
3519s FAILED (failures=2, skipped=48)

Bug#1059838: cython: autopkgtest regression with Python 3.12 on ppc64el

[Graham Inggs]

Source: cython
Version: 3.0.7-2
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

cython's autopkgtests fail with Python 3.12 on ppc64el[1].  I've
copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/c/cython/testing/ppc64el/


4439s ==
27113
4439s ERROR: test_many_expressions (test_fstring.TestCase.test_many_expressions)
27114
4439s --
27115
4439s Traceback (most recent call last):
27116
4439s File 
"/usr/lib/python3/dist-packages/setuptools/_distutils/unixccompiler.py",
line 185, in _compile
27117
4439s self.spawn(compiler_so + cc_args + [src, '-o', obj] + extra_postargs)
27118
4439s File "/usr/lib/python3/dist-packages/setuptools/_distutils/ccompiler.py",
line 1041, in spawn
27119
4439s spawn(cmd, dry_run=self.dry_run, **kwargs)
27120
4439s File "/usr/lib/python3/dist-packages/setuptools/_distutils/spawn.py",
line 70, in spawn
27121
4439s raise DistutilsExecError(
27122
4439s distutils.errors.DistutilsExecError: command
'/usr/bin/powerpc64le-linux-gnu-gcc' failed with exit code 1
27123
4439s
27124
4439s During handling of the above exception, another exception occurred:
27125
4439s
27126
4439s Traceback (most recent call last):
27127
4439s File "tests/run/test_fstring.pyx", line 530, in
test_fstring.TestCase.test_many_expressions (test_fstring.c:27468)
27128
4439s cy_eval('[' + ', '.join(build_fstr(i) for i in range(250, 260))
+ ']', x=x, width=width),
27129
4439s File "tests/run/test_fstring.pyx", line 23, in
test_fstring.cy_eval (test_fstring.c:7563)
27130
4439s return cython_inline('return ' + s, force=True, **kwargs)
27131
4439s File "/usr/lib/python3/dist-packages/Cython/Build/Inline.py",
line 289, in cython_inline
27132
4439s build_extension.run()
27133
4439s File 
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build_ext.py",
line 345, in run
27134
4439s self.build_extensions()
27135
4439s File 
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build_ext.py",
line 467, in build_extensions
27136
4439s self._build_extensions_serial()
27137
4439s File 
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build_ext.py",
line 493, in _build_extensions_serial
27138
4439s self.build_extension(ext)
27139
4439s File 
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build_ext.py",
line 548, in build_extension
27140
4439s objects = self.compiler.compile(
27141
4439s ^^
27142
4439s File "/usr/lib/python3/dist-packages/setuptools/_distutils/ccompiler.py",
line 600, in compile
27143
4439s self._compile(obj, src, ext, cc_args, extra_postargs, pp_opts)
27144
4439s File 
"/usr/lib/python3/dist-packages/setuptools/_distutils/unixccompiler.py",
line 187, in _compile
27145
4439s raise CompileError(msg)
27146
4439s distutils.errors.CompileError: command
'/usr/bin/powerpc64le-linux-gnu-gcc' failed with exit code 1
27147
4439s
27148
4439s ==
27149
4439s ERROR: test_many_expressions (test_fstring.TestCase.test_many_expressions)
27150
4439s --
27151
4439s Traceback (most recent call last):
27152
4439s File 
"/usr/lib/python3/dist-packages/setuptools/_distutils/unixccompiler.py",
line 185, in _compile
27153
4439s self.spawn(compiler_so + cc_args + [src, '-o', obj] + extra_postargs)
27154
4439s File "/usr/lib/python3/dist-packages/setuptools/_distutils/ccompiler.py",
line 1041, in spawn
27155
4439s spawn(cmd, dry_run=self.dry_run, **kwargs)
27156
4439s File "/usr/lib/python3/dist-packages/setuptools/_distutils/spawn.py",
line 70, in spawn
27157
4439s raise DistutilsExecError(
27158
4439s distutils.errors.DistutilsExecError: command
'/usr/bin/powerpc64le-linux-gnu-gcc' failed with exit code 1
27159
4439s
27160
4439s During handling of the above exception, another exception occurred:
27161
4439s
27162
4439s Traceback (most recent call last):
27163
4439s File "tests/run/test_fstring.pyx", line 530, in
test_fstring.TestCase.test_many_expressions (test_fstring.cpp:27480)
27164
4439s cy_eval('[' + ', '.join(build_fstr(i) for i in range(250, 260))
+ ']', x=x, width=width),
27165
4439s File "tests/run/test_fstring.pyx", line 23, in
test_fstring.cy_eval (test_fstring.cpp:7575)
27166
4439s return cython_inline('return ' + s, force=True, **kwargs)
27167
4439s File "/usr/lib/python3/dist-packages/Cython/Build/Inline.py",
line 289, in cython_inline
27168
4439s build_extension.run()
27169
4439s File 
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build_ext.py",
line 345, in run
27170
4439s self.build_extensions()
27171
4439s File 
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build_ext.py",
line 467, in build_extensions
27172
4439s self._build_extensions_serial()
27173

Processed: Re: pyalsaaudio ftbfs with Python 3.12

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1055564 [src:pyalsaaudio] pyalsaaudio ftbfs with Python 3.12
Added tag(s) patch.

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

Processed: severity of 1040092 is serious

[Debian Bug Tracking System]

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

> severity 1040092 serious
Bug #1040092 [src:python-pyftpdlib] python-pyftpdlib: deprecation of Python 
libraries asyncore and asynchat
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1055564: pyalsaaudio ftbfs with Python 3.12

[Matthias Klose]

Control: tags -1 + patch

this is fixed in the new upstream version 0.10.0.

example packaging at
https://launchpad.net/ubuntu/+source/pyalsaaudio/0.10.0-0ubuntu1

looking at the autopkg tests, every single test fails due to a missing 
card.  It looks like these tests don't have any value.

Bug#1059835: cython: autopkgtest regression with Python 3.12 on 32-bit

[Graham Inggs]

Source: cython
Version: 3.0.7-2
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

cython's autopkgtests fail with Python 3.12 on 32-bit architectures
[1][2][3].  I've copied what I
hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/c/cython/testing/armel/
[2] https://ci.debian.net/packages/c/cython/testing/armhf/
[3] https://ci.debian.net/packages/c/cython/testing/i386/


8361s ==
8361s FAIL: test_raiseMemError (test_unicode.UnicodeTest.test_raiseMemError)
8361s --
8361s Traceback (most recent call last):
8361s File "tests/run/test_unicode.pyx", line 2355, in
test_unicode.UnicodeTest.test_raiseMemError (test_unicode.c:144223)
8361s self.assertRaises(MemoryError, alloc)
8361s AssertionError: MemoryError not raised by lambda
8361s
8361s ==
8361s FAIL: test_raiseMemError (test_unicode.UnicodeTest.test_raiseMemError)
8361s --
8361s Traceback (most recent call last):
8361s File "tests/run/test_unicode.pyx", line 2355, in
test_unicode.UnicodeTest.test_raiseMemError (test_unicode.cpp:144235)
8361s self.assertRaises(MemoryError, alloc)
8361s AssertionError: MemoryError not raised by lambda
8361s
8361s --
8361s Ran 7570 tests in 8252.568s
8361s
8361s FAILED (failures=2, skipped=16)

Bug#1057269: marked as done (modemmanager: FTBFS dh_missing: warning: lib/systemd/system/ModemManager.service exists in debian/tmp ...)

[Debian Bug Tracking System]

Your message dated Tue, 02 Jan 2024 09:37:47 +
with message-id 
and subject line Bug#1057269: fixed in modemmanager 1.22.0-2
has caused the Debian Bug report #1057269,
regarding modemmanager: FTBFS dh_missing: warning: 
lib/systemd/system/ModemManager.service exists in debian/tmp ...
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.)


-- 
1057269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: modemmanager
Version: 1.22.0-1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: dep17m2


Dear Maintainer,

modemmanager currently FTBFS in unstable, like this:

...
dh_auto_configure -- -Dgtk_doc=true \
-Ddbus_policy_dir=/usr/share/dbus-1/system.d \
-Dpolkit=permissive \
-Dsystemdsystemunitdir=/lib/systemd/system \
...
Installing /<>/obj-x86_64-linux-gnu/data/ModemManager.service to 
/<>/debian/tmp/lib/systemd/system
...
dh_missing: warning: lib/systemd/system/ModemManager.service exists in 
debian/tmp but is not installed to anywhere
dh_missing: error: missing files, aborting
...
make: *** [debian/rules:17: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


I see you're already preparing a new build hopefully fixing this in
experimental. Hope it works!

Thanks,
Chris
--- End Message ---
--- Begin Message ---
Source: modemmanager
Source-Version: 1.22.0-2
Done: Arnaud Ferraris 

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

Debian distribution maintenance software
pp.
Arnaud Ferraris  (supplier of updated modemmanager 
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, 02 Jan 2024 09:35:55 +0100
Source: modemmanager
Architecture: source
Version: 1.22.0-2
Distribution: unstable
Urgency: medium
Maintainer: DebianOnMobile Maintainers 

Changed-By: Arnaud Ferraris 
Closes: 1035481 1057269
Changes:
 modemmanager (1.22.0-2) unstable; urgency=medium
 .
   * modemmanager: acknowledge udev rules now being under /usr.
 (Closes: #1057269)
   * d/control: make libmm-glib-dev depend on libglib2.0-dev.
 This is required as `libmm-glib` is actually built on top of `glib`.
 (Closes: #1035481)
   * d/gbp.conf: use 'debian/latest' as debian branch.
 This way we stay consistent with the other team-maintained packages.
Checksums-Sha1:
 d0417be7e1aab45e9f4e3c0666dcec21b188cef9 3008 modemmanager_1.22.0-2.dsc
 0cbb7d34851b773c930c93520e7bf12f3ba57f29 33536 
modemmanager_1.22.0-2.debian.tar.xz
 8722efc517dbbaa7ffcb26f906ea04d231fb1829 10908 
modemmanager_1.22.0-2_source.buildinfo
Checksums-Sha256:
 4c71034f55f6afa5aab8fc65a83770c331e6147b23108523742f2a19a9d307a8 3008 
modemmanager_1.22.0-2.dsc
 b5da1671f977bda485e9b920d9657fadf4032d89f396a1a6fb7ef1f2ce547eeb 33536 
modemmanager_1.22.0-2.debian.tar.xz
 ab56a63b75d9e1fad55a1b33c552b6df6cc26ee3f1c49c4898b4c1502e5cfead 10908 
modemmanager_1.22.0-2_source.buildinfo
Files:
 f62ebd53efccb24e58c5da4f380afa24 3008 net optional modemmanager_1.22.0-2.dsc
 45d0243dc98e9a5d1345f4f3b73493d3 33536 net optional 
modemmanager_1.22.0-2.debian.tar.xz
 bd0af8ea519d36dec8b3064421b291fd 10908 net optional 
modemmanager_1.22.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEeW2zk9w/9AIituoi0+u1lmu5kZYFAmWT0LMACgkQ0+u1lmu5
kZblphAArZxG1pyeQZlLcEuTY54lTAL5WXp51rcXDanhibvga5GrxrEfCJCz04xH
KmUSJWlLJM+ATWx9nlCfqeI0IElhjwUPhvJhxrECiHn9qYr20YX3IRzd1DDISbxI
Krr1YVwUB39kenwyybrWjijkSHLt9puWp1exJyfKeqmhrfaxW5bgZGRU/M8hebP6
/T6u35Rcb0CA36nd1viAs+xzZO7+aypD3VJMXTqi0OUmgmukHYzXST2XN5mrQkNE
28AqYrKx0S+QEWW1hJnJGXjaP4/Bd0Jt5FuQbPFtJDNb4lPMDe6HrBJi9D74ux5Q
f3QRP3Hzm0YqfoktXOKRFNaogyJgh4bGZBljmc+DinDld/CUf47iuF4WPYeYmy9b
XuplnErukAquFOFHYimcvlYdC/Qr6NCORAKQ8tIYQAUQjKaGgu7HLTq0GEs2LTr5
UIy+T3M3VgLe0cHMefX5yNvcKez57anXr1Ue789GGURG1ZsMkBzsqxlMhNbN7iSn
vXI02UnrNBCTmnvLPLY0YAdl/0AIcgE/4RSFkZ9LMICf2hiyxfTs4cv2S1XlyMuK
E1Oy/uH7pnfLkZ7s56Po3QzcMKFk3gROzmMRyoqBRzBVdy2c8Gu/UsPe/eewj/mX
ppGjr3SLhBhCet2iWeh15zSHnLfbBuSQXmmEz1awIYzbyxa+GlA=
=wzBw