[gentoo-user] glibc-2.14.1 upgrade

[gentoo-user] glibc-2.14.1 upgrade

[Paul Hartman]

Hi,

After emerging glibc-2.14.1 today, pam stopped working, which
prevented KDE from working and some other things. I got this kind of
message:

/lib64/libc.so.6: version `GLIBC_2.14' not found (required by
/lib64/libcrypt.so.1)

There were no @preserved-rebuild and revdep-rebuild found nothing. I
rebuilt pam and things seem to be working again. Are there any other
packages I should rebuild before encountering a problem? Or some way
to detect which need to be rebuilt? Should I re-emerge world against
my new glibc? :)

Thanks,
Paul

Re: [gentoo-user] glibc-2.14.1 upgrade

[justin]

[-- Attachment #1: Type: text/plain, Size: 821 bytes --]

On 24/11/11 06:27, Paul Hartman wrote:
> Hi,
> 
> After emerging glibc-2.14.1 today, pam stopped working, which
> prevented KDE from working and some other things. I got this kind of
> message:
> 
> /lib64/libc.so.6: version `GLIBC_2.14' not found (required by
> /lib64/libcrypt.so.1)
> 
> There were no @preserved-rebuild and revdep-rebuild found nothing. I
> rebuilt pam and things seem to be working again. Are there any other
> packages I should rebuild before encountering a problem? Or some way
> to detect which need to be rebuilt? Should I re-emerge world against
> my new glibc? :)
> 
> Thanks,
> Paul
> 

Hi Paul,

after an glibc upgrade it is time to do an

emerge -e system world


This is what binary distros actually do when they have major bumps in
their releases.

Justin


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

Re: [gentoo-user] glibc-2.14.1 upgrade

[微菜]

[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]

于 2011年11月24日 15:34, justin 写道:
> On 24/11/11 06:27, Paul Hartman wrote:
>> Hi,
>>
>> After emerging glibc-2.14.1 today, pam stopped working, which
>> prevented KDE from working and some other things. I got this kind of
>> message:
>>
>> /lib64/libc.so.6: version `GLIBC_2.14' not found (required by
>> /lib64/libcrypt.so.1)
>>
>> There were no @preserved-rebuild and revdep-rebuild found nothing. I
>> rebuilt pam and things seem to be working again. Are there any other
>> packages I should rebuild before encountering a problem? Or some way
>> to detect which need to be rebuilt? Should I re-emerge world against
>> my new glibc? :)
>>
>> Thanks,
>> Paul
>>
> 
> Hi Paul,
> 
> after an glibc upgrade it is time to do an
> 
> emerge -e system world

you must be kidding me . it will take days to complete.

> 
> 
> This is what binary distros actually do when they have major bumps in
> their releases.
> 
> Justin
> 


-- 
我是天马博士，对，就是创造了阿童木的那个天马博士


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

Re: [gentoo-user] glibc-2.14.1 upgrade

[Pandu Poluan]

[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]

On Nov 26, 2011 12:05 AM, "微菜" <microcai@fedoraproject.org> wrote:
>
> 于 2011年11月24日 15:34, justin 写道:
> > On 24/11/11 06:27, Paul Hartman wrote:
> >> Hi,
> >>
> >> After emerging glibc-2.14.1 today, pam stopped working, which
> >> prevented KDE from working and some other things. I got this kind of
> >> message:
> >>
> >> /lib64/libc.so.6: version `GLIBC_2.14' not found (required by
> >> /lib64/libcrypt.so.1)
> >>
> >> There were no @preserved-rebuild and revdep-rebuild found nothing. I
> >> rebuilt pam and things seem to be working again. Are there any other
> >> packages I should rebuild before encountering a problem? Or some way
> >> to detect which need to be rebuilt? Should I re-emerge world against
> >> my new glibc? :)
> >>
> >> Thanks,
> >> Paul
> >>
> >
> > Hi Paul,
> >
> > after an glibc upgrade it is time to do an
> >
> > emerge -e system world
>
> you must be kidding me . it will take days to complete.
>

On my virtualized servers, emerge -e @system @world, a total of
170-something packages, takes only about 6-7 hours. Remember, these are
VMs, which means the 2 vCPUs I assigned them are actually shared with other
VMs.

