Package Details: octoprint-venv 1.3.11-1

Git Clone URL: (read-only)
Package Base: octoprint-venv
Description: The snappy snappy web interface for your 3D printer! (virtualenv installation type)
Upstream URL:
Licenses: AGPL3
Conflicts: octoprint
Provides: octoprint
Submitter: Jake
Maintainer: Jake
Last Packager: Jake
Votes: 18
Popularity: 0.021045
First Submitted: 2017-01-15 12:46
Last Updated: 2019-05-27 09:48

Pinned Comments

Jake commented on 2017-10-24 16:03

If the hashsum is incorrect please just flag it out of date (also when there is no real new release, but the changed the old archive for some reason).

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

Niklas commented on 2017-08-12 17:15

Finally updated to 1.3.4. Used some commits from the master branch to make 1.3.4 compatible with the newest versions of the Flask plugins and Tornado 4.5. If you are experiencing issues related to Tornado, you can try the python2-tornado-4.4 package instead ( since 4.4 is the officially supported version of Tornado, however I did not have any problems with 4.5 so it should be fine.

ad1217 commented on 2017-06-06 00:40

sha256sum appears to be wrong or has changed, I now get f373b85058d92ef36de3dac9c64b707d5bf62f3ec30c49958d14157e6087928c.

bmd_online commented on 2017-06-03 13:38

Need to update PKGBUILD, according to release 1.3.4 :


Jake commented on 2017-05-02 21:52

Nice, thanks bmd_online!
I tested this today and it works flawless with the replaced paths, so i am going to change it in the package. Revision 3, now with working plugin installation ;)

bmd_online commented on 2017-05-02 05:07

I got it !

In PKGBUILD, you're using this command :
virtualenv2 --relocatable ${pkgdir}/opt/$pkgname

relocatable instruction is weird :
"The --relocatable option currently has a number of issues, and is not guaranteed to work in all circumstances. It is possible that the option will be deprecated in a future version of virtualenv."

I have replaced with this command :
sed -i "s|${pkgdir}/opt/$pkgname|/opt/$pkgname|g" ${pkgdir}/opt/$pkgname/bin/*

and now it works perfectly.

bmd_online commented on 2017-05-01 16:58

Installed today, still have "pip" error. For example :

2017-05-01 18:41:53,343 /usr/bin/python2.7 -m pip install
2017-05-01 18:42:13,546 > Collecting
2017-05-01 18:42:15,878 > Downloading
2017-05-01 18:42:42,960 ! Command "python egg_info" failed with error code 255 in /tmp/pip-esdU2k-build/
2017-05-01 18:42:43,486 > Complete output from command python egg_info:
2017-05-01 18:42:43,494 > Could not import OctoPrint's setuptools, are you sure you are running that under the same python installation that OctoPrint is installed under?

* I have installed python2-pip before octoprint.
* I've tried to launch manually octoprint, enabling octoprint user shell.
==> Still having the same problem.
* find /opt/octoprint-venv -not -user octoprint -print
==> Returns nothing.
* Installing plugins manually is working (cd into the /opt/octoprint-venv/bin directory and do ./python2 pip install PLUGIN).

Jake commented on 2017-04-24 16:08

No, Octoprint supports only python2 unfortunately, so it also wont run in a python3 venv... there are plans to change this in the 1.4 milestone.
I can offer a python3 pkg as soon as this is done and released.

FirefighterBlu3 commented on 2017-04-23 22:35

can you offer a python3 venv of this? it's a bit frustrating to have a full py2 setup installed when i used to have a clean py3 rpi

Jake commented on 2017-04-04 10:31

I added now that chown in the .install script. Let me know if it works for everyone or not.
(still doesn't work on my machines, with the before mentioned error)

bch24 commented on 2017-04-04 06:33

chown -R octoprint:octoprint /opt/octoprint-venv

That fixed it for me.