Bug 2144190 - Request to add it to EPEL 9
Summary: Request to add it to EPEL 9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: codespell
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Debarshi Ray
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-19 18:24 UTC by Debarshi Ray
Modified: 2022-12-08 01:11 UTC (History)
0 users

Fixed In Version: codespell-2.2.1-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-08 01:11:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Debarshi Ray 2022-11-19 18:24:40 UTC
I am trying to add a CentOS Stream 9 build to Toolbx's upstream CI:
https://github.com/containers/toolbox/pull/1171

... and one of your build requirements is codespell.  Hence, it will be really good if codespell could be added to EPEL 9.

I don't want to burden you needlessly, so, if you want, I am happy to take care of the EPEL 9 branch.

Comment 1 Bastien Nocera 2022-11-22 09:06:56 UTC
I've assigned the EPEL branch to you. I'll let you handle the updates, and reassign this bug to you for the first build.

Comment 2 Debarshi Ray 2022-11-23 14:02:21 UTC
I am confused about where things exactly are at.

I don't see an 'epel9' branch in dist-git.  Neither here:
https://src.fedoraproject.org/rpms/codespell/branches?branchname=rawhide

... nor through Git:
[rishi@topinka codespell]$ git branch -r
  origin/HEAD -> origin/rawhide
  origin/f29
  origin/f30
  origin/f31
  origin/f32
  origin/f33
  origin/f34
  origin/f35
  origin/f36
  origin/f37
  origin/main
  origin/rawhide
[rishi@topinka codespell]$ 

Did you already request a branch using 'fedpkg request-branch':
https://docs.fedoraproject.org/en-US/epel/epel-policy/#getting_fedora_packages_in_epel

I am asking because I don't see a ticket asking for an epel9 branch for codespell:
https://pagure.io/releng/fedora-scm-requests/issues?status=all&search_pattern=codespell&close_status=

Do you want me to request a branch myself?  I am happy to, but I wanted to be sure first.

Comment 3 Bastien Nocera 2022-11-23 14:43:41 UTC
> I've assigned the EPEL branch to you. I'll let you handle the updates, and reassign this bug to you for the first build.

This is exactly what I did, assigned the EPEL maintainership in https://src.fedoraproject.org/rpms/codespell

I didn't do anything else, such as creating branches, or asking for branches to be created.

Comment 4 Debarshi Ray 2022-11-23 16:00:48 UTC
Ok, I requested an epel9 branch:
https://pagure.io/releng/fedora-scm-requests/issue/49299

Comment 5 Debarshi Ray 2022-11-28 11:36:39 UTC
It looks like the automated scripts only work if the Fedora owner of the package requests the EPEL branch:
https://pagure.io/releng/fedora-scm-requests/issue/49299

Let's see if a human can help:
https://pagure.io/releng/issue/11153

Comment 6 Debarshi Ray 2022-11-28 21:01:24 UTC
Now that Bastien made me an admin of the whole codespell package, here's another attempt at fedpkg request-branch:
https://pagure.io/releng/fedora-scm-requests/issue/49451

Comment 7 Bastien Nocera 2022-11-29 09:02:09 UTC
Looks like the last attempt worked, removing myself from CC:.

Comment 8 Fedora Update System 2022-11-29 18:56:48 UTC
FEDORA-EPEL-2022-03a24db589 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-03a24db589

Comment 9 Fedora Update System 2022-11-30 01:43:49 UTC
FEDORA-EPEL-2022-03a24db589 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-03a24db589

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2022-12-08 01:11:02 UTC
FEDORA-EPEL-2022-03a24db589 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.