Re: [gentoo-user] Circular blocks after last night's sync?

[Allan Gottlieb <gottlieb@nyu.edu>]

At Tue, 28 Oct 2008 21:51:38 +0000 Robert Bridge <robert@robbieab.com> wrote:

> On Tue, 28 Oct 2008 13:21:28 -0700
> "Kevin O'Gorman" <kogorman@gmail.com> wrote:
>
>> On Tue, Oct 28, 2008 at 10:27 AM, Daniel Pielmeier
>> <daniel.pielmeier@googlemail.com> wrote:
>> > Robert Bridge schrieb am 28.10.2008 18:21:
>> >> On Tue, 28 Oct 2008 13:08:32 -0400
>> >> "James Homuth" <james@the-jdh.com> wrote:
>> >>
>> >>> During an update attempt this afternoon, these little surprises
>> >>> were waiting for me. I took a look at the archives, and
>> >>> naturally, google, but all I found were lots of the same error,
>> >>> and no information on it/what's broken. Anyone else having this
>> >>> particular problem? The block errors are below.
>> >>>
>> >>> [blocks B     ] sys-libs/ss (is blocking
>> >>> sys-libs/e2fsprogs-libs-1.41.2)
>> >>>
>> >>> [blocks B     ] <sys-fs/e2fsprogs-1.41 (is blocking
>> >>> sys-libs/e2fsprogs-libs-1.41.2)
>> >>>
>> >>> [blocks B     ] sys-libs/com_err (is blocking
>> >>> sys-libs/e2fsprogs-libs-1.41.2)
>> >>>
>> >>> [blocks B     ] sys-libs/e2fsprogs-libs (is blocking
>> >>> sys-libs/ss-1.40.9,
>> >>> sys-libs/com_err-1.40.9)
>> >>>
>> >>> This was during an emerge --update world.
>> >>>
>> >>>
>> >>
>> >> emerge -C e2fsprogs, ss, com_err && emerge -1 e2fsprogs
>> >>
>> >> e2fsprogs is being restructured, which is causing the problem.
>> >
>> > If you go the route of uninstalling things first, make sure that you
>> > have the sources prepared as wget might not work for some use flag
>> > combinations when you remove e2fsprogs, ss, com_err in advance.
>> 
>> Sadly, I did not read this until these were all unmerged, and wget is
>> truly broken.
>> 
>> Happily, I do run with buildpkg on all the time, but an this the
>> first time I've really needed them.  Getting back to a running system
>> was pretty easy.
>> 
>> However, this does not really solve the problem.  What's a safe way to
>> do this emerge?
>
> Sorry, my systems came through this a while ago, with the ~ portage, so
> I never really noticed.
>
> For a safe solution:
>
> $ emerge -uDf world                 # fetch the code
> $ emerge -C e2fsprogs, ss, com_err  # clear the blockers
> $ emerge -uD world                  # fix the system.

This didn't work for me (but it does look safe).  I
needed to first add mit-krb5 to package.keywords

This was a real mess.
allan