25 ms·

Did someone fork the GH repo before it was taken down?

Lammy 3y ago
Boom https://archive.org/details/yuzu.7z https://archive.org/details/yuzu.7z (archived by me from a git mirror; all git remotes removed before zipping)
isoprophlex 3y ago
Seems to be up still... Edit: he's dead, Jim
- wingmanjd 3y ago
  Repo URL is now dead.
  - isoprophlex 3y ago
    Whoa, cloned it just in time, with literally minutes to spare!
    - xingped 3y ago
      Share if you can!
      - sleirsgoevy 3y ago
``` git clone https://github.com/irfanhakim-as/yuzu-mainline https://github.com/irfanhakim-as/yuzu-mainline git fetch origin 537296095ab24eddcb196b5ef98004f91de9c8c2 ``` It seems that GitHub still serves the commit history through the existing forks of the repo. According to archive.org, this commit corresponds to the last release of yuzu-mainline before the repo takedown: http://web.archive.org/web/20240304185516/https://github.com/yuzu-emu/yuzu-mainline/releases/tag/mainline-0-1734 http://web.archive.org/web/20240304185516/https://github.com...
kenmacd 3y ago
If you already have a copy of the original repo, add this as another remote with: ``` git remote add irfanhakim-as https://github.com/irfanhakim-as/yuzu-mainline https://github.com/irfanhakim-as/yuzu-mainline git fetch irfanhakim-as 537296095ab24eddcb196b5ef98004f91de9c8c2 ``` Then if you want the commit to look like the latest one for the original repo edit the file `.git/packed-refs`. Mine now looks like: ``` # pack-refs with: peeled fully-peeled sorted 537296095ab24eddcb196b5ef98004f91de9c8c2 refs/remotes/origin/master ``` (Be careful with raw editing git files. There might be a more 'official' way to do it, but this worked for me)
- mmebane 3y ago
  They started deleting repos a couple of minutes ago. I checked a lot of links and they were in the Internet Archive. I'm sure there are plenty of forks of the main repo.
yuzufan 3y ago
Cloned it a couple days ago. When you find a mirror, you can look for this commit, and know that if the commit hash matches it is probably a legit copy of the repo up until that point at least commit dc94882c9062ab88d3d5de35dcb8731111baaea2 (HEAD -> master) Merge: 30567a590 fc6a87bba Author: liamwhite <liamwhite@users.noreply.github.com> Date: Tue Feb 27 12:26:26 2024 -0500 Merge pull request #13135 from german77/hid-interface service: hid: Migrate HidServer to new IPC
- deleted 3y ago
  [deleted]
- BHSPitMonkey 3y ago
  Your clone seems to be 4 commits behind the version I'm seeing in most mirrors, which has the following HEAD: commit 15e6e48bef0216480661444a8d8b348c1cca47bb (HEAD -> master, origin/ma ster, origin/HEAD) Merge: dc94882c9 2f57c5a0e Author: Narr the Reg <juangerman-13@hotmail.com> Date: Fri Mar 1 01:57:00 2024 -0600 Merge pull request #13198 from zhaobot/tx-update-20240301020652 Update translations (2024-03-01)
chatmasta 3y ago
FYI, forks don't survive DMCA purges. You need to clone a repo and then push it to a new repository.
- KomoD 3y ago
  Yuzu deleted the repos themselves so all the forks still exist for now, just with another upstream. (in the case of the main repo: roblabla/yuzu) But yeah they'll be gone soon (making a repo without fork won't help either.)
  - chatmasta 3y ago
    > making a repo without fork won't help either It'll definitely get purged, but I think in this case the rightsholder needs to submit a separate DMCA request. Regardless, if you want the code, cloning it to a local storage medium is always the most robust option :)
    - KomoD 3y ago
      > but I think in this case the rightsholder needs to submit a separate DMCA request. No you can actually do multiple in one request. > Regardless, if you want the code, cloning it to a local storage medium is always the most robust option :) 100%, that is the way to go.
KomoD 3y ago
Software Heritage has it archived. https://archive.softwareheritage.org/browse/search/?q=github.com%2Fyuzu-emu%2F&with_visit=true&with_content=true https://archive.softwareheritage.org/browse/search/?q=github...
- xingped 3y ago
  Hadn't heard of this site before but thank you so much!
justinclift 3y ago
There look to be an awful lot of forks created in the last week: https://github.com/roblabla/yuzu/forks?include=active&page=1&period=2y&sort_by=last_updated https://github.com/roblabla/yuzu/forks?include=active&page=1... Considering the ongoing attacks against GitHub whereby people are creating repos with malicious code, it's probably wise to be bloody careful of any of these yuzu forks. :( :( :(
- BHSPitMonkey 3y ago
  I see several on GitLab.com with identical commit histories, for what it's worth.
  - justinclift 3y ago
    Cool, that could be a good reference point. :)
npteljes 3y ago
Just to add my two cents, software repositories like Ubuntu's still have the thing, with the source and the build readily downloadable. Not the latest, but still. https://packages.ubuntu.com/mantic/yuzu https://packages.ubuntu.com/mantic/yuzu

