Package: camas
Version: 1.2.21-2
Severity: serious

Hi,

building the package camas in a clean sid build environment
(with pbuilder) on i386 results in:

=========================================================================
[...]
make[1]: Entering directory `/tmp/buildd/camas-1.2.21'
make[1]: *** No rule to make target `clean'.  Stop.
make[1]: Leaving directory `/tmp/buildd/camas-1.2.21'
make: [clean] Error 2 (ignored)
rm -f Makefile config.cache config.log config.status
rm -f debian/camas.links
dh_clean
 dpkg-source -b camas-1.2.21
dpkg-source: warning: no utmp entry available and LOGNAME not defined; using 
uid of process (65534)
dpkg-parsechangelog: warning: no utmp entry available and LOGNAME not defined; 
using uid of process (65534)
debian: warning: no utmp entry available and LOGNAME not defined; using uid of 
process (65534)
dpkg-architecture: warning: no utmp entry available and LOGNAME not defined; 
using uid of process (65534)
dpkg-source: building camas using existing camas_1.2.21.orig.tar.gz
dpkg-source: building camas in camas_1.2.21-2.diff.gz
dpkg-source: building camas in camas_1.2.21-2.dsc
 debian/rules build
dh_testdir
if test "yes" = "yes"; then \
            ./autogen.sh; \
        fi
Running autogen in 'tools'
# Add here commands to configure the package.
./configure --prefix=/usr --with-caudium=/usr/lib/caudium 
--with-pike=/usr/bin/pike7.2
checking whether make sets $(MAKE)... yes
checking for a BSD-compatible install... /usr/bin/install -c
configure: WARNING:  Converted . to /tmp/buildd/camas-1.2.21,
If this does not work, please use an absolute path to the configure script. 
./configure: line 1446: type: /usr/bin/pike7.2: not found
/usr/bin/pike7.2 doesn't exist or isn't an executable file.
make: *** [configure-stamp] Error 1
=========================================================================

pike7.2 isn't available anymore.

Thanks for considering.


--
DARTS - Debian Archive Regression Test Suite
http://darts.alioth.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to