[rhelv6-list] rebuilt package not showing selected for update

[Collins, Kevin [BEELINE]]

Thanks, but if what you are saying is true, why is it not working? My
build IS newer, so it should be being detected as such according to what
you are saying.

I've installed the rpmdevtools package, but how do I use the command in
the case where both packages have the same name but are in 2 repos?

I ran it against the actual RPM files and this is my result:

# /usr/bin/rpmdev-vercmp
/redhat/RedHatServer6/RHEL6.0/x86_64/rebuild/ksh-20100621-2.el6.x86_64.r
pm
/redhat/RedHatServer6/RHEL6.0/x86_64/install/Packages/ksh-20100621-2.el6
.x86_64.rpm 
0:/redhat/RedHatServer6/RHEL6.0/x86_64/rebuild/ksh-20100621-2.el6.x86_64
.rpm is newer

Thanks,

Kevin

-----Original Message-----
From: Akemi Yagi [mailto:amyagi at gmail.com] 
Sent: Friday, December 10, 2010 9:29 AM
To: Collins, Kevin [BEELINE]
Cc: rhelv6-list at redhat.com
Subject: Re: [rhelv6-list] rebuilt package not showing selected for
update

On Fri, Dec 10, 2010 at 9:00 AM, Collins, Kevin [BEELINE]
<KCollins at chevron.com> wrote:

> I may just have to change my strategy. Your sub-point release idea is
> probably the next best answer.

> If anyone else knows more about how the packages are selected or
identified
> for update, I would appreciate it.

yum/rpm will find the latest version and install it. You can tell
which version is newer by running the rpmdev-vercmp script. It is part
of the rpmdevtools package (available from EPEL for el5, should work
under el6).

For example:

$ rpmdev-vercmp xyzzy-2.1-1.el5 xyzzy-2.1-1.el5.custom
0:xyzzy-2.1-1.el5.custom is newer

Your .custom version is newer than the distro one.

$ rpmdev-vercmp xyzzy-2.1-2.el5 xyzzy-2.1-1.el5.custom
0:xyzzy-2.1-2.el5 is newer

The distro has been updated, now it is newer.

Akemi