I tested this in a mock chroot and can confirm that ansible-srpm-macros and thus %ansible_collection_url have been pulled into the buildroot. ansible-collection SRPM builds also no longer have unexpanded macros in the metadata. Thanks, Miro!
This update's test gating status has been changed to 'waiting'.
The gating test failures are preventing me from creating a BR override (and they'll also block the update from going stable). Can you please take a look?
I think the test is failing, because there is a mismatch between gcc and annobin. For some reason, the test is installing gcc-11.2.1-1.fc35 even though the latest build in updates is gcc-11.3.1-2.fc35.
I ran the test case manually in a container with gcc-11.3.1-2.fc35 and it passed for me.
This update has been submitted for testing by churchyard.
This update's test gating status has been changed to 'waiting'.
churchyard edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update's test gating status has been changed to 'failed'.
I tested this in a mock chroot and can confirm that
ansible-srpm-macrosand thus%ansible_collection_urlhave been pulled into the buildroot. ansible-collection SRPM builds also no longer have unexpanded macros in the metadata. Thanks, Miro!This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update has been pushed to testing.
The gating test failures are preventing me from creating a BR override (and they'll also block the update from going stable). Can you please take a look?
I think the test is failing, because there is a mismatch between gcc and annobin. For some reason, the test is installing gcc-11.2.1-1.fc35 even though the latest build in updates is gcc-11.3.1-2.fc35.
I ran the test case manually in a container with gcc-11.3.1-2.fc35 and it passed for me.
Here is the testing log I'm looking at: https://artifacts.dev.testing-farm.io/a2cb816f-8ce2-4c19-997f-01c421f7e9da/work-tests.ymlVu0RtR/ansible-output.txt
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
I waived the test failure.
This update has been submitted for stable by churchyard.
Thank you, @churchyard and @tstellar!
This update has been pushed to stable.