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

Installation issue with python3-apt in virtualenv and possible solution #192

Closed
bma-vandijk opened this issue Jan 8, 2021 · 1 comment
Closed
Assignees
Labels

Comments

@bma-vandijk
Copy link

Hi,

I recently installed the localenv flavour and am using Ubuntu 2020.182. It was the default installation without adding any additional packages. However, when I tried to add other software I quickly ran into this error on a Python dependency that seemed to be missing in the virtual environment.

TASK [lamachine-core : Installing aptitude (APT)] ******************************
�[1;35m[WARNING]: Updating cache and auto-installing missing dependency: python3-apt�[0m
�[0;31mfatal: [LAPTOP-5N7G0RHD.localdomain]: FAILED! => {�[0m
�[0;31m "changed": false�[0m
�[0;31m}�[0m
�[0;31m�[0m
�[0;31mMSG:�[0m
�[0;31m�[0m
�[0;31mCould not import python modules: apt, apt_pkg. Please install python3-apt package.�[0m

I think I solved this problem for now with the solution at the bottom of this page ansible/ansible#14468 and I installed python3-apt in the site-packages folder in the virtual environment manually. I was able to update LaMachine and install the Alpino package afterwards without problems.

I just wanted to let you and other users know how to potentially solve this issue. I love the LaMachine distribution so far by the way, thank you for putting all of this together!

the log file:
lamachine-lama-20210107_091225.log

@bma-vandijk bma-vandijk changed the title Installation issue with python-3apt in virtualenv and possible solution Installation issue with python3-apt in virtualenv and possible solution Jan 8, 2021
proycon added a commit that referenced this issue Jan 8, 2021
@proycon
Copy link
Owner

proycon commented Jan 8, 2021

Thanks for the report! I hadn't seen this problem pop up before but I can indeed reproduce it now. I wonder if the latest ansible version triggered this. I'm working on a fix.

@proycon proycon self-assigned this Jan 8, 2021
@proycon proycon added the bug label Jan 8, 2021
proycon added a commit that referenced this issue Jan 8, 2021
@proycon proycon closed this as completed in 0ef8bcc Jan 8, 2021
proycon added a commit that referenced this issue Jun 3, 2021
proycon added a commit that referenced this issue Jul 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants