From owner-freebsd-ports@FreeBSD.ORG Sat Dec 22 20:13:19 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A1D616A417; Sat, 22 Dec 2007 20:13:19 +0000 (UTC) (envelope-from me@janh.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mx1.freebsd.org (Postfix) with ESMTP id 053E013C442; Sat, 22 Dec 2007 20:13:18 +0000 (UTC) (envelope-from me@janh.de) Received: from janh.freebsd (d187027.adsl.hansenet.de [80.171.187.27]) by mrelayeu.kundenserver.de (node=mrelayeu8) with ESMTP (Nemesis) id 0ML31I-1J6AiQ18IA-0003GU; Sat, 22 Dec 2007 21:12:59 +0100 Message-ID: <476D6FCD.1060500@janh.de> Date: Sat, 22 Dec 2007 21:13:01 +0100 From: Jan Henrik Sylvester User-Agent: Thunderbird 2.0.0.9 (X11/20071208) MIME-Version: 1.0 To: Norikatsu Shigemura References: <47630A20.60807@janh.de> <47631447.9090009@u.washington.edu> <1197676276.1838.23.camel@ikaros.oook.cz> <47632096.8080008@math.missouri.edu> <20071215120618.1bf43910.nork@FreeBSD.org> In-Reply-To: <20071215120618.1bf43910.nork@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1/0seBs4HbUqpOdOke/ZjdU2ZspjBmUF0wTCy/ 8XQUjPuVJAHLFtCms6g65mHDDFMrgfEukaUPqiYLHNeYKNREZF XNbTcsHSv3a97U5gn1Anw== Cc: Garrett Cooper , Stephen Montgomery-Smith , pav@freebsd.org, ports-list freebsd Subject: Re: misc/compat5x package installs with weird messages 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: Sat, 22 Dec 2007 20:13:19 -0000 Norikatsu Shigemura wrote: > On Fri, 14 Dec 2007 18:32:22 -0600 > Stephen Montgomery-Smith wrote: >>> My bets are on noschg flag. >> Pav, you are exactly right. I have experienced this many times myself. >> After installing the compat5x package you need to do "chflags -R >> noschg /var/tmp/inst* && rm -rf /var/tmp/inst*" or something like that. >> I think it is a bug in pkg_install, that it doesn't check for the schg >> flag being set in its temporary file area. Or maybe it should set the >> flags in the first place. > > I knew this issue. So I fixed it with rev#1.16 on make clean. > But my work was not enough:-(. How about following patch? I did a portupgrade to the new version. It ended with: ===> Cleaning for compat5x-i386-5.4.0.8_9 ---> Cleaning out obsolete shared libraries [Updating the pkgdb in /var/db/pkg ... - 787 packages found (-0 +1) . done] Operation not permitted - /usr/local/lib/compat/pkg/libc.so.5 Operation not permitted - /usr/local/lib/compat/pkg/libc_r.so.5 Operation not permitted - /usr/local/lib/compat/pkg/libcrypt.so.2 Operation not permitted - /usr/local/lib/compat/pkg/libpthread.so.1 Operation not permitted - /usr/local/lib/compat/pkg/libthr.so.1 I do not know what was not permitted. portupgrade did backup the shared libs with their schg flag. Whatever should have happened then... I guess since nothing has changed with the libs, I can safely removed everything from /usr/local/lib/compat/pkg/ that came from this update (pam_*.so.2, snmp_*.so.2, and the files mentioned in the error message). Is that correct? BTW: Creating a compat5x-i386-5.4.0.8_9 package with pkg_create, removing it, and readding it all went without error messages. Thanks, Jan Henrik