Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
There might be a problem with the gcc version. The bug cannot be reproduced on rhel7.7 system. Can you please try reproducing this bug with gcc-4.8.5-39.el7.x86_64 ? The currently used version is 4.8.5-36.
Thank you.
I think this is rather problem with repositories, which do not match to what is installed on the system. Maybe running `yum distro-sync` before the `yum install libtool` could make it work. Anyway, I agree with Ondra that this does not seem like libtool issue.
Update on this issue - I have had wrong repos, after fix on my side the installation of the libtool using "yum -y install libtool" command is now successful. I have found, that I am not able to close this issue, probably only people from libtool team can close this bug. I have written an email to "odubaj" with a request to close this bug.
Description of problem: The libtool cannot be installed on RHEL 7.7 beta using command "yum -y install libtool" Error: Package: glibc-2.17-260.el7_6.6.i686 (rhel-7-server-os-rpms) Requires: glibc-common = 2.17-260.el7_6.6 Installed: glibc-common-2.17-292.el7.x86_64 (installed) glibc-common = 2.17-292.el7 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Enter the "yum -y install libtool" command into the terminal and see the description of the unsuccessful installation Actual results: Expected results: Additional info: FULL CONSOLE OUTPUT: [root@zcervink1-rhel-77 ~]# yum -y install libtool Loaded plugins: search-disabled-repos Resolving Dependencies --> Running transaction check ---> Package libtool.x86_64 0:2.4.2-22.el7_3 will be installed --> Processing Dependency: gcc = 4.8.5 for package: libtool-2.4.2-22.el7_3.x86_64 --> Running transaction check ---> Package gcc.x86_64 0:4.8.5-36.el7_6.2 will be installed --> Processing Dependency: cpp = 4.8.5-36.el7_6.2 for package: gcc-4.8.5-36.el7_6.2.x86_64 --> Processing Dependency: libgomp = 4.8.5-36.el7_6.2 for package: gcc-4.8.5-36.el7_6.2.x86_64 --> Processing Dependency: glibc-devel >= 2.2.90-12 for package: gcc-4.8.5-36.el7_6.2.x86_64 --> Processing Dependency: libmpc.so.3()(64bit) for package: gcc-4.8.5-36.el7_6.2.x86_64 --> Processing Dependency: libmpfr.so.4()(64bit) for package: gcc-4.8.5-36.el7_6.2.x86_64 --> Running transaction check ---> Package cpp.x86_64 0:4.8.5-36.el7_6.2 will be installed ---> Package glibc-devel.x86_64 0:2.17-260.el7_6.6 will be installed --> Processing Dependency: glibc = 2.17-260.el7_6.6 for package: glibc-devel-2.17-260.el7_6.6.x86_64 --> Processing Dependency: glibc-headers = 2.17-260.el7_6.6 for package: glibc-devel-2.17-260.el7_6.6.x86_64 --> Processing Dependency: glibc-headers for package: glibc-devel-2.17-260.el7_6.6.x86_64 ---> Package libgomp.i686 0:4.8.5-36.el7_6.2 will be installed ---> Package libmpc.x86_64 0:1.0.1-3.el7 will be installed ---> Package mpfr.x86_64 0:3.1.1-4.el7 will be installed --> Running transaction check ---> Package glibc.i686 0:2.17-260.el7_6.6 will be installed --> Processing Dependency: glibc-common = 2.17-260.el7_6.6 for package: glibc-2.17-260.el7_6.6.i686 --> Processing Dependency: libfreebl3.so for package: glibc-2.17-260.el7_6.6.i686 --> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.17-260.el7_6.6.i686 ---> Package glibc-headers.x86_64 0:2.17-260.el7_6.6 will be installed --> Processing Dependency: kernel-headers >= 2.2.1 for package: glibc-headers-2.17-260.el7_6.6.x86_64 --> Processing Dependency: kernel-headers for package: glibc-headers-2.17-260.el7_6.6.x86_64 --> Running transaction check ---> Package glibc.i686 0:2.17-260.el7_6.6 will be installed --> Processing Dependency: glibc-common = 2.17-260.el7_6.6 for package: glibc-2.17-260.el7_6.6.i686 ---> Package kernel-headers.x86_64 0:3.10.0-957.21.3.el7 will be installed ---> Package nss-softokn-freebl.i686 0:3.36.0-5.el7_5 will be installed --> Finished Dependency Resolution Error: Package: glibc-2.17-260.el7_6.6.i686 (rhel-7-server-os-rpms) Requires: glibc-common = 2.17-260.el7_6.6 Installed: glibc-common-2.17-292.el7.x86_64 (installed) glibc-common = 2.17-292.el7 Available: glibc-common-2.17-55.el7.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-55.el7 Available: glibc-common-2.17-55.el7_0.1.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-55.el7_0.1 Available: glibc-common-2.17-55.el7_0.3.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-55.el7_0.3 Available: glibc-common-2.17-55.el7_0.5.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-55.el7_0.5 Available: glibc-common-2.17-78.el7.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-78.el7 Available: glibc-common-2.17-105.el7.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-105.el7 Available: glibc-common-2.17-106.el7_2.1.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-106.el7_2.1 Available: glibc-common-2.17-106.el7_2.4.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-106.el7_2.4 Available: glibc-common-2.17-106.el7_2.6.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-106.el7_2.6 Available: glibc-common-2.17-106.el7_2.8.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-106.el7_2.8 Available: glibc-common-2.17-157.el7.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-157.el7 Available: glibc-common-2.17-157.el7_3.1.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-157.el7_3.1 Available: glibc-common-2.17-157.el7_3.2.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-157.el7_3.2 Available: glibc-common-2.17-157.el7_3.4.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-157.el7_3.4 Available: glibc-common-2.17-157.el7_3.5.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-157.el7_3.5 Available: glibc-common-2.17-196.el7.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-196.el7 Available: glibc-common-2.17-196.el7_4.2.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-196.el7_4.2 Available: glibc-common-2.17-222.el7.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-222.el7 Available: glibc-common-2.17-260.el7.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-260.el7 Available: glibc-common-2.17-260.el7_6.3.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-260.el7_6.3 Available: glibc-common-2.17-260.el7_6.4.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-260.el7_6.4 Available: glibc-common-2.17-260.el7_6.5.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-260.el7_6.5 Available: glibc-common-2.17-260.el7_6.6.x86_64 (rhel-7-server-os-rpms) glibc-common = 2.17-260.el7_6.6 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@zcervink1-rhel-77 ~]#