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 I assumed it was still a bug. Sorry. > >> >> 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. I didn't do this. I never got beyond step 3. > > > 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 No sure why I add mit-krb5, I don't think it was installed before. Regardless, I added the line to my package.keywords file, but it still wants to pull in mit-krb5-1.6.3-r4. After unmerge ss and com_err and e2fsprogs (which I had already done, e2fsprogs-libs emerge fine, but I am still getting collisions with e2fsprogs, even if I use the --nodeps switch. > > > You should also try to make sure you're using the latest version of > portage (>=2.1.6) as this has blocker handling functionality. > I do. I was updating world and portage was the first thing it pulled in. >> >> >> 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). This is what displayed at the end of the attempt to emerge e2fsprogs: Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * sys-libs/e2fsprogs-libs-1.41.3-r1 * /lib/libblkid.so * /lib/libblkid.so.1 * /lib/libblkid.so.1.0 * /lib/libuuid.so * /lib/libuuid.so.1 * /lib/libuuid.so.1.2 * /usr/include/blkid/blkid.h * /usr/include/blkid/blkid_types.h * /usr/include/uuid/uuid.h * /usr/lib/libblkid.a * /usr/lib/libblkid.so * /usr/lib/libuuid.a * /usr/lib/libuuid.so * /usr/lib/pkgconfig/blkid.pc * /usr/lib/pkgconfig/uuid.pc * /usr/share/info/libext2fs.info.bz2 * /usr/share/man/man3/libblkid.3.bz2 * /usr/share/man/man3/uuid.3.bz2 * /usr/share/man/man3/uuid_clear.3.bz2 * /usr/share/man/man3/uuid_compare.3.bz2 * /usr/share/man/man3/uuid_copy.3.bz2 * /usr/share/man/man3/uuid_generate.3.bz2 * /usr/share/man/man3/uuid_generate_random.3.bz2 * /usr/share/man/man3/uuid_generate_time.3.bz2 * /usr/share/man/man3/uuid_is_null.3.bz2 * /usr/share/man/man3/uuid_parse.3.bz2 * /usr/share/man/man3/uuid_time.3.bz2 * /usr/share/man/man3/uuid_unparse.3.bz2 * * 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. Regards, Colleen -- Registered Linux User #411143 with the Linux Counter, http://counter.li.org
