The ebuild does not seem to have mirror restriction, and yet file fail the fetch due to checksum mismatch. I guess our mirroring system tries to pull it in still: $ ebuild jabref-bin-4.1.ebuild clean fetch ... >>> Downloading 'https://github.com/JabRef/jabref/releases/download/v4.1/JabRef-4.1.jar' --2019-05-12 10:36:39-- https://github.com/JabRef/jabref/releases/download/v4.1/JabRef-4.1.jar Resolving github.com... 140.82.118.3 Connecting to github.com|140.82.118.3|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/17634071/d81aa62c-e81d-11e7-8b0e-e747fe10bb65?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20190512%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20190512T093640Z&X-Amz-Expires=300&X-Amz-Signature=41a61d660a9c3e3b340eb0473d1e1a029d54f37900345c26df99deb3d6f4d14c&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3DJabRef-4.1.jar&response-content-type=application%2Foctet-stream [following] --2019-05-12 10:36:41-- https://github-production-release-asset-2e65be.s3.amazonaws.com/17634071/d81aa62c-e81d-11e7-8b0e-e747fe10bb65?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20190512%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20190512T093640Z&X-Amz-Expires=300&X-Amz-Signature=41a61d660a9c3e3b340eb0473d1e1a029d54f37900345c26df99deb3d6f4d14c&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3DJabRef-4.1.jar&response-content-type=application%2Foctet-stream Resolving github-production-release-asset-2e65be.s3.amazonaws.com... 52.216.163.59 Connecting to github-production-release-asset-2e65be.s3.amazonaws.com|52.216.163.59|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 55587800 (53M) [application/octet-stream] Saving to: '/gentoo/distfiles/JabRef-4.1.jar.__download__' ... /gentoo/distfiles/JabRef-4.1.jar._ 100%[===============================================================>] 53.01M 152KB/s in 6m 46s 2019-05-12 10:43:28 (134 KB/s) - '/gentoo/distfiles/JabRef-4.1.jar.__download__' saved [55587800/55587800] !!! Fetched file: JabRef-4.1.jar VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 55587800 !!! Expected: 56793908 Refetching... File renamed to '/gentoo/distfiles/JabRef-4.1.jar._checksum_failure_.ctyng7en' !!! Couldn't download 'JabRef-4.1.jar'. Aborting.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=43a8cdb2a846e642dfd941ea999dcc3dc0b76e60 commit 43a8cdb2a846e642dfd941ea999dcc3dc0b76e60 Author: Patrice Clement <monsieurp@gentoo.org> AuthorDate: 2019-05-12 12:21:38 +0000 Commit: Patrice Clement <monsieurp@gentoo.org> CommitDate: 2019-05-12 12:22:16 +0000 app-text/jabref-bin: regenerate jabref-bin-4-1 Manifest hash. Closes: https://bugs.gentoo.org/685704 Signed-off-by: Patrice Clement <monsieurp@gentoo.org> Package-Manager: Portage-2.3.62, Repoman-2.3.11 app-text/jabref-bin/Manifest | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
