From owner-freebsd-questions@FreeBSD.ORG Sat Mar 18 14:06:34 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BDC716A426 for ; Sat, 18 Mar 2006 14:06:34 +0000 (UTC) (envelope-from jez.hancock@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7770043D48 for ; Sat, 18 Mar 2006 14:06:33 +0000 (GMT) (envelope-from jez.hancock@gmail.com) Received: by nproxy.gmail.com with SMTP id i2so558105nfe for ; Sat, 18 Mar 2006 06:06:32 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=m7Eou6F+ZuSAOY7XGeaLORtldp95dnnkCF+NcelIz18NO7Hp6+wyca+M4DHB355BG0HgNBBiLr8+gQrrEXRIUx1+k/8RnYXldXb2XIZOomgXtZSdDTVNq1zumsUnyADQ4XYKXgMc5sSXoufnfjkPU8aFBPcerVui1QU2AW9My50= Received: by 10.49.37.19 with SMTP id p19mr1840038nfj; Sat, 18 Mar 2006 06:06:32 -0800 (PST) Received: by 10.48.231.7 with HTTP; Sat, 18 Mar 2006 06:06:32 -0800 (PST) Message-ID: <7b3c7f0b0603180606g54ffe6e6k3152b6f00555cab0@mail.gmail.com> Date: Sat, 18 Mar 2006 14:06:32 +0000 From: "Jez Hancock" To: "FreeBSD Questions Mailing List" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Portupgrade fails to upgrade after using portsnap X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Mar 2006 14:06:34 -0000 Hi all, For a long time I've been using cvsup and portupgrade to update the ports tree once a week; this has worked well for years now. Recently though I changed to using portsnap to update the ports tree, still using portupgrade once a week to update the ports. I followed the method outlined in the handbook more or less for upgrading using portsnap, essentially running a cronjob: portsnap cron && portsnap update && portupgrade -arRF && pkg_version -v -I -l "<" to grab and extract the latest port snapshot, fetch any newer port distfiles/tarballs and then report by mail what ports are out of date. This worked well for a few weeks up until Feb 25th - since then not a singl= e out of date port has been reported and 'portupgrade -arR' fails to upgrade anything. I thought this might have been to do with the recent ports freeze= , though checking now I see that only went on from the start of March... I've changed back to use cvsup and the old method - basically 'cvsup -g -L2 supfile && cd /usr/ports && make fetchindex && portsdb -u' - but still no joy. I was convinced it was the ports db files that were out of synch and thought this might do the trick to fix the problem, but unfortunately no - if I view the resulting INDEX file from this procedure I can see there are ports out of date as well, it's just 'portupgrade -arR' etc refuses to find any updates. Questions then: What could the problem be? For future reference what is the best way to purge the ports system of out of date db files and regenerate them all so 'portupgrade -arRi' will work? Cheers. -- Jez Hancock