WD 2.10k has been checked in. Please upgrade to it


Rob Robinett
 

This version adds WD's SW version number to the spots it uploads to wsprnet.org.  That site doesn't display those version numbers, but wspr.rocks will print that version number field.
Also, version 2.10j added use of WSJT-x 2.3.0 binaries which may be downloaded when your first run this new WD.

So it is a little more important than usual that you upgrade by:

1) cd ~/wsprdaemon
2) stop wsprdaemon with:  ./wsprdaemon.sh -z
3) then get the 2.10k code with:  git pull
4) then start wsprdaemon with: ./wsprdaemon.sh -a

If done within a few seconds, that proceed should cause you to miss no more than one or two wspr cycles.


KD2OM
 

Thank you Rob,
Just did it, went fine.

Steve


On Aug 9, 2021, at 14:35, Rob Robinett <rob@...> wrote:

This version adds WD's SW version number to the spots it uploads to wsprnet.org.  That site doesn't display those version numbers, but wspr.rocks will print that version number field.
Also, version 2.10j added use of WSJT-x 2.3.0 binaries which may be downloaded when your first run this new WD.

So it is a little more important than usual that you upgrade by:

1) cd ~/wsprdaemon
2) stop wsprdaemon with:  ./wsprdaemon.sh -z
3) then get the 2.10k code with:  git pull
4) then start wsprdaemon with: ./wsprdaemon.sh -a

If done within a few seconds, that proceed should cause you to miss no more than one or two wspr cycles.


Glenn Elmore
 

fatal: not a git repository (or any of the parent directories): .git

On two systems. Was this because I downloaded via wpsrdaemon site?  Where/when does the repository get set

On 8/9/21 12:35 PM, Rob Robinett wrote:
This version adds WD's SW version number to the spots it uploads to wsprnet.org.  That site doesn't display those version numbers, but wspr.rocks will print that version number field.
Also, version 2.10j added use of WSJT-x 2.3.0 binaries which may be downloaded when your first run this new WD.

So it is a little more important than usual that you upgrade by:

1) cd ~/wsprdaemon
2) stop wsprdaemon with:  ./wsprdaemon.sh -z
3) then get the 2.10k code with:  git pull
4) then start wsprdaemon with: ./wsprdaemon.sh -a

If done within a few seconds, that proceed should cause you to miss no more than one or two wspr cycles.


Jim Lill
 

Worked fine here

On 8/9/21 4:13 PM, Glenn Elmore wrote:

fatal: not a git repository (or any of the parent directories): .git

On two systems. Was this because I downloaded via wpsrdaemon site?  Where/when does the repository get set

On 8/9/21 12:35 PM, Rob Robinett wrote:
This version adds WD's SW version number to the spots it uploads to wsprnet.org.  That site doesn't display those version numbers, but wspr.rocks will print that version number field.
Also, version 2.10j added use of WSJT-x 2.3.0 binaries which may be downloaded when your first run this new WD.

So it is a little more important than usual that you upgrade by:

1) cd ~/wsprdaemon
2) stop wsprdaemon with:  ./wsprdaemon.sh -z
3) then get the 2.10k code with:  git pull
4) then start wsprdaemon with: ./wsprdaemon.sh -a

If done within a few seconds, that proceed should cause you to miss no more than one or two wspr cycles.


Rob Robinett
 

Your WD directories were not created with git
Save your conf files snd do a clean installation using git

On Mon, Aug 9, 2021 at 1:14 PM Glenn Elmore <n6gn@...> wrote:

fatal: not a git repository (or any of the parent directories): .git

On two systems. Was this because I downloaded via wpsrdaemon site?  Where/when does the repository get set

On 8/9/21 12:35 PM, Rob Robinett wrote:
This version adds WD's SW version number to the spots it uploads to wsprnet.org.  That site doesn't display those version numbers, but wspr.rocks will print that version number field.
Also, version 2.10j added use of WSJT-x 2.3.0 binaries which may be downloaded when your first run this new WD.

So it is a little more important than usual that you upgrade by:

1) cd ~/wsprdaemon
2) stop wsprdaemon with:  ./wsprdaemon.sh -z
3) then get the 2.10k code with:  git pull
4) then start wsprdaemon with: ./wsprdaemon.sh -a

If done within a few seconds, that proceed should cause you to miss no more than one or two wspr cycles.

--
Rob Robinett
AI6VN
mobile: +1 650 218 8896


WA2TP
 

Thank you Rob
Completed on my end, no issues.

Tom


Rolf Ekstrand
 

Thank you Rob

Completed here too, no issues

Rolf  K9DZT