>>> Completed installing gimp-print-4.2.7 into /var/tmp/portage/gimp-print-4.2.7/image/ * checking 385 files for package collisions existing file /usr/share/foomatic/db/source/driver/gimp-print.xml is not owned by this package * spent 0.128607034683 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 # qfile -v /usr/share/foomatic/db/source/driver/gimp-print.xml net-print/foomatic-db-20050910 (/usr/share/foomatic/db/source/driver/gimp-print.xml)
also happens with gimp-print-5.0_rc?
>>> Completed installing gimp-print-5.0.0_rc1 into /var/tmp/portage/gimp-print-5.0.0_rc1/image/ * checking 497 files for package collisions existing file /usr/lib64/gimp/2.0/plug-ins/print is not owned by this package * spent 0.173015832901 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 # qfile -v /usr/lib64/gimp/2.0/plug-ins/print media-gfx/gimp-2.2.10 (/usr/lib64/gimp/2.0/plug-ins/print) maybe this is why gimp wants gimp-print-4.2.7 and not 5.0.
allanonjl: Can you please have a look at this? Any Idea why they are colliding and why gimp needs the older version?
gimp needs =gimp-print-4.2* since the plug-in has yet to be ported to the new API of gimp-print-5.0.0 (which is still not final).
I added a line to remove the file in the old gimp-print release: use foomaticdb && rm -f ${D}/usr/share/foomatic/db/source/driver/gimp-print.xml And a notice to the newer gimp-print-5.0.0_rc2 that gimp has to be emerged without the "gimpprint" useflag set.
