Skip to content

the record says the mirror defect was repaired, and what the repair turned up - #41

Merged
Sunrisepeak merged 2 commits into
mainfrom
docs/mirror-repair-record
Sep 20, 2026
Merged

Sunrisepeak merged 2 commits into
mainfrom
docs/mirror-repair-record

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

接 mcpp-index#443:仓库所有者在 GitCode 侧删除了那两个资产之后,缺陷已经修在源头(无前缀标签 + GitHub archive 原样上传 + 描述符写同一个文件的哈希),本记录的 §5.1 与末尾的限制列表随之改写。

顺带记下修的过程中 index 自己的 CN 检查抓到的第三处:openkal-llvm-runtime 0.1.1 的 GitCode 资产也不在了,用 GitHub 同标签的 archive 补回(哈希正是描述符原本写的 d3c460e0…,描述符未动)。随后把九个 openkal 包的 135 条 CN 地址全扫一遍,全部 200。

…urned up

The owner removed the two GitCode assets, which was the precondition gtc
cannot supply, so the two versions are now published the way every other one
here is: a plain tag, that tag's GitHub archive on both mirrors, one sha256.
While repairing it the index's own CN check found a third asset missing ---
openkal-llvm-runtime 0.1.1 --- restored from the archive whose hash the
descriptor already named. All 135 CN urls of the openkal packages answer.
…only from the trees

Sixteen manifests, one line changed --- openkal-llvm-runtime = "0.12.0" ---
and the same two observations hold: what is typed reaches the program, and the
interrupt keystroke does not end it. That is the whole of what a consumer does.
@Sunrisepeak
Sunrisepeak merged commit cfb2193 into main Sep 20, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant