Sean Whitton writes ("Bug#904862: dgit: should pass --no-source-only-changes to
pbuilder"):
> Applying these patches does mean that `dgit pbuilder` will probably
> error out with older pbuilder installed, such as the version in stretch.
> But it looks like the pbuilder maintainers keep pbuilder up-to-date in
> stretch-backports, so this seems okay.
I guess there is no way to tell at runtime whether pbuilder supports
this option. As it is these changes need a Breaks.
I wonder if we should provide a way to tell dgit that it doesn't need
to pass --no-source-only-changes. I'm keen to avoid entraining a lot
of stuff in dgit's backports, and the make recent dgit source code
useful in derivatives with different release and backports approaches.
How about: provide --no-source-only-changes via @pbuilder and
@cowbuilder, and add a new option something like
--program!:OPTION,...
which deletes OPTION ... from @program ?
So you could say
dgit --pbuilder!:--no-source-only-changes
IDK if that, plus maybe documenting this in the changelog, would be
enough to avoid thinking we need Breaks: pbuilder (<<...).
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
