Libretro cores wiped out? - RESTORED 👍
-
This is bad!. They didn't have enable 2FA?
-
More details about the whole matter:
-
One thing from the link above made me ponder:
This brings us onto another key issue – the lack of backups. We last performed a backup of our buildbot server about a couple of months ago. The truth is that while we pay a hefty amount for the servers on a monthly basis already, there is simply not enough money to pile on automated backups as well.
As a layman regarding coding and online repositories, but with a little user experience with local git clones, I wonder if a simple daily cronjob performing a
git clone <repo url>
or agit 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, although many service providers try very hard for us to think so. Or am I thinking too simple and there are more pieces of information on Github that are not covered by the
git
command? -
I updated a few things from source yesterday. I'm not saavy enough to know much, but I could upload my image if necessary. I'm not sure if there's any way I can help.
-
Most people working in these cores have a current copy. Like me https://github.com/mahoneyt944/mame2003-plus-libretro
Mame2003-plus is fine. Just needs copied back.
-
looks like a restore is in progress w/ likely GitHub and mx4w helped w/ the Main Retroarch Repo.
-
@mahoneyt944 said in Libretro cores wiped out?:
Most people working in these cores have a current copy. Like me
@CaelThunderwing said in Libretro cores wiped out?:
looks like a restore is in progress
I'm so happy that it sounds like there is going to be a quick turnaround on getting everything back to where it was.
-
@BuZz looks like most of the libretro cores are restored now. Git cloning should be fine now.
-
@mahoneyt944 thanks. The script was already modified earlier btw. It displays a warning on start only which I'll keep in place for a bit.
-
It happened to me with an official image of Retropie 4.6, I have no idea how to solve it.
-
@Edu281 update your retropie-setup script (option S):
-
I have done it as the colleague has said, in the image both the binaries and the entire package are hacked and send the warning
-
@Edu281 yes, it's a warning because this is an ongoing situation, but updating by binary and source should function as usual as libretro seem to have restored everything on git. the warning may be removed in the next few days.
-
I managed to solve it by putting the mame 2003 binary and also installing the mame 2003 plus
-
al final quite mame me salia el error
-
@Clyde said in Libretro cores wiped out? - RESTORED 👍:
I wonder if a simple daily cronjob performing a
git clone <repo url>
or agit 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
-
I have Formatted the micro sd at least six times, the Mame emulator hacking notice continues. Any solution?
-
@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.
-
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.
-
@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.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.