Bug 33377 - rpm 4.20.0 beta: no more perl dependency generators
Summary: rpm 4.20.0 beta: no more perl dependency generators
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Base system maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-07 18:48 CEST by Jani Välimaa
Modified: 2024-07-16 10:13 CEST (History)
0 users

See Also:
Source RPM: rpm-4.19.92-1.mga10.src.rpm
CVE:
Status comment:


Attachments

Description Jani Välimaa 2024-07-07 18:48:47 CEST
When building a package with rpm 4.20.0 beta from core/backports_testing there are errors in mock build.log:

error: Couldn't exec /usr/lib/rpm/perl.prov: No such file or directory
error: Couldn't exec /usr/lib/rpm/perl.req: No such file or directory

Rpm upstream removed perl dependency generators from the repo in 4.20.0 alpha:
https://github.com/rpm-software-management/rpm/commit/8eac3304261f229d380246cc773e88fac3c22282

However both removed files are still referenced in rpm-build's /usr/lib/rpm/fileattrs/perllib.attr and /usr/lib/rpm/fileattrs/perl.attr.

There is a new upstream available for the removed generators:
https://github.com/rpm-software-management/perl-rpm-packaging

Should we pkg the removed files, or patch upstream fileattrs to use our patched perl dep generators coming from rpm-setup?
Comment 1 katnatek 2024-07-07 20:02:59 CEST
I think we must package the files in https://github.com/rpm-software-management/perl-rpm-packaging because the upstream reason to not include in 'core' rpm is 

'These are far better maintained by the Perl community'
Comment 2 Lewis Smith 2024-07-08 20:56:23 CEST
Assigning to Basesystem maintainers

Assignee: bugsquad => basesystem

Comment 3 Jani Välimaa 2024-07-16 10:13:00 CEST
Added perl.{prov,req} from 'new' upstream to rpm-mageia-setup-2.80-3.mga10 in core/backports_testing where rpm-4.19.92-1.mga10 also lives.

Resolution: (none) => FIXED
Status: NEW => RESOLVED


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