From owner-freebsd-ports  Tue Oct 20 01:12:14 1998
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA20603
          for freebsd-ports-outgoing; Tue, 20 Oct 1998 01:12:14 -0700 (PDT)
          (envelope-from owner-freebsd-ports@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA20592
          for <ports@FreeBSD.ORG>; Tue, 20 Oct 1998 01:12:12 -0700 (PDT)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id BAA04588;
	Tue, 20 Oct 1998 01:09:46 -0700 (PDT)
Message-Id: <199810200809.BAA04588@implode.root.com>
To: Adrian Penisoara <ady@warpnet.ro>
cc: Malartre <malartre@aei.ca>, ports@FreeBSD.ORG,
        ftp-bugs@wcarchive.cdrom.com
Subject: Re: Weird tar problem with a port. 
In-reply-to: Your message of "Tue, 20 Oct 1998 09:51:25 +0300."
             <Pine.BSF.3.96.981020094735.21111A-100000@ady.warpnet.ro> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Tue, 20 Oct 1998 01:09:46 -0700
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>> ftp> get perl5.tar
>> local: perl5.tar remote: perl5.tar
>> 200 PORT command successful.
>> 150 Opening BINARY mode data connection for 'perl5.tar'.
>> 226 Transfer complete.
>> 1536 bytes received in 0.50 seconds (3.00 KB/s)
>> ftp> quit
>> 221 Goodbye!
>> ports$ tar -xvf perl5.tar 
>> tar: Blocksize = 3 records
>> perl5/
>> perl5/files/
>> perl5/files/md5
>> tar: Unexpected EOF on archive file
>> ports$
>> 
>> What's appening? I was in the pub/FreeBSD/ports/lang directory and
>> downloaded the perl5 ports.
>
> I've seen this too, it happens with all port subdirectories, it just
>returns a 1536 bytes ile, up to the content of the first file (usually
>xxx/files/md5).
> You should try getting the tree file by file, it seems that automatic
>archiving of directories is broken for the moment on ftp.cdrom.com.

   Yes, it was broken for a few hours due to a missing include file in a
new version of my ftpd that I was experimenting with (incorrect argument
sizes were being passed to a system call). Anyway, the experimental code
was also causing other problems, so I disabled it for the moment until
I get things sorted out. Sorry for the problems.

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project

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