Tags -1 moreinfo unreproducible Hi Paul,
On Sun, Jun 09, 2013 at 08:01:39PM -0400, Paul Tagliamonte wrote: > I've noticed the following FTBFS while rebuilding some packages in an > unstable chroot on an amd64 machine. > > /-- > | dpkg-buildpackage: source package zsi > | dpkg-buildpackage: source version 2.1~a1-3 > | dpkg-buildpackage: source changed by Bernd Zeimetz <b...@debian.org> > | dpkg-source --before-build zsi-2.1~a1 > | dpkg-buildpackage: host architecture amd64 > | fakeroot debian/rules clean > | pyversions: missing X(S)-Python-Version in control file, fall back to > debian/pyversions > | test -d debian/patched || install -d debian/patched > | dpatch deapply-all > | dpatch apply-all > | applying patch bogus-shebang-remove to ./ ...no-setuptools not applied to > ./ . > | bogus-shebang-remove not applied to ./ . > | rm -rf patch-stamp patch-stampT debian/patched > | mv: cannot stat './/debian/patched/bogus-shebang-remove.dpatch.new': No > such file or directory > | make: *** [patch-stamp] Error 1 > | dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit > status 2 > \-- I’m not able to reproduce the issue in a pbuilder nor in a sbuild chroot (nor in my machine for that matters), could it have been a transient dpatch-related issue, can you still reproduce it? Moving away from dpatch could be worth it anyway, but I’m not sure this specific issue should be used as a pretext to do so. Regards David
signature.asc
Description: Digital signature
_______________________________________________ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
