CHIRP

Enrico,

I just found out that the Stock Config files are not available on CHIRP Snap build. The other builds (Windows, Linux, macOS and flatpak) all have the Stock Config files available. Are you running the Snap build of CHIRP?

I have left a comment about this on the github site of the Snap developer.

Jim KC9HI

Hi!
Yes, unfortunately I was running the snap version. Usually snap distribute the more updated version. Not this time...
Sorry for having opened a issue without double checking that!
Have a nice day!

Hi Enrico,

I can verify that the snap version is missing the %Open stock config% menu option under File.

I'll see why this is happening. Thanks for reporting!

Tony

And I see your issue Jim!

https://github.com/goldstar611/chirp/issues/1

Thanks for the follow up, I appreciate it!

Tony Fuller wrote:

Hi Enrico,

I can verify that the snap version is missing the %Open stock config% menu option under File.

I'll see why this is happening. Thanks for reporting!

Tony

Tony,

Also realize that the snap version is also missing Radio -> Import From Stock Config in case that requires a separate fix.

Thanks,
Jim KC9HI

Hey Jim,

I currently see 2 issues with the snap package.

One is an issues with Dan's build scripts that push changes to github.com, The repo at github.com feeds the snap building and appimage building processes. I emailed Dan and he's seeing the same thing (that commits are present on the mercurial repo but not the github.com repo)

The second is that during the snap build, CHIRP is being installed into / rather than /usr (it's not actually the root of the drive, but the "root of the snap"). So the end result is that CHIRP isn't finding some files including stock configs. On a hunch, I changed my system language and loaded the CHIRP snap and confirmed that translations are not being used.

I have an open question to the snapcrafters forum at https://forum.snapcraft.io/t/python-install-prefix/31248 to see how to set the app installation prefix. Last resort is to just merge the few misplaced directories as a post-build step, but this isn't proper.

Hope that gives some insight into the snap differences.

Tony

Tony,

Thank you for working on this. I typically only use the CHIRP snap build on my Raspberry Pi. I was coaxed by another to install it on a new install of Linux Mint 21 along side of my CHIRP flatpak installation. It was then that I realized that those that were missing the Stock Config file that I wasn't missing must have been using the CHIRP snap build.

As anyone looked to see if the appimage build has this issue or not?

Jim KC9HI

Hey Jim,

I downloaded the AppImage package and checked on the stock configs menu item. It is there.
I also double checked that localization is not broken, it too is working as expected.

I should note that I specify the python install prefix when building the AppImage since I had to manually figure out how to get CHIRP working. https://github.com/goldstar611/chirp-appimage/blob/main/AppImageBuilder.yml#L12
The snap ecosystem has "plugins" for python that, as they say, should just work.

Tony

I believe that tomorrow's CHIRP daily build will include a change that addresses this issue. Right, Tony?

Jim KC9HI

Hi Jim,

That is correct, since https://github.com/kk7ds/chirp/pull/29 was merged. The next build of the snap and appimage should have the stock configs menu option as well as working localization.

And it appears (based solely on commits in the mercurial vs git repos) that Dan has fixed the synchronization issue that was going on between github.com and his local repository which I believe is what this ticket is actually referring to.

Tony