Corey,
I think my concern is that if I change that, my check-update may not
find package updates from RedHat... and I want to know about those.
Thanks,
Kevin
-----Original Message-----
From: Corey Kovacs [mailto:[email protected]]
Sent: Thursday, December 09, 2010 7:53 PM
To: Collins, Kevin [BEELINE]
Subject: Re: [rhelv6-list] rebuilt package not showing selected for update
Sorry, that should have read....
I've not done much with rhel6 yet....
Anyway, I just looked again and you haven't signed the package. Either
sign it, or make sure your yum config has gpgcheck=0 and see if that
works...
Also, I must admit I am surprised that your stuff actually updated
with identical names. You really should be changing the release in
some way since you seem to be maintaining your own version anyway. I
usually put an addition tag on, like ...
rpmbuild --define 'dist .el6.beeline' -bb ksh.spec
that way it's easier to identify which rpm's are yours on a system and
not redhat's .... sort of good form.....
-C
On Fri, Dec 10, 2010 at 3:44 AM, Corey Kovacs <[email protected]> wrote:
> I've not done much with rhel6 year but have you signed the package?
>
> Just a thought..
>
> -C
>
>
> On Fri, Dec 10, 2010 at 12:24 AM, Collins, Kevin [BEELINE]
> <[email protected]> wrote:
>> 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:[email protected]]
>> Sent: Thursday, December 09, 2010 3:28 PM
>> To: Collins, Kevin [BEELINE]
>> Cc: [email protected]; 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
>> [email protected]
>> https://www.redhat.com/mailman/listinfo/rhelv6-list
>>
>
_______________________________________________
rhelv6-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv6-list
