| 1 |
On 2012-04-17 1:41 AM, Vaeth <vaeth@××××××××××××××××××××××××.de> wrote: |
| 2 |
>>> I haven't searched layman for packages in a long time (actually had to |
| 3 |
>>> google how to do it), and am getting an error I can't seem to solve... |
| 4 |
> |
| 5 |
> Unfortunately, you have not written the actual error |
| 6 |
> which should appear probably a few (probably one) lines before: |
| 7 |
|
| 8 |
Nope... |
| 9 |
|
| 10 |
After running eix-remote update, it downloads the file, then the very |
| 11 |
next lines are: |
| 12 |
|
| 13 |
* Unpacking data |
| 14 |
/tmp/eix-remote.m6Ri2tl1/1/_var_lib_layman_a3li.eix was created with an |
| 15 |
incompatible eix-update: |
| 16 |
It uses database format 101 (current is 28). |
| 17 |
Please run 'eix-update' and try again. |
| 18 |
|
| 19 |
Followed by similar lines with different cache file names for however |
| 20 |
many hundred or so files there are... |
| 21 |
|
| 22 |
Then the last error is as I said: |
| 23 |
|
| 24 |
Writing database file /var/cache/eix .. |
| 25 |
Database contains 16219 packages in 155 categories. |
| 26 |
* could not read all eix cachefiles of |
| 27 |
/tmp/eix-remote.zv5peao3/eix-caches.tbz2 |
| 28 |
|
| 29 |
Probably your eix cachefile was *not* updated successfully. |
| 30 |
Unless the above messages suggest another cause or you specified a |
| 31 |
wrong filename, the most likely cause of this is that the server uses |
| 32 |
another eix version than you or produced broken data. Please inspect |
| 33 |
/tmp/eix-remote.zv5peao3/eix-caches.tbz2 |
| 34 |
whether this is a valid *.tar.bz2 archive containing eix cachefiles |
| 35 |
(if it has already been deleted, download it using fetch). |
| 36 |
If this is not the case (but was freshly downloaded), please report a |
| 37 |
bug. Note that the archive is *not* broken if only the cachefile format |
| 38 |
versions differ: In that case only report a bug if the eix cachefile |
| 39 |
format versions in the downloaded file are *older* than that of the most |
| 40 |
current ~x86 eix version in the portage tree (but first retry after |
| 41 |
several days before reporting such a bug to give the server maintainers |
| 42 |
a chance to upgrade after a version bump of eix). |
| 43 |
Conversely, if the downloaded versions are even newer than that |
| 44 |
supported by your eix, you will have to upgrade to the most current ~x86 |
| 45 |
version of eix to use eix-remote: This inconvenience cannot be avoided |
| 46 |
and is not a bug! |
| 47 |
|
| 48 |
>>> problems arised with cachefile _var_lib_layman_zugaina.eix |
| 49 |
>>> * Calling eix-update... |
| 50 |
>>> * could not read all eix cachefiles of |
| 51 |
>>> /tmp/eix-remote.dhR5mKNK/eix-caches.tbz2 |
| 52 |
|
| 53 |
> Maybe this error speaks about differing versions? |
| 54 |
|
| 55 |
Apparently it does, but *how* did this happen?? |
Archives