releng

#11976 retsnoop 0.9.8-1.el8 already in epel8 but Bodhi update still open
Closed: Fixed with Explanation by kevin. Opened by salimma.

Closed: Fixed with Explanation
Reopen Issue
  • Describe the issue
    I noticed this update has been open for 3 weeks:
    https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-04b99136f9

it can't go to stable because it has the wrong tags

Build: https://koji.fedoraproject.org/koji/buildinfo?buildID=2380881

but this is actually already in epel8, so looks like Bodhi's database was not properly updated and now it futilely tries to repush this package every day

$ fedrq pkgs retsnoop -b epel8
retsnoop-0.9.8-1.el8.src
retsnoop-0.9.8-1.el8.x86_64

Can the Bodhi db be manually cleaned up?

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

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

  • If we cannot complete your request, what is the impact?
    Spammy Bodhi and resource unnecessarily spent on trying to push a package that is already pushed

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

Fixed.

It should go out in the next push... I did:

✗ koji tag-pkg epel8-testing retsnoop-0.9.8-1.el8
Created task 113903831
Watching tasks (this may be safely interrupted)...
113903831 tagBuild (noarch): free
113903831 tagBuild (noarch): free -> closed
  0 free  0 open  1 done  0 failed
113903831 tagBuild (noarch) completed successfully

so, now it's in one of the right tags. Please re-open if you still see anything after today.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)
Metadata
None

low-gain low-trouble ops

None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.