I have systems subscribed to * Red Hat Linux (Severn) 9.0.93 - Beta * Red Hat Linux (Severn) 9.0.93 - Beta Updates On these systems, up2date shows them as being fully updated. The RHN web interface, however, consistently lists the following as being available for all of these systems: gdb-5.3post-1.20021129.37 as an upgrade for gdb-5.3.90-0.20030710.21 The problem, I guess, is that RHN is comparing 5.3post as > 5.3.90, while up2date is making the same comparison and finding 5.3post < 5.3.90 (neither package has an epoch). To avoid sanity issues for end users, the web front-end and the up2date front-end really should use the same comparison algorithm, and both should be consistent with rpm. FWIW, when rpm makes the same comparison, it finds 5.3post < 5.3.90, so that's what both up2date and RHN should do.... [kaboom@skuld kaboom]$ rpm -q gdb gdb-5.3.90-0.20030710.29 [kaboom@skuld kaboom]$ sudo rpm -Fvh gdb-5.3post-1.20021129.37.i386.rpm [kaboom@skuld kaboom]$ rpm -q gdb gdb-5.3.90-0.20030710.29 [kaboom@skuld kaboom]$
BTW, I think it was a fairly recent change in rpm that in version comparison, numbers are always greater than letters (so 90 > post). Presumably the RHN web side just wasn't updated when that was changed....
Reassigning to appropriate component...
This has been fixed, but not deployed to production yet.
Chris, This went live 09/30 - can you confirm?
Hmm, guess me closing this was lost in the Great Bugzilla Crash of '03 ;-) It works for me now, thanks!