On 08/16/2015 19:47, Kimmo Paasiala wrote:
> On Sun, Aug 16, 2015 at 8:40 PM, Jan Henrik Sylvester wrote:
>> On 08/15/2015 20:47, Chris Anderson 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.s
On Sun, Aug 16, 2015 at 8:40 PM, Jan Henrik Sylvester wrote:
> On 08/15/2015 20:47, Chris Anderson 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 (m
On 08/15/2015 20:47, Chris Anderson 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 1
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 (dt
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 cu
