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.024365
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

1 2 3 4 5 6 ... Next › Last »

Jake commented on 2019-08-25 12:15

sl1pkn07: You must run it as the octoprint user, if you want to use plugin installation etc. with the included pip, the permissions get set accordingly (other have only read+execute). I have also included a systemd service that does this automatically, so the simplest way is to just start/enable that.

sl1pkn07 commented on 2019-08-23 16:50

seems pip can't write into /opt/octorpint/lib/pythonXX/site-packages

eimis commented on 2018-08-06 19:13

It takes a long to compile on a raspberry pi 1 even with distcc, so here:

Jake commented on 2018-07-17 21:14

Yeah, but if you comment that line out you get a effectivly empty package ;) Maybe you had just a short internet disconnect while building the package? I would try a clean build again.

chrissnell commented on 2018-07-17 21:04

I'm having a strange problem with this package. When I run 'makepkg -si', the package build dies while fetching dependencies:

Processing dependencies for OctoPrint==1.3.8
Searching for frozendict<1.3,>=1.2
Download error on [Errno -3] Temporary failure in name resolution -- Some packages may not be found!
Couldn't find index page for 'frozendict' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Download error on [Errno -3] Temporary failure in name resolution -- Some packages may not be found!
No local packages or working download links found for frozendict<1.3,>=1.2
error: Could not find suitable distribution for Requirement.parse('frozendict<1.3,>=1.2')
==> ERROR: A failure occurred in package().

It was very odd to see a name resolution failure, so I went into the src directory and ran this by hand:

../../pkg/octoprint-venv/opt/octoprint-venv/bin/python2 install --optimize=1

... and it worked just fine. So, I commented this line out in PKGBUILD:

${pkgdir}/opt/$pkgname/bin/python2" install --optimize=1

and then ran makepkg -ei and the package was able to build and install.

EDIT: It did install but the octoprint binary is missing. Something is messed up.

Jake commented on 2018-07-11 13:46

Done, thanks tracernz. I am not bumping the pkgrel again, most will soon get it with the 1.3.9 release.

tracernz commented on 2018-07-07 01:44

Thanks for your efforts Jake! A small note, on startup I see the following log message in the journal: Starting the server via "octoprint" is deprecated, please use "octoprint serve" from now on.

Might be a good idea to add the "serve" arg to the service file next time you're working on the package. :)

Jake commented on 2018-06-29 22:14

Sorry for causing the data loss and thanks for the notice, Remspoor. I have changed it (pkgrel=5).

remspoor commented on 2018-06-28 13:42

Please,please,please change file /usr/lib/tmpfiles.d/octoprint.conf from: 'D /var/lib/octoprint - octoprint octoprint - -' to: 'd /var/lib/octoprint - octoprint octoprint - -' As a capital D removes the complete contents of the directory. After i updated and rebooted the Pi3, i lost all my configuration, videos aka everything concerning octoprint last night... :-(

Jake commented on 2018-06-27 19:16

Octoprint writes in it's own virtualenv to install plugins (which is possible through the web interface). Moving executables into /var/lib seems also wrong imho... I have looked into the --user config option, that would install the plugins into the home directory of the octoprint user, but that does not work if it is installed in a virtualenv. Maybe with --system-site-packages flag, but that could cause other issues and requires further investigation.