| 1 |
Holly Bostick <motub <at> planet.nl> writes: |
| 2 |
|
| 3 |
|
| 4 |
> > Jffnms is masked. However I am able to install it on an intel portable |
| 5 |
> > by adding this line to the /etc/portage/package.keywords |
| 6 |
> > net-analyzer/jffnms ~x86 |
| 7 |
|
| 8 |
> > This is pretty must standard approach. |
| 9 |
|
| 10 |
> > However, on a gentoo system that I manually hacked a jffnms installation |
| 11 |
> > on on a very early (experimental) ebuild does not even show jffnms |
| 12 |
> > as a masked package. It intalled configuration file is /etc/jffnms, but |
| 13 |
> > I delete that dir and contents. Still I cannot install the jffnms |
| 14 |
> > masked package on this one system. Everyother system can install jffnms |
| 15 |
> > with the aforementioned line added to package.keywords. |
| 16 |
|
| 17 |
> > Any ideas how to track this down? Should I just copy over the ebuild manually |
| 18 |
> > to /usr/portage/distfiles ? |
| 19 |
|
| 20 |
> Ebuilds don't go in /usr/portage/distfiles, so doing that won't help you. |
| 21 |
|
| 22 |
Correct, they are not ebuild but the tar.bz2 files. I recently install |
| 23 |
package realplayer: |
| 24 |
RealPlayer-10.0.6.776-20050915.i586.rpm |
| 25 |
then emerged the package. I should have been more accurate with |
| 26 |
the verbiage. |
| 27 |
|
| 28 |
The bottom line is I can install jffnms which is masked on any system |
| 29 |
but one. All are either intel or x86(athlon). I do not remember any of the |
| 30 |
the details of the previous jffnms hacking attempts on this system. |
| 31 |
|
| 32 |
So I deleted the /etc/jffnms/* directory and contents, but that did not |
| 33 |
help. |
| 34 |
|
| 35 |
On most systems I get these results: |
| 36 |
emerge -s jffnms |
| 37 |
Searching... |
| 38 |
[ Results for search key : jffnms ] |
| 39 |
[ Applications found : 1 ] |
| 40 |
|
| 41 |
* net-analyzer/jffnms |
| 42 |
Latest version available: 0.8.2 |
| 43 |
Latest version installed: [ Not Installed ] |
| 44 |
|
| 45 |
|
| 46 |
On the one system that refuse to work I get: |
| 47 |
|
| 48 |
emerge -s jffnms |
| 49 |
Searching... |
| 50 |
[ Results for search key : jffnms ] |
| 51 |
[ Applications found : 0 ] |
| 52 |
|
| 53 |
|
| 54 |
I just do not understand why one system (athlon) does not see the |
| 55 |
package and the other ones do? |
| 56 |
|
| 57 |
Is it the differences in the intel vs athlon archtecture? |
| 58 |
I thought both were x86? |
| 59 |
|
| 60 |
Both athlon systems do not show jffnms as a viable package |
| 61 |
wtih 'emerge -s jffnms'. |
| 62 |
|
| 63 |
Thoughts? |
| 64 |
|
| 65 |
> When you say that you "manually hacked an installation", what do you |
| 66 |
> mean? If you created an ebuild in your PORTDIR_OVERLAY (the correct |
| 67 |
> procedure), do you still have an overlay directory enabled (preferably |
| 68 |
> the same one), in /etc/make.conf? |
| 69 |
|
| 70 |
PORTDIR_OVERLAY is not used on any of these systems. |
| 71 |
|
| 72 |
> If you put your ebuild in the regular Portage tree, and you have since |
| 73 |
> synced , the "illegal" ebuild has likely been removed. In that case, I |
| 74 |
> would suggest enabling an overlay in /etc/make.conf, setting up an |
| 75 |
> overlay tree (default location is /usr/local/portage), putting the |
| 76 |
> ebuild there, then digesting it. It should then emerge normally. |
| 77 |
|
| 78 |
emerge -s jffnms does not show up on the athlon systems, including |
| 79 |
one that never had jffnms installed. |
| 80 |
|
| 81 |
> Did you even install the previous 'hack' with Portage? |
| 82 |
|
| 83 |
Don't remember as I tried all sorts of things over several weeks.... |
| 84 |
|
| 85 |
|
| 86 |
|
| 87 |
|
| 88 |
-- |
| 89 |
gentoo-user@g.o mailing list |
Archives