Bug 2162954 - python-termcolor: request to update version
Summary: python-termcolor: request to update version
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-termcolor
Version: 37
Hardware: noarch
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Matthias Runge
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-01-22 10:02 UTC by Leif Liddy
Modified: 2023-05-30 09:49 UTC (History)
2 users (show)

Fixed In Version: python-termcolor-2.3.0-1.fc39
Clone Of:
Environment:
Last Closed: 2023-05-30 09:49:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Leif Liddy 2023-01-22 10:02:17 UTC
Description of problem:
This isn't an issue per se.
Simply requesting that that python-termcolor version get bumped up to the latest upstream version.
The Fedora version is pegged at v1.1.0 which was released over 10 years ago. 

The current upstream version 2.2.0 has some updated color schemes I'd like to use.
https://github.com/termcolor/termcolor/pull/32

Comment 1 Leif Liddy 2023-01-22 11:29:29 UTC
Submitted PR:
https://src.fedoraproject.org/rpms/python-termcolor/pull-request/2

Comment 2 Mikel Olasagasti Uranga 2023-01-22 12:04:32 UTC
I also submitted a PR, as I thought this was a request and was unsure if a PR would follow:

https://src.fedoraproject.org/rpms/python-termcolor/pull-request/3

It has some minor differences but also adopts rpmautospec. I don't care which one should progress.

The main problem is that 2.2.0 breaks some packages as can be seen in the copr I created to test dependent packages:

https://copr.fedorainfracloud.org/coprs/mikelo2/termcolor-2.2.0/builds/

About being pegged at 1.1.0, it's not 6 months the project released 2.0.0:

https://pypi.org/project/termcolor/#history

Comment 3 Leif Liddy 2023-01-22 12:18:59 UTC
What a quick response! I've never encountered that before. 

>It has some minor differences but also adopts rpmautospec. I don't care which one should progress.
Go with your version. I like the idea of using the rpmautospec

>it's not 6 months the project released 2.0.0:
That's a valid point. I didn't even notice that. 

>The main problem is that 2.2.0 breaks some packages...
That's interesting. I performed a mockbuild, and that worked fine. 
I'll have to look at the COPR build logs...

Comment 4 Leif Liddy 2023-01-22 12:21:37 UTC
I need to get in the habit of building packages with copr.

Comment 5 Mikel Olasagasti Uranga 2023-01-22 14:44:26 UTC
- tldr could be patched downstream with https://github.com/tldr-pages/tldr-python-client/pull/204 until a new version is released. I can take care of patching, I've commit access.

- python-pytest-shutil https://github.com/man-group/pytest-plugins/issues/210 but I guess it can be patched in https://github.com/man-group/pytest-plugins/blob/master/pytest-shutil/pytest_shutil/cmdline.py#L53 with FORCE_COLOR as with tldr to solve non-tty test failure.

I can try to take care of both this week unless someone else does.

Comment 6 Fedora Update System 2023-05-30 09:46:34 UTC
FEDORA-2023-a6cd76da51 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-a6cd76da51

Comment 7 Fedora Update System 2023-05-30 09:49:29 UTC
FEDORA-2023-a6cd76da51 has been pushed to the Fedora 39 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.