Arch Linux User Repository

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

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

It takes a long to compile on a raspberry pi 1 even with distcc, so here: http://www.mediafire.com/file/i41s8d4i4cd9cqq/octoprint-venv-1.3.9-1-armv6h.pkg.tar.xz

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.

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
Reading https://pypi.python.org/simple/frozendict/
Download error on https://pypi.python.org/simple/frozendict/: [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)
Reading https://pypi.python.org/simple/
Download error on https://pypi.python.org/simple/: [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().
    Aborting...

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 setup.py install --optimize=1

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

${pkgdir}/opt/$pkgname/bin/python2" setup.py 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.

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

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. :)

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

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... :-(

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.

Depends on whether OctoPrint actually wants to write in its own code. I doubt that, so the octoprint user shouldn't have write permissions for security reasons. If OctoPrint writes in the venv it should be in /var/lib/octoprint, since everything in /opt should only be touched by package managers/installers.