Date: Tue, 08 Jul 2014 13:23:25 -0700 From: Colin Percival <cperciva@freebsd.org> To: Mike Harding <mvharding@gmail.com>, Dmitry Sivachenko <demon@FreeBSD.org>, mono@FreeBSD.org Subject: Re: Strange portsnap behavior Message-ID: <53BC533D.3080501@freebsd.org> In-Reply-To: <CALRn2n_Rm_RqgHJ2ERSmm-e%2BqpvMfZiK6jeRds==B2WLii0vhQ@mail.gmail.com> References: <CALRn2n_Rm_RqgHJ2ERSmm-e%2BqpvMfZiK6jeRds==B2WLii0vhQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <http://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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53BC533D.3080501>