Hello,
On Mon 30 Jul 2018 at 11:37AM +0200, Johannes Schauer wrote:
> my problem with adding the --no-source-only-changes option is, that sbuild
> already today has a ton of command line options. I even know of blog posts
> that
> specifically lament the hell of options that they are confronted
Hi Sean,
Quoting Sean Whitton (2018-07-30 10:50:32)
> > is there any reason why dgit does not set the SBUILD_CONFIG environment
> > variable to either an empty value or to a config file that lets sbuild do
> > exactly what dgit expects it to do?
> We are not trying to be a full wrapper for
Hello Johannes,
On Mon 30 Jul 2018 at 06:37AM +0200, Johannes Schauer wrote:
> is there any reason why dgit does not set the SBUILD_CONFIG environment
> variable to either an empty value or to a config file that lets sbuild do
> exactly what dgit expects it to do?
We are not trying to be a full
Hi,
Quoting Sean Whitton (2018-07-30 05:58:47)
> Please provide a command line option to override the sbuildrc
> configuration key SOURCE_ONLY_CHANGES. I suggest
> --no-source-only-changes.
>
> When dgit invokes sbuild it generates the _source.changes itself, and
> needs to prevent sbuild from
Package: sbuild
Version: 0.77.0-4
Tags: upstream
X-debbugs-cc: ijack...@chiark.greenend.org.uk
Dear maintainer,
Please provide a command line option to override the sbuildrc
configuration key SOURCE_ONLY_CHANGES. I suggest
--no-source-only-changes.
When dgit invokes sbuild it generates the
5 matches
Mail list logo
