Bug 144736 - yast shows security updates also if newer versions are installed
Summary: yast shows security updates also if newer versions are installed
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YOU (show other bugs)
Version: Final
Hardware: Other Linux
: P5 - None : Minor
Target Milestone: ---
Assignee: Harald Mueller-Ney
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-23 09:21 UTC by ferdinand gassauer
Modified: 2006-02-13 13:20 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 ferdinand gassauer 2006-01-23 09:21:12 UTC 
if suplementary packages from
ftp://suse.inode.at/pub/i386/supplementary/
are installed, yast still reports security updates for the "base" distribution packages.

This renders the "red ball" announcing new security updates usesless (more or less)
*) it's good to know
*) usually no need to downgrade
*) the red ball does not disappear any more - hence making the automatic checking feature obsolete, because it's always ON / red.
Comment 1 Harald Mueller-Ney 2006-02-13 13:20:05 UTC 
Many thanks for you bug report. 

This problems is known, there is no easy way to change it (YaST Online Update) in SUSE Linux 10.0. We are currently working hard to release SUSE 10.1 - Beta3 is currently available - so that I see no chance to work on this issue recently.
I can imagine this hits you as KDE developers harder than most others cause the (unsupported) supplementary tree contains the latest KDE packages.

The update mechanism for SUSE Linux 10.1 will be very much improved in this regard, so that I expect this problem fixed with the final SUSE Linux 10.1.

I see know chance to fix this now for SUSE Linux 10.1 - the kicker plugin (red ball) used YaST Online Update for checking. 

I set it to "can't fix" (wontfix).