Re: RedHat 8.0 :-)

Current is not now and has never been advertised to be 8.0 compatible.
7.2/7.3 for the server, any version/arch of hte client that can run 
up2date 2.7 should work (which is 6.2 on up I believe)


As I said in my posting to the list _yesterday_, my top priority is
getting 8.0 clients working (first) and then making sure current ports
to 8.0 itself (second).

I don't expect either to take too long, but you're going to have to give
me more than 24 hours to accomplish anything. I haven't even gotten the
ISO's downloaded yet.



On Tue, 2002-10-01 at 12:11, Matt Gunter wrote:
> I an running into a different problem.  I'm running current 1.4.1 on a
> RH 7.3 machine trying to serve up RH 8.0 to my client machines.  
> 
> First it was complaining about /usr/share/current/auth.py line 169
> having the 'X-RHN-Client-Version'.  I take that out and it is still
> complaining about /XMLRPC/$RHN/redhat-i386-8.0/getObsoletes/XXX (where
> XXX is the current time).  There is no getObsoletes directory in the
> {current_base}/www/redhat-i386-8.0/ directory.  
> 
> Is this something new that RH has added?  Does it mean current won't
> work for RH 8.0 boxes?  My 7.3 and 7.2 clients are working just fine off
> this same server so I doubt it is a configuration issue.  Any clues?
> 
> Matt Gunter
> Cypress Tech Group
> 
> >Hi,
> >Does anyone had success with RH8.0 and current? 
> >I think that python is not happy with rpm-4.1
> >Errors are below.
> >Any idea?
> >-jec
> 
> 
> _______________________________________________
> Current-server mailing list
> [email protected]
> http://lists.dulug.duke.edu/mailman/listinfo/current-server
> 
> 
-- 
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.