Hello,
On Sun 11 Nov 2018 at 01:54PM GMT, Ian Jackson wrote:
> I guess there is no way to tell at runtime whether pbuilder supports
> this option. As it is these changes need a Breaks.
Breaks seems far too strong when `dgit pbuilder` is not core dgit
functionality.
> How about: provide
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 mainta
control: tag -1 +patch
Hello,
On Sun 29 Jul 2018 at 09:50AM +0800, Sean Whitton wrote:
> I think this is likely to be implemented in pbuilder so here is a bug so
> we remember to patch dgit to use the new option.
>
> We'd also want to remove the warning about SOURCE_ONLY_CHANGES=yes from
>
Rationale: if we don't pass this, pbuilder might overwrite the
_source.changes produced by dgit. The new _source.changes will probably
work for an upload, but won't respect the -v option passed to
dgit or calculated by dgit.
--
Sean Whitton
signature.asc
Description: PGP signature
Package: dgit
Version: 6.1
Control: block -1 by 904716
Hello,
I think this is likely to be implemented in pbuilder so here is a bug so
we remember to patch dgit to use the new option.
We'd also want to remove the warning about SOURCE_ONLY_CHANGES=yes from
dgit(1).
--
Sean Whitton
5 matches
Mail list logo
