[gentoo-user] Issue with e2fsprogs

[gentoo-user] Issue with e2fsprogs

[CJoeB]

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" >>/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


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.

I have no idea what to do now.  I googled, but didn't see anything
relevant.  Any help would be appreciated.

Regards,

Colleen


-- 

Registered Linux User #411143 with the Linux Counter, http://counter.li.org

Re: [gentoo-user] Issue with e2fsprogs

[Mike Kazantsev]

[-- Attachment #1: Type: text/plain, Size: 527 bytes --]

On Sun, 22 Feb 2009 17:32:57 -0500
CJoeB <colleen.beamer@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>' (app-portage/gentoolkit) to determine
which package owns the offending files, then either unmerge it or just
set "FEATURES=-collision-protect" to force installation despite
collisions.

-- 
Mike Kazantsev // fraggod.net

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Issue with e2fsprogs

[CJoeB]

Mike Kazantsev wrote:
> On Sun, 22 Feb 2009 17:32:57 -0500
> CJoeB <colleen.beamer@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>' (app-portage/gentoolkit) to determine
> which package owns the offending files, then either unmerge it or just
> set "FEATURES=-collision-protect" to force installation despite
> collisions.
>
>   
The "FEATURES=collision-protect" didn't work.  I assume I entered the
command correctly because protage didn't give me grief.

I have no idea how to determine what is the offending package because I
don't know what the path is where the offending package is.  This is the
message I get at the end when emerge bombs:

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.

I've looked at emerge.log, but nothing sheds any light.  And if this
isn't where I'm supposed to look, I'm not sure where I should be looking.

Regards,

Colleen

-- 

Registered Linux User #411143 with the Linux Counter, http://counter.li.org

Re: [gentoo-user] Issue with e2fsprogs

[Volker Armin Hemmann]

On Montag 23 Februar 2009, CJoeB wrote:
> Mike Kazantsev wrote:
> > On Sun, 22 Feb 2009 17:32:57 -0500
> >
> > CJoeB <colleen.beamer@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>' (app-portage/gentoolkit) to determine
> > which package owns the offending files, then either unmerge it or just
> > set "FEATURES=-collision-protect" to force installation despite
> > collisions.
>
> The "FEATURES=collision-protect" didn't work.  I assume I entered the
> command correctly because protage didn't give me grief.
>
> I have no idea how to determine what is the offending package because I
> don't know what the path is where the offending package is.  This is the
> message I get at the end when emerge bombs:
>

usually the collision is shown a little bit above that. Just scroll back.

Ands you have to set -collision-protect

Re: [gentoo-user] Issue with e2fsprogs

[AllenJB]

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

Re: [gentoo-user] Issue with e2fsprogs

[CJoeB]

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

Re: [gentoo-user] Issue with e2fsprogs

[AllenJB]

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
>> 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.  

Note the version numbers here - you're trying to use e2fsprogs-1.40.9 
with e2fsprogs-libs-1.41.3 - these packages should both be at the same 
version.

Please check package.keywords and package.mask for any entries relating 
to e2fsprogs. I'm surprised portage even attempted to merge these 
without a fight.

AllenJB

> 
> Regards,
> 
> Colleen
> 

Re: [gentoo-user] Issue with e2fsprogs

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 646 bytes --]

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 1.41. That's why you are seeing collisions, because both e2fsprogs
and e2fsprogs-libs are want to install the libs. Unless you have some
strange masking in /etc/portage, unmerging all e2fsprogs* packages
followed by "emerge system" should get things straight.


-- 
Neil Bothwick

Despite the cost of living it remains popular.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Issue with e2fsprogs

[CJoeB]

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 was split into two packages
> from 1.41. That's why you are seeing collisions, because both e2fsprogs
> and e2fsprogs-libs are want to install the libs. Unless you have some
> strange masking in /etc/portage, unmerging all e2fsprogs* packages
> followed by "emerge system" should get things straight.
>   

Thanks everyone!  :-)  Problem is solved.  And it was basically my
fault.  For some reason, I had masked ">sys-fs/e2fsprogs-1.41".  Thanks
AllenJB for "whacking me on the head" and making me realize this!  :-) 
I got so caught up with the fact that I had removed e2fsprogs and was
getting collisions and was afraid I wouldn't be able to reboot my system
that I never thought to look.  I don't usually have too many problems
with Gentoo and updating my system, but when I do run into a snag, it's
always a lesson learned that I won't forget again.  Thanks again everyone!

Regards,

Colleen


-- 

Registered Linux User #411143 with the Linux Counter, http://counter.li.org