[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#643107: enchant: FTBFS: dpkg-buildpackage: error: dpkg-source -b enchant-1.6.0 gave error exit status 2



Source: enchant
Version: 1.6.0-3
Severity: important
Tags: wheezy sid
User: debian-qa@lists.debian.org
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_testdir
> dh_testroot
> rm -f build-stamp 
> # Add here commands to clean up after the build process.
> [ ! -f Makefile ] || /usr/bin/make distclean
> dh_clean 
>  dpkg-source -b enchant-1.6.0
> dpkg-source: info: using source format `3.0 (quilt)'
> dpkg-source: info: building enchant using existing ./enchant_1.6.0.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
>  enchant-1.6.0/config.guess
>  enchant-1.6.0/config.sub
> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/enchant_1.6.0-3.diff.WV_GR7
> dpkg-source: info: you can integrate the local changes with dpkg-source --commit
> dpkg-buildpackage: error: dpkg-source -b enchant-1.6.0 gave error exit status 2
> ────────────────────────────────────────────────────────────────────────────────
> Build finished at 20110924-0032

The full build log is available from:
   http://people.debian.org/~lucas/logs/2011/09/23/enchant_1.6.0-3_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.

Reply to: