[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#958489: marked as done (buster-pu: package fuse/2.9.9-1+deb10u1)

Your message dated Sat, 09 May 2020 11:53:52 +0100
with message-id <fd7fa4d56896c35aab49a5a51cb69727dc60e87a.camel@adam-barratt.org.uk>
and subject line Closing requests included in 10.4 point release
has caused the Debian Bug report #958489,
regarding buster-pu: package fuse/2.9.9-1+deb10u1
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 owner@bugs.debian.org
immediately.)


-- 
958489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958489
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian.org@packages.debian.org
Usertags: pu

Hi SRMs,

There are two RC bugs fixed in fuse for Bullseye but not yet for Buster.
First one[1] and its variant[2] are caused by a leftover in postinst -
udev has rules now to handle such things in its 50-udev-default.rules
and 99-systemd.rules files.
Then it shouldn't explicitly remove fuse.conf [3] as it should be done
by dpkg and fuse3 might still need it.
Proposed update is attached.

Thanks for consideration,
Laszlo/GCS
[1] https://bugs.debian.org/934457
[2] https://bugs.debian.org/935496
[3] https://bugs.debian.org/953222

diff -Nru fuse-2.9.9/debian/changelog fuse-2.9.9/debian/changelog
--- fuse-2.9.9/debian/changelog	2019-01-07 20:32:01.000000000 +0000
+++ fuse-2.9.9/debian/changelog	2020-04-22 19:38:47.000000000 +0000
@@ -1,3 +1,10 @@
+fuse (2.9.9-1+deb10u1) buster; urgency=medium
+
+  * Drop outdated udevadm commands from postinst (closes: #934457, #935496).
+  * Don't explicitly remove fuse.conf on purge (closes: #953222).
+
+ -- Laszlo Boszormenyi (GCS) <gcs@debian.org>  Wed, 22 Apr 2020 19:38:47 +0000
+
 fuse (2.9.9-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru fuse-2.9.9/debian/fuse.postinst fuse-2.9.9/debian/fuse.postinst
--- fuse-2.9.9/debian/fuse.postinst	2016-06-23 16:23:28.000000000 +0000
+++ fuse-2.9.9/debian/fuse.postinst	2020-04-22 19:38:47.000000000 +0000
@@ -25,17 +25,6 @@
 
 		modprobe fuse > /dev/null 2>&1 || true
 
-		if [ -x /sbin/lsmod ] && lsmod | grep -qs fuse
-		then
-			if udevadm control --reload-rules > /dev/null 2>&1
-			then
-				if [ -e /dev/fuse ]
-				then
-					udevadm test --action -p  $(udevadm info -q path -n /dev/fuse) > /dev/null 2>&1
-				fi
-			fi
-		fi
-
 		if [ -x /usr/sbin/update-initramfs ]
 		then
 			update-initramfs -u
diff -Nru fuse-2.9.9/debian/fuse.postrm fuse-2.9.9/debian/fuse.postrm
--- fuse-2.9.9/debian/fuse.postrm	2014-06-20 06:23:50.000000000 +0000
+++ fuse-2.9.9/debian/fuse.postrm	2020-04-22 19:38:47.000000000 +0000
@@ -11,7 +11,6 @@
 		;;
 
 	purge)
-		rm -f /etc/fuse.conf
 		;;
 
 	upgrade|failed-upgrade|abort-install|abort-upgrade|disappear)

--- End Message ---
--- Begin Message --- 
Package: release.debian.org
Version: 10.4

Hi,

Each of the uploads referred to by these bugs was included in today's
stable point release.

Regards,

Adam

--- End Message ---
Reply to: