If you go to registry.fedoraproject.org and click on any of the entries (e.g., 0ad -> https://registry.fedoraproject.org/repo/0ad/tags/). This returns a 304, and nothing else.
Maybe this is useful for an API or something, but if there's nothing here, then the front page shouldn't link to it.
If you go to registry.fedoraproject.org and click on any of the entries (e.g., 0ad -> https://registry.fedoraproject.org/repo/0ad/tags/). This returns a 304, and nothing else. Maybe this is useful for an API or something, but if there's nothing here, then the front page shouldn't link to it.
Yes this a flatpak and the upstream[0] we are using for registry.fp.o does not support displaying tags for flatpak.
I am not sure there is much we can do there. Except if someone volunteers to do the work upstream.
[0] - https://github.com/genuinetools/reg
ISTR an email saying registry.fp.o might move to quay.io? So spending time on that might not be fruitful in the end.
This happens because flatpaks return OCI indexes instead of image manifests in the /v2/NAME/manifests/TAG endpoint.
/v2/NAME/manifests/TAG
Someone opened a PR to start dealing with this issue here: https://github.com/genuinetools/reg/pull/202
After this gets merged, we'd need to make reg also accept OCI indexes.
Login to comment on this ticket.