[Seek Help] 更新失败,出现这些代码解决 解决问题?
Tofloor
poster avatar
baorain74
deepin
2021-07-07 15:08
Author

更新失败,出现这些代码解决 解决问题?

 

$ sudo apt-get update && sudo apt-get upgrade

请输入密码:

验证成功

获取:1 https://community-packages.deepin.com/deepin apricot InRelease [19.6 kB]                              

获取:2 https://community-packages.deepin.com/printer eagle InRelease [5,232 B]                               

获取:4 http://dl.google.com/linux/chrome/deb stable InRelease [1,811 B]

错误:4 http://dl.google.com/linux/chrome/deb stable InRelease

  由于没有公钥,无法验证下列签名: NO_PUBKEY 78BD65473CB3BD13

命中:3 https://home-store-img.uniontech.com/appstore eagle InRelease                                         

正在读取软件包列表... 完成

W: GPG 错误:http://dl.google.com/linux/chrome/deb stable InRelease: 由于没有公钥,无法验证下列签名: NO_PUBKEY 78BD65473CB3BD13

E: 仓库 “http://dl.google.com/linux/chrome/deb stable InRelease” 没有数字签名。

N: 无法安全地用该源进行更新,所以默认禁用该源。

N: 参见 apt-secure(8) 手册以了解仓库创建和用户配置方面的细节。

 

Reply Favorite View the author
All Replies
忘记、过去
deepin
2021-07-07 16:42
#1

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 78BD65473CB3BD13

Reply View the author
Ziggy
deepin
2021-07-07 21:37
#2

屏蔽第三方源

Reply View the author
baorain74
deepin
2021-07-09 06:03
#3

cat /etc/apt/sources.list

## Generated by deepin-installer

deb https://community-packages.deepin.com/deepin/ apricot main contrib non-free

#deb-src https://community-packages.deepin.com/deepin/ apricot main contrib non-free

检查这些源,这是什么 意思?怎样屏蔽第三方源呢?

Reply View the author
baorain74
deepin
2021-07-09 15:05
#4
Ziggy

屏蔽第三方源

cat /etc/apt/sources.list

## Generated by deepin-installer

deb https://community-packages.deepin.com/deepin/ apricot main contrib non-free

#deb-src https://community-packages.deepin.com/deepin/ apricot main contrib non-free

检查这些源,这是什么 意思?怎样屏蔽第三方源呢?

Reply View the author
baorain74
deepin
2021-07-10 17:31
#5
Ziggy

屏蔽第三方源

版主你好,请问如何屏蔽第三方源???

Reply View the author
Ziggy
deepin
2021-07-11 00:38
#6
baorain74

版主你好,请问如何屏蔽第三方源???

到/etc/apt/sources.list.d/里删掉除appstore以外的文件夹即可

Reply View the author