Change:
yacc = bison; # moved from top-level 2021-03-14 yafaray-core = libyafaray; # Added 2022-09-23 yarn2nix-moretea-openssl_1_1 = throw "'yarn2nix-moretea-openssl_1_1' has been removed."; # Added 2023-02-04 <ins> ytmdesktop = throw "ytmdesktop was removed because upstream vanished"; # added 2024-03-24 </ins> yubikey-manager4 = throw "yubikey-manager4 has been removed, since it is no longer required by yubikey-manager-qt. Please update to yubikey-manager."; # Added 2024-01-14 yuzu-ea = throw "yuzu-ea has been removed from nixpkgs, as it has been taken down upstream"; # Added 2024-03-04 yuzu-early-access = throw "yuzu-early-access has been removed from nixpkgs, as it has been taken down upstream"; # Added 2024-03-04

Discussion:
Project's repository no longer exist. (last person to edit the derivation's definition) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Looks like the account was hacked and shut down for a little bit.
Hi. Is it possible to reverse this now that the Organisation is back? Am looking also into updating to our latest v2.0.5 version as well and ideally automating the process as much as possible so a release will automatically push to here.
(I was the package maintainer, before it was deleted, but I personally haven't used ytmdesktop for quite some time now, because v1 had some known issues on my setup. I would like to switch back to it with v2 being out, tho) I think we could revert the commit, but it probably makes more sense to just create a new package with the v2 version. Also, if we do re-add v1, we probably need to mark it as insecure as it has some EOL dependencies iirc. I tried packaging v2 some time ago, but didn't get anywhere due to my lack of js/electron experience. The workaround I used for v1, just re-packaging the appimage, is no longer possible, as you stop releasing appimages. If there is an appimage release of v2, I could probably create a simple v2 package and then also maintain that. Though, I don't know how much effort maintaining an additional release format upstream is for you. Sadly, I currently don't have the time to figure out how to package ytmdesktop from source, but maybe someone else is willing and able to do that. Adding (mostly) automatic updates, once we have a working v2 packages, shouldn't be hard with and the related infrastructure in nixpkgs. (Though, I personally have no experience with that yet.)
Thank you for the work in helping maintain the package and Thanks for the info regarding packaging. With the usage of Electron Forge instead of Electron Builder, we've also changed how packaging works. Stuff like: Flatpak and Snap editions exist, but sadly how Linux packages are existing builders which exist.

(electron-forge-maker-appimage)[] suggests there is also an App image builder but it apperas to just be a basic proxy to Electron builder~ Otherwise building Linux Applications is a whole new thing for me, and given we've basically reset the entire codebase to fix a number of underlying issues, there's likely lots of bits which still need poking at again which didn't exist before.
I opened a PR for re-initializing ytmdesktop: Also, while I managed to get ytmdesktop to build from source using , whenever I used I would get some strange TLS cert errors, despite passing the flag. In the end, I gave up on building it from source, since I realized that with a small patch to the source code I could just extract the assets from any of the releases and reuse them everywhere (it's all just JS and bitmaps :manshrugging:). <details<summaryFor anyone who cares about building it from source and investigating that TLS error, here is where I left off with that </summary</details