| 1 |
I haven't been able to run eix-remote for a few days. I thought it |
| 2 |
might be related to https://bugs.gentoo.org/show_bug.cgi?id=408567 but |
| 3 |
the maintainer says it's not, and indeed, the remote cache file that |
| 4 |
gets downloaded here appears to be more or less empty. (46 bytes...) |
| 5 |
|
| 6 |
Just want to see if others are experiencing the similar problems. I've |
| 7 |
seen this on a couple of machines. |
| 8 |
|
| 9 |
Thanks, |
| 10 |
Mark |
| 11 |
|
| 12 |
c2stable ~ # eix-remote -q update |
| 13 |
--2012-03-20 07:26:36-- |
| 14 |
http://dev.gentooexperimental.org/eix_cache/eix-caches.tbz2 |
| 15 |
Resolving dev.gentooexperimental.org... 91.191.147.225 |
| 16 |
Connecting to dev.gentooexperimental.org|91.191.147.225|:80... connected. |
| 17 |
HTTP request sent, awaiting response... 200 OK |
| 18 |
Length: 46 [application/octet-stream] |
| 19 |
Last-modified header missing -- time-stamps turned off. |
| 20 |
--2012-03-20 07:26:36-- |
| 21 |
http://dev.gentooexperimental.org/eix_cache/eix-caches.tbz2 |
| 22 |
Reusing existing connection to dev.gentooexperimental.org:80. |
| 23 |
HTTP request sent, awaiting response... 200 OK |
| 24 |
Length: 46 [application/octet-stream] |
| 25 |
Saving to: `eix-caches.tbz2' |
| 26 |
|
| 27 |
100%[===========================================================================>] |
| 28 |
46 --.-K/s in 0s |
| 29 |
|
| 30 |
2012-03-20 07:26:36 (11.0 MB/s) - `eix-caches.tbz2' saved [46/46] |
| 31 |
|
| 32 |
* Unpacking data... |
| 33 |
chmod: cannot access `*': No such file or directory |
| 34 |
Can't open the database file /tmp/eix-remote.9aCQKKXc/1/* for reading |
| 35 |
(mode = 'rb') |
| 36 |
Did you forget to create it with 'eix-update'? |
| 37 |
problems arose with cachefile * |
| 38 |
* Calling eix-update... |
| 39 |
* could not read all eix cachefiles of /var/cache/eix/remote.tar.bz2 |
| 40 |
|
| 41 |
Probably your eix cachefile was *not* updated successfully. |
| 42 |
Unless the above messages suggest another cause or you specified a |
| 43 |
wrong filename, the most likely cause of this is that the server uses |
| 44 |
another eix version than you or produced broken data. Please check whether |
| 45 |
EIX_REMOTEARCHIVE is a valid *.tar.bz2 archive containing eix cachefiles |
| 46 |
(you can download it using fetch). |
| 47 |
If this is not the case (but was freshly downloaded), please report a bug. |
| 48 |
Note that the archive is *not* broken if only the cachefile format versions |
| 49 |
differ: In that case only report a bug if the eix cachefile format versions |
| 50 |
in the downloaded file are *older* than that of the most current ~x86 eix |
| 51 |
version in the portage tree (but first retry after several days before |
| 52 |
reporting such a bug to give the server maintainers a chance to upgrade |
| 53 |
after a version bump of eix). |
| 54 |
Conversely, if the downloaded versions are even newer than that supported by |
| 55 |
your eix, you will have to upgrade to the most current ~x86 version of eix |
| 56 |
to use eix-remote: This inconvenience cannot be avoided and is not a bug! |
| 57 |
c2stable ~ # ls -al /var/cache/eix |
| 58 |
total 10476 |
| 59 |
drwxrwxr-x 2 portage portage 4096 Mar 17 10:53 . |
| 60 |
drwxr-xr-x 11 root root 4096 Mar 14 13:45 .. |
| 61 |
-rw-r--r-- 1 root root 0 Mar 14 13:45 .keep_app-portage_eix-0 |
| 62 |
-rw-r--r-- 1 portage portage 5347242 Mar 20 07:26 portage.eix |
| 63 |
-rw-r--r-- 1 portage portage 5338997 Mar 19 09:46 previous.eix |
| 64 |
-rw-r--r-- 1 portage portage 46 Mar 20 07:26 remote.tar.bz2 |
| 65 |
c2stable ~ # |
Archives