Re: Upstream Tarball Signature Files

To: Paul Hardy <unifoundry@gmail.com>
Cc: debian-policy@lists.debian.org, guillem@debian.org, 870281@bugs.debian.org
Subject: Re: Upstream Tarball Signature Files
From: Osamu Aoki <osamu@debian.org>
Date: Tue, 8 Aug 2017 02:53:30 -0400
Message-id: <[🔎] 20170808065330.3r6jklddokacfvdw@casper.tc4.so-net.ne.jp>
In-reply-to: <[🔎] CAJqvfD-UyFM718PsyFcq45TqFbn2iOkLgMe+2Lb01+iDJRzFBg@mail.gmail.com>
References: <[🔎] CAJqvfD-UyFM718PsyFcq45TqFbn2iOkLgMe+2Lb01+iDJRzFBg@mail.gmail.com>

Hi,

On Mon, Aug 07, 2017 at 08:26:41PM -0700, Paul Hardy wrote:
...
> Making changes to debian-policy (if deemed appropriate) to allow upstream
> binary signature files would affect at least lintian, dpkg-dev, uscan, and
> Debian maintainer guides.

You should mean one of:
 Debian Developer's Reference
 Debian New Maintainers' Guide
 Guide for Debian Maintainers
 
> Such signature files are discussed in bug #870069 for lintian and #727096 for
> uscan.

Now I understand the context/motivation behind the new #870281 uscan bug
report.

Osamu

Reply to:

References:
- Upstream Tarball Signature Files
  - From: Paul Hardy <unifoundry@gmail.com>

Prev by Date: Re: Upstream Tarball Signature Files
Next by Date: Re: Upstream Tarball Signature Files
Previous by thread: Re: Upstream Tarball Signature Files
Next by thread: Re: Upstream Tarball Signature Files
Index(es):
- Date
- Thread