Arch Linux

skorpan

Member

Registered: 2007-11-09

Posts: 81

pam upgrade issues

This just happened to me for no apparent reason. I can't figure out what's going on and I'd love some help here... Fortunately, pam seems to be the only package broken at the moment, so hopefully I won't have to reinstall Arch (again).

$ sudo pacman -S pam
warning: pam-1.0.3-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
error: could not open file /var/lib/pacman/local/pam-1.0.3-1/depends: No such file or directory
error: could not open file /var/lib/pacman/local/pam-1.0.3-1/depends: No such file or directory
error: could not open file /var/lib/pacman/local/pam-1.0.3-1/depends: No such file or directory
error: could not open file /var/lib/pacman/local/pam-1.0.3-1/depends: No such file or directory
...like a thousand of those...
error: could not open file /var/lib/pacman/local/pam-1.0.3-1/depends: No such file or directory
error: could not open file /var/lib/pacman/local/pam-1.0.3-1/depends: No such file or directory
error: could not open file /var/lib/pacman/local/pam-1.0.3-1/depends: No such file or directory
error: could not open file /var/lib/pacman/local/pam-1.0.3-1/depends: No such file or directory

Targets (1): pam-1.0.3-1  

Total Download Size:    0.00 MB
Total Installed Size:   1.99 MB

