1 |
Hi all, |
2 |
|
3 |
I haven't searched layman for packages in a long time (actually had to |
4 |
google how to do it), and am getting an error I can't seem to solve... |
5 |
|
6 |
problems arised with cachefile _var_lib_layman_zugaina.eix |
7 |
* Calling eix-update... |
8 |
* could not read all eix cachefiles of |
9 |
/tmp/eix-remote.dhR5mKNK/eix-caches.tbz2 |
10 |
|
11 |
Then finally: |
12 |
|
13 |
Database contains 16219 packages in 155 categories. |
14 |
* could not read all eix cachefiles of |
15 |
/tmp/eix-remote.w473Rccs/eix-caches.tbz2 |
16 |
|
17 |
Probably your eix cachefile was *not* updated successfully. |
18 |
Unless the above messages suggest another cause or you specified a |
19 |
wrong filename, the most likely cause of this is that the server uses |
20 |
another eix version than you or produced broken data. Please inspect |
21 |
/tmp/eix-remote.w473Rccs/eix-caches.tbz2 |
22 |
whether this is a valid *.tar.bz2 archive containing eix cachefiles |
23 |
(if it has already been deleted, download it using fetch). |
24 |
If this is not the case (but was freshly downloaded), please report a bug. |
25 |
Note that the archive is *not* broken if only the cachefile format |
26 |
versions differ: In that case only report a bug if the eix cachefile |
27 |
format versions in the downloaded file are *older* than that of the most |
28 |
current ~x86 eix version in the portage tree (but first retry after |
29 |
several days before reporting such a bug to give the server maintainers |
30 |
a chance to upgrade after a version bump of eix). |
31 |
Conversely, if the downloaded versions are even newer than that |
32 |
supported by your eix, you will have to upgrade to the most current ~x86 |
33 |
version of eix to use eix-remote: This inconvenience cannot be avoided |
34 |
and is not a bug! |
35 |
|
36 |
Not sure what to do here or how things got hosed... |