FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 12-07-2009, 05:10 PM
Jarry
 
Default How can I solve "emerge @preserved-rebuild" loop?

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?

Jarry

--
__________________________________________________ _____________
This mailbox accepts e-mails only from selected mailing-lists!
Everything else is considered to be spam and therefore deleted.
 
Old 12-07-2009, 05:46 PM
Alan McKinnon
 
Default How can I solve "emerge @preserved-rebuild" loop?

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.


--
alan dot mckinnon at gmail dot com
 
Old 12-07-2009, 08:17 PM
Mark Knecht
 
Default How can I solve "emerge @preserved-rebuild" loop?

On Mon, Dec 7, 2009 at 10:10 AM, Jarry <mr.jarry@gmail.com> 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?
>
> Jarry

I saw this on every machine I updated recently. I did

emerge -C e2fsprogs-libs

and then

emerge -DuN world
revdep-rebuild -i

HTH,
Mark
 
Old 12-08-2009, 10:06 AM
dhk
 
Default How can I solve "emerge @preserved-rebuild" loop?

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
 
Old 12-08-2009, 10:18 AM
Alan McKinnon
 
Default How can I solve "emerge @preserved-rebuild" loop?

On Tuesday 08 December 2009 13:06:28 dhk wrote:
> 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.

You must remove the e2fsprogs* packages, emerge util-linux and re-emerge
e2fsprogs*

This is safe as long as you don't log out, reboot, kill bash or do other weird
and wonderful things that require a working e2fsprogs.

Think of it this way:

delete your kernel image in /boot, do all kinds of stuff and put back a
different kernel image named the same as the original. Nothing will go wrong
*unless* you reboot|restart. Same with e2fprogs.

--
alan dot mckinnon at gmail dot com
 
Old 12-08-2009, 11:08 AM
Dale
 
Default How can I solve "emerge @preserved-rebuild" loop?

Alan McKinnon wrote:

On Tuesday 08 December 2009 13:06:28 dhk wrote:


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.



You must remove the e2fsprogs* packages, emerge util-linux and re-emerge
e2fsprogs*


This is safe as long as you don't log out, reboot, kill bash or do other weird
and wonderful things that require a working e2fsprogs.

Think of it this way:


delete your kernel image in /boot, do all kinds of stuff and put back a
different kernel image named the same as the original. Nothing will go wrong
*unless* you reboot|restart. Same with e2fprogs.



Is this the one where you need to fetch the files first, then un-emerge
and emerge? I recall one being that way but not sure if it is this one.


Dale

:-) :-)
 
Old 12-08-2009, 11:15 AM
Alan McKinnon
 
Default How can I solve "emerge @preserved-rebuild" loop?

On Tuesday 08 December 2009 14:08:47 Dale wrote:
> >> 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.
> >>
> >
> > You must remove the e2fsprogs* packages, emerge util-linux and re-emerge
> > e2fsprogs*
> >
> > This is safe as long as you don't log out, reboot, kill bash or do other
> > weird and wonderful things that require a working e2fsprogs.
> >
> > Think of it this way:
> >
> > delete your kernel image in /boot, do all kinds of stuff and put back a
> > different kernel image named the same as the original. Nothing will go
> > wrong unless you reboot|restart. Same with e2fprogs.
> >
>
> Is this the one where you need to fetch the files first, then un-emerge
> and emerge? I recall one being that way but not sure if it is this one.

No, that was a while ago. This is simply a conflict involving e2fsprogs-libs

Doesn't remove wget

--
alan dot mckinnon at gmail dot com
 
Old 12-08-2009, 11:43 AM
Dale
 
Default How can I solve "emerge @preserved-rebuild" loop?

Alan McKinnon wrote:

On Tuesday 08 December 2009 14:08:47 Dale wrote:


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.


You must remove the e2fsprogs* packages, emerge util-linux and re-emerge
e2fsprogs*


This is safe as long as you don't log out, reboot, kill bash or do other
weird and wonderful things that require a working e2fsprogs.

Think of it this way:


delete your kernel image in /boot, do all kinds of stuff and put back a
different kernel image named the same as the original. Nothing will go

wrong unless you reboot|restart. Same with e2fprogs.


Is this the one where you need to fetch the files first, then un-emerge
and emerge? I recall one being that way but not sure if it is this one.



No, that was a while ago. This is simply a conflict involving e2fsprogs-libs

Doesn't remove wget



Ah, that was it. I was wondering why a file system package would
interfere with portage downloading.


Thanks.

Dale

:-) :-)
 
Old 12-08-2009, 12:39 PM
"Arttu V."
 
Default How can I solve "emerge @preserved-rebuild" loop?

On 12/8/09, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On Tuesday 08 December 2009 14:08:47 Dale wrote:
>> Is this the one where you need to fetch the files first, then un-emerge
>> and emerge? I recall one being that way but not sure if it is this one.
>
> No, that was a while ago. This is simply a conflict involving e2fsprogs-libs
>
> Doesn't remove wget

Well, I think Mr. Dalek is entirely correct, this is the same problem.
e2fsprogs-libs nowadays contains the com_err library, missing of which
was (IIRC) causing problems with, e.g., wget in the olden days.

Anyone know how the problem was actually fixed? Did they start linking
wget statically? Or are we relying on portage's new tricks, like
background downloading, which hides 99% of the problem under the rug,
as you will very likely have the sources already downloaded during
previous compiles?

--
Arttu V.
 

Thread Tools




All times are GMT. The time now is 02:45 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org