PDA

View Full Version : Apt-get update = error


turbovomit
2011-07-16, 17:50
Hi,
when i do a apt-get update , terminal say something like this:

W: GPG error: https://downloads.maemo.nokia.com ./ Release : The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AD4438160A55EF
W: You may want to run apt-get update to correct these problems.


Want can i do ?

Thank you.

eefo
2011-07-16, 17:52
Hi,
when i do a apt-get update , terminal say something like this:

W: GPG error: https://downloads.maemo.nokia.com ./ Release : The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AD4438160A55EF
W: You may want to run apt-get update to correct these problems.


Want can i do ?

Thank you.


yes the repository is down .
i am also facing this problem .
nothing to be worried .
just have some patience .

turbovomit
2011-07-16, 18:05
Ok, thank you very much.

StocChr
2011-07-16, 18:48
same problem here, we have only to wait?

Reading package lists... Done
W: GPG error: https://downloads.maemo.nokia.com ./ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ADB4438160A655EF
W: You may want to run apt-get update to correct these problems

peppino
2011-07-18, 17:00
Ok wait, but after 2 days it still down. Nokia has begun closing the maemo project?

zapotek
2011-07-18, 17:03
i have the same problem 1 month now :O!!

thopiekar
2011-07-18, 18:03
same problem here, we have only to wait?

Reading package lists... Done
W: GPG error: https://downloads.maemo.nokia.com ./ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ADB4438160A655EF
W: You may want to run apt-get update to correct these problems

The repository isn't down. There is simply a key missing in apt's keyring. You will need to add the key to the keyring to get a rid of this message.
However: All Nokia packages are available and installable..

romiiio
2011-07-18, 23:41
Hi i have the same problem so how do we add this key? Can we please have detailed how to guide please!

FranzDages
2011-07-19, 00:00
I noticed this myself a few days ago. Haven't tried since then, so I didn't know it was a continuing problem.

geneven
2011-07-19, 00:11
Can someone explain to me why they care about this error message?

peppino
2011-07-19, 19:47
The problem is only OVI repository I tried to comment

deb https://downloads.maemo.nokia.com/fremantle1.2/ovi/ ./

in /etc/apt/sources.list.d/hildon-application-manager.list and the problem disappear.
I tried to verify the signature of 3 Release file.


# gpg --no-default-keyring --keyring /etc/apt/trusted.gpg --secret-keyring /etc/apt/secring.gpg --verify Release.gpg_apps Release_apps
gpg: Signature made mer 2 feb 2011 12:42:31 CET using DSA key ID 13FA4ED6
gpg: Good signature from "Nokia repository signing key 4v1"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 1CC1 A2A2 B8CE 8F25 8F89 6B42 07C0 DFF7 13FA 4ED6

# gpg --no-default-keyring --keyring /etc/apt/trusted.gpg --secret-keyring /etc/apt/secring.gpg --verify Release.gpg_mr0 Release_mr0
gpg: Signature made lun 25 ott 2010 11:42:40 CEST using DSA key ID 13FA4ED6
gpg: Good signature from "Nokia repository signing key 4v1"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 1CC1 A2A2 B8CE 8F25 8F89 6B42 07C0 DFF7 13FA 4ED6

but ovi Release file I have


# gpg --no-default-keyring --keyring /etc/apt/trusted.gpg --secret-keyring /etc/apt/secring.gpg --verify Release.gpg_ovi Release_ovi
gpg: Signature made mar 19 lug 2011 00:05:36 CEST using RSA key ID 60A655EF
gpg: Can't check signature: public key not found

Nokia forget to release the public key 60A655EF.
In my apt-key list i have these keys:

# apt-key list
/etc/apt/trusted.gpg
--------------------
pub 1024D/C8009E74 2007-10-05 [expires: 2012-10-03]
uid Nokia repository signing key 1v1
sub 2048g/C1B723AA 2007-10-05 [expires: 2012-10-03]

