I do upgrades of chirp with a command line that looks like
*pip install --upgrade ./chirp-20230509-py3-none-any.whl*
and it works for me. Admittedly I do not use Ubuntu, and use Fedora instead but the use of python and pip is almost identical on both systems. Chirp is installed in the user python environment and not in the systemwide area.
Anyone who cannot understand that the instructions expect the user to download the newer version then use the command with the appropriate file name for the version just downloaded probably should go back and read the instructions again.. The same applies to those who do not understand that it must be downloaded first before attempting the install or upgrade.
Remember always that posted instruction commands are examples and the user must modify parts to fit their own environment -- especially when it gives paths and file names..
Jeff KI7GJG
On Thu, Sep 14, 2023 at 7:33 PM Tony Ling tonyg7txu@gmail.com wrote:
I totally agree, I'm not an expert on Ubuntu by any means, yet if I follow the instructions line by line, it fails me almost every time. I think Linux installation could be better explained. Ideally, it would have a apt-get update candidate.
On Thu, 14 Sept 2023 at 14:54, Dave B via chirp_users < chirp_users@intrepid.danplanet.com> wrote:
Hi.
I just installed the current Chirp on this LMDE 5 system, using the instructions as shown on :- https://chirp.danplanet.com/projects/chirp/wiki/ChirpOnLinux
There is a "slight wrinkle" in para 2.2.
The command line invocation:-
*pipx install --system-site-packages ./chirp-20230509-py3-none-any.whl*
Fails as the file "chirp-20230509-py-none-any.whl" was not present anywhere. That is also an old version now as well.
OK, simple for me to figure out, but for many other windoze refugees probably less so, so perhaps either some additional instruction regarding actually getting the .whl file "First" (finding the link to that was not as easy as it should be I think either) or including a wget somewhere to pull the latest from the server, and make it all work "automagically" ?
Otherwise, 20230911 is working OK with the shack Kenwood TM-V71 on a 64 bit LMDE 5 system.
Re the use of pipx, and the comment that pipx users will need to uninstall Chirp, before installing a new version. Is there a reason why "pipx upgrade" cant be used? If so, what is the reason?
Lastly, where is the Chirp Icon file hidden these days? (So I can put it in my menu system.)
Oh, I also find that this version of Chirp, does not remember the custom port name for the radio, in this case /dev/ttyTMV71 as assigned by a udev rule for consistency. The resulting entry in the port dropdown, is also mostly obscured by being shoved over to far to the left in that field.
Dave G8KBV.
-- Sent from a MicroSoft free zone:
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tony Ling at tonyg7txu@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@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 sandhillsinvestment@gmail.com at sandhillsinvestment@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com