net-print/foomatic-db-4.0.20120117 reports file collisions: * Detected file collision(s): * * /usr/share/foomatic/xmlschema/option.xsd * /usr/share/foomatic/xmlschema/driver.xsd * /usr/share/foomatic/xmlschema/printer.xsd * /usr/share/foomatic/xmlschema/types.xsd * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * net-print/foomatic-db-ppds-4.0.20120117 * /usr/share/foomatic/xmlschema/driver.xsd * /usr/share/foomatic/xmlschema/option.xsd * /usr/share/foomatic/xmlschema/printer.xsd * /usr/share/foomatic/xmlschema/types.xsd * * Package 'net-print/foomatic-db-4.0.20120117' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message. I ran: equery d foomatic-db-ppds to determine if this package was needed any longer. No dependent packages reported. I ran: emerge --depclean net-print/foomatic-db-ppds Package was removed cleanly. I ran: emerge foomatic-db Success!! I'm guessing that foomatic-db-pdds has been subsumed into foomatic-db and installs which still have foomatic-db-pdds should report this as a 'blocker' during 'emerge' of 'foomatic-db'. Of course, that's just a guess. I'm not a programmer. I know nothing.
I get the same problem. This situation (whatever it is exactly) should be shomehow reflected in [R]DEPEND, i.e. blockers or something. Doesn't look to me like the PPDs have moved to net-print/foomatic-db (so foomatic-db-ppds is not obsolete). I think the collision needs to be resolved, i.e. those four XSDs need need to be removed from one package.
*** Bug 399355 has been marked as a duplicate of this bug. ***
Fixed in foomatic-db-ppds-4.0.20120117-r1
