The fetchmail-22.214.171.124 ebuild explicity RDEPENDS on app-crypt/mit-krb5 rather
than virtual/krb5. Since I'm using heimdal I have masked all mit-krb5 versions
to avoid it getting merged by accident. Thus I'm getting 'All ebuilds that
could satisfy "app-crypt/mit-krb5" have been masked.' when I am doing a world
update. (I don't think that fetchmail will build against heimdal but that may
be another issue.)
(In reply to comment #0)
>(I don't think that fetchmail will build against heimdal but that may
> be another issue.)
No, fetchmail won't build against heimdal (see Bug 42534) so this bug is invalid.
I disagree that it is an invalid bug, if I already have heimdal installed then
this explicit use of mit-krb5 will cause a conflict, if I remove my mit-krb5
package mask and my /etc/portage/profile/virtuals choice of heimdal then:
# emerge --deep -p -u fetchmail
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[blocks B ] app-crypt/heimdal (is blocking app-crypt/mit-krb5-1.4.1-r2)
[ebuild N ] app-crypt/mit-krb5-1.4.1-r2
If heimdal is installed then the ebuild should disable kerberos support.
Then you cannot use fetchmail w/ kerberos, sorry. Put -kerberos into package.use
I consider adding a -kerberos to package.use be a work around for the problem
rather than a fix. I think the intention of package.use is to explicitly
disable a feature in a package because it is not required not to work around
In this case, since fetchmail just doesn't work with heimdal, I think that the
ebuild should take care of disabling USE=kerberos rather than expecting a
package.use entry to be created.