Change:
{ branch <del> , libsForQt5 </del> <ins> , qt6Packages </ins> , fetchFromGitHub , fetchurl }: let <del> # Fetched from https://api.citra-emu.org/gamedb, last updated 2022-05-02 </del> <ins> # Fetched from https://api.citra-emu.org/gamedb </ins> # Please make sure to update this when updating citra! compat-list = fetchurl { name = "citra-compat-list"; <del> url = "https://web.archive.org/web/20220502114622/https://api.citra-emu.org/gamedb/"; sha256 = "sha256-blIlaYaUQjw7Azgg+Dd7ZPEQf+ddZMO++Yxinwe+VG0="; </del> <ins> url = "https://web.archive.org/web/20230512234055/https://api.citra-emu.org/gamedb/"; hash = "sha256-J+zqtWde5NgK2QROvGewtXGRAWUTNSKHNMG6iu9m1fU="; </ins> }; in { <del> nightly = libsForQt5.callPackage ./generic.nix rec { </del> <ins> nightly = qt6Packages.callPackage ./generic.nix rec { </ins> pname = "citra-nightly"; <del> version = "1873"; </del> <ins> version = "1907"; </ins> src = fetchFromGitHub { owner = "citra-emu"; repo = "citra-nightly"; rev = "nightly-${version}"; <del> sha256 = "1csn9n1s2mvxwk2mahwm8mc4zgn40im374hcsqgz8gaxjkmnx288"; </del> <ins> sha256 = "l4pqok42/ybnRX90Qwhcgm2JR4/9C5bbCTk3j4QuWtw="; </ins> fetchSubmodules = true; }; inherit branch compat-list; }; <del> canary = libsForQt5.callPackage ./generic.nix rec { </del> <ins> canary = qt6Packages.callPackage ./generic.nix rec { </ins> pname = "citra-canary"; <del> version = "2440"; </del> <ins> version = "2484"; </ins> src = fetchFromGitHub { owner = "citra-emu"; repo = "citra-canary"; rev = "canary-${version}"; <del> sha256 = "06f2qnvywyaf8jc43jrzjhfshj3k21ggk8wdrvd9wjsmrryvqgbz"; </del> <ins> sha256 = "IgCpqt3rKV9IqNstF4QwnJlE3hPH+BkIhaOvEmshh0U="; </ins> fetchSubmodules = true; };

Discussion:
Attempting to install (3DS Emulator) and (Switch Emulator) at the same time is not currently possible without changing the priority of one of the packages. Correct me if I'm wrong, but shouldn't the cmake files not be included in the final output, for either package? Steps to reproduce the behavior: to install both packages side by side They install and work side by side. (They did previously, I'm not sure exactly when that stopped being the case) I'm installing both via Home Manager, but afaik that shouldn't cause any huge issues. Both packages seem to be maintained by the same four people: ashley / ivar / joshuafern / sbruder / <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result.
I take it this is an upstream issue?
No idea. I just know they're not there anymore. Maybe this? Comparing:

Package name: citra-canary Latest released version: 2399 <!-- Search your package here: --- Current version on the unstable channel: 2146 Current version on the stable/release channel: 2146 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.

Package name: citra-nightly Latest released version: 1843 <!-- Search your package here: --- Current version on the unstable channel: 1765 Current version on the stable/release channel:1765 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.