[chirp_users] chirp flatpak (In need of a few brave souls)
Well thanks to the help and pointers here I was able to navigate the truly atrocious documentation for flatpaks and was able to create a bundle. I need a few brave souls to test:
https://hobbes1069.fedorapeople.org/chirp-20200430.flatpak
I put the version in the name, so be careful, if I update it it, you could install more than one version. I still have yet to learn how you update flatpak packages.
I went through and did a "cleanup" of a lot of files we don't actually need. The original version was ~140MB...
It should be practical to get it listed on flathub. The archives are called "daily" but really it's whenever something significant has been committed and the date is the version.
Let me know if it works fine or needs some fixes.
Thanks, Richard KF5OIM
On 5/1/20 8:24 PM, Richard Shaw wrote:
still have yet to learn how you update flatpak packages.
That'd be with an OSTree repository. Essentially, it's a package/Git repository hybrid. Check the .gitlab-ci.yml file in my repo for an example of how to push to one. It's been a couple years since I did that work, so I really don't remember the specifics.
Someone then adds your repository and installs CHIRP from there. Alternatively, you can try to get it into Flathub if they'll accept non-daily builds, or find some other package repository to commit to. Flathub and Fedora are the only ones I know of.
Richard,
I did a live boot with Ubuntu 20.04, apt installed flatpak, added the runtime and installed your flatpak file. Success! I had Chirp running on Ubuntu 20.04 in under 10 minutes! And I was able to download and upload to several of the older Baofeng 888 radios and a Radioddity GA-2S (same driver in chirp).
Some notes on your current flatpak: - Chirp needs network access for the online repeater database and to check for updates - Chirp complains (when launched from the console) that 2 drivers need python-future package
I did some more modifications to my flatpak file and here's what I found: - pygtk fails to compile with gnome Sdk version 3.36 but compiles on 3.26. gnome Sdk 3.30 is unsupported for some reason. - I'll look into how to get things working on a newer version - I have no idea where to find a "list" of available versions but did find the upstream repository on gitlab - https://gitlab.gnome.org/GNOME/gnome-build-meta - Removed all the pip related stuff - Added python-future - Nolan's repo has a lot of stuff mine is missing. - Like a desktop shortcut
https://gist.github.com/goldstar611/cb0037ee29ae315bb2f0211e69d95799/revisio...
Tony
On Fri, 2020-05-01 at 20:24 -0500, Richard Shaw wrote:
Well thanks to the help and pointers here I was able to navigate the truly atrocious documentation for flatpaks and was able to create a bundle. I need a few brave souls to test:
https://hobbes1069.fedorapeople.org/chirp-20200430.flatpak
I put the version in the name, so be careful, if I update it it, you could install more than one version. I still have yet to learn how you update flatpak packages.
I went through and did a "cleanup" of a lot of files we don't actually need. The original version was ~140MB...
It should be practical to get it listed on flathub. The archives are called "daily" but really it's whenever something significant has been committed and the date is the version.
Let me know if it works fine or needs some fixes.
Thanks, Richard KF5OIM _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tony F at goldstar611@hotmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Fri, May 1, 2020 at 9:09 PM goldstar611@hotmail.com wrote:
Richard,
I did a live boot with Ubuntu 20.04, apt installed flatpak, added the runtime and installed your flatpak file. Success! I had Chirp running on Ubuntu 20.04 in under 10 minutes! And I was able to download and upload to several of the older Baofeng 888 radios and a Radioddity GA-2S (same driver in chirp).
Good deal!
Some notes on your current flatpak:
- Chirp needs network access for the online repeater database and to check
for updates
Added, for the next version.
- Chirp complains (when launched from the console) that 2 drivers need
python-future package
Ok, I'll add that with pip.
I did some more modifications to my flatpak file and here's what I found:
- pygtk fails to compile with gnome Sdk version 3.36 but compiles on 3.26.
gnome Sdk 3.30 is unsupported for some reason.
- I'll look into how to get things working on a newer version
I'm using 3.28 as the current target. I'm not sure I really need to be using the gnome sdk over the regular freedesktop sdk but I inherited that with the json file.
- Nolan's repo has a lot of stuff mine is missing.
- Like a desktop shortcut
Mine should show a desktop shortcut. It worked with a local repo install.
Thanks, Richard
Ok, new package with the following changes:
Changed to org.gnome.Platform//3.32
This is the LATEST that can be used, if you go any higher pygtk2 won't build, which a WHOLE other topic. Chirp really needs to be migrated to Gtk3.
Updated to the latest version of libxml2. Probably doesn't matter one bit, but the previous version was being downloaded from debian or something.
$ curl -LO https://hobbes1069.fedorapeople.org/chirp-20200430.flatpak $ flatpak uninstall chirp $ flatpak install chirp-20200430.flatpak
Thanks, Richard
Incoming feedback on the flatpak via CHIRP Issues page:
"I've followed your suggestions and everything works now. Thank you so much ;-)" https://chirp.danplanet.com/issues/7837#change-24349
"Hello there, [m]any thanks for a solution. At this moment Chirp is running, with the use of flatpak." https://chirp.danplanet.com/issues/7871
There's no specific radio model usage in those issues but it I'll see if I can get those data points.
Tony ________________________________ From: chirp_users-bounces@intrepid.danplanet.com chirp_users-bounces@intrepid.danplanet.com on behalf of Richard Shaw hobbes1069@gmail.com Sent: Sunday, May 3, 2020 5:37 PM To: Discussion of CHIRP chirp_users@intrepid.danplanet.com Subject: Re: [chirp_users] chirp flatpak (In need of a few brave souls)
Ok, new package with the following changes:
Changed to org.gnome.Platform//3.32
This is the LATEST that can be used, if you go any higher pygtk2 won't build, which a WHOLE other topic. Chirp really needs to be migrated to Gtk3.
Updated to the latest version of libxml2. Probably doesn't matter one bit, but the previous version was being downloaded from debian or something.
$ curl -LO https://hobbes1069.fedorapeople.org/chirp-20200430.flatpak $ flatpak uninstall chirp $ flatpak install chirp-20200430.flatpak
Thanks, Richard
I don't understand all this "flat pack" stuff. I may be setting up Ubuntu live on a USB stick for someone with Chirp on it. Will still do like always, add the repository and then install the daily? Glenn ----- Original Message ----- From: "Phil" phillor9@gmail.com To: chirp_users@intrepid.danplanet.com Sent: Tuesday, May 12, 2020 11:30 PM Subject: Re: [chirp_users] chirp flatpak (In need of a few brave souls)
On 12/5/20 11:39 am, Tony Fuller wrote:
Incoming feedback on the flatpak via CHIRP Issues page:
Excellent work, and I can confirm that the Baofeng UV-82III works under Kububtu 20.04.
On Tue, May 12, 2020 at 11:37 PM Glenn K0LNY glennervin@cableone.net wrote:
I don't understand all this "flat pack" stuff.
Many distros are removing Python 2 as it was EOL'd at the end of last year. Chirp is not ready for Python 3 yet so that leaves us in a bit of a bind. A flatpak (no c) is an application that runs in a completely separate sandbox and all the dependencies are in the sandbox with it so it allows systems without Python 2 (and the python 2 dependencies) to be run on a system which has no Python 2.
Thanks, Richard KF5OIM
Isn't it easier to just linstall Python 2 from an older distro?
On 13 May 2020 at 07:40 Richard Shaw hobbes1069@gmail.com wrote:
On Tue, May 12, 2020 at 11:37 PM Glenn K0LNY < glennervin@cableone.net mailto:glennervin@cableone.net > wrote: > > I don't understand all this "flat pack" stuff.>Many distros are removing Python 2 as it was EOL'd at the end of last year. Chirp is not ready for Python 3 yet so that leaves us in a bit of a bind. A flatpak (no c) is an application that runs in a completely separate sandbox and all the dependencies are in the sandbox with it so it allows systems without Python 2 (and the python 2 dependencies) to be run on a system which has no Python 2. Thanks, Richard KF5OIM _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Nigel A. Gunn, ///shoulders.outwards.resolutions tel +1 937 825 5032 Amateur Radio G8IFF W8IFF and GMRS WRBV701, e-mail nigel@ngunn.net www http://www.ngunn.net
On 5/13/20 7:19 AM, Nigel A. Gunn G8IFF/W8IFF wrote:
Isn't it easier to just linstall Python 2 from an older distro?
That option is certainly still open to you, but for my part, I'd rather just "flatpak repo add ..." and "flatpak install". At that point, there's no risk that a distro update will break the almost certainly unsupported older installation of Python.
Will the end user notice any difference?
----- Original Message ----- From: Richard Shaw To: Discussion of CHIRP Sent: Wednesday, May 13, 2020 6:40 AM Subject: Re: [chirp_users] chirp flatpak (In need of a few brave souls)
On Tue, May 12, 2020 at 11:37 PM Glenn K0LNY glennervin@cableone.net wrote:
I don't understand all this "flat pack" stuff.
Many distros are removing Python 2 as it was EOL'd at the end of last year. Chirp is not ready for Python 3 yet so that leaves us in a bit of a bind. A flatpak (no c) is an application that runs in a completely separate sandbox and all the dependencies are in the sandbox with it so it allows systems without Python 2 (and the python 2 dependencies) to be run on a system which has no Python 2.
Thanks, Richard KF5OIM
--------------------------------------------------------------------------------
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Glenn at glennervin@cableone.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Wed, May 13, 2020 at 9:44 AM Glenn K0LNY glennervin@cableone.net wrote:
Will the end user notice any difference?
If setup correctly, not really. It looks and works the same.
As to the "if setup correctly" part, since flatpaks run in a sandbox/container, you have to tell it what access it has to the host system, for instance, for the chirp flatpak:
"finish-args": [ "--share=ipc", "--share=network", "--socket=x11", "--socket=wayland", "--filesystem=home", "--device=all"
The ipc, x11, and wayland are needed for a GUI application (you can have command line flatpaks as well), the network is needed for downloading things ike Radio Reference, "home" gives the application access to the home directory and "device=all" is needed for access to serial ports.
Thanks, Richard
What are the steps now for installing Chirp? I mean, will I have to do a bunch of cryptic Linux commands to get it installed in the CLI?
----- Original Message ----- From: Richard Shaw To: Discussion of CHIRP Sent: Wednesday, May 13, 2020 10:07 AM Subject: Re: [chirp_users] chirp flatpak (In need of a few brave souls)
On Wed, May 13, 2020 at 9:44 AM Glenn K0LNY glennervin@cableone.net wrote:
Will the end user notice any difference?
If setup correctly, not really. It looks and works the same.
As to the "if setup correctly" part, since flatpaks run in a sandbox/container, you have to tell it what access it has to the host system, for instance, for the chirp flatpak:
"finish-args": [ "--share=ipc", "--share=network", "--socket=x11", "--socket=wayland", "--filesystem=home", "--device=all"
The ipc, x11, and wayland are needed for a GUI application (you can have command line flatpaks as well), the network is needed for downloading things ike Radio Reference, "home" gives the application access to the home directory and "device=all" is needed for access to serial ports.
Thanks, Richard
--------------------------------------------------------------------------------
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Glenn at glennervin@cableone.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Wed, May 13, 2020 at 10:11 AM Glenn K0LNY glennervin@cableone.net wrote:
What are the steps now for installing Chirp? I mean, will I have to do a bunch of cryptic Linux commands to get it installed in the CLI?
Depends on how your distro manages flatpaks. The command line "flatpak install ..." method is certainly available but at least on Fedora it also integrates with the Software app IF the flatpak is in a repo.
Currently I'm only providing a standalone file. Additionally I have the chirp version in the filename which is both a good and bad thing.
I'ts good because you know what version you're installed, it's bad because you could potentially install multiple versions since they have different names. I haven't tested this yet.
Short term you can remove the old version before installing the new version. Medium term I can look at getting it into a public Flatpak repo.
Long term the solution HAS to be to get chirp running on Python 3 / Gtk 3.
Thanks, Richard
How about automatic updates from the repo?
On 13 May 2020 at 11:07 Richard Shaw hobbes1069@gmail.com wrote:
On Wed, May 13, 2020 at 9:44 AM Glenn K0LNY < glennervin@cableone.net mailto:glennervin@cableone.net > wrote: > > Will the end user notice any difference?>If setup correctly, not really. It looks and works the same. As to the "if setup correctly" part, since flatpaks run in a sandbox/container, you have to tell it what access it has to the host system, for instance, for the chirp flatpak: "finish-args": [ "--share=ipc", "--share=network", "--socket=x11", "--socket=wayland", "--filesystem=home", "--device=all" The ipc, x11, and wayland are needed for a GUI application (you can have command line flatpaks as well), the network is needed for downloading things ike Radio Reference, "home" gives the application access to the home directory and "device=all" is needed for access to serial ports. Thanks, Richard _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Nigel Gunn, W8IFF at nigel@ngunn.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Nigel A. Gunn, ///shoulders.outwards.resolutions tel +1 937 825 5032 Amateur Radio G8IFF W8IFF and GMRS WRBV701, e-mail nigel@ngunn.net www http://www.ngunn.net
participants (7)
-
Glenn K0LNY -
goldstar611＠hotmail.com -
Nigel A. Gunn G8IFF/W8IFF -
Nolan Darilek -
Phil -
Richard Shaw -
Tony Fuller