| 1 |
On Fri, Nov 25, 2011 at 12:59 PM, Florian Philipp <lists@×××××××××××.net> wrote: |
| 2 |
> Am 25.11.2011 19:11, schrieb Pandu Poluan: |
| 3 |
>> |
| 4 |
>> On Nov 26, 2011 12:05 AM, "΢²Ë" <microcai@×××××××××××××.org |
| 5 |
>> <mailto:microcai@×××××××××××××.org>> wrote: |
| 6 |
>>> |
| 7 |
>>> ÓÚ 2011Äê11ÔÂ24ÈÕ 15:34, justin дµÀ: |
| 8 |
>>> > On 24/11/11 06:27, Paul Hartman wrote: |
| 9 |
>>> >> Hi, |
| 10 |
>>> >> |
| 11 |
>>> >> After emerging glibc-2.14.1 today, pam stopped working, which |
| 12 |
>>> >> prevented KDE from working and some other things. I got this kind of |
| 13 |
>>> >> message: |
| 14 |
>>> >> |
| 15 |
>>> >> /lib64/libc.so.6: version `GLIBC_2.14' not found (required by |
| 16 |
>>> >> /lib64/libcrypt.so.1) |
| 17 |
>>> >> |
| 18 |
>>> >> There were no @preserved-rebuild and revdep-rebuild found nothing. I |
| 19 |
>>> >> rebuilt pam and things seem to be working again. Are there any other |
| 20 |
>>> >> packages I should rebuild before encountering a problem? Or some way |
| 21 |
>>> >> to detect which need to be rebuilt? Should I re-emerge world against |
| 22 |
>>> >> my new glibc? :) |
| 23 |
>>> >> |
| 24 |
>>> >> Thanks, |
| 25 |
>>> >> Paul |
| 26 |
>>> >> |
| 27 |
>>> > |
| 28 |
>>> > Hi Paul, |
| 29 |
>>> > |
| 30 |
>>> > after an glibc upgrade it is time to do an |
| 31 |
>>> > |
| 32 |
>>> > emerge -e system world |
| 33 |
>>> |
| 34 |
>>> you must be kidding me . it will take days to complete. |
| 35 |
>>> |
| 36 |
>> |
| 37 |
>> On my virtualized servers, emerge -e @system @world, a total of |
| 38 |
>> 170-something packages, takes only about 6-7 hours. Remember, these are |
| 39 |
>> VMs, which means the 2 vCPUs I assigned them are actually shared with |
| 40 |
>> other VMs. |
| 41 |
>> |
| 42 |
>> On a non-virtualized system, should be faster. Of course, if you have |
| 43 |
>> sizable packages, it might take around 24 hours to complete. |
| 44 |
>> |
| 45 |
>> Rgds, |
| 46 |
>> |
| 47 |
> |
| 48 |
> I've used Gentoo since 2006 and never had any reason to emerge -e. I can |
| 49 |
> also cite posts on this mailing list going back as far as 2007 (just my |
| 50 |
> local archive, mind you) that say it is unnecessary for glibc updates. |
| 51 |
> Or, to cite Volker Armin Hemmann's eloquent reply from 08-11-2007: "no" ;-) |
| 52 |
|
| 53 |
Can I detect which packages need to be rebuilt (revdep-rebuild finds |
| 54 |
nothing), other than waiting for something to fail? Or do you think |
| 55 |
the messages are a false alarm, symptoms of already-loaded programs |
| 56 |
and will go away after my next reboot? |
Archives