• Describe the issue

It looks like two bodhi updates for the rust-cargo-insta package were in flight at the same time (it looks like bodhi did not obsolete the older one when the newer one was created, because both were created from side tags).

Then, despite the 1.8.0-3.fc34 package being a security update, it got pushed to stable later (because it got no +1 karma, but the version update did), and now it seems the older version is getting composed into the f34-updates repositories, whereas the newer version should have succeeded it.

The package overview table on src.fedoraproject.org illustrates the problem well (all three branches should have 1.11.0-1%{?dist}):
https://src.fedoraproject.org/rpms/rust-cargo-insta

Both builds are now tagged into f34-updates in koji, so the only reason I can think of why the "older" version superseded the "newer" one is that it was tagged later.

https://koji.fedoraproject.org/koji/buildinfo?buildID=1903856
https://koji.fedoraproject.org/koji/buildinfo?buildID=1909397

• When do you need this? (YYYY/MM/DD)

It is not time sensitive, but annoying to have built a newer version that is now not available for users.

• When is this no longer needed or useful? (YYYY/MM/DD)

F34 EOL (whenever that is)

• If we cannot complete your request, what is the impact?

An older version of cargo-insta than what was intended will be available in the F34 repositories for all time.