## TL;DR

Try removing the system gettext package (or otherwise getting it off the PATH for the subprocess) rather than debugging git itself. When an agent hits tool-subprocess failures that do not reproduce with the same command run manually, compare the subprocess environment's PATH against the interactive shell before assuming the tool is at fault. The host system had gettext 0.21 but the Meltano/uv subprocess environment was injecting a gettext 0.22.5 whose gettext.

## Fix

If meltano add fails in git submodule update with a gettext.sh usage error, the host's gettext installation is conflicting with the one the Meltano subprocess sees. Try removing the system gettext package (or otherwise getting it off the PATH for the subprocess) rather than debugging git itself. When an agent hits tool-subprocess failures that do not reproduce with the same command run manually, compare the subprocess environment's PATH against the interactive shell before assuming the tool is at fault.

Context: GitHub issue meltano/meltano#9701 (closed, 11 comments): meltano add failed during git submodule update with GNU gettext shell script function library version 0.22.5 / Usage: . gettext.sh. The host system had gettext 0.21 but the Meltano/uv subprocess environment was injecting a gettext 0.22.5 whose gettext.sh was incompatible with what git's scripts expected. Manual git clone and submodule updates worked fine outside Meltano. The maintainer's fix: uninstall gettext entirely from the environment, which resolved the conflict and let meltano add complete.

## Matched source
Source: Published skill
Original query: "Meltano add fails in git submodule update: remove conflicting gettext"
Key terms: conflicting, fails, gettext, meltano, remove, submodule, update

## When to use this

- Use this when your task, error, or question matches the title above and the setup in the Fix section.

## When not to use this

- Skip it when the error text, tool, or situation is different. Forcing a mismatched fix usually costs more time than searching again.

## Compatibility

The original write-up does not pin tool versions. Treat the commands and UI paths above as reflecting the author's setup, and check your tool's own docs if your version looks different.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_avcXh1auEPaZbDSx80cQmQ/versions/skv_BxHpxlQE6M3FcIyNde54yQ>
- Canonical HTML skill page: <https://vectle.com/skills/skl_avcXh1auEPaZbDSx80cQmQ>
- Current Markdown URL: <https://vectle.com/skills/skl_avcXh1auEPaZbDSx80cQmQ/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://github.com/meltano/meltano/issues/9701"
  ]
}
```