Yeah, I thought about that but then if an update comes out from RedHat with the same revision, I would likely not see that one (which I would want to see, so I can rebuild it to get any bug fixes).
Kevin -----Original Message----- From: Justin Clift [mailto:jcl...@redhat.com] Sent: Thursday, December 09, 2010 3:28 PM To: Collins, Kevin [BEELINE] Cc: rhelv6-list@redhat.com; Greg Bailey Subject: Re: [rhelv6-list] rebuilt package not showing selected for update On 10/12/2010, at 10:20 AM, Collins, Kevin [BEELINE] wrote: > But this has always worked before... I assumed that in this case maybe > yum was looking at the build date or something of that nature to > determine which package to install. Just as a general thought, what happens if you increment the package release number in a "sub release" fashion? Something like from this: ksh-20100621-2.el6.x86_64.rpm to this: ksh-20100621-2.1.el6.x86_64.rpm I don't know that would work, but if it does, it *might* fix the problem without blocking newer releases. (though you might not want those anyway) _______________________________________________ rhelv6-list mailing list rhelv6-list@redhat.com https://www.redhat.com/mailman/listinfo/rhelv6-list
