Skip to content

Vendor nc's base64.c instead of fetching it - #30

Merged
mosajjal merged 1 commit into
masterfrom
fix/nc-vendor-base64
Sep 2, 2026
Merged

mosajjal merged 1 commit into
masterfrom
fix/nc-vendor-base64

Conversation

@mosajjal

@mosajjal mosajjal commented Sep 2, 2026

Copy link
Copy Markdown
Owner

Second CI-only failure on the same build: the runner could not reach
gitlab.alpinelinux.org, where base64.c and b64.patch were being fetched from.

curl: (28) Failed to connect to gitlab.alpinelinux.org port 443 after 132505 ms

base64.c (ISC, from BIND, unchanged) now lives in build/nc/ and is copied into the
build. The one-line prototype b64.patch supplied is a sed instead, so there is no
patch file to carry.

Recipes gained a files key for this — sources that belong next to the Dockerfile
rather than behind someone else's uptime.

Rebuilt clean locally: x64 and ARM both static, both smoke tests passing.

🤖 Generated with Claude Code

The runner could not reach the distro git host the file came from, so
the build failed there twice while passing locally. base64.c now lives
in build/nc/ and is copied in; the one-line prototype the patch supplied
is a sed instead.

Recipes gained a "files" key for this: sources that belong next to the
Dockerfile rather than behind someone else's uptime.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@mosajjal
mosajjal force-pushed the fix/nc-vendor-base64 branch from 6cdc796 to be54966 Compare September 2, 2026 10:08
@mosajjal
mosajjal merged commit a26d023 into master Sep 2, 2026
1 check passed
@mosajjal
mosajjal deleted the fix/nc-vendor-base64 branch September 2, 2026 10:10
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