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.
Description of problem:
depsolve_loop_limit 0 or "forever" should mean that depsolver will executed forever until resolves all dependencies, but in fact it causes that depsolver exits immediately.
depsolve_loop_limit 1 does not works too as expected.
Moreover, the yum.cons man page is not correct; it says "forever" as a keywork can be used, but it is not accepted by yum. "<forever>" is the correct keyword.
More details can be fond in bug 1038299.
Version-Release number of selected component (if applicable):
yum-3.4.3-106.2.el7
How reproducible:
always
Steps to Reproduce:
0 [root@rhel7 ~ ]# grep depsolv /etc/yum.conf
depsolve_loop_limit=2
0 [root@rhel7 ~ ]# yum install ksh
Loaded plugins: auto-update-debuginfo, product-id, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Resolving Dependencies
--> Running transaction check
---> Package ksh.x86_64 0:20120801-11.el7 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Installing:
ksh x86_64 20120801-11.el7 rhel7 874 k
Transaction Summary
================================================================================
Install 1 Package
Total download size: 874 k
Installed size: 3.1 M
Is this ok [y/d/N]: n
Exiting on user command
Your transaction was saved, rerun it with:
yum load-transaction /tmp/yum_save_tx.2013-12-12.16-42.VOWqKV.yumtx
1 [root@rhel7 ~ ]#
1 [root@rhel7 ~ ]# sed -i 's/depsolve_loop_limit.*/depsolve_loop_limit=1/' /etc/yum.conf
0 [root@rhel7 ~ ]# yum install ksh
Loaded plugins: auto-update-debuginfo, product-id, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Resolving Dependencies
--> Running transaction check
---> Package ksh.x86_64 0:20120801-11.el7 will be installed
--> Running transaction check
Error: Depsolving loop limit reached.
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
1 [root@rhel7 ~ ]# sed -i 's/depsolve_loop_limit.*/depsolve_loop_limit=0/' /etc/yum.conf
0 [root@rhel7 ~ ]# yum install ksh
Loaded plugins: auto-update-debuginfo, product-id, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Resolving Dependencies
Error: Depsolving loop limit reached.
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
1 [root@rhel7 ~ ]#
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.