From owner-freebsd-current@FreeBSD.ORG Mon Oct 13 19:08:06 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6341784F for ; Mon, 13 Oct 2014 19:08:06 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 224D110E for ; Mon, 13 Oct 2014 19:08:05 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id C2BD91FE022; Mon, 13 Oct 2014 21:08:03 +0200 (CEST) Message-ID: <543C2315.7040403@selasky.org> Date: Mon, 13 Oct 2014 21:08:05 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Kurt Jaeger Subject: Re: Problem with perl and SVK References: <543C19AD.8070603@selasky.org> <20141013183706.GO29437@home.opsec.eu> <543C200F.90905@selasky.org> In-Reply-To: <543C200F.90905@selasky.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Oct 2014 19:08:06 -0000 On 10/13/14 20:55, Hans Petter Selasky wrote: > On 10/13/14 20:37, Kurt Jaeger wrote: >> Hi! >> >>> When updating the system to the latest perl and SVK version in ports, I >>> am seeing this: >> [...] >> >> I'm seeing the same on 10.0p9 and perl 5.20. >> >>> Any ideas how to fix? >> >> This seems to bringt svk back in the game: >> >> cd /usr/local/lib/perl5/site_perl/5.20/SVK >> vi Util.pm >> >> replace >> >> use autouse 'List::Util' => qw( max(@) ); >> >> with >> >> use List::Util; >> >> but a short test shows: >> >> $ svk >> Use of uninitialized value $ARGV[0] in ucfirst at >> /usr/local/lib/perl5/site_perl/5.20/App/CLI/Command.pm line 116. >> SVK Documentation - Main index: >> [...] >> >> so the root cause is somewhere deeper. >> > > Hi, > > Using "use List::Util;" instead of autouse fixes the "svk diff" at least > over here. > > --HPS Hi, Seems to work: https://svnweb.freebsd.org/changeset/base/273059 The other perl warning has always been there. Will someone make a patch for the SVK port? --HPS