Please allow base-files 5.10 in testing
I think this bug should be fixed in squeeze because it has a simple fix
and also because otherwise users of squeeze when it becomes stable
will suffer from it at every base-files upgrade (i.e. at every point
release).
OTOH, if this fix is not allowed in squeeze please say so and I will
undo it for the final release, i.e. the one saying 6.0 in /etc/issue
et al, which will be the next one after this.
The complete diff is below.
Thanks.
diff -ru base-files-5.9//debian/changelog base-files-5.10//debian/changelog
--- base-files-5.9//debian/changelog 2010-08-06 19:42:25.000000000 +0200
+++ base-files-5.10//debian/changelog 2010-11-13 13:11:04.000000000 +0100
@@ -1,3 +1,12 @@
+base-files (5.10) unstable; urgency=medium
+
+ * Changed postinst to not reset /var/run/utmp permissions on every upgrade.
+ It is definitely not base-files business to change the permissions of
+ an already existing /var/run/utmp, as the system admin might have
+ changed them on purpose after the file was created. Closes: #601746.
+
+ -- Santiago Vila <sanvila@debian.org> Sat, 13 Nov 2010 13:01:12 +0100
+
base-files (5.9) unstable; urgency=medium
* Changed /etc/profile so that it defines PATH again. Closes: #571086.
diff -ru base-files-5.9//debian/postinst.in base-files-5.10//debian/postinst.in
--- base-files-5.9//debian/postinst.in 2010-04-01 17:55:37.000000000 +0200
+++ base-files-5.10//debian/postinst.in 2010-11-13 13:08:07.000000000 +0100
@@ -69,14 +69,13 @@
chown root:utmp /var/log/wtmp /var/log/btmp /var/log/lastlog
chmod 664 /var/log/wtmp /var/log/lastlog
chmod 660 /var/log/btmp
+ if [ ! -f /var/run/utmp ]; then
+ echo -n>/var/run/utmp
+ fi
+ chown root:utmp /var/run/utmp
+ chmod 664 /var/run/utmp
fi
-if [ ! -f /var/run/utmp ]; then
- echo -n>/var/run/utmp
-fi
-chown root:utmp /var/run/utmp
-chmod 664 /var/run/utmp
-
if [ ! -d /var/lib/dpkg ]; then
mkdir -m 755 -p /var/lib/dpkg
chown root:root /var/lib/dpkg
Reply to: