Skip to content

[Installer] bootstrap.sh fails with "fatal: not in a git directory" when GIT_DIR is set in the environment #23

Description

@qw12po09

Install method

bootstrap.sh / build from source (ran install.sh, then separately tried what the reporter called "the app data version")

Platform

Linux (CachyOS)

Updating from version

Not stated; appears to be a fresh install.

Installing or updating to version

Vintage Story 1.22.7 (the version bootstrap.sh --version 1.22.7 downloads). The Optimum package version itself is not stated; the reporter describes it as "the newest version" as of 2026-08-22.

Steps taken

First attempt: ran install.sh on CachyOS Linux.

Second attempt: tried what the reporter called "the app data version," which also failed with the same error.

Where it stopped

Both attempts stopped during the repository refresh, immediately after cloning VintagestoryApi.

Full error output or log

First attempt:

fatal: not in a git directory
make[1]: *** [Makefile:62: bootstrap] Error 128
make[1]: Leaving directory '/mnt/zoomin/Vintage Story/optimum'
make: *** [Makefile:65: build] Error 2

install.sh attempt:

==> Building Optimum...
bash scripts/bootstrap.sh --refresh --version 1.22.7
Downloading https://cdn.vintagestory.at/gamefiles/stable/vs_client_linux-x64_1.22.7.tar.gz
  % Total    % Received % Xferd  Average Speed  Time    Time    Time   Current
                                 Dload  Upload  Total   Spent   Left   Speed
100 590.5M 100 590.5M   0      0 30.29M      0   00:19   00:19         30.79M
Extracting /mnt/zoomin/Vintage Story/Waxlight/optimum/Optimum-0.3.13/.vanilla/archives/vs_client_linux-x64_1.22.7.tar.gz
Decompiling VintagestoryLib.dll with ilspycmd: 10.1.1.8388
Decompiling Vintagestory.dll with ilspycmd: 10.1.1.8388
Cloning VintagestoryApi at 63d33f70018c606fb0f70ead900fe90625fbd7b2
fatal: not in a git directory
make: *** [Makefile:73: refresh] Error 128

Checks

  • I read the Building from Source wiki page for my platform. Not stated.

Investigation notes

The maintainer noted a related Mod DB report of the same fatal: not in a git directory pattern in an older Optimum package (comment #196668), where the cause traced to using a downloaded ZIP instead of a Git clone during a later git add -f ... step. Not confirmed as the same cause here; worth checking whether the failing optimum/ source directory is a Git worktree and whether this install was extracted from an archive.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugIncorrect behaviorbuildBootstrap, compile, patch, or .NET toolinginstallerInstall, packaging, or bootstraplinuxLinux-specific

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions