Dne 14. 02. 24 v 14:56 Michael J Gruber
napsal(a):
Why branched config pointed to rolling config? # ls -ln | grep fedora-40 lrwxrwxrwx. 1 0 135 26 Jan 11 20:46 fedora-40-aarch64.cfg -> fedora-rawhide-aarch64.cfg lrwxrwxrwx. 1 0 135 23 Jan 11 20:46 fedora-40-i386.cfg -> fedora-rawhide-i386.cfg lrwxrwxrwx. 1 0 135 26 Jan 11 20:46 fedora-40-ppc64le.cfg -> fedora-rawhide-ppc64le.cfg lrwxrwxrwx. 1 0 135 24 Jan 11 20:46 fedora-40-s390x.cfg -> fedora-rawhide-s390x.cfg lrwxrwxrwx. 1 0 135 25 Jan 11 20:46 fedora-40-x86_64.cfg -> fedora-rawhide-x86_64.cfg... because on Jan 25th, f40 was rawhide. We branched yesterday. So, either you wait for updated mock-config to land in f40, or you roll it yourself. It's no mock science 🙂
And if you check Bodhi, it is sitting there and waiting for you guys :)
https://bodhi.fedoraproject.org/updates/?search=mock-core-configs
-- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
