Control: clone -1 -2
Control: reassign -1 ntfs-3g
Control: reassign -2 fuse
Control: tags -2 + patch
Hi,
On Sun, Jan 07, 2024 at 10:52:52PM +0100, Chris Hofstaedtler wrote:
> Package: fuse,fuse3,ntfs-3g
> X-Debbugs-CC: Laszlo Boszormenyi (GCS) <g...@debian.org>, Helmut Grohne
> <helm...@debian.org>
>
> Hello Laszlo!
>
> fuse, fuse3, and ntfs-3g use dpkg-statoverride on aliased paths in
> /bin: /bin/fusermount, /bin/fusermount3.
I am further splitting this bug after having split off fuse3 earlier.
> 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?
My earlier patch for fuse3 has reached trixie. It duplicates the
dpkg-statoverride check (and is thus able to deal with both a
/bin/fusermount and /usr/bin/fusermount statoverride) and adds a NEWS
entry requesting the administrator to duplicate their statoverrides.
I am attaching a similar patch for fuse here and leave the original bug
for ntfs-3g only. The patch is independent of the library move #1060229
and both need to be applied to solve /usr-move matters for fuse.
Helmut
diff --minimal -Nru fuse-2.9.9/debian/changelog fuse-2.9.9/debian/changelog
--- fuse-2.9.9/debian/changelog 2024-02-29 23:24:20.000000000 +0100
+++ fuse-2.9.9/debian/changelog 2024-08-07 14:07:13.000000000 +0200
@@ -1,3 +1,10 @@
+fuse (2.9.9-8.2) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Handle both canonial and aliased statoverride. (DEP17 P5) (Closes: #-1)
+
+ -- Helmut Grohne <hel...@subdivi.de> Wed, 07 Aug 2024 14:07:13 +0200
+
fuse (2.9.9-8.1) unstable; urgency=medium
* Non-maintainer upload.
diff --minimal -Nru fuse-2.9.9/debian/fuse.NEWS fuse-2.9.9/debian/fuse.NEWS
--- fuse-2.9.9/debian/fuse.NEWS 1970-01-01 01:00:00.000000000 +0100
+++ fuse-2.9.9/debian/fuse.NEWS 2024-08-07 14:07:13.000000000 +0200
@@ -0,0 +1,9 @@
+fuse (2.9.9-8.2) unstable; urgency=medium
+
+ The fuse package honours a dpkg-statoverride of /bin/fusermount installed
+ by a system administrator (e.g. to remove the setuid binary installed by
+ default). The path to this file according to the package manager is
+ transitioned to /usr/bin/fusermount. If you installed a statoverride,
+ please move it to the new path and verify the permissions.
+
+ -- Helmut Grohne <hel...@subdivi.de> Wed, 07 Aug 2024 14:07:13 +0200
diff --minimal -Nru fuse-2.9.9/debian/fuse.postinst
fuse-2.9.9/debian/fuse.postinst
--- fuse-2.9.9/debian/fuse.postinst 2023-11-05 13:44:31.000000000 +0100
+++ fuse-2.9.9/debian/fuse.postinst 2024-08-07 14:07:12.000000000 +0200
@@ -18,7 +18,8 @@
then
chmod 0600 /dev/cuse > /dev/null 2>&1
fi
- if ! dpkg-statoverride --list /bin/fusermount > /dev/null 2>&1
+ if ! dpkg-statoverride --list /bin/fusermount > /dev/null 2>&1
&&
+ ! dpkg-statoverride --list /usr/bin/fusermount >
/dev/null 2>&1
then
chmod 4755 /bin/fusermount
fi
