Bugzilla – Bug 280387
zypper hangs resolving dependencies
Last modified: 2007-08-06 08:10:32 UTC
There is a bug report for this which I added to, but can't find in searches. If dependencies for a package are missing in 10.3 Alpha4 update, the resolver doesn't report it, it simply keeps trying forever. e.g changing status of emacs to "update" and the updater never returns with missing dependencies. Download the package and do "rpm -Uvh <package>.x86_64.rpm", it then reports failed dependencies. What I do next is to kill -9 all "yast sw_single" processess "rm /var/run/zypp.pid", CTRL-ALT-ESC and bomb out the installer window. Next time around, I bypass updating that package. I have also tried downloading all the latest yast and zypp RPM's and doing rpm -Uvh, still does not fix the problem.
Created attachment 143780 [details] y2logs
*** This bug has been marked as a duplicate of bug 275100 ***
This bug incorrectly flagged as a duplicate of bug 275100. It persists right up to 10.3 Alpha6plus on both x86_64 and a x86 fresh install done a few days ago. Workaround is as detailed above. The dependencies never get resolved however long it's left (8 hours+ in one case).
Selecting some packages from Factory will cause zypper to not return, stays permanently "working on" and window goes grey. Kill -9 the pids of yast2 sw_single, removing /var/run/zypp.pid and at times needing to bomb out the window is the only way to return it to sanity, then YaST --> Installation Source can be restarted. It's not capable of resolving certain dependencies.
I had one case here in which the solver run has taken a very long time. The reasons for that has been a very large logfiles in the error case. I have reduced the logging once more so we save about 80% time. But I am not sure if this reflects your problem. We have a new option in zypper : --debug-solver Generates testcase for the solver. If the error still exists please reproduce the error with the newest libzypp (3.13.6) and zypper by using this new option. Feel free to reopen the bug if this error still exists.
I just had the problem with ImageMagick. Standalone "rpm -Uvh ImageMagick-6.3.5.3-5.x86_64.rpm" gave the following:- error: Failed dependencies: libMagick.so.10()(64bit) is needed by ImageMagick-6.3.5.3-5.x86_64 libWand.so.10()(64bit) is needed by ImageMagick-6.3.5.3-5.x86_64 libMagick.so.10()(64bit) is needed by (installed) ImageMagick-Magick++-6.3.3.8-27.x86_64 libMagick.so.10()(64bit) is needed by (installed) koffice-illustration-1.6.3-6.x86_64 libMagick.so.10()(64bit) is needed by (installed) pstoedit-3.44-81.x86_64 libMagick.so.10()(64bit) is needed by (installed) libxine1-1.1.7-0.x86_64 libMagick.so.10()(64bit) is needed by (installed) psiconv-0.9.8-90.x86_64 libWand.so.10()(64bit) is needed by (installed) ImageMagick-Magick++-6.3.3.8-27.x86_64 libWand.so.10()(64bit) is needed by (installed) koffice-illustration-1.6.3-6.x86_64 libWand.so.10()(64bit) is needed by (installed) pstoedit-3.44-81.x86_64 libWand.so.10()(64bit) is needed by (installed) libxine1-1.1.7-0.x86_64 libWand.so.10()(64bit) is needed by (installed) psiconv-0.9.8-90.x86_64 ImageMagick = 6.3.3.8 is needed by (installed) ImageMagick-Magick++-6.3.3.8-27.x86_64 ImageMagick = 6.3.3.8 is needed by (installed) ImageMagick-devel-6.3.3.8-27.x86_64 Did the usual trick as previously described. Restarted YaST --> Installation Sources, upgraded libzypp and zypper, dependencies for Imagemagick now resolved.
Problem has reocurred with other packages. Begs the question why "rpm -Uvh <package>" returns "Failed dependencies", but YaST just just goes away forever.
Please generate a new bug concerning ImageMagick-6.3.5.3-5.x86_64.rpm and generate a testcase: http://en.opensuse.org/Bugs/YaST#I_want_to_report_a_bug_related_to_package_dependencies_and_libzypp_solver._Which_logs_to_attach.3F
The problem is not specific to a particular package, it's any package where there are a number of failed dependencies. ImageMagick was just an indication of what happens. I don't know if they would ever be resolved, but I've had occasions where they have not been resolved after >8 hours. May be tonight I shall open a new bug stating that zypper does not handle failed dependencies.