Sorry for re-sending, for some reason my reply was rejected.
Am 15.07.2011 17:22 schrieb "Hans-Joachim Ehlers" HansJoachim.Ehlers@eumetsat.int:
Problem: nmap-4.75-1.26.i586 requires libdnet.so.1, but this requirement cannot be provided uninstallable providers: libdnet1-1.11-87.17.i586[SUSE-Linux-Enterprise-Server-11-SP1 11.1.1-1.152] libdnet1-1.11-87.17.i586[http-10.11.8.3-bf69b41f] Solution 1: Following actions will be done: do not forbid installation of libdnet1-1.11-87.17.i586[SUSE-Linux-Enterprise-Server-11-SP1 11.1.1-1.152] do not forbid installation of liblua5_1-5.1.4-1.15.i586[SUSE-Linux-Enterprise-Server-11-SP1 11.1.1-1.152] Solution 2: Following actions will be done: do not forbid installation of libdnet1-1.11-87.17.i586[http-10.11.8.3-bf69b41f] do not forbid installation of liblua5_1-5.1.4-1.15.i586[SUSE-Linux-Enterprise-Server-11-SP1 11.1.1-1.152] Solution 3: do not ask to install a solvable providing nmap Solution 4: break nmap by ignoring some of its dependencies
Now i try to install liblua5_1 and libdnet1 but the --force option MUST be given
But: If i remove the software and its dependencies via rpm -e - in this case nmap , libdnet1 & liblua5_1 i can install nmap right right away wiyhout any errors.
Is this a know bug or do i something wrong ?
Do you have these packages in <remove-packages>? If so, this is the same behavior we see on openSUSE, and I guess it is expected, even though it is a bit annoying.
(Background: We extensively use remove-packages to "block" more than 100 packages from being auto-added during installation, because we don't need them ("default" pattern iirc, we don't use "minimal" for some reason I don't remember right now). During later steps of the machine lifetime, we have exactly the same problem because these packages are forbidden.)
Is there a nicer way to block packages during install only? Forbidding them completely seems to be a bit counter-intuitive, assuming this is the same problem.