| 1 |
On 2019.03.10 22:50, tuxic@××××××.de wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> I've got this this morning: |
| 5 |
> strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment -R |
| 6 |
> .GCC.command.line -R .note.gnu.gold-version |
| 7 |
> /usr/lib64/libmxml.so.1.6 |
| 8 |
> * checking 9 files for package collisions |
| 9 |
> * This package will overwrite one or more files that may belong to |
| 10 |
> other |
| 11 |
> * packages (see list below). You can use a command such as `portageq |
| 12 |
> * owners / <filename>` to identify the installed package that owns a |
| 13 |
> * file. If portageq reports that only one package owns a file then do |
| 14 |
> * NOT file a bug report. A bug report is only useful if it |
| 15 |
> identifies at |
| 16 |
> * least two or more packages that are known to install the same |
| 17 |
> file(s). |
| 18 |
> * If a collision occurs and you can not explain where the file came |
| 19 |
> from |
| 20 |
> * then you should simply ignore the collision since there is not |
| 21 |
> enough |
| 22 |
> * information to determine if a real problem exists. Please do NOT |
| 23 |
> file |
| 24 |
> * a bug report at https://bugs.gentoo.org/ unless you report exactly |
| 25 |
> * which two packages install the same file(s). See |
| 26 |
> * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on |
| 27 |
> how |
| 28 |
> * to solve the problem. And once again, please do NOT file a bug |
| 29 |
> report |
| 30 |
> * unless you have completely understood the above message. |
| 31 |
> * |
| 32 |
> * Detected file collision(s): |
| 33 |
> * |
| 34 |
> * /usr/share/man/man3/mxml.3.bz2 |
| 35 |
> * /usr/include/mxml.h |
| 36 |
> * /usr/lib64/libmxml.so.1.6 |
| 37 |
> * /usr/lib64/pkgconfig/mxml.pc |
| 38 |
> * /usr/lib64/libmxml.so.1 |
| 39 |
> * /usr/lib64/libmxml.so |
| 40 |
> * |
| 41 |
> * Searching all installed packages for file collisions... |
| 42 |
> * |
| 43 |
> * Press Ctrl-C to Stop |
| 44 |
> * |
| 45 |
> * dev-libs/mxml-2.12:0::gentoo |
| 46 |
> * /usr/include/mxml.h |
| 47 |
> * /usr/lib64/libmxml.so |
| 48 |
> * /usr/lib64/libmxml.so.1 |
| 49 |
> * /usr/lib64/libmxml.so.1.6 |
| 50 |
> * /usr/lib64/pkgconfig/mxml.pc |
| 51 |
> * /usr/share/man/man3/mxml.3.bz2 |
| 52 |
> * |
| 53 |
> * Package 'dev-libs/mxml-3.0' NOT merged due to file collisions. If |
| 54 |
> * necessary, refer to your elog messages for the whole content of the |
| 55 |
> * above message. |
| 56 |
> * |
| 57 |
> * The following package has failed to build, install, or execute |
| 58 |
> postinst: |
| 59 |
> * |
| 60 |
> * (dev-libs/mxml-3.0:1/6::gentoo, ebuild scheduled for merge), Log |
| 61 |
> file: |
| 62 |
> * '/var/tmp/portage/dev-libs/mxml-3.0/temp/build.log' |
| 63 |
> |
| 64 |
> |
| 65 |
> Is it ok tp rm |
| 66 |
> /usr/share/man/man3/mxml.3.bz2 |
| 67 |
> /usr/include/mxml.h |
| 68 |
> /usr/lib64/libmxml.so.1.6 |
| 69 |
> /usr/lib64/pkgconfig/mxml.pc |
| 70 |
> /usr/lib64/libmxml.so.1 |
| 71 |
> /usr/lib64/libmxml.so |
| 72 |
> |
| 73 |
> manually prior to reemergeing? |
| 74 |
Hello Meino, |
| 75 |
|
| 76 |
I'd file a bug, as it looks like 2.12 in slot 0 and 3.0 in slot 1 both |
| 77 |
install some of the same files. It looks like version 3.0 was just |
| 78 |
added to the tree, so either it doesn't need to be in a separate slot, |
| 79 |
or else those files need renaming. |
| 80 |
|
| 81 |
Deleting and re-emerging would probably work, but if you later remove |
| 82 |
one of the versions, those files will also be removed, and the |
| 83 |
remaining version will probably fail due to the missing .so file(s). |
| 84 |
|
| 85 |
Jack |
Archives