#11836 Bump f39 flatpak dist-tag
Closed: Fixed by jnsamyak. Opened by yselkowitz.

  • Describe the issue
    As part of migrating the libreoffice flatpak to F39, we have had to rework how java-related packages are built for flatpaks. This has been implemented, but some packages that were previously built need to be rebuilt without any modifications needed. To that end, please:
koji edit-tag -x rpm.macro.distcore='.fc%{fedora}app4'  f39-flatpak-app-build && koji regen-repo f39-flatpak-app-build
  • When do you need this? (YYYY/MM/DD)
    ASAP

  • If we cannot complete your request, what is the impact?
    We would need to artificially revbump the affected packages themselves, or wait until they are bumped for other reasons. Libreoffice is one of the last flatpaks to be migrated to F39, which is a blocker for OSBS decommissioning in https://pagure.io/fedora-infrastructure/issue/11504

/cc @otaylor


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

Hello @yselkowitz

Thanks for helping out with the commands here you go

Regenerating repo for tag: f39-flatpak-app-build
Created task: 110319057
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=110319057
Watching tasks (this may be safely interrupted)...
110319057 newRepo (f39-flatpak-app-build): free
110319057 newRepo (f39-flatpak-app-build): free -> open (buildvm-x86-04.iad2.fedoraproject.org)
  110319138 createrepo (x86_64): free
  110319139 createrepo (aarch64): free
  110319140 createrepo (ppc64le): free
  110319138 createrepo (x86_64): free -> open (buildvm-x86-25.iad2.fedoraproject.org)
  110319139 createrepo (aarch64): free -> open (buildvm-x86-10.iad2.fedoraproject.org)
  110319140 createrepo (ppc64le): free -> open (buildvm-x86-21.iad2.fedoraproject.org)
...
110319057 newRepo (f39-flatpak-app-build): open (buildvm-x86-04.iad2.fedoraproject.org) -> closed
  0 free  0 open  4 done  0 failed
110319057 newRepo (f39-flatpak-app-build) completed successfully

If there is anything else please let me know!

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

Metadata