Automatic update for lksctp-tools-1.0.20-1.fc42.
* Sun Sep 15 2024 Peter Hanecak <hany@hany.sk> - 1.0.20-1
- Updated to 1.0.20
- Update URL
- Dropped patches which were incorporated into the upstream
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2024-b81736114cPlease log in to add feedback.
This update was automatically created
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update's test gating status has been changed to 'ignored'.
This update has been submitted for stable by bodhi
So, today I managed to break gating briefly, which caused all gated updates to go stable. This one appears to have been gated because its test suite is completely broken, looking at the results:
That probably needs looking into. But at least, it doesn't seem like the failed test was telling us the package was definitely broken, which is a good thing since it's now stable...
oh, right, that's fallout from the RPM change that extracts package sources under a
name-version-buildsubdirectory, see https://github.com/teemtee/tmt/issues/2987 and https://github.com/rpm-software-management/rpm/issues/2078 .I tried to fix this in https://pagure.io/standard-test-roles/pull-request/413 , but it looks like the test ran with an older version of standard-test-roles , since the log shows it going straight from "Extract and setup the sources" to "Flatten sources", with no "Discover the build directory" step in the middle. @mvadkert @msrb , how can I tell what version of standard-test-roles was used from the test logs? I can't find any log which logs install of the package. Do we need to push a newer version to F40 maybe? My PR should be in the version that's in F41/Rawhide.