Re: Sean Svihlaengage on startup. I'm now working to get these changes pushed upstream and included in the Debian package.
I'm a student worker/command controller with the Laboratory for Atmospheric and Space Physics (LASP). I've added some features to Gpredict which are useful to our automation, namely allowing the user to have a mission-specific configuration track and
repository?
The challenge I'm facing is that the repository I've made these changes in was cloned from upstream, currently in version 2.3.118, whereas the ham radio team's fork is currently on version 2.3.72. Is there any interest in updating the ham radio team's
Hi,
can you try to get upstream to release a new version? We aren't
actually on "2.3.72", we are 72 git commits ahead of the 2.3 release.
We should get back to proper tarball builds, but the last tagged
release on github.com is from January 2018.
Christoph
I'm a student worker/command controller with the Laboratory for Atmospheric and Space Physics (LASP). I've added some features to Gpredict which are useful to our automation, namely allowing the user to have a mission-specific configuration track andengage on startup. I'm now working to get these changes pushed upstream and included in the Debian package.
The challenge I'm facing is that the repository I've made these changes in was cloned from upstream, currently in version 2.3.118, whereas the ham radio team's fork is currently on version 2.3.72. Is there any interest in updating the ham radio team'srepository?
Please introduce multi-thread... Gpredict becomes frozen when connected to other programs if something goes wrong in the protocol. (e.g. when enabled
to control antennas)
can you try to get upstream to release a new version? We aren't
actually on "2.3.72", we are 72 git commits ahead of the 2.3 release.
We should get back to proper tarball builds, but the last tagged
release on github.com is from January 2018.
Please introduce multi-thread... Gpredict becomes frozen when
connected to other programs if something goes wrong in the protocol.
(e.g. when enabled to control antennas)
I say all of this just to say that I am not sure if perhaps our
contributions are considered undesirable changes to the program, or if
the developers are just too busy to respond. So, I am wondering if we
may need to make a PPA to release our fork until such time that some or
all of our changes might get merged.
Since it's been a little while, we could try to re-initiate contact
with the gpredict developers and perhaps we'd have better luck this
time around.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 20:01:33 |
Calls: | 6,646 |
Calls today: | 1 |
Files: | 12,190 |
Messages: | 5,327,383 |