From owner-freebsd-stable@FreeBSD.ORG Tue Jul 28 00:12:40 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF4DF106564A for ; Tue, 28 Jul 2009 00:12:40 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from nskntmtas04p.mx.bigpond.com (nskntmtas04p.mx.bigpond.com [61.9.168.146]) by mx1.freebsd.org (Postfix) with ESMTP id 6C7828FC19 for ; Tue, 28 Jul 2009 00:12:39 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from nskntotgx03p.mx.bigpond.com ([124.188.162.219]) by nskntmtas04p.mx.bigpond.com with ESMTP id <20090728001238.NBV1821.nskntmtas04p.mx.bigpond.com@nskntotgx03p.mx.bigpond.com> for ; Tue, 28 Jul 2009 00:12:38 +0000 Received: from areilly.bpa.nu ([124.188.162.219]) by nskntotgx03p.mx.bigpond.com with ESMTP id <20090728001237.ONTQ21119.nskntotgx03p.mx.bigpond.com@areilly.bpa.nu> for ; Tue, 28 Jul 2009 00:12:37 +0000 Received: (qmail 97964 invoked by uid 501); 28 Jul 2009 00:12:38 -0000 Date: Tue, 28 Jul 2009 10:12:38 +1000 From: Andrew Reilly To: freebsd-stable@freebsd.org Message-ID: <20090728001238.GA97218@duncan.reilly.home> References: <20090726222403.GA19875@duncan.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090726222403.GA19875@duncan.reilly.home> User-Agent: Mutt/1.4.2.3i X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150201.4A6E4276.0018,ss=1,fgs=0 Subject: Re: Weird portmaster behaviour -- everything fails to install X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jul 2009 00:12:41 -0000 Problem solved! In case anyone is interested, or has encountered a similar problem, I believe that my problem was that somehow my /var/db/pkg directory had a whole pile of near-duplicate entries corresponding to port revisions. Portmaster was checking the installed version against the MD5 hashes in the "old" version +CONTENTS file, and they weren't matching. I assume that I acquired all of these out-of-date pkg entries through a backup restore mishap: I've been having gmirror issues lately (not gmirror's fault, I think -- just a series of dodgy hard drives.) All is good again. No duplicate db/pkg entries at last, and portmaster runs to completion as intended. Cheers, -- Andrew On Mon, Jul 27, 2009 at 08:24:03AM +1000, Andrew Reilly wrote: > I've spent the weekend doing a ports catch-up: there seems to > have been a lot of activity recently! It's taking a long time > at least partly because portmaster doesn't seem to be "doing the > right thing" all of a sudden: it will happily trace the > dependencies and build the first superceded port, but fails to > re-install it. On every occsaion this weekend, it gets to > ===> Installing for foo-0.123_2 > ===> Generating temporary packing list > ===> Checking if graphics/foo already installed > ===> foo-0.123_2 is already installed > You may wish to "make deinstall" and blah, blah, blah... > > Of course it's installed, that's why I'm running portmaster! > > So I go into the directory, run make deinstall reinstall clean, > and that goes without a hitch. Restart portmaster -uBd -a and > half an hour later it will fail in the same way, and I'll have > to do the same dance. > > It's most likely something dumb that I've got misconfigured: can > anyone suggest to me where I should look?