Your message dated Sun, 07 Jul 2024 06:04:19 +0000
with message-id <[email protected]>
and subject line Bug#1073058: fixed in fuse3 3.14.0-6
has caused the Debian Bug report #1073058,
regarding fuse3: apply usrmerge and statoverride
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.)
--
1073058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073058
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: fuse3
Source-Version: 3.14.0-6
Done: Laszlo Boszormenyi (GCS) <[email protected]>
We believe that the bug you reported is fixed in the latest version of
fuse3, 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 fuse3 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: Sun, 07 Jul 2024 07:17:03 +0200
Source: fuse3
Architecture: source
Version: 3.14.0-6
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) <[email protected]>
Changed-By: Laszlo Boszormenyi (GCS) <[email protected]>
Closes: 1073058
Changes:
fuse3 (3.14.0-6) unstable; urgency=medium
.
[ Helmut Grohne ]
* Move aliased files to /usr (DEP17) (closes: #1073058).
Checksums-Sha1:
cdd13823dbffaea6c409fdff2f4b3090314daff4 2385 fuse3_3.14.0-6.dsc
fe347ddc8138e94c0ed59eabcb3ff8d2ec6412b2 18108 fuse3_3.14.0-6.debian.tar.xz
Checksums-Sha256:
c904fe136cc9cde52ed999a858565b64157c408fb3ba1dc4eb84d2bed6ac461e 2385
fuse3_3.14.0-6.dsc
efae49752cae09644a7ff87c907bb94d4854fbe1f7744558a9f55d06db3cff10 18108
fuse3_3.14.0-6.debian.tar.xz
Files:
320510d8b323fb6adeb9497f738e69f8 2385 utils optional fuse3_3.14.0-6.dsc
59210b2f4bc19ce410d77ab3dd4f13c7 18108 utils optional
fuse3_3.14.0-6.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmaKKnwACgkQ3OMQ54ZM
yL+v4RAAsVXhXkWWEzuhkVg01Vqqat3WfVe3/CbmM8hUdciHwHJ1WYW/5HCsSY1l
Md8F0d76waXh2doQzNiqhsnTcOBkzisEq2B65UHeqvj8QIH/T4yO6dymwgoMLi0h
QkDMT1Jd/o0mDfAijlzbsZ6xzqnjsPW4mhjVVO+WHAP+r1gSpwHumCaAZQMW4sUf
MRQQiWYBz8fk7nCtGRV6WfRTdrNrXqUhIs13/OlpmsLDUimpS0BqP9veLoiGJu7E
a+7AMCTjbUijSDqoHA1ATn8Kf0yHYDVZKG3s1PmfJHR6BF4Py7mcD9H9SjMWgXXo
8Mru2HHNaeJmQAnnhGU91s9TWyhdq7tFE2rtqfc3JxRmiRA/PZA5XcG2m4TkdL88
Gcp7iZ2/6AUh8yYCyaXsqkxb71xUFsl72cfsTwlWHTz5FfS0/kjl0krg8GHBjpfr
C3aWDINyplRk74+96TvKsPjJeEd6jiwyd6j6/Vomu7vs2qD2gEKdwmEWvQW68H/o
UeIyGy7Au3zlLFvZWSNhaL5JszEQ4+hUFM8gOxG2m9y2JozPgD44hBMPGjyAPs9L
QGoCwW2delWF4o1pp4L9+FPpe5JeY480JEPNLGP/nMdPvgnOpMyOADnILUcv/yQv
yO8le4pND+6TwoSeNc0+btYOCUaWxZ5PLdAPm3UBVyLg+mXu/aQ=
=T3Sw
-----END PGP SIGNATURE-----
pgpaMSpd56EvE.pgp
Description: PGP signature
--- End Message ---
