They should probably have a depend block on each other, to prevent this: --- ^[[31;01m * ^[[39;49;00mThis package will overwrite one or more files that may belong to other ^[[31;01m * ^[[39;49;00mpackages (see list below). You can use a command such as `portageq ^[[31;01m * ^[[39;49;00mowners / <filename>` to identify the installed package that owns a ^[[31;01m * ^[[39;49;00mfile. If portageq reports that only one package owns a file then do ^[[31;01m * ^[[39;49;00mNOT file a bug report. A bug report is only useful if it identifies at ^[[31;01m * ^[[39;49;00mleast two or more packages that are known to install the same file(s). ^[[31;01m * ^[[39;49;00mIf a collision occurs and you can not explain where the file came from ^[[31;01m * ^[[39;49;00mthen you should simply ignore the collision since there is not enough ^[[31;01m * ^[[39;49;00minformation to determine if a real problem exists. Please do NOT file ^[[31;01m * ^[[39;49;00ma bug report at http://bugs.gentoo.org unless you report exactly which ^[[31;01m * ^[[39;49;00mtwo packages install the same file(s). Once again, please do NOT file ^[[31;01m * ^[[39;49;00ma bug report unless you have completely understood the above message. ^[[31;01m * ^[[39;49;00m ^[[31;01m * ^[[39;49;00mDetected file collision(s): ^[[31;01m * ^[[39;49;00m ^[[31;01m * ^[[39;49;00m /usr/bin/oxygen-gtk-demo ^[[31;01m * ^[[39;49;00m /usr/bin/oxygen-gtk-deco ^[[31;01m * ^[[39;49;00m /usr/lib64/gtk-2.0/2.10.0/engines/liboxygen-gtk.so ^[[31;01m * ^[[39;49;00m ^[[31;01m * ^[[39;49;00mSearching all installed packages for file collisions... ^[[31;01m * ^[[39;49;00m ^[[31;01m * ^[[39;49;00mPress Ctrl-C to Stop ^[[31;01m * ^[[39;49;00m ^[[31;01m * ^[[39;49;00mx11-themes/oxygen-gtk-1.1.6 ^[[31;01m * ^[[39;49;00m /usr/bin/oxygen-gtk-deco ^[[31;01m * ^[[39;49;00m /usr/bin/oxygen-gtk-demo ^[[31;01m * ^[[39;49;00m /usr/lib64/gtk-2.0/2.10.0/engines/liboxygen-gtk.so ^[[31;01m * ^[[39;49;00m ^[[31;01m * ^[[39;49;00mPackage 'x11-themes/oxygen-gtk-1.2.0-r1' NOT merged due to file ^[[31;01m * ^[[39;49;00mcollisions. If necessary, refer to your elog messages for the whole ^[[31;01m * ^[[39;49;00mcontent of the above message. --- Reproducible: Always
Fixed. Sync in some hours and try again.
