FS#51931 - [lighttpd] Permission mismatch between .tmpfiles and PKGBUILD

Attached to Project: Arch Linux
Opened by Tinu Weber (ayekat) - Wednesday, 23 November 2016, 07:41 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:15 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Pierre Schmitz (Pierre)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No


The PKGBUILD (and thus the package) installs /var/cache/lighttpd with access permissions 0700, but the installed lighttpd.tmpfiles sets the permissions for that directory to 0755. Consequently, at each subsequent upgrade, pacman detects a permission mismatch between the package and the filesystem version of that directory, and emits a warning.

Is there a reason why these two differ (and consequently cause a warning at each upgrade)?

Latest version checked: lighttpd-1.4.43-1
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:15 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/lighttpd/issues/1
Comment by Doug Newgard (Scimmia) - Thursday, 24 November 2016, 17:11 GMT
Since this dir is part of the package, the easiest thing would be to just remove it from the tmpfiles entry.
Comment by Tinu Weber (ayekat) - Tuesday, 16 May 2017, 08:34 GMT
Here is a patch that would apply the change suggested by Doug.

EDIT: On a second thought—this would probably break the automatic cleaning after 10 days. I've added another patch that would just fix the permissions in the tmpfiles line rather than remove it entirely.
Comment by Daniel Müllner (muellner) - Sunday, 19 February 2023, 08:42 GMT
The issue is still present in February 2023 in lighthttpd-1.4.69-1. The second patch by Tinu Weber (cachedir2.patch) seems reasonable to me.
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.