Fetch zlib from its own releases - #874
Open
MayCXC wants to merge 1 commit into
Open
Conversation
Every dependency this script fetches comes from a GitHub release page except zlib, which came from zlib.net, and a build dies whenever that one host does. zlib publishes the same release tarballs on its own GitHub repository, so the fetch joins the others on infrastructure that answers.
MayCXC
force-pushed
the
dev-image-zlib-fetch
branch
from
August 27, 2026 20:47
e154eff to
bb03e8a
Compare
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.
Summary
Every dependency this script fetches comes from a GitHub release page except zlib, which came from
zlib.net, and a build dies whenever that one host does. zlib publishes the same release tarballs on its own GitHub repository, so the fetch joins the others on infrastructure that answers.Motivation and Context
The x86_64 dependency build has one host in it that the others do not depend on, and it fails often enough to notice. The tarballs are the same artifacts published by the same project, so this is a change of mirror rather than of source.
Testing
make dist-x86_64's dependency step fetches and builds zlib from the new location.Type of Change