FS#25435 - [pacman] warning: couldn't create package cache, using /tmp instead

Attached to Project: Pacman
Opened by Sverd Johnsen (sjohnsen) - Sunday, 07 August 2011, 15:02 GMT
Last edited by Dan McGee (toofishes) - Monday, 22 August 2011, 16:37 GMT
Task Type Bug Report
Category Backend/Core
Status Closed
Assigned To Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version 3.5.3
Due in Version 4.0.0
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

When $cachedir is 0555, pacman (or whatever makes the check) assumes that it's not writable which is bogus since pacman runs as root during installs which implies CAP_DAC_OVERRIDE unless it's been dropped intentionally beforehand. It also doesn't honor TMPDIR and doesn't check if /tmp has enough space when proceeding.
This task depends upon

Closed by  Dan McGee (toofishes)
Monday, 22 August 2011, 16:37 GMT
Reason for closing:  Fixed
Additional comments about closing:  Commit e07547ee4ed4fd812
Comment by Sverd Johnsen (sjohnsen) - Sunday, 07 August 2011, 15:10 GMT
I forgot there is a bugtracker category specifically for pacman related stuff. Sorry, please move this if you have the chance :P
Comment by Dan McGee (toofishes) - Tuesday, 09 August 2011, 15:16 GMT
It isn't bogus; we're trying to respect your filesystem permissions. Can you give a legit reason as to why you'd mark a directory 555 over 755, especially something where you know writes are going to take place? There is no way we are changing this, as there are plenty of situations where CAP_DAC_OVERRIDE doesn't apply- basically any remote filesystem, any readonly mount, etc.

Patches welcome for TMPDIR, and checking space is a whole bundle of complexity- patches would be accepted there but it would have to be done right.

Loading...