Upgrade flags do not work

[aniqueta]

Describe the bug

Since I do not have the restic binary in /usr/local/bin, but instead in /opt/restic, I'm trying to use the autorestic upgrade function, and that does not work. Instead I receive the following error:

restic already installed
Fatal: output path /usr/local/bin/restic is not a normal file, use --output to specify a different file path

Error: exit status 1
cannot lock before reading config location

To workaround, I'm trying the --restic-bin flag to specify the /opt/restic location. This does not work with autorestic. It produces the same error above. Passing a binary path does work when using restic self-update --output directly. This suggests that the --restic-bin flag is not being correctly passed to restic.

To workaround, I'm trying to disable the restic update using --restic false but that also does not work. This means that the upgrade process is stopped mid-way, and the upgrade process doesn't move on to update autorestic even if it cannot update restic.

Expected behavior

autorestic is able to handle the --restic-bin and --restic flags appropriately.

Perhaps even better would be that it's smart enough to know where the restic binary is and automatically configures the path for updates.

Environment

• OS: macOS 12.3.1
• Version: 1.5.8