New release: 1.2.6

Whoa, another one? Yup. I forgot to pin the version of a library OctoPrint now depends on since 1.2.5. A new version of that library was released today which apparently has a bug that causes the install of OctoPrint to crash when it tries to pull in that new library version ("pip install ." works, "python setup.py install" does not). If you tried to update today and ran into errors, read further below on how to solve this manually.

OctoPrint 1.2.6 pins the version number of the offending library (and a bunch of others, to prevent this from happening again) and also includes a tiny improvement with regards to handling version reporting in detached checkouts, courtesy of +Koen Kooi.

Find the full changelog here: https://github.com/foosel/OctoPrint/releases/tag/1.2.6

If you don't get an "Update Now" button with your update notification, read this: https://github.com/foosel/OctoPrint/wiki/Plugin:-Software-Update#making-octoprint-updateable-on-existing-installations

Updating woes earlier today? Read on

If you tried updating from 1.2.4 (or older) to 1.2.5 today (2015-09-02), your "python setup.py install" call might have failed, causing OctoPrint 1.2.5 to not install correctly. If your server is currently not starting up properly, try updating your OctoPrint installation manually via the "good old fashioned way" described on the Wiki, that will get you 1.2.6 which doesn't have that issue anymore: https://github.com/foosel/OctoPrint/wiki/FAQ#how-can-i-update-the-octoprint-installation-on-my-octopi-image

Alternatively, manually install psutil in version 3.1.1, then run OctoPrint's "python setup.py install" again. For OctoPi:

cd ~/OctoPrint
~/oprint/bin/pip install psutil==3.1.1
~/oprint/bin/python setup.py install
sudo service octoprint restart

Adjust the OctoPrint checkout folder and the paths to pip and python to match your individual installation if your are not running OctoPi.