Created attachment 315567 [details, diff] The patch to drop the workaround for test I'm not sure when it last worked, but you can test this bug with =sys-auth/polkit-0.106-r1 by removing the `chown -R` from it's pkg_postinst() that is working around the issue. src_install() { default fowners -R polkitd:root /{etc,usr/share}/polkit-1/rules.d } And after emerge, the owners are back to "root:root"
With chown -R in pkg_postinst(): drwx------ 2 polkitd root Jun 17 11:01 /etc/polkit-1/rules.d -rw-r--r-- 1 polkitd root Jun 17 10:46 /etc/polkit-1/rules.d/50-default.rules drwx------ 2 polkitd root Jun 8 02:32 /usr/share/polkit-1/rules.d Without chown -R (and just fowners in src_install, only the file has correct perms: -rw-r--r-- 1 polkitd root Jun 17 11:44 /etc/polkit-1/rules.d/50-default.rules drwx------ 2 root root Jun 17 11:44 /etc/polkit-1/rules.d drwx------ 2 root root Jun 17 11:44 /usr/share/polkit-1/rules.d
To clarify: /etc/polkit-1/rules.d and /usr/share/polkit-1/rules.d exist as root:root and this is when trying to change them to polkitd:root Only files inside the directories change perm, not the directories itself
< Tommy[D]> ssuominen: fowners does work as intended, it does change the ownership inside $D, but afterwards, those directories get copied to $ROOT, in which case you have a cp, which preserves the ownership of the original directory no way to set permissions from ebuild without using pkg_ and ${ROOT} then, that's far from ideal... fowners/fperms in specific should always be respected, since the maintainer is intentionally/specifically setting them, maybe i'll file another PMS bug for this later
*** This bug has been marked as a duplicate of bug 141619 ***
