On Tue, Oct 28, 2008 at 1:08 PM, James Homuth <[EMAIL PROTECTED]> 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. Unmerge the old e2fsprogs and emerge the new programs and libs. IIRC this is not new. I had this happen a few months ago.
-- Andrey Vul A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?
