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#67390 - usr/lib/systemd/system/org.cups.cups-lpd.socket is 444 instead of 644
Attached to Project:
Arch Linux
Opened by Paul Hunnisett (phunni) - Saturday, 25 July 2020, 13:24 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 25 July 2020, 14:58 GMT
Opened by Paul Hunnisett (phunni) - Saturday, 25 July 2020, 13:24 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 25 July 2020, 14:58 GMT
|
DetailsDescription: In the latest cups package the permissions for /usr/lib/systemd/system/org.cups.cups-lpd.socket seems to now be 444 instead of 644 - is there a reason for that? If not can it be changed back?
Additional info: * package version(s) 2.3.3-2 Steps to reproduce: Check permissions on /usr/lib/systemd/system/org.cups.cups-lpd.socket |
This task depends upon
Comment by Doug Newgard (Scimmia) -
Saturday, 25 July 2020, 13:59 GMT
Because that's how upstream installs it. Is it a problem?
Comment by Paul Hunnisett (phunni) -
Saturday, 25 July 2020, 14:46 GMT
It breaks the install scripts I use to create my system so that it's immutable and stateless, which I suppose is my problem, but I thought that if there was no real technical reason why not it could be 644...?