I opened a duplicate at https://pagure.io/pagure/issue/4676. Some notes from there:

The version table on src.fp.o seems to request information from Bodhi, but F31 had some period where nothing went through it and packages were directly tagged into f31. For packages which have not had any updates since then, the table incorrectly shows the previous version for F31, but not the other releases.

This may be the case for librealsense as well, but there are so many module builds, it's hard to tell (and that itself may be a different cause for the error).

Yes, that may be the case here. Some background about librealsense: Upstream bumps the soname on every minor release, thus the package rarely gets updates to release branches. All updates only land in rawhide and are forked into the new release branch. This is also why we provide a module that always contains the latest version for all branches.

It's still surprising to see librealsense1 here, it's an entirely different package. The librealsense/librealsense split happened back in Fedora 28: https://fedoraproject.org/wiki/Changes/librealsense2

See also duplicate https://pagure.io/pagure/issue/4688

Another:

Another one is https://src.fedoraproject.org/rpms/libgit2

All those cases are due to an incorrect match of mdapi, so I opened an issue there: https://pagure.io/mdapi/issue/96

Another one is https://src.fedoraproject.org/rpms/tin .

We've reduced the issue but it isn't quite fixed yet.

Alright, I think the version that we have in mdapi now solves this problem.

Let's close this ticket and re-open if we see this again :)

Thanks for all your contributions fine folks! :)