Hey (I hope I'm replying to this the right way), so, if the AUR maintainers think that the package should be removed, then it can be removed. It is my first AUR package so I may have misunderstood when I should actually create a new package vs contact the maintainers. The reason why I didn't contact the "discord-canary" maintainers is because my fix is a workaround to a bug on the original deb (as provided by Discord) Discord Canary package. My fix, however, does conflict with the original Discord installation, so you wouldn't be able to have "discord" and "discord-canary" installed on the same machine, which is why I thought it would be better to upload as a new package instead of trying to patch the original package (which could break some users workflows). The bug is that it seems that Discord hardcodes somewhere "discord.desktop" in the Discord source code, so all notifications and the unread notification badge relies on the "discord.desktop" file name but, because the "discord-canary" package uses the "discord-canary.desktop" (Which isn't wrong mind you! That's the name of the file inside the original deb package!) notifications are bound to an unknown application (so you can't disable them in KDE Plasma Notifications panel) and unread notifications badges do not work even if you have libunity installed. In fact I did provide a workaround to the bug in the original "discord-canary" package comments, however my workaround was not *that* great because it does break every time a new Discord Canary update is released, due to my DE (KDE Plasma) preferring the updated package desktop file instead of using the "discord.desktop" copy until the system is restarted or the local desktop cache refreshed. So I've decided to patch it on the PKGBUILD level. About the name: It was inspired by the "discord-canary-with-flags" package name. I couldn't figure out a better name for it because the package does what it says on the tin, I also didn't want to use a vague name like "discord-canary-fix" because that would feel very sketchy (see the names used by malicious AUR packages). So it is a conundrum of: "Should this be fixed in the original package and break users that have both discord and discord-canary installed, or should I create my own package for the users that understand the drawbacks?" But anyway, if the package feels like it can be removed, feel free to go ahead with it. I do understand that my package is, for all intents and purposes, just a clone of the current "discord-canary" package with a fix that, honestly, I think that only myself cares about. Em qui., 24 de jul. de 2025 às 15:35, <notify@aur.archlinux.org> escreveu:

yochananmarqos [1] filed a deletion request for discord-canary-with- stable-dot-desktop [2]:

Unnecessary duplicate of discord-canary. If there is an issue with the existing package, contact the Maintainer instead of creating a duplicate with such a minor change. Also, the package name is ridiculous.

[1] https://aur.archlinux.org/account/yochananmarqos/ [2] https://aur.archlinux.org/pkgbase/discord-canary-with-stable-dot-desktop/