Circular blocks after last night's sync?
At Tue, 28 Oct 2008 18:27:24 +0100 Daniel Pielmeier <firstname.lastname@example.org> wrote:
> Robert Bridge schrieb am 28.10.2008 18:21:
>> On Tue, 28 Oct 2008 13:08:32 -0400
>> "James Homuth" <email@example.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
>>> [blocks B ] <sys-fs/e2fsprogs-1.41 (is blocking
>>> [blocks B ] sys-libs/com_err (is blocking
>>> [blocks B ] sys-libs/e2fsprogs-libs (is blocking
>>> 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.
I have obtained the sources to e2fsprogs, e2fsprogs-libs, ss, com_error
via emerge --fetchonly.
Am I correct in believing that emerge --unmerge will NOT remove the