[chirp_users] chirp_users Digest, Vol 177, Issue 9

[Tony Ling]

I discovered today that the 2022 version of CHIRP which did not show under
Synaptic or apt list --installed had been created, and then created under
flatpack. Having done that, that's one step forward, my 2022 legacy CHIRP
is now uninstalled.
I still can't run chirp though
anthony at anthony-System-Product-Name:~$ ~/.local/bin/chirp
Traceback (most recent call last):
  File "/home/anthony/.local/bin/chirp", line 8, in <module>
    sys.exit(chirpmain())
  File
"/home/anthony/.local/lib/python3.10/site-packages/chirp/wxui/__init__.py",
line 65, in chirpmain
    import wx
  File "/home/anthony/.local/lib/python3.10/site-packages/wx/__init__.py",
line 17, in <module>
    from wx.core import *
  File "/home/anthony/.local/lib/python3.10/site-packages/wx/core.py", line
12, in <module>
    from ._core import *
ImportError: libpcre2-32.so.0: cannot open shared object file: No such file
or directory


On Fri, 15 Sept 2023 at 22:23, Jeffrey Vian <sandhillsinvestment at gmail.com>
wrote:

> Chirp is not packaged for specific distros since there would be a lot of
> work involved in making it work for each one and the work would multiply
> for each distro where it was specifically packaged.
>
> As is the intent is for the user to install it using pip and thus it is
> almost universal for installation in every distro out there.
>
> If you wish to take on the task of making packages for specific distros
> then by all means please volunteer.
>
> Most of us are happy that it is available and will work for (almost)
> everyone as it is.  Distribution as a python package and installing it with
> pip is universal in approach and avoids the extra overhead of meeting the
> multiple packaging requirements for various distros.
>
> Jeff
> KI7GJG
>
>
>
> On Fri, Sep 15, 2023 at 3:47 PM Dave B via chirp_users <
> chirp_users at intrepid.danplanet.com> wrote:
>
>> Well Sean.
>>
>> If you read my original post, you'd have seen that the line:-
>>
>>      pipx install --system-site-packages ./chirp-20230509-py3-none-any.whl
>>
>> Is the line in error at this time...
>>
>>
>> As to suggesting to learn how to build a package from the sources...
>>
>> Why is that not already done by the authors/maintainers?
>> Surely they know what's needed better than anyone...
>>
>>
>> 73.
>>
>>      Dave.
>>
>>
>>
>> On 15/09/2023 20:00, chirp_users-request at intrepid.danplanet.com wrote:
>> > From: Sean Dennis
>> > Out of curiosity, what step(s) in those instructions "fail [you] every
>> > time"?
>>
>> --
>> Sent from a MicroSoft free zone:
>>
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users at intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>> This message was sent to sandhillsinvestment at gmail.com at
>> sandhillsinvestment at gmail.com
>> To unsubscribe, send an email to
>> chirp_users-unsubscribe at intrepid.danplanet.com
>> To report this email as off-topic, please email
>> chirp_users-owner at intrepid.danplanet.com
>> Searchable archive:
>> https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
>
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Tony Ling at tonyg7txu at gmail.com
> To unsubscribe, send an email to
> chirp_users-unsubscribe at intrepid.danplanet.com
> To report this email as off-topic, please email
> chirp_users-owner at intrepid.danplanet.com
> Searchable archive:
> https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20230916/b4aed4b6/attachment.html