so in that case - if you're sure that it's not a bug (or result of that lib being previously provided as a dependency of dependency of that package), but a result of upstream change - new release / commit which introducing that change

On Wed, Nov 13, 2024 at 3:41 PM Doug Newgard <dnewgard@outlook.com> wrote:

On 11/13/24 8:32 AM, Actionless Loveless wrote:
>  > and on the flagging  page itself,
<snip>
> i don't see anything here  suggesting that there are some rule
> exemptions for a VCS package. if you have another reliable source, feel
> free to quote&link that.

The full text when flagging a VCS package:

Use this form to flag the package base <pkgbase>-git and the following
packages out-of-date:

<pkgname>-git
This seems to be a VCS package. Please do not flag it out-of-date if the
package version in the AUR does not match the most recent commit.
Flagging this package should only be done if the sources moved or
changes in the PKGBUILD are required because of recent upstream changes.

Please do not use this form to report bugs. Use the package comments
instead. Enter details on why the package is out-of-date below,
preferably including links to the release announcement or the new
release tarball.

Your PKGBUILD was fine, then changes were made upstream and it is no
longer fine, hence it's out of date.