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) and --nodeps is contradictory. In addition, you just
unmerged e2fsprogs, which means using --update (-u) now makes very
little sense. -N (--newuse) also makes very little sense (in addition to
the fact that it implies --update).
4. echo "sys-libs/com_err" >>/etc/portage/package.mask
5. echo "sys-libs/ss" >>/etc/portage/package.mask
6. echo "sys-libs/com_err-1.40.11" >>/etc/portage/profile/package.provided
7. echo "sys-libs/ss-1.40.11" >>/etc/portage/profile/package.provided
You should not add these packages to package.provided. There should be
no need for this. I can see this causing issues.
From the forums:
http://forums.gentoo.org/viewtopic-t-712898.html
# echo "<=app-crypt/mit-krb5-1.6.3-r2" >> /etc/portage/package.keywords
# emerge --sync
# emerge -f e2fsprogs e2fsprogs-libs
# emerge --unmerge ss com_err e2fsprogs
# emerge -av e2fsprogs e2fsprogs-libs
You should also try to make sure you're using the latest version of
portage (>=2.1.6) as this has blocker handling functionality.
This worked from a few people, so I felt safe doing it.
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 collisions).
I have no idea what to do now. I googled, but didn't see anything
relevant. Any help would be appreciated.
Regards,
Colleen
AllenJB
