Source: dipy Version: 0.5.0-3 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: > make[2]: Entering directory `/build/dipy-VVIcz0/dipy-0.5.0/doc' > cd examples_built && rm -rf *.py *.rst *.png fig > rm -rf _build/* > rm *-stamp > rm: cannot remove `*-stamp': No such file or directory > make[2]: [clean] Error 1 (ignored) > make[2]: Leaving directory `/build/dipy-VVIcz0/dipy-0.5.0/doc' > dh_clean > make[1]: Leaving directory `/build/dipy-VVIcz0/dipy-0.5.0' > dpkg-source -b dipy-0.5.0 > dpkg-source: info: using source format `3.0 (quilt)' > dpkg-source: info: building dipy using existing > ./dipy_0.5.0.orig-doc-examples.tar.gz ./dipy_0.5.0.orig.tar.gz > dpkg-source: info: local changes detected, the modified files are: > dipy-0.5.0/dipy/COMMIT_INFO.txt > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/dipy_0.5.0-3.diff.9xTEHZ > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b dipy-0.5.0 gave error exit status 2 > ──────────────────────────────────────────────────────────────────────────────── > Build finished at 20110923-2334 The full build log is available from: http://people.debian.org/~lucas/logs/2011/09/23/dipy_0.5.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. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
