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!
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!
FS#20051 - [udisks] updates rewrite its configuration file.
Attached to Project:
Arch Linux
Opened by Yichao Zhou (zhou13) - Friday, 02 July 2010, 06:23 GMT
Last edited by Ionut Biru (wonder) - Friday, 02 July 2010, 09:06 GMT
Opened by Yichao Zhou (zhou13) - Friday, 02 July 2010, 06:23 GMT
Last edited by Ionut Biru (wonder) - Friday, 02 July 2010, 09:06 GMT
|
DetailsAfter "# pacman -Syu", /usr/share/polkit-1/actions/org.freedesktop.udisks.policy has been modified again.
I think moving the new configuration file to "org.freedesktop.udisks.policy.pacnew" is a better choice. Otherwise I need to modify the file after every updates. |
This task depends upon
I think this is a configuration file.
If its author make it, I think he hope its user to modify it.
Otherwise I think define it as a const variable is a better choice.
I don't think I'm wrong.
For example, If I want a normal user to use GVFS or want to mount something,
I must modify file this file. Or maybe you have a better choice?