Installer doesnt check for already existing update_manager entry #24
Assignees
Labels
bug
Something isn't working
Comments
KwadFan
added a commit
that referenced
this issue
Aug 13, 2022
Show default answers in case of user only hits enter. Includes fix: Install on rpi bullseye fails This also should fix #24 Signed-off-by: Stephan Wendel <[email protected]>
KwadFan
added a commit
that referenced
this issue
Aug 16, 2022
Show default answers in case of user only hits enter. Includes fix: Install on rpi bullseye fails This also should fix #24 Signed-off-by: Stephan Wendel <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened
After running the installer again, there are double entrys for crowsnest that leads to not starting moonraker due errors in config file.
What did you expect to happen
Checking for already existing entry.
How to reproduce
Run Crowsnest Installer twice.
Additional information
No response
The text was updated successfully, but these errors were encountered: