From: james <garftd@verizon.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT: latest longterm kernel.org patches are unsigned
Date: Mon, 20 Aug 2018 17:33:03 -0400 [thread overview]
Message-ID: <e563fc16-b539-168b-b601-bcefdd6658f5@verizon.net> (raw)
In-Reply-To: <20180817160712.mlopxb7xpx6ny6qu@matica.foolinux.mooo.com>
On 8/17/18 12:07 PM, Ian Zimmerman wrote:
> If you browse this URL:
>
> https://cdn.kernel.org/pub/linux/kernel/v4.x/
>
> you'll see that for each 4.14 patch up to 4.14.58 there is a
> cooresponding GPG signature file:
>
> patch-4.14.58.sign 25-Jul-2018 09:28 833
> patch-4.14.58.xz 25-Jul-2018 09:28 1M
>
> etc.
>
> But starting with 4.14.59, there are no .sign files. Why? Is this a
> bug, and if so, where do I report it?
>
> This breaks my lovingly duct-taped kernel update infrastructure ...
>
Ian,
Not sure this is related to your problem but it's an interesting read
about (intel) microcodes and current blocks being enforced by Gentoo,
clandestinely?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906158
https://bugs.gentoo.org/664134
Apologies if I research is fragmented or flawed...
hth,
James
next prev parent reply other threads:[~2018-08-20 21:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 16:07 [gentoo-user] OT: latest longterm kernel.org patches are unsigned Ian Zimmerman
2018-08-19 20:01 ` Nils Freydank
2018-08-20 21:33 ` james [this message]
2018-08-21 3:22 ` J. Roeleveld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e563fc16-b539-168b-b601-bcefdd6658f5@verizon.net \
--to=garftd@verizon.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox