Please update OSBS buildroot to include flatpak-module-tools-0.11.3-3.el7 (or is it running Fedora? any of the flatpak-module-tools-0.11.3-3.fc30-fc33 builds then). The new flatpak-module-tools build is needed to fix generated flatpak runtimes to work correctly with flatpak 1.7.x on the client side (see https://bugzilla.redhat.com/show_bug.cgi?id=1822753)
Metadata Update from @mohanboddu: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: groomed, low-trouble, medium-gain
Pinging @cverna, would be good to get a howto or sop out of it.
Metadata Update from @cverna: - Issue assigned to cverna
I have created a playbook to do that and documented it in https://pagure.io/fedora-infra/howtos/blob/master/f/rebuild_osbs_buildroot.md
This is currently running so the image will soon be updated (in ~10min).
Closing now, please reopen if needed.
Metadata Update from @cverna: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thanks, @cverna! Hm, I don't think this worked because the flatpak-module-tools update isn't in the stable repos yet (so it wasn't picked up when rebuilding the image). I'll get it to stable and let's try rebuilding the image again tomorrow.
The OSBS buildroot is using a Fedora 31 base image and when I checked it looks like it had the correct version of flatpak-module-tools.
and when I checked it looks like it had the correct version of flatpak-module-tools.
Weird. It doesn't seem to get used for flatpak builds at least.
Not entirely sure what's going on here, but could you do another run of the playbook and see if it makes the update show up for flatpak builds? The flatpak-module-tools updates (including the Fedora 31 one) are now in the stable repos.
Metadata Update from @kalev: - Issue status updated to: Open (was: Closed)
@kalev I just did a new rebuild so you can give it a try.
I just did a test flatpak build and I can see the expected changes there so the buildroot update seemed to work this time :) Thanks, @cverna!
Metadata Update from @kalev: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.