On Tue, 2005-01-18 at 10:03 -0500, Jeff Spaleta wrote:
On Tue, 18 Jan 2005 08:44:23 -0600, Chris Adams
<cmadams(a)hiwaay.net> wrote:
> There is an update to wireless-tools in updates-released, but
> NetworkManager blocks it because it is linked against libiw.so.27 and
> the new wireless-tools provides libiw.so.28.
>
> yum doesn't handle this problem very well either:
yum handles the problem just fine.....
yum tries to resolve the deps... there are conflicting deps so yum fails.
What would you prefer yum do? Install a package in a way that causes
a broken dep chain inside your rpm database? If the deps can't be met
without causing conflicts, yum tells you and stop processing, how is
this not correct behavior when there really is a broken dep in the
repo tree?
To be fair it's a case I should be checking for in yum.
if a package is already in the ts and it's not one of the packages that
can be installed multiple times:
raise an error and/or cause problems.
-sv