register openkal-musl 0.19.1 - #460
Merged
Merged
Conversation
Registration only: nothing here pins it yet. openkal-llvm-runtime names 0.19.0 exactly, and moving that pin is a separate change. 0.19.1 moves its own openkal-windows pin to 0.10.1, which makes a file opened for writing describable. `do_fstat` calls `okm_fs_file_info` and maps its error, so before it, `fstat` on a descriptor the caller opened a line earlier returned EACCES on Windows -- the pair libarchive performs when opening an archive for output. All four urls this and the previous registration add were fetched before this entry was written, not merely linted for shape: both hosts serve 0.19.1 at 1152093 bytes and 0.10.1 at 89854, and each CN copy is byte-for-byte identical to its GitHub archive. The CN url was written wrong once and caught by reading it back: a piecewise substitution replaced the file name before the directory pattern could match and produced `download/0.19.0/openkal-musl-0.19.1.tar.gz`, which serves nothing. The version is now replaced wholesale within each block, because the key, the GLOBAL tag, and both halves of the CN url name one version and have to move together.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Registration only — nothing here pins it yet.
openkal-llvm-runtimenames0.19.0exactly, and moving that pin is a separate change.0.19.1moves its ownopenkal-windowspin to0.10.1, which makes a file opened for writing describable.do_fstatcallsokm_fs_file_infoand maps its error, so before it,fstaton a descriptor the caller opened a line earlier returnedEACCESon Windows — the pair libarchive performs when opening an archive for output.Every url added by this and #459 was fetched, not merely linted for shape:
github.com/…/openkal-musl/archive/refs/tags/0.19.1.tar.gzgitcode.com/mcpp-res/openkal-musl/…/openkal-musl-0.19.1.tar.gzgithub.com/…/openkal-windows/archive/refs/tags/0.10.1.tar.gzgitcode.com/mcpp-res/openkal-windows/…/openkal-windows-0.10.1.tar.gzEach CN copy is byte-for-byte identical to its GitHub archive, and both were uploaded from a CN host with
gtc.That check earned its keep: the CN url was written wrong once. A piecewise substitution replaced the file name before the directory pattern could match, producing
download/0.19.0/openkal-musl-0.19.1.tar.gz— correct in shape, 404 in fact. The version is now replaced wholesale within each block, because the key, the GLOBAL tag and both halves of the CN url name one version and have to move together.