#9658 Please retire ktoblzcheck in EPEL 8
Closed: Fixed by mohanboddu. Opened by notting.

  • Describe the issue

Please retire ktoblzcheck in EPEL 8.

After requesting the branch, I realized it was no longer needed. No builds have been pushed live for EPEL 8 yet.

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

2020/09/01 ?

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

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

Stray branch in SCM that implies ilveness and package availability.


Hi, @notting you should be able to retire package branch yourself by running $fedpkg retire on a branch that you wish to retire.

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

Metadata Update from @notting:
- Issue status updated to: Open (was: Closed)

Tried that. I wouldn't have filed this issue if that actually worked.

[notting@nostromo: ~/prog/rpms/ktoblzcheck]$ fedpkg retire "because it's not needed"
Fedora release (epel8) is in state 'current' - retire operation is not allowed.

That is a bug in fedpkg, you can workaround it by:

$ git switch epel8
$ git rm -r .
$ echo "$REASON" > dead.package
$ git add dead.package
$ git commit -m "$REASON"
$ git push

The bug has been fixed couple months ago, but there was no release yet https://pagure.io/fedpkg/issue/395

That is a bug in fedpkg, you can workaround it by:

$ git switch epel8 $ git rm -r . $ echo "$REASON" > dead.package $ git add dead.package $ git commit -m "$REASON" $ git push

The bug has been fixed couple months ago, but there was no release yet https://pagure.io/fedpkg/issue/395

But that won't block it in koji will it?

@notting This seems to be fixed, but I am not sure if you wanna do it for epel8-playground or not.

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

Pushed SCM for epel8. I don't think I can block koji.

Metadata