From owner-freebsd-ports@FreeBSD.ORG Sat Oct 1 23:15:10 2005 Return-Path: X-Original-To: freebsd-ports@freebsd.org 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 CAC0516A41F for ; Sat, 1 Oct 2005 23:15:10 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6859E43D45 for ; Sat, 1 Oct 2005 23:15:10 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id 854E6CCF77B; Sat, 1 Oct 2005 19:15:07 -0400 (EDT) Received: from frontend2.messagingengine.com ([10.202.2.151]) by frontend1.internal (MEProxy); Sat, 01 Oct 2005 19:15:07 -0400 X-Sasl-enc: Vn/9CVwsYcVMBC8b19rEHAtpsFnik2gTZiYAYZjmG+v5 1128208502 Received: from gumby.localdomain (dsl-80-41-67-133.access.as9105.com [80.41.67.133]) by frontend2.messagingengine.com (Postfix) with ESMTP id 7B8A9570394; Sat, 1 Oct 2005 19:15:02 -0400 (EDT) From: RW To: freebsd-ports@freebsd.org Date: Sun, 2 Oct 2005 00:15:03 +0100 User-Agent: KMail/1.8.2 References: <433855C1.4060803@mkproductions.org> <4761.192.168.1.2.1128018711.squirrel@mail.scadian.net> <433C3E15.6000406@mkproductions.org> In-Reply-To: <433C3E15.6000406@mkproductions.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510020015.04006.list-freebsd-2004@morbius.sent.com> Cc: Mark Kane Subject: Re: Portupgrade Error X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Oct 2005 23:15:10 -0000 On Thursday 29 September 2005 20:18, Mark Kane wrote: > Nothing skipped or failed, and it appears to be done now. I didn't see > anything about "perl-after-upgrade" when portupgrade upgraded Perl a > couple weeks ago, but that seemed to do it. It was in /usr/ports/UPDATING; you should alway look there before updating ports. You might want to take a look at portmanager. It usually takes a lot longer to run, but it's more thorough and forgiving than portupgrade. It generally requires less manual intervention, and fewer visits to mailing lists.