Bug 145404 - NetworkManager blocks current update to wireless-tools
Summary: NetworkManager blocks current update to wireless-tools
Status: CLOSED DUPLICATE of bug 145395
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 3
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Dan Williams
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-01-18 01:02 UTC by Michal Jaegermann
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2006-02-21 19:07:59 UTC

Attachments (Terms of Use)

Description Michal Jaegermann 2005-01-18 01:02:35 UTC
Description of problem:

'rpm -qR NetworkManager' shows 'wireless-tools >= 27' but also
'libiw.so.27'.  This is causing trouble as then current update
'wireless-tools-28-0.pre4.1.fc3' provides libiw.so.28 and yum
attempts to pull wireless-tools - 1:27-0.pre25.2 "as update for 
NetworkManager" (this is from a yum debug output) even if
wireless-tools-27-0.pre25.3 are currently installed.  That action,
not so surprisingly, fails and we have a dependency problem until
NetworkManager will get the next update.

yum, alas, does not skip automatically through such sore spots
when simply asked 'update' or 'upgrade'.

Version-Release number of selected component (if applicable):

Comment 1 David Martin 2005-01-18 01:41:47 UTC
I have the same problem. Here's the error from up2date. Seems like
kdenetwork depends on libiw.so.27 as well:

There was a package dependency problem.  The message was:

Unresolvable chain of dependencies:
NetworkManager  0.3.3-1.cvs20050112.1.fc requires libiw.so.27
kdenetwork  3.3.1-1                      requires libiw.so.27

Please modify your package selections and try again.

Comment 2 Michal Jaegermann 2005-01-18 04:10:40 UTC
Oh, I happen not to have kdenetwork installed so I missed that.
Does this dependency on libiw.so has to be that specific?
This will cause headaches every time wireless-tools version
will get bumped up.

Comment 3 Dan Williams 2005-01-18 14:18:30 UTC

*** This bug has been marked as a duplicate of 145395 ***

Comment 4 Red Hat Bugzilla 2006-02-21 19:07:59 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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