From: Ian Zimmerman <itz@very.loosely.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] OT: latest longterm kernel.org patches are unsigned
Date: Fri, 17 Aug 2018 09:07:13 -0700 [thread overview]
Message-ID: <20180817160712.mlopxb7xpx6ny6qu@matica.foolinux.mooo.com> (raw)
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 ...
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.
next reply other threads:[~2018-08-17 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 16:07 Ian Zimmerman [this message]
2018-08-19 20:01 ` [gentoo-user] OT: latest longterm kernel.org patches are unsigned Nils Freydank
2018-08-20 21:33 ` james
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=20180817160712.mlopxb7xpx6ny6qu@matica.foolinux.mooo.com \
--to=itz@very.loosely.org \
--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