From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2)
Gecko/20040803

Description of problem:
If the RHN version of a package is marked as obsoleting a package
that's currently installed, then up2date will always try to install
that package, even a newer, 3rd-party version of the package is
already installed.  (I think this is what's happening - I may be
wrong.  See "Steps to reproduce" for the exact problem that I'm seeing.)

Version-Release number of selected component (if applicable):
up2date-4.2.38-1

How reproducible:
Always

Steps to Reproduce:
1. Build SpamAssassin 2.64 from the SRPM at
http://www.spamassassin.org/.  This creates 3 RPMs:
spamassassin-2.64-1, spamassassin-tools-2.64-1, and
perl-Mail-SpamAssassin-2.64-1.
2. Install these RPMs.  Upgrade or replace Red Hat's version of the
spamassassin RPM (2.55-3.1).
3. Run up2date.


Actual Results:  up2date says that spamassassin-2.55-3.1 obsoletes
perl-Mail-SpamAssassin-2.64-1 and tries to "upgrade" from
spamassassin-2.64-1 to spamassassin-2.55-3.1.

Expected Results:  up2date should recognize that, even if
spamassassin-2.55-3.1 says it obsoletes perl-Mail-SpamAssassin-2.64-1,
a newer version of spamassassin is already installed.  up2date should
therefore not attempt to "upgrade" from spamassassin-2.64-1 to
spamassassin-2.55-3.1.

Additional info: