# emerge =dev-python/aesara-2.8.12 -pvq [ebuild U ] dev-python/aesara-2.8.12 [2.8.10] USE="-test (-doc%*)" PYTHON_TARGETS="python3_10 -python3_9 -python3_11%" !!! Fetched file: aesara-rel-2.8.12.gh.tar.gz VERIFY FAILED! !!! Reason: Filesize does not match recorded size !!! Got: 4582575 !!! Expected: 4582559
Created attachment 853936 [details] build.log
confirmed with GENTOO_MIRRORS="" ebuild aesara-2.8.12.ebuild clean fetch aesara-2.8.11.ebuild still works
Since I'm remanifesting it for the second time, I'm going to shout at upstream.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8770b600d562351b84fb652aeb32a94b5fbcffc0 commit 8770b600d562351b84fb652aeb32a94b5fbcffc0 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2023-02-23 05:54:56 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2023-02-23 06:18:15 +0000 dev-python/aesara: Remanifest again, sigh Upstream has fixed ".git_archival.txt". It does not affect installed files. Closes: https://bugs.gentoo.org/895910 Signed-off-by: Michał Górny <mgorny@gentoo.org> dev-python/aesara/Manifest | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
My mistake. This isn't aesara's upstream fault but how git behaves given the configuration documented in setuptools_scm. The hash changes because the release tag no longer corresponds to the main branch.