Your message dated Mon, 19 Aug 2024 11:19:31 +0000
with message-id <[email protected]>
and subject line Bug#1060229: fixed in ntfs-3g 1:2022.10.3-4
has caused the Debian Bug report #1060229,
regarding fuse,fuse3,ntfs-3g: migrate dpkg-statoverride for UsrMerge?
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.)
--
1060229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060229
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fuse,fuse3,ntfs-3g
X-Debbugs-CC: Laszlo Boszormenyi (GCS) <[email protected]>, Helmut Grohne
<[email protected]>
Hello Laszlo!
fuse, fuse3, and ntfs-3g use dpkg-statoverride on aliased paths in
/bin: /bin/fusermount, /bin/fusermount3.
They do so in their postinst scripts, only checking if a
statoverride exists. If not, they run chmod on some programs.
The postinst does not add a statoverride.
As you know, these paths need to become canonicalized to /usr/{...}.
When this happens, the old dpkg-statoverride entries stop working.
Now my question: do you think it is worth migrating any such
dpkg-statoverride automatically?
If not, how should users/admins who previously created an override
be informed about this problem? Some suggestions might be:
- NEWS.Debian entry
- trixie Release Notes
What do you think?
I've started working on UsrMerge patches for fuse and fuse3. Those
patches would need to take into account the question above, and also
the file loss problem between fuse and fuse3.
Additional context: the three packages are the only packages in this
"problem space". One other package uses dpkg-statoverride on an
aliased path, but it also creates the override - what we decide here
might influence that package, but probably not.
I hope to hearing from you about this soon,
Chris
--- End Message ---
--- Begin Message ---
Source: ntfs-3g
Source-Version: 1:2022.10.3-4
Done: Laszlo Boszormenyi (GCS) <[email protected]>
We believe that the bug you reported is fixed in the latest version of
ntfs-3g, 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.
Laszlo Boszormenyi (GCS) <[email protected]> (supplier of updated ntfs-3g 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, 19 Aug 2024 12:50:21 +0200
Source: ntfs-3g
Architecture: source
Version: 1:2022.10.3-4
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) <[email protected]>
Changed-By: Laszlo Boszormenyi (GCS) <[email protected]>
Closes: 1060229
Changes:
ntfs-3g (1:2022.10.3-4) unstable; urgency=medium
.
[ Chris Hofstaedtler <[email protected]> ]
* Drop ntfs-3g.postinst, which previously checked a statoverride for another
package. In the best case it was prone to not working because of timing
conditions, and in the worst case it did nothing.
Instead, install ntfs-3g mode 4755 in data.tar, set Rules-Requires-Root:
binary-targets (closes: #1060229).
* Drop effectively empty ntfs-3g.postrm.
Checksums-Sha1:
c2b8d1d426676e8312a5c265eb5723416fbbebaf 2127 ntfs-3g_2022.10.3-4.dsc
2759e437b7616229a1dd13f3af6116175ca186c0 23716
ntfs-3g_2022.10.3-4.debian.tar.xz
Checksums-Sha256:
29f1dc19e9de2528620330ddc104282820c3f3ed62029da85230b2a5dd46bb65 2127
ntfs-3g_2022.10.3-4.dsc
7d45aaaee88f9753a5889c2462596bde4c39d2a0d35e228e3f71f4fc7200c9f0 23716
ntfs-3g_2022.10.3-4.debian.tar.xz
Files:
8020f9ca0bd4b9fba1feeae659cc93d8 2127 otherosfs optional
ntfs-3g_2022.10.3-4.dsc
3855716d203d6eb9cce96c27f115f0d9 23716 otherosfs optional
ntfs-3g_2022.10.3-4.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmbDJj4ACgkQ3OMQ54ZM
yL9w6A/6A5dMLE5eUimmbt1bH0KRHeJbUQg2h1cFxhFFlbngH29qQpkAmxseELUr
WD5wzw47O1QhTjSNCiu3I0YqsC6VeTSzW6ykdYR+c1lN4XPsUifePyEbNcJ/6kZZ
eWae7ldgt+v9HQpf1cD2LoUAZxEuGmvN+2RoYBCv5YY6dt42nZ43lVGf00oGuXRj
taR+saX5oFPJ5sWuor9jm+xYYWS+GTMMIt1r0im0lVKgBX3kTtEnze48ayUBORDM
knizhmILOnih4iioycB8DjXDATxQn84SMiPATaq9TrHEAcJyDvjGmhrBtffb4ahr
/vHcIEFMoOwsuqE2kkSuCIyd8wULbx1gLhITQ33ku+kTfzPJ1KQWRLjED/s1uF8e
RuxUfPWNbQGda5LlWav+Oa66FTGLnQssrnBnaSeQfMqgikRB7jdksl9TdlJgvSJ/
qEaBVCMhzgKcFgRndBNbo3qKjAMKRLlbA+QxXOYSBVz9pfPNAImFG6qhTZ0FQIMR
MlcE+pFwW03TTVMA5PxH3szXTRAQItgfCtfch609SIU9/9tJzxXfa/lOX/Fourrh
oh+FGWtZ99gFbJfZ7FBdKxbyzFR+bITrcYZKlUMlxU9gtWuHUyu5CISDtenlHD84
015ZTvXbiia7R5y2QLW+wFvWZj8cVePHb6vuEtkqMsVEiazCiGw=
=CV0l
-----END PGP SIGNATURE-----
pgp5vXMLN5sPg.pgp
Description: PGP signature
--- End Message ---
