Bug 30427 - We still have rpmlint 1.11 while upstream is at 2.5.0 now
Summary: We still have rpmlint 1.11 while upstream is at 2.5.0 now
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: RPM stack maintainers
QA Contact:
URL:
Whiteboard: MGA8TOO?
Keywords:
: 30892 (view as bug list)
Depends on:
Blocks:
 
Reported: 2022-05-14 08:32 CEST by Kristoffer Grundström
Modified: 2023-10-24 22:19 CEST (History)
5 users (show)

See Also:
Source RPM: rpmlint
CVE:
Status comment:


Attachments
Proposal spec file (2.44 KB, text/plain)
2022-12-09 09:55 CET, Kristoffer Grundström
Details
Regex patch (2.40 KB, patch)
2022-12-09 09:57 CET, Kristoffer Grundström
Details | Diff
Full build output (93.00 KB, text/plain)
2022-12-09 09:59 CET, Kristoffer Grundström
Details
Updated proposal spec file (2.35 KB, text/plain)
2022-12-27 02:15 CET, Kristoffer Grundström
Details
Updated full build output (109.32 KB, text/plain)
2022-12-27 02:25 CET, Kristoffer Grundström
Details
katnatek version of rpmlint 2.4.0 spec (3.36 KB, text/plain)
2023-10-15 03:30 CEST, katnatek
Details

Description Kristoffer Grundström 2022-05-14 08:32:22 CEST
Description of problem: I noticed that our version of rpmlint is somewhat old. I therefor ask to have it updated. These are the new improvements according to the repo on GitHub:

    Fixed support for loading .rpmlintrc files
    Added support for /usr/lib/modules as a valid path for kernel modules in packages
    Added /usr/share/dbus-1/system.d to D-Bus config folder list
    Massively reworked the shlib-policy-name-error rules
    Added support for %autochangelog macro in %changelog section
    Improved support for detecting whether code is compiled correctly with hardening flags
    Multiple fixes to library dependency checks
    Added support for libalternatives as an alternative to alternatives

Version-Release number of selected component (if applicable): 2.2
Kristoffer Grundström 2022-05-14 08:32:39 CEST

CC: (none) => lovaren

Comment 1 Marja Van Waes 2022-05-17 13:38:52 CEST
Thanks for spotting this, Kristoffer.

I don't know whether our updates policy allows for upgrading rpmlint in stable. It should be done in cauldron first, anyway.

Assignee: bugsquad => rpmstack
CC: (none) => marja11
Whiteboard: (none) => MGA8TOO?
Version: 8 => Cauldron
Summary: Minor feature release update for rpmlint => We still have rpmlint 1.11 while upstream is at 2.2 now

Comment 2 sturmvogel 2022-09-26 21:09:24 CEST
*** Bug 30892 has been marked as a duplicate of this bug. ***
Kristoffer Grundström 2022-12-09 09:48:53 CET

Summary: We still have rpmlint 1.11 while upstream is at 2.2 now => We still have rpmlint 1.11 while upstream is at 2.4.0 now

Comment 3 Kristoffer Grundström 2022-12-09 09:55:06 CET
Created attachment 13554 [details]
Proposal spec file

Please note that I had to make some significant changes since I used the spec file from Fedora because our spec file for 1.11 didn't work to build 2.4.0 even with our patches.
Feel free to change it as you please, but it will build successfully.
Comment 4 Kristoffer Grundström 2022-12-09 09:57:51 CET
Created attachment 13555 [details]
Regex patch
Comment 5 Kristoffer Grundström 2022-12-09 09:59:03 CET
Created attachment 13556 [details]
Full build output
Comment 6 Kristoffer Grundström 2022-12-27 02:15:36 CET
Created attachment 13600 [details]
Updated proposal spec file

Attachment 13554 is obsolete: 0 => 1

Comment 7 Kristoffer Grundström 2022-12-27 02:22:08 CET
I don't know if rpmlint-fedora-license-data brings any use to Mageia, but I built and installed that as well.
Comment 8 Kristoffer Grundström 2022-12-27 02:25:02 CET
Created attachment 13601 [details]
Updated full build output

Attachment 13556 is obsolete: 0 => 1

Comment 9 Neal Gompa 2023-01-25 14:39:20 CET
(In reply to Kristoffer Grundström from comment #7)
> I don't know if rpmlint-fedora-license-data brings any use to Mageia, but I
> built and installed that as well.

We follow Fedora's licensing guidance, so yes, it would make sense here.

CC: (none) => ngompa13

Comment 10 Kristoffer Grundström 2023-09-24 02:53:25 CEST
No harm meant for asking, but why are we still at 1.11 even after the release of Mageia 9?
Comment 11 Jens Persson 2023-10-10 04:18:33 CEST
Rpmlint seems to have no maintainer atm.

http://pkgsubmit.mageia.org/data/maintdb.txt

Also RPM, DNF and DNF5 are outdated.

CC: (none) => xerxes2

Comment 12 katnatek 2023-10-15 03:30:14 CEST
Created attachment 14058 [details]
katnatek version of rpmlint 2.4.0 spec

I import some things from fedora's spec to Kristoffer spec, build well on my system, but fail in my copr :S 

https://download.copr.fedorainfracloud.org/results/katnatek/blogdrake/mageia-9-x86_64/06526702-rpmlint/builder-live.log.gz

Attachment 13600 is obsolete: 0 => 1

katnatek 2023-10-15 04:07:21 CEST

CC: (none) => j.alberto.vc

Comment 13 katnatek 2023-10-15 04:27:44 CEST
Disabling the test the build is successful in copr :)

https://copr.fedorainfracloud.org/coprs/katnatek/blogdrake/build/6527080/
Comment 14 Kristoffer Grundström 2023-10-24 22:16:12 CEST
I test built 2.5.0, feel free to adjust the package accordingly and here's my repo:

https://copr.fedorainfracloud.org/coprs/umeaman/rpmlint/build/6562315/

Summary: We still have rpmlint 1.11 while upstream is at 2.4.0 now => We still have rpmlint 1.11 while upstream is at 2.5.0 now

Comment 15 Kristoffer Grundström 2023-10-24 22:19:25 CEST
Btw, I think I've found a regression from 2009.
While using the new rpmlint version on a spec file it gives no-buildroot-tag warning even though this spec file doesn't contain buildroot anywhere.

If you read the Fedora page about that issue they state that buildroot should NOT BE USED so this warning should not happen.

This problem has been reported in RedHat and closed, here's the link:

https://bugzilla.redhat.com/show_bug.cgi?id=516378

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