pub 1024D/7C4B240D 2007-10-05 [expires: 2012-10-03]
uid Nokia repository signing key 1v2
sub 2048g/0580E9EB 2007-10-05 [expires: 2012-10-03]

pub 1024D/32009917 2007-10-05 [expires: 2012-10-03]
uid Nokia repository signing key 2v1
sub 2048g/1F2E958F 2007-10-05 [expires: 2012-10-03]

pub 1024D/E1448911 2007-10-05 [expires: 2012-10-03]
uid Nokia repository signing key 2v2
sub 2048g/EE0B0D1A 2007-10-05 [expires: 2012-10-03]

pub 1024D/413DA5CA 2007-10-05 [expires: 2012-10-03]
uid Nokia repository signing key 3v1
sub 2048g/4D5BEEF4 2007-10-05 [expires: 2012-10-03]

pub 1024D/EC9627ED 2007-10-05 [expires: 2012-10-03]
uid Nokia repository signing key 3v2
sub 2048g/0E39BF83 2007-10-05 [expires: 2012-10-03]

pub 1024D/13FA4ED6 2007-10-05 [expires: 2012-10-03]
uid Nokia repository signing key 4v1
sub 2048g/8B1115B2 2007-10-05 [expires: 2012-10-03]

pub 1024D/4C36F0B6 2007-10-05 [expires: 2012-10-03]
uid Nokia repository signing key 4v2
sub 2048g/3CF7720A 2007-10-05 [expires: 2012-10-03]

pub 2048R/616730BD 2009-07-27
uid maemo.org Extras repositories (Fremantle Extras) <repositories@maemo.org>

pub 1024D/4510B055 2009-03-18
uid MaemoSW Admin <admin@maemo.research.nokia.com>
sub 2048g/F18168D7 2009-03-18

pub 1024D/FF445C24 2009-03-16
uid Mozilla Release Engineering <release@mozilla.com>


Sorry for the paranoid.

romiiio
2011-07-19, 21:57
Sorry for being a noob could you please explain in detail how to get rid of this problem please!

Rob1n
2011-07-20, 09:50
Sorry for being a noob could you please explain in detail how to get rid of this problem please!

Find someone at Nokia and ask them to release the public key (though if it's not certified in any way then it's no more secure really - it probably ought to be certified with one the old keys), or just ignore the warning as it doesn't actually stop anything from working.

lilikandrian
2011-07-31, 19:58
YEAH...I Have this problem too... :(

Bramji
2011-07-31, 20:02
oke, disable all repos. refresh ham, enable all repos, refresh. It worked for me!

lilikandrian
2011-08-06, 23:50
oke, disable all repos. refresh ham, enable all repos, refresh. It worked for me!

yes its work when I use from HAM, but when I update from xTrm I steal get error.

prankster
2011-08-25, 11:30
as far as i know this issue has been raised in past in 2010 and now here it comes again in 2011,i wonder when it gets over ?this public key issue .
cant update right through x-terminal.it has been almost a month or so ,dev's isnt there any method been evolved to handle this ?

Rob1n
2011-08-25, 12:43
as far as i know this issue has been raised in past in 2010 and now here it comes again in 2011,i wonder when it gets over ?this public key issue .
cant update right through x-terminal.it has been almost a month or so ,dev's isnt there any method been evolved to handle this ?

The public key issue has absolutely zero effect on whether or not you can update anything. That's why it's a WARNING, not an ERROR.

sehrz
2011-09-01, 09:14
i have disable this repository and now update work ok, but will that be reapired or not !?

Rob1n
2011-09-01, 09:41
i have disable this repository and now update work ok, but will that be reapired or not !?

I doubt it will be fixed, no, but as it doesn't actually prevent anything from working then there's no major issue.

Herbert_86
2011-10-24, 00:19
Nobody knows about this problem?

michaaa62
2011-10-24, 06:37
http://talk.maemo.org/showpost.php?p=1109501&postcount=2