Masked by missing keyword
This is common if you are attempting to install the application when it has not been tested on your architecture.
If you have a CVS package marked has 9999 you can do the following: echo "media-gfx/retina **" >> /etc/portage/package.keywords
Bear in mind that if you install onto untested architecture for that application, it may not work.
Note: Note that usage of -* (as many people used to use it, atleast) has been obsoleted and it should no longer be used. It has been replaced by **. You may occaisionally come across third party overlays which still use -*. Please petition their maintainers to update them.
echo "sys-boot/grub **" >> /etc/portage/package.keywords
# echo "sys-boot/grub **" >> /etc/portage/package.keywords
# emerge -pv grub
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] dev-libs/lzo-2.02-r1 USE="-examples" 586 kB
[ebuild NS ] sys-boot/grub-1.96 USE="-custom-cflags -netboot -static" 625 kB
Total: 2 packages (1 new, 1 in new slot), Size of downloads: 1,211 kB
Hard Masked
Hard Masked packages are unmasked by adding them to /etc/portage/package.unmask. The syntax for this file, however, slightly differs from package.keywords:
echo "=app-admin/filewatcher-2.4.0" >> /etc/portage/package.unmask
This would unmask version 2.4.0 of app-admin/filewatcher. If you want to unmask every version of a package, just specify its name like so:
echo "app-admin/filewatcher" >> /etc/portage/package.unmask
Of course, it is also possible to use the < and > operators like in package.keywords.
Note, that a package which has been hard masked is usually marked as unstable as well. You probably have to add the package to both package.unmask and package.keywords.
А почему именно grub-1.96 ?
