Libretro cores wiped out? - RESTORED 👍
-
Just checking mame2003-plus core on github and it's been wiped out along with many other libretro cores.... what's going on here?
-
@mahoneyt944 hacked, apparently. DO NOT go to the libretro website...
-
-
I can't do anything about existing installs but have disabled git cloning any libretro repo if updating retropie, to avoid any issues.
If someone updates a libretro core from source without updating retropie they may have issues until this is resolved.
Thanks for the heads up.
-
Based on the destruction on github... I think someone had access rights to the repositories but didn't have libretro's main account to delete them. You need the main account's password for that. They removed all the commits with their access rights. Seems foolish.
I just happen to have a full copy of mame2003-plus just before the loss because I was working on the core. So it will live on once it's all sorted.
-
Ah damn! I had finally got linux installed on my machine to have a go at the X86 version and now pretty much all the emulators I use aren't available! My condolences to them :(
-
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 masterto 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
gitcommand? -
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
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.