Description:

SCons packages >=3.1.0 are missing the version and revision strings for the SCons engine in "site-packages/SCons/__init__.py". This causes SCons build scripts that check the SCons version to throw an error like "ValueError: invalid version number '__VERSION__'".

$ scons --version
SCons by Steven Knight et al.:
script: v3.1.1.__BUILD__, 2019-08-08 03:09:12, by none on none
engine: v__VERSION__.__BUILD__, __DATE__, by __DEVELOPER__ on __BUILDSYS__
engine path: ['/usr/lib/python3.7/site-packages/SCons']
__COPYRIGHT__


In older package versions <= 3.0.4 built for Python2 that was set correctly:

$ scons --version
SCons by Steven Knight et al.:
script: v3.0.4.3a41ed6b288cee8d085373ad7fa02894e1903864, 2019-01-23 17:30:35, by bdeegan on kufra
engine: v3.0.4.3a41ed6b288cee8d085373ad7fa02894e1903864, 2019-01-23 17:30:35, by bdeegan on kufra
engine path: ['/usr/lib/python2.7/site-packages/SCons']
Copyright (c) 2001 - 2019 The SCons Foundation


In the PKGBUILD for scons <= 3.0.4 the release tarballs from sourceforge were used. The files in the release tarball have been already prepared to contain the correct version and revision strings.

Newer PKGBUILD for scons >= 3.1.0 uses (unprepared) source snapshots from Github. Is there any reason for that? Maybe the prepared release tarball available from pypi.org or sourceforge could be used again. In other case the string replacement with sed in the PKGBUILD should be enhanced to also cover the __init__.py file.