-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mycroft 2: mycroft-msm not installed #95
Comments
Is the standard |
no sadly.... nada |
Hey there, great to hear you got your Mark II! We've got some posts and updated docs coming out to provide some more detail, however the short answer is that there is no MSM in the default software shipping on the Mark II. MSM is in need of attention, and over time it became clear that git is not the best way for us to distribute and update software packages for end-users. It's made for development and it can get into a mess when things don't go smoothly. So in the mycroft-dinkum software shipped on the Mark II, Skills are updated atomically with the rest of the OS. That means if you pick Stable or LTS as your update channel, then Skills won't update themselves independent of the operating system or core underneath. You get Beta / Stable / LTS software top to bottom with the one setting. |
How can I install & activate skills that you don't distribute? How can I find out the differences in your Beta/Stable/LTS versions? |
I am also interested in the answers to the question posed by @rmsppu as well as how to go about developing skills using the Mark II. Hopefully that will all be covered in the updated documentation mentioned but if not, a quick answer here might be helpful. |
What is the release cycle within each of the releases? and when will the installation of skills become available to the end user? |
Mycroft 2, received today.
The "mycroft-msm" package is not installed.
Other commands that are cited in the docs are also not installed (mycroft-config) under Mycroft release 21.2.1, stable channel:
The text was updated successfully, but these errors were encountered: