sarman/tftsr-devops_investigation
1
1
Fork 0
Code Issues 4 Pull Requests Actions 34 Packages Projects 3 Releases 6 Wiki Activity

fix(ci): unset SODIUM_USE_PKG_CONFIG and use SODIUM_LIB_DIR in auto-tag.yml #111

Merged
sarman merged 1 commits from fix/unset-sodium-pkg-config-master into master 2026-06-18 01:14:16 +00:00
Conversation 0 Commits 1 Files Changed 1 +6 -3
sarman commented 2026-06-18 01:12:57 +00:00
Owner
Copy Link

Problem

Same root cause as the beta fix (#110): the runner environment at 172.0.0.29 has SODIUM_USE_PKG_CONFIG set, which conflicts with SODIUM_LIB_DIR (used for Windows cross-compile) causing an immediate panic in libsodium-sys-stable.

Master was accidentally less visible because Linux builds used apt-get install libsodium-dev + the ambient SODIUM_USE_PKG_CONFIG would trigger pkg-config (finding the just-installed package). Windows was still broken.

Fix

  • All three platform build steps in auto-tag.yml now unset SODIUM_USE_PKG_CONFIG before running cargo
  • Linux builds (amd64 + arm64) switched from inline apt-get install libsodium-dev to SODIUM_LIB_DIR — the Docker images already include libsodium-dev, removing the redundant install step
  • arm64 PKG_CONFIG_PATH extended to match beta workflow

Aligns master with beta for consistent, deterministic sodium linking across all platforms.

## Problem Same root cause as the beta fix (#110): the runner environment at `172.0.0.29` has `SODIUM_USE_PKG_CONFIG` set, which conflicts with `SODIUM_LIB_DIR` (used for Windows cross-compile) causing an immediate panic in `libsodium-sys-stable`. Master was accidentally less visible because Linux builds used `apt-get install libsodium-dev` + the ambient `SODIUM_USE_PKG_CONFIG` would trigger pkg-config (finding the just-installed package). Windows was still broken. ## Fix - All three platform build steps in `auto-tag.yml` now `unset SODIUM_USE_PKG_CONFIG` before running cargo - Linux builds (amd64 + arm64) switched from inline `apt-get install libsodium-dev` to `SODIUM_LIB_DIR` — the Docker images already include `libsodium-dev`, removing the redundant install step - arm64 `PKG_CONFIG_PATH` extended to match beta workflow Aligns master with beta for consistent, deterministic sodium linking across all platforms.
sarman added 1 commit 2026-06-18 01:12:59 +00:00
fix(ci): unset SODIUM_USE_PKG_CONFIG and use SODIUM_LIB_DIR in auto-tag.yml
Some checks failed
PR Review Automation / review (pull_request) Has been cancelled
Details
Test / rust-tests (pull_request) Has been cancelled
Details
Test / frontend-typecheck (pull_request) Has been cancelled
Details
Test / frontend-tests (pull_request) Has been cancelled
Details
Test / rust-clippy (pull_request) Has been cancelled
Details
Test / rust-fmt-check (pull_request) Has been cancelled
Details
a15e69413a 
The libsodium-sys-stable build.rs panics when both SODIUM_LIB_DIR and
SODIUM_USE_PKG_CONFIG are set simultaneously. The runner environment at
172.0.0.29 has SODIUM_USE_PKG_CONFIG set (not traceable to any workflow
file or Docker image ENV layer), which conflicts with any step that sets
SODIUM_LIB_DIR.

For all three platform builds (linux-amd64, windows-amd64, linux-arm64):
- Add `unset SODIUM_USE_PKG_CONFIG` to the shell before cargo runs
- Switch Linux builds from inline apt-get to SODIUM_LIB_DIR (Docker
  images already include libsodium-dev, removing the redundant install)
- Extend arm64 PKG_CONFIG_PATH to include /usr/aarch64-linux-gnu/lib/pkgconfig
  (matching the beta workflow for consistency)

The unset is a no-op when the variable is absent; it cleanly clears any
ambient value injected by the runner infrastructure.
sarman merged commit df833e8464 into master 2026-06-18 01:14:16 +00:00
sarman deleted branch fix/unset-sodium-pkg-config-master 2026-06-18 01:14:17 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
Compat/Breaking

Breaking change that won't be backward compatible

  
Kind/Bug

Something is not working

  
Kind/Documentation

Documentation changes

  
Kind/Enhancement

Improve existing functionality

  
Kind/Feature

New functionality

  
Kind/Security

This is security issue

  
Kind/Testing

Issue or pull request related to testing

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No Label
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sarman/tftsr-devops_investigation#111
No description provided.
Delete Branch "fix/unset-sodium-pkg-config-master"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?