MarsSeed [1] filed a deletion request for azure-cli-bin [2]: The azure-cli package has been added to Arch/extra repo in March 2024. I don't think it is very useful to keep this old-distro-targeting (Debian Bookworm), Python 3.11 based upstream build, which btw contains its own Python 3.11 runtimes (python3, pip, pbr, etc.) and binary+Python-module ecosystem in the install, with up to two hundred of its own Python modules. Also this PKGBUILD strips the upstream binaries, therefore the installed package is useless for crash reporting purposes. Upstream's binaries are also less secure than the Arch build, as the ELF files here lack full RELRO and PIE. The AUR package is also configured improperly: - It defines 'python' as its dependency, but it is not true, as I mentioned, this package installs its own /opt/az/bin/python3 symlink to the /opt/az/bin/python3.11 runtime. - Man viewing doesn't work in the AUR package, as the relevant files are installed inside /opt/az and not to their proper places inside '/usr/share'. - Bash completions get installed in the wrong place, inside /etc/bash_completon.d, instead of the expected '/usr/share/bash- completion/completions'. - It does not install the mandatory MIT license file. I am observing that there is a discrepancy in AUR PM decisionmaking regarding keeping or deleting upstream's binary releases from AUR when a source-based build gets added to the official Arch repos. I typically saw Arch Developers like @arojas, and Package Maintainers like @Antiz delete '-bin' counterparts of Arch repo packages from AUR, citing the reason that the in such cases the '-bin' builds do not add any meaningful benefit to users. I think this specific PKGBUILD has even stronger than typical reasons to be dropped from AUR. [1] https://aur.archlinux.org/account/MarsSeed/ [2] https://aur.archlinux.org/pkgbase/azure-cli-bin/