Libretro cores wiped out? - RESTORED 👍

A Former User

al final quite mame me salia el error

meleu

@Clyde said in Libretro cores wiped out? - RESTORED 👍:

I wonder if a simple daily cronjob performing a git clone <repo url> or a git pull origin master to a local repo clone that's backed up differentially should have saved everything that's now gone.

In other words, not everything has to be bought as a service (...)

Maintaining regular backups for over 250+ repositories locally would require a good amount of effort, bandwidth and storage.

Also, the buildbot is a tool that requires good processing power. Because it is/was "constantly" getting the code from all those repositories and building them for a wide range of target platforms. Namely:

Windows (including Vista/XP, 2000/ME, 98/95)
Linux
Raspberry Pi
Android
iOS
macOS
Xbox One
Playstation Vita, 2, 3, 4 and PSP
Nintendo Switch, Wii, Wii U, and 3DS/2DS
GameCube

As you can see, they do need a robust infrastructure to keep everything up and running. Providing everything for free for any retrogaming fan around the globe.

That being said, I emphatically suggest that every retrogamer at least consider making a donation to the libretro project.

Here are the links:

https://patreon.com/libretro
https://github.com/sponsors/libretro
more options are listed here: http://retroarch.com/index.php?page=donate

A Former User

I have Formatted the micro sd at least six times, the Mame emulator hacking notice continues. Any solution?

dankcushions

@Edu281 like i keep saying, it's a warning. it's staying there until retropie chooses to turn it off in the script, when the situation is fully resolved. updates and by binary and source should still happen.

BuZz

Not sure why it's such a problem. It's an informative warning and it only shows when launching RetroPie-Setup. Just ignore it but keep it in mind if anything fails to install.

mahoneyt944

@BuZz
I think what @Clyde was suggesting was for the libretro team to make a secondary GitHub account / repository that's only purpose was to fork every libretro core regularly via script to serve as a "backup". This could actually work, it just wouldn't be a local copy. Obviously has it's limitations but could be a saver in a pinch, since the forks would have all the files and commit history.

Either way things are getting back to normal. Glad to see libretro back up.

BuZz

@mahoneyt944 Sorry - misunderstanding. I was replying about the warning msg to @Edu281

Clyde

@meleu said in Libretro cores wiped out? - RESTORED 👍:

I emphatically suggest that every retrogamer at least consider making a donation to the libretro project.

Done ($5/mth on Github). Thanks for the links and the encouragement. 👍

@mahoneyt944 said in Libretro cores wiped out? - RESTORED 👍:

@BuZz
I think what @Clyde was suggesting was for the libretro team to make a secondary GitHub account / repository

Actually no, I meant a local backup via git clone. But @meleu explained very elaborately the problems with it.

meleu

Guess who's back!
http://buildbot.libretro.com/
🦾

meleu

I asked the libretro's leadership and they said the buildbot server online is not the definitive one yet.

Anyways, I was in the RAPodcast again, this time trying to explain to users what happened with the libretro's infrastructure.

I also brought some curiosities about the project's innerworks, in a hope to bridge the gap between end-users and the crazy nerds who develop the tools we love.

If you want to check it out, here's the link: