Retropie setup script update fails --

doctordruidphd

Raspberry Pi 4b 8gb
Ubuntu 22.04
Installed from git repository
retropie version 4.8.1

System works fine, but I cannot update the setup script. Running sudo ./retropie_setup.sh, choose update retropie setup script. It runs for a while, then kicks out an error:
Update failed!
error: RPC failed, curl 18 transfer closed with
outstanding read data remaining
error: 7505 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband
packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output.

From searching around, I gather this is a git error due to a slower than expected internet connection, but there is nothing I can do about the connection speed. I have tried several remedies , none have worked., including:

git config --global http.version HTTP/1.1

git config --global http.postBuffer 524288000
git config --global http.lowSpeedLimit 0
git config --global http.lowSpeedTime 999999

Any ideas how to proceed? I tried cloning a new copy of the installation, but got basically the same message.

mitu

Do note we only support RaspiOS for RPI platforms - Ubuntu is not supported and the setup script always assumes RaspiOS is present.
Try disabling compression for git and see if that solves the cloning.

doctordruidphd

OK, thanks for the info. I am also trying to install retropie on a fresh "lite" raspian so as to be able to run it on a Pi5, but I am getting the same git fatal errors trying to download the setup, so it's clearly a git problem. Same problem trying to download the current retroarch. Strange thing is that my internet speed is actually a little faster than it was when I originally did the downloads a couple of years ago, so git must have made some changes. I did try disabling git compression, to no avail. Just wondering if anyone else had run into this.

mitu

@doctordruidphd said in Retropie setup script update fails --:

Just wondering if anyone else had run into this.

Yes, I did. The solution at the time was to disable git compression, hence my reply.