▲ Post: #1 ▼

This has started happening after a complete update:

W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://dl.dropbox.com ./ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C1622487AAA521A8

What's the significance of this issue and how critical is it; because it doesn't look like a good thing, for repository authentication of "safe" updates.



Thanks - cef1000

▲ Post: #2 ▼

(22-08-2011 04:15 AM)cef1000 Wrote:  This has started happening after a complete update:

W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://dl.dropbox.com ./ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY C1622487AAA521A8

What's the significance of this issue and how critical is it; because it doesn't look like a good thing, for repository authentication of "safe" updates.



Thanks - cef1000

Not a big deal at all. Just a problem r/t dropbox. Here is the possible explanation I found:

This is because of the apparently hasty algorithm I developed for finding the latest version. It simply looks at the most recent entry in the rss feed, and compares it against your currently installed version. In the past, this worked just fine. Just recently though, Dropbox has began backporting fixes to their stable branch. For example, stable version 1.1.31 was released more recently than experimental version 1.2.0. If you were using version 1.2.0 already, even though it finds 1.1.31 as the most recent entry in the rss feed, the comparator finds that you are already running a greater numbered version. On the other hand, if you were running 1.1.31, it won't find 1.2.0 - and if you were using something older it'd find 1.1.31 as the most recent and upgrade to it.


There are some possible work arounds on this page, but I would not worry about it.

Kantoquad

▲ Post: #3 ▼

Ok I'm just going to take your word for it that its not a security issues of some sort. My only comment is that for new inexperienced Linux users using PinGuyOS as a possible replacement OS for Windows; would likely be disconcerted about that message.

Since this notebook is my multi-boot field machine and I'm trying to determine if I can get everything I need done in the field using PinGuyOs instead of Windows; it doesn't concern me at all to ignore this.



I've marked it solved! Many thanks.

cef1000

▲ Post: #4 ▼

Cef1000

No problem. This does not seem to be unique to Pinguy., but keep us updated on your findings!! Occasional errors happen with synaptic. Sometimes repositories are down. This should have no real effect on your computer.

Regards,

Kantoquad