Yes, I know the source URL in the ebuild points to the home page, and not mirror://gentoo, but clods like me (who often manually download source files) check for the gentoo mirrors first (much faster), and this one caught me. Nothing major, but I would never EXPECT to see a bad source file on the gentoo mirrors. I think that someone should either put the correct file there, or at least delete the bad file so that people HAVE to retrieve it from a good source.
That's what you get when upstream messes up with released tarballs (Bug 171924)
*** Bug 172270 has been marked as a duplicate of this bug. ***
Package is not using make.conf "GENTOO_MIRRORS="..." settings. >>> Emerging (1 of 1) sys-apps/file-4.20 to / >>> Downloading 'ftp://ftp.astron.com/pub/file/file-4.20.tar.gz' --11:34:48-- ftp://ftp.astron.com/pub/file/file-4.20.tar.gz => `/usr/portage/distfiles/file-4.20.tar.gz' Resolving ftp.astron.com... 38.117.134.204 Connecting to ftp.astron.com|38.117.134.204|:21...
4.21 stable now... nothing to be done here.
(In reply to comment #4) > 4.21 stable now... nothing to be done here. Not stable on every architechture, but regardless, I don't see the point of keeping a bad tarball on the Gentoo infrastructure. How hard can it be to just delete it (the 4.20 ebuild is still in portage the last time I checked)?