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

Ubuntu 24.04 / Debian Trixy #15

Open
Tmx666 opened this issue Jul 29, 2024 · 4 comments
Open

Ubuntu 24.04 / Debian Trixy #15

Tmx666 opened this issue Jul 29, 2024 · 4 comments

Comments

@Tmx666
Copy link

Tmx666 commented Jul 29, 2024

Won’t install mlat client on either of these OS’s as they have a different set of Python Libraries I believe 24.04 / Trixir use Python 3.12 which makes the mlat client not compatible

@Tmx666
Copy link
Author

Tmx666 commented Jul 29, 2024

It makes a call for Setup tools import setup which calls as a module not found error no module named setuptools

@PeterWem
Copy link

PeterWem commented Jul 29, 2024

Same error after my OS was updated from Ubuntu 23.10 to 24.04. I have Setuptools installed.

Installing mlat-client to virtual environment

34
36
38
Traceback (most recent call last):
  File "/usr/local/share/adsbexchange/mlat-client-git/setup.py", line 25, in <module>
    from setuptools import setup, Extension
ModuleNotFoundError: No module named 'setuptools'
48
50
60
70
readsb version: 3.14.1631 adsbexchange git: eea98b1 (committed: Mon Jun 17 09:18:43 2024 -0700)

$ sudo apt install python3-setuptools

python3-setuptools is already the newest version (68.1.2-2ubuntu1).

@walkure
Copy link

walkure commented Sep 1, 2024

At Python 3.12 , There're two breaking changes affected to this issue.

  • Do not pre-install setuptools in virtual environments created with venv.
  • asyncore is removed from the standard library. ( mlat-client requires asyncore ).

Also, at the venv, system-wide site libraries are hidden by default. (Therefore, cannot see libraries installed by apt are invisible on the venv).
So, I've added the statementpip3 install setuptools pyasyncore before python3 setup.py build and successfully installed and running at Ubuntu 24.04.1.

&& python3 setup.py build >> $LOGFILE \

I don't know if this will happen if we install manually setuptools and pyasyncore on below Python 3.12.
I think it is necessary to check the Python version instead of simply adding the statement above.

@PeterWem
Copy link

PeterWem commented Sep 2, 2024

At Python 3.12 , There're two breaking changes affected to this issue.

* Do not pre-install setuptools in virtual environments created with [venv](https://docs.python.org/3.12/library/venv.html#module-venv).

* [asyncore](https://docs.python.org/3.12/whatsnew/3.12.html#asynchat-and-asyncore) is removed from the standard library. ( mlat-client requires `asyncore` ).

Also, at the venv, system-wide site libraries are hidden by default. (Therefore, cannot see libraries installed by apt are invisible on the venv). So, I've added the statementpip3 install setuptools pyasyncore before python3 setup.py build and successfully installed and running at Ubuntu 24.04.1.

&& python3 setup.py build >> $LOGFILE \

I don't know if this will happen if we install manually setuptools and pyasyncore on below Python 3.12. I think it is necessary to check the Python version instead of simply adding the statement above.

Yes! Thank you! I have created a fork and added your statement. I am back running MLAT now.

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