public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: dhk <dhkuhl@optonline.net>
To: gentoo-user@lists.gentoo.org
Cc: Jarry <mr.jarry@gmail.com>
Subject: Re: [gentoo-user] How can I solve "emerge @preserved-rebuild" loop?
Date: Tue, 08 Dec 2009 06:06:28 -0500	[thread overview]
Message-ID: <4B1E3334.20801@optonline.net> (raw)
In-Reply-To: <200912072046.34378.alan.mckinnon@gmail.com>

Alan McKinnon wrote:
> On Monday 07 December 2009 20:10:31 Jarry wrote:
>> Hi,
>> I update my server quite frequently without any problem, but
>> today after running "emerge -uDN world" I got these messages:
>>
>> -----
>>
>> !!! existing preserved libs:
>>  >>> package: sys-libs/e2fsprogs-libs-1.41.9
>>
>>   *  - /lib64/libuuid.so
>>   *      used by /bin/mount (sys-apps/util-linux-2.16.1)
>>   *      used by /bin/umount (sys-apps/util-linux-2.16.1)
>>   *      used by /sbin/blkid (sys-apps/util-linux-2.16.1)
>>   *      used by 16 other files
>>   *  - /lib64/libblkid.so
>>   *      used by /bin/mount (sys-apps/util-linux-2.16.1)
>>   *      used by /bin/umount (sys-apps/util-linux-2.16.1)
>>   *      used by /sbin/blkid (sys-apps/util-linux-2.16.1)
>>   *      used by 8 other files
>> Use emerge @preserved-rebuild to rebuild packages using these libraries
>> -----
>>
>> So I did run "emerge @preserved-rebuild", but at the end
>> of it I got the very same messages. How can I solve this?
> 
> 
> An old version of e2fsprogs-libs provided some libs that the programs in util-
> linux linked to. Portage realised after updating e2fsprogs-libs that these 
> libs are still in use so have not deleted them until everything using them no 
> longer does. Sometimes it gets itself confused. Others report that running 
> emerge @preserved-rebuild multiple times fixes it, but I'm not so sure. It 
> think it's more a case of the various ld* utils don't do the right thing at 
> the right time - just yesterday I had b0rked @preserved-rebuild output fix 
> itself after a reboot with no extra emerging done.
> 
> Try this:
> 
> Run ldd on a few of the listed binaries using old libs, eyeball the output and 
> apply brainpower, followed by:
> 
> emerge -av1 util-linux
> emerge -avC e2fsprogs-libs ; emerge -av1 e2fsprogs-libs
> 
> revdep-rebuild won't help you here, as the binaries are not broken. It will 
> only confirm internal consistency once preserved-rebuild appears to have 
> sorted itself out.
> 
> 
I have the same problem, but the "emerge -av1 util-linux" has blocking
issues with sys-fs/e2fsprogs.  Whenever I remove sys-fs stuff I usually
regret it.

dhk



  reply	other threads:[~2009-12-08 11:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07 18:10 [gentoo-user] How can I solve "emerge @preserved-rebuild" loop? Jarry
2009-12-07 18:46 ` Alan McKinnon
2009-12-08 11:06   ` dhk [this message]
2009-12-08 11:18     ` Alan McKinnon
2009-12-08 12:08       ` Dale
2009-12-08 12:15         ` Alan McKinnon
2009-12-08 12:43           ` Dale
2009-12-08 13:39           ` Arttu V.
2009-12-07 21:17 ` Mark Knecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B1E3334.20801@optonline.net \
    --to=dhkuhl@optonline.net \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=mr.jarry@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox