From owner-freebsd-ports@FreeBSD.ORG Sun Dec 5 04:01:59 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E985116A4CF for ; Sun, 5 Dec 2004 04:01:56 +0000 (GMT) Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id A51B543D5C for ; Sun, 5 Dec 2004 04:01:56 +0000 (GMT) (envelope-from dsyphers@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) ESMTP id iB541rpN022810 for ; Sat, 4 Dec 2004 20:01:53 -0800 Received: from yggdrasil.seektruth.org (c-67-171-38-33.client.comcast.net [67.171.38.33]) (authenticated bits=0)iB541cUV017021 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Sat, 4 Dec 2004 20:01:46 -0800 From: David Syphers User-Agent: KMail/1.7.1 To: ports@freebsd.org MIME-Version: 1.0 Content-Disposition: inline Date: Sat, 4 Dec 2004 20:01:40 -0800 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200412042001.41036.dsyphers@u.washington.edu> Subject: portupgrade, packages, and same versions X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 04:01:59 -0000 So I did show-and-tell on questions@, and nobody seems to know. Anyone here know why portupgrade has to be run twice when forcing an upgrade via packages? See example error below. It's a very minor thing, but I don't think it's the desired behavior. I'm running portupgrade 20040701_3 on 5.3-STABLE. ---------- Forwarded Message ---------- On Thursday 02 December 2004 05:54 pm, Kris Kennaway wrote: > On Thu, Dec 02, 2004 at 05:33:50PM -0800, David Syphers wrote: > > Or not, actually. It has nothing to do with the -u option. It fails > > whenever it has to fetch the package (which it does successfully). The > > next time it's run, when it has the package already, it succeeds. > > Again, show us, don't tell us. yggdrasil# portupgrade -fuPP nasm-0.98.38_1,1 ---> Checking for the latest package of 'devel/nasm' ---> Fetching the package(s) for 'nasm-0.98.38_1,1' (devel/nasm) ---> Fetching nasm-0.98.38_1,1 /var/tmp/nasm-0.98.38_1,1.tbz 100% of 133 kB 232 kBps ---> Downloaded as nasm-0.98.38_1,1.tbz ---> Identifying the package /var/tmp/nasm-0.98.38_1,1.tbz ---> Saved as /usr/ports/packages/All/nasm-0.98.38_1,1.tbz ---> Found a package of 'devel/nasm': nasm-0.98.38_1,1.tbz (nasm-0.98.38_1,1) ---> Located a package version 0.98.38_1,1 (nasm-0.98.38_1,1.tbz) ** Ignoring the package, which is the same version as is installed (0.98.38_1,1) ** No package available: devel/nasm ** Listing the failed packages (*:skipped / !:failed) ! devel/nasm (nasm-0.98.38_1,1) (package not found) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed yggdrasil# portupgrade -fuPP nasm-0.98.38_1,1 ---> Checking for the latest package of 'devel/nasm' ---> Found a package of 'devel/nasm': nasm-0.98.38_1,1.tbz (nasm-0.98.38_1,1) ---> Reinstalling 'nasm-0.98.38_1,1' (devel/nasm) using a package ---> Backing up the old version ---> Uninstalling the old version ---> Deinstalling 'nasm-0.98.38_1,1' [Updating the pkgdb in /var/db/pkg ... - 185 packages found (-1 +0) (...) done] pkg_info: can't find package 'nasm-0.98.38_1,1.tbz' installed or in a file! ---> Installing the new version via the package ---> Cleaning out obsolete shared libraries [Updating the pkgdb in /var/db/pkg ... - 186 packages found (-0 +1) . done] -David -- "To get out of the Metaphysical Void, you either have to grasp the meaning of the universe or roll doubles twice." -Cecil Adams