Поиск в Поддержке

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

I'm got this error from apt-get on Maemo: "W: GPG error: http://moff.mozilla.com fremantle Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 667387BFFF445C24"

  • 3 ответа
  • 76 имеют эту проблему
  • 524 просмотра
  • Последний ответ от oKtosiTe

more options

I got to firefox.com/m, and it installed the source you see in the question, but it keep offering to install the 1.2 version of Firefox Mobile from the Ovi store. So, I got to the shell and did an apt-get update, an it did the error on the question.

Все ответы (3)

more options

Try the following commands: sudo gainroot gpg --keyserver pgpkeys.mit.edu --recv-key 667387BFFF445C24 gpg -a --export 667387BFFF445C24 | apt-key add - until the final "OK" display on your screen. Good luck!

more options

After decipher the command line you wrote, I did the importation of the key from the MIT server and added it to apt-key ring, as showing below:

Nokia-N900:~# gpg --keyserver pgpkeys.mit.edu --recv-key 667387BFFF445C24

gpg: directory `/root/.gnupg' created

gpg: can't open `/gnupg/options.skel': No such file or directory

gpg: keyring `/root/.gnupg/secring.gpg' created

gpg: keyring `/root/.gnupg/pubring.gpg' created

gpg: requesting key FF445C24 from hkp server pgpkeys.mit.edu

gpg: /root/.gnupg/trustdb.gpg: trustdb created

gpg: key FF445C24: public key "Mozilla Release Engineering <release@mozilla.com>" imported

gpg: Total number processed: 1

gpg: imported: 1

gpg: unchanged: 1

Nokia-N900:~# gpg -a --export 667387BFFF445C24 | apt-key add -


But, on apt-get update I got a new error:

W: Conflicting distribution: http://moff.mozilla.com fremantle Release (expected fremantle but got )

W: Failed to fetch http://moff.mozilla.com/latest/maemo/multi/dists/fremantle/Release Unable to find expected entry release/binary-armel/Packages in Meta-index file (malformed Release file?)

E: Some index files failed to download, they have been ignored, or old ones used instead.

Thank you for you answer, but, what now?

more options

I would like to add that after adding the key, updating the package lists fails more seriously, and I've had to disable the Mozilla repositories altogether for the time being in order to still receive other updates.