From owner-freebsd-multimedia@FreeBSD.ORG Fri May 23 01:13:19 2014 Return-Path: Delivered-To: multimedia@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C5887634; Fri, 23 May 2014 01:13:19 +0000 (UTC) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id A93E12EDA; Fri, 23 May 2014 01:13:19 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id EA4023AE46; Thu, 22 May 2014 18:13:13 -0700 (PDT) From: "Ronald F. Guilmette" To: Kevin Oberman Subject: Re: multimedia/ffmpeg: pkg_add: leave_playpen: can't chdir back to '' In-Reply-To: Date: Thu, 22 May 2014 18:13:13 -0700 Message-ID: <13613.1400807593@server1.tristatelogic.com> Cc: FreeBSD Ports ML , multimedia@freebsd.org X-BeenThere: freebsd-multimedia@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Multimedia discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2014 01:13:19 -0000 In message Kevin Oberman wrote: >On Thu, May 22, 2014 at 1:44 PM, Ronald F. Guilmette >wrote: >... >> share/doc/ffmpeg/swscale.txt: Could not unlink >> share/doc/ffmpeg/tablegen.txt: Could not unlink >> share/doc/ffmpeg/viterbi.txt: Could not unlink >> tar: Error exit delayed from previous errors. >> pkg_add: leave_playpen: can't chdir back to '' >> *** [install-package] Error code 2 >> >> Stop in /usr/ports/multimedia/ffmpeg. >> *** [install] Error code 1 >> >> Stop in /usr/ports/multimedia/ffmpeg. >> > >The list of "Could not unlink" messages smell like some sort of permissions >problem. Nevermind. Apparently, there was a _file_... please note... a _file_ (not a directory) on my system with the name /usr/local/share/doc/ffmpeg and this was apparently causing all the problems. I removed it and now the install completes without error. I myseld never intentionally created that file, and I feel that it must have been a left-over of some kind of some prior install of ffmpeg... perhaps from long ago. The file itself was apparently a text file, 7 bytes long, containing only the following text: 0.7.15 I say again that I personally have no recollection of *ever* having intentionally created any such file. I humbly suggest that install scripts should avoid making assumptions about the presence of absence of some particular type of thing within the file system unless the scripts in question have themselves made all necessary arrangements beforehand to create said filesystem objects (and using "rm -f" where necessary, in order to reliably clear the way for any such creations).