Bug 2126207 - fedora-review 0.9.0 fails to run rpmlint 2.2
Summary: fedora-review 0.9.0 fails to run rpmlint 2.2
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-review
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Neal Gompa
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2088759
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-12 21:06 UTC by Diego Herrera
Modified: 2023-07-25 02:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Diego Herrera 2022-09-12 21:06:50 UTC
Description of problem:

I was trying to run fedora-review on a package today and noticed that the Rpmlint section of the review.txt file had the following output

  Rpmlint
  -------
  Cannot parse rpmlint output:

Version-Release number of selected component (if applicable):
fedora-review.noarch-0.9.0-1.fc36

How reproducible:
yes

Steps to Reproduce:
1. run fedora-review to review a package

Actual results:
The Rpmlint section of the review.txt document says "Cannot parse rpmlint output:"

Expected results:
Actual Rpmlint results are written on the review.txt document.

Additional info:

Ran fedora-review on verbose and tried to run the rpmlint command generated by the app myself, found out that it failed with the following output

rpmlint: error: unrecognized arguments: --ignore-unused-rpmlintrc

Making a short research, noticed that this flag was added on rpmlint 2.3.0 [0], which is still not packaged on fedora (current version is 2.2.0 [1])

[0] https://github.com/rpm-software-management/rpmlint/releases/tag/2.3.0
[1] https://src.fedoraproject.org/rpms/rpmlint

Comment 1 Ben Cotton 2023-02-07 14:54:57 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle.
Changing version to 38.


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