Package Details: mycroft-core 18.8.4-2

Git Clone URL: https://aur.archlinux.org/mycroft-core.git (read-only)
Package Base: mycroft-core
Description: The Mycroft Artificial Intelligence platform.
Upstream URL: https://github.com/MycroftAI/mycroft-core
Licenses: Apache
Submitter: manzo
Maintainer: xenrox
Last Packager: xenrox
Votes: 21
Popularity: 0.825348
First Submitted: 2016-12-27 12:48
Last Updated: 2018-10-30 14:12

Latest Comments

1 2 3 4 5 Next › Last »

librewish commented on 2019-03-20 07:49

mycroft-core is outdated it asks to be upgraded to version 19

ixil commented on 2018-10-31 20:55

@xenrox, sorry for slow reply forgot to enable notifications. The problem was that I only tried to run it through systemctl --user start starting it directly from start-mycroft.sh cli Shows that it trying to create (requires sudo) /opt/mycroft{,/skills}. Then changes the ownership(also needs sudo) and group to my user, shouldn't this be the user and group mycroft-core - it tries to change the owner/group every startup.

Now I have connection problems, the websocket library throws an uncaught exception which doesn't seem to appear in the logs (I assume in /var/log/mycroft/*)

xenrox commented on 2018-10-23 08:43

@ixil That sounds more like an issue with your sudo setup/pam module than with this package. Can you tell me which command you used which caused this problem? Normally you would do: systemctl --user enable mycroft.service Sudo is not even required. /opt/mycroft/skills/ is created by mycroft when it is started for the first time and downloads the default skills. Edit: If you want a faster reply, write me an email (address is encoded in the PKGBUILD).

ixil commented on 2018-10-21 14:31

Using the systemd user file I'm getting an error:

hostname sudo[14288]: pam_unix(sudo:auth): conversation failed
hostname sudo[14288]: pam_unix(sudo:auth): auth could not identify password for myuser

Any hints?

Also previously it was trying to create /opt/mycroft/skills/ which I manually did and changed the group to mycroft-core - should this be in the post-install instructions? or changed in the settings - in which case that should probably follow the default arch directories

idleshand commented on 2018-10-19 20:25

Thanks for maintaining this package. :)

xenrox commented on 2018-10-19 12:18

@idleshand Thanks for notifying me. I updated the package.

idleshand commented on 2018-10-18 13:08

Looks to me like it is worth updating the pkgbuild to reflect the changes that have been made to the original "dev_setup.sh".

The only changes I can actually see are related to pip. Specifically upgrading to using pip v18 as in this commit: https://github.com/MycroftAI/mycroft-core/commit/5e6c1773e4daa2da99f63110944fd220bf2298ee#diff-18dbf5207379240f00af7b954cde81ff

And then using curl to get pip directly and installing to the virtual_env instead of using easy_install, in this commit https://github.com/MycroftAI/mycroft-core/commit/923ea9f532175ba70027d09eb250b2c81655bdde#diff-18dbf5207379240f00af7b954cde81ff

z3ntu commented on 2018-08-12 09:13

The postinstall script fails to build pyyaml for some reason. edit: Patching /usr/share/mycroft-core/requirements.txt to use pyyyaml 3.13 instead of 3.11 works (see https://github.com/yaml/pyyaml/issues/152) edit2: still can't properly start the mycroft service due to some permission problems even though I'm in the mycroft-core group

ubuntourist commented on 2018-06-21 17:24

See also https://community.mycroft.ai/t/change-virtualenvwrapper-to-pipenv/3968

ubuntourist commented on 2018-06-14 17:07

The python-pipenv package conflicts with the python-virtualenvwrapper package.

(pipenv is now the recommended replacement for pip and virtualenv according to Python Software Foundation [https://packaging.python.org/tutorials/managing-dependencies/#managing-dependencies])