#12708 Re-push root-6.34.08-4.fc42 to stable
Closed: Fixed 12 days ago by patrikp. Opened 14 days ago by ellert.

  • Describe the issue

Two updates containing a build of the root package where in updates-testing at the same time:

The second update did not automatically obsolete the first one because it in addition contained updates of another package. The creators of the second update were probably not aware of the existence of the first one.

This would normally not be a problem, since the updates would be push to stable in the same order they ware created. However, the second update here was a push of a side-tag with an update of the R package which is a popular package and the update therefore attracted a lot of karma, so was push to stable early.

So the update containing the older version was pushed later replacing the new version.

Can the newer version be put back in?

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

No strict deadline.

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

Whenever there will be a new update of the package for some reason.

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

The root package's R interface in the repository will have been built with the wrong R version.


Metadata Update from @patrikp:
- Issue assigned to patrikp

13 days ago

Just FYI, we don't need to actually do anything with bodhi here. Just retag the 'newer' one so it's the latest tagged.

koji operates on tags and it just composes the latest package tagged.

So, a 'koji tag-pkg f42-updates root-6.34.08-4.fc42 --force or a untag and retag of it should fix this in the next compose.

Metadata Update from @phsmoura:
- Issue tagged with: low-gain, low-trouble, ops

13 days ago

I think this should be fixed now. :thumbsup:

$ koji list-history --build root-6.34.08-4.fc42
Tue Apr 29 13:22:19 2025 root-6.34.08-4.fc42 re-tagged into f42-updates by patrikp [still active]

Metadata Update from @patrikp:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

12 days ago

Log in to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog