Bug 151950 - YaST System Update falsely claims installation source as being not compatible
Summary: YaST System Update falsely claims installation source as being not compatible
Status: RESOLVED DUPLICATE of bug 186719
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 4
Hardware: i686 SuSE Linux 10.1
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-17 20:51 UTC by Forgotten User OS1JNCFbCX
Modified: 2006-06-21 11:14 UTC (History)
1 user (show)

See Also:
Found By: Beta-Customer
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 Forgotten User OS1JNCFbCX 2006-02-17 20:51:05 UTC 
When trying to run YaST system update on a system updated to the latest packages in factory it complains that the installation source (it was originally installed from) is not compatible. A message box appears that complains: "The installed product is not compatible with the product on the installation media..."
Comment 1 Michael Gross 2006-02-20 12:58:03 UTC 
Robert, this issue is known:
Here from http://en.opensuse.org/Bugs:Most_Annoying_Bugs

# Only a fresh installation is supported. Update from a previous installation is not working!

Which means that the update-feature is broken right now and is a work in progress.
Comment 2 Forgotten User OS1JNCFbCX 2006-02-20 13:05:23 UTC 
Well, one should add bug numbers to these most annoying bugs then to get more details and to allow other users follow the progress of these problems. Otherwise you have practically no real chance to decide whether a bug you see is related to a mentioned most annoying bug or not.
Comment 3 Jiri Srain 2006-06-21 11:14:07 UTC 
reopenning...
Comment 4 Jiri Srain 2006-06-21 11:14:55 UTC 
... and resolving as duplicate of another report.

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