From owner-freebsd-stable  Sat Jul 29 18:18:25 2000
Delivered-To: freebsd-stable@freebsd.org
Received: from ducky.nz.freebsd.org (chilled.unixathome.org [203.79.82.27])
	by hub.freebsd.org (Postfix) with ESMTP
	id E1EA837B598; Sat, 29 Jul 2000 18:18:05 -0700 (PDT)
	(envelope-from dan@langille.org)
Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99])
	by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id NAA69773;
	Sun, 30 Jul 2000 13:17:49 +1200 (NZST)
From: "Dan Langille" <dan@langille.org>
Organization: langille.org
To: andrew@ugh.net.au
Date: Sun, 30 Jul 2000 13:17:41 +1200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: is fetch broken?
Reply-To: dan@langille.org
Cc: freebsd-stable@FreeBSD.org, des@FreeBSD.org
Message-ID: <39842AF5.9469.30DB554C@localhost>
References: <20000729174208.F59315@strontium.scientia.demon.co.uk>
In-reply-to: <Pine.BSF.4.21.0007301106350.42780-100000@starbug.ugh.net.au>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On 30 Jul 2000, at 11:10, andrew@ugh.net.au wrote:

> Are you using an HTTP proxy? 

Yes, a transparent one imposed by my ISP.

> Have you tried the -b and/or -t options?

I was using -b, but that is deprecated.  So I stopped using it.  I see the 
same symptoms for both options.  And -t is deprecated as well.

>  I get
> similar errors (and always have) if I don't use -b.

I never had a error such as:

fetch: DESCR?rev=1.2 appears to be truncated: 258/4294967295 bytes

But when not using -b, I sometimes received a message saying try -b or 
-t.

Is it more than a coincidence that the last commit was proxy related?

"MFC: Sync with -CURRENT (most notably, fix resume and proxy 
problems)"

--
Dan Langille  [I'm looking for more work]
The FreeBSD Diary - http://www.freebsddiary.org/
FreshPorts - http://freshports.org/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message