$ GENTOO_MIRRORS="" ebuild libsearpc-3.0.8-r2.ebuild fetch [..] HTTP request sent, awaiting response... 404 Not Found 2018-04-07 22:15:02 ERROR 404: Not Found. !!! Couldn't download 'libsearpc-3.0.8.tar.gz'. Aborting.
(In reply to Jonas Stein from comment #0) > $ GENTOO_MIRRORS="" ebuild libsearpc-3.0.8-r2.ebuild fetch > > [..] > HTTP request sent, awaiting response... 404 Not Found > 2018-04-07 22:15:02 ERROR 404: Not Found. > > !!! Couldn't download 'libsearpc-3.0.8.tar.gz'. Aborting. Oh well... Apparently this has gotten broke-fixed in 1d5c3db30745ac4f36d5831d715760865fe3b32c... Upstream uses a very unsane tagging scheme for this repository, meaning that the tag v3.1-latest is actually the software version 3.0.8. Anyways it would be better to use a vcs-snapshot-like SRC_URI in this case. Will fix it up ASAP.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=160214c6008e6fcc0a15c6a4688c5358b8a2e213 commit 160214c6008e6fcc0a15c6a4688c5358b8a2e213 Author: Moritz Schlarb <moschlar@metalabs.de> AuthorDate: 2018-04-08 19:26:09 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2018-04-13 18:25:44 +0000 net-libs/libsearpc: Fix SRC_URI Upstream has an insane usage of git tags, so the tag is called v3.1-latest, but it is actually the library version 3.0.8. On the next version bump, we at least need to change the SRC_URI to use the snapshot tarball, but right now this would lead to mirrors serving the wrong tarball, which is probably not the best thing to do. Closes: https://bugs.gentoo.org/652760 net-libs/libsearpc/libsearpc-3.0.8-r3.ebuild | 36 ++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+)
