[PRQ#65420] Deletion Request for electron33-bin
BryanLiang [1] filed a deletion request for electron33-bin [2]: electron33 has been provided in the Extra repo. [1] https://aur.archlinux.org/account/BryanLiang/ [2] https://aur.archlinux.org/pkgbase/electron33-bin/
AUR rules don’t forbid binary packages corresponding to stock ones built from the source.
On 6 Nov 2024, at 13:49, notify@aur.archlinux.org wrote:
BryanLiang [1] filed a deletion request for electron33-bin [2]:
electron33 has been provided in the Extra repo.
[1] https://aur.archlinux.org/account/BryanLiang/ [2] https://aur.archlinux.org/pkgbase/electron33-bin/
Request #65420 has been Accepted by Muflone [1]: please avoid to upload packages already existing in the repositories. even if rules don't forbid it, make sure to have solid reasons to do that [1] https://aur.archlinux.org/account/Muflone/
Similar questions arise about once every half-year for electronNN-bin AUR packages, where NN is from 2 to 34 and was answered many times, so I thought it’s a known fact that these packages have a different release cycle. For example, electon33-bin was uploaded with the very first electron33 alpha on 2024-08-21, 55 days before the first commit[0] in a stock electon33 package on 2024-10-15, and it will remain in AUR for many years after the stock repo drops the electron33, just like electron2-bin[1]. [0] https://gitlab.archlinux.org/archlinux/packaging/packages/electron33/-/commi... [1] https://aur.archlinux.org/packages/electron2-bin
participants (2)
-
notify＠aur.archlinux.org
-
Yurii Kolesnykov