[chirp_users] Chirp installation under Ubuntu error messages
I believe that I have all of the required dependencies installed but perhaps I've missed something.
:~/.local/bin$ ./chirp Traceback (most recent call last): File "/home/phil/.local/bin/./chirp", line 33, in <module> sys.exit(load_entry_point('chirp===py3-20221124', 'console_scripts', 'chirp')()) File "/home/phil/.local/bin/./chirp", line 25, in importlib_load_entry_point return next(matches).load() File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 171, in load module = import_module(match.group('module')) File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1050, in _gcd_import File "<frozen importlib._bootstrap>", line 1027, in _find_and_load File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 688, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 883, in exec_module File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed File "/home/phil/.local/lib/python3.10/site-packages/chirp/wxui/__init__.py", line 6, in <module> from chirp import directory File "/home/phil/.local/lib/python3.10/site-packages/chirp/directory.py", line 26, in <module> from chirp.drivers import icf # , rfinder File "/home/phil/.local/lib/python3.10/site-packages/chirp/drivers/__init__.py", line 1, in <module> from chirp.drivers import vx5 File "/home/phil/.local/lib/python3.10/site-packages/chirp/drivers/vx5.py", line 164, in <module> @directory.register AttributeError: partially initialized module 'chirp.directory' has no attribute 'register' (most likely due to a circular import)
I believe that I have all of the required dependencies installed but perhaps I've missed something.
:~/.local/bin$ ./chirp Traceback (most recent call last): File "/home/phil/.local/bin/./chirp", line 33, in <module> sys.exit(load_entry_point('chirp===py3-20221124',
This looks like you have some super old version installed? Or possibly a mix of two...
Probably better to open a bug for this in case it turns into something actionable so I can reference a fix against it.
--Dan
On 15/1/23 10:16, Dan Smith via chirp_users wrote: :~/.local/bin$ ./chirp
Traceback (most recent call last): File "/home/phil/.local/bin/./chirp", line 33, in <module> sys.exit(load_entry_point('chirp===py3-20221124',
This looks like you have some super old version installed? Or possibly a mix of two...
I did have an old version that I removed with apt and I did have a a flatpak version that I think I had removed some time ago. I'll check.
Probably better to open a bug for this in case it turns into something actionable so I can reference a fix against it.
This has probably been answered many times, how does one submit a bug report? On git hub I suppose.
I did have an old version that I removed with apt and I did have a a flatpak version that I think I had removed some time ago. I'll check.
The flatpak would be completely isolated from this, so that's not related. And definitely no apt package was going to be installing that super old version into python 3.10, and in your home directory.
This has probably been answered many times, how does one submit a bug report? On git hub I suppose.
File a bug here:
https://chirp.danplanet.com/projects/chirp/issues/new
That way we can figure out where you got what you're installing, how you're installing it, and what you had before to try to get you squared away.
--Dan
On 15/1/23 10:32, Dan Smith via chirp_users wrote:
The flatpak would be completely isolated from this, so that's not related.
Of course, silly me. I did purge a version of chirp but I didn't take notice of the version.
There's a warning and "Failed to build chirp" message in the following. However, chirp was uninstalled and installed again. Could there be a problem here?
:~/Downloads$ pip3 install chirp-py3-20221124.tar.gz Defaulting to user installation because normal site-packages is not writeable Processing ./chirp-py3-20221124.tar.gz Preparing metadata (setup.py) ... done Building wheels for collected packages: chirp Building wheel for chirp (setup.py) ... done Created wheel for chirp: filename=chirp-py3_20221124-py3-none-any.whl size=1316229 sha256=f6483be358e15758c5c82433e084da4cc324fb70d4c3742c532c091708a261df Stored in directory: /home/phil/.cache/pip/wheels/49/60/45/a1010353ccfe93bd68f36b46006636fd3be5a18be125fb6cc0 WARNING: Built wheel for chirp is invalid: Metadata 1.2 mandates PEP 440 version, but 'py3-20221124' is not Failed to build chirp Installing collected packages: chirp Attempting uninstall: chirp Found existing installation: chirp py3-20221124 Uninstalling chirp-py3-20221124: Successfully uninstalled chirp-py3-20221124 Running setup.py install for chirp ... done DEPRECATION: chirp was installed using the legacy 'setup.py install' method, because a wheel could not be built for it. pip 23.1 will enforce this behaviour change. A possible replacement is to fix the wheel build issue reported above. Discussion can be found at https://github.com/pypa/pip/issues/8368 Successfully installed chirp-py3-20221124
File a bug here:
https://chirp.danplanet.com/projects/chirp/issues/new
That way we can figure out where you got what you're installing, how you're installing it, and what you had before to try to get you squared away.
I'll delay submitting a bug report in case I've made an error with the installation.
:~/Downloads$ pip3 install chirp-py3-20221124.tar.gz
This is insanely old (in chirp-next time frames). You should be using the latest from here:
https://trac.chirp.danplanet.com/chirp_next/
Looks like you're going to the bottom to get the first, but that's the oldest. Purge again and get today's build.
--Dan
Silly me again Dan, sorry to have bothered you.
No worries, I was wondering where you got that old tarball until I realized it was the oldest build dir. We can blame Rich NE1EE for *forcing* me to reverse the sort in that directory. Just kidding Rich, it was the right call :)
So you're good now?
--Dan
On 2023-01-14 17:44:-0800, you wrote:
Silly me again Dan, sorry to have bothered you.
No worries, I was wondering where you got that old tarball until I realized it was the oldest build dir. We can blame Rich NE1EE for *forcing* me to reverse the sort in that directory. Just kidding Rich, it was the right call :)
So you're good now?
--Dan
I skim all the posts from CHIRP, looking for keywords that suggest the post might be of interest. For *nix posts, it is usually a few seconds, then hit delete. I havta admit that I focussed on "Rich NE1EE" , them promptly found "blame" on the double-take...but it took 3 passes to understand Dan's humorous post! I am quite the jokester, so I appreciated the heart hiccup and the smile this brought to me during my morning skim of ham-related emails. Thanks for all the hard work, CHIRP crew!
~R~ 72/73 de Rich NE1EE The Dusty Key On the banks of the Piscataqua
participants (3)
-
Dan Smith -
Phil -
Rich NE1EE