Consider you have some package installed. Later it was masked by package.mask file, then if you try to update your system with "emerge -NDu world" portage will tell you that package was masked by package.mask. But if it was masked by keyword(e.g. marked unstable) or LICENSE entry was added or ebuild of that particular installed version was removed - portage will tell nothing.
However I think portage should warn user about such situations.
(In reply to comment #0)
> But if it was masked by
> keyword(e.g. marked unstable)
We have a long history of users temporarily overriding ACCEPT_KEYWORDS via the environment in order to install just a few packages with unstable keywords. This creates a conflict with your desire to have a warning message, since it would be considered noise by users who had temporarily overridden ACCEPT_KEYWORDS as described above.
The situation in this are should improve after portage-2.1.10 has been stabilized, since the emerge --autounmask option is enabled by default in this release, so users will no longer feel a need to do temporary overrides of ACCEPT_KEYWORDS.
We already try to handle this kind of issue as well as possible by during dependency resolution. As an example, for bug 350285 we fixed --depclean to remove newer slots masked by keywords:
> or LICENSE entry was added
Since bug 288083, we have a warning for missed updates due to license masks:
> or ebuild of that
> particular installed version was removed - portage will tell nothing.
The problem with this is that we'd like for users to be able to install from binary packages, without the need to have the ebuilds present, and without receiving irrelevant warnings when the ebuilds are not present. I suppose we can add a option to trigger a warning like this if it's desired. Then you could add such an option to EMERGE_DEFAULT_OPTS if it suits you.
> However I think portage should warn user about such situations.
As it is, you should be able to trigger all relevant warnings by running `emerge -pe world`.
Seems like this issue is more complicated than I thought. Thanks for detailed answer!
(In reply to comment #1)
> I suppose we
> can add a option to trigger a warning like this if it's desired. Then you could
> add such an option to EMERGE_DEFAULT_OPTS if it suits you.
Sounds reasonable to me. I'd like to see this happened.
> As it is, you should be able to trigger all relevant warnings by running
> `emerge -pe world`.
I'll use this for now. Thanks!
*** Bug 832979 has been marked as a duplicate of this bug. ***