Skip to content
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

VM setup guide not mentioning venv activation? #195

Open
joshuajaharwood opened this issue Sep 23, 2020 · 4 comments
Open

VM setup guide not mentioning venv activation? #195

joshuajaharwood opened this issue Sep 23, 2020 · 4 comments

Comments

@joshuajaharwood
Copy link

I've been following the VM guide for installing Mycroft to develop some skills (and maybe mycroft-core), and noticed that the page doesn't mention that you have to activate the virtual environment first. It isn't activated automatically and starting mycroft services without it being activated causes package manager errors.

Could somebody else confirm/deny this, please? If it is an issue, I'll correct the instructions :)

Thanks!

@forslund
Copy link
Collaborator

You shouldn't (TM) need to manually activate the venv, the start script should handle that automatically.

If you're getting errors during startup there may be a bug...

@krisgesling
Copy link
Contributor

Hi Joshua, can you post the commands you used and the output you got?

Also can you confirm the OS you're running and which version of VirtualBox?

@joshuajaharwood
Copy link
Author

Commands

  • sudo apt update
  • sudo apt upgrade
  • sudo apt install alsa pulseaudio
  • git clone https://github.com/MycroftAI/mycroft-core.git
  • cd mycroft-core
  • ./dev_setup.sh -fm
  • n - unstable branches (happens on stable AND unstable)
  • y
  • y
  • y
  • enter, y
  • sudo reboot
  • mycroft-start all
  • mycroft-cli-client

Result

The following is produced in the logs:
Link

Software

Host OS: ElementaryOS 6.0 Next
Guest OS: Ubuntu 20.04.1-live-server-amd64
VirtualBox 6.1.10

@forslund
Copy link
Collaborator

forslund commented Sep 28, 2020

I think that is mainly an issue with msm/pako reporting this error even when there are no system packages to install... (basically none of the default skills require special system packages to be installed)

Edit: and thanks for such a clear and concise description!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants