• Johannes Pfau (8/8) Jul 22 2017 I just updated the gdc-6 branch in my repo to gcc 6.4.0 and the CI
• Iain Buclaw via D.gnu (3/10) Jul 22 2017 Just switch it to whatever is the current. Downloading the xz would

Johannes Pfau <nospam example.com> writes:

I just updated the gdc-6 branch in my repo to gcc 6.4.0 and the CI
started to fail downloading the tarball. Turns out that the .bz2
tarball was replaced with a .tar.xz tarball for gcc 6.4.0 and I guess
it'll be similar for all new releases:
ftp://ftp.mirrorservice.org/sites/sourceware.org/pub/gcc/releases/gcc-6.4.0/

What's the best workaround for this? Simply trying .xz first and if
that fails trying .bz2? Or switching to .gz tarballs entirely?

-- Johannes

"Iain Buclaw via D.gnu" <d.gnu puremagic.com> writes:

On 22 July 2017 at 12:23, Johannes Pfau via D.gnu <d.gnu puremagic.com> wrote:
 I just updated the gdc-6 branch in my repo to gcc 6.4.0 and the CI
 started to fail downloading the tarball. Turns out that the .bz2
 tarball was replaced with a .tar.xz tarball for gcc 6.4.0 and I guess
 it'll be similar for all new releases:
 ftp://ftp.mirrorservice.org/sites/sourceware.org/pub/gcc/releases/gcc-6.4.0/

 What's the best workaround for this? Simply trying .xz first and if
 that fails trying .bz2? Or switching to .gz tarballs entirely?

Just switch it to whatever is the current.  Downloading the xz would
be better for size.