Your message dated Mon, 16 Mar 2026 07:04:25 +0000
with message-id <[email protected]>
and subject line Bug#1122076: fixed in libunwind 1.8.1-0.3
has caused the Debian Bug report #1122076,
regarding python-memray: FTBFS with Python 3.14: Segmentation fault
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.)


-- 
1122076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1122076
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: python-memray
Version: 1.17.0+dfsg-1
Severity: serious
Tags: ftbfs
User: [email protected]
Usertags: python3.14

The build segfaults during tests, but only on amd64 and i386:

Current thread 0xf7b49700 [python3.14] (most recent call first):
  File "/build/reproducible-path/python-
memray-1.17.0+dfsg/.pybuild/cpython3_3.14_memray/build/tests/unit/test_reader.py",
line 30 in test_rejects_different_header_magic

https://buildd.debian.org/status/fetch.php?pkg=python-
memray&arch=i386&ver=1.17.0%2Bdfsg-1%2Bb1&stamp=1765038158&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: libunwind
Source-Version: 1.8.1-0.3
Done: Helmut Grohne <[email protected]>

We believe that the bug you reported is fixed in the latest version of
libunwind, 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.
Helmut Grohne <[email protected]> (supplier of updated libunwind 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: Mon, 16 Mar 2026 07:03:10 +0100
Source: libunwind
Architecture: source
Version: 1.8.1-0.3
Distribution: unstable
Urgency: medium
Maintainer: Adrian Bunk <[email protected]>
Changed-By: Helmut Grohne <[email protected]>
Closes: 1122076 1130107
Changes:
 libunwind (1.8.1-0.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Disable C++ exception support everywhere.
     (Closes: #1122076, #1130107) (Addresses: #1107618)
Checksums-Sha1:
 0f23a6c213ead5f74f3f1e407b6d84fac6f50172 2980 libunwind_1.8.1-0.3.dsc
 a4b750908f96737e0f3e3c1583faab53a605afac 27820 
libunwind_1.8.1-0.3.debian.tar.xz
Checksums-Sha256:
 5bc766b2191d185726525f9f48104388864f93bc39c22197fd1ba3dae5935d69 2980 
libunwind_1.8.1-0.3.dsc
 d8bc68150e69ae6a10ff8e09bfac178e23b3aa816c9b72c41f507f50683cce35 27820 
libunwind_1.8.1-0.3.debian.tar.xz
Files:
 aec8347247e59db3b6e633417f28704e 2980 libs optional libunwind_1.8.1-0.3.dsc
 7d5ddbcbec17f39e035f9c3a2f2c87ba 27820 libs optional 
libunwind_1.8.1-0.3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEETMLS2QqNFlTb+HOqLRqqzyREREIFAmm3ofIACgkQLRqqzyRE
REK9mw//cDWohkyvQlBAUvP1VloeTYhA/TxP0BnRaYGRQTmP58GAT6srszfnSqsi
X2kWsntzSqhEmtZ8zDz1FmqpGec4EeQsDz45Sa37ASJvM8Kgv2u11qQsZFMGJIUQ
a6MJKoGSWRAbzrrRzPLtDo81/ATTPZVPo7GMUGeOHxjd7MadPc/gb/6iZnRF9aRS
MDFvp/0m3aY4LxSC00sSa4eJgLFyaunHZXb3E8JILTMN2Ib+FyAXOb+NNKgblrlj
eDU2bKIL1a+cWE6B3Gw3yPBkVjPRjcck2stanu0z5YGdypWicvjkBCn4JqaEOlXB
Gzref/2IY50VkCK0Ad9gasytuEVErKvhxxZj7uQ3G7zpKAyarmAnCo4jxmfJMRQq
BBqWYDaKuFFEY+pZLiZqcr2w0XqD4a8hgCVKa3uCKfm7+LxJ043MtMEEmDv4tyyF
e2v5Js8V7U5WeirQHplZ++h1PAPRNAtqb7Z4WkWH5jcWbcFtJVmIG4hNMlh6tHPn
bZt4j37ETmQgonjRvumoEVZ6A6ukTwNX0TsjS/m6ltgrRbtF6Derq7jLqHq3txFL
DdpGMW4Hw+tvw8kMxwEMaf48TuCrWbdj7jvdUaeSRQHYBwB3FOnYumYUVaqtmfBb
GIdphCtuniC+80zFMo+KWssj/jkIF9hNmiQoh+I0/9gN7mKdV3E=
=HMNB
-----END PGP SIGNATURE-----

Attachment: pgp3alYPb0LKu.pgp
Description: PGP signature


--- End Message ---

Reply via email to