I haven't been able to run eix-remote for a few days. I thought it might be related to https://bugs.gentoo.org/show_bug.cgi?id=408567 but the maintainer says it's not, and indeed, the remote cache file that gets downloaded here appears to be more or less empty. (46 bytes...)
Just want to see if others are experiencing the similar problems. I've seen this on a couple of machines. Thanks, Mark c2stable ~ # eix-remote -q update --2012-03-20 07:26:36-- http://dev.gentooexperimental.org/eix_cache/eix-caches.tbz2 Resolving dev.gentooexperimental.org... 91.191.147.225 Connecting to dev.gentooexperimental.org|91.191.147.225|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 46 [application/octet-stream] Last-modified header missing -- time-stamps turned off. --2012-03-20 07:26:36-- http://dev.gentooexperimental.org/eix_cache/eix-caches.tbz2 Reusing existing connection to dev.gentooexperimental.org:80. HTTP request sent, awaiting response... 200 OK Length: 46 [application/octet-stream] Saving to: `eix-caches.tbz2' 100%[===========================================================================>] 46 --.-K/s in 0s 2012-03-20 07:26:36 (11.0 MB/s) - `eix-caches.tbz2' saved [46/46] * Unpacking data... chmod: cannot access `*': No such file or directory Can't open the database file /tmp/eix-remote.9aCQKKXc/1/* for reading (mode = 'rb') Did you forget to create it with 'eix-update'? problems arose with cachefile * * Calling eix-update... * 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! c2stable ~ # ls -al /var/cache/eix total 10476 drwxrwxr-x 2 portage portage 4096 Mar 17 10:53 . drwxr-xr-x 11 root root 4096 Mar 14 13:45 .. -rw-r--r-- 1 root root 0 Mar 14 13:45 .keep_app-portage_eix-0 -rw-r--r-- 1 portage portage 5347242 Mar 20 07:26 portage.eix -rw-r--r-- 1 portage portage 5338997 Mar 19 09:46 previous.eix -rw-r--r-- 1 portage portage 46 Mar 20 07:26 remote.tar.bz2 c2stable ~ #
