Hi,I just got myself a Ultra 2. Trying to install gcc and others, but apt-get give me an error:# apt-get updateGet:1 http://archive.debian.org etch Release.gpg [1033B]Hit http://archive.debian.org etch ReleaseIgn http://archive.debian.org etch/main Packages/DiffIndexHit http://archive.debian.org etch/main PackagesGet:2 http://www.readynas.com 4.2.19/ Release.gpg [490B]Hit http://www.readynas.com 4.2.19/ ReleaseErr http://www.readynas.com 4.2.19/ ReleaseGet:3 http://www.readynas.com 4.2.19/ Release [738B]Ign http://www.readynas.com 4.2.19/ ReleaseIgn http://www.readynas.com 4.2.19/ Packages/DiffIndexHit http://www.readynas.com 4.2.19/ PackagesFetched 1229B in 1s (849B/s)Reading package lists... DoneW: 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 B7F02108D553259AW: 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?ThanksMaurice

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#p335958I 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?

4.2.19 apt-get key missing | NETGEAR Communities

24 Replies

Replies have been turned off for this discussion

InTheShires
Tutor
May 02, 2012
WhoCares? wrote:
Looks quite like ;) Let's hope it is fixed in 4.2.21 then ...

-Stefan

Indeed.

Rather shoddy work though, wouldn't you agree?
WhoCares_
Mentor
May 02, 2012
Well, strictly speaking having a working key isn't really necessary and I can imagine that there's more important stuff going on at ReadyNAS HQ than rebuilding and singing packages. That said it would still be "nice to have". Maybe I should start offering a signed repository ;)

-Stefan
InTheShires
Tutor
May 02, 2012
WhoCares? wrote:
Well, strictly speaking having a working key isn't really necessary and I can imagine that there's more important stuff going on at ReadyNAS

-Stefan

Oh, I get that, and understand it.

It's just annoying, and doesn't represent the brand name very well, that a fix has been missing from the previous two(?) FW upgrades despite assurances to the contrary.
WhoCares_
Mentor
May 03, 2012
As I said, I could offer a signed repository quite easily. Still, that wouldn't be an official repository, that's why I'm reluctant to actually do it. Also I really think that for the vast majority of users it really doesn't matter for they just install add-ons or maybe not even that. Which reminds me: I've got Cacti (almost) finished, the only thing missing is that it doesn't create graphs (well, and the Frontview interface is non-existant right now). Nevertheless: would you be interested in testing?

-Stefan
chirpa
Luminary
May 03, 2012
It was fixed in 4.2.20. I have verified on multiple systems of mine.

If you still see the issue, we would need remote access to take a look at what is causing it.
WhoCares_
Mentor
May 03, 2012
Ok, I tried on two different systems and found one to be working fine and the other to fail. If you want to get remote access just let me know.

-Stefan
WhoCares_
Mentor
May 03, 2012
Whoops. Have to correct myself. The system that is working is running 4.2.20-T42 while the one that's failing is running 4.2.20(-release).

-Stefan
chirpa
Luminary
May 03, 2012
Ya, get me SSH to the problem one?
chirpa
Luminary
May 03, 2012
Thanks to Stefan it has been fixed.
InTheShires
Tutor
May 04, 2012
chirpa wrote:
Thanks to Stefan it has been fixed.

Excellent news. Thank you Stefan and Chirpa.

Yes Stefan I'm interested. PM on it's way.

Forum Discussion

4.2.19 apt-get key missing

24 Replies

Related Content

Broken apt Package after apt-get upgrade ?

what? accidental apt-get upgrade

Missing 5Ghz Channels

Trying to get SDK complete: apt-get update fails with 403 forbidden

Error: Missing JSON response.

NETGEAR Academy

ProSupport for Business