From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 01:52:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8CB816A4CE for ; Mon, 15 Nov 2004 01:52:49 +0000 (GMT) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AFE643D4C for ; Mon, 15 Nov 2004 01:52:49 +0000 (GMT) (envelope-from kientzle@freebsd.org) Received: from freebsd.org (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id iAF1qg90005103; Sun, 14 Nov 2004 17:52:49 -0800 (PST) (envelope-from kientzle@freebsd.org) Message-ID: <41980BEA.2030405@freebsd.org> Date: Sun, 14 Nov 2004 17:52:42 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sean McNeil References: <1100466137.48774.4.camel@server.mcneil.com> <20041114222745.GB17027@xor.obsecurity.org> <1100471468.45413.0.camel@server.mcneil.com> In-Reply-To: <1100471468.45413.0.camel@server.mcneil.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org cc: Kris Kennaway Subject: Re: bsdtar doesn't work with ports backup of libsigc++20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 01:52:50 -0000 Sean McNeil wrote: > >I was doing a complete rebuild of my system and ran into a problem with >bsdtar: > >portupgrade -f libsigc++-2.0.3 > >---> Backing up the old version >tar: share/doc/libsigc-2.0/docs/reference/html/classsigc_1_1signal_3_01T__return_00_01T__arg1_00_01T__arg2_00_01T__arg3_00_01T__arg4_00_01T__arg5_00_01T__arg6_01_4-members.html: (null) >** Backup failed. I just committed a couple of changes to -CURRENT that seem to address this: Look for rev 1.21 of archive_write_set_format_pax.c (Same problem as Joe Marcus Clarke reported: long filenames and file flags are handled through the same "extended attribute" mechanism, which appears to have been broken since November 4.) Let me know. Tim