> and on the flagging  page itself,


here are the contents of the flagging page itself:



> Flag Package Out-Of-Date:    <name>

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

   <name>
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.

___________

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.

also i wonder what sort of personal obsession one would have to keep refreshing a page for posting the same message over and over? this not looks any different than stalking

On Wed, Nov 13, 2024 at 3:23 PM Doug Newgard <dnewgard@outlook.com> wrote:
On 11/13/24 8:10 AM, Robin Candau wrote:
> On 11/13/24 2:51 PM, Actionless Loveless wrote:
>> The field is designed for notifying the maintainer of the package when
>> a new release is available, not for reporting any other sort of
>> problems (for which there are other means of reporting).

As pointed out in both the thread you referenced and on the flagging
page itself, this is completely untrue for VCS packages. External
changes require changes to the PKGBUILD, which is the definition of out
of date for VCS packages.