Learn more about these different git repos.
Other Git URLs
After sending this to mailing list I realized that it will be better to put it here.
It seems update fcitx5-qt-5.0.16-2.fc37 from 1 somehow did not make it to stable repository while other package in same update did. This caused broken dependences during update 2.
Seems that bodhi is doing something weird. I might have an idea how this happened: I decided to update fcitx5-qt to 5.0.16 and created a update 3 containing fcitx5-qt-5.0.16-1.fc37, during 3 waiting to make it to stable, qt6 rebuild happens and created another update with fcitx5-qt-5.0.16-2.fc37 1. 1 gets a lot karma and pushed to stable soon. And when 3 gets pushed afterwards, somehow fcitx5-qt-5.0.16- 1.fc37 overrides fcitx5-qt-5.0.16-2.fc37.
I don't know if this behavior should be considered as a bug, but anyway, it seems that manual override from releng is needed to fix the broken dependencies.
Metadata Update from @humaton: - Issue tagged with: medium-gain, medium-trouble, ops
yes, this is an ordering issue.
koji itself doesn't know anything about versions. It has no way to tell if something is higher or lower in version, It only knows what order they were tagged into.
So, lets look at history here:
% koji list-history --build fcitx5-qt-5.0.16-1.fc37 Mon Nov 21 00:16:54 2022 fcitx5-qt-5.0.16-1.fc37 tagged into f37-updates-candidate by yanqiyu Mon Nov 21 04:27:22 2022 fcitx5-qt-5.0.16-1.fc37 tagged into f37-signing-pending by bodhi Mon Nov 21 04:29:43 2022 fcitx5-qt-5.0.16-1.fc37 untagged from f37-signing-pending by autopen Mon Nov 21 04:29:43 2022 fcitx5-qt-5.0.16-1.fc37 tagged into f37-updates-testing-pending by autopen Mon Nov 21 17:22:27 2022 fcitx5-qt-5.0.16-1.fc37 untagged from f37-updates-candidate by bodhi Mon Nov 21 17:22:27 2022 fcitx5-qt-5.0.16-1.fc37 tagged into f37-updates-testing by bodhi Mon Nov 21 17:22:52 2022 fcitx5-qt-5.0.16-1.fc37 untagged from f37-updates-testing-pending by bodhi Mon Nov 28 18:28:40 2022 fcitx5-qt-5.0.16-1.fc37 tagged into f37-updates-pending by bodhi Tue Nov 29 16:15:46 2022 fcitx5-qt-5.0.16-1.fc37 untagged from f37-updates-testing by bodhi Tue Nov 29 16:15:46 2022 fcitx5-qt-5.0.16-1.fc37 tagged into f37-updates by bodhi [still active] Tue Nov 29 16:16:14 2022 fcitx5-qt-5.0.16-1.fc37 untagged from f37-updates-pending by bodhi
and
% koji list-history --build fcitx5-qt-5.0.16-2.fc37 Fri Nov 25 00:13:26 2022 fcitx5-qt-5.0.16-2.fc37 tagged into f37-build-side-60327 by jgrulich Fri Nov 25 01:35:41 2022 fcitx5-qt-5.0.16-2.fc37 tagged into f37-signing-pending by bodhi Fri Nov 25 01:35:58 2022 fcitx5-qt-5.0.16-2.fc37 tagged into f37-updates-candidate by bodhi Fri Nov 25 01:40:19 2022 fcitx5-qt-5.0.16-2.fc37 untagged from f37-signing-pending by autopen Fri Nov 25 01:40:19 2022 fcitx5-qt-5.0.16-2.fc37 tagged into f37-updates-testing-pending by autopen Fri Nov 25 16:28:00 2022 fcitx5-qt-5.0.16-2.fc37 untagged from f37-updates-candidate by bodhi Fri Nov 25 16:28:00 2022 fcitx5-qt-5.0.16-2.fc37 tagged into f37-updates-testing by bodhi Fri Nov 25 16:29:08 2022 fcitx5-qt-5.0.16-2.fc37 untagged from f37-updates-testing-pending by bodhi Sat Nov 26 12:12:21 2022 fcitx5-qt-5.0.16-2.fc37 tagged into f37-updates-pending by bodhi Sat Nov 26 16:16:44 2022 fcitx5-qt-5.0.16-2.fc37 untagged from f37-updates-testing by bodhi Sat Nov 26 16:16:44 2022 fcitx5-qt-5.0.16-2.fc37 tagged into f37-updates by bodhi [still active] Sat Nov 26 16:17:54 2022 fcitx5-qt-5.0.16-2.fc37 untagged from f37-updates-pending by bodhi Sat Nov 26 16:17:59 2022 fcitx5-qt-5.0.16-2.fc37 untagged from f37-build-side-60327 by bodhi
In the case of single build updates, bodhi will obsolete the 'older' one and just push the newer one. However, if the 'older' update has multiple packages in it, it does not. It can't know if those other packages are intended to work with the new package or not. I've proposed upstream to bodhi to reject the newer update in these cases, which would force maintainers to remove the old update or wait.
In any case, you need to watch for this sort of thing currently.
I've retagged -2 in, so it should go out in the next compose.
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.