From owner-freebsd-ports@FreeBSD.ORG Wed May 27 23:17:08 2009 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 87E7E106564A; Wed, 27 May 2009 23:17:08 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id 484958FC19; Wed, 27 May 2009 23:17:08 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mobileKamikaze.norad (unknown [88.130.192.155]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 024928A019F; Thu, 28 May 2009 01:17:06 +0200 (CEST) Message-ID: <4A1DC9EC.2050602@bsdforen.de> Date: Thu, 28 May 2009 01:17:00 +0200 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.21 (X11/20090408) MIME-Version: 1.0 To: pav@FreeBSD.org References: <4A1D6DB8.40209@bsdforen.de> <1243450420.29778.2.camel@hood.oook.cz> <4A1DC5BF.9020106@bsdforen.de> In-Reply-To: <4A1DC5BF.9020106@bsdforen.de> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 8bit Cc: freebsd-ports@FreeBSD.org Subject: Re: pkg_add errors 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: Wed, 27 May 2009 23:17:08 -0000 Dominic Fandrey wrote: > Pav Lucistnik wrote: >> Dominic Fandrey píše v st 27. 05. 2009 v 18:43 +0200: >> >>> During my last run of 'pkg_upgrade -a', cups-client forgot to install >>> the library libcups.so.2, which I fortunately recognized due to my >>> routine of running pkg_libchk after every package/port upgrade. >>> >>> Running 'pkg_upgrade cups-client' fixed that problem. The interesting >>> part is, that the reinstallation of cups-client was done from the >>> same package. So either pkg_add, tar or the file system were to blame, >>> because the package is without fault. >>> >>> I expect that this unreliability of pkg_add (or the underlying systems) >>> has a severe impact on my further development of pkg_upgrade. >> I think it was entirely different story -- >> >> installation of cups-client (put libcups on disc) >> upgrade of cups-base (remove libcups from disc) >> > > Well, that's possible, but why would cups-base perform such an evil > deed? Stupid me, I just read UPDATING. That explains everything. But that puts the question forward how to deal with this. People using pkg_upgrade do not require a ports tree and hence do not have UPDATING. > It's a very soothing suggestion, though. At least as far as pkg_upgrade > is concerned.