As discussed in this thread:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/RZJPOB4PWNMDV25L5MUKSTGMRZAMQNPO/#RZJPOB4PWNMDV25L5MUKSTGMRZAMQNPO
Originally filed as pungi#1111.
The source repo is indeed empty and primary xml claims there are 0 packages. However I don't see how this could be an issue with Pungi, given that the updates compose looks different to that and is very much not empty. https://kojipkgs.fedoraproject.org/compose/updates/Fedora-29-updates-20190111.0/compose/Everything/x86_64/os/repodata/ The 20190109.2 is also correct.
I don't know what exactly happens to the compose once it finishes and how it gets to mirrors. I think it's either a problem in Bodhi or some sync script that's causing the data to go missing.
CC @nbecker
@adrian This is happening because the url https://mirrors.fedoraproject.org/metalink?repo=updates-released-source-f29&arch=x86_64 is resolving to http://...../fedora/linux/updates/29/Everything/source/tree/repodata/repomd.xml
Instead they should be pointing to http:/....../fedora/linux/updates/29/Everything/SRPMS/repodata/repomd.xml
This is fine for testing source repos, but its failing on stable source repos.
Similar problems have been reported multiple times already. This is a MirrorManager problem, kind of.
MirrorManager initially detected the repository 'updates-released-source' when it was first available. Unfortunately that is the repository at '29/Everything/source'. Once a repository is created in MirrorManager it will not change. So MirrorManager will not detect the same repository under a different path '29/Everything/SRPMS'.
To avoid situation like this in the future it is important that repository paths do not change.
This is now fixed and should be live in about 30 minutes. I would close the ticket, but it seems I cannot.
Thanks for the fix...
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.