Bug#893644: stretch-pu: package leap-archive-keyring/2016.03.08
Julien Cristau <jcristau@debian.org> writes:
> 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.
Indeed, I believe this could be a Recommends (like
debian-keyring). Would you like me to change that?
--
micah
Reply to: