Created attachment 628126 [details] build.log with 1.15 installed setuptools_scm-3.5.0 recently got stabilized for all arches. However when the previous version was 1.15.6-r1 , it fails with the error in the attached build.log Inspired by https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235301 comment 3, I unmerged setuptools_scm-1.15.6-r1 and installed setuptools_scm-3.5.0 and it worked fine. This is an issue because the previous stable version on arm64 was 1.15.6-r1 , whereas on other arches it was 3.x where this bug does not occur.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4204d850d764dca14e99f9aa4a70a95c2021ff11 commit 4204d850d764dca14e99f9aa4a70a95c2021ff11 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2020-04-12 15:20:28 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2020-04-12 15:21:22 +0000 dev-python/setuptools_scm: Hard-block ancient versions Closes: https://bugs.gentoo.org/715674 Signed-off-by: Michał Górny <mgorny@gentoo.org> dev-python/setuptools_scm/setuptools_scm-3.5.0.ebuild | 1 + 1 file changed, 1 insertion(+)
The main worry here for me was that it appears as if setuptools_scm is using system version of setuptools_scm during the build of itself, and while this does blow up when that system version is ancient - it might cause much more subtle issues (and be very wrong in principle) when that system version is a bit less ancient (e.g. previous version on normal upgrade)
I'd like to fix this properly but it's a horrible upstream design, and I don't really have time for this right now. Given that it only causes issues for people using ancient versions...
