From: "Andrey Vul" <andrey.vul@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Circular blocks after last night's sync?
Date: Tue, 28 Oct 2008 13:19:58 -0400 [thread overview]
Message-ID: <e38d12ff0810281019v5f4e80abg588c10d7406f30bb@mail.gmail.com> (raw)
In-Reply-To: <02e501c9391f$cf54cb60$a500a8c0@quan>
On Tue, Oct 28, 2008 at 1:08 PM, 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.
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?
next prev parent reply other threads:[~2008-10-28 17:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 17:08 [gentoo-user] Circular blocks after last night's sync? James Homuth
2008-10-28 17:19 ` Andrey Vul [this message]
2008-10-28 17:22 ` Neil Bothwick
2008-10-28 17:29 ` Daniel Pielmeier
2008-10-28 17:21 ` Robert Bridge
2008-10-28 17:27 ` Daniel Pielmeier
2008-10-28 17:40 ` Allan Gottlieb
2008-10-28 18:43 ` Daniel Pielmeier
2008-10-28 19:09 ` Allan Gottlieb
2008-10-28 19:26 ` Alan McKinnon
2008-10-28 19:38 ` Willie Wong
2008-10-28 20:00 ` Daniel Pielmeier
2008-10-28 22:09 ` Allan Gottlieb
2008-10-28 19:58 ` Daniel Pielmeier
2008-10-28 20:03 ` Eray Aslan
2008-10-28 20:15 ` Chris Walters
2008-10-28 20:21 ` Kevin O'Gorman
2008-10-28 20:26 ` Daniel Pielmeier
2008-10-28 21:51 ` Robert Bridge
2008-10-28 22:08 ` Allan Gottlieb
-- strict thread matches above, loose matches on Subject: below --
2008-10-28 20:18 Steven Susbauer
2008-10-28 21:57 ` Alan McKinnon
2008-10-28 22:05 ` James Homuth
2008-10-28 22:02 ` Alan McKinnon
2008-10-28 20:27 Steven Susbauer
2008-10-28 21:58 ` Jacques Montier
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=e38d12ff0810281019v5f4e80abg588c10d7406f30bb@mail.gmail.com \
--to=andrey.vul@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