Summary: | gmime: file collision with sharutils in /usr/bin/uuencode and /usr/bin/uudecode | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexander Skwar <askwar> |
Component: | Current packages | Assignee: | Net-Mail Packages <net-mail+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 83994 | ||
Attachments: |
gmime r3 ebuild
Diff to 2.1.9-r2.ebuild |
Description
Alexander Skwar
2004-11-07 16:21:28 UTC
Bad subject of the bug. Good catch, Alexander, I didn't notice this. I was puzzled on how to solve this, but then I decided to do the same thing Mandrake did - install these two files with "gmime-" prefix. 2.1.9-r1 is now in CVS portage, should be hitting mirrors in few hours. Thanks! Bug reopened. making executable: /usr/lib/libgmime-2.0.so.2.1.9 >>> Completed installing gmime-2.1.9-r1 into /var/tmp/portage/gmime-2.1.9-r1/image/ * checking 141 files for package collisions existing file /usr/bin/uudecode is not owned by this package existing file /usr/bin/uuencode is not owned by this package * spent 0.0920889377594 seconds checking for file collisions * This package is blocked because it wants to overwrite * files belonging to other packages (see messages above). * If you have no clue what this is all about report it * as a bug for this package on http://bugs.gentoo.org package dev-libs/gmime-2.1.9-r1 NOT merged No package files given... Grabbing a set. [15:44:45 alexander@server:~/tmp] $ epm -qf /usr/lib/libgmime-2.0.so.2.1.9 file /usr/lib/libgmime-2.0.so.2.1.9: No such file or directory [15:46:49 alexander@server:~/tmp] $ epm -qf /usr/bin/uudecode /usr/bin/uuencode sharutils-4.2.1-r10 sharutils-4.2.1-r10 What package are those two files owned by? Ok, I really don't know how did this happen, maybe portage changed behavior in some way, but now (2.1.9-r2), it should be fixed. Thanks for reporting again! Uhm?
Still broken:
making executable: /usr/lib/libgmime-2.0.so.2.1.9
>>> Completed installing gmime-2.1.9-r2 into /var/tmp/portage/gmime-2.1.9-r2/image/
* checking 141 files for package collisions
existing file /usr/bin/uudecode is not owned by this package
existing file /usr/bin/uuencode is not owned by this package
That's with 2.1.9-r2.
uu{en,de}code is from sharutils.
Created attachment 59516 [details]
gmime r3 ebuild
In this ebuild, I copied over the solution found in the .14 ebuild. This now
works - no more any collisions.
I'm not TOO sure, if it's correct, though. Don't know how "make install" is
actually called. Please verify.
Created attachment 59517 [details, diff] Diff to 2.1.9-r2.ebuild That's the diff to the previous -r2 ebuild. Applying it will result in an ebuild just like the one from attachment 59516 [details] Ok, what I didn't realize was that portage checks for file collision _before_ pkg_preinst() is called. Accidentally, I have turned collision-protect feature off last night, because of one package or another, thus -r2 went just fine - the files got renamed properly and installed all right. Anyway, -r3, based on your patch is now in portage. Thanks. |