On Thu, Aug 25, 2022 at 09:04:57PM +0200, Claudia Pellegrino via aur-general wrote:
Hi Leonidas,
What stops you from opening bug report and submitting patches for those now without being a TU? If these are in core/extras your options would be the same as you have now, right?
Wait, is this actually a thing?
As a non-TU, one thing that has deterred me from using the bug tracker to submit patches for outdated packages is this warning:
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
followed by:
REPEAT: Do NOT report bugs for outdated packages!
and similarly, on the wiki:
Reasons for not being a bug […] A package which is not-up-to-date. Use the Flag Package Out-of-Date feature on Arch's packages website.
That’s a total of three warnings. Enough for me to decide to not take chances. Your suggestion seems to contradict those warnings though. What am I missing?
I think it's worth separating a package update (most often it's just a change to pkgver and hash sums) and fixing a bug, improving pkgbuild, or adding features. as a maintainer, I would like to receive the second and never see the first.
Regards Claudia (aka Auerhuhn)
-- Sincerely, Alexander | Trusted User