Learn more about these different git repos.
Other Git URLs
I found even more cases like https://pagure.io/releng/issue/10687 when checking for package downgrades between F35 and F36.
The superseded newer packages are still tagged with f36, but some of the older packages are now tagged with f36, f36-rebuild, and f37, so clearly the mass branching script also picked the wrong packages to move to f37 ... not sure if there's a better way to check than to compare the NVRs of available packages.
elixir-0:1.13.2-1.fc35 > elixir-0:1.13.1-2.fc36 Version 1.13.2 was built before 1.13.1 during the mass rebuild, but was supersesed by the older build.
golang-github-aliyun-alibaba-cloud-sdk-0:1.61.1453-1.fc35 > golang-github-aliyun-alibaba-cloud-sdk-0:1.61.1369-2.fc36 Version 1.61.1453 was built before 1.61.1369 during the mass rebuild, but was superseded by the older build.
golang-github-aliyun-ossutil-0:1.7.9-1.fc35 > golang-github-aliyun-ossutil-0:1.7.8-2.fc36 Version 1.7.9 was built before 1.7.8 during the mass rebuild, but was superseded by the older build.
php-doctrine-datafixtures-0:1.5.2-1.fc35 > php-doctrine-datafixtures-0:1.5.1-2.fc36 Version 1.5.2 was built before 1.5.1 during the mass rebuild, but was superseded by the older build.
poke-0:2.1-2.fc35 > poke-0:1.4-2.fc36 Version 2.1 was built as 2.1-2.fc36, but is only tagged into f37 (mass branching snafu).
python-feedgenerator-0:2.0.0-1.fc35 > python-feedgenerator-0:1.9.1-5.fc36 Version 2.0.0 was built as 2.0.0-1.fc36, but is only tagged into f37 (mass branching snafu).
rust-imgui-0:0.8.2-1.fc35 > rust-imgui-0:0.8.0-3.fc36
rust-imgui-winit-support-0:0.8.2-2.fc35 > rust-imgui-winit-support-0:0.8.0-4.fc36 Version 0.8.2 was built after 0.8.0 during the mass rebuild, but was superseded by the older build.
When do you need this? (YYYY/MM/DD)
It would be great if this could be sorted out before the final freeze.
N/A
Older versions than were intended continue to pollute F36 (and in some cases, Rawhide / F37) repositories.
Metadata Update from @mohanboddu: - Issue tagged with: after freeze, medium-gain, medium-trouble, ops
Probably samething as https://pagure.io/releng/issue/10687#comment-784704, but we have to fix it post f36 beta freeze.
post-beta-freeze-ping
The builds should be tagged correctly now.
Thanks! I'll check again after the next compose.
Looks like this is fixed now. :thumbsup:
Metadata Update from @decathorpe: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.