Arch Linux

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!
Tasklist

FS#9370 - Pacman 3.1.1-1: directory permissions differ for new package

Attached to Project: Arch Linux
Opened by name withheld (Gullible Jones) - Monday, 28 January 2008, 01:38 GMT
Last edited by Dan McGee (toofishes) - Sunday, 02 March 2008, 00:21 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dan McGee (toofishes)
Architecture All
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

On upgrading to the latest version of pacman, I was presented with this message:

warning: directory permissions differ on var/cache/
filesystem: 777 package: 755
warning: directory permissions differ on var/cache/pacman/
filesystem: 777 package: 755

Since no bugfix involving permissions was mentioned in CVS, and permissions issues can produce major security holes, I'm going to assume this is a problem.

Additional info:
* pacman 3.1.1-1


Steps to reproduce:

Upgrade from pacman 3.1.0 to 3.1.1-1.
This task depends upon

Closed by  Dan McGee (toofishes)
Sunday, 02 March 2008, 00:21 GMT
Reason for closing:  Works for me
Additional comments about closing:  Please open a new bug if you can answer my requests in the last comment.
Comment by Dan McGee (toofishes) - Monday, 28 January 2008, 02:13 GMT
Um...the problem is on your system, dude, not with the pacman package. It looks like you gave write access to /var/cache/ and /var/cache/pacman/ to all users at some point.
Comment by name withheld (Gullible Jones) - Monday, 28 January 2008, 02:52 GMT
If I did, I most certainly did not do so purposefully or knowingly. Could it have been an issue with the the Archboot installer?
Comment by Dan McGee (toofishes) - Monday, 28 January 2008, 03:00 GMT
Perhaps, I am not that familiar with the installer so I do not know. Is this a recently installed system? I don't know of any directories we have on Arch that are created with permissions other than 755 besides /tmp.
Comment by Aaron Griffin (phrakture) - Thursday, 31 January 2008, 18:00 GMT
Hmmm /var/cache/{,pacman} may have been created BY pacman... I wonder if the umask wasn't set right. What happens if you delete /var/cache/pacman and then do a -S operation?
Comment by Dan McGee (toofishes) - Saturday, 09 February 2008, 15:40 GMT
Without feedback I can't do anything here.
Comment by Dan McGee (toofishes) - Wednesday, 27 February 2008, 04:26 GMT
Ping? No response and I'm closing.
Comment by name withheld (Gullible Jones) - Wednesday, 27 February 2008, 05:03 GMT
Yeah, this was a recently installed system. Sorry about taking forever to respond.

I changed the permissions on /var/cache to what they should have been... But at any rate, deleting /var/cache/pacman and installing packages failed to produce the message again. I think this is a problem with the Archboot installer.
Comment by Dan McGee (toofishes) - Wednesday, 27 February 2008, 06:08 GMT
No problem.

I just recently used the Arch installer on my Eee and didn't notice this issue, and all permissions seem to be OK right now. If you don't mind, I'd like to close this- something went wrong somewhere, but we don't have enough information here to track it down. If you do have info and can provide exact directions to reproduce (or fix it), then we can start another ticket for that.

Loading...