Bug 431863

Summary: Yast2 sw_single needs to catogorize updates by date and not version
Product: [openSUSE] openSUSE 11.1 Reporter: Dave Plater <davejplater>
Component: YaST2Assignee: Thomas Göttlicher <tgoettlicher>
Status: RESOLVED INVALID QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P4 - Low    
Version: Factory   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Dave Plater 2008-10-03 09:15:50 UTC 
This could be a feature request or a bug. In latest factory quite a few packages have version tags which have a different format to previous packages, as a result sw_single qt lists them in red but in fact they are newer versions to previously installed versions but they will not be selected by "all in this list > update if newer version available"
I can see this as a bug if an update from 11.0 to 11.1 is attempted.
See bugs https://bugzilla.novell.com/show_bug.cgi?id=417308
and      https://bugzilla.novell.com/show_bug.cgi?id=430164
Which IMO are related.
Comment 1 Thomas Göttlicher 2008-10-14 11:31:24 UTC 
Which date are you talking about that could be used for figuring out which package is the latest? The build date can't be use because one could build an old package after a new package. The changelog is only available for installed packages.

In my opinion the version tag is the only value that is usable for the decision whether a package is newer or older. If the version tag is wrong formated it's a bug from the package maintainer.
Comment 2 Dave Plater 2008-10-15 11:57:19 UTC 
Sorry for the late reply, internet was down. I was referring to the build date as that was my only way of telling which packages were older but you are 100% right the build service should not change their version tag formats which they have.
For example I have yast2-pam-2.16.2-1.118 installed, build time Wed 01 Oct 2008 05:45:08 AM SAST which is the same as current factory, the previous version from the temporary factory which no longer exists is :-
yast2-pam-2.16.2-1.120 build time Sat 20 Sep 2008 05:42:35 AM SAST but it is shown in yast as a newer version. If this problem will no longer occur then version tags are the best method. This is why I came to the conclusion that build time would be a more reliable method.