-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Debian] Replace Python 2 packages by their Python 3 counterparts and remove doubled "automake" #2167
Conversation
…oubled "automake" + python3-setuptools: https://packages.debian.org/stretch/python3-setuptools + python3-gi: https://packages.debian.org/stretch/python3-gi
Hello, @MichaIng, thank you for helping with the Mycroft project! We welcome everyone To protect yourself, the project, and users of Mycroft technologies we require Please visit https://mycroft.ai/cla to initiate this one-time signing. Thank |
Thanks for this, will merge as soon as the CLA gets in. I don't think python3-gi is actually needed for core either and we should be able to remove that requirement all together. |
I filled the form already but didn't receive a confirmation email yet. This takes a while?
Would be even better. Shall I remove it completely (on all distros) with this PR? Even as is, the PR should be tested on other architectures before merging, so then dependency on GObject could be tested all together. |
There's some amount of manual labor involved in getting the CLA mails sent out so you should have the mail soon-ish. If it doesn't arrive in a day or two, check spam then yell at me and I'll look into it. Just change it for debian/ubuntu and then we can create help-wanted issues for the other OS'es so it can be tested properly. (I currently only run Debian derivatives) |
@forslund |
Resolved conflict with new info print when pre-reqs are installed. |
CLA has arrived. Going to spin up a new Ubuntu VM and try this fresh! Thanks for contributing! |
Tested and looks good! Merging! |
Description
The aim is simply to skip installing Python 2 on Debian where only Python 3 is required. (Removal of the doubled
automake
package from dependency list is trivial. 😉)The second one is not the -dev package. There is non available for Python 3 only, instead for both: https://packages.debian.org/stretch/python-gi-dev
However I tested with the above two on x86 and didn't notice any compilation (including Mimic) or related run error with Mycroft. However clearly needs additional testing on e.g. ARM devices in case, or knowledge of the devs who know where/how the GObject libs/headers are actually used.
So take this PR for now as an idea to think about skipping the install of Python 2 on Debian.
How to test
Install on Debian on different CPU architectures, where compilation might have different needs compared to x86.
Contributor license agreement signed?