Your message dated Sat, 06 Dec 2025 12:04:28 +0000
with message-id <[email protected]>
and subject line Bug#1122039: fixed in mapdamage 2.2.3+dfsg-2
has caused the Debian Bug report #1122039,
regarding FTBFS with Python 3.14: cd: can't cd to mapdamage
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 [email protected]
immediately.)
--
1122039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1122039
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: mapdamage
Version: 2.2.3+dfsg-1
Severity: serious
Tags: ftbfs
User: [email protected]
Usertags: python3.14
debian/rules override_dh_auto_test
make[1]: Entering directory '/build/reproducible-path/mapdamage-2.2.3+dfsg'
set -e \
; for py3 in 3.14 3.13 \
; do cd mapdamage \
;
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/build/reproducible-
path/mapdamage-2.2.3+dfsg/.pybuild/cpython3_${py3}/scripts \
PYTHONPATH=/build/reproducible-
path/mapdamage-2.2.3+dfsg/.pybuild/cpython3_3.13/build \
python3 mp_test.py \
; done
[...]
/bin/sh: 3: cd: can't cd to mapdamage
make[1]: *** [debian/rules:15: override_dh_auto_test] Error 2
I think this doesn't really support building for several supported versions,
due to a `cd` in a loop.
https://buildd.debian.org/status/fetch.php?pkg=mapdamage&arch=amd64&ver=2.2.3%2Bdfsg-1%2Bb1&stamp=1764975143&raw=0
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.17.7+deb14+1-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: mapdamage
Source-Version: 2.2.3+dfsg-2
Done: Étienne Mollier <[email protected]>
We believe that the bug you reported is fixed in the latest version of
mapdamage, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Étienne Mollier <[email protected]> (supplier of updated mapdamage 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 06 Dec 2025 12:09:59 +0100
Source: mapdamage
Architecture: source
Version: 2.2.3+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
<[email protected]>
Changed-By: Étienne Mollier <[email protected]>
Closes: 1122039
Changes:
mapdamage (2.2.3+dfsg-2) unstable; urgency=medium
.
* d/rules: fix mishap with directory handling. (Closes: #1122039)
Checksums-Sha1:
31a5ad1a4380dac4e8e86b88ac7f30f3c2044ed2 2467 mapdamage_2.2.3+dfsg-2.dsc
6e1ff1d1ece78bce127b21c43de009bd500be164 7168
mapdamage_2.2.3+dfsg-2.debian.tar.xz
Checksums-Sha256:
39d692073db850d2b1b7b21b784aea362c5b303f1f8c1e323be97d72c008a326 2467
mapdamage_2.2.3+dfsg-2.dsc
1b254399b1b01f9bc4261e78ac91f65a8a55f2ac7de8095c8614fe88b22ef9bf 7168
mapdamage_2.2.3+dfsg-2.debian.tar.xz
Files:
2f2fb53382b80596cad7e93423d3e4eb 2467 science optional
mapdamage_2.2.3+dfsg-2.dsc
0dda9fab2018241be0f44ee55a5bfc19 7168 science optional
mapdamage_2.2.3+dfsg-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmk0GCQUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdqVCBAArnDzF8lz6wQTRBqT3ARMptKnD/SJ
aR0JY7vNWReCan544rjwXh6shr+j3ITdQX/XvpUGv1WFDrjESsywIndHwmG91qVb
kf7e9h5sgy0n17CMXX5CfVCfbnL/9jOTT5I5tOrv1q16iiLY4pDqfm/ALa36vT98
reLdmlzPnl0D+4zL+m7MgB5Pm/ULNVFJ2p+cgg3VL2U0cm7XgD7EQ90trcZjATfb
6OpEb0U+2PuP2cRcu58kjMfyFh5O+bOaJguroUzhsJhL8Nwo7scR7wBbchl23QXa
cXJzRXVaG+ac2jGO1UFa7jqTLlSUd3BdHEhxKeo79jbllK86Q/KYXz22aGT21YYN
JJjk7XMOW7GC0TGPo4Y7ffbeH4ydM49JFADlao3aKFgQfAsaruORiINI48Gp2v7F
LBxfdez3XftbSwVzwxkpt+vqieMXZl7CiNxu+gszFwcuL3rqLdoTMsFpzJvWjvq0
9jjmiuUxQpuy5dq9UB0eAp2KiOOPzkSu+uEpB8XN0ouHLH0wbZvT3ervsYoCWo9f
2zRaMNgN4aV6t5LqRZ61JbREqdZfOhu4ehn62k99ZseUgxMF02AsAz9HQGNaXJHF
mBQSc3Ro5YcPnE2q5cxC1wMplzt7ywA+EZtHiPNIpSx+oCoG2R0Ado9F6GnIYuMY
bqpUCmubEC+jbxs=
=RwYN
-----END PGP SIGNATURE-----
pgpmOKiWJBlPo.pgp
Description: PGP signature
--- End Message ---
