Is there any fix for it ?
eix-remote update
--2015-01-16 18:28:11-- http://gpo.zugaina.org/eix_cache/eix-cache.tbz2
Resolving gpo.zugaina.org... 176.31.182.181
Connecting to gpo.zugaina.org|176.31.182.181|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3188736 (3.0M) [text/plain]
Saving to: ‘eix-cache.tbz2’
eix-cache.tbz2
100%[==============================================================================>]
3.04M 235KB/s in 14s
2015-01-16 18:28:25 (221 KB/s) - ‘eix-cache.tbz2’ saved [3188736/3188736]
* Unpacking data
...<nip> ...
[529] 'zx2c4' layman/zx2c4 (cache: eix*
/tmp/eix-remote.k30uzIKu/1/zx2c4.eix [*/zx2c4])
Reading Packages .. Finished
Applying masks ..
Calculating hash tables ..
Writing database file /var/cache/eix/remote.eix ..
Database contains 29790 packages in 241 categories.
* could not read all eix cachefiles of /var/cache/eix/remote.tar.bz2
Probably your eix cachefile was *not* updated successfully.
Unless the above messages suggest another cause or you specified a
wrong filename, the most likely cause of this is that the server uses
another eix version than you or produced broken data. Please check whether
EIX_REMOTEARCHIVE is a valid *.tar.bz2 archive containing eix cachefiles
(you can download it using fetch).
If this is not the case (but was freshly downloaded), please report a bug.
Note that the archive is *not* broken if only the cachefile format versions
differ: In that case only report a bug if the eix cachefile format versions
in the downloaded file are *older* than that of the most current ~x86 eix
version in the portage tree (but first retry after several days before
reporting such a bug to give the server maintainers a chance to upgrade
after a version bump of eix).
Conversely, if the downloaded versions are even newer than that supported by
your eix, you will have to upgrade to the most current ~x86 version of eix
to use eix-remote: This inconvenience cannot be avoided and is not a bug!
