[Bug 335510] New: Don' t ask the user about solving dependencies while upgrading from one distversion to another
https://bugzilla.novell.com/show_bug.cgi?id=335510 Summary: Don't ask the user about solving dependencies while upgrading from one distversion to another Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: openSUSE 10.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: geroxp@web.de QAContact: jsrain@novell.com Found By: --- Recently I had to help a friend of mine solving boot problems with his openSuSE 10.3 operating system. It turned out that while upgrading from 10.2 he was asked about a lot unresolved dependencies and choosed to delete packages rather then upgrade the package (yast said something about that would change the "provider" of the package). So he deleted "hal". Since hal is absolutely necessary for openSuSE to startup his system wouldn't boot anymore (it said that /dev/hda could not be found). Also in conjunction with that "solved" dependency issues grub was not upgraded properly resulting in a useless entry in menu.lst where an "initrd" was set that doesn't even exist. Well, to cut a long story short: The novice user should not be bothered with such questions like if he/she wants "to upgrade a package that would change the provider" or such weird questions that the average user simply does not understand. Please read the following comment that really gets this to the point: https://bugs.launchpad.net/ubuntu/+bug/1/comments/493 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=335510
Matej Horvath
https://bugzilla.novell.com/show_bug.cgi?id=335510#c2
Stefan Hundhammer
https://bugzilla.novell.com/show_bug.cgi?id=335510#c3
Stefan Hundhammer
Please read the following comment that really gets this to the point: https://bugs.launchpad.net/ubuntu/+bug/1/comments/493
This is utterly unrelated. For one thing, it's a mind set problem. Compare here: http://linux.oneandoneis2.org/LNW.htm For another, that seemingly great idea of have simple mode for novices and an expert mode for experts is an approach that falls apart when thinking it through for just a few minutes. There are no users (OK, make this "almost no users") who are experts in every area. And installation is something that covers a lot of areas. While somebody might be an expert when it comes to partitioning, this same user might be completely lost with, say, software dependencies. An "expert mode", though, would force him to answer expert questions in every area. This is why our approach to all that is to begin as simple as possible and offer an "expert" button whereever it makes sense. That way, every user can use a simple approach where hit makes sense for him, but gradually refine expert options where the simple solution does not cover his particular use case. Not only does this cover the novice case AND the some-areas-expert case (which is the most common), it also covers the case where even the expert wants something to be done quick and simple. The situation this bug report is all about is pathological. It is not the normal case. Sure, it would be desirable to not get into that situation in the first place. Is that feasible? I don't know. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=335510#c4
--- Comment #4 from Gero Mudersbach
If we knew a solution without asking the user those questions, we wouldn't bother him with that.
The solution would be to install the update even if it changes the provider of the package. If the package isn't locked somehow that would be no problem.
And besides, this is nothing that could possibly be changed on the UI level. If at all, it would be something for the solver.
Not sure. This bug is also about the meaning of the questions asked by yast. If such questions arise it should be more coherent so even a novice can get a clue what it means.
For one thing, it's a mind set problem. Compare here: http://linux.oneandoneis2.org/LNW.htm
Okay, what are the goals here? Is it to have a desktop-system which is intended only for the enterprise where software-upgrades are handled by administrators who know what todo? Or is it also a system for small companies or stand-alone workstations (laptops, freelancers, home users etc.)? Linux is not Windows, thats for sure! But should it be complicated then? :)
The situation this bug report is all about is pathological. It is not the normal case. Sure, it would be desirable to not get into that situation in the first place. Is that feasible? I don't know.
I can only speak from my own experience. Everytime I have to update and or upgrade an openSuse system I have these dependency problems. I know why this is not the "normal" case: The standard installation of openSuse comes with no things like multimedia capabilities (like mp3, DVD etc.) and other toys. These days you can tell nobody that it's impossible to handle an encrypted DVD or just play an mp3 file for an operating system. So everybody, even the corporate users with their laptops using free operating systems install that things on top of the normal system. So almost everybody (at least the many I know) have additional repos configured that provide such packages. Now, the openSuse community could say: "Hey, it's not our fault." Thats right, but we could also take this opportunity to improve the user experience and usability of the system. My proposals for the first step are as follows: - Examine the usability of yast and its underlying solver in conjunction with dependency problems - Check if the descriptions of problems reported by yast are coherent and distinct - Check if it is possible to optimize the solving process (don't ask the user about the same package twice, embrace dependency problems concerning the same package) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=335510
User schubi@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=335510#c5
Stefan Schubert
participants (1)
-
bugzilla_noreply@novell.com