Johannes Schauer Marin Rodrigues writes ("Re: Bug#1056595: dgit: must not
override dpkg include lists"):
> this bug was triggered by julian trying to work on my package sbuild
> in ubuntu. I usually upload all my packages with "dgit --quilt=gbp
> push-source" and hence the problem julian faces was created.
I'm still not sure what the precise problem is. Is it that the .dsc
in the Debian archive contains a .gitignore ?
> I'd also have no problem with resolving this particular situation by
> adding an appropriate debian/source/options to sbuild for the next
> upload. Then the same thing would happen independent of whether the
> person building sbuild uses dgit or not.
I think probably that would help. IIRC there are some strange
interactions between dpkg command line options and d/s/options.
(I can't remember the details offhand.)
dgit does look in d/s/options but mostly to check that there's nothing
there that would make dpkg-source do something that dgit doesn't want.
Maybe some of our documentation (eg, dgit-maint-native(7)) should
recommend creating d/s/options, and maybe dgit ought to check that?
> But would that be future proof as in: will dgit maybe adjust these options in
> the future and if yes, is there something dgit could do to inform me that my
> debian/source/options might be incomplete?
dgit's default behaviour in this area hasn't changed for a very long
time. It always wants to upload precisely your git tree, and
therefore it must pass dpkg-source options that make it able to
generate such a source package.
I think the only thing that might change is that #908747 might get
fixed, but that also seems unlikely and wouldn't invalidate your
d/s/options anyway.
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
