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