Re: Supported versions

It's really funny... I was pleased with those updates until I tried
registering a -new- server with rhn_register-2.7.9-6.x.1. and
up2date-2.7.46-6.x.1 It ignored my /etc/sysconfig/rhn/rhn_register
settings and effectively connected me to the real RedHat up2date server
where my user account was to be registered.. The only workaround I found
was to downgrade to rhn_register-2.7.2 and up2date-2.7.11-6.x.1 and to
re-register.. This time it effectively connected to my Current server..
Does anyone know if this was a 'fall-back' procedure because I didn't add
my RHNS-CA-CERT to the new /etc/sysconfig/rhn/up2date-keyring.gpg keyring?
Can anyone reproduce this? This was from a sparc64 RH6.2 box..

Vincent

On 19 Mar 2002, Peter Bowen wrote:

> On Tue, 2002-03-19 at 14:52, Hunter Matthews wrote:
> > Red Hat has _just_ announced up2date and rhn_register bug fixes, taking
> > up2date to 2.7.42 or something. I haven't tested those yet, but they
> > should work for people.
>
> These actaully add a couple of very nice options the up2date config
> file.  You can now configure the server certificate and gpg keyring
> files.  This should be a big bonus bonus for current, as you don't have
> to build your own up2date packages and/or manually change the
> RHNS-CA-CERT file.  Additionally, it makes it easy to add your own
> packages that you sign yourself.
>
> Thanks.
> Peter