Sometimes there are Manifest errors:
localhost portage # emerge =irate-20040202 Calculating dependencies |!!! Manifest file not found: '/usr/local/portage/net-p2p/irate/Manifest'
!!! All ebuilds that could satisfy "=irate-20040202" have been masked. !!! One of the following masked packages is required to complete your request: !!! Manifest file not found: '/usr/local/portage/net-p2p/irate/Manifest' - net-p2p/irate-20040202 (masked by: corruption)
I've had this with other ebuilds too. The fix is to download the Manifest and the /files/ directories from the same place the ebuild came from.
Now am I doing something wrong, is the ebuild developer doing something wrong or should this be in the documentation?-FreakWent 03-Apr-2007
I just tried to install the latest dev-lang/ifc from bugzilla using these steps and it didnt work. Talked to the developer and he told me to copy the contents of /usr/portage/dev-lang/ifc into the overlay dir. This worked. Should this be included in the article, or is that probably just a one-off thing? Never made an ebuild so I wouldn't know. I just play with these things. Thx.
You were probably missing e.g. patches from its "files" subdirectory.
> echo "<category>/<package> ~x86" >>/etc/portage/package.keywords</nowiki>
instead of> ACCEPT_KEYWORDS=~x86 emerge -p package
It makes the ~x86 settings permanent for that package, so you don't have to do it again. --Exdaix 23:02, 27 Jun 2004 (GMT)
It removes the mask from a package; otherwise, it could be downgraded (or givve an error of 'not found') during the next emerge -D world, possible resulting in bad dependancies. --Sudrien, 2004.12.23
There is also another drawback, "ACCEPT_KEYWORDS" unmasks all dependencies.> echo "<category>/<package> ~x86" >>/etc/portage/package.keywords
unmasks only one selected package. --Wintermute, 28.04.2005
~x86 in package.keywords is no longer valid, it works only without the ~x86 Keyword, use >echo "<category>/<package>" >> /etc/portage/package.keywords Clark Nonsense - you must be confusing package.keywords with e.g. package.mask. What's the source of this info? What portage version? --PaulBredbury
ACK, this is nonsense. ~x86 may be skipped as it is default, but it still works when it's specified. --Bigfoot
Yeah. I assume portage has changed for that to be correct. man portage now shows that e.g. "net-analyzer/netcat" is allowed in package.keywords - I'm sure that wasn't there a few months ago.
Shoud the original package be unmerged first?
If I already have a package installed, but then decided to customize it using an overlay, do I have to unmerge the existing package first? Or will emerging the customized overlay package remove any unneeded files from the existing installation? And what happens if I want to go back to the original package by unsetting PORTDIR_OVERLAY? Will all the files added by the customized version be removed? How to remove local ebuild/overlays?
I've look thoughout the docs and can not find any info on removing local ebuilds and overlays. On my system, I have a couple ebuilds that have moved in the main portage tree and now need to remove them. I can not find the undigest command nor how to properlly remove an ebuield. Can a kind person add this info to the How-to wiki?