> As an additional sidenode, if the issue you want to report is that the package is

> broken because it can't be built, the maintainer has already highlighted that it is due

> to gcc update, and they are awaiting upstream to patch the issue. That was posted 3

> days ago so I assume it is still valid right now as I do not see any recent commits to

> the AUR for this package. (not since 2023-04-18)

This is indeed what I'm talking about, sorry I should've read the comments on Aurweb
before posting here. Since the problem has already been reported, I feel like there's no more to do but waiting if the maintainer is willing to backport the patch.

I totally understand that packages may break, I was kind of wondering why upstream would have released a non-compiling version, but I have the explanation now.

Have a good day/night,
Mirkwood