Bug#727096: uscan: store signature for upstream tarball in debian/
Paul Wise
pabs at debian.org
Tue Apr 12 13:52:04 UTC 2016
On Tue, 2016-04-12 at 09:19 +0200, Ansgar Burchardt wrote:
> For a given upstream tarball the upstream signature should go in a file
> with the extension `.asc`. For example, for
> dune-common_2.4.1.orig.tar.xz
> the signature should be in
> dune-common_2.4.1.orig.tar.xz.asc
Is there any possibility to extend this to include the fingerprint,
thus allowing for multiple signatures; for example one from upstream
and one from the Debian maintainer? Having multiple detached signatures
is also planned for the reproducible builds .buildinfo files IIRC.
--
bye,
pabs
https://wiki.debian.org/PaulWise
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/devscripts-devel/attachments/20160412/749a6963/attachment.sig>
More information about the devscripts-devel
mailing list