Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 471868 [details] Output from "yum -d5 -y update --skip-broken --nogpg" (after installing a lot with exclude and selecting, this should be close to the minimal conflicted set) Description of problem: Running "yum -y update --skip-broken --nogpg" fails, saying that lots of packages are "not found" (?), and updates nothing (even though there are lots of packages that can be updated using --exclude and/or stating non-problematic packages) Version-Release number of selected component (if applicable): yum-3.2.28-14.fc15.noarch How reproducible: On and off (depending on what exactly is updated in the repos). It fails today here (I'm running texlive-2010 from J. Novy's repo). Steps to Reproduce: 1. yum -y update --skip-broken 2. 3. Actual results: Total failure Expected results: Install what doesn't conflict Additional info: When something like this happened earlier, installing (most?) of the conflict freee packages then made yum behave (i.e., only skip truly broken ones, and install the rest). Now it seems to fail regardless.
Look like this none :( https://bugzilla.redhat.com/show_bug.cgi?id=666950 Try this on: https://bugzilla.redhat.com/show_bug.cgi?id=666950#c2
Created attachment 471902 [details] Output from "yum -d9 -y update --skip-broken --exclude=libreoffice\* --exclude=poppler\*" Installing much by "yum -y update package" and/or "--exclude=something" fixed most of the problems, this used to crash and burn regardless exclusions.
Created attachment 471903 [details] Output from "yum -d9 -y update --skip-broken"
This has happened on and off for some time here. And like https://bugzilla.redhat.com/show_bug.cgi?id=666950#c4, updating most of the stuff that can be updated used to fix the "Skip broken can't fix" and no updates at all.
Created attachment 472087 [details] Output from "yum -d9 -y update --skip-broken", yum-3.2.28-16.fc15.noarch
Created attachment 472091 [details] Output from "yum -d9 -y update --skip-broken --exclude=libreoffice\* --exclude=poppler\*", yum--3.2.28-16.fc15.noarch
I just tried new yum on my netbook (sees little use currently, so lags way behind). There were some 700 updates available. Updated yum, and tried to update the rest... it failed with a slew of conflicts. Excluding the "usual suspects" didn't help, so I selected a bunch of around 100 packages that didn't conflict (libreoffice*, texlive-*, kernel* and some more), updated them and tried again. Still failure. Rinse and repeat several times until a final "yum -y update --skip-broken" went through (almost... Thunar fails due to a packaging problem). The strange thing is that the packages skiped at the end were a half dozen or so, but during the process it complained about many, many more conflicted packages. I thought it had gone into a loop as it listed the packages to update some 3 or 4 times before getting on with the updating business. Sorry for the rambling.
I think that the current upstream will solve these issues, so i will close this one for now, please test with current upstream if you hit any problems. cd <some workdir> git clone git://yum.baseurl.org/yum.git cd yum git checkout -t origin/yum-3_2_X ./yummain.py -d5 update
So you're sa(In reply to comment #8) > I think that the current upstream will solve these issues, so i will close this > one for now, please test with current upstream if you hit any problems. > > cd <some workdir> > git clone git://yum.baseurl.org/yum.git > cd yum > git checkout -t origin/yum-3_2_X > ./yummain.py -d5 update So you're saying this is a bug, but it's upstream? If so, is there an upstream bug number?
It is fixed in the upstream git repo :)