Holly Bostick <motub <at> planet.nl> writes:
> > Jffnms is masked. However I am able to install it on an intel portable > > by adding this line to the /etc/portage/package.keywords > > net-analyzer/jffnms ~x86 > > This is pretty must standard approach. > > However, on a gentoo system that I manually hacked a jffnms installation > > on on a very early (experimental) ebuild does not even show jffnms > > as a masked package. It intalled configuration file is /etc/jffnms, but > > I delete that dir and contents. Still I cannot install the jffnms > > masked package on this one system. Everyother system can install jffnms > > with the aforementioned line added to package.keywords. > > Any ideas how to track this down? Should I just copy over the ebuild > > manually > > to /usr/portage/distfiles ? > Ebuilds don't go in /usr/portage/distfiles, so doing that won't help you. Correct, they are not ebuild but the tar.bz2 files. I recently install package realplayer: RealPlayer-10.0.6.776-20050915.i586.rpm then emerged the package. I should have been more accurate with the verbiage. The bottom line is I can install jffnms which is masked on any system but one. All are either intel or x86(athlon). I do not remember any of the the details of the previous jffnms hacking attempts on this system. So I deleted the /etc/jffnms/* directory and contents, but that did not help. On most systems I get these results: emerge -s jffnms Searching... [ Results for search key : jffnms ] [ Applications found : 1 ] * net-analyzer/jffnms Latest version available: 0.8.2 Latest version installed: [ Not Installed ] On the one system that refuse to work I get: emerge -s jffnms Searching... [ Results for search key : jffnms ] [ Applications found : 0 ] I just do not understand why one system (athlon) does not see the package and the other ones do? Is it the differences in the intel vs athlon archtecture? I thought both were x86? Both athlon systems do not show jffnms as a viable package wtih 'emerge -s jffnms'. Thoughts? > When you say that you "manually hacked an installation", what do you > mean? If you created an ebuild in your PORTDIR_OVERLAY (the correct > procedure), do you still have an overlay directory enabled (preferably > the same one), in /etc/make.conf? PORTDIR_OVERLAY is not used on any of these systems. > If you put your ebuild in the regular Portage tree, and you have since > synced , the "illegal" ebuild has likely been removed. In that case, I > would suggest enabling an overlay in /etc/make.conf, setting up an > overlay tree (default location is /usr/local/portage), putting the > ebuild there, then digesting it. It should then emerge normally. emerge -s jffnms does not show up on the athlon systems, including one that never had jffnms installed. > Did you even install the previous 'hack' with Portage? Don't remember as I tried all sorts of things over several weeks.... -- gentoo-user@gentoo.org mailing list