From owner-freebsd-questions@FreeBSD.ORG Sat Mar 18 16:58:23 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 C8C7716A400 for ; Sat, 18 Mar 2006 16:58:23 +0000 (UTC) (envelope-from donaldjoneill@gmail.com) Received: from smtp101.sbc.mail.mud.yahoo.com (smtp101.sbc.mail.mud.yahoo.com [68.142.198.200]) by mx1.FreeBSD.org (Postfix) with SMTP id 6ADCB43D45 for ; Sat, 18 Mar 2006 16:58:23 +0000 (GMT) (envelope-from donaldjoneill@gmail.com) Received: (qmail 85628 invoked from network); 18 Mar 2006 16:58:22 -0000 Received: from unknown (HELO ?192.168.1.197?) (donaldj@ameritech.net@69.211.212.230 with plain) by smtp101.sbc.mail.mud.yahoo.com with SMTP; 18 Mar 2006 16:58:22 -0000 From: "Donald J. O'Neill" To: freebsd-questions@freebsd.org Date: Sat, 18 Mar 2006 10:58:19 -0600 User-Agent: KMail/1.9.1 References: <7b3c7f0b0603180606g54ffe6e6k3152b6f00555cab0@mail.gmail.com> In-Reply-To: <7b3c7f0b0603180606g54ffe6e6k3152b6f00555cab0@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603181058.19413.donaldjoneill@gmail.com> Cc: Jez Hancock Subject: Re: 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 16:58:23 -0000 On Saturday 18 March 2006 08:06, Jez Hancock wrote: > 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 > single 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 > _______________________________________________ Doing a little better job of reading the man page would help. While it tells you how to set up a cronjob, it also tells you this is a bad idea. You ran the cronjob, which succeeded, but failed to update the ports tree because it had nothing to update it with. If you had ever run portsnap manually, I think you would have set-up your cronjob a little differently. Don