Learn more about these different git repos.
Other Git URLs
I added modulemd-obsoletes documents for various nextcloud streams into fedora-module-defaults git repository https://pagure.io/releng/fedora-module-defaults/pull-request/243. The change was pushed into "main" branch for Rawhide and f36 and f35 (5a39c76e2f53d844a49aad1ab1f33d11a25d9bf9 commit) branches for stable Fedoras.
As expected the modulemd-obsoletes documents appeared in Rawhide 20220803.n.0 compose. But Fedora-Modular-35-updates-20220805.0 is still missing them. Though I verified in pungi log that the compose used that commit.
Could you check what's wrong? Why the documents do not exist in the F35 modular updates compose?
I see it is using that version:
2022-08-05 02:02:42 [DEBUG ] Exporting directory . from git https://pagure.io/releng/fedora-module-defaults.git (branch 5a39c76e2f53d844a49aad1ab1f33d11a25d9bf9)...
2022-08-05 02:02:44 [DEBUG ] Writing module defaults
2022-08-05 02:02:44 [DEBUG ] Writing module obsoletes
Does it need a specific version of pungi?
pungi-4.3.4-1.fc36.noarch is currently on bodhi-backend01
Metadata Update from @zlopez:
- Issue tagged with: low-gain, medium-trouble, ops
No, it does not. Both Rawhide and F35 compose logs show the same pungi version.
For some reason F35 compose is missing all obsoletes documents. Probably because "fedora.conf" file in f35 branch of pungi-fedora git repository is missing "module_obsoletes_dir" section. Despite of that the log reads "Writing module obsoletes" which is quite misleading.
Could you please add the module_obsoletes_dir section into pungi configuration for F35. It seems that only f35 is missing that section.
pungi-fedora is used for pre GA composes (and cloud and container nightlys).
Once a release is GA, bodhi doesn't the updates pushes.
and it does set module_obsoluete_dir. :(
Then I have not idea what's the cause. If you don't find any, close this issue on F35 end of life.
to comment on this ticket.