Testing of Flatpak-1.6 against the internal container registry, registry.redhat.io, and registry.redhat.com revealed some defects that it would be good to fix for 8.2.
* flatpak cannot authenticate to the internal container registry, blocking testing of whether installing the Flatpaks we will ship in 8.2 from a registry works correctly:
* downloading registry.redhat.io after prompting the user for username/password is twice as slow as it needs to be:
Switched from blocker to exception, since harm is is fairly modest:
- installing Flatpaks from container registries would be less responsive and possibly look buggy
- pre-release testing would be harder.
Risks of these fixes should, however, also be small - they are small self-contained patches that only affect the installing-from-OCI registries code paths.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.