https://bugzilla.redhat.com/show_bug.cgi?id=1835934 --- Comment #3 from Jaroslav Škarvada <jskarvad@xxxxxxxxxx> --- Upstream rejected the patch and wrote that the syntax error is there on purpose meaning the drivers weren't hand converted and tested and may not work. The syntax error is there to prevent the drivers from loading (more in [1]). It's strange approach, but I am unable to test all the drivers, because I don't own all the radios - from the list I own just the UV3R, so I will test it and fix possible runtime errors I will encounter. I will probably also try to propose this UV3R patch upstream. Regarding the rest of the problematic drivers I will probably remove them from the package and left it on the upstream to finish the conversion in their own pace. It's the following drivers: a/chirp/drivers/alinco.py a/chirp/drivers/anytone.py a/chirp/drivers/anytone_ht.py a/chirp/drivers/ap510.py a/chirp/drivers/baofeng_common.py a/chirp/drivers/baofeng_uv3r.py a/chirp/drivers/bf-t1.py a/chirp/drivers/bj9900.py a/chirp/drivers/bjuv55.py a/chirp/drivers/fd268.py a/chirp/drivers/ft1d.py a/chirp/drivers/ft2800.py a/chirp/drivers/ft2900.py a/chirp/drivers/ft450d.py a/chirp/drivers/ft50.py a/chirp/drivers/ft60.py a/chirp/drivers/ft70.py a/chirp/drivers/ft7100.py a/chirp/drivers/ft8100.py a/chirp/drivers/ft90.py a/chirp/drivers/ftm350.py a/chirp/drivers/kguv8d.py a/chirp/drivers/kguv8dplus.py a/chirp/drivers/kguv8e.py a/chirp/drivers/kguv9dplus.py a/chirp/drivers/kyd.py a/chirp/drivers/kyd_IP620.py a/chirp/drivers/leixen.py a/chirp/drivers/lt725uv.py a/chirp/drivers/puxing.py a/chirp/drivers/radioddity_r2.py a/chirp/drivers/radtel_t18.py a/chirp/drivers/retevis_rt1.py a/chirp/drivers/retevis_rt21.py a/chirp/drivers/retevis_rt22.py a/chirp/drivers/retevis_rt23.py a/chirp/drivers/retevis_rt26.py a/chirp/drivers/rfinder.py a/chirp/drivers/rh5r_v2.py a/chirp/drivers/tdxone_tdq8a.py a/chirp/drivers/th7800.py a/chirp/drivers/th9000.py a/chirp/drivers/th9800.py a/chirp/drivers/th_uv8000.py a/chirp/drivers/thd72.py a/chirp/drivers/thuv1f.py a/chirp/drivers/tk760g.py a/chirp/drivers/ts2000.py a/chirp/drivers/ts480.py a/chirp/drivers/ts590.py a/chirp/drivers/vgc.py a/chirp/drivers/vx6.py a/chirp/drivers/vxa700.py a/chirp/drivers/wouxun.py Upstream also wrote that he appreciate that we don't package anything from the py3 branch at this point, because it's in such a half-working state. Personally, I think it's OK for the rawhide. It's one of the core open source principles to release often and release quickly even in a half-working state. It seems there is startup notification that it's experimental. Moreover I was able to successfully program my UV5R with it. So for me to choose whether I will be able to program my UV5R in rawhide or not, the choice is clear. [1] https://chirp.danplanet.com/issues/7877 -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
