Simon McVittie writes ("Bug#1019454: dgit push-built --quilt=unapplied should
auto-create separate dgit view like push-source does"):
> On Fri, 09 Sep 2022 at 18:53:27 +0100, Ian Jackson wrote:
> > Hmmm. I think dgit is expecting you to have built the source package
> > along with the binaries, with some variant on `dgit build`.
>
> That seems plausible. I did build the source package along with the
> binaries, just not with `dgit build`: I already have a build environment
> I'm happy with, and I don't want to pass its options through too many
> layers of "interpret some options and then pass the rest on". (Perhaps
> I should start using `dgit build` for its convenient -v handling, but
> that's not part of my workflow right now.)
Right, fair enough.
> > Note that there are situations where you must use dgit to make the
> > source package (or specify funny options to your builder program),
> > notably if you have changes to (or additions of) .gitignore in the
> > upstream part of the tree.
>
> If I got this wrong, the failure mode would be that dgit complains that
> my .dsc doesn't match my git state and refuses to upload it, correct?
Yes.
> If so, I don't see that as a problem: I'm fine with limiting myself
> to the category of changes that makes my git tree simple to deal with
> (that goes with the patches-unapplied territory).
Quite so.
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.
