Package: libdatrie
Version: 0.2.2-2
Severity: serious
Justification: ftbfs

Hi,

your package fails to build twice in a row:

 dpkg-buildpackage -rfakeroot -D -us -uc
dpkg-buildpackage: set CFLAGS to default value: -g -O2
dpkg-buildpackage: set CPPFLAGS to default value:
dpkg-buildpackage: set LDFLAGS to default value:
dpkg-buildpackage: set FFLAGS to default value: -g -O2
dpkg-buildpackage: set CXXFLAGS to default value: -g -O2
dpkg-buildpackage: source package libdatrie
dpkg-buildpackage: source version 0.2.2-2
dpkg-buildpackage: source changed by Theppitak Karoonboonyanan <[email protected]>
dpkg-buildpackage: host architecture i386
 fakeroot debian/rules clean
dh_testdir
dh_testroot
# Add here commands to clean up after the build process.
[ ! -f Makefile ] || /usr/bin/make maintainerclean
make[1]: Entering directory `/tmp/libdatrie-0.2.2'
make[1]: *** No rule to make target `maintainerclean'.  Stop.
make[1]: Leaving directory `/tmp/libdatrie-0.2.2'
make: *** [clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
debuild: fatal error at line 1330:
dpkg-buildpackage -rfakeroot -D -us -uc failed


You probably intended to use maintainer-clean (note the dash).

In the changelog you mentioned, that you changed that because you now
run autoreconf. Please note though, that maintainer-clean will *not*
clean up the files that were changed by autoreconf, i.e. you will end up
with a huge diff. You rather have to clean up the generated files
manually.

In you blog you mentioned, that you converted all you packages to this
new scheme, so it might be worthwile to check them all (I only checked
libdatrie).

Thanks,
Michael



-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32.3 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



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

Reply via email to