Re: [chirp_users] Chirp On Puppy Linux
The chirp download site and the linux instructions have all been updated in the last few days. https://chirp.danplanet.com/projects/chirp/wiki/Download and https://chirp.danplanet.com/projects/chirp/wiki/ChirpOnLinux
Dan and I worked together to iron those out for both the Ubuntu/debian versions and the fedora based versions, so those instructions should work on almost all current linux systems using python 3.
Jeff KI7GJG
On Sat, Mar 25, 2023 at 6:25 PM Stuart Longland stuartl@longlandclan.id.au wrote:
On Fri, 17 Mar 2023 20:51:30 -0500 Jeffrey Vian sandhillsinvestment@gmail.com wrote:
I installed python3-pip, then as my user I installed chirp-next as my regular user using pip. Will need to check my notes and verify the steps on a new clean install
of
Fedora 37 and Chirp-next. (you did not note the OS you are running, but
I
assume it is linux.)
Actually, he did in the subject line. The Puppy Linux site is https://puppylinux-woof-ce.github.io/
That said, it appears there's multiple "flavours" of that distribution, some of which are Debian/Ubuntu based and some are Slackware based. (There's a blast from the past! Slackware would be what, 31 years old now?)
So more detail might be needed. Off the top of my head though, I'd check for:
- wxWidgets libraries
- wxPython, if it's compiled, otherwise grab wxWidgets development libraries and a compiler.
- ensure you have `pip` installed for Python 3
The exact commands will differ depending on the base OS being used. Debian/Ubuntu derivatives, one should be able to use `apt`'s commands (i.e. `apt-cache search` / `apt-get install`). For Slackware, you'll need to use Slackware's tools (`pkgtool`).
If all of that is in place, you _should_ be able to run `python3 -m pip install --user requirements.txt` to install the Python module dependencies into your local user's home directory.
Then you should be able to run Chirp with `./chirpwx.py`, or install it into your home directory with `python3 setup.py install --user`. -- Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind... ...it's backed up on a tape somewhere.
Thank you Jeffrey Stuart Martin Dave B Jim For your help with my problem. The flavor of puppy Linux I am using is the Ubuntu derivative called Fossapup. Puppy does not have the apt command. In order to install libraries/packages you use the puppy package manager to search and install packages from the Ubuntu depositories. I think I have installed all the libraries I need.
I would like to run chirp from the command line with the following command. Python3 Chirpw.py Or Python3 chirpwx.py
Which ever is the new file name. In the chirp-20230328.tar.gz file that I downloaded and extracted does not have chirpw.py or chirpwx.py
Is it no longer possible to run chirp via the python interpreter running the source code like you were able to run the legacy python 2 version of chirp?
Again thank you all for your help. It is greatly appreciated.
Best regards John
On Sat, Mar 25, 2023 at 9:25 PM Jeffrey Vian sandhillsinvestment@gmail.com wrote:
The chirp download site and the linux instructions have all been updated in the last few days. https://chirp.danplanet.com/projects/chirp/wiki/Download and https://chirp.danplanet.com/projects/chirp/wiki/ChirpOnLinux
Dan and I worked together to iron those out for both the Ubuntu/debian versions and the fedora based versions, so those instructions should work on almost all current linux systems using python 3.
Jeff KI7GJG
On Sat, Mar 25, 2023 at 6:25 PM Stuart Longland < stuartl@longlandclan.id.au> wrote:
On Fri, 17 Mar 2023 20:51:30 -0500 Jeffrey Vian sandhillsinvestment@gmail.com wrote:
I installed python3-pip, then as my user I installed chirp-next as my regular user using pip. Will need to check my notes and verify the steps on a new clean
install of
Fedora 37 and Chirp-next. (you did not note the OS you are running,
but I
assume it is linux.)
Actually, he did in the subject line. The Puppy Linux site is https://puppylinux-woof-ce.github.io/
That said, it appears there's multiple "flavours" of that distribution, some of which are Debian/Ubuntu based and some are Slackware based. (There's a blast from the past! Slackware would be what, 31 years old now?)
So more detail might be needed. Off the top of my head though, I'd check for:
- wxWidgets libraries
- wxPython, if it's compiled, otherwise grab wxWidgets development libraries and a compiler.
- ensure you have `pip` installed for Python 3
The exact commands will differ depending on the base OS being used. Debian/Ubuntu derivatives, one should be able to use `apt`'s commands (i.e. `apt-cache search` / `apt-get install`). For Slackware, you'll need to use Slackware's tools (`pkgtool`).
If all of that is in place, you _should_ be able to run `python3 -m pip install --user requirements.txt` to install the Python module dependencies into your local user's home directory.
Then you should be able to run Chirp with `./chirpwx.py`, or install it into your home directory with `python3 setup.py install --user`. -- Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind... ...it's backed up on a tape somewhere.
On Tue, 28 Mar 2023 12:24:07 -0400 John KB2SCS kb2scsjb@gmail.com wrote:
For your help with my problem. The flavor of puppy Linux I am using is the Ubuntu derivative called Fossapup. Puppy does not have the apt command. In order to install libraries/packages you use the puppy package manager to search and install packages from the Ubuntu depositories. I think I have installed all the libraries I need.
Okay, bit strange… Ubuntu is a Debian derivative, therefore uses `apt`, so as an Ubuntu derivative, there should be an `apt` binary installed.
But, I digress…
I would like to run chirp from the command line with the following command. Python3 Chirpw.py Or Python3 chirpwx.py
Okay, watch case sensitivity here; most installs on Python (even on Windows) use a lower case `python`, and all Linux distributions are case-sensitive. `python3` should work, but `Python3` will likely yield a "command not found".
Similarly with file names; `Chirpw.py` won't work if the file is actually called `chirpw.py`. I know it sounds pedantic, but on Unix variants, it matters.
Which ever is the new file name. In the chirp-20230328.tar.gz file that I downloaded and extracted does not have chirpw.py or chirpwx.py
Is it no longer possible to run chirp via the python interpreter running the source code like you were able to run the legacy python 2 version of chirp?
The git repository does have a `chirpwx.py`. This seems to not be distributed in the tarball. That said, you can still run Chirp from the unpacked tarball:
I downloaded https://trac.chirp.danplanet.com/chirp_next/next-20230328/chirp-20230328.tar... -- for reference, here's the checksum to confirm you got the same file I did.
$ sha256sum /tmp/chirp-20230328.tar.gz 5e4ce5f2eef80fec7a5d7e47383c99957c16a31df2f8b4a705fab0c50090ce5a /tmp/chirp-20230328.tar.gz
I unpacked it with `tar -xzf chirp-20230328.tar.gz`; that created a `chirp-20230328` sub-directory. Indeed, if I enter that directory and do a `ls`, there's no `chirpwx.py`. I had a look though, there's a `chirp/wxui` sub-directory though, so I tried:
$ python3 -m chirp.wxui
The Chirp window appeared. So you might be able to run it that way.
That said, the safer approach may be to run `python3 setup.py install --user` and run it via whatever scripts that creates in your `~/.local/bin` directory (or via desktop icons).
Thank You All The amount of help that i got was and is amazing. Thank you one and all. Success! Chirp now works just fine on my Puppy Linux system.
Again thank you so much.
Best Regards John
On Tue, Mar 28, 2023 at 6:02 PM Stuart Longland VK4MSL me@vk4msl.id.au wrote:
On Tue, 28 Mar 2023 12:24:07 -0400 John KB2SCS kb2scsjb@gmail.com wrote:
For your help with my problem. The flavor of puppy Linux I am using is
the
Ubuntu derivative called Fossapup. Puppy does not have the apt command. In order to install
libraries/packages
you use the puppy package manager to search and install packages from the Ubuntu depositories. I think I have installed all the libraries I need.
Okay, bit strange… Ubuntu is a Debian derivative, therefore uses `apt`, so as an Ubuntu derivative, there should be an `apt` binary installed.
But, I digress…
I would like to run chirp from the command line with the following
command.
Python3 Chirpw.py Or Python3 chirpwx.py
Okay, watch case sensitivity here; most installs on Python (even on Windows) use a lower case `python`, and all Linux distributions are case-sensitive. `python3` should work, but `Python3` will likely yield a "command not found".
Similarly with file names; `Chirpw.py` won't work if the file is actually called `chirpw.py`. I know it sounds pedantic, but on Unix variants, it matters.
Which ever is the new file name. In the chirp-20230328.tar.gz file that I downloaded and extracted does not have chirpw.py or
chirpwx.py
Is it no longer possible to run chirp via the python interpreter running the source code like you were able to run the legacy python 2 version of chirp?
The git repository does have a `chirpwx.py`. This seems to not be distributed in the tarball. That said, you can still run Chirp from the unpacked tarball:
I downloaded
https://trac.chirp.danplanet.com/chirp_next/next-20230328/chirp-20230328.tar... -- for reference, here's the checksum to confirm you got the same file I did.
$ sha256sum /tmp/chirp-20230328.tar.gz 5e4ce5f2eef80fec7a5d7e47383c99957c16a31df2f8b4a705fab0c50090ce5a /tmp/chirp-20230328.tar.gz
I unpacked it with `tar -xzf chirp-20230328.tar.gz`; that created a `chirp-20230328` sub-directory. Indeed, if I enter that directory and do a `ls`, there's no `chirpwx.py`. I had a look though, there's a `chirp/wxui` sub-directory though, so I tried:
$ python3 -m chirp.wxui
The Chirp window appeared. So you might be able to run it that way.
That said, the safer approach may be to run `python3 setup.py install --user` and run it via whatever scripts that creates in your `~/.local/bin` directory (or via desktop icons). -- Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind... ...it's backed up on a tape somewhere.
participants (3)
-
Jeffrey Vian -
John KB2SCS -
Stuart Longland VK4MSL