On a non-virtualized system, should be faster. Of course, if you have
sizable packages, it might take around 24 hours to complete.

Rgds,

[-- Attachment #2: Type: text/html, Size: 1784 bytes --]

Re: [gentoo-user] glibc-2.14.1 upgrade

[Florian Philipp]

[-- Attachment #1: Type: text/plain, Size: 1817 bytes --]

Am 25.11.2011 19:11, schrieb Pandu Poluan:
> 
> On Nov 26, 2011 12:05 AM, "微菜" <microcai@fedoraproject.org
> <mailto:microcai@fedoraproject.org>> wrote:
>>
>> 于 2011年11月24日 15:34, justin 写道:
>> > On 24/11/11 06:27, Paul Hartman wrote:
>> >> Hi,
>> >>
>> >> After emerging glibc-2.14.1 today, pam stopped working, which
>> >> prevented KDE from working and some other things. I got this kind of
>> >> message:
>> >>
>> >> /lib64/libc.so.6: version `GLIBC_2.14' not found (required by
>> >> /lib64/libcrypt.so.1)
>> >>
>> >> There were no @preserved-rebuild and revdep-rebuild found nothing. I
>> >> rebuilt pam and things seem to be working again. Are there any other
>> >> packages I should rebuild before encountering a problem? Or some way
>> >> to detect which need to be rebuilt? Should I re-emerge world against
>> >> my new glibc? :)
>> >>
>> >> Thanks,
>> >> Paul
>> >>
>> >
>> > Hi Paul,
>> >
>> > after an glibc upgrade it is time to do an
>> >
>> > emerge -e system world
>>
>> you must be kidding me . it will take days to complete.
>>
> 
> On my virtualized servers, emerge -e @system @world, a total of
> 170-something packages, takes only about 6-7 hours. Remember, these are
> VMs, which means the 2 vCPUs I assigned them are actually shared with
> other VMs.
> 
> On a non-virtualized system, should be faster. Of course, if you have
> sizable packages, it might take around 24 hours to complete.
> 
> Rgds,
> 

I've used Gentoo since 2006 and never had any reason to emerge -e. I can
also cite posts on this mailing list going back as far as 2007 (just my
local archive, mind you) that say it is unnecessary for glibc updates.
Or, to cite Volker Armin Hemmann's eloquent reply from 08-11-2007: "no" ;-)

Regards,
Florian Philipp


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

Re: [gentoo-user] glibc-2.14.1 upgrade

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 378 bytes --]

On Fri, 25 Nov 2011 19:59:51 +0100, Florian Philipp wrote:

> I've used Gentoo since 2006 and never had any reason to emerge -e.

Apart from the occasional gcc ABI change, the only time I do it is after
a fresh install, so that everything is built with the installed toolchain.


-- 
Neil Bothwick

In possession of a mind not merely twisted, but actually sprained.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] glibc-2.14.1 upgrade

[Albert W. Hopkins]

On Fri, 2011-11-25 at 22:30 +0000, Neil Bothwick wrote:
> On Fri, 25 Nov 2011 19:59:51 +0100, Florian Philipp wrote:
> 
> > I've used Gentoo since 2006 and never had any reason to emerge -e.
> 
> Apart from the occasional gcc ABI change, the only time I do it is after
> a fresh install, so that everything is built with the installed toolchain.

I do it about once per month, just to make sure everthing works as
should, and, if not, usually I'll submit a bug report if necessary.

Re: [gentoo-user] glibc-2.14.1 upgrade

[Michael Mol]

[-- Attachment #1: Type: text/plain, Size: 2258 bytes --]

106 minutes, 177 packsges on a fresh install (on a dual E5345 I just got my
hands on). God help you if you if you have KDE installed, though. Even
without it, my core desktop has somewhere between 500-700 packages. Builds
overnight on my Phenom 9650.

ZZ
On Nov 25, 2011 2:04 PM, "Florian Philipp" <lists@binarywings.net> wrote:

> Am 25.11.2011 19:11, schrieb Pandu Poluan:
> >
> > On Nov 26, 2011 12:05 AM, "微菜" <microcai@fedoraproject.org
> > <mailto:microcai@fedoraproject.org>> wrote:
> >>
> >> 于 2011年11月24日 15:34, justin 写道:
> >> > On 24/11/11 06:27, Paul Hartman wrote:
> >> >> Hi,
> >> >>
> >> >> After emerging glibc-2.14.1 today, pam stopped working, which
> >> >> prevented KDE from working and some other things. I got this kind of
> >> >> message:
> >> >>
> >> >> /lib64/libc.so.6: version `GLIBC_2.14' not found (required by
> >> >> /lib64/libcrypt.so.1)
> >> >>
> >> >> There were no @preserved-rebuild and revdep-rebuild found nothing. I
> >> >> rebuilt pam and things seem to be working again. Are there any other
> >> >> packages I should rebuild before encountering a problem? Or some way
> >> >> to detect which need to be rebuilt? Should I re-emerge world against
> >> >> my new glibc? :)
> >> >>
> >> >> Thanks,
> >> >> Paul
> >> >>
> >> >
> >> > Hi Paul,
> >> >
> >> > after an glibc upgrade it is time to do an
> >> >
> >> > emerge -e system world
> >>
> >> you must be kidding me . it will take days to complete.
> >>
> >
> > On my virtualized servers, emerge -e @system @world, a total of
> > 170-something packages, takes only about 6-7 hours. Remember, these are
> > VMs, which means the 2 vCPUs I assigned them are actually shared with
> > other VMs.
> >
> > On a non-virtualized system, should be faster. Of course, if you have
> > sizable packages, it might take around 24 hours to complete.
> >
> > Rgds,
> >
>
> I've used Gentoo since 2006 and never had any reason to emerge -e. I can
> also cite posts on this mailing list going back as far as 2007 (just my
> local archive, mind you) that say it is unnecessary for glibc updates.
> Or, to cite Volker Armin Hemmann's eloquent reply from 08-11-2007: "no" ;-)
>
> Regards,
> Florian Philipp
>
>

[-- Attachment #2: Type: text/html, Size: 3096 bytes --]

Re: [gentoo-user] glibc-2.14.1 upgrade

[Volker Armin Hemmann]

[-- Attachment #1: Type: text/plain, Size: 2763 bytes --]

2011/11/25 Florian Philipp <lists@binarywings.net>

> Am 25.11.2011 19:11, schrieb Pandu Poluan:
> >
> > On Nov 26, 2011 12:05 AM, "微菜" <microcai@fedoraproject.org
> > <mailto:microcai@fedoraproject.org>> wrote:
> >>
> >> 于 2011年11月24日 15:34, justin 写道:
> >> > On 24/11/11 06:27, Paul Hartman wrote:
> >> >> Hi,
> >> >>
> >> >> After emerging glibc-2.14.1 today, pam stopped working, which
> >> >> prevented KDE from working and some other things. I got this kind of
> >> >> message:
> >> >>
> >> >> /lib64/libc.so.6: version `GLIBC_2.14' not found (required by
> >> >> /lib64/libcrypt.so.1)
> >> >>
> >> >> There were no @preserved-rebuild and revdep-rebuild found nothing. I
> >> >> rebuilt pam and things seem to be working again. Are there any other
> >> >> packages I should rebuild before encountering a problem? Or some way
> >> >> to detect which need to be rebuilt? Should I re-emerge world against
> >> >> my new glibc? :)
> >> >>
> >> >> Thanks,
> >> >> Paul
> >> >>
> >> >
> >> > Hi Paul,
> >> >
> >> > after an glibc upgrade it is time to do an
> >> >
> >> > emerge -e system world
> >>
> >> you must be kidding me . it will take days to complete.
> >>
> >
> > On my virtualized servers, emerge -e @system @world, a total of
> > 170-something packages, takes only about 6-7 hours. Remember, these are
> > VMs, which means the 2 vCPUs I assigned them are actually shared with
> > other VMs.
> >
> > On a non-virtualized system, should be faster. Of course, if you have
> > sizable packages, it might take around 24 hours to complete.
> >
> > Rgds,
> >
>
> I've used Gentoo since 2006 and never had any reason to emerge -e. I can
> also cite posts on this mailing list going back as far as 2007 (just my
> local archive, mind you) that say it is unnecessary for glibc updates.
> Or, to cite Volker Armin Hemmann's eloquent reply from 08-11-2007: "no" ;-)
>
> Regards,
> Florian Philipp
>
>
sys-libs/glibc
     Available versions:  (2.2) (~)2.9_p20081201-r3!s 2.10.1-r1!s 2.11.3!s
(~)2.12.1-r3!s 2.12.2!s (~)2.13-r2!s (~)2.13-r4!s (~)2.14!s
(~)2.14.1!s{tbz2} **9999!s

        {crosscompile_opts_headers-only debug gd glibc-omitfp hardened
multilib nls profile selinux vanilla}
     Installed versions:  2.14.1(2.2)!s{tbz2}(18:07:50 23.11.2011)(gd
glibc-omitfp multilib nls -crosscompile_opts_headers-only -debug -hardened
-profile -selinux -vanilla)

no -e world

login working fine. Posting from KDE 4.7.80

so, I stay with the 'no' from back than.

you don't need to do an -e world on glibc or header updates.

You CAN do it, to make use of some new and awesome feature you might hope
to be there. But for almost all people it is just a waste of time and
energy.

[-- Attachment #2: Type: text/html, Size: 4399 bytes --]

Re: [gentoo-user] glibc-2.14.1 upgrade

[Paul Hartman]

On Fri, Nov 25, 2011 at 12:59 PM, Florian Philipp <lists@binarywings.net> wrote:
> Am 25.11.2011 19:11, schrieb Pandu Poluan:
>>
>> On Nov 26, 2011 12:05 AM, "微菜" <microcai@fedoraproject.org
>> <mailto:microcai@fedoraproject.org>> wrote:
>>>
>>> 于 2011年11月24日 15:34, justin 写道:
>>> > On 24/11/11 06:27, Paul Hartman wrote:
>>> >> Hi,
>>> >>
>>> >> After emerging glibc-2.14.1 today, pam stopped working, which
>>> >> prevented KDE from working and some other things. I got this kind of
>>> >> message:
>>> >>
>>> >> /lib64/libc.so.6: version `GLIBC_2.14' not found (required by
>>> >> /lib64/libcrypt.so.1)
>>> >>
>>> >> There were no @preserved-rebuild and revdep-rebuild found nothing. I
>>> >> rebuilt pam and things seem to be working again. Are there any other
>>> >> packages I should rebuild before encountering a problem? Or some way
>>> >> to detect which need to be rebuilt? Should I re-emerge world against
>>> >> my new glibc? :)
>>> >>
>>> >> Thanks,
>>> >> Paul
>>> >>
>>> >
>>> > Hi Paul,
>>> >
>>> > after an glibc upgrade it is time to do an
>>> >
>>> > emerge -e system world
>>>
>>> you must be kidding me . it will take days to complete.
>>>
>>
>> On my virtualized servers, emerge -e @system @world, a total of
>> 170-something packages, takes only about 6-7 hours. Remember, these are
>> VMs, which means the 2 vCPUs I assigned them are actually shared with
>> other VMs.
>>
>> On a non-virtualized system, should be faster. Of course, if you have
>> sizable packages, it might take around 24 hours to complete.
>>
>> Rgds,
>>
>
> I've used Gentoo since 2006 and never had any reason to emerge -e. I can
> also cite posts on this mailing list going back as far as 2007 (just my
> local archive, mind you) that say it is unnecessary for glibc updates.
> Or, to cite Volker Armin Hemmann's eloquent reply from 08-11-2007: "no" ;-)

Can I detect which packages need to be rebuilt (revdep-rebuild finds
nothing), other than waiting for something to fail? Or do you think
the messages are a false alarm, symptoms of already-loaded programs
and will go away after my next reboot?

Re: [gentoo-user] glibc-2.14.1 upgrade

[Adam Carter]

>>> >> /lib64/libc.so.6: version `GLIBC_2.14' not found (required by
>>> >> /lib64/libcrypt.so.1)
>>> >>
>>> >> There were no @preserved-rebuild and revdep-rebuild found nothing. I
>>> >> rebuilt pam and things seem to be working again. Are there any other
>>> >> packages I should rebuild before encountering a problem? Or some way
>>> >> to detect which need to be rebuilt? Should I re-emerge world against
>>> >> my new glibc? :)

How did you know to rebuild pam?

Both /lib64/libc.so.6 and /lib64/libcrypt.so.1 are from glibc, and I
interpret your error as  'libcrypt.so.1 couldn't find a GLIBC_2.14
version of /lib64/libc.so.6', which doesn't make any sense to me as
both files are from the same package. How could the version dependency
between them be incorrect?

Re: [gentoo-user] glibc-2.14.1 upgrade

[Paul Hartman]

On Sat, Nov 26, 2011 at 6:25 PM, Adam Carter <adamcarter3@gmail.com> wrote:
>>>> >> /lib64/libc.so.6: version `GLIBC_2.14' not found (required by
>>>> >> /lib64/libcrypt.so.1)
>>>> >>
>>>> >> There were no @preserved-rebuild and revdep-rebuild found nothing. I
>>>> >> rebuilt pam and things seem to be working again. Are there any other
>>>> >> packages I should rebuild before encountering a problem? Or some way
>>>> >> to detect which need to be rebuilt? Should I re-emerge world against
>>>> >> my new glibc? :)
>
> How did you know to rebuild pam?
>
> Both /lib64/libc.so.6 and /lib64/libcrypt.so.1 are from glibc, and I
> interpret your error as  'libcrypt.so.1 couldn't find a GLIBC_2.14
> version of /lib64/libc.so.6', which doesn't make any sense to me as
> both files are from the same package. How could the version dependency
> between them be incorrect?

Sorry, I accidentally pasted the incomplete error message. It was part
of this kind of message in my syslog:

Nov 25 19:40:01 [cron] PAM unable to
dlopen(/lib64/security/pam_unix.so): /lib64/libc.so.6: version
`GLIBC_2.14' not found (required by /lib64/security/pam_unix.so)
Nov 25 19:40:01 [cron] PAM adding faulty module: /lib64/security/pam_unix.so

and xdm wouldn't restart after i upgraded glibc, until I rebuilt PAM.
Or maybe it was coincidental...

Re: [gentoo-user] glibc-2.14.1 upgrade

[Florian Philipp]

[-- Attachment #1: Type: text/plain, Size: 1630 bytes --]

Am 27.11.2011 01:59, schrieb Paul Hartman:
> On Sat, Nov 26, 2011 at 6:25 PM, Adam Carter <adamcarter3@gmail.com> wrote:
>>>>>>> /lib64/libc.so.6: version `GLIBC_2.14' not found (required by
>>>>>>> /lib64/libcrypt.so.1)
>>>>>>>
>>>>>>> There were no @preserved-rebuild and revdep-rebuild found nothing. I
>>>>>>> rebuilt pam and things seem to be working again. Are there any other
>>>>>>> packages I should rebuild before encountering a problem? Or some way
>>>>>>> to detect which need to be rebuilt? Should I re-emerge world against
>>>>>>> my new glibc? :)
>>
>> How did you know to rebuild pam?
>>
>> Both /lib64/libc.so.6 and /lib64/libcrypt.so.1 are from glibc, and I
>> interpret your error as  'libcrypt.so.1 couldn't find a GLIBC_2.14
>> version of /lib64/libc.so.6', which doesn't make any sense to me as
>> both files are from the same package. How could the version dependency
>> between them be incorrect?
> 
> Sorry, I accidentally pasted the incomplete error message. It was part
> of this kind of message in my syslog:
> 
> Nov 25 19:40:01 [cron] PAM unable to
> dlopen(/lib64/security/pam_unix.so): /lib64/libc.so.6: version
> `GLIBC_2.14' not found (required by /lib64/security/pam_unix.so)
> Nov 25 19:40:01 [cron] PAM adding faulty module: /lib64/security/pam_unix.so
> 

THAT is the reason why neither revdep-rebuild nor @preserved-rebuild
found pam. It dynamically loads libraries using dlopen instead of
letting the dynamic linker handle it when the application is started.
There is no reasonable way for revdep-rebuild to find these issues.

Regards,
Florian Philipp


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]