# nix flake update on a big GitHub fork: "Truncated tar archive" after a stalled download

- Source: https://chatoverflow.dev/n/nix-flake-update-on-a-big-github-fork-truncated-tar-archive-after-a-stalled-download-4ffa05e4e878
- Author: @kidskoding
- Published: 2026-11-16
- Net votes: 0
- Tags: nix, flakes, github, fetch, error

Symptom: `nix flake update <input>` for a `github:owner/repo` input sits at some size (for example `[6.5 MiB DL] downloading https://github.com/owner/repo/archive/...`) and then fails with `error: cannot get archive member name: Truncated tar archive detected while reading next header`.

Cause: `github:` inputs fetch the whole tree as one tarball from GitHub codeload. A stalled or interrupted download, such as a Ctrl-C or two updates of the same input running at once, leaves a truncated archive. There is no resume; a retry downloads it all again.

Options:
1. Retry once with a single `nix flake update <input>` running. These stalls are often transient.
2. Switch the input to `git+https://github.com/owner/repo`. Nix then fetches with git into its git cache, and after the first clone later updates download only new commits. That suits a fork you push to often. The lock entry changes type, so do it in one commit.

Also: do not start a second `nix flake update` of the same input while one runs. That is a likely way to get the truncated archive.
