时间戳

首页 > 解决方案 > build-simple-cdd 在 tmp/mirror/README 中校验和无效

shell - build-simple-cdd 在 tmp/mirror/README 中校验和无效

问题描述

我的工作机器是 Linux Debian Buster (10.0)。
我正在尝试从 root 帐户创建一个简单的 CDD iso：

使用的命令行：

build-simple-cdd --debug --dist buster --force-root

回复： 

2019-07-07 11:24:52,978 DEBUG Reading configuration...
gpg: directory '/root/.gnupg' created
gpg: /root/.gnupg/trustdb.gpg: trustdb created
2019-07-07 11:24:53,042 DEBUG Checking configuration...
2019-07-07 11:24:53,273 DEBUG Creating build environment in /root...
2019-07-07 11:24:53,378 DEBUG Building local Debian mirror for debian-cd...
2019-07-07 11:24:53,379 DEBUG downloading: /root/tmp/mirror/extrafiles
2019-07-07 11:24:53,867 DEBUG verify gpg signature running command gpg --batch --no-default-keyring --keyring /usr/share/keyrings/debian-archive-keyring.gpg --verify /root/tmp/mirror/extrafiles
2019-07-07 11:24:53,899 DEBUG verify gpg signature stderr: gpg: Signature made Sat 06 Jul 2019 04:34:24 AM CEST
2019-07-07 11:24:53,900 DEBUG verify gpg signature stderr: gpg:                using RSA key 126C0D24BD8A2942CC7DF8AC7638D0442B90D010
2019-07-07 11:24:53,911 DEBUG verify gpg signature stderr: gpg: Good signature from "Debian Archive Automatic Signing Key (8/jessie) <ftpmaster@debian.org>" [unknown]
2019-07-07 11:24:53,915 DEBUG verify gpg signature stderr: gpg: WARNING: This key is not certified with a trusted signature!
2019-07-07 11:24:53,915 DEBUG verify gpg signature stderr: gpg:          There is no indication that the signature belongs to the owner.
2019-07-07 11:24:53,916 DEBUG verify gpg signature stderr: Primary key fingerprint: 126C 0D24 BD8A 2942 CC7D  F8AC 7638 D044 2B90 D010
2019-07-07 11:24:53,917 DEBUG verify gpg signature retval: 0
2019-07-07 11:24:53,994 DEBUG downloading: /root/tmp/mirror/README
2019-07-07 11:24:54,462 ERROR Invalid checksum for /root/tmp/mirror/README: expected 463536fa7b9fd3800f1957f4fc5690ca8739e87efda85d81ae3b46306469da03, got 4e96e82b362f9b4d7a0670a3ec6b053d451db98a1df55471671b70170db7bc04

有什么线索？？？提前致谢...

标签： shelldebian

解决方案

我几乎可以肯定这与昨天更新到 10.0 有关。我能够通过编辑带有详细信息的自述文件，就好像它是 9.9（8.11 变旧并将 7.11 的详细信息查找为 oldold）来克服这个特定错误。但是，然后我得到了另一个文件的另一个校验和错误。

我只是等到比我更有能力的人更新cdd。

推荐阅读