There are four AUR packages all delivering the same ZCode application ( https://zcode.ai):
| Package | Version | Votes | Maintainer | |---|---|---|---| | `z-code-bin` | 3.1.4-2 | 2 | czy | | `zcode-desktop-bin` | 3.1.4-1 | 2 | duanluan | | `zcode-bin` | 3.1.2-3 | 1 | AnRan | | `zcode-appimage` | 3.1.5-1 | 0 | Xefreh | The AUR submission guidelines state: > Check the AUR if the package already exists. If it is currently > maintained, changes can be submitted in a comment for the maintainer's > attention. If it is unmaintained or the maintainer is unresponsive, the > package can be adopted and updated as required. Do not create duplicate > packages. > > — https://wiki.archlinux.org/title/AUR_submission_guidelines `z-code-bin` existed first and is actively maintained. The three later packages are clear duplicates that violate the guidelines above: they share the same upstream binary and purpose, with no technical distinction beyond the AppImage variant's packaging format. I attempted to resolve this via deletion requests: - PRQ#82994 (`zcode-bin`) — rejected (2026-06-18) - PRQ#82995 (`zcode-desktop-bin`) — rejected (2026-06-18) - PRQ#83110 (`zcode-appimage`) — closed (2026-06-23) All were rejected or closed yet we still have 4 packages for the same application. Additionally, `zcode-desktop-bin` claims to "repack from the official macOS release", not appropriate for an Arch Linux package and misleading to users. I'm asking a TU to: 1. Merge `zcode-bin` and `zcode-desktop-bin` into `z-code-bin`. 2. Delete the leftover packages. 3. Rule on whether `zcode-appimage` should also be merged or if AppImage packaging is considered distinct enough to coexist with `-bin`. Currently, it's the same upstream binary in a different archive format, and submitting it as a new package when `z-code-bin` already existed appears to violate the "Do not create duplicate packages" rule.) — bermudi
