| 1 |
Alan McKinnon wrote: |
| 2 |
> On Tuesday 08 December 2009 13:06:28 dhk wrote: |
| 3 |
> |
| 4 |
>> Alan McKinnon wrote: |
| 5 |
>> |
| 6 |
>>> On Monday 07 December 2009 20:10:31 Jarry wrote: |
| 7 |
>>> |
| 8 |
>>>> Hi, |
| 9 |
>>>> I update my server quite frequently without any problem, but |
| 10 |
>>>> today after running "emerge -uDN world" I got these messages: |
| 11 |
>>>> |
| 12 |
>>>> ----- |
| 13 |
>>>> |
| 14 |
>>>> !!! existing preserved libs: |
| 15 |
>>>> >>> package: sys-libs/e2fsprogs-libs-1.41.9 |
| 16 |
>>>> |
| 17 |
>>>> * - /lib64/libuuid.so |
| 18 |
>>>> * used by /bin/mount (sys-apps/util-linux-2.16.1) |
| 19 |
>>>> * used by /bin/umount (sys-apps/util-linux-2.16.1) |
| 20 |
>>>> * used by /sbin/blkid (sys-apps/util-linux-2.16.1) |
| 21 |
>>>> * used by 16 other files |
| 22 |
>>>> * - /lib64/libblkid.so |
| 23 |
>>>> * used by /bin/mount (sys-apps/util-linux-2.16.1) |
| 24 |
>>>> * used by /bin/umount (sys-apps/util-linux-2.16.1) |
| 25 |
>>>> * used by /sbin/blkid (sys-apps/util-linux-2.16.1) |
| 26 |
>>>> * used by 8 other files |
| 27 |
>>>> Use emerge @preserved-rebuild to rebuild packages using these libraries |
| 28 |
>>>> ----- |
| 29 |
>>>> |
| 30 |
>>>> So I did run "emerge @preserved-rebuild", but at the end |
| 31 |
>>>> of it I got the very same messages. How can I solve this? |
| 32 |
>>>> |
| 33 |
>>> An old version of e2fsprogs-libs provided some libs that the programs in |
| 34 |
>>> util- linux linked to. Portage realised after updating e2fsprogs-libs |
| 35 |
>>> that these libs are still in use so have not deleted them until |
| 36 |
>>> everything using them no longer does. Sometimes it gets itself confused. |
| 37 |
>>> Others report that running emerge @preserved-rebuild multiple times fixes |
| 38 |
>>> it, but I'm not so sure. It think it's more a case of the various ld* |
| 39 |
>>> utils don't do the right thing at the right time - just yesterday I had |
| 40 |
>>> b0rked @preserved-rebuild output fix itself after a reboot with no extra |
| 41 |
>>> emerging done. |
| 42 |
>>> |
| 43 |
>>> Try this: |
| 44 |
>>> |
| 45 |
>>> Run ldd on a few of the listed binaries using old libs, eyeball the |
| 46 |
>>> output and apply brainpower, followed by: |
| 47 |
>>> |
| 48 |
>>> emerge -av1 util-linux |
| 49 |
>>> emerge -avC e2fsprogs-libs ; emerge -av1 e2fsprogs-libs |
| 50 |
>>> |
| 51 |
>>> revdep-rebuild won't help you here, as the binaries are not broken. It |
| 52 |
>>> will only confirm internal consistency once preserved-rebuild appears to |
| 53 |
>>> have sorted itself out. |
| 54 |
>>> |
| 55 |
>> I have the same problem, but the "emerge -av1 util-linux" has blocking |
| 56 |
>> issues with sys-fs/e2fsprogs. Whenever I remove sys-fs stuff I usually |
| 57 |
>> regret it. |
| 58 |
>> |
| 59 |
> |
| 60 |
> You must remove the e2fsprogs* packages, emerge util-linux and re-emerge |
| 61 |
> e2fsprogs* |
| 62 |
> |
| 63 |
> This is safe as long as you don't log out, reboot, kill bash or do other weird |
| 64 |
> and wonderful things that require a working e2fsprogs. |
| 65 |
> |
| 66 |
> Think of it this way: |
| 67 |
> |
| 68 |
> delete your kernel image in /boot, do all kinds of stuff and put back a |
| 69 |
> different kernel image named the same as the original. Nothing will go wrong |
| 70 |
> *unless* you reboot|restart. Same with e2fprogs. |
| 71 |
> |
| 72 |
|
| 73 |
Is this the one where you need to fetch the files first, then un-emerge |
| 74 |
and emerge? I recall one being that way but not sure if it is this one. |
| 75 |
|
| 76 |
Dale |
| 77 |
|
| 78 |
:-) :-) |
Archives