Bug 426476 – move and slotmove commands should not be applied if new metadata would be invalid in EAPI of installed ebuild

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Arfrever Frehtes Taifersar Arahesis 2012-07-13 19:03:21 UTC]

move commands should not be applied if new ${CATEGORY} or ${PN} would be invalid in EAPI of installed ebuild.
slotmove commands should not be applied if new ${SLOT} would be invalid in EAPI of installed ebuild.

In these situations, Portage should print warnings telling users to upgrade/reinstall/uninstall given packages.

[Comment 1 Arfrever Frehtes Taifersar Arahesis 2012-07-13 19:21:37 UTC]

Usually ebuild with original ${CATEGORY}/${PN} or ${SLOT} will no longer be available, so Portage should only suggest manual uninstallation and later potential installation of new ebuild.

[Comment 2 Zac Medico 2012-07-13 23:34:47 UTC]

Here's a really minimal fix, just to prevent breakage from occurring:

http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=dde6df65ecbc522dc23cb8d24be3e4dd52657da8

[Comment 3 Zac Medico 2012-07-17 23:57:16 UTC]

(In reply to comment #0)
> move commands should not be applied if new ${CATEGORY} or ${PN} would be
> invalid in EAPI of installed ebuild.

This is fixed in git:

http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=2df06cb95c1f97a470034bf2be73869256633685

> In these situations, Portage should print warnings telling users to
> upgrade/reinstall/uninstall given packages.

I didn't add any warnings yet. I guess if there's a problem then it will show as a SLOT conflict, blocker, or just a plain unsatisfied dependency, which shouldn't be too hard for users to interpret.

[Comment 4 Zac Medico 2012-07-18 00:30:07 UTC]

This is fixed in 2.1.11.8 and 2.2.0_alpha119.