gregor herrmann writes ("Re: Bug#932465: dgit cowbuilder' fails with
"unrecognized option""):
> On Fri, 19 Jul 2019 19:56:32 +0100, Ian Jackson wrote:
> > In the meantime, gregor (and anyone else reading this):
> > I think a workaround is to pass this command-line option to dgit:
> >
> > --cowbuilder!:--no-source-only-changes
>
> I can confirm that
> dgit --rm-old-changes --cowbuilder\!:--no-source-only-changes cowbuilder
> worked.
Good, thaks.
> > This assumes that your cowbuilder is not configured to do source only
> > changes by default. If it does then I think you may have to adjust
> > that, because dgit is of course only invoking cowbuilder to build
> > binaries (presumably for your formal test build), and if you wanted to
> > do a source-only upload you would just use dgit push-source.
>
> I'm happy with my current build setup for now, just wanted to play
> with dgit.
>
> And I've successfully uploaded 2 packages with `dgit push-source'
> already :) which is the more important part in my understanding.
Yes. Indeed if you are happy with your build setup for formal test
builds, there is no need to use dgit to do builds. dgit push-source
is sufficient.
If you want to go through NEW or to upload to security (where
source-only uploads are not permitted) then you may find you need
dgit cowbuilder (or some other dgit build rune) working.
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> 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.
