As a short term fix we can adjust the message of that to say: "If this package was already rebuilt and the issue is fixed, please close this Bugzilla."

Note that in both linked cases, the packages have been built after the bugzilla was opened, hence the original report was not wrong. But yes, the "your package has not been built successfully in 32" message is indeed wrong. It is also wrong if the package was once built in 32 but fails now.

So I suggest to replace:

your package has not been built successfully in 32. Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. Following the latest policy for such packages [2], your package
will be orphaned if this bug remains in NEW state more than 8 weeks.

To:

your package has an open Fails To Build From Source bug. Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.
Following the latest policy for such packages [2], your package
will be orphaned if this bug remains in NEW state more than 8 weeks.

Side note: Closing the Bugzilla if the build has happened after it was filed is actually nicer UX, but I'm afraid it would require much bigger effort :(

Yes that change would at least correct the false claim.

I didn't mean to complain about the original reports. I didn't need them in this case as I had already received other notifications, but that's OK. I do think I shouldn't have to close them manually though. I think any automation that files bug reports should also close them when it can be automatically determined that the problem is fixed.

I think any automation that files bug reports should also close them when it can be automatically determined that the problem is fixed.

I agree on principle. However in practice, this just have not been done. The automation that was supposed to do this is somewhat broken and nobody has the time to look into it :(

The script is: https://pagure.io/releng/blob/master/f/scripts/mass-rebuild-close-bugs.py

https://pagure.io/releng/pull-request/9290

This was merged.