> Note that I did one thing differently. > On fedora I chose to install pip instead of pipx.
Just a reminder that Fedora is the _only_ remaining linux distro on which this still works. It won't work on anything debian-derived (which includes his mint system, ubuntu, etc), arch, gentoo, etc. Even homebrew on macos has gone the externally-managed route. More details about fedora here and on the linked pages: https://discussion.fedoraproject.org/t/status-of-marking-the-base-python-environment-as-externally-managed-pep-668/95164 What I gather is that since fedora's packaging tool is written in python the flag breaks their own stuff in certain situations. Oh the irony :) Either way, we just need to be clear that anyone *not* on fedora will have to run pip with --break-system-packages to make that route work, which I would definitely not recommend. > After closing it I tested the app with the newly installed icon and that > worked as well. Thanks for the extra data point in support of it not being a CHIRP issue :) Given we've had a couple megathreads on Linux issues not specific to chirp lately, I'm hoping we can avoid another one here again since 98% of the subscribers are focused on Windows and MacOS. The build system installs the candidate wheel via pipx as part of the tests it runs, so ideally anything related to that will cause a build abort and it'll get noticed. --Dan _______________________________________________ Users mailing list [email protected] https://lists.chirpmyradio.com/postorius/lists/users.lists.chirpmyradio.com To unsubscribe, send an email to [email protected] To report this email as off-topic, please email [email protected] List archives: https://lists.chirpmyradio.com/hyperkitty/list/[email protected]/
