Description of problem: Installing libtool-ltdl-devel currently drags in automake as a dependency, and with it the perl interpreter and many perl modules. This is unfortunate since perl is no longer part of the default buildroot, so packages linking to libltdl get a lot of bloat in mock and koji due to this. Version-Release number of selected component (if applicable): libtool-2.4.6-33.fc32 How reproducible: always Steps to Reproduce: 1. Build a package linking to libltdl and not using automake in koji or mock Actual results: automake, autoconf and perl are installed Expected results: automake, autoconf and perl are not installed
I added the dep beause of https://bugzilla.redhat.com/show_bug.cgi?id=1193591 Depending on automake is wise for general package (otherwise we risk that package fails to build if it was generated with different version of automake). Perhaps we could have two packages, like: libtool-ltdl-devel -> libtool-ltdl-devel-minimal
That is an inappropriate fix for that issue. Any package that runs autoreconf in %prep or %build must build-require automake, autoconf, libtool and whatever is needed to run autoreconf for the package. Adding a dependency on automake to libtool-ltdl-devel because a package maintainer doesn't want to add all the build-requires to his specfile is not right.
The thing is most of the affected packages don't do autoreconf. I added that to the example, iirc, only because I found it weird that autoreconf actually did not help.
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
> Adding a dependency on automake to libtool-ltdl-devel because a package > maintainer doesn't want to add all the build-requires to his specfile is not > right. I did not close this bug because I agree with you. We should use conflicts instad.
Please take a look at: https://src.fedoraproject.org/rpms/libtool/pull-request/5
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.