You can now get up2date working again by downloading https://rhn.redhat.com/help/RHNS-CA-CERT and copying it to /usr/share/rhn/RHNS-CA-CERT I don't think the rawhide up2date has the right certificate yet, so keep a copy of the RHNS-CA-CERT file in case it gets overwritten by an up2date update.
Michael Young
On Fri, Aug 29, 2003 at 12:56:16PM +0100, M A Young wrote:
You can now get up2date working again by downloading https://rhn.redhat.com/help/RHNS-CA-CERT and copying it to /usr/share/rhn/RHNS-CA-CERT I don't think the rawhide up2date has the right certificate yet, so keep a copy of the RHNS-CA-CERT file in case it gets overwritten by an up2date update.
Updated version of up2date fixing the CERTs problem are now available for the released versions of Red Hat Linux and Red Hat Enterprise Linux. Please see https://rhn.redhat.com/ for instructions and download informations,
Daniel
Updated version of up2date fixing the CERTs problem are now available for the released versions of Red Hat Linux and Red Hat Enterprise Linux. Please see https://rhn.redhat.com/ for instructions and download informations,
Which doesn't help for the beta, where it has also broken updating from third party repositories
On Fri, Aug 29, 2003 at 08:17:27AM -0400, Alan Cox wrote:
Updated version of up2date fixing the CERTs problem are now available for the released versions of Red Hat Linux and Red Hat Enterprise Linux. Please see https://rhn.redhat.com/ for instructions and download informations,
Which doesn't help for the beta, where it has also broken updating from third party repositories
Right, that doesn't cover the beta sorry.
Daniel
P.S. In case people still need to upgrade non-beta setups, I enclose a script which might help automating this process but didn't got complete coverage for all cases, it worked okay for a few machines but only covers Red Hat Linux not Red Hat Enterprise linux.
On Friday 29 Aug 2003 1:03 pm, Daniel Veillard wrote:
On Fri, Aug 29, 2003 at 12:56:16PM +0100, M A Young wrote:
You can now get up2date working again by downloading https://rhn.redhat.com/help/RHNS-CA-CERT and copying it to /usr/share/rhn/RHNS-CA-CERT I don't think the rawhide up2date has the right certificate yet, so keep a copy of the RHNS-CA-CERT file in case it gets overwritten by an up2date update.
Updated version of up2date fixing the CERTs problem are now available for the released versions of Red Hat Linux and Red Hat Enterprise Linux. Please see https://rhn.redhat.com/ for instructions and download informations,
Daniel
The instruction are missing --nodeps which was required on my system.
Dave.
Updated version of up2date fixing the CERTs problem are now available for the released versions of Red Hat Linux and Red Hat Enterprise Linux. Please see https://rhn.redhat.com/ for instructions and download informations,
The instruction are missing --nodeps which was required on my system.
That shouldnt be needed. What dependancies ?
On Friday 29 Aug 2003 2:20 pm, Alan Cox wrote:
Updated version of up2date fixing the CERTs problem are now available for the released versions of Red Hat Linux and Red Hat Enterprise Linux. Please see https://rhn.redhat.com/ for instructions and download informations,
The instruction are missing --nodeps which was required on my system.
That shouldnt be needed. What dependancies ?
-- Rhl-beta-list mailing list Rhl-beta-list@redhat.com http://www.redhat.com/mailman/listinfo/rhl-beta-list
on my system
up2date = 3.1.23.1 is needed by (installed) up2date-gnome-3.1.23.1-5
Dave.
On Fri, Aug 29, 2003 at 03:16:31PM +0100, David Holden wrote:
on my system
up2date = 3.1.23.1 is needed by (installed) up2date-gnome-3.1.23.1-5
New versions of up2date-gnome have been released at the same time and can be found at the same place. Upgrade both package in a single transaction, i.e. by giving both filenames as arguments to rpm -U
Daniel
On Friday 29 Aug 2003 3:39 pm, Daniel Veillard wrote:
On Fri, Aug 29, 2003 at 03:16:31PM +0100, David Holden wrote:
on my system
up2date = 3.1.23.1 is needed by (installed) up2date-gnome-3.1.23.1-5
New versions of up2date-gnome have been released at the same time and can be found at the same place. Upgrade both package in a single transaction, i.e. by giving both filenames as arguments to rpm -U
Daniel
Yes, this is not a problem for me I know about rpm, but for a newbie the RHN alert I got just refers to
"New versions of the up2date and rhn_register clients are now available which are required for continued access to Red Hat Network."
a newbie going to the referenced site is likely to just download the up2date rpm, as other than offering it for a download does not mention it, this has already been a issue on the redhat list.
Dave.
On Fri, 2003-08-29 at 09:39, Daniel Veillard wrote:
On Fri, Aug 29, 2003 at 03:16:31PM +0100, David Holden wrote:
on my system
up2date = 3.1.23.1 is needed by (installed) up2date-gnome-3.1.23.1-5
New versions of up2date-gnome have been released at the same time and can be found at the same place. Upgrade both package in a single transaction, i.e. by giving both filenames as arguments to rpm -U
Daniel
The problem is that, using up2date, I'm prompted to upgrade my up2date, but still get the message "up2date-gnome-3.1.46-2 requires up2date = 3.1.46". However, both up2date and up2date-gnome are at 3.9.18-2. I can fix it manually, obviously, but this looks like a problem (dunno if it's Bugzilla-worthy).
On Fri, Aug 29, 2003 at 04:28:06PM -0500, Kyle Maxwell wrote:
On Fri, 2003-08-29 at 09:39, Daniel Veillard wrote:
On Fri, Aug 29, 2003 at 03:16:31PM +0100, David Holden wrote:
on my system
up2date = 3.1.23.1 is needed by (installed) up2date-gnome-3.1.23.1-5
New versions of up2date-gnome have been released at the same time and can be found at the same place. Upgrade both package in a single transaction, i.e. by giving both filenames as arguments to rpm -U
Daniel
The problem is that, using up2date, I'm prompted to upgrade my up2date, but still get the message "up2date-gnome-3.1.46-2 requires up2date = 3.1.46". However, both up2date and up2date-gnome are at 3.9.18-2. I can fix it manually, obviously, but this looks like a problem (dunno if it's Bugzilla-worthy).
Hum, sounds you have a newer (beta) version installed.
rpm -U --oldpackage up2date-3.1.46-2.i386.rpm up2date-gnome-3.1.46-2.i386.rpm
this is going backward in the release numbering, and as Alan pointed out you will loose the new features of Adrian's latest releases, but at least connecting to RHN servers should be possbile again. The other solution is to update only the CERT as someone posted before, but I didn't tested that myself.
Daniel
On Fri, 2003-08-29 at 19:36, Daniel Veillard wrote:
Hum, sounds you have a newer (beta) version installed.
rpm -U --oldpackage up2date-3.1.46-2.i386.rpm up2date-gnome-3.1.46-2.i386.rpm
this is going backward in the release numbering, and as Alan pointed out you will loose the new features of Adrian's latest releases, but at least connecting to RHN servers should be possbile again. The other solution is to update only the CERT as someone posted before, but I didn't tested that myself.
I installed the CERT by hand and that worked OK. Looks like the problem was purely that when up2date prompted me to update itself and restart, it wasn't including up2date-gnome in that same transaction. Cancelling and re-trying without letting up2date update itself separately worked OK and I was able to install it through the "normal" update process.
Have a great Labor Day weekend.
Le ven 29/08/2003 à 16:16, David Holden a écrit :
on my system
up2date = 3.1.23.1 is needed by (installed) up2date-gnome-3.1.23.1-5
Update both at the same time : # rpm -U up2date...rpm up2date-gnome...rpm
Dave.
On Fri, Aug 29, 2003 at 09:20:15AM -0400, Alan Cox wrote:
Updated version of up2date fixing the CERTs problem are now available for the released versions of Red Hat Linux and Red Hat Enterprise Linux. Please see https://rhn.redhat.com/ for instructions and download informations,
The instruction are missing --nodeps which was required on my system.
That shouldnt be needed. What dependancies ?
The up2date-gnome package on ftp.redhat.com's up2dates directory fails the --checksig on my system. Then again, my rpm is borked again (surprise, surprise) on my RH8 box (it won't do any deletes during an rpm process nor will rpm -e work at all) so it is likely something to do with that.
-
Alan Cox -
Daniel Veillard -
David Holden -
Féliciano Matias -
Jack Bowling -
Kyle Maxwell -
M A Young