[chirp_users] New Daily Build
Greetings,
A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location:
http://trac.chirp.danplanet.com/chirp_daily/daily-20201221
A list of the changes included in this build (since the last daily) follows:
Changes for Build #640 [Dan Smith dsmith@danplanet.com] Style fix related to patch for #8565
[Jim Unroe rock.unroe@gmail.com] [H777] Retevis H777 Plus
This patch adds support for the Retevis H777 Plus (FRS/PMR) models with fixed antennas.
Related to #8565
[Jim Unroe rock.unroe@gmail.com] [H777] Rework Serial Timeout
The previous patch has broken uploads for the classic BF-888s radios and newer Retevis H777 models. The constanstant switching of the timeout to .5 before each block is sent and back to .25 after each block is sent on a Windows computer creates "noise" that causes the apparently "faster" radios to mis the "ack" returned by the radio which results in the upload failing.
This patch resolves the issue by setting the serial timeout to .5 and leaving it remain that way for all serial activity.
fixes #8197
[Jim Unroe rock.unroe@gmail.com] [RT22] Remove FRS and PMR446 Frequency Tables
This driver was coded in a way that erasing a memory row would preselect the appropriate FRS or PMR446 frequency, bandwidth and transmit power level. This would similar to how the OEM programming software functions (actually the OEM software has the frequencies, bandwidth and power level settings fixed so that they cannot be edited).
While getting ready to submit test images for these models, I rediscovered that the CHIRP test suite regards this as a memory that can't be erased and reports an error.
This patch removes the frequency tables and other code related to this so that the test suite will pass when tested with the related "image" files.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [RT22] Add Retevis RT622 Model
This patch adds support for the Retevis RT622 PMR446 version.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [RT22] Add Retevis RT22FRS Model
This patch adds support for the Retevis RT22 FRS version.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [RT22] Add Radio ID to Retevis RT22 Driver
Add additional radio ID and supporting code that is required to support currently shipping Retevis RT22 models and other similar variants.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [RT22] Retevis RT22 Driver Cleanup for better PEP8 Compliance
Clean up driver before adding another radio ID and support for additional radio models.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [KT-8R] Add New MCU Version
This patch adds an additional MCU Version to the support for the QYT KT-8R
fixes #8513
[Brad Schuler brad@schuler.ws] [anytone_iii] Naming convention cleanup (issue #8503)
[Mark Leigh mark.leigh@shaw.ca] Added methods and UI to query/import RadioRef.com for Canada. Fixes #8021 My first foray into Python, so forgive anything that's not optimal.
user: Mark Leigh mark.leigh@shaw.ca branch 'default' changed chirp/directory.py changed chirp/radioreference.py changed chirp/ui/mainapp.py
It has been reported that the models supported by the anytone778uv.py driver module are missing from today's build. I have verified this and they are gone. Reverting back to the previous build restores them.
The missing radios are still available when running "chirpw" from the up-to-date chirp.hg folder of my Windows 7 CHIRP development computer.
Could this be somehow related to the "future module" since this driver module requires it?
Jim KC9HI
On Mon, Dec 21, 2020 at 3:16 AM Build System via chirp_users chirp_users@intrepid.danplanet.com wrote:
Greetings,
A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location:
http://trac.chirp.danplanet.com/chirp_daily/daily-20201221
A list of the changes included in this build (since the last daily) follows:
Changes for Build #640 [Dan Smith dsmith@danplanet.com] Style fix related to patch for #8565
[Jim Unroe rock.unroe@gmail.com] [H777] Retevis H777 Plus
This patch adds support for the Retevis H777 Plus (FRS/PMR) models with fixed antennas.
Related to #8565
[Jim Unroe rock.unroe@gmail.com] [H777] Rework Serial Timeout
The previous patch has broken uploads for the classic BF-888s radios and newer Retevis H777 models. The constanstant switching of the timeout to .5 before each block is sent and back to .25 after each block is sent on a Windows computer creates "noise" that causes the apparently "faster" radios to mis the "ack" returned by the radio which results in the upload failing.
This patch resolves the issue by setting the serial timeout to .5 and leaving it remain that way for all serial activity.
fixes #8197
[Jim Unroe rock.unroe@gmail.com] [RT22] Remove FRS and PMR446 Frequency Tables
This driver was coded in a way that erasing a memory row would preselect the appropriate FRS or PMR446 frequency, bandwidth and transmit power level. This would similar to how the OEM programming software functions (actually the OEM software has the frequencies, bandwidth and power level settings fixed so that they cannot be edited).
While getting ready to submit test images for these models, I rediscovered that the CHIRP test suite regards this as a memory that can't be erased and reports an error.
This patch removes the frequency tables and other code related to this so that the test suite will pass when tested with the related "image" files.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [RT22] Add Retevis RT622 Model
This patch adds support for the Retevis RT622 PMR446 version.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [RT22] Add Retevis RT22FRS Model
This patch adds support for the Retevis RT22 FRS version.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [RT22] Add Radio ID to Retevis RT22 Driver
Add additional radio ID and supporting code that is required to support currently shipping Retevis RT22 models and other similar variants.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [RT22] Retevis RT22 Driver Cleanup for better PEP8 Compliance
Clean up driver before adding another radio ID and support for additional radio models.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [KT-8R] Add New MCU Version
This patch adds an additional MCU Version to the support for the QYT KT-8R
fixes #8513
[Brad Schuler brad@schuler.ws] [anytone_iii] Naming convention cleanup (issue #8503)
[Mark Leigh mark.leigh@shaw.ca] Added methods and UI to query/import RadioRef.com for Canada. Fixes #8021 My first foray into Python, so forgive anything that's not optimal.
user: Mark Leigh mark.leigh@shaw.ca branch 'default' changed chirp/directory.py changed chirp/radioreference.py changed chirp/ui/mainapp.py
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jim at rock.unroe@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
I forgot to mention this was reported as issue #8569.
Jim KC9HI
On Mon, Dec 21, 2020 at 12:58 PM Jim Unroe rock.unroe@gmail.com wrote:
It has been reported that the models supported by the anytone778uv.py driver module are missing from today's build. I have verified this and they are gone. Reverting back to the previous build restores them.
The missing radios are still available when running "chirpw" from the up-to-date chirp.hg folder of my Windows 7 CHIRP development computer.
Could this be somehow related to the "future module" since this driver module requires it?
Jim KC9HI
On Mon, Dec 21, 2020 at 3:16 AM Build System via chirp_users chirp_users@intrepid.danplanet.com wrote:
Greetings,
A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location:
http://trac.chirp.danplanet.com/chirp_daily/daily-20201221
A list of the changes included in this build (since the last daily) follows:
Changes for Build #640 [Dan Smith dsmith@danplanet.com] Style fix related to patch for #8565
[Jim Unroe rock.unroe@gmail.com] [H777] Retevis H777 Plus
This patch adds support for the Retevis H777 Plus (FRS/PMR) models with fixed antennas.
Related to #8565
[Jim Unroe rock.unroe@gmail.com] [H777] Rework Serial Timeout
The previous patch has broken uploads for the classic BF-888s radios and newer Retevis H777 models. The constanstant switching of the timeout to .5 before each block is sent and back to .25 after each block is sent on a Windows computer creates "noise" that causes the apparently "faster" radios to mis the "ack" returned by the radio which results in the upload failing.
This patch resolves the issue by setting the serial timeout to .5 and leaving it remain that way for all serial activity.
fixes #8197
[Jim Unroe rock.unroe@gmail.com] [RT22] Remove FRS and PMR446 Frequency Tables
This driver was coded in a way that erasing a memory row would preselect the appropriate FRS or PMR446 frequency, bandwidth and transmit power level. This would similar to how the OEM programming software functions (actually the OEM software has the frequencies, bandwidth and power level settings fixed so that they cannot be edited).
While getting ready to submit test images for these models, I rediscovered that the CHIRP test suite regards this as a memory that can't be erased and reports an error.
This patch removes the frequency tables and other code related to this so that the test suite will pass when tested with the related "image" files.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [RT22] Add Retevis RT622 Model
This patch adds support for the Retevis RT622 PMR446 version.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [RT22] Add Retevis RT22FRS Model
This patch adds support for the Retevis RT22 FRS version.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [RT22] Add Radio ID to Retevis RT22 Driver
Add additional radio ID and supporting code that is required to support currently shipping Retevis RT22 models and other similar variants.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [RT22] Retevis RT22 Driver Cleanup for better PEP8 Compliance
Clean up driver before adding another radio ID and support for additional radio models.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [KT-8R] Add New MCU Version
This patch adds an additional MCU Version to the support for the QYT KT-8R
fixes #8513
[Brad Schuler brad@schuler.ws] [anytone_iii] Naming convention cleanup (issue #8503)
[Mark Leigh mark.leigh@shaw.ca] Added methods and UI to query/import RadioRef.com for Canada. Fixes #8021 My first foray into Python, so forgive anything that's not optimal.
user: Mark Leigh mark.leigh@shaw.ca branch 'default' changed chirp/directory.py changed chirp/radioreference.py changed chirp/ui/mainapp.py
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jim at rock.unroe@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
It has been reported that the models supported by the anytone778uv.py driver module are missing from today's build. I have verified this and they are gone. Reverting back to the previous build restores them.
The missing radios are still available when running "chirpw" from the up-to-date chirp.hg folder of my Windows 7 CHIRP development computer.
Could this be somehow related to the "future module" since this driver module requires it?
Nothing has changed in this module in today's build, meaning nothing should be different from this vs. the last build. Sounds like it's just missing from the windows installer-based build? Anything in the debug log during chirp startup? I'll have to get my hands on a windows machine to try to reproduce and debug, but nothing stands out as a likely reason.
--Dan
Nothing has changed in this module in today's build, meaning nothing should be different from this vs. the last build. Sounds like it's just missing from the windows installer-based build? Anything in the debug log during chirp startup? I'll have to get my hands on a windows machine to try to reproduce and debug, but nothing stands out as a likely reason.
Okay, sure enough, in the build logs I see that the process wasn't able to install the future module:
Retrying (Retry(total=0, connect=None, read=None, redirect=None)) after connection broken by 'ConnectTimeoutError(<pip._vendor.requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x0131B0B0>, 'Connection to pypi.python.org timed out. (connect timeout=15)')': /simple/future/ Could not find a version that satisfies the requirement future (from versions: )
This turns out to be related to a smallish change in the network topology where the build environment runs, which prevented the build from accessing the public internet. I've fixed that now and have regenerated today's build and updated the files in the build directory:
https://trac.chirp.danplanet.com/chirp_daily/daily-20201221/
Thanks for the attention to detail from all involved!
--Dan
How in the hell do I unsubscribe from the dam emails I have only tried about 20 times to stop them
On Mon, Dec 21, 2020 at 1:54 PM Dan Smith via chirp_users < chirp_users@intrepid.danplanet.com> wrote:
Nothing has changed in this module in today's build, meaning nothing
should be different from this vs. the last build. Sounds like it's just missing from the windows installer-based build? Anything in the debug log during chirp startup? I'll have to get my hands on a windows machine to try to reproduce and debug, but nothing stands out as a likely reason.
Okay, sure enough, in the build logs I see that the process wasn't able to install the future module:
Retrying (Retry(total=0, connect=None, read=None, redirect=None))
after connection broken by 'ConnectTimeoutError(<pip._vendor.requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x0131B0B0>, 'Connection to pypi.python.org timed out. (connect timeout=15)')': /simple/future/
Could not find a version that satisfies the requirement future (from
versions: )
This turns out to be related to a smallish change in the network topology where the build environment runs, which prevented the build from accessing the public internet. I've fixed that now and have regenerated today's build and updated the files in the build directory:
https://trac.chirp.danplanet.com/chirp_daily/daily-20201221/
Thanks for the attention to detail from all involved!
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Ryan Davis at tubaplayer2003@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Did you try sending a blank email to chirp_users-unsubscribe@intrepid.danplanet.com
?
------------------------------------------- Matthew Poletiek 303.810.9082 matthew.poletiek@gmail.com www.matthewpoletiek.com
On Mon, Dec 21, 2020 at 2:05 PM ryan davis tubaplayer2003@gmail.com wrote:
How in the hell do I unsubscribe from the dam emails I have only tried about 20 times to stop them
On Mon, Dec 21, 2020 at 1:54 PM Dan Smith via chirp_users < chirp_users@intrepid.danplanet.com> wrote:
Nothing has changed in this module in today's build, meaning nothing
should be different from this vs. the last build. Sounds like it's just missing from the windows installer-based build? Anything in the debug log during chirp startup? I'll have to get my hands on a windows machine to try to reproduce and debug, but nothing stands out as a likely reason.
Okay, sure enough, in the build logs I see that the process wasn't able to install the future module:
Retrying (Retry(total=0, connect=None, read=None, redirect=None))
after connection broken by 'ConnectTimeoutError(<pip._vendor.requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x0131B0B0>, 'Connection to pypi.python.org timed out. (connect timeout=15)')': /simple/future/
Could not find a version that satisfies the requirement future (from
versions: )
This turns out to be related to a smallish change in the network topology where the build environment runs, which prevented the build from accessing the public internet. I've fixed that now and have regenerated today's build and updated the files in the build directory:
https://trac.chirp.danplanet.com/chirp_daily/daily-20201221/
Thanks for the attention to detail from all involved!
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Ryan Davis at tubaplayer2003@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Matthew Poletiek at matthew.poletiek@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Ya about 10 to 20 times and still getting them
On Mon, Dec 21, 2020, 15:19 Matthew Poletiek matthew.poletiek@gmail.com wrote:
Did you try sending a blank email to chirp_users-unsubscribe@intrepid.danplanet.com
?
Matthew Poletiek 303.810.9082 matthew.poletiek@gmail.com www.matthewpoletiek.com
On Mon, Dec 21, 2020 at 2:05 PM ryan davis tubaplayer2003@gmail.com wrote:
How in the hell do I unsubscribe from the dam emails I have only tried about 20 times to stop them
On Mon, Dec 21, 2020 at 1:54 PM Dan Smith via chirp_users < chirp_users@intrepid.danplanet.com> wrote:
Nothing has changed in this module in today's build, meaning nothing
should be different from this vs. the last build. Sounds like it's just missing from the windows installer-based build? Anything in the debug log during chirp startup? I'll have to get my hands on a windows machine to try to reproduce and debug, but nothing stands out as a likely reason.
Okay, sure enough, in the build logs I see that the process wasn't able to install the future module:
Retrying (Retry(total=0, connect=None, read=None, redirect=None))
after connection broken by 'ConnectTimeoutError(<pip._vendor.requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x0131B0B0>, 'Connection to pypi.python.org timed out. (connect timeout=15)')': /simple/future/
Could not find a version that satisfies the requirement future (from
versions: )
This turns out to be related to a smallish change in the network topology where the build environment runs, which prevented the build from accessing the public internet. I've fixed that now and have regenerated today's build and updated the files in the build directory:
https://trac.chirp.danplanet.com/chirp_daily/daily-20201221/
Thanks for the attention to detail from all involved!
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Ryan Davis at tubaplayer2003@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Matthew Poletiek at matthew.poletiek@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Ryan Davis at tubaplayer2003@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
R U unsubscribing with the same email account used to subscribe? Fred VA6FRM
On Mon., Dec. 21, 2020, 14:00 ryan davis, tubaplayer2003@gmail.com wrote:
Ya about 10 to 20 times and still getting them
On Mon, Dec 21, 2020, 15:19 Matthew Poletiek matthew.poletiek@gmail.com wrote:
Did you try sending a blank email to chirp_users-unsubscribe@intrepid.danplanet.com
?
Matthew Poletiek 303.810.9082 matthew.poletiek@gmail.com www.matthewpoletiek.com
On Mon, Dec 21, 2020 at 2:05 PM ryan davis tubaplayer2003@gmail.com wrote:
How in the hell do I unsubscribe from the dam emails I have only tried about 20 times to stop them
On Mon, Dec 21, 2020 at 1:54 PM Dan Smith via chirp_users < chirp_users@intrepid.danplanet.com> wrote:
Nothing has changed in this module in today's build, meaning nothing
should be different from this vs. the last build. Sounds like it's just missing from the windows installer-based build? Anything in the debug log during chirp startup? I'll have to get my hands on a windows machine to try to reproduce and debug, but nothing stands out as a likely reason.
Okay, sure enough, in the build logs I see that the process wasn't able to install the future module:
Retrying (Retry(total=0, connect=None, read=None, redirect=None))
after connection broken by 'ConnectTimeoutError(<pip._vendor.requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x0131B0B0>, 'Connection to pypi.python.org timed out. (connect timeout=15)')': /simple/future/
Could not find a version that satisfies the requirement future
(from versions: )
This turns out to be related to a smallish change in the network topology where the build environment runs, which prevented the build from accessing the public internet. I've fixed that now and have regenerated today's build and updated the files in the build directory:
https://trac.chirp.danplanet.com/chirp_daily/daily-20201221/
Thanks for the attention to detail from all involved!
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Ryan Davis at tubaplayer2003@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Matthew Poletiek at matthew.poletiek@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Ryan Davis at tubaplayer2003@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Fred McDougall VA6FRM at frmcdo@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
You’re not alone, Ryan. I, too, have tried unsubscribing numerous times. Doing such a simple thing is usually not hard, most places.
The Chirp list is the Hotel California.
73, Jeff K4EI
On Dec 21, 2020, at 4:14 PM, Frederick R. McDougall frmcdo@gmail.com wrote:
R U unsubscribing with the same email account used to subscribe? Fred VA6FRM
On Mon., Dec. 21, 2020, 14:00 ryan davis, <tubaplayer2003@gmail.com mailto:tubaplayer2003@gmail.com> wrote: Ya about 10 to 20 times and still getting them
On Mon, Dec 21, 2020, 15:19 Matthew Poletiek <matthew.poletiek@gmail.com mailto:matthew.poletiek@gmail.com> wrote: Did you try sending a blank email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
?
Matthew Poletiek 303.810.9082 matthew.poletiek@gmail.com mailto:matthew.poletiek@gmail.com www.matthewpoletiek.com http://www.matthewpoletiek.com/
On Mon, Dec 21, 2020 at 2:05 PM ryan davis <tubaplayer2003@gmail.com mailto:tubaplayer2003@gmail.com> wrote: How in the hell do I unsubscribe from the dam emails I have only tried about 20 times to stop them
On Mon, Dec 21, 2020 at 1:54 PM Dan Smith via chirp_users <chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com> wrote:
Nothing has changed in this module in today's build, meaning nothing should be different from this vs. the last build. Sounds like it's just missing from the windows installer-based build? Anything in the debug log during chirp startup? I'll have to get my hands on a windows machine to try to reproduce and debug, but nothing stands out as a likely reason.
Okay, sure enough, in the build logs I see that the process wasn't able to install the future module:
Retrying (Retry(total=0, connect=None, read=None, redirect=None)) after connection broken by 'ConnectTimeoutError(<pip._vendor.requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x0131B0B0>, 'Connection to pypi.python.org http://pypi.python.org/ timed out. (connect timeout=15)')': /simple/future/ Could not find a version that satisfies the requirement future (from versions: )
This turns out to be related to a smallish change in the network topology where the build environment runs, which prevented the build from accessing the public internet. I've fixed that now and have regenerated today's build and updated the files in the build directory:
https://trac.chirp.danplanet.com/chirp_daily/daily-20201221/ https://trac.chirp.danplanet.com/chirp_daily/daily-20201221/
Thanks for the attention to detail from all involved!
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Ryan Davis at tubaplayer2003@gmail.com mailto:tubaplayer2003@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Matthew Poletiek at matthew.poletiek@gmail.com mailto:matthew.poletiek@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Ryan Davis at tubaplayer2003@gmail.com mailto:tubaplayer2003@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Fred McDougall VA6FRM at frmcdo@gmail.com mailto:frmcdo@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jeff Hughes at jeffreyhughes@earthlink.net mailto:jeffreyhughes@earthlink.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
You can also unsubscribe via the web link: http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Scroll down to the bottom of the page and the last input box is for inputing your email address. From there you can unsubscribe or edit options.
Lyle Giese, KD9RCN
On 12/21/20 3:42 PM, Jeff Hughes wrote:
You’re not alone, Ryan. I, too, have tried unsubscribing numerous times. Doing such a simple thing is usually not hard, most places.
The Chirp list is the Hotel California.
73, Jeff K4EI
On Dec 21, 2020, at 4:14 PM, Frederick R. McDougall <frmcdo@gmail.com mailto:frmcdo@gmail.com> wrote:
R U unsubscribing with the same email account used to subscribe? Fred VA6FRM
On Mon., Dec. 21, 2020, 14:00 ryan davis, <tubaplayer2003@gmail.com mailto:tubaplayer2003@gmail.com> wrote:
Ya about 10 to 20 times and still getting them On Mon, Dec 21, 2020, 15:19 Matthew Poletiek <matthew.poletiek@gmail.com <mailto:matthew.poletiek@gmail.com>> wrote: Did you try sending a blank email to chirp_users-unsubscribe@intrepid.danplanet.com <mailto:chirp_users-unsubscribe@intrepid.danplanet.com> ? ------------------------------------------- Matthew Poletiek 303.810.9082 matthew.poletiek@gmail.com <mailto:matthew.poletiek@gmail.com> www.matthewpoletiek.com <http://www.matthewpoletiek.com/> On Mon, Dec 21, 2020 at 2:05 PM ryan davis <tubaplayer2003@gmail.com <mailto:tubaplayer2003@gmail.com>> wrote: How in the hell do I unsubscribe from the dam emails I have only tried about 20 times to stop them On Mon, Dec 21, 2020 at 1:54 PM Dan Smith via chirp_users <chirp_users@intrepid.danplanet.com <mailto:chirp_users@intrepid.danplanet.com>> wrote: > Nothing has changed in this module in today's build, meaning nothing should be different from this vs. the last build. Sounds like it's just missing from the windows installer-based build? Anything in the debug log during chirp startup? I'll have to get my hands on a windows machine to try to reproduce and debug, but nothing stands out as a likely reason. Okay, sure enough, in the build logs I see that the process wasn't able to install the future module: > Retrying (Retry(total=0, connect=None, read=None, redirect=None)) after connection broken by 'ConnectTimeoutError(<pip._vendor.requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x0131B0B0>, 'Connection topypi.python.org <http://pypi.python.org/>timed out. (connect timeout=15)')': /simple/future/ > Could not find a version that satisfies the requirement future (from versions: ) This turns out to be related to a smallish change in the network topology where the build environment runs, which prevented the build from accessing the public internet. I've fixed that now and have regenerated today's build and updated the files in the build directory: https://trac.chirp.danplanet.com/chirp_daily/daily-20201221/ <https://trac.chirp.danplanet.com/chirp_daily/daily-20201221/> Thanks for the attention to detail from all involved! --Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com <mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users <http://intrepid.danplanet.com/mailman/listinfo/chirp_users> This message was sent to Ryan Davis attubaplayer2003@gmail.com <mailto:tubaplayer2003@gmail.com> To unsubscribe, send an email tochirp_users-unsubscribe@intrepid.danplanet.com <mailto:chirp_users-unsubscribe@intrepid.danplanet.com> _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com <mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users <http://intrepid.danplanet.com/mailman/listinfo/chirp_users> This message was sent to Matthew Poletiek atmatthew.poletiek@gmail.com <mailto:matthew.poletiek@gmail.com> To unsubscribe, send an email tochirp_users-unsubscribe@intrepid.danplanet.com <mailto:chirp_users-unsubscribe@intrepid.danplanet.com> _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com <mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users <http://intrepid.danplanet.com/mailman/listinfo/chirp_users> This message was sent to Ryan Davis attubaplayer2003@gmail.com <mailto:tubaplayer2003@gmail.com> To unsubscribe, send an email tochirp_users-unsubscribe@intrepid.danplanet.com <mailto:chirp_users-unsubscribe@intrepid.danplanet.com> _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com <mailto:chirp_users@intrepid.danplanet.com> http://intrepid.danplanet.com/mailman/listinfo/chirp_users <http://intrepid.danplanet.com/mailman/listinfo/chirp_users> This message was sent to Fred McDougall VA6FRM atfrmcdo@gmail.com <mailto:frmcdo@gmail.com> To unsubscribe, send an email tochirp_users-unsubscribe@intrepid.danplanet.com <mailto:chirp_users-unsubscribe@intrepid.danplanet.com>
chirp_users mailing list chirp_users@intrepid.danplanet.com mailto:chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Jeff Hughes atjeffreyhughes@earthlink.net mailto:jeffreyhughes@earthlink.net To unsubscribe, send an email tochirp_users-unsubscribe@intrepid.danplanet.com mailto:chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Lyle at lyle@lcrcomputer.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
yes
On Mon, Dec 21, 2020 at 1:15 PM Frederick R. McDougall frmcdo@gmail.com wrote:
R U unsubscribing with the same email account used to subscribe? Fred VA6FRM
On Mon., Dec. 21, 2020, 14:00 ryan davis, tubaplayer2003@gmail.com wrote:
Ya about 10 to 20 times and still getting them
On Mon, Dec 21, 2020, 15:19 Matthew Poletiek matthew.poletiek@gmail.com wrote:
Did you try sending a blank email to chirp_users-unsubscribe@intrepid.danplanet.com
?
Matthew Poletiek 303.810.9082 matthew.poletiek@gmail.com www.matthewpoletiek.com
On Mon, Dec 21, 2020 at 2:05 PM ryan davis tubaplayer2003@gmail.com wrote:
How in the hell do I unsubscribe from the dam emails I have only tried about 20 times to stop them
On Mon, Dec 21, 2020 at 1:54 PM Dan Smith via chirp_users < chirp_users@intrepid.danplanet.com> wrote:
Nothing has changed in this module in today's build, meaning nothing
should be different from this vs. the last build. Sounds like it's just missing from the windows installer-based build? Anything in the debug log during chirp startup? I'll have to get my hands on a windows machine to try to reproduce and debug, but nothing stands out as a likely reason.
Okay, sure enough, in the build logs I see that the process wasn't able to install the future module:
Retrying (Retry(total=0, connect=None, read=None, redirect=None))
after connection broken by 'ConnectTimeoutError(<pip._vendor.requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x0131B0B0>, 'Connection to pypi.python.org timed out. (connect timeout=15)')': /simple/future/
Could not find a version that satisfies the requirement future
(from versions: )
This turns out to be related to a smallish change in the network topology where the build environment runs, which prevented the build from accessing the public internet. I've fixed that now and have regenerated today's build and updated the files in the build directory:
https://trac.chirp.danplanet.com/chirp_daily/daily-20201221/
Thanks for the attention to detail from all involved!
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Ryan Davis at tubaplayer2003@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Matthew Poletiek at matthew.poletiek@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Ryan Davis at tubaplayer2003@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Fred McDougall VA6FRM at frmcdo@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Kevin at kevians2001@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Best bet if you can't get it to unsubscribe you with the links in the emails is to just set up a mail filter and route them to trash. Much easier than getting upset. A lot of times the email unsubscribes won't work if you have anything fancy in your mail or a sig added.
Dave
On Mon, Dec 21, 2020 at 3:05 PM ryan davis tubaplayer2003@gmail.com wrote:
How in the hell do I unsubscribe from the dam emails I have only tried about 20 times to stop them
On Mon, Dec 21, 2020 at 1:54 PM Dan Smith via chirp_users < chirp_users@intrepid.danplanet.com> wrote:
Nothing has changed in this module in today's build, meaning nothing
should be different from this vs. the last build. Sounds like it's just missing from the windows installer-based build? Anything in the debug log during chirp startup? I'll have to get my hands on a windows machine to try to reproduce and debug, but nothing stands out as a likely reason.
Okay, sure enough, in the build logs I see that the process wasn't able to install the future module:
Retrying (Retry(total=0, connect=None, read=None, redirect=None))
after connection broken by 'ConnectTimeoutError(<pip._vendor.requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x0131B0B0>, 'Connection to pypi.python.org timed out. (connect timeout=15)')': /simple/future/
Could not find a version that satisfies the requirement future (from
versions: )
This turns out to be related to a smallish change in the network topology where the build environment runs, which prevented the build from accessing the public internet. I've fixed that now and have regenerated today's build and updated the files in the build directory:
https://trac.chirp.danplanet.com/chirp_daily/daily-20201221/
Thanks for the attention to detail from all involved!
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Ryan Davis at tubaplayer2003@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W2IJL at n36078@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Mon, Dec 21, 2020 at 3:05 PM ryan davis tubaplayer2003@gmail.com wrote:
How in the hell do I unsubscribe from the dam emails I have only tried about 20 times to stop them
Did you follow the instructions at the end of the email?
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Ryan Davis at tubaplayer2003@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Right here ^^^^^
Jim KC9HI
Dan,
On Tue, Dec 22, 2020 at 1:27 PM Dan Smith dsmith@danplanet.com wrote:
Nothing has changed in this module in today's build, meaning nothing should be different from this vs. the last build. Sounds like it's just missing from the windows installer-based build? Anything in the debug log during chirp startup? I'll have to get my hands on a windows machine to try to reproduce and debug, but nothing stands out as a likely reason.
Okay, sure enough, in the build logs I see that the process wasn't able to install the future module:
Retrying (Retry(total=0, connect=None, read=None, redirect=None)) after connection broken by 'ConnectTimeoutError(<pip._vendor.requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x0131B0B0>, 'Connection to pypi.python.org timed out. (connect timeout=15)')': /simple/future/ Could not find a version that satisfies the requirement future (from versions: )
This turns out to be related to a smallish change in the network topology where the build environment runs, which prevented the build from accessing the public internet. I've fixed that now and have regenerated today's build and updated the files in the build directory:
https://trac.chirp.danplanet.com/chirp_daily/daily-20201221/
Thanks for the attention to detail from all involved!
--Dan
An issue was just opened because the recently added AnyTone radio models are missing. Could the same thing have happened causing the "future" module to be missing in the Mac build?
https://chirp.danplanet.com/issues/8787
Jim
An issue was just opened because the recently added AnyTone radio models are missing. Could the same thing have happened causing the "future" module to be missing in the Mac build?
Well, this is different in that the Mac build is frozen and is the thing missing the module. The App gets built just by jamming the updated python files in during the build on a non-mac machine, whereas the windows installer is built from pieces each time on an actual windows system. I could jam the future module in there as well, but there are other problems with that. I really want to try to get us off the legacy mac stack if possible, but it's complicated.
--Dan
THANKS Mark - nice work!! Worked perfectly.
[Mark Leigh mark.leigh@shaw.ca] Added methods and UI to query/import RadioRef.com for Canada. Fixes #8021 My first foray into Python, so forgive anything that's not optimal.
-----Original Message----- From: chirp_users-bounces@intrepid.danplanet.com [mailto:chirp_users-bounces@intrepid.danplanet.com] On Behalf Of Build System via chirp_users Sent: December 21, 2020 12:14 AM To: chirp_users@intrepid.danplanet.com Subject: [chirp_users] New Daily Build
Greetings,
A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location:
http://trac.chirp.danplanet.com/chirp_daily/daily-20201221
A list of the changes included in this build (since the last daily) follows:
Changes for Build #640 [Dan Smith dsmith@danplanet.com] Style fix related to patch for #8565
[Jim Unroe rock.unroe@gmail.com] [H777] Retevis H777 Plus
This patch adds support for the Retevis H777 Plus (FRS/PMR) models with fixed antennas.
Related to #8565
[Jim Unroe rock.unroe@gmail.com] [H777] Rework Serial Timeout
The previous patch has broken uploads for the classic BF-888s radios and newer Retevis H777 models. The constanstant switching of the timeout to .5 before each block is sent and back to .25 after each block is sent on a Windows computer creates "noise" that causes the apparently "faster" radios to mis the "ack" returned by the radio which results in the upload failing.
This patch resolves the issue by setting the serial timeout to .5 and leaving it remain that way for all serial activity.
fixes #8197
[Jim Unroe rock.unroe@gmail.com] [RT22] Remove FRS and PMR446 Frequency Tables
This driver was coded in a way that erasing a memory row would preselect the appropriate FRS or PMR446 frequency, bandwidth and transmit power level. This would similar to how the OEM programming software functions (actually the OEM software has the frequencies, bandwidth and power level settings fixed so that they cannot be edited).
While getting ready to submit test images for these models, I rediscovered that the CHIRP test suite regards this as a memory that can't be erased and reports an error.
This patch removes the frequency tables and other code related to this so that the test suite will pass when tested with the related "image" files.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [RT22] Add Retevis RT622 Model
This patch adds support for the Retevis RT622 PMR446 version.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [RT22] Add Retevis RT22FRS Model
This patch adds support for the Retevis RT22 FRS version.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [RT22] Add Radio ID to Retevis RT22 Driver
Add additional radio ID and supporting code that is required to support currently shipping Retevis RT22 models and other similar variants.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [RT22] Retevis RT22 Driver Cleanup for better PEP8 Compliance
Clean up driver before adding another radio ID and support for additional radio models.
related to #6467
[Jim Unroe rock.unroe@gmail.com] [KT-8R] Add New MCU Version
This patch adds an additional MCU Version to the support for the QYT KT-8R
fixes #8513
[Brad Schuler brad@schuler.ws] [anytone_iii] Naming convention cleanup (issue #8503)
[Mark Leigh mark.leigh@shaw.ca] Added methods and UI to query/import RadioRef.com for Canada. Fixes #8021 My first foray into Python, so forgive anything that's not optimal.
user: Mark Leigh mark.leigh@shaw.ca branch 'default' changed chirp/directory.py changed chirp/radioreference.py changed chirp/ui/mainapp.py
participants (11)
-
Build System
-
Dan Smith
-
Dave Matthews
-
Frederick R. McDougall
-
G-mail
-
Jeff Hughes
-
Jim Unroe
-
Kevin Evans
-
Lyle Giese
-
Matthew Poletiek
-
ryan davis