Created attachment 325398 [details] Looping begins at TSINFO of 110 member(s) Description of problem: f10->rawhide --skip-broken is looping Version-Release number of selected component (if applicable): yum-3.2.20-4.fc11.noarch How reproducible: Always Steps to Reproduce: 1. Install f10 (KDE Live) 2. Switch to rawhide 3. yum --skip-broken update Actual results: Update does not finish. Expected results: Updated system. Additional info:
This doesn't appear to be exclusive to Rawhide. I am seeing the same thing on a freshly installed F10 machine. Perhaps there is one subtle difference. After a fresh F10 install, I do a 'yum -y --skip-broken update' and this works as expected. However, if I run the same command again, it will loop forever. I'll attach the output from 'yum -y update --skip-broken' below.
Created attachment 326581 [details] output from 'yum -y --skip-broken update' I eventually had to kill the process. I would expect that yum would realize that there is nothing to be done due to broken dependencies and exit.
Yes, it should detect a loop, but that is broken because of some recent changes to the skip-broken code. I will add some new loop checking code.
i have added some better loop detection upstream, but that dont fix the main issue, why skip-broken don't solve the problem or clean out all packages in the transaction. That need some extra testing, but it is very hard to see what goes wrong when the transaction is so big, and rawhide is so full of dep problems as it is for the moment.
Also happens on f10 here for regular upgrades (with broken dependencies / missing obsoletes for kadu). On fedora-devel it is discussed whether it would make sense to enable --skip-broken per default, which obviously isn't an option as long as this bug is present.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I just tested using yum 3.2.23 and it functioned correctly. is there anyone else still having this issue with the latest version of yum?
I will close this one, if anyone detects any skip-broken looping the please reopen.