This only affects packages where the SRPM name and the RPM name do not match, requiring the "slow lookup" method.
This appears to be because only the latest version of the package is represented in the repodata.xml, even though all previous versions are present in the repository.
Also, when loading the repodata for the binary files to do the lookup, some aarch64 directories are sneaking in there, and should be omitted.
Steps to reproduce
Attempt to retrieve sources for an RPM in their tree that has since been superseded by a newer RPM:
Expected result
Actual behavior
Errata
This only affects packages where the SRPM name and the RPM name do not match, requiring the "slow lookup" method.
This appears to be because only the latest version of the package is represented in the
repodata.xml
, even though all previous versions are present in the repository.Also, when loading the repodata for the binary files to do the lookup, some
aarch64
directories are sneaking in there, and should be omitted.