Package: smart Version: 0.28-7 Severity: serious Hi,
building the package smart in a clean build environment (with pbuilder) on i386 results in: ========================================================================= [...] ii sysv-rc 2.86.ds1-1 Standard boot mechanism using symlinks in /e ii sysvinit 2.86.ds1-1 System-V like init ii tar 1.14-2 GNU tar ii util-linux 2.12p-3 Miscellaneous system utilities ii zlib1g 1.2.2-4 compression library - runtime -> user script /dev/shm/var/cache/pbuilder/build//31044/tmp/hooks/A10dpkg-l.sh finished dpkg-parsechangelog: warning: no utmp entry available and LOGNAME not defined; using uid of process (1001) debian: warning: no utmp entry available and LOGNAME not defined; using uid of process (1001) dpkg-buildpackage: source package is smart dpkg-parsechangelog: warning: no utmp entry available and LOGNAME not defined; using uid of process (1001) debian: warning: no utmp entry available and LOGNAME not defined; using uid of process (1001) dpkg-buildpackage: source version is 0.28-7 dpkg-parsechangelog: warning: no utmp entry available and LOGNAME not defined; using uid of process (1001) debian: warning: no utmp entry available and LOGNAME not defined; using uid of process (1001) dpkg-buildpackage: source maintainer is Michael Vogt <[EMAIL PROTECTED]> dpkg-architecture: warning: no utmp entry available and LOGNAME not defined; using uid of process (1001) dpkg-architecture: warning: no utmp entry available and LOGNAME not defined; using uid of process (1001) dpkg-buildpackage: host architecture is i386 dpkg-checkbuilddeps: warning: no utmp entry available and LOGNAME not defined; using uid of process (1001) dpkg-architecture: warning: no utmp entry available and LOGNAME not defined; using uid of process (1001) dpkg-architecture: warning: no utmp entry available and LOGNAME not defined; using uid of process (1001) fakeroot debian/rules clean dh_testdir dh_testroot rm -f build-stamp configure-stamp # Add here commands to clean up after the build process. #-/usr/bin/make clean ./setup.py clean --all make: ./setup.py: Command not found make: *** [clean] Error 127 ========================================================================= This is caused by ./setup.py being interpreted by python which in turn doesn't exist since all the python2.3 dependencies don't include /usr/bin/python. A crude solution would be adding "python" to Build-Depends but a careful python2.4 transition would be appropriate here. /usr/bin/python from python2.4 seems to be the cause of the build success on the maintainer's machine since he didn't try the build in a clean environment. Remember: pbuilder is your friend. Thanks for considering. -- DARTS - Debian Archive Regression Test Suite -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
