Re: Double build failures
On Thu, May 10, 2012 at 12:07:28PM +0200, Jakub Wilk wrote:
> * Brian Sutherland <brian@vanguardistas.net>, 2012-05-10, 10:36:
> >AFAIK, the problem is double build failures because dpkg detects
> >that there are leftovers/changes from the first build. You end up
> >with failures when a second build is attempted [1].
> >
> >This leads people to use workarounds like this snippet taken from
> >the style guide [2]:
> >
> > override_dh_auto_clean:
> > dh_auto_clean
> > rm -rf build
> > rm -rf *.egg-info
>
> (Note that "rm -rf build" is unrelated to egg-info problem.)
>
> There are simpler workarounds, though:
>
> 1) Add *.egg-info/* to debian/clean. (This requires compat >= 7.)
>
> 2) Add extend-diff-ignore="^[^/]+\.egg-info/" to debian/source/options.
> (This requires source format 3.0.)
>
> >Which work sometimes, but sometimes cause other bugs with the
> >second build. For example, when setup.py uses
> >setuptools+include_package_data without specifying a MANIFEST.in.
> >In that case deleting *.egg-info causes missing files in the built
> >package.
>
> Interesting. Can you show us example of a package like this?
For example zope.configuration, or zope.security, had this problem
around Nov 2011.
Even running the tests didn't help as they ran at build time against the
unpacked source.
> In any case, solution 2) wouldn't trigger this problem.
Yeah, thats the approach that was used in the end for the zope.*
packages. Any objections (from anyone) to updating the style guide to
prefer solution 2?
--
Brian Sutherland
Reply to: