Bug 334809

Summary: YaST2 terminates when trying to change package architecture
Product: [openSUSE] openSUSE 10.3 Reporter: Juergen Orschiedt <jorschiedt>
Component: libzyppAssignee: Stefan Schubert <schubi>
Status: RESOLVED NORESPONSE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: kkaempf
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 10.3   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Screenshot of YaST2 installation process
corresponding YaSt2 logfile

Description Juergen Orschiedt 2007-10-18 11:59:42 UTC 
Had problem #334783 (#2) - 32bit plugin with 64bit JVM.
Tried to resolve by advicing the installer to use the 32bit version of JAVA-1_6_0*sun (see attached screenshot).
YaST2 showed the installation window without any package in.
YaST2 logfile is also attached.
Comment 1 Juergen Orschiedt 2007-10-18 12:00:42 UTC 
Created attachment 179214 [details]
Screenshot of YaST2 installation process
Comment 2 Juergen Orschiedt 2007-10-18 12:04:27 UTC 
Created attachment 179215 [details]
corresponding YaSt2 logfile
Comment 3 Klaus Kämpf 2007-10-19 10:12:46 UTC 

*** This bug has been marked as a duplicate of bug 334783 ***
Comment 4 Juergen Orschiedt 2007-10-19 12:00:12 UTC 
architecture: x86_64
installed the java-1_6_0-sun-plugin-1.6.0.u3-0.1 (32bit)
propably because of a packaging problem, YaST selected the java-1_6_0-sun-1.6.0.u3-0.1 64bit JRE, which was found AFTER the complete installation process.
So I started YaST again, to exchange the 64bit package against the 32bit package (see screenshot from comment #1, which was taken during a later step) by selecting the "1.6.0.u3-0.1 i586" from  'Versions'.
Instead of deleteing the 64bit package and installing the 32bit one, I simply got an processing window without any package in, YaST simply didn't exchange the 64bit against the requested 32bit package.

To get rid of the 64bit JRE I had to manually delete the java-1_6_0-sun and add the 32bit version in an own step.
Comment 5 Ladislav Slezák 2007-11-20 13:32:00 UTC 
According to comment #4 the problem seems to be in the solver, reassigning...
Comment 7 Stefan Schubert 2007-12-05 11:53:01 UTC 
ping ;-)
Comment 8 Stefan Schubert 2008-01-04 13:23:58 UTC 
Feel free to reopen the bug if you can provide a testcase.