So, are you saying that this tool is only comparing the strings and not looking at any packages? After a bit of playing, that would seem to be the case... which at least lets me test for what I think is a "smart" way to name my rebuild packages.
Thanks, Kevin -----Original Message----- From: Akemi Yagi [mailto:amy...@gmail.com] Sent: Friday, December 10, 2010 11:26 AM To: Collins, Kevin [BEELINE] Cc: rhelv6-list@redhat.com Subject: Re: [rhelv6-list] rebuilt package not showing selected for update On Fri, Dec 10, 2010 at 11:01 AM, Collins, Kevin [BEELINE] <kcoll...@chevron.com> wrote: > Ok, but then why is the rpmdev-vercmp saying that my rebuilt package is > newer? Yet it is still not being treated as newer by yum... > > I did the rebuild again, this time changing the "el6" to "el6.custom" > and now check-update sees the rebuilt package as newer and available for > update. > > My concern is that when Redhat releases "el6_1", my version might still > be considered newer. Any idea how the "release" is compared? > > Thanks, > > Kevin I don't know how else I can explain but will do my best. $ rpmdev-vercmp 2.1-1.el6 2.1-1.el6.custom 0:2.1-1.el6.custom is newer $ rpmdev-vercmp 2.1-1.el6_1 2.1-1.el6.custom 0:2.1-1.el6_1 is newer Akemi _______________________________________________ rhelv6-list mailing list rhelv6-list@redhat.com https://www.redhat.com/mailman/listinfo/rhelv6-list
