NIXTAMAL-LOCK(1)

πŸ“¦ version 2.4.0, in nixpkgs unstable

nixtamal-lock(1) β€” lock all not-yet-locked inputs πŸ’…

Okay so bestie, welcome to NIXTAMAL-LOCK(1) β€” the manual page for nixtamal-lock, and it is literally here to lock all your not-yet-locked inputs. Main character energy only. ✨


πŸ’– NAME πŸ’–

nixtamal-lock β€” Lock all not-yet-locked inputs.

That’s the whole vibe: if an input isn’t locked yet, this command locks it. Periodt. πŸŽ€

✨ SYNOPSIS ✨

nixtamal lock [OPTION]… [INPUT_NAME]…

πŸŽ€ LICENSE πŸŽ€

GNU General Public License, version 3.0 later (GPL-3.0-or-later)

πŸ¦‹ MAKER πŸ¦‹

toastal <https://toast.al/contact/>

🌸 FUNDING 🌸

See: https://toast.al/funding/

🧚 ARGUMENTS 🧚

  • INPUT_NAME β€” Input names to lock (if already locked, will skip). Lowkey efficient, no cap. πŸ’…

πŸ’… OPTIONS πŸ’…

  • --color=WHEN (absent=auto or NIXTAMAL_OUTPUT_COLOR env) β€” Colorize the output. WHEN must be one of auto, always or never.
  • --directory=PATH (absent NIXTAMAL_DIRECTORY env) β€” Working directory for Nixtamal-related files (default: $PWD/nix/tamal).
  • -f, --force β€” Force input to lock. Useful if you’re changing the manifest in a manner that otherwise wouldn’t trigger a lock, such as changing a URL or hash algorithm. Fr fr, sometimes you gotta make it happen. πŸ”₯
  • -j INT, --jobs=INT (absent=80 or NIXTAMAL_JOBS env) β€” Nixtamal’s executor pool domain size.
  • --no-tui β€” Disable the TUI & use Logs.app for status output.
  • -p PATCH_NAME, --patch=PATCH_NAME β€” Patch name(s) to lock (if already locked, will skip).
  • -q, --quiet β€” Be quiet. Takes over -v and --verbosity.
  • --relock β€” Alias for --force.
  • --skip-patch-check (absent NIXTAMAL_SKIP_PATCH_CHECK env) β€” Skip checking that patches apply. Faster & works offline, but broken patches lock silently & fail at build instead. > 🚨 Bestie, that caveat is real: silent broken patch now, build-time chaos later. πŸ™ˆ
  • -v, --verbose β€” Increase verbosity. Repeatable, but more than twice does not bring more.
  • --verbosity=LEVEL (absent=warning or NIXTAMAL_LOG_LEVEL env) β€” Be more or less verbose. LEVEL must be one of quiet, error, warning, info or debug. Takes over -v.

πŸ‘‘ COMMON OPTIONS πŸ‘‘

  • --help[=FMT] (default=auto) β€” Show this help in format FMT. The value FMT must be one of auto, pager, groff or plain. With auto, the format is pager or plain whenever the TERM env var is dumb or undefined.
  • --version β€” Show version information.

🌈 EXIT STATUS 🌈

nixtamal lock exits with:

  • 0 β€” on success.
  • 65 β€” Nixtamal working directory or manifest not set up. Run nixtamal set-up.
  • 66 β€” Version mismatch between manifest and lockfile. Run nixtamal lock, but might require removing the lockfile first until nixtaml fast-forward is made.
  • 67 β€” Manifest ∨ lockfile is not using the latest schema version. Run nixtamal upgrade to upgrade.
  • 68 β€” Failed to parse the manifest file.
  • 69 β€” Failed to parse the lockfile.
  • 70 β€” Failed to serialize lockfile.
  • 71 β€” Fresh command execution threw an exception.
  • 72 β€” Fresh command output nothing.
  • 73 β€” Prefetch command threw an exception.
  • 74 β€” Prefetch command output was unusable.
  • 75 β€” Prefetch command flopped on JSON output.
  • 76 β€” Darcs context file is missing or invalid. Try running nixtamal lock on the input.
  • 77 β€” Vendored patch file is missing. Try running nixtamal lock to fetch it.
  • 78 β€” Silo error (such as bad hex in generation number).
  • 79 β€” Version not found or invalid in manifest file.
  • 80 β€” Upgrading Nixtamal failed.
  • 81 β€” BLAKE3 hash algorithm is requested but this Nix doesn’t support it.
  • 82 β€” Input kind mismatch between manifest & lockfile which prevents values to be melded.
  • 83 β€” Blueprint scaffolding failed to write files.
  • 84 β€” A patch failed to apply.
  • 85 β€” An input references patches that are not defined in the manifest.
  • 123 β€” on indiscriminate errors reported on standard error.
  • 124 β€” on command line parsing errors.
  • 125 β€” on unexpected internal errors (bugs).

🫢 ENVIRONMENT 🫢

These environment variables affect the execution of nixtamal lock:

  • NIXTAMAL_DIRECTORY β€” Directory for Nixtamal
  • NIXTAMAL_JOBS β€” See option --jobs.
  • NIXTAMAL_LOG_LEVEL β€” See option --verbosity.
  • NIXTAMAL_OUTPUT_COLOR β€” See option --color.
  • NIXTAMAL_SKIP_PATCH_CHECK β€” See option --skip-patch-check.

πŸ’€ BUGS πŸ’€

No tracker is set up; contact the maker directly or join the XMPP chatroom @ <xmpp:nixtamal@chat.toastal.in.th?join>.

⭐ SEE ALSO ⭐


πŸ’– That’s the whole page, bestie β€” Nixtamal 2.4.0, NIXTAMAL-LOCK(1), and the original footer didn’t print a date, so no fake date, just this cute sign-off. Periodt. πŸŽ€

πŸ“¦ where this page comes from