On Wednesday 15 September 2010 07:40:56 Jonas Smedegaard wrote:
> Hi,
> Just switching to dpkg source format 3.0 does not work nicely with
> git-buildpackage: the source format auto-applies patches and leave it as
> such after package cleanup, while git-buildpackage expects patches to be
> unapplied.
> As some may have noticed in past threads, I have not liked the approach
> of extending debian/rules to explicitly unapply patches based on e.g.
> the existance of the .git directory.  I find that a bad hack.
> It seems the proper solution is at hand: I noticed at Debian Planet the
> following entry:
> http://raphaelhertzog.com/2010/09/14/how-to-customize-dpkg-sources-behaviou
> r-in-your-debian-source-package/
> In that blog entry, Raphaƫl mentions the special file
> debian/source/local-options which is taken into account during build but
> not included into the generated source package.
> I hereby propose that we recommend generally switching to source format
> 3.0 (quilt) - even for packages not currently using patches - and add
> the following info to debian/source/local-options:
> unapply-patches = True
> abort-on-uptream-changes = True
> Warning: This is completely untested.  Just written based on above blog
> entry. ;-)
>   - Jonas

Just tried this (after reading dpkg-source manpage as well, above entries are 
wrong). This unapplies the patches after a build, not during cleaning of a 
package where the package is cleaned first, then patches are unapplied. This 
will break packages which patch the build system to fix cleaning issues.

Andres Mejia

pkg-multimedia-maintainers mailing list

Reply via email to