From owner-freebsd-questions@FreeBSD.ORG Wed Aug 29 19:04:18 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 041361065673 for ; Wed, 29 Aug 2012 19:04:18 +0000 (UTC) (envelope-from jacks@sage-american.com) Received: from mail.sagedata.net (mail.sagedata.net [38.106.15.121]) by mx1.freebsd.org (Postfix) with ESMTP id 93A728FC19 for ; Wed, 29 Aug 2012 19:04:17 +0000 (UTC) Received: from [192.168.1.67] (99-111-143-21.lightspeed.crchtx.sbcglobal.net [99.111.143.21]) by mail.sagedata.net (8.14.5/8.14.5) with ESMTP id q7TJ4Guj019802 for ; Wed, 29 Aug 2012 14:04:16 -0500 (CDT) (envelope-from jacks@sage-american.com) X-Authentication-Warning: mail.sagedata.net: Host 99-111-143-21.lightspeed.crchtx.sbcglobal.net [99.111.143.21] claimed to be [192.168.1.67] Message-ID: <503E67B4.3090104@sage-american.com> Date: Wed, 29 Aug 2012 14:04:20 -0500 From: Jack Stone User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <503BF131.4030803@sage-american.com> <44ehmp3k1a.fsf@be-well.ilk.org> <503E3071.7000905@sage-american.com> <44vcg11rdq.fsf@be-well.ilk.org> In-Reply-To: <44vcg11rdq.fsf@be-well.ilk.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: milter-spamc/1.15.388 (mail.sagedata.net [38.106.15.121]); Wed, 29 Aug 2012 14:04:17 -0500 X-Spam-Status: NO, hits=-10.00 required=4.50 X-Spam-Report: Content analysis details: (-10.0 points, 4.5 required) | | pts rule name description | ---- ---------------------- -------------------------------------------------- | -0.0 SHORTCIRCUIT Not all rules were run, due to a shortcircuited rule | -10 ALL_TRUSTED Passed through trusted hosts only via SMTP | Subject: Re: Upgrading perl 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: Wed, 29 Aug 2012 19:04:18 -0000 On 8/29/2012 1:32 PM, Lowell Gilbert wrote: > Jack Stone writes: > >> Actually, on other servers with the same upgrading needs, perl-5.12 >> installed without any issue. My intention is to upgrade perl in >> increments to get well past EOL. > You're somewhat on your own, then; I can't test any of my ideas before > suggesting them to you. > >> Wonder if I just deinstalled the old perl5-5.10 and then installed the >> perl5-12 would work. I can do that right from the port: make perl5-12 >> first to see if that works, then: >> # make deinstall (perl-5.10) then: make install clean > I would be surprised if the perl-5.12 port will build for you; I think > you'll get the same error. If not, then yes, it should work. > >> What do you think? I've got to move up because an important perl >> program requires a minimum 5.12. > Well, it's also possible that there's a local problem on that > machine. You indicated that you used portupgrade for similar updates on > similarly-aged machines, but I'll guess that they were only roughly > similar. I'll guess that you built your own INDEX file; if not, you > probably should (and the associated database for portupgrade). Compare > the infrastructure in ports/Mk (and maybe /usr/share/mk) with the > similar machines that succeeded, and look at the Makefile in perl5.12 to > make sure it sets options properly. > > Good luck. > > Hi Lowell and thanks for the good wishes! Yes, on the other servers which upgraded without issue are running the same freebsd-7.x, and the make files are identical for the perl-5.12. I just now ran a test on a test server of same vintage and it did build directly in the port just using "make" to see if it would work. It did. The trick is to DISABLE_CONFLICTS=YES in the /etc/make.conf. This still doesn't mean the important production server will cooperatebut will have to take a risk and try it. That server has a bootable clone that is run every day so I can rescue the server. I will just to make a fresh clone right before I try the perl upgradeso to minimize any loss of data. -- All the best, Jack