Bug 83485

i had same prob, except with not only cyrus-sasl and krb5-libs, but also with
open-ldap. it wanted the older one of that, too, even though i had a newer one
already installed.

This is going to be difficult to impossible to fix without having
redhat-config-packages tie into RHN.  

>This is going to be difficult to impossible to fix without having
>redhat-config-packages tie into RHN.

Well, if that's what it takes.... 

Automatic updates are essential for the security of the machine, the safety of
the user, and the health of the Internet (ref: SQL_Slammer). And we can't expect
the user to know with certainty what they will want installed from the CD during
the initial setup.

What redhat-config-packages needs is a way to determine

1. if the required package is installed, and if so
2. if the version is the same or newer than the required version.

In this case, the following would have made that determination:

<pre>

#!/usr/bin/perl

$required = 'cyrus-sasl-2.1.7-2';
$installed = 'cyrus-sasl-2.1.10-1';

($pkg_req, $maj_req, $med_req, $min_req, $rev_req) = pkg_parse($required);
($pkg_ins, $maj_ins, $med_ins, $min_ins, $rev_ins) = pkg_parse($installed);

print "Package: ", $pkg_req, "\n\n";
print "   required:    Major = ", $maj_req, "\n",
      "               Medial = ", $med_req, "\n",
      "                Minor = ", $min_req, "\n",
      "             Revision = ", $rev_req, "\n\n";
print "  installed:    Major = ", $maj_ins, "\n",
      "               Medial = ", $med_ins, "\n",
      "                Minor = ", $min_ins, "\n",
      "             Revision = ", $rev_ins, "\n\n";

if ($maj_ins>$maj_req) {
	$ok = 1;
}
elsif ($maj_ins<$maj_req) {
	$ok = 0;
}
else {
	if ($med_ins>$med_req) {
		$ok = 1;
	}
	elsif ($med_ins<$med_req) {
		$ok = 0;
	}
	else {
		if ($min_ins>$min_req) {
			$ok = 1;
		}
		elsif ($min_ins<$min_req) {
			$ok = 0;
		}
		else {
			$ok = ($rev_ins>=$rev_req);
		}
	}
}

if ($ok) {
	print "The installed version is the same or newer than the required version\n";
}
else {
	print "The installed version is older than the required version\n";
}


sub pkg_parse {
	($_) = @_;
	/(.+)-(\d+)\.(\d+)\.(\d+)-(\d+)$/;
	my @parsed = ($1, $2, $3, $4, $5);
	return @parsed;

}

</pre>

*** Bug 84238 has been marked as a duplicate of this bug. ***

Thanks for not responding to bug #78638 where all of this has been documented
earlier. :-(

>Thanks for not responding to bug #78638

I did search for related bugs before posting. Had I found that one, I might 
have reopened it....

*** Bug 87855 has been marked as a duplicate of this bug. ***

*** Bug 89633 has been marked as a duplicate of this bug. ***

Similar issue in RH9:
Trying to install several packages (KDE, VIM, Xemacs, ...) fails:
unlocatable package:
openssh-3.5p1.6

However:
rpm -qa | grep openssh
openssh-3.5p1.6-9

Similar problem in RH9.

I performed a farily vanilla server install of RH9 plus KDE. Then ran Up2Date 
to get all the latest patches.

However, I decided to add some dev packages. I then recieved a packages not 
found warning. (Krb5-libs = 1.2.7-8 and Openssl = 0.9.7a-2 not found) Due to 
Up2Date I am actually running newer versions.

Any Advice?

The work-around is to install the updated development packages with up2date
prior to installing the rest with redhat-config-packages:

  up2date krb5-devel openssl-devel

You may need to do the same for any other package which causes problems in
redhat-config-packages.

*** Bug 103937 has been marked as a duplicate of this bug. ***

*** Bug 105971 has been marked as a duplicate of this bug. ***

*** Bug 89139 has been marked as a duplicate of this bug. ***

It would be _really_ nice if up2date simply understood the package "groups". 
Then up2date could be a better workaround for this.  

Could problem be somehow related to the installed comps.xml not being updated?  

AFAIK, there is no other convenient way to install whole "groups" of packages.
This and the CD mount problem are becoming quite frustrating for people.  I am
receiving ever increasing reports of this problem from many folks.  (Hopefully
this is the best place to report it).

This report is filed against a product which is no longer supported.  It is very
likely that the problem is resolved in the current version of Fedora Core or
scheduled to be resolved with the new system-config-packages scheduled to land
in Fedora Core 5.