You are not logged in.
Pages: 1
Hey all.
pam=1.3.1-1.1 has picked up a dependency on libaudit:
$ ldd /usr/lib/libpam.so
linux-gate.so.1 (0xb7f60000)
libaudit.so.1 => /usr/lib/libaudit.so.1 (0xb7f00000)
libdl.so.2 => /usr/lib/libdl.so.2 (0xb7efa000)
libc.so.6 => /usr/lib/libc.so.6 (0xb7d18000)
libcap-ng.so.0 => /usr/lib/libcap-ng.so.0 (0xb7d11000)
/usr/lib/ld-linux.so.2 (0xb7f62000)
This dependency isn't present in x86_64, and isn't listed in the PKGBUILD depends - is this intended as an upcoming change, or something like a dirty chroot?
Currently, without a depends entry, upgrading only the `pam` package won't pull in `audit` which makes anything with a pam rule fail, e.g.
$ sudo
sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy"
sudo: unable to load /usr/lib/sudo/sudoers.so: libaudit.so.1: cannot open shared object file: No such file or directory
sudo: fatal error, unable to load plugins
Building in a chroot/build container without `audit` installed produces `pam` without the linked dependency:
$ ldd /usr/lib/libpam.so
linux-gate.so.1 (0xf7750000)
libdl.so.2 => /usr/lib/libdl.so.2 (0xf772d000)
libc.so.6 => /usr/lib/libc.so.6 (0xf754b000)
/usr/lib/ld-linux.so.2 (0xf7752000)
Offline
Your clean build libpam also seems to be missing a libcap-ng include (that wasn't listed as a dependency in the PKGBUILD presumably), although I seem to recall having libcap-ng anyway.
I've very little idea what's going on here. At a guess, it seems to have been linked against libs it doesn't actually require.
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
I'll just note that I have audit installed because it's a dependency of package systemd.
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
Oh, oops. https://git.archlinux.org/svntogit/pack … fb24482448 added audit to systemd. That would explain it.
Offline
Pages: 1