releng

#11982 Please create Fedora 40 Flatpak release in Bodhi
Closed: Fixed by jnsamyak. Opened by mattia.

Closed: Fixed
Reopen Issue

Describe the issue

flatpak-indexer stopped indexing flatpak updates on February 13th because it is broken, as it expects Fedora 40 Flatpak to be present in Bodhi.

Please create the release for resuming flatpak-indexer functionality. It looks like the SOP does mention the creation of the Flatpak release when a new Rawhide release is created.

BTW, I spotted few things that needs correction:

  • when creating the new Rawhide release (the RPM one, not the Flatpak), --branch should be set to rawhide (not f41 as described in the SOP)
  • it is said You need to run the bodhi openshift playbook, so that UI will know about the new release, but I think that's not necessary, cached releases list in Bodhi should be refreshed when a release is created/edited (but please check)

cc @otaylor

When do you need this? (YYYY/MM/DD)

As soon as possible to restore flatpak-indexer functionality

When is this no longer needed or useful? (YYYY/MM/DD)

n/a

If we cannot complete your request, what is the impact?

New flatpaks and flatpak updates are not published to users.

Metadata Update from @phsmoura:
- Issue tagged with: medium-gain, medium-trouble, ops

Hello @matia!

Indeed it does, and we tried running at the time of branching but I guess due to tags mismatch it didn't get created; I'll assign this to myself and will get back to you ASAP.

This is what we need to run to resolve this:

bodhi releases create \
  --name "F40F" --long-name "Fedora 40 Flatpaks" \
  --id-prefix FEDORA-FLATPAK --version 40 --branch f40 \
  --dist-tag f40-flatpak \
  --stable-tag f40-flatpak-updates \
  --testing-tag f40-flatpak-updates-testing \
  --candidate-tag f40-flatpak-updates-candidate \
  --pending-stable-tag f40-flatpak-updates-pending \
  --pending-testing-tag f40-flatpak-updates-testing-pending \
  --state pending \
  --override-tag f40-flatpak-override

This is from where we needed to check if the tags are set properly: https://pagure.io/releng/blob/main/f/scripts/branching/make-koji-release-tags

Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

Metadata Update from @jnsamyak:
- Assignee reset

Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

I guess I got why it didn't give an error; so we ran the koji release-tag script which ideally should have created those koji tags! :)

But I checked, at koji.fpo and searched for those tags and I couldn't find it!

Ok to fix this, firstly i created tags in koji and then i created a bodhi update using the above command; and I ran the playbook again so once can see it in: https://bodhi.fedoraproject.org/releases/F40F

If there are any more issues, please let us know, thanks!

Metadata Update from @jnsamyak:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Metadata

medium-gain medium-trouble ops

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.