Masked packages

CollieJim · 03-17-2010, 12:21 AM

On several occasions I have been unable to emerge a package:

Code:

!!! All ebuilds that could satisfy "media-video/miro" have been masked.
!!! One of the following masked packages is required to complete your request:
- media-video/miro-2.5.3 (masked by: ~x86 keyword)

Recently I came across one that was masked because of licensing concerns, not because of any software incompatibility.

How do I find out why a package is masked?

TIA

troop · 03-17-2010, 04:51 PM

Maintainer just don't think this package stable on x86.
cat /usr/portage/media-video/miro/miro-2.5.4.ebuild

Quote:

# NOTES:
# it's probably not working with python-3
# used xulrunner has to be the same as the one used for gtkmozembed-python
# psyco can make miro speedier, add a USE flag, recommand in postinst ?

# TODO:
# create a real test suite, upstream bug 12369
# try to have a real xine/gstreamer choice, upstream bug 12371

CollieJim · 03-20-2010, 01:46 AM

Thanks.
That gives me the answer for miro, but I'm looking for a general source of information.
It would be nice if there were comments in the ebuilds that emerge displays along with the 'masked' indication.

imaginasys · 03-23-2010, 12:37 PM

Quote:

Originally Posted by CollieJim

Thanks.
That gives me the answer for miro, but I'm looking for a general source of information.
It would be nice if there were comments in the ebuilds that emerge displays along with the 'masked' indication.

The reason is in the message "masked by: ~x86 keyword".

You are using stable branch and the package you depend on is in testing...

Read: http://www.gentoo.org/doc/en/handboo...?part=2&chap=1
and find this text "Code Listing 5.4: Portage warning about masked packages - reason"

You can look for miro at http://gentoo-portage.com/ to have info on a package: use flags, dependencies, reverse dependencies, and so on...

Good reading,

BT

vik · 04-20-2010, 01:19 AM

I had a package masked because of a license: it was dev-java/sun-jre-bin. I created /etc/portage/package.license and added this dev-java/sun-jre-bin dlj-1.1 to get rid of the masking. Emerge should tell you why the package is masked when you try to emerge it, or emerge -pv <pkg>.