From owner-freebsd-mono@FreeBSD.ORG Tue Jul 8 20:45:18 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 7B7A735B; Tue, 8 Jul 2014 20:45:18 +0000 (UTC) Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9C5172F58; Tue, 8 Jul 2014 20:45:17 +0000 (UTC) Received: by mail-lb0-f180.google.com with SMTP id w7so4262931lbi.25 for ; Tue, 08 Jul 2014 13:45:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=qPnPGJzN7wZ6hoX6SaZV01QoLbL/3mF0c5gXWXu9jNA=; b=jPG3J/YQzGFsSsF8nEOc7WGW72TOh1vEHLZLPJHggcQ3sEXRm8CIPo8hy4IBMyCHnE PGDvyw9Rg389V3fFWse+zLoYyRnde14Y7ay3yRsJZ1vJDn10jDM5LXESBNd12Fehn9nY dbWruArkJxX1TmnKy94zYZoEE4QflNf9NvFKzoIt+EBLW2DxUDXl8nhapxWEdKSW3HeB 80DNArhxmqOH+jcGHdSAsaxgxjmx3k21sAytkC6LXMirviOTMlJ8QfQobIzjCZvxcbWQ jTsFTrdqByqvHym0k06JUyj3t+GvVUyXbz1qCoq/ykVjAXwLWruomQKZOxqN+PjDUQyz xu2g== X-Received: by 10.112.147.233 with SMTP id tn9mr18380962lbb.17.1404852315515; Tue, 08 Jul 2014 13:45:15 -0700 (PDT) Received: from [10.0.1.2] (ip-95-220-142-209.bb.netbynet.ru. [95.220.142.209]) by mx.google.com with ESMTPSA id h4sm10675015lbj.1.2014.07.08.13.45.14 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 08 Jul 2014 13:45:14 -0700 (PDT) Sender: Dmitry Sivachenko Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) Subject: Re: Strange portsnap behavior From: Dmitry Sivachenko In-Reply-To: <53BC533D.3080501@freebsd.org> Date: Wed, 9 Jul 2014 00:45:12 +0400 Content-Transfer-Encoding: quoted-printable Message-Id: <993EAE59-5995-4160-B27E-9D88C5BE8D12@FreeBSD.org> References: <53BC533D.3080501@freebsd.org> To: Colin Percival X-Mailer: Apple Mail (2.1878.2) Cc: marcus@FreeBSD.org, mono@FreeBSD.org, Mike Harding 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:45:18 -0000 CCing marcus@: Can we please add a check for "no more than 100 characters for patch = file names" to portlint please? Thanks! On 09 =D0=B8=D1=8E=D0=BB=D1=8F 2014 =D0=B3., at 0:23, Colin Percival = wrote: > Mike: Thanks for bringing this to my attention! It needs a change in = the > two ports in order to stop confusing portsnap. >=20 > 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, >=20 > = patch-src_addins_VersionControl_MonoDevelop.VersionControl.Subversion_Mono= Develop.VersionControl.Subversion.dll.config >=20 > (which appears in both ports) and >=20 > = patch-hadoop-common-project-hadoop-common-src-main-native-src-org-apache-h= adoop-security-hadoop_user_info.c > = patch-hadoop-yarn-project-hadoop-yarn-hadoop-yarn-server-hadoop-yarn-serve= r-nodemanager-src-main-native-container-executor-impl-container-executor.c= > = patch-hadoop-yarn-project-hadoop-yarn-hadoop-yarn-server-hadoop-yarn-serve= r-nodemanager-src-main-native-container-executor-test-test-container-execu= tor.c >=20 > (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. >=20 > Can you please rename these patch files? >=20 > Thanks, > Colin Percival >=20 > 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 >>=20 >> 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). >>=20 >> The directory date gets updated, but the files are all older. Here's = an example >> portsnap... >>=20 >> 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. =20 >> 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. >=20 >=20 > --=20 > Colin Percival > Security Officer Emeritus, FreeBSD | The power to serve > Founder, Tarsnap | www.tarsnap.com | Online backups for the truly = paranoid