安装时候选的163的源,安完了就这样

http://mirrors.163.com/debian/dists/stretch-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.https://repo.debiancn.org/dists/stable/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.冲突的发行版:https://repo.debiancn.org stable InRelease (期望 stable 但得到 stretch)http://mirrors.163.com/debian/dists/stretch-proposed-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.http://mirrors.163.com/debian/dists/stretch/Release.gpg: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.http://dl.google.com/linux/chrome/deb/dists/stable/Release.gpg: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.GPG 错误:http://dl.google.com/linux/chrome/deb stable Release: 由于没有公钥,无法验证下列签名: NO_PUBKEY 1397BC53640DB551仓库 “http://dl.google.com/linux/chrome/deb stable Release” 没有数字签名。无法安全地用该源进行更新,所以默认禁用该源。参见 apt-secure(8) 手册以了解仓库创建和用户配置方面的细节。http://security.debian.org/debian-security/dists/stretch/updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.

百度是缺少公钥,然而按照网上的解决方法结局是这样:
gpg --keyserver pgpkeys.mit.edu --recv-key 1397BC53640DB551
gpg: directory ‘/root/.gnupg’ created
gpg: keybox ‘/root/.gnupg/pubring.kbx’ created
gpg: failed to start the dirmngr ‘/usr/bin/dirmngr’: 没有那个文件或目录
gpg: connecting dirmngr at ‘/root/.gnupg/S.dirmngr’ failed: 没有那个文件或目录
gpg: keyserver receive failed: No dirmngr

安装了dirmng以后,是这样
root@zg:/home/zg# gpg --keyserver pgpkeys.mit.edu --recv-key 640DB551
gpg: key 7721F63BD38B4796: “Google Inc. (Linux Packages Signing Authority) linux-packages-keymaster@google.com” not changed
gpg: Total number processed: 1
gpg: unchanged: 1

建议先将 /etc/apt/trusted.gpg 文件备份后删除,之后再运行 apt update,对缺失的公钥重新使用 apt-key 导入。