Boom https://archive.org/details/yuzu.7z https://archive.org/details/yuzu.7z (archived by me from a git mirror; all git remotes removed before zipping)

isoprophlex 3y ago

Seems to be up still... Edit: he's dead, Jim

wingmanjd 3y ago
Repo URL is now dead.
- isoprophlex 3y ago
  Whoa, cloned it just in time, with literally minutes to spare!
  - xingped 3y ago
    Share if you can!
    - sleirsgoevy 3y ago
``` git clone https://github.com/irfanhakim-as/yuzu-mainline https://github.com/irfanhakim-as/yuzu-mainline git fetch origin 537296095ab24eddcb196b5ef98004f91de9c8c2 ``` It seems that GitHub still serves the commit history through the existing forks of the repo. According to archive.org, this commit corresponds to the last release of yuzu-mainline before the repo takedown: http://web.archive.org/web/20240304185516/https://github.com/yuzu-emu/yuzu-mainline/releases/tag/mainline-0-1734 http://web.archive.org/web/20240304185516/https://github.com...
- kenmacd 3y ago
  If you already have a copy of the original repo, add this as another remote with: ``` git remote add irfanhakim-as https://github.com/irfanhakim-as/yuzu-mainline https://github.com/irfanhakim-as/yuzu-mainline git fetch irfanhakim-as 537296095ab24eddcb196b5ef98004f91de9c8c2 ``` Then if you want the commit to look like the latest one for the original repo edit the file `.git/packed-refs`. Mine now looks like: ``` # pack-refs with: peeled fully-peeled sorted 537296095ab24eddcb196b5ef98004f91de9c8c2 refs/remotes/origin/master ``` (Be careful with raw editing git files. There might be a more 'official' way to do it, but this worked for me)
mmebane 3y ago
They started deleting repos a couple of minutes ago. I checked a lot of links and they were in the Internet Archive. I'm sure there are plenty of forks of the main repo.

yuzufan 3y ago

Cloned it a couple days ago. When you find a mirror, you can look for this commit, and know that if the commit hash matches it is probably a legit copy of the repo up until that point at least commit dc94882c9062ab88d3d5de35dcb8731111baaea2 (HEAD -> master) Merge: 30567a590 fc6a87bba Author: liamwhite <liamwhite@users.noreply.github.com> Date: Tue Feb 27 12:26:26 2024 -0500 Merge pull request #13135 from german77/hid-interface service: hid: Migrate HidServer to new IPC

deleted 3y ago
[deleted]
BHSPitMonkey 3y ago
Your clone seems to be 4 commits behind the version I'm seeing in most mirrors, which has the following HEAD: commit 15e6e48bef0216480661444a8d8b348c1cca47bb (HEAD -> master, origin/ma ster, origin/HEAD) Merge: dc94882c9 2f57c5a0e Author: Narr the Reg <juangerman-13@hotmail.com> Date: Fri Mar 1 01:57:00 2024 -0600 Merge pull request #13198 from zhaobot/tx-update-20240301020652 Update translations (2024-03-01)

chatmasta 3y ago

FYI, forks don't survive DMCA purges. You need to clone a repo and then push it to a new repository.

KomoD 3y ago
Yuzu deleted the repos themselves so all the forks still exist for now, just with another upstream. (in the case of the main repo: roblabla/yuzu) But yeah they'll be gone soon (making a repo without fork won't help either.)
- chatmasta 3y ago
  > making a repo without fork won't help either It'll definitely get purged, but I think in this case the rightsholder needs to submit a separate DMCA request. Regardless, if you want the code, cloning it to a local storage medium is always the most robust option :)
  - KomoD 3y ago
    > but I think in this case the rightsholder needs to submit a separate DMCA request. No you can actually do multiple in one request. > Regardless, if you want the code, cloning it to a local storage medium is always the most robust option :) 100%, that is the way to go.

KomoD 3y ago

Software Heritage has it archived. https://archive.softwareheritage.org/browse/search/?q=github.com%2Fyuzu-emu%2F&with_visit=true&with_content=true https://archive.softwareheritage.org/browse/search/?q=github...

xingped 3y ago
Hadn't heard of this site before but thank you so much!

justinclift 3y ago

There look to be an awful lot of forks created in the last week: https://github.com/roblabla/yuzu/forks?include=active&page=1&period=2y&sort_by=last_updated https://github.com/roblabla/yuzu/forks?include=active&page=1... Considering the ongoing attacks against GitHub whereby people are creating repos with malicious code, it's probably wise to be bloody careful of any of these yuzu forks. :( :( :(

BHSPitMonkey 3y ago
I see several on GitLab.com with identical commit histories, for what it's worth.
- justinclift 3y ago
  Cool, that could be a good reference point. :)

npteljes 3y ago

Just to add my two cents, software repositories like Ubuntu's still have the thing, with the source and the build readily downloadable. Not the latest, but still. https://packages.ubuntu.com/mantic/yuzu https://packages.ubuntu.com/mantic/yuzu