| 1 |
On 1/5/06, Trenton Adams <trenton.d.adams@×××××.com> wrote: |
| 2 |
> Calculating world dependencies | |
| 3 |
> emerge: there are no ebuilds to satisfy ">=dev-perl/PodParser-1.22". |
| 4 |
> (dependency required by "mail-filter/spamassassin-3.1.0" [binary]) |
| 5 |
|
| 6 |
This is something that sometimes occurs when you get an out-of-sync |
| 7 |
portage tree (you are syncing at the same time as the mirror is |
| 8 |
updating). |
| 9 |
|
| 10 |
The fix is to just emerge --sync again. |
| 11 |
|
| 12 |
It can also happen if you use NFS for portage but do not keep the |
| 13 |
cache up-to-date. |
| 14 |
|
| 15 |
> re-merge it without --usepkg. If I recall correctly, I also would |
| 16 |
> have had to remove the file "/var/cache/edb/remote_metadata.pickle", |
| 17 |
|
| 18 |
The portage cache should be updated automatically at the end of every |
| 19 |
sync. So no, removing this file would not be necessary. |
| 20 |
|
| 21 |
> but I started using NFS for my portage instead. That file has |
| 22 |
> information about packages, and their dependencies, so I looked in it, |
| 23 |
> and it had the wrong information. |
| 24 |
|
| 25 |
Are you also using NFS for /var/cache/edb? If not, then you need to |
| 26 |
run emerge --metadata. |
| 27 |
|
| 28 |
-Richard |
| 29 |
|
| 30 |
PS: Please avoid top-posting here. |
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-user@g.o mailing list |
Archives