@KathyReid
I have been doing a bit of development lately with my own set of skills and I have been plagued by a few msm issues that I have been able to overcome but I am not confident I am using the tool correctly.
I am on a picroft platform.
I am only able to have success with msm if I follow this proceedure
ssh into picroft
sudo su
source /opt/venvs/mycroft-core/bin/activate
cd skills
msm install âskill repo nameâ
After this my skill will install but the skill has the username âpcwiiâ hyphenated at the end of my skill-name.
Also the skill-name is owned by root:root not mycroft:mycroft.
To solve this I rename the directory then chown -R mycroft:mycroft the skill-name directory.
Although this is working for me it feels like I am definitely missing something with the usage on msm.
Has the documentation for msm been clearly outlined for different platforms?
Lastly if I perform an msm update (after steps 1, 2 and 3 above) I am getting an âuncommitted changesâ error on a couple skills. The issue is I am pretty sure all my changes on github are committed.
Thanks for all your work and support
If you are using Mycroft via apt-get (the default with picroft), there should be a file at /usr/bin/msm that will run msm properly under the correct user. You should be able to just run msm install "repo name" and it will turn that command into sudo su mycroft -c "/opt/venvs/mycroft-core/bin/msm install 'repo name'". As for the uncommitted changes issue, if you post the output of msm update, we can debug further. Thereâs a chance a permissions issue could cause the uncommitted changes so you could try a chown -R mycroft:mycroft /opt/mycroft/skills to see if it helps.
Ok, I am no access to my machine so I canât provide the msm output at this time. As far as the apt-get goes, I am actually running the picroft image. The image was created a very long time ago (8 months maybe). I have not had to re-create it as it has been working fine since, even with all the core updates over that time. Could the issue be due to that? I will provide the output to msm at my next opportunity to assist in the debugging. Thanks for the help @Wolfgange and @KathyReid .
Any skill that you see an uncommitted change for settings.json is because that file is changed by the software. The skill author should add that file to the .gitignore and remove it from their skill. Iâm not sure about the skills that have changes in __init__.py. Iâd just check the changes with cd /opt/mycroft/skills/nanoleaf*; git diff.