The flag is still set in the makepkg pkg tree, but it seems to get lost when pacman does the actual install onto the system. Is this the expected behavior from pacman?
It's not really a big deal since I've just been using the install script to chmod the bit back, but I just wanted to check in case I missed something obvious.
Umm... Are you sure it's a good idea to make pacman setuid?
I think you might have misunderstood me (or maybe vice versa). I'm referring to setuid files being installed by pacman, not flagging pacman itself with setuid.
Last edited by bdrive (2008-11-05 18:11:00)
I am still having this exact issue with pacman 4.2.1
Does anyone know if this is the correct behavior? (and if it is, why?)
I solved the problem. In the end, the issue was really about the behavior of chown (which I had used in the install script).
To solve the problem, do chown first and then chmod, because chown removes the setuid bit (apparently for security reasons).
Please don't necrobump: https://wiki.archlinux.org/index.php/Fo … bumping.22