Move to openkal-musl 0.5.0 - #1
Merged
Merged
Conversation
This package was pinned to 0.3.1 --- a caret on a 0.x version bounds it below the next minor, so it has been resolving 0.3.x while the C library released 0.4.0 and now 0.5.0. Ninety-seven utilities above a C library two minors behind the one everything else in this ecosystem builds against is a consumer that is no longer testing the ecosystem. 0.5.0 routes the socket, datagram, readiness and image-copying families onto the interfaces openkal 0.8 added. Several of these utilities reach for `fork' and for `select' through musl's own sources; whether they now do more than they did is what this run answers.
The manifest changed and the version did not, so the index entry for 0.1.1 would keep serving a tarball whose manifest names openkal-musl 0.3.1 --- a package that resolves, builds, and tests a C library two minors behind the one this repository is now written against.⚠️ Nothing would have failed. That is the reason for the bump: a stale entry in an index is not a broken entry, it is a truthful-looking one.
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
2 participants
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.
This package was pinned to
openkal-musl = "0.3.1". A caret on a0.xversionbounds it below the next minor, so it has been resolving 0.3.x while the C
library released 0.4.0 and now 0.5.0.
Ninety-seven utilities above a C library two minors behind the one everything
else in this ecosystem builds against is a consumer that is no longer testing
the ecosystem.
0.5.0 routes the socket, datagram, readiness and image-copying families onto the
interfaces openkal 0.8 added. Several of these utilities reach for
forkandfor
selectthrough musl's own sources; whether they now do more than theydid is what this run answers, and it is the reason this repository is part of
the change rather than a follow-up to it.
This is one change across seven repositories, and every branch carries the
same name. Each repository's continuous integration substitutes its siblings'
working trees taken from the branch of the name under test, so the graph only
holds together when they agree.
openkal-muslopenkal-macosopenkal-windowsopenkal.spacedeclined in termsopenkal-linuxopenkal-llvm-runtime__config_site's claims asserted by a program, and the C library repinnedopenkalsbaseThe specification does not change. No interface was added, none was altered,
and
SURFACE.txtis untouched — every capability below is composed from atomsopenkal 0.8 already had.