Closed mylesagray closed 3 years ago
pls upload the full moonraker.log...
@meteyou sorry about that, full moonraker and kliippy log included in Gist.
Fixed it... the moonraker.log
was showing that the repos weren't on master
branch - I don't recall checking out a different branch, but anyway.
I did a git checkout master
on each repo and a git pull
.
moonraker
was failing due to a missing dep (I was running on an older mainsailos release), so I used the commands in the mainsailos image build to install the deps:
KLIPPER_PYTHON_DIR="${HOME}/klippy-env"
KLIPPER_SOURCE_DIR="${HOME}/klipper"
MOONRAKER_PYTHON_DIR="${HOME}/moonraker-env"
MOONRAKER_SOURCE_DIR="${HOME}/moonraker"
CONFIG_PATH="/home/pi/klipper_config/moonraker.conf"
SYSTEMDDIR="/etc/systemd/system"
${KLIPPER_PYTHON_DIR}/bin/pip install -r ${KLIPPER_SOURCE_DIR}/scripts/klippy-requirements.txt
${MOONRAKER_PYTHON_DIR}/bin/pip install -r ${MOONRAKER_SOURCE_DIR}/scripts/moonraker-requirements.txt
After this it was all working as expected, closing.
Describe the bug:\ Updated to latest on moonraker, klipper and mainsail (running on mainsailos) - Enabled update_manager in config:
The mainsail UI shows the following:
All folders (
~/klipper
,~/moonraker
and~/mainsail
) all have valid git remotes and pulls work as expected.Expected behavior:\ Moonraker discovers all packages and pulls latest versions from upstream repos.
Screenshots:\ Above
Logfiles:\ https://gist.github.com/mylesagray/b38b06ec8a2901ca1b96992979faee12