libopie problems after upgrade to 10.2

[Johan Schuijt-Li]

I actually have the exact same problem, but worked around by creating a symlink. My libopie.so.8 has the exact same properties as yours (file length and date).

I also did a small diff on the checksums in /usr/lib compared to the release build:

$ diff base.txt jail.txt 
12,13c12,13
< SHA256 (dtrace) = 7a9b63f277e8ecc59969fd76c0ed77981b1cd58f6934e5893208820df6fd379d
< SHA256 (engines) = c99cccdfe0bbbd06d049309d67012809e53337f4b8d534cffbc7f28c4347f4da
---
> SHA256 (dtrace) = e55210c96547241d3747b755578f7e2c9a9561759b6f90ba3b802090184531a3
> SHA256 (engines) = d58cb5ccc79382bef2d1b2637c914120502032f8ab933d28f703ffc2ba0a9b0b
15,16c15,16
< SHA256 (i18n) = d7d88d2462ff9e50b9b5666bf93def022d9f10c23c038acc07f429c8ace86095
< SHA256 (include) = 1a9401ab8473379478012cf6af354f3448dffd6ba22af138c940824e2695f6e6
---
> SHA256 (i18n) = f699bb9a283924ade54398dc45c67c511789435ff76abd08060f1016a09d88bd
> SHA256 (include) = 5036f146c7e63b8414f62cac8c13abb92cb1c16dd8845748b8eca320a1f69d42
330,332c330,331
< SHA256 (libopie.so) = c8ce7de5c31ddfd588cf3dd5b68dd97b0f76180d09a7011a9e9b351f6c5cece0
< SHA256 (libopie.so.7) = c8ce7de5c31ddfd588cf3dd5b68dd97b0f76180d09a7011a9e9b351f6c5cece0
< SHA256 (libopie.so.8) = c8ce7de5c31ddfd588cf3dd5b68dd97b0f76180d09a7011a9e9b351f6c5cece0
---
> SHA256 (libopie.so) = 3a0c6bab3535b4a731a19e6df04b9d95ad1e3d0d6e44852c10f0ffbd7cde6ad1
> SHA256 (libopie.so.7) = 3a0c6bab3535b4a731a19e6df04b9d95ad1e3d0d6e44852c10f0ffbd7cde6ad1
558c557
< SHA256 (private) = 11bd2e8f469c06a1f88baf0a43591cb83161399dd03a644f615bf04627cc5e99
---
> SHA256 (private) = 9888acf06a8c0cbb025309581c4ed52c17d91fcc6a75340fae05807f8d0c3915


I’m comparing my installed system against a clean 10.2-RELEASE poudriere jail.

- Johan

> On 15 Aug 2015, at 20:47, Chris Anderson <cva at pobox.com> wrote:
> 
> 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 at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"