From owner-freebsd-questions@FreeBSD.ORG Sat Nov 17 05:56:47 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 406F7371 for ; Sat, 17 Nov 2012 05:56:47 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:2:7]) by mx1.freebsd.org (Postfix) with ESMTP id BC9B28FC0C for ; Sat, 17 Nov 2012 05:56:45 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuMEAIwmp1DLevdH/2dsb2JhbABEv0+EZoIeAQEEAThBBQsLIRMDDwkDAgECAUUTAQcBAYgDBb8bjDOBZoMnA6Y/gwKBSE8 Received: from ppp247-71.static.internode.on.net (HELO leader.local) ([203.122.247.71]) by ipmail07.adl2.internode.on.net with ESMTP; 17 Nov 2012 16:26:44 +1030 Message-ID: <50A7251D.3040100@ShaneWare.Biz> Date: Sat, 17 Nov 2012 16:18:13 +1030 From: Shane Ambler User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121030 Thunderbird/16.0.2 MIME-Version: 1.0 To: freebsd@dreamchaser.org Subject: Re: how to correct corrupted ports tree? References: <50A718F5.8040806@dreamchaser.org> In-Reply-To: <50A718F5.8040806@dreamchaser.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Mailing List X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Nov 2012 05:56:47 -0000 On 17/11/2012 15:26, Gary Aitken wrote: > decided to rebuild ports for peace of mind, > but my basic ports tree is hosed: > I didn't see anything in the handbook about how to get the ports tree itself > back to a sane condition. Do I have to blow the whole thing away and do a > fresh extract? I don't see a way to force refetch of the actual ports files > like "distinfo" when portsnap thinks the port is up to date. portsnap extract will always install the entire tree, if you have made any modifications they will be overwritten, but new ports folders you have added should remain, sometimes this can also cause old folders to be left behind. Worst case is to delete the existing /usr/ports and extract a clean set. Another option is partial extraction - portsnap extract lang/php5-extensions will extract just the one port portsnap extract lang/php5 will match all lang ports starting with php5 portsnap extract lang will extract all the lang ports I think that you will find your issue comes from the fact that all the php4 ports have been deleted - you seem to have some old folders left behind. Could be from extracting over an existing cvs checkout. Maybe you want a clean start. If you still have php4 installed then you should be able to use portmaster -o lang/php5-extensions lang/php4-extensions to get it to update with the new version find /usr/ports -type d -and -name "php4*" | xargs rm -R will delete any remaining php4 folders find /usr/ports -name "CVS" | xargs rm -R will remove all the cvs garbage left behind.