Bug 2325366 - rpmlint-fedora-license-data: fails to install from epel10
Summary: rpmlint-fedora-license-data: fails to install from epel10
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: fedora-license-data
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav SuchΓ½
QA Contact:
URL:
Whiteboard:
Depends On: 2319854
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-11-12 01:58 UTC by Carl George 🎩
Modified: 2024-11-21 04:26 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-11-21 04:26:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Carl George 🎩 2024-11-12 01:58:54 UTC
Description of problem:
rpmlint-fedora-license-data and rpmlint-fedora-license-data-legacy from EPEL 10 have unresolved dependencies, causing them to be uninstallable.


Version-Release number of selected component (if applicable):
rpmlint-fedora-license-data-1.57-1.el10_0
rpmlint-fedora-license-data-legacy-1.57-1.el10_0


How reproducible:
always


Steps to Reproduce:
1. dnf install rpmlint-fedora-license-data rpmlint-fedora-license-data-legacy


Actual results:
Error: 
 Problem 1: conflicting requests
  - nothing provides rpmlint >= 2 needed by rpmlint-fedora-license-data-1.57-1.el10_0.noarch from epel
 Problem 2: conflicting requests
  - nothing provides rpmlint >= 2 needed by rpmlint-fedora-license-data-legacy-1.57-1.el10_0.noarch from epel


Expected results:
successful installation


Additional info:
If you think resolving this will take a long time, and would prefer to remove this uninstallable package from EPEL 10 in the meantime, just say so in this ticket and I can untag the build for you.  This won't retire the branch, so as soon as the underlying problem is resolved you can re-publish by creating a new update.

Comment 1 Carl George 🎩 2024-11-21 04:26:27 UTC
With the addition of rpmlint in bug 2319854, these packages are now installable.


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