just upgraded from 10.1-RELEASE-p16 to 10.2-RELEASE using freebsd-update. after the upgrade, I began getting errors because pam_opie.so.5 has an unsatisfied link to libopie.so.7 (my system only has libopie.so.8).
I notice a fresh install of 10.2-RELEASE does indeed contain libopie.so.7, so I'm curious how I managed to get into this state in the first place and whether it is anything I should worry about. This machine has only been upgraded using freebsd-update and I'm pretty sure it started from 10.0-RELEASE. I have temporarily worked around with an entry in libmap. Here are the files involved: # ls -l /usr/lib/pam_opie* lrwxr-xr-x 1 root wheel 13 Sep 27 2013 /usr/lib/pam_opie.so -> pam_opie.so.5 -r--r--r-- 1 root wheel 7000 Aug 14 11:56 /usr/lib/pam_opie.so.5 lrwxr-xr-x 1 root wheel 19 Sep 27 2013 /usr/lib/pam_opieaccess.so -> pam_opieaccess.so.5 -r--r--r-- 1 root wheel 5568 Aug 14 11:56 /usr/lib/pam_opieaccess.so.5 # ls -l /usr/lib/libopie* -r--r--r-- 1 root wheel 84582 Aug 14 11:57 /usr/lib/libopie.a lrwxr-xr-x 1 root wheel 12 Sep 29 2014 /usr/lib/libopie.so -> libopie.so.8 -r--r--r-- 1 root wheel 38280 Oct 5 2014 /usr/lib/libopie.so.8 -r--r--r-- 1 root wheel 88048 Aug 14 11:57 /usr/lib/libopie_p.a _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
