Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#18963 - [udisks] install script should kill old udisks daemon and reload udev rules

Attached to Project: Arch Linux
Opened by Marti (intgr) - Monday, 05 April 2010, 09:02 GMT
Last edited by Ionut Biru (wonder) - Tuesday, 06 April 2010, 08:15 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ionut Biru (wonder)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
The installation/upgrade script of udisks should kill the existing udisks daemon, otherwise the upgrade won't take effect until the next reboot. UDisks will start up by itself again and the user won't notice anything.

You also have to re-trigger all block devices in udev, to process any changed udev rules.

Here's the install script used in my AUR udisks entry... I also killed devkit-disks-daemon in case the user is upgrading from devkit-disks to udisks. I'm not entirely sure whether the D-Bus reload is necessary, but dbus didn't seem to reload /etc/dbus-1/system.d without it.

post_upgrade() {
if [ -f /var/run/dbus.pid ]; then
kill `pidof /usr/lib/devicekit-disks/devkit-disks-daemon` 2>/dev/null || true
kill `pidof /usr/lib/udisks/udisks-daemon` 2>/dev/null || true

/etc/rc.d/dbus reload

# we ship udev rules, so trigger an update
udevadm trigger --subsystem-match=block --action=change
fi
}

post_install() {
post_upgrade
}
This task depends upon

Closed by  Ionut Biru (wonder)
Tuesday, 06 April 2010, 08:15 GMT
Reason for closing:  Won't implement
Comment by Ionut Biru (wonder) - Tuesday, 06 April 2010, 08:07 GMT
having that would mean that we have to make the same thing on a lot of packages and relogin is the way to go.
always was like that and we are not holding users on hand when they do updates.
Comment by Marti (intgr) - Tuesday, 06 April 2010, 08:14 GMT
Ok, fair enough.

Loading...