Closed Clevero closed 5 years ago
You've still got 1.6.2 installed because the submodule wasn't updated by git checkout. Can you try git checkout --recurse-submodules v1.7
?
Yes, updating the submodule is the step that I mentioned. Should have mark it better 🤔
Updating the submodule manually via git submodule update --recursive --remote fixed it. Maybe this could be done automatically in the script?
My assumption was that this step is automatically done by the installer
Whoops, sorry, didn't read carefully enough. Yes, I agree, we need this to work automagically.
submodules have other problems as well which we weighed when switching to the current concept, see #9. I'm seriously pondering going back to just installing from PyPI. See #36 for discussion.
Expected Behavior
After running the installer again and change/set only the config parameters to fit your needs, Peekaboo should start normally
Current Behavior
After unning the installer on a 1.6.2 installation, Peekaboo fails to start because of some missing config parameters and sections in the config and does not catch up the new internal defaults
Possible Solution
The installer does update the submodule itself
Steps to Reproduce
service peekaboo restart
Context (Environment)
Updating the submodule manually via
git submodule update --recursive --remote
fixed it. Maybe this could be done automatically in the script?Detailed Description
example error message: