Aniruddha wrote:
On Thu, 2007-10-11 at 13:42 +0200, Stefan Hundhammer wrote:
My solution is simple; just automatically remove the conflicting files and let the user know you are doing that. Or provide sane default setting which can be easily agreed upon. ... In the old (pre-10.1) package manager we offered that kind of solution. But frankly, it was never very useful. And those users who selected that probably had to reinstall the system in most cases.
I don't think it's a good idea to reintroduce that kind of behaviour. It hurts more than it could possibly heal.
The more I work with openSUSE the more I feel the dependency handling by zypper/yast2 really needs improvement. Updating becomes impossible for novices. Right now when I want to update I get the following error, it really is a shame that one has manually delete packages in order to fix dependency problems manually:
2 Problems: Problem: No valid solution found with just resolvables of best architecture. Problem: Cannot install wesnoth-data-base, because it is conflicting with wesnoth-data Problem: No valid solution found with just resolvables of best architecture. With this run only resolvables with the best architecture have been regarded. Regarding all possible resolvables takes time, but can come to a valid result.
Solution 1: Make a solver run with ALL possibilities. Regarding all resolvables with a compatible architecture. number, (r)etry or (c)ancel>
- enter '1' here - you'll get a solution proposal for the next problem - choose the solution number you like (probably 'remove wesnoth-data') hth Jano -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org