libpam.so lost in update to 11.0-ALPHA3
Bryan Drewery
bdrewery at FreeBSD.org
Thu Jun 16 22:35:33 UTC 2016
On 6/16/16 11:39 AM, Florian Ermisch wrote:
>
>
> Am 14. Juni 2016 13:36:32 MESZ, schrieb Ben Woods <woodsb02 at gmail.com>:
>> On Tuesday, 14 June 2016, Pavel Timofeev <timp87 at gmail.com> wrote:
>>
>>>
>>> 14 июня 2016 г. 10:37 пользователь "Ben Woods" <woodsb02 at gmail.com
>>> <javascript:_e(%7B%7D,'cvml','woodsb02 at gmail.com');>> написал:
>>>>
>>>> On 14 June 2016 at 09:11, René Ladan <rene at freebsd.org
>>> <javascript:_e(%7B%7D,'cvml','rene at freebsd.org');>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I updated my pkgbase installation (11.0-amd64 from a few weeks
>> ago) to
>>>>> 11.0-ALPHA3. Building and installing went fine but it turns out
>> that
>>>>> libpam.so* is lost in the update (both the symlink and the
>> actual so,
>>>>> currently so.6) :
>>>>>
>>>>> # pkg upgrade
>>>>> # pkg autoremove
>>>>> <<FreeBSD-lib removed which contains the old libpam.so.5, so
>> one
>>>>> version lower)
>>>>> << yes, I forgot to run mergemaster>>
>>>>> # reboot
>>>>> <<login(1) no longer works, but single-user + dhclient is
>> still fine)
>>>>>
>>>>> Is this a known bug?
>>>>>
>>>>> Regards,
>>>>> René
>>>>>
>>>>
>>>> Michael Lucas mentioned on twitter a few days ago that pam was
>> broken
>>>> recently in FreeBSD current.
>>>>
>>>> Michael: was this a problem with libpam.so going missing? Were you
>> using
>>>> pkgbase, or is this an issue with the normal build/install system
>> also?
>>>>
>>>> Regards,
>>>> Ben
>>>>
>>>> --
>>>
>>> Hi!
>>> I have the same problem with normal build/install system.
>>>
>>
>> Ok, thanks for the feedback.
>>
>> Bringing in the FreeBSD-current@ mailing list as it is not a problem
>> with
>> PkgBase, but with 11-current.
>>
>> Regards,
>> Ben
>>
> On my laptop running a few weeks old CURRENT sudo
> just broke after a `pkg upgrade`. The missing lib it's
> complaining about is libpam.so.6 but when built from
> ports it's linked against libpam.so.5.
>
Packages built after base r301892 will be fixed.
--
Regards,
Bryan Drewery
More information about the freebsd-current
mailing list