https://bugzilla.novell.com/show_bug.cgi?id=431863 Thomas Göttlicher changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Priority|P5 - None |P4 - Low -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=431863 User dave.plater@yahoo.co.uk added comment https://bugzilla.novell.com/show_bug.cgi?id=431863#c2 --- Comment #2 from Dave Plater 2008-10-15 05:57:19 MDT --- 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. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.