Gandolf_1
Posts: 3
Joined: Mon Jan 01, 2018 8:33 pm

Re: Trouble updating - GPG error? NO_PUBKEY? Err InRelease?

Tue Jan 02, 2018 2:23 pm

/etc/apt/sources.list contains
deb http://mirrordirector.raspbian.org/raspbian/ stretch main contrib non-free rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://archive.raspbian.org/raspbian/ stretch main contrib non-free rpi

/etc/apt/sources.list.d is empty

raspberry pi stretch doesn't appear to have the MONOIDE.


Anything else I can try??

torak666
Posts: 61
Joined: Tue Feb 06, 2018 4:58 pm

Re: Trouble updating - GPG error? NO_PUBKEY? Err InRelease?

Sat Apr 14, 2018 2:06 pm

Hi,
i installed the last release of raspbian strech lite
Raspbian-stretch-lite 2018-03-13-r
since March month i try without success to update my raspberrypi with sudo apt-get update
now i have a key error to update the rapsberry pi with command "sudo apt-get update"

I have already done this command without success
wget https://archive.raspbian.org/raspbian.public.key -O - | sudo apt-key add -

i don't know what to do for this error

Code: Select all

sudo apt-get update
Hit:1 http://archive.raspberrypi.org/debian stretch InRelease
Hit:2 http://mirrordirector.raspbian.org/raspbian stretch InRelease
Ign:3 https://dl.bintray.com/mpmc/deb raspbianstretch InRelease
Get:4 https://dl.bintray.com/mpmc/deb raspbianstretch Release [8,212 B]
Get:5 https://dl.bintray.com/mpmc/deb raspbianstretch Release.gpg [821 B]
Ign:5 https://dl.bintray.com/mpmc/deb raspbianstretch Release.gpg
Fetched 9,033 B in 1s (7,947 B/s)
Reading package lists... Done
W: GPG error: https://dl.bintray.com/mpmc/deb raspbianstretch Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 379CE192D401AB61
W: The repository 'https://dl.bintray.com/mpmc/deb raspbianstretch Release' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Thanks for advance for any help to solve this error.
Regards

Babber
Posts: 3
Joined: Thu Jul 05, 2018 11:14 am

Re: Trouble updating - GPG error? NO_PUBKEY? Err InRelease?

Thu Jul 05, 2018 11:19 am

Hi,
I had a very similar problem, and this helped me:

Code: Select all

wget https://archive.raspbian.org/raspbian.public.key -O - | sudo apt-key add -
wget https://archive.raspberrypi.org/debian/raspberrypi.gpg.key -O - | sudo apt-key add -
The first command can also be found at https://www.raspbian.org/RaspbianRepository, but as you said you have already tried that. But maybe along that line, you could try something like

Code: Select all

wget https://dl.bintray.com/mpmc/deb/:Release.gpg -O - | sudo apt-key add -
which may be the key to the specific repository you need.
I hope this helps.

mgirod
Posts: 5
Joined: Sun Dec 02, 2018 10:29 am

Re: Trouble updating - GPG error? NO_PUBKEY? Err InRelease?

Sun Dec 02, 2018 10:47 am

I have the following (standard?) addresses in my lists:

$ cat /etc/apt/sources.list
deb http://mirrordirector.raspbian.org/raspbian/ jessie main contrib non-free rpi
$ cat /etc/apt/sources.list.d/raspi.list
deb http://archive.raspberrypi.org/debian/ jessie main ui

To them correspond the keys:

$ sudo apt-key list | egrep ^pub
pub 2048R/90FDDD2E 2012-04-01
pub 2048R/7FA3303E 2012-06-17

The time stamps strike me as old.
However, if I delete them and run:

$ wget http://mirrordirector.raspbian.org/raspbian.public.key -O - | sudo apt-key add -
$ wget http://archive.raspbian.org/raspbian.public.key -O - | sudo apt-key add -

I get them back. This is the setup with which I fail to update.
The following command doesn't add a key:

$ wget https://archive.raspberrypi.org/debian/ ... pi.gpg.key -O - | sudo apt-key add -

mgirod
Posts: 5
Joined: Sun Dec 02, 2018 10:29 am

Re: Trouble updating - GPG error? NO_PUBKEY? Err InRelease?

Mon Dec 03, 2018 10:10 pm

I thought I found the reason for my problems: the switch from jessie to stretch, but no, no help:
/> cat /etc/apt/sources.list /etc/apt/sources.list.d/raspi.list
deb http://mirrordirector.raspbian.org/raspbian/ stretch main contrib non-free rpi
deb http://archive.raspberrypi.org/debian/ stretch main ui
/> sudo apt update
Get:1 http://archive.raspberrypi.org stretch InRelease [25.3 kB]
Get:2 http://mirrordirector.raspbian.org stretch InRelease [15.0 kB]
Ign http://archive.raspberrypi.org stretch InRelease
E: GPG error: http://archive.raspberrypi.org stretch InRelease: Clearsigned file isn't valid, got 'NODATA' (does the network require authentication?)

mgirod
Posts: 5
Joined: Sun Dec 02, 2018 10:29 am

Re: Trouble updating - GPG error? NO_PUBKEY? Err InRelease?

Wed Dec 05, 2018 8:03 pm

Reboot helped.

deesse_K
Posts: 1
Joined: Tue Apr 02, 2019 7:05 am

Re: Trouble updating - GPG error? NO_PUBKEY? Err InRelease?

Tue Apr 02, 2019 7:14 am

Hi,

For thoose who get the same error I used to manage it in adding dirmngr package

Code: Select all

  apt-get install dirmngr
and add manually the missing keys

Code: Select all

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys YOUR_KEY_HERE
Hope this can help.

hilliao
Posts: 3
Joined: Mon Feb 10, 2020 7:25 am

Re: Trouble updating - GPG error? NO_PUBKEY? Err InRelease?

Sun May 24, 2020 6:14 pm

The error I got was the following:

Code: Select all

hil@raspberrypi:~ $ sudo apt update
Hit:1 https://download.docker.com/linux/raspbian stretch InRelease
Hit:2 https://download.docker.com/linux/raspbian buster InRelease
Get:4 http://archive.raspberrypi.org/debian buster InRelease [25.1 kB]
Get:5 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Get:3 https://packagecloud.io/headmelted/codebuilds/debian stretch InRelease [23.4 kB]
Err:3 https://packagecloud.io/headmelted/codebuilds/debian stretch InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0CC3FD642696BFC8
Fetched 63.5 kB in 2s (36.4 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
189 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packagecloud.io/headmelted/codebuilds/debian stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0CC3FD642696BFC8
W: Failed to fetch https://packagecloud.io/headmelted/codebuilds/debian/dists/stretch/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0CC3FD642696BFC8
W: Some index files failed to download. They have been ignored, or old ones used instead.
The fix I found was from the Repository users: Why am I getting GPG errors from a packagecloud.io repository? section in https://blog.packagecloud.io/eng/2018/1 ... migration/. The command I executed was:

Code: Select all

curl -L https://packagecloud.io/headmelted/codebuilds/gpgkey  | sudo apt-key add -
apt update
Hit:1 https://download.docker.com/linux/raspbian stretch InRelease
Hit:3 https://download.docker.com/linux/raspbian buster InRelease
Get:4 http://archive.raspberrypi.org/debian buster InRelease [25.1 kB]
Get:2 https://packagecloud.io/headmelted/codebuilds/debian stretch InRelease [23.4 kB]
Get:5 https://packagecloud.io/headmelted/codebuilds/debian stretch/main armhf Packages [5,025 B]
Hit:6 http://raspbian.raspberrypi.org/raspbian buster InRelease
Fetched 53.5 kB in 4s (13.5 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
190 packages can be upgraded. Run 'apt list --upgradable' to see them.
error fixed!

Return to “Troubleshooting”