From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How can I solve "emerge @preserved-rebuild" loop?
Date: Tue, 08 Dec 2009 06:43:11 -0600 [thread overview]
Message-ID: <4B1E49DF.9020707@gmail.com> (raw)
In-Reply-To: <200912081415.25559.alan.mckinnon@gmail.com>
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
:-) :-)
next prev parent reply other threads:[~2009-12-08 12:44 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
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 [this message]
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=4B1E49DF.9020707@gmail.com \
--to=rdalek1967@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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