Hello Jingbei Li, On 4/13/23 19:43, Jingbei Li wrote:
Quoting Polarian <polarian@polarian.dev>:
I think people are forgetting that as a Maintainer you are meant to look into each update, read the change logs, check if there is any incompatibilities, patch out anything which is non-free (if possible) or patch any issues with the source which might not compile on Arch Linux for whatever reason, check new dependencies, check if dependencies have been removed, check if the compile procedure has changed, and thus the PKGBUILD will need rewriting, the list goes on.
Sure a PR to bump the release is always nice, but it should be checked against all the things I have named above, and then merged, then you push it manually.
If you don't have the time for the above? try maintaining less packages, or try finding more time, there is no cheat code to maintaining packages.
Is that an official statement, or your personal opinion? It sounds opinionated to me. I had a quick look at the AUR submission guidelines, but was unable to find anything on automation or required pre-update checks, at all. If you can point me to relevant documentation, I'd appreciate that a lot.
If you specifically seek for an official answer: Jelle hasn't used his official e-mail address, but there are two messages in this Thread from Jelle and me: - Jelle van der Waa <jelle@vdwaa.nl> - Levente Polyak <anthraxx@archlinux.org> Both of which you can consider official. Please deactivate your automation and fix the workflow. Thank you very much for your efforts and contributing to our community. Sincerely, Levente