On Sun, Mar 22, 2020 at 09:42:32PM +0000, Chris Lamb wrote:
> > Should use the '-sa' option to force both the *.orig.tar.gz and *.asc
> > into .*.changes? I think that such an upload will be rejected by DAK, as
> > the *.tar.gz is already in the archive. But to be honest this is based
> > on my past experiences, but maybe something has changed since then. Is
> > re-uploading upstream tarballs permitted now?
>
> AIUI -sa by itself will not be rejected but I am unclear whether the
> inclusion of the signature will cause a rejection. You could just try
> it? :)
I can tell you both that such an upload won't be rejected by dak as long
as the .orig.tar.gz is the very same as the one that was previously
uploaded.
Honestly, I'm somewhat partial on putting such archive-dependant
information in lintian is alright (dak is only one of the many debian
archive software out there…).
Also, to put the .tar.gz.asc in the git repository you'll need to ask
pristine-tar to do a new "commit" (see man pristine-tar for "commit");
that said if I were you I'd just manually checkout to the pristine-tar
branch and git commit the .asc file… (you'll see if that worked if
`pristine-tar list` list the file once you go back to the master
branch).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Attachment:
signature.asc
Description: PGP signature