Bug 2350299 - Heads-up: python-diff-cover fails to build with python-pygments 2.19.1 on Fedora 43
Summary: Heads-up: python-diff-cover fails to build with python-pygments 2.19.1 on Fed...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-diff-cover
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ali Erdinc Koroglu
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2371859 (view as bug list)
Depends On:
Blocks: PYTHON3.14 F43FTBFS F43FailsToInstall 2335657
TreeView+ depends on / blocked
 
Reported: 2025-03-06 11:26 UTC by Karolina Surma
Modified: 2025-11-03 04:25 UTC (History)
3 users (show)

Fixed In Version: python-diff-cover-9.4.1-1.fc43
Clone Of:
Environment:
Last Closed: 2025-07-05 19:26:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Karolina Surma 2025-03-06 11:26:04 UTC
python-diff-cover fails to build with python-pygments 2.19.1 in Fedora 43.
I intend to update python-pygments in Fedora Rawhide in ~1 week.

There may be an upstream solution to the issue (not tested) - version 9.2.3 supposedly contains the fix

The failure:

_______________________________ test_style_defs ________________________________

    def test_style_defs():
        style_str = Snippet.style_defs()
        expected_styles = load_fixture("snippet.css").strip()
    
        # Check that a sample of the styles are present
        # (use only a sample to make the test more robust
        # against Pygments changes).
        for expect_line in expected_styles.split("\n"):
>           assert expect_line in style_str
E           AssertionError: assert '.o { color: #666666 } /* Operator */' in 'pre { line-height: 125%; }\ntd.linenos .normal { color: inherit; background-color: transparent; padding-left: 5px; pa...e.Instance */\n.vm { color: #19177C } /* Name.Variable.Magic */\n.il { color: #666 } /* Literal.Number.Integer.Long */'

The testing takes place in COPR:
https://copr.fedorainfracloud.org/coprs/ksurma/pygments-2.19.1-f43/package/python-diff-cover

Comment 1 Karolina Surma 2025-06-11 15:58:23 UTC
*** Bug 2371859 has been marked as a duplicate of this bug. ***

Comment 2 Fedora Fails To Install 2025-06-20 19:51:38 UTC
Hello,

Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/

This package fails to install and maintainers are advised to take one of the following actions:

 - Fix this bug and close this bugzilla once the update makes it to the repository.
   (The same script that posted this comment will eventually close this bugzilla
   when the fixed package reaches the repository, so you don't have to worry about it.)

or

 - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't done so yet.

or

 - Orphan the package if you no longer plan to maintain it.


If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue.
This package may be orphaned in 7+ weeks.
This is the first reminder (step 3) from the policy.

Don't hesitate to ask for help on https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/ if you are unsure how to fix this bug.

Comment 3 Fedora Update System 2025-07-05 19:22:22 UTC
FEDORA-2025-c4edc3d917 (python-diff-cover-9.4.1-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-c4edc3d917

Comment 4 Fedora Update System 2025-07-05 19:26:36 UTC
FEDORA-2025-c4edc3d917 (python-diff-cover-9.4.1-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Red Hat Bugzilla 2025-11-03 04:25:03 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


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