Debian Trixie and Ubuntu Noble Numbat compatibility. #26
+331
−6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Jul 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
AKA, Python 3.12+ compatibility.
This pull request contains a fix utilizing cx_freeze v7.2.0 with the addition of requiring the python3-pyasyncore package to be installed when
./sensible-build <pixie|noble>is specified. Changes were made to the README.md file as well such as the addition of a command to be ran in conjunction with the initial dependency command when installing PiAware on Trixie or Noble along with the removal of "special characters" in said commands so people can utilize the GitHub code copy function without having to edit the pasted command. I also modified the dpkg-buildpackage command outlined in the README.md to match that of the command used for dump1090-fa todpkg-buildpackage -b --no-signafter running into a signing issue.NOTE:
This has been tested in a live Ubuntu Nobel Numbat environment. And I was able to confirm MLAT data was received and acknowledge via journalctl and the FlightAware receiver statistics page. Testing on Debian Trixie however was not completed due to installation issues I encountered using the latest test ISO from Debian.
Trixie is still a way off where Noble Numbat is a current LTS release which is why I am submitting this pull request now. That and the problem was narrowed down to a Python 3.12+ which both releases utilize. It should be noted that both python3-filelock and python3-pyasyncore currently reside in the Trixie package list which should fulfill the needs of cx_freeze and the asyncore issues on Trixie as well.