Skip to content

use --no-same-owner to fix tar errors #1002

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ipetkov merged 2 commits into from
Apr 3, 2026
+7 −1
Merged

use --no-same-owner to fix tar errors #1002

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c1528a0
use --no-same-owner to fix tar errors
kybe236 Mar 28, 2026
f86354a
Update CHANGELOG
ipetkov Apr 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,12 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.

## Unreleased

### Changed
* `downloadCargoPackage` now extracts tarballs with `--no-same-owner`.
Ultimately this should make no difference since the Nix store will reset all
ownership permissions anyway, but it may avoid some spurious errors on certain
systems.

## [0.23.2] - 2026-03-23

### Added
Expand Down
2 changes: 1 addition & 1 deletion lib/downloadCargoPackage.nix
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ stdenv.mkDerivation {
unpackPhase = ''
runHook preUnpack
mkdir -p crate
tar -xzf ${tarball} -C crate --strip-components=1
tar -xzf ${tarball} -C crate --strip-components=1 --no-same-owner
runHook postUnpack
'';

Expand Down