New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Composing flatpaks does not work because they use a different repo name in Fedora #2658
Labels
Crash
Issues related to an unhandled crash
High priority
These issues are higher priority than normal
Comments
bowlofeggs
added
High priority
These issues are higher priority than normal
Crash
Issues related to an unhandled crash
labels
Oct 9, 2018
owtaylor
added a commit
to owtaylor/bodhi
that referenced
this issue
Oct 9, 2018
Instead of hardcoding that a registry image is at <release>/<name>, look it up via the registry metadata that OSBS writes. Fixes fedora-infra#2658
owtaylor
added a commit
to owtaylor/bodhi
that referenced
this issue
Oct 9, 2018
Instead of hardcoding that a registry image is at <release>/<name>, look it up via the registry metadata that OSBS writes. Fixes fedora-infra#2658 Signed-off-by: Owen W. Taylor <otaylor@fishsoup.net>
bowlofeggs
pushed a commit
to owtaylor/bodhi
that referenced
this issue
Oct 23, 2018
Instead of hardcoding that a registry image is at <release>/<name>, look it up via the registry metadata that OSBS writes. Fixes fedora-infra#2658 Signed-off-by: Owen W. Taylor <otaylor@fishsoup.net>
bowlofeggs
pushed a commit
to owtaylor/bodhi
that referenced
this issue
Oct 23, 2018
Instead of hardcoding that a registry image is at <release>/<name>, look it up via the registry metadata that OSBS writes. Fixes fedora-infra#2658 Signed-off-by: Owen W. Taylor <otaylor@fishsoup.net>
owtaylor
added a commit
to owtaylor/bodhi
that referenced
this issue
Oct 31, 2018
Instead of hardcoding that a registry image is at <release>/<name>, look it up via the registry metadata that OSBS writes. Fixes fedora-infra#2658 Signed-off-by: Owen W. Taylor <otaylor@fishsoup.net>
owtaylor
added a commit
to owtaylor/bodhi
that referenced
this issue
Nov 5, 2018
Instead of hardcoding that a registry image is at <release>/<name>, look it up via the registry metadata that OSBS writes. Fixes fedora-infra#2658 Signed-off-by: Owen W. Taylor <otaylor@fishsoup.net>
mergify bot
pushed a commit
that referenced
this issue
Nov 5, 2018
Instead of hardcoding that a registry image is at <release>/<name>, look it up via the registry metadata that OSBS writes. Fixes #2658 Signed-off-by: Owen W. Taylor <otaylor@fishsoup.net>
This feature is planned for inclusion in the upcoming 3.11.0 release: #2709 |
This patch has been deployed to Bodhi's staging environment: https://bodhi.stg.fedoraproject.org Please test and let us know if you find issues! |
This fix is now deployed to Fedora's production instance. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Crash
Issues related to an unhandled crash
High priority
These issues are higher priority than normal
@owtaylor and I tested a flatpak compose today in Bodhi's staging, and found that it fails to find the flatpak in the registry because it expects it to have the Fedora version prepended into the repository name:
The URL should not have had that
f29/
added beforeflatpak-runtime
, but that is hardcoded into Bodhi since containers have it.@owtaylor suggested that we could use the Koji metadata to know the name of the registry repository instead of hardcoding it. For example, https://koji.stg.fedoraproject.org/koji/buildinfo?buildID=1137170 tells us that
candidate-registry.stg.fedoraproject.org/flatpak-runtime:f29-20181008180041.2
is a pull URL. This works for containers too:The text was updated successfully, but these errors were encountered: