解决GPG error: The following signatures couldn't be verified because the public key is not available
来源:互联网 发布:配置网络 ubuntu 编辑:程序博客网 时间:2024/05/01 06:06
因为公司同事写的新脚本里使用了git v1.8 以后才有命令参数,这个参数在git v1.7版本上是没有的,而我们的Ubuntu 10.04的package 源里最新的git-core 就是1.7.xx,需要升级git的话需要添加新的git 源到/etc/apt/sources.list:
deb http://ppa.launchpad.net/git-core/ppa/ubuntu lucid main
deb-src http://ppa.launchpad.net/git-core/ppa/ubuntu lucid main
注:以上只适用Ubuntu10.04
然后执行:
$ sudo apt-get update
有错误:
W: GPG error: http://ppa.launchpad.net lucid Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A1715D88E1DF1F24
Google 之,在这篇文档里有提到解决方案:
http://muzso.hu/2007/05/25/how-to-fix-no_pubkey-errors-in-apt-get-update-operations
具体的解决方法步骤是(注意下面的KEY 是根据每次报错而不同的,可能需要用实际报错的KEY替换命令中的KEY值):
$ sudo gpg --keyserver keyserver.ubuntu.com --recv A1715D88E1DF1F24
$ sudo gpg --export --armor A1715D88E1DF1F24 | sudo apt-key add -
注:上面第二个命令中的第二个sudo,因为sudo不能跨越Pipe,所以第二个命令也需要使用sudo
接着执行:
$ sudo apt-get update
不会再报错了;接着安装git-core:
$ sudo apt-get install git-core
注:在执行上面这条命令时有可能没有能够升级git,可以试试先删除然后重新安装的方法,看能否解决:
$ sudo apt-get remove git
$ sudo apt-get install git-core
- 解决GPG error: The following signatures couldn't be verified because the public key is not available
- The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 010
- The following signatures couldn't be verified because the public key is not available
- The following signatures couldn't be verified because the public key is not available
- The following signatures couldn't be verified because the public key is not available
- 修复debian:The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 010908312D230C5F
- ubuntu14.04 报错 The following signatures couldn't be verified because the public key is not available
- 修复 apt-get update “the following signatures couldn’t be verified because the public key is not avai
- Fix apt-get update “the following signatures couldn’t be verified because the public key is not avai
- apt-get couldn't be verified because the public key is not available: NO_PUBKEY XXX
- W: GPG error: http://apt.postgresql.org lucid-pgdg Release: The following signatures couldn't be ver
- W: There is no public key available for the following key IDs, E: Couldn't rebuild package cache
- W: GPG error: http://dl.google.com/linux/chrome/deb stable Release: The following signatures couldn'
- error: couldn't parse contents of '/Users/.../Info.plist': The data couldn’t be read because...
- error: couldn't parse contents of '/Users/.../Info.plist': The data couldn’t be read because...
- W: There is no public key available for the following key IDs: 3B4FE6ACC0B21F32
- Coroutine couldn't be started because the the game object 'GameController' is inactive!
- The animation state could not be played because it couldn't be found!
- 【Cracking the coding interview】Q1.1(字符唯一)
- Unity屏幕渲染技术
- Oracle中出现Ora-00054该怎么处理,V$locked_object和V$session的用法
- TS流的基本概念
- secureCRT下的串口不能输入
- 解决GPG error: The following signatures couldn't be verified because the public key is not available
- Ubuntu下使用Mysql
- 黑马程序员_多态性
- 开发者所需要知道的iOS7 SDK新特性
- 创建一个进程来执行另一个程序
- Mysql查询按照某字段指定顺序排序
- nginx做静态文件下载服务器
- 获取正在运行的桌面包名
- js数据验证