On Wednesday, April 22, 2020 at 7:01:40 AM UTC-6, armi wrote:
>
> Hi Mailing List! 
>
> I get the following error since a couple of weeks. Platform is CentOS 
> Linux release 7.7.1908 (Core). Installed Jenkins is 2.232-1.1 . 
>
> If you do research with the error message, this is apparently an issue 
> that occurs every now and then. 
>
> Why does the maintainer always mess up with the GPG key? 
>
> How can it be fixed? 
>

Thanks for asking and thanks for using Jenkins.  Jenkins 2.232 was the 
first Jenkins build from the Jenkins core release automation project.  It 
is the first change to the Jenkins GPG signing key in many, many years.

You can resolve it by following the directions on the Jenkins install page 
http://mirrors.jenkins-ci.org/redhat/ .  That page says:

WARNING: The gpg key use to sign our packages has been updated on 16th of 
April 2020, therefore you need to reimport it if you imported before this 
date.

The specific command you need to execute is:

 sudo rpm --import https://pkg.jenkins.io/redhat/jenkins.io.key


Thanks,
Mark Waite
 

>
> Thank you! 
>
> Best regards 
> Armin 
>
>
> The following updates will be applied on minibldjnk: 
> ================================================================================
>  
>
>   Package           Arch             Version             Repository   
>  Size 
> ================================================================================
>  
>
> Updating: 
>   jenkins           noarch           2.233-1.1           jenkins    63 M 
>
> Transaction Summary 
> ================================================================================
>  
>
> Upgrade  1 Package 
> Updates failed to install with the following error message: 
> Public key for jenkins-2.233-1.1.noarch.rpm is not installed 
>
>
> __________ Information from mm-lab IT security __________The message was 
> checked by ESET Mail Security. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f2ddea88-8c63-4e18-9428-641a5403d733%40googlegroups.com.

Reply via email to