From: Greg KH <gregkh@linuxfoundation.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Ronald Warsow <rwarsow@gmx.de>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: stable kernel checksumming fails
Date: Sun, 7 Mar 2021 16:48:09 +0100 [thread overview]
Message-ID: <YET1uTT61awy0X6S@kroah.com> (raw)
In-Reply-To: <20210307154354.qbbsy355d5zfubnf@chatter.i7.local>
On Sun, Mar 07, 2021 at 10:43:54AM -0500, Konstantin Ryabitsev wrote:
> On Sun, Mar 07, 2021 at 03:45:15PM +0100, Greg KH wrote:
> > > checksumming the downloaded kernel manually gives an "Okay" though.
> > >
> > >
> > > is this just me (on Fedora 33) ?
> >
> > Fails for me on Arch:
> >
> > Verifying checksum on linux-5.11.4.tar.xz
> > /usr/bin/sha256sum: /home/gregkh/Downloads/linux-tarball-verify.gZo313NCk.untrusted/sha256sums.txt: no properly formatted SHA256 checksum lines found
> > FAILED to verify the downloaded tarball checksum
> >
> >
> > Konstantin, anything change recently?
>
> I think it's just cache invalidation problems. I've committed a tiny change to
> the script that always grabs that file from the origin servers instead of
> going via the CDN.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/commit/?id=71e570c5f090b5740e323f98504bf38592785b49
>
> This should sidestep the problem.
>
> -K
Nice, fixed it for me, thanks!
Ronald, does it now work for you too?
greg k-h
next prev parent reply other threads:[~2021-03-07 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 14:10 stable kernel checksumming fails Ronald Warsow
2021-03-07 14:45 ` Greg KH
2021-03-07 15:43 ` Konstantin Ryabitsev
2021-03-07 15:48 ` Greg KH [this message]
2021-03-07 18:28 ` Ronald Warsow
2021-03-07 22:59 ` Bhaskar Chowdhury
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=YET1uTT61awy0X6S@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rwarsow@gmx.de \
--cc=stable@vger.kernel.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