1 |
On Tue, 28 Oct 2008 13:08:32 -0400 |
2 |
"James Homuth" <james@×××××××.com> wrote: |
3 |
|
4 |
> During an update attempt this afternoon, these little surprises were |
5 |
> waiting for me. I took a look at the archives, and naturally, google, |
6 |
> but all I found were lots of the same error, and no information on |
7 |
> it/what's broken. Anyone else having this particular problem? The |
8 |
> block errors are below. |
9 |
> |
10 |
> [blocks B ] sys-libs/ss (is blocking |
11 |
> sys-libs/e2fsprogs-libs-1.41.2) |
12 |
> |
13 |
> [blocks B ] <sys-fs/e2fsprogs-1.41 (is blocking |
14 |
> sys-libs/e2fsprogs-libs-1.41.2) |
15 |
> |
16 |
> [blocks B ] sys-libs/com_err (is blocking |
17 |
> sys-libs/e2fsprogs-libs-1.41.2) |
18 |
> |
19 |
> [blocks B ] sys-libs/e2fsprogs-libs (is blocking |
20 |
> sys-libs/ss-1.40.9, |
21 |
> sys-libs/com_err-1.40.9) |
22 |
> |
23 |
> This was during an emerge --update world. |
24 |
> |
25 |
> |
26 |
|
27 |
emerge -C e2fsprogs, ss, com_err && emerge -1 e2fsprogs |
28 |
|
29 |
e2fsprogs is being restructured, which is causing the problem. |