Re: [RFC] General Resolution to deploy tag2upload

[Sean Whitton <spwhitton@spwhitton.name>]

Hello,

On Wed 12 Jun 2024 at 04:23pm +01, Simon McVittie wrote:

> On Wed, 12 Jun 2024 at 15:20:45 +0100, Ian Jackson wrote:
>> tag2upload, like dgit, ensures and insists that the git tree you are
>> uploading corresponds precisely [1] to the generated source package.
>>
>> If you base your Debian git maintainer branch on the upstream git (as
>> you should) and there is a discrepancy between the contents of the
>> upstream git branch, and the .orig.tar.gz you're using, the upload
>> will fail.
>
> Is your position here that if your upstream releases source tarballs
> that intentionally differ from what's in git (notably this is true
> for Autotools `make dist`), then any Good™ maintainer must generate
> their own .orig.tar.* from upstream git and use those in the upload,
> disregarding upstream's source tarball entirely?
>
> That approach has many advantages, but it flatly contradicts what devref
> claims a Good™ maintainer would do, which is to always use the pristine
> source tarball as released by upstream (unless it's non-free) - which
> implies that if they're using dgit, then the upstream tree must match
> an import of the tarball.

dev-ref is out-of-date here, I think.  There is no longer a conesnsus we
should be doing that.

-- 
Sean Whitton