#12376 picard-2.12.1-1.fc41 tagged incorrectly (possibly during the f41 branching) and missing from f41 repos
Closed: Fixed by decathorpe. Opened by decathorpe.

  • Describe the issue

I don't know how this happened, but it appears to be an issue caused during the branching of fedora 41. It looks like the "prevent these issues from happening" steps were not carried out correctly this release cycle?

This update has an f41 dist-tag but is only in Fedora 42:
https://bodhi.fedoraproject.org/updates/FEDORA-2024-95f1285d8f
https://koji.fedoraproject.org/koji/buildinfo?buildID=2525999

This leads to the update not being available in f41, but it is in f40, f39, and rawhide.

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

Before the F41 final freeze.

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

Unclear (either at F41 EOL or when the next update for this package fixes the issue).

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

The old version of this package remains in the f41 repos (i.e. older than both f40 and f42/rawhide).

I am also curious why the precautionary steps that should prevent race conditions during the f41 branching didn't take this release cycle - we have found multiple updates that had similar problems by now.


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

Metadata Update from @jnsamyak:
- Issue tagged with: low-trouble

Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

Okay to resolve this I have done three things:

  1. Tagged picard-2.12.1-1.fc41 to f41tag: https://koji.fedoraproject.org/koji/taskinfo?taskID=124309315
  2. Untaged picard-2.12.1-1.fc41 from f42 tag.
  3. Rebuild picard-2.12.1-1.fc42 for rawhide (f42 tag): https://koji.fedoraproject.org/koji/taskinfo?taskID=124309318

With the new compose nightly I hope this goes in stable: https://bodhi.fedoraproject.org/updates/FEDORA-2024-8c5987b9ad!

Thanks, that looks like a good solution to me! Let's see if this problem is gone by tomorrow.

UPDATE: This update has been submitted for stable by bodhi

One thing, that was missed was signing the package while I was retagging them from f42->f41, and that's why the compose failed; but @kevin fixed it and the branched compose is running now

@decathorpe, did this got fixed now?

Looks like it, yes. Thank you!

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

Metadata