Bug 612276 - skip-broken: looping forever trying to upgrade from f13 to rawhide
Summary: skip-broken: looping forever trying to upgrade from f13 to rawhide
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: rawhide
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-07 18:17 UTC by Adam Williamson
Modified: 2014-01-21 23:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-09 18:24:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
console output during a failed attempt (35.54 KB, text/plain)
2010-07-07 18:17 UTC, Adam Williamson
no flags Details

Description Adam Williamson 2010-07-07 18:17:05 UTC
Trying to do 'yum upgrade --skip-broken' to update from F13 to rawhide results in yum looping apparently forever at the dependency resolution stage. Output of a typical such session attached. It seems to cycle a few times showing fewer and fewer dependency searches each time for a while, but then it settles down showing the same set of perl deps, over and over again. It'll sit doing this for at least half an hour if I leave it, that's the longest I've tried.

Note that yum and rpm are at their fc14 versions. yum-3.2.27-17.fc14.noarch , rpm-4.8.1-3.fc14.x86_64 .

Comment 1 Adam Williamson 2010-07-07 18:17:36 UTC
Created attachment 430143 [details]
console output during a failed attempt

Comment 2 Tim Lauridsen 2010-07-09 16:15:40 UTC
Could you please test with 'yum -d9 --skip-broken ....' to get an idea what goes wrong

Comment 3 Adam Williamson 2010-07-09 18:24:58 UTC
actually I just got bored, removed the packages that required the use of --skip-broken, and updated that way. So i'll close this as we can't really reproduce it now.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers


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