Learn more about these different git repos.
Other Git URLs
It looks like the build from the F36 mass rebuild takes precedence over newer builds for f36 and f37:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1899489
This build is still tagged with both f36 and f37, despite newer versions of this package having been built for f36 and f37:
These are tagged with f36 and f37, respectively, as well, so I have no idea how this could have happened.
However, this problem seems to affect only two out of the three packages in this F36 update: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ef85659010
Which makes it even more strange (maybe one of the packages was updated later? But then, how did that build make it through, when the dependencies were not available?...)
As far as I can tell, the builds from this bodhi update for 0.8.2 should be the ones available for f36, not the old 0.8.0-3 build from the mass rebuild.
ASAP, this is blocking fixes for FTBFS / FTI issues in Fedora 36, so at the very latest, before the final freeze goes into effect.
Never. It blocks work on F36. So, maybe, no longer useful with F36 EOL, in mid-2023?
Broken builds of rust-imgui* and dependent packages in Fedora 36 that cannot be fixed by packagers.
It was just the timing from when the mass rebuild is done and it got tagged into the f36 tag.
rust-imgui-0.8.0-3.fc36 got tagged into f36 tag on Jan 25th:
rust-imgui-0.8.0-3.fc36
Tue Jan 25 23:18:45 2022 rust-imgui-0.8.0-3.fc36 tagged into f36 by autopen [still active]
where as rust-imgui-0.8.2-1.fc36 got tagged into f36 tag on Jan 24th:
rust-imgui-0.8.2-1.fc36
Mon Jan 24 18:46:34 2022 rust-imgui-0.8.2-1.fc36 tagged into f36 by bodhi [still active]
There are couple of options:
What would you like us to do?
I would defer this decision to the package maintainer: @remilauzier , what do you think?
Metadata Update from @mohanboddu: - Issue tagged with: low-gain, low-trouble, ops
I can wait till the beta is out since it’s supposed to be in a week.
Metadata Update from @humaton: - Issue tagged with: after freeze
post-beta-freeze-ping
rust-imgui-0.8.2-1 should be now tagged correctly for both f36 and f37
Thanks, I'll check this 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.