On Fri, Dec 12, 2008 at 2:20 PM, Hubert Grzeskowiak <arch-general-ml@nemesis13.de> wrote:
Hubert Grzeskowiak schrieb:
Aaron Griffin schrieb:
Aaron Griffin schrieb:
hi there, can it be, that the some dirs written to /var/lib/pacman/local/* are not chmod'ed properly? sometimes i get errors because as user i don't have the permissions to do anything with it (it's set to drwx------). this only occurs on some packages (eg. the new nmap package). other dirs and files inside all (also the corrupted) directories seem okay (files: -rw-r--r--; dirs: drwxr-xr-x)
i played around with umask and sudo (always used on de-/installations) with no result -everything was okay- so i conclude it's a per-package problem. It's not, those files are not installed directly out of the package -
On Thu, Dec 11, 2008 at 12:47 PM, Hubert Grzeskowiak <arch-general-ml@nemesis13.de> wrote: pacman writes them itself.
What is root's umask?
root's and user's umask is the same: 0077 Can you try setting it to 0022 (the default, and what I have on my system) and see if the problem persists? If it does not, we then know
On Thu, Dec 11, 2008 at 2:46 PM, Hubert Grzeskowiak <arch-general-ml@nemesis13.de> wrote: the cause... Still, pacman's explicit chmod of this dir should fix this... gah.
Dan, does pacman also explicitly set its own umask anywhere?
ok. gonna change it before updating the next time
upgraded as root with umask 0022 and it's all okay.
That's so weird... so pacman's umask setting just doesn't work?