--- Dan McGee <dpmcgee@gmail.com> wrote:
On 8/20/07, Mister Dobalina <reebydobalina@yahoo.ca> wrote:
# pacman -Q pacman libarchive pacman 3.0.5-3 libarchive 2.2.6-1
# mkdir /tmp/pacman.test
# pacman -Ud
/var/cache/pacman/pkg/filesystem-2007.08-1.pkg.tar.gz
--root /tmp/pacman.test
# ls -l /tmp/pacman.test
total 0 drwxr-xr-x 2 root root 40 2007-07-30 15:52 bin/ drwxr-xr-x 2 root root 40 2007-07-30 15:52 boot/ drwxr-xr-x 2 root root 40 2007-07-30 15:52 dev/ drwxr-xr-x 4 root root 440 2007-07-30 15:52 etc/ drwxr-xr-x 3 root root 60 2007-07-30 15:52 home/ drwxr-xr-x 3 root root 60 2007-07-30 15:52 lib/ drwxr-xr-x 5 root root 100 2007-07-30 15:52 mnt/ drwxr-xr-x 2 root root 40 2007-07-30 15:52 opt/ drwxr-xr-x 2 root root 40 2007-07-30 15:52 proc/ drwxr-x--- 2 root root 40 2007-07-30 15:52 root/ drwxr-xr-x 2 root root 40 2007-07-30 15:52 sbin/ drwxr-xr-x 2 root root 40 2007-07-30 15:52 srv/ drwxr-xr-x 2 root root 40 2007-07-30 15:52 sys/ drwxr-xr-x 2 root root 40 2007-08-20 12:09 tmp/ drwxr-xr-x 10 root root 220 2007-07-30 15:52 usr/ drwxr-xr-x 13 root root 280 2007-08-20 12:09 var/
Did you run this as root? If not, scriptlets and directory permissions could get funky as a regular user doesn't have permission to chroot (to run scriptlets) and/or set some funky permissions on directories, perhaps.
-Dan
All commands were run as root. The reason I sent the original message is that a few days ago this problem wasn't happening, but after a recent update it started. I noticed it because I use the --root option to set up a quick'n'dirty tmpfs chroot environment from a small set of base packages, all from a script. The problem is obviously very easy to chmod around in the script, but just wanted to let you know that this had suddenly popped up. Cheers, Jeremy Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail at http://mrd.mail.yahoo.com/try_beta?.intl=ca