After the move of x11-themes/qtcurve-qt4 to x11-themes/qtcurve (see bug 489978) x11-themes/qtcurve-qt4 fails to emerge on stable systems due to file collisions. This is because the version of x11-themes/qtcurve-qt4 installed before the move is now considered an installed version of x11-themes/qtcurve (which would not have been installed yet, since it's keyworded) and portage attempts to install x11-themes/qtcurve-qt4, which fails due to file conflicts with the installed "x11-themes/qtcurve" (which was actually installed using the x11-themes/qtcurve-qt4 ebuild before the move). Workaround: emerge -C x11-themes/qtcurve Then "emerge -uDN world" works. However, even then stable systems won't actually benefit from the move, and will need manual action when x11-themes/qtcurve will become stable. Reproducible: Always
This conflict is caused because no move has happened in the CVS tree: $ cvs up ; find -name 'qtcurve*.ebuild' ./qtcurve/qtcurve-1.8.17.ebuild ./qtcurve-qt4/qtcurve-qt4-1.8.14.ebuild See the three steps at: http://devmanual.gentoo.org/ebuild-writing/ebuild-maintenance/#moving-ebuilds For resolution I think all three steps need to be repeated.
My bad. I forgot the proper procedure. Should be fixed now.
