Bugzilla – Bug 227375
cannot resolve conflicts
Last modified: 2007-01-02 08:49:18 UTC
I used opensuse 10.0 and conflict resolution was simple -- if I try to delete package A, but there was package B depending on it, I could keep A, delete B as well or ignore conflict. But with 10.2 it does not work at all. If I try to keep A, there is still conflict (???), if I try to delete B as well there is still conflict, all I can do is to ignore conflict. What kind of conflict resolving is this? Since I don't see any patch for yast2 in updates (just checked) I think it is a major bug since system is unusable.
Please attach your yast log files. http://en.opensuse.org/Bugs/YaST Thank you.
Created attachment 109008 [details] y2logs
The only error which I see a lot of time is: ******** Error: ResolverInfo<NO_PROVIDER> OpenOffice_org-kde-2.0.4-38.i586[20061208-221351] Error!>>There are no install able providers of libuno_sal.so.3 for OpenOffice_org-kde-2.0.4-38.i586[20061208-221351]<<, Trigger: none It has nothing to do with conflicts. Please try to reproduce your error and create a testcase described here: http://en.opensuse.org/Bugs/YaST#I_want_to_report_a_bug_related_to_package_dependencies_and_libzypp_solver._Which_logs_to_attach.3F
Created attachment 109439 [details] dep. logs Hmm, this is a good lesson for me -- next time write everything down. I cannot find a good self dependant packages, I admit yast2 now work pretty well (Murphy's law :-( ). There are strange dependencies (like OO-quickstarter -> kde, or kpowersave -> preload) but this has nothing to do with resolving conflicts I described. I'll try to do some more tests, as soon as I find good dependency conflict I let you know.
So meanwhile I close this bug. Feel free to reopen it if you have more information.
Ok, here it is -- wxdfast based on wxGTK, right? Simple dependency. I try to remove wxGTK. Yast2 asked me about conflict, I set "keep wxdfast", then yast2 asked me again: * keep wxdfast * delete wxGTK * ignore * ignore all Here is the bug, because I already answered this question, but what the heck -- I can click this "ignore", right? I click it, and I see the same question -- over and over again. There was not such problems with 10.0 -- when I said ignore, the package was ignored. Btw. ignore all does not make any difference. I have to run rpm manually to remove this package.
Aaah, thanks. The reason for that behaviour has been double resolvable entries in the pool. This has been fixed meanwhile.