Bug#893644: stretch-pu: package leap-archive-keyring/2016.03.08
- To: micah anderson <micah@debian.org>, 893644@bugs.debian.org
- Cc: "Adam D. Barratt" <adam@adam-barratt.org.uk>
- Subject: Bug#893644: stretch-pu: package leap-archive-keyring/2016.03.08
- From: Julien Cristau <jcristau@debian.org>
- Date: Sun, 2 Dec 2018 17:11:13 +0100
- Message-id: <[🔎] 20181202161113.GA21024@tomate.cristau.org>
- Reply-to: Julien Cristau <jcristau@debian.org>, 893644@bugs.debian.org
- In-reply-to: <87h8os2pja.fsf@muck.riseup.net>
- References: <152157795708.6107.11774770508154554723.reportbug@localhost> <1521581215.3014.20.camel@adam-barratt.org.uk> <152157795708.6107.11774770508154554723.reportbug@localhost> <87o9jhpogb.fsf@riseup.net> <1522530220.3129.87.camel@adam-barratt.org.uk> <152157795708.6107.11774770508154554723.reportbug@localhost> <87h8os2pja.fsf@muck.riseup.net> <152157795708.6107.11774770508154554723.reportbug@localhost>
On Tue, Apr 03, 2018 at 01:00:41PM -0400, micah anderson wrote:
> I went with 2017.11.24~deb9u1 because indeed, the changes since the
> current version in stretch are appropriate for a stable update, namely:
>
> 1. Providing keys in a second location, to aid in the transition from
> jessie->stretch methods for how sources.list [signed-by=] method changed
> to allow for both paths and fingerprints
>
> 2. fix priority to be in-line with debian policy
>
> 3. add a dependency on gnupg
>
> 4. update the expirations on the keys themselves
>
> I'm only unsure if changing the Priority section is allowed in a stable
> point update?
>
It's a no-op. Priority and Section in the package are meaningless.
I'm curious about 3 though, no explanation seems to be provided.
Cheers,
Julien
Reply to: