[users] CentOS-5 yum update loop - perl-TermReadKey perl-Term-ReadKey

[Dag Wieers]

On Sat, 23 Feb 2008, Phil Schaffner wrote:

> If both dries and rpmforge repos are enabled under CentOS-5, on
> subsequent yum updates perl-TermReadKey (dries) perl-Term-ReadKey
> (rpmforge) want to replace each other.  Haven't tried to debug further.
> Mutual obsoletes?

Obsoletes should always be versioned (both version and release), that 
helps when doing renames because then highest wins.

This of course is not true when a project renames and renumbers their 
releases to a lower version, in that case you require an unversioned 
obsolete.

I guess an older RPM package did not have a versioned obsolete. The RPM 
package ought to be called perl-TermReadKey as that is what the upstream 
perl package says. It is a common misconception that a perl RPM package is 
named after the module it contains. It is not.

A perl RPM package from CPAN is named after its perl package name, which 
is usually the name of the archive (unless that name already contains 
perl which then is stripped from it). The reason for this is that it 
eliminates any doubt or inconsistency. You can get the information from:

 	ftp://ftp.kulnet.kuleuven.ac.be/pub/mirror/CPAN/modules/02packages.details.txt.gz

In this case I noticed that the Obsoletes was missing the release-part in 
the perl-Term-ReadKey package. We should probably remove the old 
perl-Term-ReadKey packages from the repository as I once did with the SPEC 
file.

Thanks for reporting,
-- 
--   dag wieers,  dag at wieers.com,  http://dag.wieers.com/   --
[Any errors in spelling, tact or fact are transmission errors]