Bug 121835 - you still thinks I am on SUSE 9.3 after upgrade to 10
Summary: you still thinks I am on SUSE 9.3 after upgrade to 10
Status: RESOLVED DUPLICATE of bug 116339
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YOU (show other bugs)
Version: Final
Hardware: 32bit SUSE Other
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-08 08:42 UTC by Thorsten Staerk
Modified: 2005-10-11 07:04 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thorsten Staerk 2005-10-08 08:42:13 UTC 
you still thinks I am on SUSE 9.3 after upgrade to 10. Please have a look at 
http://blog.mecworks.com/articles/2005/04/12/fixed-you-error-on-suse-93/ 
describing the same bug for the upgrade from 9.2 to 9.3.
Comment 1 Michael Radziej 2005-10-10 09:45:40 UTC 
How did you update? Did you use the "system update" icon in the YaST control
center, or did you boot from the installation media?
Comment 2 Thorsten Staerk 2005-10-10 17:23:53 UTC 
I used the "system update" icon in the YaST control center.
Comment 3 Michael Radziej 2005-10-10 17:28:38 UTC 

*** This bug has been marked as a duplicate of 116339 ***
Comment 4 Thorsten Staerk 2005-10-10 19:35:48 UTC 
you CLOSE a bug, marking it as duplicate of a STRIKETHROUGH bug that has been 
MARKED AS RESOLVED because of your last comment "we accept patches for 
this" ???
Comment 5 Klaus Kämpf 2005-10-11 07:04:15 UTC 
Well, currently there is no easy way to fix this in older products. And the 
amount of users falling into this 'trap' is relatively small. OTOH, this 
function did save a lot of defective systems by bringing them to a consistent 
state. 
 
So please boot with CD1 and choose 'update'. This should fix your system. 
 
This is a duplicate of 116339 and correctly marked as such. 

*** This bug has been marked as a duplicate of 116339 ***