| 1 |
>> Any ideas on how to debug this? |
| 2 |
> |
| 3 |
> First of all, update all affected parties to the latest versions |
| 4 |
> (eix, portage, layman). |
| 5 |
|
| 6 |
Did that. I'm always up to date. |
| 7 |
|
| 8 |
> |
| 9 |
> Second, use divide and conqueror strategy. If this is the eix |
| 10 |
> problem, isolate it to eix only without invoking layman (or emaint |
| 11 |
> sync -a or what on the earth you were doing?!). |
| 12 |
|
| 13 |
I use eix-sync, so I believe this is a problem with eix rather than |
| 14 |
any ancillary software. |
| 15 |
|
| 16 |
> |
| 17 |
> Try with eix-update. If problem persists, look for what eix cache |
| 18 |
> method you are using: see man eix for the list, there are many of |
| 19 |
> them. Since you have exec error, it likely is ebuild, try to change |
| 20 |
> it to parse or metadata. |
| 21 |
> |
| 22 |
|
| 23 |
eix-update gives the same error messages as eix-sync. I've tried |
| 24 |
reading the eix |
| 25 |
man page, and have to admit that I don't understand what the various |
| 26 |
cache methods mean. I did try both "eix-update -m science parse" and |
| 27 |
"eix-update -m science metadata" without solving the problem (and without |
| 28 |
me understanding precisely how these commands change the situation). |
| 29 |
FWIW, eix --dump gives |
| 30 |
|
| 31 |
# STRING |
| 32 |
# Portage cache-backend that should be used for the overlays. |
| 33 |
# (metadata[:*]/sqlite/flat[:*]/portage-2.1/parse[*][|]ebuild[*]/eix[*][:*]) |
| 34 |
OVERLAY_CACHE_METHOD="parse|ebuild*" |
| 35 |
|
| 36 |
In my installations, I note that there's a |
| 37 |
/usr/portage/metadata/md5-cache directory, but no |
| 38 |
/var/lib/layman/science/metadata |
| 39 |
cache directories. Is something missing? |
| 40 |
|
| 41 |
Is there some place other than the eix man page that describes these |
| 42 |
various kinds of caches? |
| 43 |
|
| 44 |
Thanks for your suggestions, |
| 45 |
|
| 46 |
John |
Archives