Re: Problem with up2date after upgrade
Hunter Matthews <[email protected]> 31 Oct 2002 10:48:33 -0500
| Newsgroups | gmane.network.up2date.current.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 2002-10-31 at 04:53, Arthur Clune wrote: > --On 30/10/02 15:47:39 -0600 Krell, Mike wrote: > > > We have a beta environment, running current-1.0.6-1 and hosting a > > channel for redhat 7.1. I've upgraded from up2date-2.7.61-7.x.1 to > > up2date-2.8.39-1.7.1 on the servers subscribing to the 7.1 channel, and > > have started getting the following messages: > > This was discussed on the list - you need to move to a version of current > that supports 2.8 up2date clients (the RH8 up2date backported). But 1.0._6_ was supposed to provide that support. I'm not sure why up2date 2.8 would be failing for him. -- Hunter Matthews Unix / Network Administrator Office: BioScience 145/244 Duke Univ. Biology Department Key: F0F88438 / FFB5 34C0 B350 99A4 BB02 9779 A5DB 8B09 F0F8 8438 Never take candy from strangers. Especially on the internet.