On Donnerstag, 11. Dezember 2008 21:42 Hubert Grzeskowiak wrote:

...

http://bugs.archlinux.org/task/12263

so in fact it's unsure what causes this... great. gonna make an alias for chmodding the dirs after each DB change as a temporary workaround and look forward for a patch.

Opening a root shell with "su -" or "sudo -i" is not an option for you? See you, Attila

On Donnerstag, 11. Dezember 2008 22:55 Hubert Grzeskowiak wrote:

i don't use su - call me paranoid, but i think it's too dangerous and in this case even the smallest danger is unnecessary

No problem to be paranoid because it could helps. I have the same problem with sudo.-)

i'm not sure what sudo -i makes in detail, but would it solve this problem?

"sudo -i" simulate initial login. See better the man page of sudo because the english there is very much better than mine. Personally i prefer to use this both solutions for a "real root login" because root and my user have a different umask. See you, Attila

Aaron Griffin schrieb:

On Thu, Dec 11, 2008 at 12:47 PM, Hubert Grzeskowiak wrote:

...

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 - pacman writes them itself.

What is root's umask?

root's and user's umask is the same: 0077

Aaron Griffin schrieb:

On Thu, Dec 11, 2008 at 2:46 PM, Hubert Grzeskowiak wrote:

...

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

On Fri, Dec 12, 2008 at 2:20 PM, Hubert Grzeskowiak 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 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 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?

On Fri, Dec 12, 2008 at 4:03 PM, Hubert Grzeskowiak wrote:

Aaron Griffin schrieb:

...

On Fri, Dec 12, 2008 at 2:20 PM, Hubert Grzeskowiak wrote:

...

Hubert Grzeskowiak schrieb:

...

Aaron Griffin schrieb:

...

...

Aaron Griffin schrieb: > On Thu, Dec 11, 2008 at 12:47 PM, Hubert Grzeskowiak > wrote: >> 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 - > 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 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?

either that or it's sudo. i've only tested it with the default umask so far and without sudo. if the bug would appear there, it would be easy to say that it's pacman setting his own strange permissions.

i think, we need a few more tests for a precise statement: -sudo pacman with non-default umask -su/root pacman with non-default umask sry that i don't make it myself, but i'm currently kinda out of time unfortunately.

sudo might do some weird LD_PRELOAD magic, causing the umask() syscall to not really work right- that is my best guess. -Dan

Aaron Griffin schrieb:

On Fri, Dec 12, 2008 at 4:25 PM, Dan McGee wrote:

...

On Fri, Dec 12, 2008 at 4:03 PM, Hubert Grzeskowiak wrote:

...

Aaron Griffin schrieb:

...

On Fri, Dec 12, 2008 at 2:20 PM, Hubert Grzeskowiak wrote:

...

Hubert Grzeskowiak schrieb:

...

Aaron Griffin schrieb: > On Thu, Dec 11, 2008 at 2:46 PM, Hubert Grzeskowiak > wrote: >> Aaron Griffin schrieb: >>> On Thu, Dec 11, 2008 at 12:47 PM, Hubert Grzeskowiak >>> wrote: >>>> 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 - >>> 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 > 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?

either that or it's sudo. i've only tested it with the default umask so far and without sudo. if the bug would appear there, it would be easy to say that it's pacman setting his own strange permissions.

i think, we need a few more tests for a precise statement: -sudo pacman with non-default umask -su/root pacman with non-default umask sry that i don't make it myself, but i'm currently kinda out of time unfortunately. sudo might do some weird LD_PRELOAD magic, causing the umask() syscall to not really work right- that is my best guess.

Oh la la. Thank you Xyne! http://bbs.archlinux.org/viewtopic.php?id=59483

so we have the reason now, but not a solution at all. should we yell at the sudo devs now or patch it ourselves (what would be against arch's ideals)? a pacman hack would be possible, too, but an exception for sudo is kinda dirty. i don't want to reorganize my system settings for a so-called feature in sudo and i'm sure there are many others thinking the same way. H.G.

I have not seen any more messages about this question... Just one bit of information: I have had this problem in one of my machines, and I have not even installed sudo. Regards, Guillermo -----Mensaje original----- De: arch-general-bounces@archlinux.org [mailto:arch-general-bounces@archlinux.org] En nombre de Hubert Grzeskowiak Enviado el: domingo, 14 de diciembre de 2008 23:30 Para: arch-general@archlinux.org Asunto: Re: [arch-general] wrong file permissions in /var/lib/pacman/local setting user's umask to 0022 before sudo pacman works and it's independent of root's umask. H.G.

On Thu, Dec 11, 2008 at 2:50 PM, Aaron Griffin wrote:

On Thu, Dec 11, 2008 at 2:46 PM, Hubert Grzeskowiak wrote:

...

Aaron Griffin schrieb:

...

On Thu, Dec 11, 2008 at 12:47 PM, Hubert Grzeskowiak wrote:

...

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 - 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 the cause... Still, pacman's explicit chmod of this dir should fix this... gah.

Dan, does pacman also explicitly set its own umask anywhere?

Yeah, that bug report points you directly to the code where that happens: http://projects.archlinux.org/?p=pacman.git;a=blob;f=lib/libalpm/be_files.c;...