Skip to content

Avoid Windows mtime restore in bundled builds#766

Merged
mlafeldt merged 1 commit into
mainfrom
fix/windows-bundled-archive-mtime
May 22, 2026
Merged

Avoid Windows mtime restore in bundled builds#766
mlafeldt merged 1 commit into
mainfrom
fix/windows-bundled-archive-mtime

Conversation

@mlafeldt

Copy link
Copy Markdown
Member

The reproducible source archive previously used Unix epoch mtimes. On Windows targets backed by FAT/FAT32, restoring that timestamp can fail because those filesystems cannot represent Unix epoch times.

Fixes #764

Tested with and without the fix in CI: https://github.com/duckdb/duckdb-rs/actions/runs/26278548238

The reproducible source archive previously used Unix epoch mtimes. On
Windows targets backed by FAT/FAT32, restoring that timestamp can fail
because those filesystems cannot represent Unix epoch times. That surfaces
as SetFileTime ERROR_INVALID_PARAMETER during tar unpacking.

Do not preserve archive mtimes when unpacking bundled sources, and keep
generated archive mtimes at 2000-01-01 so the artifact remains
deterministic and filesystem-compatible.
@mlafeldt mlafeldt added the build label May 22, 2026
@mlafeldt mlafeldt self-assigned this May 22, 2026
@mlafeldt mlafeldt merged commit 2f11774 into main May 22, 2026
7 checks passed
@mlafeldt mlafeldt deleted the fix/windows-bundled-archive-mtime branch May 22, 2026 10:02
mlafeldt added a commit that referenced this pull request May 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

error: failed to run custom build command for libduckdb-sys v1.10503.0

1 participant