[Bug 226041] New: A new install of 10.2 RC1 seems to be more prone to errors than 10.2
https://bugzilla.novell.com/show_bug.cgi?id=226041 Summary: A new install of 10.2 RC1 seems to be more prone to errors than 10.2 Product: openSUSE 10.2 Version: RC 1 Platform: 32bit OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: kern@sibbald.com QAContact: jsrain@novell.com Because of certain minor problems, I had to do the installation on my laptop three times before it completed correctly. The first time, I selected everything I wanted to be installed. When it got to the third CD, it complained that it could not find the package tetex on the CD. I clicked on Skip, hoping to continue without that package, and the install immediately failed and bounced into the red system error screen. If I am not mistaken on previous systems (i.e. 10.1) you would have already done a reboot and hence I would have been able to "manually" install all the missing packages. However, an attempt to reboot failed after printing GRUB in the upper left corner. I started installation again (after reburning CD 3), and this time decided to select a minimal installation. This time it completed, and I used Yast to select a large bunch of packages to install (Gnome, development tools, ...). After completing the selection, it found unresolvable conflicts. Since the information printed on the conflict page is somewhat confusing (it is hard to read what the original package is as the name seems to be mixed with other data). I mistakenly told it to remove kde-base (I think). I believed this would simply not install the update package. Well after clicking to continue, it proceeded to delete some 290 packages. Clicking on Abort had no effect. As you can imagine, this left the system in an unusable state -- the worst part was that it had removed all the yast repositories in a way that produced errors when I reran yast. The third installation went well. Recommendation: 1. Try to get the system in a stable bootable condition as fast as possible, even if it takes putting back in the reboot that 10.1 did. That reboot was not annoying to me -- rather it saved me when my CD drive died during loading the 3rd CD of version 10.1 (I finished the install via Internet using yast). 2. Please look at how the information is displayed in the conflict resolution dialog. For me the original package is not clearly displayed, and I have certainly missunderstood what deleting that particular package meant (confusion between deleting it and not upgrading). 3. Abort clearly doesn't work as it should. The process of deleting packages just ignored all my requests to abort. Please note that I mention this for your information, but the installation went no worse than the previous distros I've installed (RedHat, Fedora, debian, Ubuntu, ...). Despite the problems I had, I think you have the best installer of any distro. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226041 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |yast2-maintainers@suse.de |screening@forge.provo.novell| |.com | -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226041 lslezak@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |lslezak@novell.com Status|NEW |ASSIGNED Summary|A new install of 10.2 RC1 |Package removal cannot be aborted |seems to be more prone to | |errors than 10.2 | ------- Comment #1 from lslezak@novell.com 2006-12-05 07:50 MST ------- Skipping/ignoring a failure in the first attempt is known bug (see bug #217425). 1. The reboot behaviour won't be changed, many users were confused by the previous behaviour. If you want to install from a remote source then configure it at the boot menu. 2. The conflict resolution problem should be more described - a screenshot would be probably the best information, if you can reproduce it then create a new bugzilla entry (report only one problem in a bug report). 3. Abort problem during package uninstallation hasn't been reported yet => changing the summary accordingly -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226041 lslezak@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dmacvicar@novell.com AssignedTo|lslezak@novell.com |ma@novell.com Status|ASSIGNED |NEW Component|YaST2 |libzypp ------- Comment #2 from lslezak@novell.com 2007-02-07 02:27 MST ------- Pkg-bindings ignored the value returned from the callback handler and returned the default value to libzypp instead. The abort request was not passed to the library. Unfortunately it still doesn't work, it seems that libzypp ignores the returned value. Pkg-bindings have been fixed in SVN trunk, there are also small changes in yast2-packager. (Abort was not enabled and the abort status was not reset when the package installation was restarted.) -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226041 lslezak@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |asemen@novell.com ------- Comment #3 from lslezak@novell.com 2007-04-26 06:56 MST ------- *** Bug 256443 has been marked as a duplicate of this bug. *** -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226041 ma@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226041 User ma@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=226041#c4 Michael Andres <ma@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #4 from Michael Andres <ma@novell.com> 2008-07-07 05:18:06 MDT --- fixed on 11.0 (libzypp-4.26.1) -- 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.
participants (1)
-
bugzilla_noreply@novell.com