AllenJB wrote:
CJoeB wrote:
Hi everyone,
I know there is a bug here, but I followed this from the bug comments:
It's not a bug. It's a valid blocker. They happen.
Yes, I know that, but I seem to remember this issue before and so, did a
google and the solution I found was in a bug report, so
CJoeB wrote:
AllenJB wrote:
CJoeB wrote:
On step 3, e2fsprogs-libs emerged fine, but at the end of the emerge of
e2fsprogs, the emerge bombed and I got a message saying that e2progs was
not merged due to file collisions.
Please post the complete message (ie. the complete list of file
On Mon, 23 Feb 2009 09:22:31 -0500, CJoeB wrote:
* Package 'sys-fs/e2fsprogs-1.40.9' NOT merged due to file collisions.
* If necessary, refer to your elog messages for the whole content of
the
* above message.
e2fsprogs-1.40 included the libraries, it was split into two packages
from
Neil Bothwick wrote:
On Mon, 23 Feb 2009 09:22:31 -0500, CJoeB wrote:
* Package 'sys-fs/e2fsprogs-1.40.9' NOT merged due to file collisions.
* If necessary, refer to your elog messages for the whole content of
the
* above message.
e2fsprogs-1.40 included the libraries, it
Hi everyone,
I know there is a bug here, but I followed this from the bug comments:
1. emerge -NuDav --fetchonly world
2. emerge -C ss com_err e2fsprogs
3. emerge -NuDav --nodeps e2fsprogs-libs e2fsprogs
4. echo sys-libs/com_err /etc/portage/package.mask
5. echo sys-libs/ss
On Sun, 22 Feb 2009 17:32:57 -0500
CJoeB colleen.bea...@gmail.com wrote:
On step 3, e2fsprogs-libs emerged fine, but at the end of the emerge of
e2fsprogs, the emerge bombed and I got a message saying that e2progs was
not merged due to file collisions.
You can use 'equery b PATH'
Mike Kazantsev wrote:
On Sun, 22 Feb 2009 17:32:57 -0500
CJoeB colleen.bea...@gmail.com wrote:
On step 3, e2fsprogs-libs emerged fine, but at the end of the emerge of
e2fsprogs, the emerge bombed and I got a message saying that e2progs was
not merged due to file collisions.
You
On Montag 23 Februar 2009, CJoeB wrote:
Mike Kazantsev wrote:
On Sun, 22 Feb 2009 17:32:57 -0500
CJoeB colleen.bea...@gmail.com wrote:
On step 3, e2fsprogs-libs emerged fine, but at the end of the emerge of
e2fsprogs, the emerge bombed and I got a message saying that e2progs was
not
CJoeB wrote:
Hi everyone,
I know there is a bug here, but I followed this from the bug comments:
It's not a bug. It's a valid blocker. They happen.
1. emerge -NuDav --fetchonly world
2. emerge -C ss com_err e2fsprogs
3. emerge -NuDav --nodeps e2fsprogs-libs e2fsprogs
Using -D (--deep)
9 matches
Mail list logo