Proceed with installation? [Y/n] 
checking package integrity...
(1/1) checking for file conflicts [###########################################] 100%
error: could not open file /var/lib/pacman/local/pam-1.0.3-1/files: No such file or directory
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
pam: /etc/default/passwd exists in filesystem
pam: /etc/environment exists in filesystem
pam: /etc/pam.d/other exists in filesystem
pam: /etc/security/access.conf exists in filesystem
pam: /etc/security/group.conf exists in filesystem
pam: /etc/security/limits.conf exists in filesystem
pam: /etc/security/namespace.conf exists in filesystem
pam: /etc/security/namespace.init exists in filesystem
pam: /etc/security/pam_env.conf exists in filesystem
pam: /etc/security/time.conf exists in filesystem
pam: /lib/libpam.so exists in filesystem
pam: /lib/libpam.so.0 exists in filesystem
pam: /lib/libpam.so.0.81.12 exists in filesystem
pam: /lib/libpam_misc.so exists in filesystem
pam: /lib/libpam_misc.so.0 exists in filesystem
pam: /lib/libpam_misc.so.0.81.3 exists in filesystem
pam: /lib/libpamc.so exists in filesystem
pam: /lib/libpamc.so.0 exists in filesystem
pam: /lib/libpamc.so.0.81.0 exists in filesystem
pam: /lib/security/pam_access.so exists in filesystem
pam: /lib/security/pam_cracklib.so exists in filesystem
pam: /lib/security/pam_debug.so exists in filesystem
pam: /lib/security/pam_deny.so exists in filesystem
pam: /lib/security/pam_echo.so exists in filesystem
pam: /lib/security/pam_env.so exists in filesystem
pam: /lib/security/pam_exec.so exists in filesystem
pam: /lib/security/pam_faildelay.so exists in filesystem
pam: /lib/security/pam_filter.so exists in filesystem
pam: /lib/security/pam_ftp.so exists in filesystem
pam: /lib/security/pam_group.so exists in filesystem
pam: /lib/security/pam_issue.so exists in filesystem
pam: /lib/security/pam_keyinit.so exists in filesystem
pam: /lib/security/pam_lastlog.so exists in filesystem
pam: /lib/security/pam_limits.so exists in filesystem
pam: /lib/security/pam_listfile.so exists in filesystem
pam: /lib/security/pam_localuser.so exists in filesystem
pam: /lib/security/pam_loginuid.so exists in filesystem
pam: /lib/security/pam_mail.so exists in filesystem
pam: /lib/security/pam_mkhomedir.so exists in filesystem
pam: /lib/security/pam_motd.so exists in filesystem
pam: /lib/security/pam_namespace.so exists in filesystem
pam: /lib/security/pam_nologin.so exists in filesystem
pam: /lib/security/pam_permit.so exists in filesystem
pam: /lib/security/pam_rhosts.so exists in filesystem
pam: /lib/security/pam_rootok.so exists in filesystem
pam: /lib/security/pam_securetty.so exists in filesystem
pam: /lib/security/pam_shells.so exists in filesystem
pam: /lib/security/pam_stress.so exists in filesystem
pam: /lib/security/pam_succeed_if.so exists in filesystem
pam: /lib/security/pam_tally.so exists in filesystem
pam: /lib/security/pam_time.so exists in filesystem
pam: /lib/security/pam_umask.so exists in filesystem
pam: /lib/security/pam_unix.so exists in filesystem
pam: /lib/security/pam_unix2.so exists in filesystem
pam: /lib/security/pam_unix_acct.so exists in filesystem
pam: /lib/security/pam_unix_auth.so exists in filesystem
pam: /lib/security/pam_unix_session.so exists in filesystem
pam: /lib/security/pam_userdb.so exists in filesystem
pam: /lib/security/pam_warn.so exists in filesystem
pam: /lib/security/pam_xauth.so exists in filesystem
Errors occurred, no packages were upgraded.

u_no_hu

Member

Registered: 2008-06-15

Posts: 453

Re: pam upgrade issues

Seems like your local database got corrupted. Try removing and installing pam and hope noting else got corrupted....

---

Don't be a HELP VAMPIRE. Please search before you ask.

Subscribe to The Arch Daily News.

skorpan

Member

Registered: 2007-11-09

Posts: 81

Re: pam upgrade issues

This is what happens when I try to remove it:

$ sudo pacman -R pam
checking dependencies...
error: could not open file /var/lib/pacman/local/pam-1.0.3-1/depends: No such file or directory
error: could not open file /var/lib/pacman/local/pam-1.0.3-1/depends: No such file or directory
error: could not open file /var/lib/pacman/local/pam-1.0.3-1/depends: No such file or directory
error: could not open file /var/lib/pacman/local/pam-1.0.3-1/depends: No such file or directory
error: could not open file /var/lib/pacman/local/pam-1.0.3-1/depends: No such file or directory
...a thousand of those...
error: could not open file /var/lib/pacman/local/pam-1.0.3-1/depends: No such file or directory
error: could not open file /var/lib/pacman/local/pam-1.0.3-1/depends: No such file or directory
error: could not open file /var/lib/pacman/local/pam-1.0.3-1/depends: No such file or directory
error: could not open file /var/lib/pacman/local/pam-1.0.3-1/depends: No such file or directory
error: could not open file /var/lib/pacman/local/pam-1.0.3-1/depends: No such file or directory
error: failed to prepare transaction (could not satisfy dependencies)
:: coreutils: requires pam>=1.0.1-1
:: openssh: requires pam
:: shadow: requires pam
:: sudo: requires pam

Should I remove coreutils, openssh, shadow and sudo as well?

bender02

Member

From: UK

Registered: 2007-02-04

Posts: 1,328

Re: pam upgrade issues

You could try forcing reinstalling pam: pacman -Sf pam
Thank should fix the problem with the pacman database that you have.

skorpan

Member

Registered: 2007-11-09

Posts: 81

Re: pam upgrade issues

Seemed to work, thanks a lot! Let's hope nothing breaks again!

wonder

Developer

From: Bucharest, Romania

Registered: 2006-07-05

Posts: 5,941

Website

Re: pam upgrade issues

in the future don't force anything. the problem was in pacman database. just do pacman -Syy

---

Give what you have. To someone, it may be better than you dare to think.

ghostHack

Member

From: Bristol UK

Registered: 2008-02-29

Posts: 261

Re: pam upgrade issues

His problem was with /var/lib/pacman/local which is the currently installed packages, pacman -Syy only rebuilds the /var/lib/pacman/sync database (AFAIK).