Adrian Bunk writes ("Bug#1028025: hippotat shouldn't be a native package"):
> I don't know what your workflow is, e.g. git-archive(1) with
> export-ignore attribute for debian/ could be used to generate
> the orig.tar.xz.
My upstream release process does not involve tarballs.
I make and publish a git tag. Downstreams are expected to get the
source code from git. If they want to make tarballs they can do so.
Then with my Debian hat on, I make a tarball because Debian still
expects tarballs. dgit does the git to tarball conversion for me.
(I also do a "cargo publish", which does involve tarballs underneath.
That is quite regrettable, but out of my bailiwick.)
If someone does an NMU in Debian (they are very welcome to) I will
either use the git branch and commits they provided (if they did it
with dgit or otherwise gave me their git branch eg via salsa) or
import it into git ASAP (if they didn't).
IMO It doesn't make sense to separately maintain upstream and debian
branches just to handle a usually-empty difference. I have often
integrated NMUs in packages maintained this way and it works well.
One way to look at this is that (with my Debian hat on) I am using the
workflow described in dgit-maint-merge(7).
> being able to split my own changes into separate patches makes it
> easier for other people to review my changes.
That is true, if you need to make a substantial NMU. I'm sure most
maintainers will almost immediately import such a thing into git.
In such a situation (you're making an NMU with a package I maintain
this way), if you were to provide me with your git commits, that would
be welcome. The most obvious way would be for you to do your NMU with
`dgit push`, but of course you can use a branch or MR on salsa or
something.
If you prefer to stick to the lowest-common-denominator tarballs, as
represented in the Debian ftp archive, then of course that is up to
you.
I hope this clarifies things.
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.
