Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#71596 - Package Search excluding staging packages

Attached to Project: Arch Linux
Opened by drws (drws) - Friday, 23 July 2021, 18:34 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 27 July 2021, 20:29 GMT
Task Type Bug Report
Category Web Sites
Status Assigned
Assigned To Jelle van der Waa (jelly)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No



Let's consider the buildbot package for example, as it is a currently-active case of this possible issue. If one searches for "buildbot" in Package Search, two categories of results are shown - exact and partial matches. As a newer version of buildbot is currently staging, Package Search shows both available versions. However, there is also a buildbot-common package and as expected, it is listed in the partially-matched section of results. However, more unexpectedly, only its older package version is shown there, but not the newer one, which is also currently in community-staging.

I propose that partially-matched results from staging repositories are included in Package Search results. Also, staging repositories are not available in Package Search filters. All in all, it seems that they are not fully implemented into the website.

Additional info / Steps to reproduce:
This task depends upon