Unable to launch chirp-next using app icon nor CLI

[apachecai]

I am not able to launch the chirp-next app (KDE Plasma) since a couple months ago after updates. When I clicked the app icon, it tired to load then failed. Please see below for the outcome when I launched in CLI. I hope I can find out why…

Traceback (most recent call last):
File "/usr/bin/chirp", line 8, in <module>
sys.exit(chirpmain())
~~~~~~~~~^^
File "/usr/lib/python3.14/site-packages/chirp/wxui/__init__.py", line 203, in chirpmain
from chirp.wxui import main
File "/usr/lib/python3.14/site-packages/chirp/wxui/main.py", line 49, in <module>
from chirp.wxui import printing
File "/usr/lib/python3.14/site-packages/chirp/wxui/printing.py", line 18, in <module>
import yattag
ModuleNotFoundError: No module named 'yattag'

[ajgringo619]

That time-frame coincides with the upgrade of Python from 3.13 to 3.14. Try rebuilding it; package was updated today.

[apachecai]

No luck…Python has been up-to-date.

[ajgringo619]

So the rebuild of chirp-next didn’t help?

[apachecai]

Do I have to remove the package first then rebuild?

[ajgringo619]

No, but it doesn’t hurt anything. This happens every year when Python releases a new major version. Unfortunately, some AUR packages don’t auto-rebuild like they should.

[apachecai]

Thank you. Can I just do “yay”? Or I have to go through the manual rebuild process?

[ajgringo619]

This EOS thread shows you all you need to know: Rebuilding AUR packages

[apachecai]

Done! Thank you so much!