Summary: | =sys-apps/portage-2.3.6 allows installing blocked packages | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Alexis Ballier <aballier> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | esigra |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 300071 |
Description
Alexis Ballier
2017-06-09 14:39:11 UTC
It's normal for emerge to ignore this blocker if one of the packages was previously installed with the emerge --nodeps option. You can also get into a similar state if you interrupt emerge before it has an opportunity to uninstall texlive-genericrecommended-2016. This situation will resolve itself if you run emerge --depclean to remove texlive-genericrecommended-2016. (In reply to Zac Medico from comment #1) > It's normal for emerge to ignore this blocker if one of the packages was > previously installed with the emerge --nodeps option. > > You can also get into a similar state if you interrupt emerge before it has > an opportunity to uninstall texlive-genericrecommended-2016. This situation > will resolve itself if you run emerge --depclean to remove > texlive-genericrecommended-2016. Right, depclean cleaned it. It *might* be possible I installed dev-texlive/texlive-genericrecommended-2016 with --nodeps to force it a bit when doing the upgrade/dowgrade between 2016 and 2017 but dev-texlive/texlive-plaingeneric-2017 was definitely *not* merged with --nodeps and that is the one with the blocker. Isn't it possible that emerge world restores to a valid state ? It seems weird to have to depclean to reach that point. Anyway, if not possible, feel free to close as invalid. Yeah, we can certainly improve the behavior. |