1 |
Richard Fish <bigfish <at> asmallpond.org> writes: |
2 |
|
3 |
> > * net-analyzer/jffnms |
4 |
> > Latest version available: 0.8.2 |
5 |
> > Latest version installed: [ Not Installed ] |
6 |
|
7 |
> net-analyzer/jffnms is not part of the official portage tree, nor is |
8 |
> it in the online package database. So there are only two ways this |
9 |
> ebuild exist: |
10 |
|
11 |
> 1. It was previously a part of portage, and has since been removed, in |
12 |
> which case the next emerge --sync will end up removing it from your |
13 |
> portage tree. |
14 |
|
15 |
bummer. |
16 |
|
17 |
> 2. You installed an ebuild manually in either the portage tree or |
18 |
> portage overlay. |
19 |
|
20 |
Nope. |
21 |
|
22 |
> Are there any copyright or CVS comments at the top of |
23 |
> /usr/portage/net-analyzer/jffnms/jffnms-0.8.2.ebuild? |
24 |
|
25 |
dunno, the dir does not exist, yet an emerge sync |
26 |
shows the package. The system was last sync'd on monday |
27 |
the 21st of Nov. |
28 |
|
29 |
How do I retreive the old ebuilds, so I can keep working on the |
30 |
ebuild or use it as a basis to finish the ebuild package for |
31 |
jffnms? |
32 |
|
33 |
Bugzilla 92501 was the original request. |
34 |
|
35 |
I wonder why it wass abandoned before it was ever finished? |
36 |
|
37 |
James |
38 |
|
39 |
|
40 |
|
41 |
-- |
42 |
gentoo-user@g.o mailing list |