From owner-freebsd-ports@FreeBSD.ORG Sun Apr 8 19:18:49 2007 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 697C416A402; Sun, 8 Apr 2007 19:18:49 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 4406213C465; Sun, 8 Apr 2007 19:18:48 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.222] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id l38JImH7078281; Sun, 8 Apr 2007 12:18:48 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <46194018.8030102@freebsd.org> Date: Sun, 08 Apr 2007 12:18:48 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ulrich Spoerlein References: <20070407174756.GA46385@roadrunner.q.local> <4617F67B.7050304@freebsd.org> <20070408075917.GA40103@roadrunner.q.local> In-Reply-To: <20070408075917.GA40103@roadrunner.q.local> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org Subject: Re: Cannot package converters/libiconv inside clean chroot X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Apr 2007 19:18:49 -0000 > There are at least two issues here, one is pkg_add refusing a valid > (AFAICS) tbz file, the other is bsdtar(1) choosing a different tar > format based on unionfs(!). Those two symlink entries have an "opaque" file flag. This explains the format change (bsdtar uses the extended pax format when it sees a file with flags set, since ustar can't store those). I would guess that pkg_add is invoking bsdtar with -p (restore permissions), bsdtar is restoring the 'opaque' flag, and then pkg_add is tripping over those symlinks for some reason when it tries to move them. To test this hypothesis, try stripping those flags with: tar -cjf new-libiconv-1.9.2_2.tbz --format=ustar @libiconv-1.9.2_2.tbz The "new-libiconv" tarfile should be identical except it won't have the file flags stored. If pkg_add likes new-libiconv but not libiconv, then it must be those opaque flags. I don't know if this is a bug in unionfs, in pkg_add, or in bsdtar. I think we need someone who understands the 'opaque' flag to chime in here. Tim