1 |
On Mon, 23 May 2016 15:08:35 +0300, Thanasis wrote: |
2 |
|
3 |
> On 05/23/2016 12:49 PM, Neil Bothwick wrote: |
4 |
> > On Mon, 23 May 2016 09:32:14 +0100, Neil Bothwick wrote: |
5 |
> > |
6 |
> >>> wget -N http://gpo.zugaina.org/eix_cache/eix-cache.tbz2 |
7 |
> >>> |
8 |
> >>> But the command fails, and it looks like the file eix-cache.tbz2, |
9 |
> >>> which |
10 |
> >>> is downloaded, is either empty or corrupt. |
11 |
> >>> |
12 |
> >>> Any one else faced/facing the same problem? |
13 |
> >> |
14 |
> >> "eix - q remote" still works here. |
15 |
> > |
16 |
> > Sorry, copying commands on a mobile while distracted is never a good |
17 |
> > idea. That should be |
18 |
> > |
19 |
> > eix-remote -q update |
20 |
> > |
21 |
> > |
22 |
> |
23 |
> Can you check what file gets downloaded in your case, because it fails |
24 |
> here: |
25 |
> |
26 |
> # eix-remote -q update |
27 |
> |
28 |
> * failed: wget -N --no-verbose -- |
29 |
> http://gpo.zugaina.org/eix_cache/eix-cache.tbz2 |
30 |
|
31 |
http://gpo.zugaina.org/eix_cache/eix-cache.tbz2 |
32 |
|
33 |
So the same as yours. So either it's a problem with routing from you to |
34 |
the server or there's some sort of user-agent checking to stop people |
35 |
randomly using wget ;-) |
36 |
|
37 |
No, it's not that, wget worked from here. |
38 |
|
39 |
The other question is: why are you using wget when eix already has the |
40 |
facility to download and import this file built in. |
41 |
|
42 |
|
43 |
-- |
44 |
Neil Bothwick |
45 |
|
46 |
I am Speedy Gonzales of Borg: Prepare to be accelerated! |