Red Hat Bugzilla – Bug 489271
NetworkManager fails to update due to depsolving problem with NetworkManager-openconnect
Last modified: 2009-03-12 07:49:24 EDT
Description of problem:
The last update via yum failed due to depsolving problem. Not a problem for an expert, but newbees could be stressed and as it aborts the update they would not get other security fixes.
Version-Release number of selected component (if applicable):
[root@localhost ~]# rpm -qa | grep NetworkManager
trying to update to
Regular update via yum.
Steps to Reproduce:
1. run yum -d 9 update
--> Processing Conflict: NetworkManager conflicts NetworkManager-openconnect < 1:0.7.0.99-1
NetworkManager conflicts with NetworkManager-openconnect
--> Finished Dependency Resolution
Dependency Process ending
1:NetworkManager-0.7.0.99-1.fc10.x86_64 from updates has depsolving problems
--> NetworkManager conflicts with NetworkManager-openconnect
This is not the first time the NetworkManager has depsolving issues. Several months ago it was NetworkManager-openvpn (I had Fedora 8 that time) that triggered the problem. Is it a sign of some deeper issues in handling NetworkManager dependencies?
And one more note to yum: I guess it is not correct that a single depsolving issue aborts the installation of other (independent) security fixes. What I would expect is some higher level intelligence: if there is a depsolving issue with a single package, report it and allow user to choose to skip this package, so the rest is updated. A plugin? or a yum core feature?
*** Bug 489340 has been marked as a duplicate of this bug. ***
*** Bug 489332 has been marked as a duplicate of this bug. ***
This bug has been triaged.
Fedora Bugzappers volunteer triage team
NetworkManager-0.7.0.99-2.fc10 has been submitted as an update for Fedora 10.
NetworkManager-0.7.0.99-2.fc9 has been submitted as an update for Fedora 9.
NetworkManager-0.7.0.99-3.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
NetworkManager-0.7.0.99-3.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 489364 has been marked as a duplicate of this bug. ***
NEXTRELEASE is it mean fedora 11?
Nah, currentrelease, sorry. -3 fixes the problem.
Sorry to spam a closed bug. With regard to the yum question, you can use the '--skip-broken' option to skip over depsolving problems.