Hello, SCons developers are close to release new major release of SCons, which started to deprecate some obsolete function and dropped support for Python code older than 2.4. Full release notes can be found here: http://sourceforge.net/projects/scons/files/scons/2.0.0.beta.20100531/RELEASE.txt/view
SCons unittest is very well designed, and there should not be any major breakages, but risk of backward incompatible changes could affect some Debian packages which does not see updates from upstreams so often. So, I rebuilt reverse dependencies of SCons to spot some problems, and I published my results online. Here is a brief summary: * 58 packages build-depending on SCons * 53 packages built successfully (2 of them needed sourceful changes, such as build-dependency mangling or so, but not related to SCons). * 4 packages FTBFS: * 1 package has temporary dependency screwup This is a dd-list of FTBFSing packages: Tim Abbott <tabb...@mit.edu> sagemath Michael Ablassmeier <a...@debian.org> kstreamripper William J Beksi <wjbe...@users.sourceforge.net> skim (U) Zhengpeng Hou <zhengpeng-...@ubuntu.com> skim (U) Steffen Joeris <steffen.joe...@skolelinux.de> abakus skim maintainers <jaldhar-s...@debian.org> skim Jaldhar H. Vyas <jald...@debian.org> skim (U) Build logs and other details can be found here: http://people.debian.org/~dktrkranz/scons-2.0 I have already informed upstream of my rebuild tests, and I hopefully will be given instructions on how to properly fix FTBFSes, which I will report as important bugs against affected packages. SCons 2.0 release should happen in June, if RT does not mind, I intend to upload 2.0 to unstable shortafter. Thoughts? -- .''`. : :' : Luca Falavigna <dktrkr...@debian.org> `. `' `-
signature.asc
Description: OpenPGP digital signature
