Bug 1286451
Summary: | Please update Chirp to support Baofeng BF-F8HP radios | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jaroslav Škarvada <jskarvad> |
Component: | chirp | Assignee: | Richard Shaw <hobbes1069> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | hobbes1069, randyn3lrx |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | chirp-20151130-1.fc23 chirp-20151130-1.fc22 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-12-14 10:22:33 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jaroslav Škarvada
2015-11-29 16:30:14 UTC
I don't really want to update to a snapshot, it would be better if they would go ahead and tag a release as it's been a while. Unless it's dependent on other updates I can pull in the latest uv5r.py to at least get you going. (In reply to Richard Shaw from comment #1) > I don't really want to update to a snapshot, it would be better if they > would go ahead and tag a release as it's been a while. > I will try to write them, but it seems they moved to a snapshot release model, it even reports snapshot as release version in about dialog. > Unless it's dependent on other updates I can pull in the latest uv5r.py to > at least get you going. Thanks, I have no problem with backport. But uv5r.py would require some patching, direct copy is not enough. The BF-F8HP seems to support all the tri-power 2014+ classes of Baofengs (e.g. very probably, I didn't tested all: BF-UVB2Plus, UV-8HX, UV-5RTP, and many others), so it is good to have the support there. Upstream bug: http://chirp.danplanet.com/issues/3035 It doesn't seem there will be any release following the previous release model, reply from upstream: Hi Jaroslov, We're not doing releases anymore. It just doesn't make sense with our development process. This works just fine with Ubuntu because we generate the packages and upload to the PPA during every nightly build process. I don't (try to) do this with Fedora because the last survey I did indicated that there was little or no demand for Fedora packages. If there is something I can do to better enable you to use the snapshots, please let me know. So probably we will have to move to snapshot release model as well or drop the package. IMHO one refresh per release should be enough and shouldn't require much effort. Bah that's annoying... So does the version never change? Do i need to bump the Epoch and change the version to 0? Or will they at lest maintain some sort of stable branch that I can patch against like I do for mythtv? Ok, I posted to devel just to be sure but I'm planning on making the date the version, should work fine. I just submitted a scratch build using the date as the version, when complete can you verify it works and addresses this bug? http://koji.fedoraproject.org/koji/taskinfo?taskID=12017406 Thanks I am going to check with real HW. I asked question about the new release model upstream: http://chirp.danplanet.com/issues/3035#note-3 I.e. whether they are going to stay with this release model and if there is a chance there will be 0.5.1 version anytime. Reply from upstream: Well stick with the date, which is the whole version. So, we never plan to have an 0.5.0 version. (In reply to Richard Shaw from comment #8) > I just submitted a scratch build using the date as the version, when > complete can you verify it works and addresses this bug? > > http://koji.fedoraproject.org/koji/taskinfo?taskID=12017406 Works great with my new Baofeng, thanks. chirp-20151130-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-7410210eb6 chirp-20151130-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update chirp' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-19c63f6f10 chirp-20151130-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update chirp' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-7410210eb6 chirp-20151130-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report. chirp-20151130-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. |