Troubleshooting

What to do when lnk doesn't install, or a plugin won't install or update (Install, Plugins).

Installing

The installer checks the release's signature before it puts lnk in place, so most of what goes wrong is that check or the PATH.

lnk: command not found after installing

Add ~/.lnk/bin to your PATH: the installer leaves your shell's settings alone, and prints the line to add.

"ssh-keygen (OpenSSH) is needed to check the release signature"

Install OpenSSH 8.1 or newer, or set LNK_INSECURE=1 to install without checking the signature.

"the release signature did not verify"

Check ssh -V is 8.1 or newer. If it is, don't install, and report it (Report a Vulnerability).

Plugins

A plugin installs when a command needs it, so most of what goes wrong is a plugin lnk can't take, or one installed another way.

A command says its plugin isn't installed

Run lnk plugin add <plugin>. Typed, lnk installs it itself: this is a plugin's call underneath, or you said no.

"a standalone program is not an installable plugin"

Only a plugin lnk runs is added from outside Link: its lnk-<name> answers --link-describe as a plugin, never as a program of its own.

A plugin from outside Link "not upgraded: ... doesn't trust"

Its release is signed by another key. If its maker says they changed keys, lnk plugin remove <name>, then add it again.

"The plugin at ... isn't in lnk's folder"

lnk plugin remove removes only what's in lnk's folder, and leaves one on your PATH to you: remove it the way you installed it.