August 2024 - Users - lists.chirpmyradio.com

Re: Users Digest, Vol 186, Issue 1
by Dave B 25 Jan '25

25 Jan '25

Re:- On 01/06/2024 21:38, users-request(a)lists.chirpmyradio.com wrote: > I don't want to specify a specific version here because it's specified in the package and mentioned when you install (see above). Putting it here is just asking for it to be stale if it doesn't get updated the next time we bump. However, I'll be glad to add to the page that if you see something like the above error message it means your python is too old if you think it's necessary for clarity. > >> (Sorry to shout, but...) > Yeah, but please don't do that again. Your responses here have already been quite rude and I'm sure the other volunteers who work on this (and the docs, thanks Jeff!) will join me in appreciating you being a lot more respectful. Thanks! > > --Dan OK Dan. Apologies for "shouting", but things could be somewhat easier for us (the less experience Python users out here) than your good self, who only get involved with installs and updates when needed. Just having something on the download page (and in the archive) that states what the minimum Python version (and wxPython perhaps) is needed for any particular version of Chirp, would save "A Lot" of user time (+ cost for those on a $-per-kByte connection) and confusion re Chirp, when they find after waiting (and or paying for) the download, that it won't install. I see you updated the download info page some hours ago now, at least your name is at the bottom of the page, not Jeff's. (Sorry, I don't know who Jeff is in this respect.) As to "needing" to update my distro (LMDE 5 just now) that is still in full support for nearly another 80 days, it keeps telling me. I don't doubt that things move on over time, that's the nature of stuff, but some appreciation for us the users would help us a lot. As for what pipx is telling us when it fails, that's rather cryptic and embedded in a lot of other text, and looks at first, to be something that was spat out as some code crashed and burnt. OK. For now, I've installed one of the 2024 January 11th version, as that still works with Python 3.9.x So I have the use of Chirp again, for now. FYI: There are several LTS versions of Linux, that last a lot longer than the 2 to 2 1/5 years of the mainstream distro's. Many are popular with Radio Amateurs, just because they /*do not*/ keep messing messing with utility version changes and such. "Stability" is preferable to many of us, rather than living on the bleeding edge of development. If a distro (as mine is) still receives security patches, that for the most part, is all we need. However... For those who would like to know if it's viable to try to install a CHIRP update, before doing so. First, in a terminal command line session. (Ctrl + Alt + T will launch a fresh terminal/command line session.) These commands will show you what you are running. (The '$' indicates the command line prompt, you do not need to enter it.) The result is shown on the next line. Find out the currently installed Python version. $ python3 --version Python 3.9.2 (https://devguide.python.org/versions/ is good to view, in relation to what you discover above. 3.9.x doesn't die, until October 2025, nearly a year and a half away, just for info...) To find out the installed version of wxpython... $ python3 -c "import wx;print(wx.__version__)" 4.0.7 Both as discovered on my present system. In a downloaded .whl file, using an archive browser, look for the folder 'chirp-yyymmdd.dist-info' (Where yyyymmdd equals the date part of whatever file you downloaded.) In that folder, look in the file METADATA and you'll find a string (it is a plain text file) like:- 'Requires-Python: >=3.7,<4' That (in this case) indicates that a Python version between 3.7 and 4 is needed. (Greater or equal to v3.7 and less than v4 That example comes from the 20240111 dated .whl file.) If you download the .tar.gz file instead, look for the file 'requirements.txt' Again, that has some minimum version info re wxpython, but not python itself, that can be found in the file PKG-INFO Again, both are plain text files. Sadly, you do have to download an entire file first to discover that info in either case.. Frankly, I'd suggest doing that first, */before/* uninstalling an existing working version of Chirp! Oh, I'd also keep a local copy of the downloaded file, especially when you do install it successfully. You may need it to repair things if something else goes bad, or to revert to a known working state if a future install goes bad. Perhaps without i'net access at that time. FYI: The immediate past day-job (thankfully I'm retired now!) I used to be the customer support and service guru, in-house and on-site, both hardware and software. I learnt very early on, that making as much information available to users, /before/ they commit themselves, saves a lot of time, effort (and cost) and greatly increases a customers likelihood to come back for more of whatever we were doing at the time, and giving us more of their money! That is with hardware, and especially software! Yes, Chirp is largely free to us the users, other than the cost of time and effort to install and learn. For that we are all grateful indeed. But wasting even "free" time does not go down well with many of us. Retired I might be now, but I'm as busy as ever, just working for other "managers". (Domestic and/or feline!) 73. Dave G8KBV. -- Created on and sent from a Unix like PC running and using free and open source software:

9 14

Re: Chirp install on Linux failure, again. (Dan Smith)
by Dave B 28 Aug '24

28 Aug '24

Thanks for the replies. Well... After some research. (And still as yet unable to locate "The Pipx people".) (The most informative site I found is at:- https://pipx.pypa.io/stable/troubleshooting/ But I've not yet found a way to locate, let alone to reach out to the Pipx crew.) Anyway, after reading through that page, and also several other similar sites. I uninstalled/purged the antique distro version of Chirp. Then removed/purged python3-venv and python3-pip That also removed pipx. System restart, no issues. I then :- sudo apt install python3-venv python3-pip Completed with no error. Pipx still didn't exist, so... sudo apt install pipx Also completed with no errors. pipx list now returns :*~*$ pipx list nothing has been installed with pipx 😴 System restart again, no issues. Then retried... $ pipx install --system-site-packages ./Downloads/chirp-20240827-py3-none-any.whl The install still fails in the same way as before. :-( Looking at the structure of the .whl file, it "seems" to be a simple compressed archive of a folder structure that contains the application. So, how to install that manually, and invoke it correctly? Or, how to install from sources? Otherwise, I'm stumped. 73. Dave G0WBX. -- Created on and sent from a Unix like PC running and using open source software:

2 1

Chirp install on Linux failure, again.
by Dave B 27 Aug '24

27 Aug '24

Evening... OK, I've had the time to upgrade from LMDE5 to LMDE6, after uninstalling the earlier resident Chirp, and some other tools that were said to conflict with the upgrade process. (Virtualbox for one...) Overall, the upgrade went well. The system is stable and has been reliably working well for the last week, so time to re-install what was removed prior to the upgrade. So far so good, with other software... Some of it my own Python ramblings, that works just as it did on LMDE5. ("LMDE", is Linux Mint Debian Edition. Mint without any Ubuntu code, just Debian as it's basis, plus the Mint parts.) Anyway... Chirp chirp-20240827-py3-none-any.whl Fresh download an hour ago.... (1,805,686 bytes) Following the instructions at:- https://chirpmyradio.com/projects/chirp/wiki/ChirpOnLinux This happens.... *dave@hp-compaq-sfdt*:*~/Downloads*$ pipx install --system-site-packages ./chirp-20240827-py3-none-any.whl Traceback (most recent call last): File "/usr/bin/pipx", line 8, in <module> sys.exit(cli()) ^^^^^ File "/usr/lib/python3/dist-packages/pipx/main.py", line 819, in cli return run_pipx_command(parsed_pipx_args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/pipx/main.py", line 202, in run_pipx_command return commands.install( ^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/pipx/commands/install.py", line 30, in install package_name = package_name_from_spec( ^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/pipx/commands/common.py", line 333, in package_name_from_spec package_name = venv.install_package_no_deps( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/pipx/venv.py", line 268, in install_package_no_deps old_package_set = self.list_installed_packages() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/pipx/venv.py", line 348, in list_installed_packages pip_list = json.loads(cmd_run.stdout.strip()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/json/__init__.py", line 346, in loads return _default_decoder.decode(s) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) *dave@hp-compaq-sfdt*:*~/Downloads*$ That looks a bit "terminal", so what's awry this time? python3 is now reporting version 3.11.2 pipx is the newest version (1.1.0-1) (That literally updated less than an hour ago!) For now, I've installed the distro version, as I need to alter some radio settings... That for the record, is:- CHIRP 0.3.0dev on Linux hp-compaq-sfdt 6.1.0-23-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.99-1 (2024-07-15) x86_64 (Python 3.11.2) But it does the job for now. Comments re the .whl file install error? What is missing this time? 73. Dave G0WBX. -- Created on and sent from a Unix like PC running and using open source software:

3 5

Add new radio and best latest version chirp for Win 7
by sq3llh＠gmail.com 27 Aug '24

27 Aug '24

Hi . I only use Win7, what is the latest version of CHIRP for Win7? I have a radio HYT TC446S. How to add a radio to my chirp my chirp legacy-20221217

3 3

New chirp-next build
by donotreply＠chirpmyradio.com 27 Aug '24

27 Aug '24

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://archive.chirpmyradio.com/chirp_next/next-20240827 A list of changes since the last build are here: --

2 1

Ubuntu install fails
by jkhmr7＠gmail.com 21 Aug '24

21 Aug '24

So after realising my earlier mistake with directories I am facing the following when trying to install on Ubuntu 22.04 LTS Fatal error from pip prevented installation. Full pip output in file: /home/jonh/.local/pipx/logs/cmd_2024-08-21_14.10.06_pip_errors.log pip seemed to fail to build package: yattag Some possibly relevant errors from pip install: error: subprocess-exited-with-error TypeError: canonicalize_version() got an unexpected keyword argument 'strip_trailing_zero' error: metadata-generation-failed Error installing chirp from spec '/home/jonh/Downloads/chirp-20240821-py3-none-any.whl'. I can post the full output if that helps, hopefully someone can help me out. Many thanks

2 1

Ubuntu install fails
by jkhmr7＠gmail.com 21 Aug '24

21 Aug '24

Not sure if this is related to the other thread that is running but I didn't see anything relevant in there so posting a fresh thread. Attempting to install Chirp Next on an Ubuntu 22.04lts laptop. Python 3 installs fine but when trying to install I get the following "Unable to parse package spec: ./chirp-20240821-py3-none-any.whl" Have re-downloaded the file but no difference. Any guidance much appreciated for a Linux noob. Thanks all.

1 0

New chirp-next build
by donotreply＠chirpmyradio.com 21 Aug '24

21 Aug '24

Greetings, A new build of CHIRP-next is available. This includes changes made directly to the tree since yesterday and may include additional features, bug fixes, etc. Unless you have a reason not to, we recommend using the latest build of CHIRP-next at all times. You can get it from here: https://archive.chirpmyradio.com/chirp_next/next-20240821 A list of changes since the last build are here: 02f2d727 Update locale for recent changes fbe972cd uvk5: Bless 5.00.x firmware versions d86e626d uvk5: Add a restricted version for unsupported firmwares ea606c01 Mark extra columns immutable if mem.extra is bf97426c Fix setting extra comment if immutable 459cbaee ft70: Remove incorrect lowercase support 2eeb42f5 ft4: Make a few strings translatable. 63be12ae uvk5 driver to reference chirp_common ctcss/dtcs codes bc64f9dd Add welcome screen images for Bulgarian 17bfbf10 RT490: Add supported charset - Fixes #11020 - Fixes #11309 Issues addressed in this build: [Bug 11020] lowercase characters etc. not supported [Bug 11414] String "Cloning from radio" not translated [Bug 11479] CHIRP next-20240814 allows lower case on Yaesu FT-70DR [Bug 11483] ERROR: Radio serial detection failed: Firmware '5.00.05' [Feature 11309] Radtel RT - 490 --

1 0

Retevis cable issue
by Anael Cyberjinh 18 Aug '24

18 Aug '24

Hello I just brought a Retevis RA89 with the 2 Pin Cable from retevis too I use Arch Linux / Debian. I installed chirp without issue But now when I connect my radio to my computer I am unable to get it work I contact the seller who tell me to use windows … I've got this in the dmesg log [sam. 17 août 11:22:17 2024] usb 1-9.4: new full-speed USB device number 11 using xhci_hcd [sam. 17 août 11:22:17 2024] usb 1-9.4: device descriptor read/64, error -32 [sam. 17 août 11:22:17 2024] usb 1-9.4: device descriptor read/64, error -32 [sam. 17 août 11:22:17 2024] usb 1-9.4: new full-speed USB device number 12 using xhci_hcd [sam. 17 août 11:22:17 2024] usb 1-9.4: device descriptor read/64, error -32 [sam. 17 août 11:22:17 2024] usb 1-9.4: device descriptor read/64, error -32 [sam. 17 août 11:22:17 2024] usb 1-9-port4: attempt power cycle [sam. 17 août 11:22:18 2024] usb 1-9.4: new full-speed USB device number 13 using xhci_hcd [sam. 17 août 11:22:18 2024] usb 1-9.4: Device not responding to setup address. [sam. 17 août 11:22:18 2024] usb 1-9.4: Device not responding to setup address. [sam. 17 août 11:22:18 2024] usb 1-9.4: device not accepting address 13, error -71 [sam. 17 août 11:22:18 2024] usb 1-9.4: new full-speed USB device number 14 using xhci_hcd [sam. 17 août 11:22:18 2024] usb 1-9.4: Device not responding to setup address. [sam. 17 août 11:22:19 2024] usb 1-9.4: Device not responding to setup address. [sam. 17 août 11:22:19 2024] usb 1-9.4: device not accepting address 14, error -71 [sam. 17 août 11:22:19 2024] usb 1-9-port4: unable to enumerate USB device Have you any idea how can I get the communication between my computer and the radio is possible with Linux ? I find this topic https://vk2.net/articles/Retevis-RT3S-on-a-Mac-or-Linux-PC I am not reassure … I also checked https://chirpmyradio.com/projects/chirp/wiki/CableGuide and i think i need a specific cable but not sure to understand well ? Regards

6 6

Repeater programming with CHIRP
by radkins01＠live.com 18 Aug '24

18 Aug '24

Hi all, just a quick question or two: I'm using the latest build of CHIRP, and when I populate a list of repeaters, the program enters *every freaking repeater in Florida*, which is like a gazillion. I only want repeaters within 100 miles (or less) of me here in the greater Tampa Bay area. I tried to remove some of the entries but that doesn't work. How can I tell CHIRP that I only want repeaters within a certain set of parameters? There doesn't appear to be a way to be more selective with the program. ANY assistance appreciated! Thanks.... Rick KE4EXZ

3 2