Troubleshooting FAQ

Welcome to the troubleshooting FAQ! If you do not find an answer to your question, feel free to open an issue on the issue tracker or reach out via email to anyone in the core team.

There’s no repobee command in my shell

The most common cause of this issue is that the repobee executable is not on the path, but there could be other explaniations as well. First, try starting a new shell. You may even need to log out and log back in, depending on where you appendend to the PATH varible.

If starting a new shell or restarting logging out and back in does not resolve the issue, check if you have the ~/.repobee/bin directory on your PATH variable.

$ echo $PATH | grep -o "$HOME/.repobee/bin"

If you get no output, then the directory is not on your PATH. Before adding the bin directory to your path, you can check that the executable is actually present on your system.

Expected content in RepoBee’s bin directory
$ ls -l ~/.repobee/bin
lrwxrwxrwx 1 slarse slarse 37 Sep  2 14:37 repobee -> /home/slarse/.repobee/env/bin/repobee

If your output looks something like this, then you’ve got RepoBee installed. If it does not look like this (e.g. the symlink is dangling or the directory dous not exist), then you should try executing the installer again. Once you see the directory and a valid symlink, try directly executing the executable with a qualified path.

Executing RepoBee with a qualified path
$ ~/.repobee/bin/repobee -h
# help output should pop up here

If that works, all you need to do is to add the bin directory to your PATH. Where you should do that depends on what shell you use. For example, for bash you should typically put environment variables in ~/.profile, for zsh they typically go in ~/.zshenv, and for fish they go in ~/.config/fish/config/fish.

Example PATH configuration
# for bash, add this to your ~/.profile
export PATH="$PATH:$HOME/.repobee/bin"

# for zsh, add this to your ~/.zshenv
export PATH="$PATH:$HOME/.repobee/bin"

# for fish, add this to your ~/.config/fish/
set -x PATH "$PATH:$HOME/.repobee/bin"


With bash, the .profile file can be overridden by the ~/.bash_profile file.

Error message bad interpreter: No such file or directory”

This is typically caused by the system wide Python executable being upgraded or otherwise changed after installing RepoBee. To fix this, remove the ~/.repobee directory and then execute the installer again (see Install).

RepoBee crashes

First try to upgrade RepoBee to the latest version with repobee manage upgrade. If that does not resolve the issue, try uninstalling plugins one-by-one with repobee --no-plugins plugin uninstall until RepoBee works again. If that has no effect either, then you should remove the ~/.repobee directory and execute the installer again (see Install).