Bug 2217156 - speedtest-cli conflicts with python3-speedtest-cli
Summary: speedtest-cli conflicts with python3-speedtest-cli
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: speedtest-cli
Version: 38
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jonathan Wright
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-24 14:42 UTC by Paweł
Modified: 2024-11-27 06:04 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-28 13:14:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Paweł 2023-06-24 14:42:00 UTC
speedtest-cli conflicts with python3-speedtest-cli because two different people packaged the same program.


Reproducible: Always

Steps to Reproduce:
1. Install speedtest-cli
2. Install python3-speedtest-cli
or vice versa
Actual Results:  
Conflicts between packages

Expected Results:  
Well, I think one package is enough. Maybe let the maintaners talk to each other and leave only one package.

counterpart bug https://bugzilla.redhat.com/show_bug.cgi?id=1947451

Comment 1 Aoife Moloney 2024-05-28 13:14:14 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 2 Vedran Miletić 2024-11-27 06:04:44 UTC
While the bug is a duplicate of bug 1822736, it is still present in Fedora 41. Can you reopen it?


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