The mainapp module is used by chirpw, which, as Dan said, is a dead end, and is *not* part of the py3 build that people are working on.
There are lots of issues with the py3 branch right now. It is still a long way from being ready for prime time. There is UI missing, and many drivers have issues and / or have not been tested. It's really not a stable target to be trying to package.
Martin. KD6YAM
On Tue, Nov 15, 2022 at 5:10 AM Barry Jackson via chirp_devel < chirp_devel@intrepid.danplanet.com> wrote:
On 15/11/2022 06:40, Apostolos Kefalas wrote:
Hello Barry,
I really can not understand where this error comes from.
Can you please share your build log?
Have in mind that chirp py3 branch has 2 executables, chirpw.py and
chirpwx.py.
chirpw.py is obsolete and should not be used. chirpwx.py is the way you
should
go.
Also you may want to look at Debian package of chirp which was updated a
few
days ago
https://tracker.debian.org/pkg/chirp
BR Apostolos
Hi Apostolos, Thanks for your reply. I have attached the build log. You will see the offending require on line 950.
I am assuming that this is found by rpm's auto requires somehow.
The only references to it in the sources are in chirp/ui/mainapp.py
[baz@jackodesktop chirp-20221115]$ grep -r GtkosxApplication chirp/ui/mainapp.py: from gi.repository import GtkosxApplication chirp/ui/mainapp.py: macapp = GtkosxApplication.Application()
Any help would be appreciated. Barry
chirp_devel mailing list chirp_devel@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_devel Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers