Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 8 May 2023 13:01:07 -0400
From:   Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     Ronald Warsow <rwarsow@gmx.de>, linux-kernel@vger.kernel.org,
        stable@vger.kernel.org
Subject: Re: no sha256sum for 6.3.1 (was Re: Linux 6.3.1)
Message-ID: <20230508-length-distress-784870@meerkat>
References: <f0497747-2318-7355-6ea6-ff01f9eb97ef@gmx.de>
 <2023050617-stardom-granola-32e3@gregkh>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <2023050617-stardom-granola-32e3@gregkh>
Precedence: bulk

On Sat, May 06, 2023 at 09:38:35AM +0900, Greg KH wrote:
> > fetching new kernels via script:
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/tree/get-verified-tarball
> > 
> > it seems
> > https://cdn.kernel.org/pub/linux/kernel/v6.x/sha256sums.asc
> > 
> > doesn't contain a hash for 6.3.1
> 
> Yeah, that does look odd.
> 
> Konstantin, I think you said you updated some things on the servers
> right after I did the 6.3.1 release, would this have caused the
> signature to not be recorded in this file?

Sorry, this got fixed last week. I forgot to mount the key storage after the
final reboot. It should be all good now.

-K