Red Hat Bugzilla – Bug 242279
yumex ignored dependencies when installing
Last modified: 2008-05-15 13:32:03 EDT
Description of problem:
I just installed x86_64 fedora 7 from DVD, did a "yum install yumex", then
ran yumex to install a slew of additional stuff not on the DVD image. Among
the things I installed (which I have so far noticed are messed up) are
claws-mail (along with lots of claws-mail plugins) and bogofilter. The
claws-mail rpm says it depends on compface and libetpan (I ran rpm -q -R
to be sure, and they are listed), and bogofilter says it depends on libgsl,
yet none of those libraries were installed. The tools wouldn't run till
I explicitly installed those libs.
Version-Release number of selected component (if applicable):
I had similar problems in test4 and figured I just thumb fingered something,
but it has happened again on f7 final with my reinstall. In fact, I just
rand package-cleanup --problems and I see a whole slew of other missing
libraries (I'll attache the listing), all for things I installed in my
initial yumex run (mplayer, vlc, etc).
Steps to Reproduce:
1. install f7 x86_64
2. install yumex
3. use yumex to install gobs of additional packages
loads of missing libraries
dependencies should have been added and installed
Obviously I have no idea if this is a yumex problem only or it is in
the lower level yum layers yumex uses.
Created attachment 156002 [details]
output from package-cleanup --problems
Seems like this probably isn't a yumex bug, but a yum bug. I've just
submitted bug 242368 after installing i386 fedora 7 in a new partition
and running into the same missing dependency problems using pirut to
add the additional packages as I had using yumex on the 64 bit f7
This is caused by a bug in yum, it is fixed in upstream yum cvs and will be
available in yum 3.2.1.
I have made a temporary work around to solve this in current yumex SVN, it will
be available in next yumex release.
yumex-1.9.9-1.0.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
This bug appears to have been resolved for me (it caused some major headaches).
Thanks for the 1.9.9-1.0.fc7 update, much appreciated.
yumex-1.9.9-1.0.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.
Its back :-).
I ran updates yesterday which tried to pull down a new rpmdevtools and
elfutils-libs. The dependency analysis added fakeroot as a dependency
When it tried to run the transaction, the elfutils-libs signature problem
that was discussed in the fedora users mailing list cropped up, so I went
to the queue page, removed all the elfutils related rpms from the queue and
said process queue.
Following that update, package-cleanup --problems said that fakeroot was
missing, so somehow fakeroot disappeared from the transaction when I edited
the queue and tried again (exactly the same circumstance that happened
when I first submitted this bug).
Please retest with current version of yum-3.2.5
It's probably a yumex error. After selecting packages, the dependency checking
happens and the dependencies along with the selected packages appear in the
After you click it goes into downloading the rpms, if a download fails (i.e.
lose network connection), or the installation process fails, yumex simply stops
- allowing you to continue with whatever. It has _not_ however added the
dependencies to the package queue, and when you reprocess the queue it fails to
recheck them. Thus it downloads the ones you have selected without the
dependencies, then installs them causing problems.
I have a dodgy wireless connection where I am and keep running into this problem
I've also seen this problem with yum-3.2.5-1.fc7 and yumex-2.0.2-1.fc7. If you
try to install something with dependencies, when yumex asks you to download and
install everything, including the dependencies, you you click on "cancel" then
"proceed queue" again, the dependencies are not presented in the list of
packages to download and install.
If you exit yumex and restart it, everything works fine again.
the yum depsolver has been a moving target lately, so this error keep popping up.
I will make it work with current yum
I have tried the following with:
Test case 1:
Selected BackupPC and 'process queue'
got a confirmation dialog with some deps.
press 'cancel' and 'process queue' again
Got the same confirmation dialog with same deps.
Test case 2:
removed openoffice.org base etc.
Selected 'openoffice.org-writer & openoffice.org-langpack-da_DK'
'Process Queue' & 'Ok' on confirmation dialog.
Disabled my wireless connection while downloading
pressed the 'Skip' button to skip mirror and provoke a lot of timeout errors.
Af the error dialog, i selected 'Process Queue' again and got the same
confirmation dialog with the same deps.
Try update to yum-3.2.7 in updates-testing and try again.
(yum --enablerepo=updates-testing update yum)
Do you still have this issue ?
I certainly haven't seen it for a long time. I'm not sure
that proves it is gone :-).
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.
Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping