Unable to get sources for eduke32

sleve_mcdichael

Log: https://pastebin.com/n2qspCBu
Relevant excerpt:

Cloning into '/home/pi/RetroPie-Setup/tmp/build/eduke32'...
error: RPC failed; curl 56 GnuTLS recv error (-9): Error decoding the received TLS packet.
fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed

mitu

Seems like an issue with the server. Can you run the clone manually and set GIT_CURL_VERBOSE =1 to get a debug log ?

GIT_CURL_VERBOSE =1 git clone --recursive --branch master "https://voidpoint.io/terminx/eduke32.git" "/home/pi/RetroPie-Setup/tmp/build/eduke32"

sleve_mcdichael

@mitu I ran the clone manually and...it worked? But I ran it from the local console with | tee gitlog.txt and the logfile was empty. So I tried again with 2>&1 | tee gitlog.txt which kind of worked but not really...it printed and captured a few lines, but not near like what was displayed the first time. I canceled the operation after a couple of minutes.

But since it worked, I tried the module again, and it failed again. Same error, setup log was nearly identical to before, save for timestamps.

At that point I just got back on my phone and remoted in via SSH so I can copy/paste from that.

The clone failed once, and then succeeded when I tried again immediately after. Here is the log from those attempts: https://pastebin.com/wRTf3Z0C

mitu

From what I've seen in other similar issues having this error, the connection speed may cause the server to close the connection during the clone start.
Since we're not doing a shallow clone (as most modules do), the download size is larger and the server may time out early due to the connection speed.

Not sure what we can do on the client to fix this - I can't reproduce the problem here anyway no matter how many times I clone the repo (either manually or through the setup script).

Merlin3D

Retrorangepi.org has the source on there images

mitu

@Merlin3D Sure, but I don't see how it helps solving this problem. I can download the source without issues and the project's site is up and running - it's no a source availability issue.