Retropie can no longer update from first boot

xman1

The files it is looking for from the following no longer exist when trying to do an update.

Retropie wants to update the following: http://raspbian.raspberrypi.org/raspbian/pool/main/s/subversion/subversion-tools_1.10.4-1+deb10u1_armhf.deb

Sometime today, the link where it is looking for the file removed that file and now only has the following: http://raspbian.raspberrypi.org/raspbian/pool/main/s/subversion/subversion-tools_1.10.4-1+deb10u2_armhf.deb so the update fails and I can't even get into the configuration anymore as it keeps trying to run this update.

Any advice on which script controls this so I can update it to point to the new file?

xman1

Since Retropie is irreversibly broken for the moment, I will load Raspberian and load Retropie on top for now.

mitu

@xman1 said in Retropie can no longer update from first boot:

Any advice on which script controls this so I can update it to point to the new file?

Run manually sudo apt update && sudo apt upgrade before updating RetroPie.

xman1

@mitu - It is still broken even using this method. I get the following for the update:

InRelease is not valid yet (invalid for another 183d 5h 4min 2s). Updates for this repository will not be applied.

I reflased with a brand new image just to check. Using the Raspberry Pi 4/400 image. This image worked this morning when updating. Not later on. I should have left it alone instead of redoing it.

It might be because if the Buster package that retropie choose to use. Probably should use stable.

mitu

@xman1 said in Retropie can no longer update from first boot:

InRelease is not valid yet (invalid for another 183d 5h 4min 2s). Updates for this repository will not be applied.

Either your system date is not synchronized or the mirror you're using has issues.

It might be because if the Buster package that retropie choose to use. Probably should use stable.

Buster is stable.

xman1

@mitu Back when I ran Debian (many years) Buster was the testing branch. Seems things have changed.

And you were right... It was totally the time. System was not able to update the time server. I found the cause and did a manual ntp update and everything is back to normal. I am feeling like a moron right now for not checking that!

Thanks for your help.

mitu

@xman1 said in Retropie can no longer update from first boot:

I am feeling like a moron right now for not checking that!

One of the different things (from a PC) with a Raspberry Pi is the lack of a RTC on-board, the time is always set-up via NTP. Have fun with RetroPie !

xman1

@mitu Yep - I am so used to an RTC I didn't think about it. I'm a newb Pi user obviously.