From owner-freebsd-stable@freebsd.org Sun Sep 2 00:15:12 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 136CAFD44CB; Sun, 2 Sep 2018 00:15:12 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (phouka1.phouka.net [107.170.196.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "phouka.net", Issuer "Go Daddy Secure Certificate Authority - G2" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 180D781D5A; Sun, 2 Sep 2018 00:15:10 +0000 (UTC) (envelope-from warlock@phouka1.phouka.net) Received: from phouka1.phouka.net (localhost [127.0.0.1]) by phouka1.phouka.net (8.15.2/8.15.2) with ESMTPS id w8209X5w017671 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 1 Sep 2018 17:09:33 -0700 (PDT) (envelope-from warlock@phouka1.phouka.net) Received: (from warlock@localhost) by phouka1.phouka.net (8.15.2/8.15.2/Submit) id w8209WxM017670; Sat, 1 Sep 2018 17:09:32 -0700 (PDT) (envelope-from warlock) Date: Sat, 1 Sep 2018 17:09:32 -0700 From: John Kennedy To: Jonathan Chen Cc: Alex McKeever , FreeBSD Current , FreeBSD Stable Subject: Re: Failing to retrieve source tarballs for anything. Message-ID: <20180902000932.GA47243@phouka1.phouka.net> References: <826294696.2192772.1535822734294.ref@mail.yahoo.com> <826294696.2192772.1535822734294@mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Sep 2018 00:15:12 -0000 On Sun, Sep 02, 2018 at 07:58:16AM +1200, Jonathan Chen wrote: > On 2 September 2018 at 05:25, Alex McKeever wrote: > > After compiling PKG, when I go to ports to compile anything (my eMac can run FreeBSD but not modern Linux due to the version of the Radeon GPU) it fails to retrieve any of the source tarballs for any of the software, desktop environments etc. I would like help to fix this, as I???d like to run something current. > > How old is your ports tree? It it up to date? What sort of problems > are you seeing in fetching the port sources? > > Since no one else has reported any problems, it is most likely > something to do with your local environment. Alex, despite what the documentation says, I wouldn't try to build too much using the regular make methods (or portmaster). There are a number of dependencies that are incompatible that you can skate by if you use packages, synth or poudriere. Unless you're going to heavily customize your options, I'd stick with the simplest, packages, until you have a reason not to. FreeBSD 11.2 is stable... what version are you running? If you're running something really old, packages may no longer be offered and you should try to upgrade, but that is a different problem. 11.1 and 10.4 still have some life. As Jonathan noted, having an up-to-date port tree is also important. If it's too old, you may be trying to grab tarballs that no longer exist. Have you looked at chapter 4 of the FreeBSD handbook? https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports.html One way to update the sources is via the portsnap fetch/extract/update: https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html The "binary packages" method is described here: https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/pkgng-intro.html If you're using packages, and you "pkg upgrade", you'll see something like: root@rpi3:~ # pkg upgrade Updating FreeBSD repository catalogue... FreeBSD repository is up to date. All repositories are up to date. Checking for upgrades (1 candidates): 100% Processing candidates (1 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. My home ISP does something wonky with their DNS and I have some issues with connecting to some resources, but that is trivially solved by changing my DNS server. That typically manifests as unreachable sites or unresolvable hostnames, which might match your symptoms depending on the "fail."