Re: LuaRocks install failing to get the manifest

Here is more details. I just rebooted (Just to make sure).

```

$ sudo luarocks install --from=http://rocks.moonscript.org/dev wsapi-xavante cvs-1

Warning: Failed searching manifest: Failed fetching manifest for http://rocks.moonscript.org/dev - Failed downloading http://rocks.moonscript.org/dev/manifest - timeout

Warning: Failed searching manifest: Failed fetching manifest for http://rocks.moonscript.org/ - Failed downloading http://rocks.moonscript.org/manifest - timeout

Error: No results matching query were found.

```

$ sudo luarocks install luarocks

Warning: Failed searching manifest: Failed fetching manifest for http://rocks.moonscript.org/ - Failed downloading http://rocks.moonscript.org/manifest - timeout

Error: No results matching query were found.

```

Regards,
Ryan

On Fri, Mar 20, 2015 at 2:43 PM, Ryan Pusztai <rpusztai@gmail.com> wrote:

It could be, but it is not feeling like it.

I just ran this on my main machine (Ubuntu 14.04 x8_64, LuaRocks v2.2.0)
```
luarocks install --from=http://rocks.moonscript.org/dev wsapi-xavante cvs-1
```

It finished but was delayed by 30+ seconds.

On the other system this is what I see:
```
$ sudo luarocks install --from=http://rocks.moonscript.org/dev wsapi-xavante cvs-1
[sudo] password for administrator:
Warning: Failed searching manifest: Failed fetching manifest for http://rocks.moonscript.org/dev - Failed downloading http://rocks.moonscript.org/dev/manifest - timeout

Error: No results matching query were found.
```

--
Regards,
Ryan

On Fri, Mar 20, 2015 at 2:03 PM, Hisham <h@hisham.hm> wrote:
On 20 March 2015 at 14:45, Ryan Pusztai <rpusztai@gmail.com> wrote:
> I have a script that installs about 20 rocks. I am getting a warning and it
> is going VERY slow. Is there a limit to asking for the manifest? It does
> this for each rock needing to be installed.

I just downloaded the manifest-5.1.zip 20 times in a shell loop with
no problems (less than a second each time). luarocks itself keeps a
cache in between executions with a timestamp, and tries to get
last-modified via HEAD from the server before trying to GET the
manifest.

Are you sure it's not something in your end?

-- Hisham