Hello, On Sun, Jan 01, 2017 at 09:29:17PM +0000, Ian Jackson wrote: > Bernhard R. Link writes ("Re: Idea: sbuild/pbuilder "--dgit" option"): > > The effect it has (and what I understand the thing you want), is that it > > will make a build *fail* if there is a .git-ignore file that has a > > different content than the .orig.tar.* (or is not included in the form > > of a debian/patches/ file). Because when it is no longer an ignored > > derivation between unpacked source and current clean working directory, > > it is by definition an fatal error. (Unless one was to reintroduce the > > annoying, error-hiding, error-introducing 'generate new patches at build' > > time behaviour). > > This is a problem in some situations, indeed. The problem case is > when: the source format is `3.0 (quilt)'; without > `single-debian-patch'; and the build is being done by a maintainer; > and the maintainer wants to build from their master branch. > > But I think the proposed --dgit option to a build tool can still be > useful in some situations. For example, with other source formats, or > with single-debian-patch (where I think the patch is autoregenerated > as needed); or if the build is being done by a non-maintainer user > from the dgit history view; or the maintainer is willing to invoke > dgit to obtain the dgit history view and build from that.
Quick note that I believe you have to add auto-commit in addition to single-debian-patch to get this automatic behaviour. -- Sean Whitton
Description: PGP signature
_______________________________________________ vcs-pkg-discuss mailing list firstname.lastname@example.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/vcs-pkg-discuss