Bug 342635

Summary: upgrade 10.2 to 10.3 complications with extra repositories
Product: [openSUSE] openSUSE 10.3 Reporter: ferdinand gassauer <gassauer>
Component: YaST2Assignee: Stefan Schubert <schubi>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Enhancement    
Priority: P5 - None CC: tgoettlicher
Version: Final   
Target Milestone: ---   
Hardware: 64bit   
OS: Linux   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2logs

Description ferdinand gassauer 2007-11-19 07:47:48 UTC 
having installed KDE 3.5.8 , some guru and packman packages the upgrade process should be enhanced.

* the option "delete unmaintained packages" does not delete packman and gutu packages

* KDE is not downgraded to 3.5.7 which is distributed as standard.

* the solver is not able to detect and report this.

* the installation summary does not show the "kept" packages unless clicked. 
workaround for this:
-> delete "kept" packages - just select only "kept" messages in the summary and delete all.

* a "downgrade to distribution" option is missing.
workaround for this:
-> upgrade unconditionally - which IMHO should be the default for migrations from 10.2 to 20.3.

thank you for listening
Comment 1 ferdinand gassauer 2007-11-19 07:48:35 UTC 
gutu = guru of course
Comment 2 Thomas Göttlicher 2007-11-27 09:18:59 UTC 
Please attach y2logs. If you are in doubt follow:

http://en.opensuse.org/Bugs/YaST

Thanks!
Comment 3 Thomas Göttlicher 2007-11-27 09:22:32 UTC 
Stefan, can help with this solver issue, please?
Comment 5 ferdinand gassauer 2007-11-27 10:42:59 UTC 
Created attachment 184842 [details]
 y2logs

I  think I can not follow Stefans suggestion "solver testcase", because I have solved the problems manually as described in the bug report.

I attach the logfiles generated with 
"save_y2logs /tmp/y2logs.tgz"

BTW 
what does this checkbox really mean?
"Big File - Stored locally and may be purged"
* what is "Big"
* where is "locally" 
* consequences of "may be purged"
Comment 6 Stefan Schubert 2008-04-23 12:49:18 UTC 
We have changed the complete update machanism for 11.0. This should be solved since beta1