https://bugzilla.novell.com/show_bug.cgi?id=704344
https://bugzilla.novell.com/show_bug.cgi?id=704344#c10
Scott Couston
wrote earlier, that I myself tested the first scenario (boot new media, select Update) and was warned by YaST about different architecture.
Have you done it the same way, but did not see a warning? Than it would be YaST bug that you were not warned.
Or, have you seen the warning, entered package manager and it came up with tons of conflicts? If this is the case, do you consider as bug that you were allowed to enter package manager? Yes, you observed the same test condition as I and got the same result! I am the first to ack that this may be a Yast issue and/or Installation. In this test the packet manager displays a huge amount of X_64 library files to be replaced with I586. If we permit the packet manager conflicts to be accepted to I586 and the installation proceed further; ultimately the Kernel and/or Video specific files will be I586 and the X_64 PC will not boot. The user sees the same issue we see if we try to boot from a the wrong Kernel specific discord with the CPU architecture - The total I584 version would replace the X64 producing either inability to boot and/or completely stuff up Video and perhaps old X_64 repositories. The PC would be totally useless. I dont think there would ever be a deliberate reason to do this! I think at the same time we halt such an installation, we do so by refinement to the packet manager, not offering ANY solution to change software architecture related Library, Kernel and Video files. At the same time we should also make sure an existing PC-MAC installation cannot be upgraded to an I586 and X_64 based PC and vice-a-versa (sp) -- 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.