Re: [chirp_users] ARM Distribution?
I use chirp on a pi 2 without problem. Downlod the version for linux.
Sent from my Samsung Galaxy Tab®4
-------- Original message -------- From: patrick@ogrd.net Date:04/07/2016 9:34 AM (GMT-04:00) To: chirp_users@intrepid.danplanet.com Subject: [chirp_users] ARM Distribution?
I've got a little Raspberry Pi 2 (ARM) computer setup with UbuntMATE, and when I went to install everything I ran into problems, however we did work it out. Either way I just wanted to bring this bit to the table to request a version of CHIRP for ARM. Also, as much as I can tell what I've got setup is a text-based Python program, and documentation is slim; is there more documentation somewhere else where I'm not looking?
DItto. I just installed CHIRP on my Pi-2 (OS=raspbian/wheezy) by running:
sudo apt-get install chirp
and it works perfectly with my Boafeng UV-5R.
Assuming you are using a std "USB programming cable", be sure to choose the proper /dev/ttyUSBx serial port (/dev/ttyUSB0, on my Pi-2), and select the correct make & model for your HT.
On Thu, Apr 7, 2016 at 5:41 PM, NP3AR NP3AR@gmx.com wrote:
I use chirp on a pi 2 without problem. Downlod the version for linux.
Sent from my Samsung Galaxy Tab®4
-------- Original message -------- From: patrick@ogrd.net Date:04/07/2016 9:34 AM (GMT-04:00) To: chirp_users@intrepid.danplanet.com Subject: [chirp_users] ARM Distribution?
I've got a little Raspberry Pi 2 (ARM) computer setup with UbuntMATE, and when I went to install everything I ran into problems, however we did work it out. Either way I just wanted to bring this bit to the table to request a version of CHIRP for ARM. Also, as much as I can tell what I've got setup is a text-based Python program, and documentation is slim; is there more documentation somewhere else where I'm not looking?
-- http://www.ogrd.net _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to joe at np3ar@gmx.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dave Knight at diemkae@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
DItto. I just installed CHIRP on my Pi-2 (OS=raspbian/wheezy) by running:
sudo apt-get install chirp
and it works perfectly with my Boafeng UV-5R.
Just so you know, the chirp package you're getting is beyond ancient. Like, crusty petrified old :)
If you're not installing chirp-daily from the PPA, or installing from the tarball, then you're probably getting 0.3.x or 0.4.x which is...OLD. :)
--Dan
Yes.
dpkg -l chirp
tells me:
||/ Name Version Architecture Description +++-==================-==============-==============-========================================= ii chirp 0.1.12-1 armhf Configuration tool for amateur radios
chirpw --version says:
CHIRP daily-20160201 on Linux - Raspbian GNU/Linux 7 (Python 2.7.3)
On one of my Linux laptops, chirpw --version reveals:
CHIRP 0.3.1 on Linux - Ubuntu 14.04.4 LTS (Python 2.7.6)
On Thu, Apr 7, 2016 at 7:23 PM, Dan Smith dsmith@danplanet.com wrote:
DItto. I just installed CHIRP on my Pi-2 (OS=raspbian/wheezy) by
running:
sudo apt-get install chirp
and it works perfectly with my Boafeng UV-5R.
Just so you know, the chirp package you're getting is beyond ancient. Like, crusty petrified old :)
If you're not installing chirp-daily from the PPA, or installing from the tarball, then you're probably getting 0.3.x or 0.4.x which is...OLD. :)
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Dave Knight at diemkae@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Is running the latest daily really the only way to get an up to date and usable version of chirp? Is it really all that impossible to make a versioned release every now and then? It would certainly be easier on your non-ubuntu users if their distros had a fighting chance.
-Zero
On 04/07/2016 07:23 PM, Dan Smith wrote:
DItto. I just installed CHIRP on my Pi-2 (OS=raspbian/wheezy) by running:
sudo apt-get install chirp
and it works perfectly with my Boafeng UV-5R.
Just so you know, the chirp package you're getting is beyond ancient. Like, crusty petrified old :)
If you're not installing chirp-daily from the PPA, or installing from the tarball, then you're probably getting 0.3.x or 0.4.x which is...OLD. :)
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Rick Farina at sidhayn@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
I do know that if Chirp was willing to release "official" versions more often, many of the Distro packaging systems would automatically recognize, download, and package it for both their next major distro release but also for some of their bleeding edge repos as well. Btw, this is a very similar issue for Xastir as well who is constantly releasing new code but only to their SCM only. They haven't made an official release since September 2014.
--David KI6ZHD
I do know that if Chirp was willing to release "official" versions more often, many of the Distro packaging systems would automatically recognize, download, and package it for both their next major distro release but also for some of their bleeding edge repos as well.
Most distros require manual intervention for this. There is, of course, no difference between the daily builds and something more "official". Our official builds are daily builds. Please back up your assertions.
Note that fedora clearly is building automatically from our daily builds, and whenever they come out:
https://apps.fedoraproject.org/packages/chirp
--Dan
It seems so much easier to just download the OS X version and drop the single .app file into the Applications folder.
On Apr 8, 2016, at 5:18 PM, Dan Smith dsmith@danplanet.com wrote:
I do know that if Chirp was willing to release "official" versions more often, many of the Distro packaging systems would automatically recognize, download, and package it for both their next major distro release but also for some of their bleeding edge repos as well.
Most distros require manual intervention for this. There is, of course, no difference between the daily builds and something more "official". Our official builds are daily builds. Please back up your assertions.
Note that fedora clearly is building automatically from our daily builds, and whenever they come out:
https://apps.fedoraproject.org/packages/chirp
--Dan _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Fred at _chirp@mail2fm.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Hey Dan,
Most distros require manual intervention for this.
I think some distros are changing a bit here.. but it really depends on their policies. Seems Debian is using the 11 month old 0.4.0 release:
https://packages.debian.org/source/jessie/chirp
What they DO have is crawlers that notify the maintainer if new releases have been published. You'll definitely get more modern versions of Chirp included with distros if you publish more "official" versions. Just think.. you can run Chirp on an IBM S390 or PowerPC! Woohoo!
There is, of course, no difference between the daily builds and something more "official". Our official builds are daily builds. Please back up your assertions. Note that fedora clearly is building automatically from our daily builds, and whenever they come out: https://apps.fedoraproject.org/packages/chirp
IF you look at https://apps.fedoraproject.org/packages/chirp , you'll see that only their bleeding edge repo, Rawhide, gets the dailies. All the other distros seem to get hand-selected versions (seems to be the 02/29/16 version) for whatever reason.
--David
Debian emphasizes stability over having the latest versions. Once there is a package freeze prior to a new release, unless there are serious problems nothing will be updated until it is time for the next release, which is often more than a year. The "testing" version is somewhat more up-to-date, while "unstable" will be even more so, but can still lag far behind the dailies.
Bob, N7XY
On 4/8/16 8:18 PM, David Ranch wrote:
Hey Dan,
Most distros require manual intervention for this.
I think some distros are changing a bit here.. but it really depends on their policies. Seems Debian is using the 11 month old 0.4.0 release:
https://packages.debian.org/source/jessie/chirpWhat they DO have is crawlers that notify the maintainer if new releases have been published. You'll definitely get more modern versions of Chirp included with distros if you publish more "official" versions. Just think.. you can run Chirp on an IBM S390 or PowerPC! Woohoo!
There is, of course, no difference between the daily builds and something more "official". Our official builds are daily builds. Please back up your assertions. Note that fedora clearly is building automatically from our daily builds, and whenever they come out: https://apps.fedoraproject.org/packages/chirp
IF you look at https://apps.fedoraproject.org/packages/chirp , you'll see that only their bleeding edge repo, Rawhide, gets the dailies. All the other distros seem to get hand-selected versions (seems to be the 02/29/16 version) for whatever reason.
--David _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Bob Nielsen at n7xy@n7xy.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
I think some distros are changing a bit here.. but it really depends on their policies. Seems Debian is using the 11 month old 0.4.0 release:
No, 0.4.0 was released on 3/24/2014. That's over two years old. Also, 0.4.1 is the latest supposed stable release and was for over a year, but they never picked it up, despite known radio-harming bugs in 0.4.0.
What they DO have is crawlers that notify the maintainer if new releases have been published. You'll definitely get more modern versions of Chirp included with distros if you publish more "official" versions. Just think.. you can run Chirp on an IBM S390 or PowerPC! Woohoo!
Sorry, but I completely don't buy this. What will get more recent updates into the distros is people stepping up to maintain the packages. The only person I see even offering to do that here is Rick.
Rick, I'm not going to maintain a separate stable branch in mercurial, which means any random release in time is the most stable until the next one. If you want to just pick the first release in a given calendar month or calendar quarter and package that, that seems reasonable and I'll be glad to try and help with directory structure or notifications if you want. That said, I don't really think there's any reason to choose an arbitrary partitioning scheme, and would rather you just script/cron the process, or do it when you have spare time on a Saturday.
Anyway, to summarize:
The automatic builds are the only official builds. Distros are welcome to pick them up automatically every time they're published, or on some other arbitrary schedule. Ubuntu users will continue to get automatic updates along with all the rest of their system updates via the PPA the day of the release.
--Dan
Is running the latest daily really the only way to get an up to date and usable version of chirp? Is it really all that impossible to make a versioned release every now and then?
It's certainly not, but it's not very useful either. Since we don't merge things that we know are broken, there's no need to maintain a stable branch. That makes the main branch the most stable one all the time. That means you're free to grab a snapshot at any time, package it for your distro and repeat in whatever your desired interval is. If you'd like to build some automation around it for your distro like I have for the PPA, let me know and I'll be glad to help do some signaling for you to trigger off of.
When we did maintain stable versions, the distros didn't reliably update those either, so I don't really see the point. Ubuntu base still has 0.3.1 in it from three years ago, apparently :)
It would certainly be easier on your non-ubuntu users if their distros had a fighting chance.
A couple years ago, I did a poll looking for people to indicate what linux distros they cared about so I could focus whatever time I had on things that were likely to generate value for people. 99% used an ubuntu or debian variant. I feel like we're doing the best for everyone if 99% run ubuntu and get the latest bug and feature updates the day after we release them.
--Dan
participants (7)
-
Bob Nielsen -
Dan Smith -
David Ranch -
Fred Maxwell -
Knight, Dave -
NP3AR -
Rick Farina