Bug 911626

Summary:	dev-libs/liblinear-246: 404 on fetch attempt
Product:	Gentoo Linux	Reporter:	Sarenka <sarenka>
Component:	Current packages	Assignee:	Sam James <sam>
Status:	CONFIRMED ---
Severity:	normal	CC:	jstein, m.lach2003
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Sarenka 2023-08-02 16:36:39 UTC

Whiile upgrading I`ve received 404 error on fetch

>>> Downloading 'https://www.csie.ntu.edu.tw/~cjlin/liblinear/liblinear-2.46.tar.gz'
--2023-08-02 18:23:59--  https://www.csie.ntu.edu.tw/~cjlin/liblinear/liblinear-2.46.tar.gz
Resolving www.csie.ntu.edu.tw... 140.112.30.26
Connecting to www.csie.ntu.edu.tw|140.112.30.26|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2023-08-02 18:24:01 ERROR 404: Not Found.

!!! Couldn't download 'liblinear-2.46.tar.gz'. Aborting.
 * Fetch failed for 'dev-libs/liblinear-246', Log file:
 *  '/var/tmp/portage/dev-libs/liblinear-246/temp/build.log'

Confirmed 404 on uri

Comment 1 Sam James archtester

2023-08-02 16:38:31 UTC

Upstream seem to delete old versions when a new one comes out. Please ensure you have a valid GENTOO_MIRRORS set.

Comment 2 Sarenka 2023-08-02 16:51:39 UTC

Set for valid http in PL, checked on global rsync, synced write before emerge, gentoo paceges shows the same ebuild source as one on my machine.

Comment 3 Sam James archtester

2023-08-02 16:53:11 UTC

(In reply to Sarenka from comment #2)
> Set for valid http in PL, checked on global rsync, synced write before
> emerge, gentoo paceges shows the same ebuild source as one on my machine.

GENTOO_MIRRORS is used to fetch upstream sources that are mirrored. It's not the same as an rsync mirror.

Comment 4 Sarenka 2023-08-02 17:08:09 UTC

OK, so in repos.conf:
sync-uri = rsync://rsync.gentoo.org/gentoo-portage

in make.conf:
GENTOO_MIRRORS="http://ftp.vectranet.pl/gentoo/"
is my standard, i`ve checkd with different before reporting...

Comment 5 Jonas Stein gentoo-dev

2023-08-02 21:19:20 UTC

they do not delete old releases on github. Should we switch to github?
https://github.com/cjlin1/liblinear/tags

Comment 6 Sam James archtester

2023-08-02 21:24:34 UTC

(In reply to Jonas Stein from comment #5)
> they do not delete old releases on github. Should we switch to github?
> https://github.com/cjlin1/liblinear/tags

Those aren't dist tarballs so in theory are unreliable too.

Comment 7 Michał Lach 2023-09-18 14:50:12 UTC

(In reply to Sam James from comment #6)
> (In reply to Jonas Stein from comment #5)
> > they do not delete old releases on github. Should we switch to github?
> > https://github.com/cjlin1/liblinear/tags
> 
> Those aren't dist tarballs so in theory are unreliable too.

That's how version liblinear-243.ebuild is done from the beggining
(https://gitweb.gentoo.org/repo/gentoo.git/commit/dev-libs/liblinear?id=03027911410624d6e59ef558a6747eef81464996), it is based on github.

From a quick glance at bugzilla issue history for version 263, there seems to be none, so the unreliability might just be purely hypothetical.

Just as the OP, I use the PL mirror.