Pending on apps.fedoraproject.org/packages/ being up. (I might end up using mdapi directly, just want to investigate using something more pleasant, like pkgwat.api)

Note that apps.fedoraproject.org/packages is notoriously known for missing packages.

Not only is apps.fedoraproject.org/packages often wrong, it's a tertiary source; definitely better to check mdapi directly. The further away you get from the true database, the more likely you'll find issues.

@qulogic sorry for letting this slip. Would you be willing/able to elaborate and/or point us to examples/relevant docs for using mdapi to get the relevant information? Thank you!

There's a description of the API on the mdapi front page https://mdapi.fedoraproject.org/

Or you could see what Pagure does: https://pagure.io/pagure/blob/master/f/pagure/themes/srcfpo/templates/repo_info.html#_503

Ah, OK. For some reason I went straight to the git repo, and tried to make sense of that, while missing on the fact that it is a service to be used, well I guess that happens :) Thanks!

PR with fix for backend: https://pagure.io/fedora-qa/oraculum/pull-request/54#

FYI: I am using pagure's api ( https://src.fedoraproject.org/_dg/bodhi_updates/rpms/%s ) for this as I found mdapi contains pretty old information for some cases/packages (especially versions in updates). mdapi is used just for cases where pagure returns None for version in Fedora XX / stable.

Commit faccb60f fixes this issue

Pending on frontend now...

Package versions are now shown as tooltip, just hover over the package name:

Nice! Thanks.

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/apps/packager_dashboard/issues/24

Please continue any further discussion there.