Date: Wed, 21 Sep 2016 08:19:52 -0500 From: John Marino <freebsd.contact@marino.st> To: Mathieu Arnold <mat@FreeBSD.org>, John Marino <marino@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r422505 - head/archivers/snappy-java Message-ID: <3bbaf8af-e9d0-9fce-b103-2055bdce8e18@marino.st> In-Reply-To: <ec547bd4-0930-f39c-7a36-6462c7ad4517@FreeBSD.org> References: <201609201519.u8KFJrTF059560@repo.freebsd.org> <ec547bd4-0930-f39c-7a36-6462c7ad4517@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/21/2016 03:19, Mathieu Arnold wrote: > Le 20/09/2016 à 17:19, John Marino a écrit : >> Author: marino >> Date: Tue Sep 20 15:19:52 2016 >> New Revision: 422505 >> URL: https://svnweb.freebsd.org/changeset/ports/422505 >> >> Log: >> archivers/snappy-java: new fedora MASTER_SITE to unbreak > > I'm picking a commit at random. > > If our distcache is not a valid upstream, then someone else's distcache > is not either. It doesn't look like a cache to me. It looks like that, unlike FreeBSD, they keep a copy of distribution tarballs that they use. It's not a cache, but a primary repository. That's what it looks like to me. If you know that it's definitively just a cache, that might change the story. As as aside, as Chris Rees alluded, some of these breakages that had no warnings had big consequences. Really, too big to just break outright. The situation I transitioned them to are better than what they were. They are intended to be temporary in any case. John --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3bbaf8af-e9d0-9fce-b103-2055bdce8e18>