[gentoo-user] Re: masked package woes

2005-11-26 Thread James
Nick Rout nick at rout.co.nz writes:

  Bugzilla 92501  was the original request.

 
 By the look of the CVS tree this ebuild has NEVER been in portage. How
 it got on your system can only be explained by you.

Where/how do you look at the portage tree in the full complement
of packages that are available or what's not in the portage tree?
Does one just look in /usr/portage/distfiles or some other special
directory, or is there a place where one can peruse the entire tree
regardless of what they have install on a gentoo system?

 If you think it is in portage on some of your systems you can verify by
 looking in the directory


I only said this because 'emerge -s jffnms' has previously shown
the package (in red) as masked.  Plus this page was created:
http://dev.gentoo.org/~angusyoung/docs/jffnms/docs/jffnms.html

 ls /usr/portage/net-analyzer/jffnms/

No, this dir does not exist.

 If you want to build it why don't you download the ebuild from the
 bugzilla site and put it in your overlay? The overlay process is well
 documented, I am not going to burden this list with yet another
 explanation.

I guess I have no other choice.

  I wonder why it wass abandoned before it was ever finished?

 It doesn't look abandoned to me, the last post was on 19 October 2005,
 when a new version of the ebuild was posted.

OK, I confused see the package with 'emerge -s jffnms' with it
being masked but in the official tree of packages

 Lots of new evuilds get posted to bugzilla, not as many ever come out
 the other end.

 Once you have tested it don't forget to go back to the bug and report
 back on your experience. 

OK

James

-- 
gentoo-user@gentoo.org mailing list



[gentoo-user] Re: masked package woes

2005-11-26 Thread James
Richard Fish bigfish at asmallpond.org writes:


 The entire tree is in /usr/portage.  For example, all possible
 net-analyzer packages are /usr/portage/net-analyzer.  find
 /usr/portage -name '*.ebuild' will show you all ebuilds in the tree,
 masked or not, installed or not.  Compare this to what you actually
 have installed under /var/db/pkg.

This make things more clear.

 Also, the portage CVS tree can be viewed at:
 http://www.gentoo.org/cgi-bin/viewcvs.cgi/?root=gentoo-x86

OK

  I only said this because 'emerge -s jffnms' has previously shown
  the package (in red) as masked.  Plus this page was created:
  http://dev.gentoo.org/~angusyoung/docs/jffnms/docs/jffnms.html

 Ok, but view his blog here:
 http://dev.gentoo.org/~angusyoung/blog/
 Notice the statement ...which I hope to add to portage in the near future.

Cool.

 It is entirely possible (but incorrect) to place ebuilds downloaded
 manually into the /usr/portage tree.  It is also possible (and
 correct) to place those ebuilds into PORTAGE_OVERLAY.

Yes, I'm following these instructions:
http://gentoo-wiki.com/HOWTO_Installing_3rd_Party_
Ebuilds#ebuild:_A_Safer_Approach

 You (or someone else with root access to the system) must have done
 one or the other on the system that shows it as available.

Yes it was a long time ago, and I just do not remember.
Nobody else has root on the system.  

Thanks for the help, Everyone


James




-- 
gentoo-user@gentoo.org mailing list



[gentoo-user] Re: masked package woes

2005-11-24 Thread James
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



Re: [gentoo-user] Re: masked package woes

2005-11-24 Thread Richard Fish
On 11/24/05, James [EMAIL PROTECTED] wrote:
 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 ]

net-analyzer/jffnms is not part of the official portage tree, nor is
it in the online package database.  So there are only two ways this
ebuild exist:

1. It was previously a part of portage, and has since been removed, in
which case the next emerge --sync will end up removing it from your
portage tree.

2. You installed an ebuild manually in either the portage tree or
portage overlay.

Are there any copyright or CVS comments at the top of
/usr/portage/net-analyzer/jffnms/jffnms-0.8.2.ebuild?

 Is it the differences in the intel vs athlon archtecture?
 I thought both were x86?

No.  There is only a single (official) portage tree for all archs.

-Richard

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Re: masked package woes

2005-11-24 Thread Nick Rout

On Fri, 25 Nov 2005 01:45:49 + (UTC)
James wrote:

 emerge -s jffnms does not show up on the athlon systems, including
 one that never had jffnms installed.


Has the machine been sync'd recently (sorry if this has been covered
already)

-- 
Nick Rout [EMAIL PROTECTED]

-- 
gentoo-user@gentoo.org mailing list



[gentoo-user] Re: masked package woes

