* Messages for package app-portage/eix-0.28.5: * * Installation of a directory is blocked by a file: * '/etc/eixrc' * This file will be renamed to a different name: * '/etc/eixrc.backup.0000' * Is this a problem
This is intended behaviour: In early versions /etc/eixrc was a file, now it is a directory. So your old file must be renamed to obtain a directory which is what portage does autmatically during merging eix to / If you had previously modified /etc/eixrc and want to keep the modifications, just rename /etc/eixrc.backup.0000 to e.g. /etc/eixrc/01-my-old-eixrc. If you had never modified /etc/eixrc you can delete /etc/eixrc.backup.0000 instead Please leave this bug open until >=eix-0.25.5 is stable for a while so that users upgrading and getting confused by the portage message can see this bug.
I just hit that bug with paludis and unfortunately, paludis fails to install which is intended according to the paludis guys and the spec: "Ebuilds must not attempt to merge a directory on top of any existing file that is not either a directory or a symlink to a directory." Reference: http://paludis.exherbo.org/trac/ticket/1285 So, this is in fact a problem :-)
It is not reasonable in an ebuild to mess around with user configuration files and inventing temporary filenames. For things like this package managers exist: It would be just crazy to include such code in every future eix ebuild (and probaly into several other ebuilds) just because one upgrade might need it. If the paludis guys refuse to adapt a reasonable solution, I suggest to live with the fact that you have to manually delete/rename the prevous /etc/eixrc for one upgrade of eix.
(In reply to Martin Väth from comment #3) > It is not reasonable in an ebuild to mess around with user configuration > files and inventing temporary filenames. For things like this package > managers exist: > It would be just crazy to include such code in every future eix ebuild (and > probaly into several other ebuilds) just because one upgrade might need it. > > If the paludis guys refuse to adapt a reasonable solution, I suggest to live > with the fact that you have to manually delete/rename the prevous /etc/eixrc > for one upgrade of eix. We *could* hack around this issue in pkg_preinst, but I agree with Martin -- the solution here is really to require a manual move of the file, due to it being in a CONFIG_PROTECT area. If it was elsewhere, then it would be a different story..
