Re: [chirp_users] Upgrading CHIRP on Ubuntu 23.04?
Removing the old package and installing the new one worked, but there should be a more "efficient" method...
This worked: jon@jon-notebook:~/Downloads$ pipx list venvs are in /home/jon/.local/pipx/venvs apps are exposed on your $PATH at /home/jon/.local/bin package chirp 20230531, installed using Python 3.11.2 - chirp - chirpc jon@jon-notebook:~/Downloads$ pipx uninstall-all uninstalled chirp! ✨ 🌟 ✨ jon@jon-notebook:~/Downloads$ pipx install --system-site-packages ./chirp-20230601-py3-none-any.whl installed package chirp 20230601, installed using Python 3.11.2 These apps are now globally available - chirp - chirpc done! ✨ 🌟 ✨
Any way to upgrade on a flagged system like Ubuntu 23.04 in the future without removing the old one first?
Jon Gauthier - KB1HTW
---------- Forwarded message ---------- From: Jon Gauthier jon@sailbeausoleil.com To: chirp_users@intrepid.danplanet.com Cc: Bcc: Date: Thu, 01 Jun 2023 14:48:07 -0400 Subject: [chirp_users] Upgrading CHIRP on Ubuntu 23.04? When trying to follow the upgrade instructions on the ChirpOnLinux page, there seems to be an error or some information missing.
"Once chirp is properly installed, upgrades to newer versions are done with two simple steps: 1. Download the newer .tar.gz file. 2. Run pip install --upgrade ./chirp-<version>.whl (use pipx if you used it above)"
Since I'm running Ubuntu 23.04, I used "pipx" to install the latest CHIRP. Today, a new version came out so I downloaded the latest .whl version and ran
"pipx install --upgrade ./chirp-20230601-py3-none-any.whl"
But pipx doesn't have a "--upgrade" option to the install verb. If I try pipx without the "--upgrade" option, it tells me:
'chirp' already seems to be installed. Not modifying existing installation in '/home/jon/.local/pipx/venvs/chirp'. Pass '--force' to force installation.
Should I "install --force" it? "pipx reinstall" doesn't work, since the new version isn't installed yet. Should I remove the old package "chirp 20230531" first then install the new one using:
"pipx install --system-site-packages ./chirp-20230601-py3-none- any.whl"?
Jon Gauthier - KB1HTW
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users 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
Jon,
From: Download - CHIRP (danplanet.com) https://chirp.danplanet.com/projects/chirp/wiki/Download https://chirp.danplanet.com/projects/chirp/wiki/Download
*Upgrading*: You do *NOT *need to uninstall an existing version of CHIRP before installing a newer one. Just install the new one and it will replace the existing copy! However, *be sure to quit CHIRP before installing the new version!*
*The CHIRP team recommends CHIRP-next unless you experience problems with your radio*. If you do, please see How_To_Report_Issues https://chirp.danplanet.com/projects/chirp/wiki/How_To_Report_Issues. 73 David N1EA
On Thu, Jun 1, 2023 at 4:03 PM Jon Gauthier jon@sailbeausoleil.com wrote:
Removing the old package and installing the new one worked, but there should be a more "efficient" method...
This worked: jon@jon-notebook:~/Downloads$ pipx list venvs are in /home/jon/.local/pipx/venvs apps are exposed on your $PATH at /home/jon/.local/bin package chirp 20230531, installed using Python 3.11.2 - chirp - chirpc jon@jon-notebook:~/Downloads$ pipx uninstall-all uninstalled chirp! ✨ 🌟 ✨ jon@jon-notebook:~/Downloads$ pipx install --system-site-packages ./chirp-20230601-py3-none-any.whl installed package chirp 20230601, installed using Python 3.11.2 These apps are now globally available - chirp - chirpc done! ✨ 🌟 ✨
Any way to upgrade on a flagged system like Ubuntu 23.04 in the future without removing the old one first?
Jon Gauthier - KB1HTW
Thanks for the response, David.
But the instructions as written, do not work for Ubuntu 23.04 (Lunar Lobster). Now, I do realize that 23.04 is not an LTS (long-term-support) version of Ubuntu, so it may have its quirks.
But the upgrade instructions, as written, do not work:
"Once chirp is properly installed, upgrades to newer versions are done with two simple steps:
1. Download the newer .tar.gz file. 2. Run pip install --upgrade ./chirp-<version>.whl (use pipx if you used it above)
First of all, they tell you to download the .tar.gz file instead of the preferred .whl file.
Secondly, pipx does not have a --upgrade option to the "install" verb. Instead, it uses the verb "upgrade". But as I noted in my initial post, when I tried:
"pipx upgrade ./chirp-20230601-py3-none-any.whl"
it responded: "'chirp' already seems to be installed. Not modifying existing installation in '/home/jon/.local/pipx/venvs/chirp'. Pass '--force' to force installation."
I tried the --force option which "seemed" to install chirp successfully, but chirp would not load. The only thing that worked was to explicitly uninstall as I noted in the thread using pipx, then did a fresh install with pipx of the new version.
It may work fine on an LTS version like Ubuntu 22.04 using pip, but with 23.04 using pipx, I had to uninstall the old version first.
73 Jon KB1HTW
Jon,
From: Download - CHIRP (danplanet.com) https://chirp.danplanet.com/projects/chirp/wiki/Download https://chirp.danplanet.com/projects/chirp/wiki/Download
*Upgrading*: You do *NOT *need to uninstall an existing version of CHIRP before installing a newer one. Just install the new one and it will replace the existing copy! However, *be sure to quit CHIRP before installing the new version!*
*The CHIRP team recommends CHIRP-next unless you experience problems with your radio*. If you do, please see How_To_Report_Issues https://chirp.danplanet.com/projects/chirp/wiki/How_To_Report_Issues. 73 David N1EA
On Thu, 2023-06-01 at 15:52 -0400, Jon Gauthier wrote:
Removing the old package and installing the new one worked, but there should be a more "efficient" method...
This worked: jon@jon-notebook:~/Downloads$ pipx list venvs are in /home/jon/.local/pipx/venvs apps are exposed on your $PATH at /home/jon/.local/bin package chirp 20230531, installed using Python 3.11.2 - chirp - chirpc jon@jon-notebook:~/Downloads$ pipx uninstall-all uninstalled chirp! ✨ 🌟 ✨ jon@jon-notebook:~/Downloads$ pipx install --system-site-packages >./chirp-
20230601-py3-none-any.whl
installed package chirp 20230601, installed using Python 3.11.2 These apps are now globally available - chirp - chirpc done! ✨ 🌟 ✨
Any way to upgrade on a flagged system like Ubuntu 23.04 in the future without removing the old one first?
Jon Gauthier - KB1HTW
---------- Forwarded message ---------- From: Jon Gauthier jon@sailbeausoleil.com To: chirp_users@intrepid.danplanet.com Cc: Bcc: Date: Thu, 01 Jun 2023 14:48:07 -0400 Subject: [chirp_users] Upgrading CHIRP on Ubuntu 23.04? When trying to follow the upgrade instructions on the ChirpOnLinux page, there seems to be an error or some information missing.
"Once chirp is properly installed, upgrades to newer versions are done with two simple steps: 1. Download the newer .tar.gz file. 2. Run pip install --upgrade ./chirp-<version>.whl (use pipx if you used it above)"
Since I'm running Ubuntu 23.04, I used "pipx" to install the latest CHIRP. Today, a new version came out so I downloaded the latest .whl version and ran
"pipx install --upgrade ./chirp-20230601-py3-none-any.whl"
But pipx doesn't have a "--upgrade" option to the install verb. If I try pipx without the "--upgrade" option, it tells me:
'chirp' already seems to be installed. Not modifying existing installation in '/home/jon/.local/pipx/venvs/chirp'. Pass '--force' to force installation.
Should I "install --force" it? "pipx reinstall" doesn't work, since the new version isn't installed yet. Should I remove the old package "chirp 20230531" first then install the new one using:
"pipx install --system-site-packages ./chirp-20230601-py3-none- any.whl"?
Jon Gauthier - KB1HTW
But the instructions as written, do not work for Ubuntu 23.04 (Lunar Lobster). Now, I do realize that 23.04 is not an LTS (long-term-support) version of Ubuntu, so it may have its quirks.
It's not just that, it's that as of 23.04, the way python applications are (or can be) installed in a distro-managed python environment has changed fundamentally. This is not something we control nor chose. Since 23.04 (and Debian 11, etc) is the first distro where this new restriction has hit the masses, you can expect some bumps along the way. Feel free to submit your feedback to the distros and python community who have chosen this path for you.
But the upgrade instructions, as written, do not work:
"Once chirp is properly installed, upgrades to newer versions are done with two simple steps:
- Download the newer .tar.gz file.
- Run pip install --upgrade ./chirp-<version>.whl (use pipx if you used it
above)
The command as provided is correct. Since pipx aims (seemingly) to be a stand-in for pip itself, the parenthetical *should* be correct, but clearly isn't.
First of all, they tell you to download the .tar.gz file instead of the preferred .whl file.
...which is fine, you can use either.
Secondly, pipx does not have a --upgrade option to the "install" verb. Instead, it uses the verb "upgrade". But as I noted in my initial post, when I tried:
"pipx upgrade ./chirp-20230601-py3-none-any.whl"
it responded: "'chirp' already seems to be installed. Not modifying existing installation in '/home/jon/.local/pipx/venvs/chirp'. Pass '--force' to force installation."
I tried the --force option which "seemed" to install chirp successfully, but chirp would not load. The only thing that worked was to explicitly uninstall as I noted in the thread using pipx, then did a fresh install with pipx of the new version.
It may work fine on an LTS version like Ubuntu 22.04 using pip, but with 23.04 using pipx, I had to uninstall the old version first.
Sounds like a bug (or quirk) in pipx, but I guess this is how it has to be for the moment. I've updated the instructions. David was echoing the general instructions on the download page that chirp itself has no such requirement, which is correct.
I hope you'll understand that the documenting ever-moving target and spectrum of how python applications are installed on Linux is a challenge. Also, Linux users represent less than two percent of CHIRP's userbase, which means issues with the newest one-month-old distro that has radically changed the landscape should be expected until a critical mass (like yourself) have bumped into them.
--Dan
participants (3)
-
D.J.J. Ring, Jr. -
Dan Smith -
Jon Gauthier