NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
4.2.19 apt-get key missing
Hi,
I just got myself a Ultra 2. Trying to install gcc and others, but apt-get give me an error:
# apt-get update
Get:1 http://archive.debian.org etch Release.gpg [1033B]
Hit http://archive.debian.org etch Release
Ign http://archive.debian.org etch/main Packages/DiffIndex
Hit http://archive.debian.org etch/main Packages
Get:2 http://www.readynas.com 4.2.19/ Release.gpg [490B]
Hit http://www.readynas.com 4.2.19/ Release
Err http://www.readynas.com 4.2.19/ Release
Get:3 http://www.readynas.com 4.2.19/ Release [738B]
Ign http://www.readynas.com 4.2.19/ Release
Ign http://www.readynas.com 4.2.19/ Packages/DiffIndex
Hit http://www.readynas.com 4.2.19/ Packages
Fetched 1229B in 1s (849B/s)
Reading package lists... Done
W: GPG error: http://www.readynas.com 4.2.19/ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B7F02108D553259A
W: You may want to run apt-get update to correct these problems
#
Does anybody have a similar problem and/or knows how to correct it?
Thanks
Maurice
I just got myself a Ultra 2. Trying to install gcc and others, but apt-get give me an error:
# apt-get update
Get:1 http://archive.debian.org etch Release.gpg [1033B]
Hit http://archive.debian.org etch Release
Ign http://archive.debian.org etch/main Packages/DiffIndex
Hit http://archive.debian.org etch/main Packages
Get:2 http://www.readynas.com 4.2.19/ Release.gpg [490B]
Hit http://www.readynas.com 4.2.19/ Release
Err http://www.readynas.com 4.2.19/ Release
Get:3 http://www.readynas.com 4.2.19/ Release [738B]
Ign http://www.readynas.com 4.2.19/ Release
Ign http://www.readynas.com 4.2.19/ Packages/DiffIndex
Hit http://www.readynas.com 4.2.19/ Packages
Fetched 1229B in 1s (849B/s)
Reading package lists... Done
W: GPG error: http://www.readynas.com 4.2.19/ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B7F02108D553259A
W: You may want to run apt-get update to correct these problems
#
Does anybody have a similar problem and/or knows how to correct it?
Thanks
Maurice
24 Replies
Replies have been turned off for this discussion
- This is a known problem and is due to be fixed in firmware 4.2.20.
-Stefan - Thank you Stefan for the prompt reply.
- Hi all,
I also have 4.2.19 on ReadyNAS Probusiness, and I also get these authentication errors when I try to apt-get build-essential.
Is it safe to ignore those authentication errors and let the install proceed? What will happen if I let it install and then 4.2.20 comes out with the correct keys, will it cause some sort of corruption?
Thanks in advance,
Ken - I have the same on my brand new Ultra 2.
I need tuecrypt and so need to run apt-get.
I downgraded to 4.2.17 but the problem stays the same.
Is there a workaround?
When will 4.2.20 will be released? - Regarding 4.2.20 release, see my answer in your thread: http://www.readynas.com/forum/viewtopic.php?p=335958#p335958
I can't see it being released before next year.
When you downgraded to 4.2.17 did you do an "apt-get update" to ensure the 4.2.17 source list was loaded into APT? - Hi mdgm.
After downgrading to 4.2.17 I tried to do an apt-get update, but get the same error as with 4.2.19: public key unavailable.
It was only when that did not work that I thought I would try the 4.2.20 [T19] beta (I normally would not have tried a beta). But there the link on chrirpa's page to the kernel sources does not work.
Any ideas how I can get truecrypt running? - I just purchased the Ultra 2 Plus this morning, upgraded the firmware unaware of this error and now I'm having the same trouble.
It's been 4moths since the last post on this thread and I find it hard to believe this hasn't been fixed yet...
Is there a fix for this and I just haven't searched for it properly?
Any information on this issue would be appreciated as I need to install a few things... touffster wrote: I just purchased the Ultra 2 Plus this morning, upgraded the firmware unaware of this error and now I'm having the same trouble.
It's been 4moths since the last post on this thread and I find it hard to believe this hasn't been fixed yet...
Is there a fix for this and I just haven't searched for it properly?
Any information on this issue would be appreciated as I need to install a few things...
viewtopic.php?f=35&t=14903&start=90
Check near the bottom, "WhoCares?" explains the issue.WhoCares? wrote: This is a known problem and is due to be fixed in firmware 4.2.20.
-Stefan
Or not, as the case may be... :roll:- Looks quite like ;) Let's hope it is fixed in 4.2.21 then ...
-Stefan
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
