Your message dated Fri, 05 Sep 2025 22:07:47 +0000
with message-id <[email protected]>
and subject line Bug#1092846: fixed in ntfs2btrfs 20250616-3
has caused the Debian Bug report #1092846,
regarding ntfs2btrfs: FTBFS with fmtlib 11.1
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.)
--
1092846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1092846
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ntfs2btrfs
Version: 20240115-2
Severity: important
Tags: ftbfs
Control: affects -1 src:fmtlib
X-Debbugs-Cc: [email protected], [email protected]
Dear maintainers,
We are planning the transition towards fmtlib 11.1 (in experimental).
You package ntfs2btrfs 20240115-2 FTBFS with fmtlib 11.1.1+ds1-1.
There are no significant API changes from (in testing) fmtlib 10 to 11.
After a quick look at ratt logs (thanks @aron for running it), I can
spot problems including (but not limited to):
- removal of APIs: nmodl, opm-common
- use of private APIs (fmt::detail): dolphin-emu
- '-fpermissive' compiler errors: doxygen, nheko
- unformattable types: genomicsdb, gerbera
- missing #include for std header: ntfs2btrfs, transmission
...and many of them have already been fixed by upstream.
There might be false positives due to collision with other on-going
transitions (e.g. python3.13). Please close this bug if so.
--
Thanks,
Shengqi Chen
--- End Message ---
--- Begin Message ---
Source: ntfs2btrfs
Source-Version: 20250616-3
Done: Alex Myczko <[email protected]>
We believe that the bug you reported is fixed in the latest version of
ntfs2btrfs, 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.
Alex Myczko <[email protected]> (supplier of updated ntfs2btrfs 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: Fri, 05 Sep 2025 16:48:39 -0500
Source: ntfs2btrfs
Architecture: source
Version: 20250616-3
Distribution: experimental
Urgency: medium
Maintainer: Alex Myczko <[email protected]>
Changed-By: Alex Myczko <[email protected]>
Closes: 1092846
Changes:
ntfs2btrfs (20250616-3) experimental; urgency=medium
.
* d/control: build against libfmt-dev 11.1. (Closes: #1092846)
Checksums-Sha1:
4b8d53f52d08a45cd8d3ef71fd5333456e8af86d 1969 ntfs2btrfs_20250616-3.dsc
af23e61c5eab1f7756ed9b927f7aa494383f1634 2752
ntfs2btrfs_20250616-3.debian.tar.xz
8c39fa1d0a48c17883a7ed1660caa0dce7bd2914 6960
ntfs2btrfs_20250616-3_source.buildinfo
Checksums-Sha256:
8ef20eca30bd08761e52ec86e322242928a3399ede6c9f162f83dcb7c0e05590 1969
ntfs2btrfs_20250616-3.dsc
b7d2edabf492b33f049b5b4f38fe10ffef169ee4f4cfbe44c88759738d5076ff 2752
ntfs2btrfs_20250616-3.debian.tar.xz
ec0d1525e3dd4f370783ae02f19f710e67973518f5cfe160350e26bf32925989 6960
ntfs2btrfs_20250616-3_source.buildinfo
Files:
ac02d243cbf1a92fdca3692c8232371b 1969 utils optional ntfs2btrfs_20250616-3.dsc
adb2b230cd1d7b0b662ec0624c0ed7fb 2752 utils optional
ntfs2btrfs_20250616-3.debian.tar.xz
752741f46fd8939de181bc8472752aed 6960 utils optional
ntfs2btrfs_20250616-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJDBAEBCgAtFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmi7WxkPHHRhckBkZWJp
YW4ub3JnAAoJEBFoUrzfdRXAjfEQAI9ZCTXY1VGkCjeocBueK/bAZh6oIgw7sZ6w
rdEf+60fMrgyqjcSQ0wPPbyOK6QOZ6PeXBrkmbpxuTBvOC1OArT/6sCS3Tj9E4ZH
mBSURkHVP06x/wzebfcAhkNzT9uPFuVXM+aH23Lx2t9nQHcDMbVNyTBQDb3AKF4+
fuXekXnar79oBGUqGh/G+9MaxhUeLLkLMWo3hoAQacGxEqmw2CgVokDWhUDsrUw3
+8GxOOiJFYr1SQRWkh7bkRbokpGFRBwhjcRsuneE1pGaWl6ejfmLSagRnd0xI3ir
gqb4/k4lrZxKnsw5s9vtNDTmQGBd4R9qh0eGlEC8ddrNMEaurdDCxk13CZK/Ofst
z3EI3J5tAbhiaG8IA1hgc3W7X0+XNkzpn0XLKIr9i2BWoT+mVQtoP0gzI9R8A8Xn
u9ClL1e83s+n4L8JL7Dz0S4ID39LWO5QymkRXCiTd3f31owIL51uHsxRxGn9mTaT
M3lhqbrrM3OAR/NMHfSq8qSTKfOxNB/Zdc5IufwxE33+hYN//FR0VIfdwtad4vmH
HlhcTTy1R/ijlx42q19/R4qKJg/sBUP8gsF/vnOl07hiXl/9JH/f5q6XdDXpT9Sm
3DAVH+bTuHqb0NJAcodJy1wZbbGtB6h0ZLnj/43o/6zn7jqUWSm5OyFY8xOS2wwg
xavnXTwd
=xqP3
-----END PGP SIGNATURE-----
pgpQxBdC39r73.pgp
Description: PGP signature
--- End Message ---
