From owner-freebsd-mono@FreeBSD.ORG Tue Jul 8 20:25:23 2014 Return-Path: Delivered-To: mono@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 27C08D5E for ; Tue, 8 Jul 2014 20:25:23 +0000 (UTC) Received: from o3.shared.sendgrid.net (o3.shared.sendgrid.net [208.117.48.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CCA102DA3 for ; Tue, 8 Jul 2014 20:25:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; s=smtpapi; bh=rA6ZErsa+0GE3btR6bxvBBQuHVI=; b=FSFyl3BK/l/tWbX1BC a7sgi/STvNbDiUjwdNwIqGyPRQiaM91fBPbJy6w+NEQ44Cnjb211LxG4mhUTk6g8 EGFMIk22QLSIrahOMf8Wa0POg4WHMBpAbtZBiKuIC9/ryKwKFY7qcDVi/6ewZMxo gkEYZHKH1Ds6ixmQ2pJjBRu4c= Received: by mf196.sendgrid.net with SMTP id mf196.4306.53BC53AA1 2014-07-08 20:25:14.125425085 +0000 UTC Received: from mail.tarsnap.com (unknown [10.100.60.97]) by ismtpd-027.iad1.sendgrid.net (SG) with ESMTP id 14717a6ccfd.2193.797b09 for ; Tue, 08 Jul 2014 20:25:13 +0000 (GMT) Received: (qmail 58397 invoked from network); 8 Jul 2014 20:25:11 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 8 Jul 2014 20:25:11 -0000 Received: (qmail 18580 invoked from network); 8 Jul 2014 20:23:25 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 8 Jul 2014 20:23:25 -0000 Message-ID: <53BC533D.3080501@freebsd.org> Date: Tue, 08 Jul 2014 13:23:25 -0700 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Mike Harding , Dmitry Sivachenko , mono@FreeBSD.org Subject: Re: Strange portsnap behavior References: In-Reply-To: X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SG-EID: CHN6NfIFthFTV9beFUYLTNxKlRO4j22K7zgts+wpWsTFuimigDR1mb3/NSvr36Z0rYG0VlgsRWAShtvie3c2JWMXx1N8vPJjMIIsusOG3ddgFjghn/EHXW6f+cuEnm7QAB4Z1BF2cN3TPfUhcTwYcg== X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2014 20:25:23 -0000 Mike: Thanks for bringing this to my attention! It needs a change in the two ports in order to stop confusing portsnap. Dmitry and mono@ people: The long patch names in the devel/hadoop2 and devel/monodevelop ports are causing problems for the portsnap build. In particular, patch-src_addins_VersionControl_MonoDevelop.VersionControl.Subversion_MonoDevelop.VersionControl.Subversion.dll.config (which appears in both ports) and patch-hadoop-common-project-hadoop-common-src-main-native-src-org-apache-hadoop-security-hadoop_user_info.c patch-hadoop-yarn-project-hadoop-yarn-hadoop-yarn-server-hadoop-yarn-server-nodemanager-src-main-native-container-executor-impl-container-executor.c patch-hadoop-yarn-project-hadoop-yarn-hadoop-yarn-server-hadoop-yarn-server-nodemanager-src-main-native-container-executor-test-test-container-executor.c (appearing in devel/hadoop2) are longer than the 100 character limit for the tar format which portsnap uses internally. Portmgr agreed to a "no file names over 100 characters" policy last year when I ran into the same problem with a different port. Can you please rename these patch files? Thanks, Colin Percival On 07/08/14 11:25, Mike Harding wrote: > I have seen this for at least a few days, running portsnap a few times a day > > Nearly every time I do a portsnap, devel/hadoop2 and devel/monodevelop get > updated, even though they have no changes in the svn repo (of course > devel/hadoop2 just had a change since I decided to write the email, but > monodevelop hasn't been updated in 11 days). > > The directory date gets updated, but the files are all older. Here's an example > portsnap... > > root@bsd:/usr/ports # portsnap fetch update > Looking up portsnap.FreeBSD.org mirrors... 7 > mirrors found. > Fetching snapshot tag from isc.portsnap.freebsd.org... done. > Fetching snapshot metadata... done. > Updating from Tue Jul 8 09:30:43 PDT 2014 to Tue Jul 8 10:25:06 PDT 2014. > Fetching 4 metadata patches... done. > Applying metadata patches... done. > Fetching 0 metadata files... done. > Fetching 7 patches. > (7/7) 100.00% done. > done. > Applying patches... > done. > Fetching 0 new ports or files... done. > Removing old files and directories... done. > Extracting new files: > /usr/ports/devel/hadoop2/ > /usr/ports/devel/monodevelop/ > /usr/ports/games/manaplus/ > /usr/ports/graphics/blender/ > /usr/ports/mail/amavis-logwatch/ > /usr/ports/math/kktdirect/ > /usr/ports/net/py-kombu/ > Building new INDEX files... done. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid