Re: function login call blew up

John Berninger <[email protected]>
Newsgroups gmane.network.up2date.current.devel
Message-ID <[email protected]>
Actually, the server API hasn't changed, but we've now discovered that
Current is totally broken on 7.3, as well as the most recent Red Hat
up2date errata package.  Hunter's got a patch for it and is reviewing it
this weekend, so hopefully early next week there will be at least one
new release; he's been extremely busy lately, though, so don't expect it
at 8 am Monday morning.  :)

        For those of you interested in the technical details, the
problem is definitely with the Current server; in early versions, Hunter
exploited a ``feature'' of the up2date client which really wasn't
supposed to be there by gzipping the package list and header
information, and sending the gzipped data to the client when it was
requested, in order to save disk space.  Well, with version 2.7.61 (the
latest 7.[012] errata) and version 2.7.63 (stock 7.3), that feature was
removed, so our server isn't talking to the clients in a way the clients
understand anymore.  This was a relatively simple fix, it just took a
bit to find and isolate it, and of course we've now got to go through
the monkey business of creating and certifying new packages and such...

On Fri, 17 May 2002, Ingo T. Storm wrote:

> > I'm working with Redhat 7.3
> 
> 7.3 blows up here all the time with different errors. I'd say it seems the
> server API has changed.
> 
> Ingo
> 
> _______________________________________________
> Current-server mailing list
> [email protected]
> http://lists.dulug.duke.edu/mailman/listinfo/current-server

-- 
Thank you,
John Berninger

Systems Administrator		[email protected]
Department of Mathematics	Box 8205, Harrelson Hall
NC State University		Raleigh, NC 27695
Phone:  (919)515-6315		Fax:	(919)515-3798

GPG Key ID: A8C1D45C
        Fingerprint: B1BB 90CB 5314 3113 CF22  66AE 822D 42A8 A8C1 D45C
--
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.