Bug 2382816 - Please branch and build python-colorful in epel10
Summary: Please branch and build python-colorful in epel10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-colorful
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Carl George 🎩
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-07-23 10:15 UTC by Ulrik Haugen
Modified: 2025-08-07 01:36 UTC (History)
2 users (show)

Fixed In Version: python-colorful-0.5.7-1.el10_1 python-colorful-0.5.7-1.el10_0
Clone Of:
Environment:
Last Closed: 2025-08-07 01:36:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ulrik Haugen 2025-07-23 10:15:28 UTC
Please branch and build python-colorful in epel10.

Reproducible: Always

Comment 1 Fedora Update System 2025-07-23 22:00:17 UTC
FEDORA-EPEL-2025-963be72143 (python-colorful-0.5.7-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-963be72143

Comment 2 Fedora Update System 2025-07-24 01:27:13 UTC
FEDORA-EPEL-2025-963be72143 has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-963be72143

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

Comment 3 Ulrik Haugen 2025-07-25 12:18:22 UTC
Briefly tested and feedback submitted in Bodhi. Thanks!

Comment 4 Carl George 🎩 2025-07-25 18:56:02 UTC
I noticed in your bodhi comment that you said you tested in a UBI container, I'm assuming by manually downloading the package.  Just for clarity, I only built this for EPEL 10.1.  It will get automatically included in future EPEL 10 minor versions, but it won't automatically go backwards to EPEL 10.0.  RHEL 10 (and UBI 10) will only see the EPEL 10.0 repo until RHEL 10.1 is released.  CentOS 10 is already consuming the EPEL 10.1 repo.  You can read more about this structure here:

https://docs.fedoraproject.org/en-US/epel/branches/#_epel_10

If needed, I can explicitly build this for EPEL 10.0 as well, just let me know.

Comment 5 Fedora Update System 2025-07-26 01:51:49 UTC
FEDORA-EPEL-2025-963be72143 (python-colorful-0.5.7-1.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Ulrik Haugen 2025-07-29 09:08:39 UTC
(In reply to Carl George 🤠 from comment #4)
> I noticed in your bodhi comment that you said you tested in a UBI container,
> I'm assuming by manually downloading the package.  Just for clarity, I only
> built this for EPEL 10.1.  It will get automatically included in future EPEL
> 10 minor versions, but it won't automatically go backwards to EPEL 10.0. 
> RHEL 10 (and UBI 10) will only see the EPEL 10.0 repo until RHEL 10.1 is
> released.  CentOS 10 is already consuming the EPEL 10.1 repo.  You can read
> more about this structure here:
> 
> https://docs.fedoraproject.org/en-US/epel/branches/#_epel_10

Thank you for this very helpful comment that i now wish i'd read before i came to understand how epel 10 point releases work yesterday when working on 2383208 (see https://src.fedoraproject.org/rpms/rpmlint/pull-request/53).

> If needed, I can explicitly build this for EPEL 10.0 as well, just let me
> know.

Because we were not aware of this we didn't set up our mirroring as we should have but i hope we can repair it before 10.1 is released (which i'm guessing will be about november) so yes please, an epel 10.0 build would be very much appreciated!

By the way, i think i saw you ask someone for a pull request to https://docs.fedoraproject.org/en-US/epel/epel-package-request/#end_users that does not seem to have materialised (or at least get merged), would you consider one from an epel user and if so would you please point me to the pagure project in question?

Comment 7 Carl George 🎩 2025-07-29 22:45:43 UTC
> Because we were not aware of this we didn't set up our mirroring as we should have but i hope we can repair it before 10.1 is released (which i'm guessing will be about november) so yes please, an epel 10.0 build would be very much appreciated!

Building it now, I'll submit the update against this bug once it's complete.

https://koji.fedoraproject.org/koji/taskinfo?taskID=135456412

> By the way, i think i saw you ask someone for a pull request to https://docs.fedoraproject.org/en-US/epel/epel-package-request/#end_users that does not seem to have materialised (or at least get merged), would you consider one from an epel user and if so would you please point me to the pagure project in question?

The EPEL docs are generated from:

https://pagure.io/epel

The source for the package request page is:

https://pagure.io/epel/blob/main/f/modules/ROOT/pages/epel-package-request.adoc

We have a WIP pull request already, but the submitter hasn't integrated the feedback yet:

https://pagure.io/epel/pull-request/339

If you want to submit another pull request that implements the suggested wording (or something similar with your own spin on it, perhaps with a more descriptive commit message) we can merge that instead.

Comment 8 Fedora Update System 2025-07-29 22:55:19 UTC
FEDORA-EPEL-2025-e2d399b9b6 (python-colorful-0.5.7-1.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-e2d399b9b6

Comment 9 Fedora Update System 2025-07-30 02:06:08 UTC
FEDORA-EPEL-2025-e2d399b9b6 has been pushed to the Fedora EPEL 10.0 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-e2d399b9b6

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

Comment 10 Fedora Update System 2025-08-07 01:36:57 UTC
FEDORA-EPEL-2025-e2d399b9b6 (python-colorful-0.5.7-1.el10_0) has been pushed to the Fedora EPEL 10.0 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.