Work Being Done to Update the Project #542
Replies: 3 comments 1 reply
-
|
Good to see you back and good to see the project has been revived and
updated. I still have two receivers running your earlier code. They are
update starved and I look forward to helping with testing once things get
going again.
Welcome back!
…On Fri, Jun 14, 2024 at 7:08 PM Joe Prochazka ***@***.***> wrote:
After a long time away from the project I have begun to update the scripts
to work with the most recent releases made since the last time I was able
to work on the project. My first goal is to bring the current code up to
date. This means reworking the scripts to work with currently supported
distributions of Linux as well as make things work with the most current
versions of the third-party code bases it interacts with as well as
removing support for now defunct packages. These changes can be tracked in
a new branch named "phoenix
<https://github.com/jprochazka/adsb-receiver/tree/phoenix>", get it? This
branch also has the following milestone
<https://github.com/jprochazka/adsb-receiver/milestone/16> attached to
it. Once completed this branch will become v2.8.0. For this version do not
expect to see anything new. Once the current code is up and working, I am
planning to begin work on the portal. Maybe some fancier graphs and a more
modernized layout based on more modern technologies?
Something to take note of is the fact support for Ubuntu will be lacking
at this time. I am currently working on FlightAware support at the moment
and their code does not play nice with the most recent versions of the
distribution. This is to be expected being their software is geared mainly
towards Raspberry PI OS. In the future I hope to once again get things
working on other Debian based distribution such as Ubuntu but in order to
get things up and running as quickly as possible Debian and Raspberry Pi OS
compatibility are going to be my main focus.
It should be noted that at some point in the near future, I will be going
through the issues and doing a bit of housekeeping. Over time I will be
deleting many of the older issues which are addressed in the upcoming
version in order to keep the issue tracker saine and of use to those who
may experience issues from here on out. I also merged a few pull requests
into the master branch which people were kind enough to submit during my
absence. Thanks to those who contributed!
As for documentation, I will be relaunching adsbreceiver.net shortly.
This site will contain new updated documentation I am putting together as I
test the different installation operations during the update process.
—
Reply to this email directly, view it on GitHub
<#542>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFJE7U2QUXY2J22VXBTDDJTZHNZWZAVCNFSM6AAAAABJLD7EZCVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZWHAZDCNZQGY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hello @laferrierem thanks for suffering through the downtime. Is there anything you would like to see set at a higher priority on my TODO list as far as what you have installed currently? Meaning decoders, feeders, addons, etc. |
Beta Was this translation helpful? Give feedback.
-
|
Ha I'm happy about the birth of the phoenix project, I can't wait to help with testing once things are finished. Happy to see you again! |
Beta Was this translation helpful? Give feedback.
-
|
Welcome back! |
Beta Was this translation helpful? Give feedback.
-
After a long time away from the project I have begun to update the scripts to work with the most recent releases made since the last time I was able to work on the project. My first goal is to bring the current code up to date. This means reworking the scripts to work with currently supported distributions of Linux as well as make things work with the most current versions of the third-party code bases it interacts with as well as removing support for now defunct packages. These changes can be tracked in a new branch named "phoenix", get it? This branch also has the following milestone attached to it. Once completed this branch will become v2.8.0. For this version do not expect to see anything new. Once the current code is up and working, I am planning to begin work on the portal. Maybe some fancier graphs and a more modernized layout based on more modern technologies?
Something to take note of is the fact support for Ubuntu will be lacking at this time. I am currently working on FlightAware support at the moment and their code does not play nice with the most recent versions of the distribution. This is to be expected being their software is geared mainly towards Raspberry PI OS. In the future I hope to once again get things working on other Debian based distribution such as Ubuntu but in order to get things up and running as quickly as possible Debian and Raspberry Pi OS compatibility are going to be my main focus.
It should be noted that at some point in the near future, I will be going through the issues and doing a bit of housekeeping. Over time I will be deleting many of the older issues which are addressed in the upcoming version in order to keep the issue tracker saine and of use to those who may experience issues from here on out. I also merged a few pull requests into the master branch which people were kind enough to submit during my absence. Thanks to those who contributed!
As for documentation, I will be relaunching adsbreceiver.net shortly. This site will contain new updated documentation I am putting together as I test the different installation operations during the update process.
Update June 20th, 2024
There are only a handful of items left which need to be addressed with the lite version of the portal as well as a couple broken graphs after which updating the advanced version will be done. Once the portal is ready, I think I will feel comfortable enough to merge the changes into the master branch and create a new release.
The issue tracker has been cleared out. Due to the out-of-date state of the master branch, I ask that issues only be opened pertaining to the new phoenix branch until it has been merged into master. Any issues related to the current master branch will be disregarded at this time.
Live testing should be done on distributions listed as not tested in issues #540, #541, #543, #545, #546, #548, #553, and #554 before they are closed. If anyone wants to give them a once over and report their results feel free to do so.
Here is the CHANGELOG for the phoenix branch as of today.
Installers
Portal
Beta Was this translation helpful? Give feedback.
All reactions