Source: libdrizzle
Version: 0.8-1
Severity: important
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20110923 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  fakeroot debian/rules clean
> dh clean
>    dh_testdir
>    dh_auto_clean
>    dh_clean
>  dpkg-source -b libdrizzle-0.8
> dpkg-source: info: using source format `3.0 (quilt)'
> dpkg-source: info: building libdrizzle using existing 
> ./libdrizzle_0.8.orig.tar.gz
> dpkg-source: warning: file libdrizzle-0.8/m4/pandora_fdatasync.m4 has no 
> final newline (either original or modified version)
> dpkg-source: info: local changes detected, the modified files are:
>  libdrizzle-0.8/config/autorun.sh
>  libdrizzle-0.8/libdrizzle/win32/Makefile.am
>  libdrizzle-0.8/libdrizzle/win32/alloca.c
>  libdrizzle-0.8/libdrizzle/win32/alloca.h
>  libdrizzle-0.8/libdrizzle/win32/config.h
>  libdrizzle-0.8/libdrizzle/win32/conn_uds.c
>  libdrizzle-0.8/libdrizzle/win32/gnulib/errno.h
>  libdrizzle-0.8/libdrizzle/win32/inttypes.h
>  libdrizzle-0.8/libdrizzle/win32/poll.c
>  libdrizzle-0.8/libdrizzle/win32/poll.h
>  libdrizzle-0.8/libdrizzle/win32/stdint.h
>  libdrizzle-0.8/m4/acx_pthread.m4
>  libdrizzle-0.8/m4/pandora_cinttypes.m4
>  libdrizzle-0.8/m4/pandora_cstdint.m4
>  libdrizzle-0.8/m4/pandora_cxx_demangle.m4
>  libdrizzle-0.8/m4/pandora_drizzle_build.m4
>  libdrizzle-0.8/m4/pandora_fdatasync.m4
>  libdrizzle-0.8/m4/pandora_have_innodb.m4
>  libdrizzle-0.8/m4/pandora_have_libavahi.m4
>  libdrizzle-0.8/m4/pandora_have_libbdb.m4
>  libdrizzle-0.8/m4/pandora_have_libdl.m4
>  libdrizzle-0.8/m4/pandora_have_libdrizzle.m4
>  libdrizzle-0.8/m4/pandora_have_libevent.m4
>  libdrizzle-0.8/m4/pandora_have_libgearman.m4
>  libdrizzle-0.8/m4/pandora_have_libmemcached.m4
>  libdrizzle-0.8/m4/pandora_have_libpcre.m4
>  libdrizzle-0.8/m4/pandora_have_libpq.m4
>  libdrizzle-0.8/m4/pandora_have_libreadline.m4
>  libdrizzle-0.8/m4/pandora_have_libtokyocabinet.m4
>  libdrizzle-0.8/m4/pandora_have_libuuid.m4
>  libdrizzle-0.8/m4/pandora_have_libxml2.m4
>  libdrizzle-0.8/m4/pandora_have_libz.m4
>  libdrizzle-0.8/m4/pandora_have_protobuf.m4
>  libdrizzle-0.8/m4/pandora_plugins.m4
>  libdrizzle-0.8/m4/pandora_pthread.m4
>  libdrizzle-0.8/m4/pandora_python3_devel.m4
>  libdrizzle-0.8/m4/pandora_run_cpplint.m4
>  libdrizzle-0.8/m4/pandora_sasl.m4
>  libdrizzle-0.8/m4/pandora_stl_hash.m4
>  libdrizzle-0.8/m4/pandora_swig.m4
>  libdrizzle-0.8/m4/pandora_with_gettext.m4
>  libdrizzle-0.8/m4/pandora_with_lua.m4
>  libdrizzle-0.8/m4/pandora_with_memcached.m4
>  libdrizzle-0.8/m4/pandora_with_perl.m4
>  libdrizzle-0.8/m4/pandora_with_php.m4
>  libdrizzle-0.8/m4/pandora_with_python.m4
>  libdrizzle-0.8/m4/pandora_with_python3.m4
>  libdrizzle-0.8/m4/pandora_with_r.m4
>  libdrizzle-0.8/m4/pandora_with_ruby.m4
>  libdrizzle-0.8/m4/pkg.m4
>  libdrizzle-0.8/tests/gdb-run
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/libdrizzle_0.8-1.diff.FOhXYa
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b libdrizzle-0.8 gave error exit 
> status 2
> ────────────────────────────────────────────────────────────────────────────────
> Build finished at 20110924-0033

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/09/23/libdrizzle_0.8-1_lsid64.buildlog

This error is due to recent dpkg changes "“dpkg-source -b” on a “2.0”
or “3.0 (quilt)” source package will fail if it detects upstream changes
which are not managed by a quilt patch." [0] 

[0] http://lists.debian.org/debian-devel-announce/2011/09/msg00001.html

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.



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

Reply via email to