Bug 2217262 - RPM packaging of gsl-devel has "Requires:" automake - brings in huge unnecessary stuff
Summary: RPM packaging of gsl-devel has "Requires:" automake - brings in huge unnecess...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gsl
Version: 8.8
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Pavel Cahyna
QA Contact: CS System Management SST QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-25 16:55 UTC by mark@galassi.org
Modified: 2023-06-25 16:58 UTC (History)
0 users

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-160694 0 None None None 2023-06-25 16:58:11 UTC

Description mark@galassi.org 2023-06-25 16:55:05 UTC
Description of problem:

RPM packaging of gsl-devel has "Requires:" automake, which is unneeded and causes problems.  It is clearly incorrect to have Requires: on automake -- at most it should be "BuildRequires:".  This brings in a large amount of Perl packages.  Note that gsl is a tight math library that typically should only require the standard math library.

Recommendation: please change, in gsl.spec, the line:

Requires: pkgconfig, automake

to read instead:

Requires: pkgconfig
BuildRequires: automake



Version-Release number of selected component (if applicable):

gsl-devel-2.5-1

How reproducible:

Type:

$ dnf repoquery --installed --whatrequires automake

The answer will include something like:

gsl-devel-0:2.5-1.el8.x86_64

(or just look at the gsl.spec file for el8)

Steps to Reproduce:
1. dnf install gsl-devel gsl
2. dnf repoquery --installed --whatrequires automake | grep -i gsl
3. observe that it says: "gsl-devel-0:2.5-1.el8.x86_64"

Actual results:

gsl-devel-0:2.5-1.el8.x86_64

Expected results:

(blank output)

Additional info:


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