2005-11-24 Thread James
Richard Fish bigfish at asmallpond.org writes:

  *  net-analyzer/jffnms
Latest version available: 0.8.2
Latest version installed: [ Not Installed ]

 net-analyzer/jffnms is not part of the official portage tree, nor is
 it in the online package database.  So there are only two ways this
 ebuild exist:

 1. It was previously a part of portage, and has since been removed, in
 which case the next emerge --sync will end up removing it from your
 portage tree.

bummer.

 2. You installed an ebuild manually in either the portage tree or
 portage overlay.

Nope.

 Are there any copyright or CVS comments at the top of
 /usr/portage/net-analyzer/jffnms/jffnms-0.8.2.ebuild?

dunno, the dir does not exist, yet an emerge sync
shows the package. The system was last sync'd on monday
the 21st of Nov.

How do I retreive the old ebuilds, so I can keep working on the 
ebuild or use it as a basis to finish the ebuild package for
jffnms?

Bugzilla 92501  was the original request.

I wonder why it wass abandoned before it was ever finished?

James



-- 
gentoo-user@gentoo.org mailing list



[gentoo-user] Re: masked package woes

2005-11-24 Thread James
Nick Rout nick at rout.co.nz writes:


  emerge -s jffnms does not show up on the athlon systems, including
  one that never had jffnms installed.

 Has the machine been sync'd recently (sorry if this has been covered
 already)

Monday the 21st of November.


James





-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Re: masked package woes

2005-11-24 Thread Nick Rout

On Fri, 25 Nov 2005 02:32:58 + (UTC)
James wrote:

 Richard Fish bigfish at asmallpond.org writes:
 
   *  net-analyzer/jffnms
 Latest version available: 0.8.2
 Latest version installed: [ Not Installed ]
 
  net-analyzer/jffnms is not part of the official portage tree, nor is
  it in the online package database.  So there are only two ways this
  ebuild exist:
 
  1. It was previously a part of portage, and has since been removed, in
  which case the next emerge --sync will end up removing it from your
  portage tree.
 
 bummer.
 
  2. You installed an ebuild manually in either the portage tree or
  portage overlay.
 
 Nope.
 
  Are there any copyright or CVS comments at the top of
  /usr/portage/net-analyzer/jffnms/jffnms-0.8.2.ebuild?
 
 dunno, the dir does not exist, yet an emerge sync
 shows the package. The system was last sync'd on monday
 the 21st of Nov.
 
 How do I retreive the old ebuilds, so I can keep working on the 
 ebuild or use it as a basis to finish the ebuild package for
 jffnms?
 
 Bugzilla 92501  was the original request.
 

By the look of the CVS tree this ebuild has NEVER been in portage. How
it got on your system can only be explained by you.

If you think it is in portage on some of your systems you can verify by
looking in the directory

ls /usr/portage/net-analyzer/jffnms/

If you want to build it why don't you download the ebuild from the
bugzilla site and put it in your overlay? The overlay process is well
documented, I am not going to burden this list with yet another
explanation.


 I wonder why it wass abandoned before it was ever finished?
 

It doesn't look abandoned to me, the last post was on 19 October 2005,
when a new version of the ebuild was posted.

Lots of new evuilds get posted to bugzilla, not as many ever come out
the other end.

Once you have tested it don't forget to go back to the bug and report
back on your experience. 

 James
 
 
 
 -- 
 gentoo-user@gentoo.org mailing list

-- 
Nick Rout [EMAIL PROTECTED]

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Re: masked package woes

2005-11-24 Thread Ciaran McCreesh
On Fri, 25 Nov 2005 02:32:58 + (UTC) James
[EMAIL PROTECTED] wrote:
|  2. You installed an ebuild manually in either the portage tree or
|  portage overlay.
| 
| Nope.
| 
|  Are there any copyright or CVS comments at the top of
|  /usr/portage/net-analyzer/jffnms/jffnms-0.8.2.ebuild?
| 
| dunno, the dir does not exist, yet an emerge sync
| shows the package. The system was last sync'd on monday
| the 21st of Nov.
| 
| How do I retreive the old ebuilds, so I can keep working on the 
| ebuild or use it as a basis to finish the ebuild package for
| jffnms?

Doesn't look like it was ever in the tree...

[EMAIL PROTECTED] net-analyzer 0 0.45 $ cvs log jffnms
cvs log: nothing known about jffnms

-- 
Ciaran McCreesh : Gentoo Developer (Supreme Lord Gerbil Wrangler)
Mail: ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm



signature.asc
Description: PGP signature