Bug 249329 - comms/chirp: update to 20200213
Summary: comms/chirp: update to 20200213
Status: In Progress
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Diane Bruce
URL:
Keywords: patch
: 249588 (view as bug list)
Depends on:
Blocks: 249337
  Show dependency treegraph
 
Reported: 2020-09-15 10:01 UTC by Charlie Li
Modified: 2020-10-16 13:16 UTC (History)
3 users (show)

See Also:
bugzilla: maintainer-feedback? (hamradio)


Attachments
Proposed python3 hack (8.34 KB, patch)
2020-09-28 20:42 UTC, Diane Bruce
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Charlie Li 2020-09-15 10:01:51 UTC
See review D26434 for details, but tl;dr this is a stopgap measure to prevent this port from being removed for being Python 2-only.
Comment 1 Diane Bruce freebsd_committer 2020-09-15 12:17:42 UTC
(In reply to Charlie Li from comment #0)
Thanks for this!
Comment 2 Steve Wills freebsd_committer 2020-09-24 17:08:07 UTC
*** Bug 249588 has been marked as a duplicate of this bug. ***
Comment 3 Diane Bruce freebsd_committer 2020-09-28 20:42:48 UTC
Created attachment 218388 [details]
Proposed python3 hack

Try this instead? We could continue to pull the daily builds, then run it through 2to3 (ick) there are still a few python files that need special patching.

I don't have an interface to test with. :-(
Comment 4 Charlie Li 2020-10-07 22:18:40 UTC
There are more than a few files that need special attention after running 2to3. Not only does the py3 branch reflect that, but even my attempts to run under Python 3 on the default branch essentially only gets the first screen of the pygobject-based GUI running; dialogs and radio programming do not work at all. Both branches also have pygtk2-isms that need pruning/refactoring because they don't work under pygobject despite the latter's compatibility "layer"; the import and export dialogs are prime examples of not functional. This is what I mean by our (as in what's in phab) patches not going upstream for now, since there is *that* much work and cleanup to do in the default branch.

The wxPython-based GUI is very much still half-baked (and hasn't had much activity since way earlier this year it seems), I would say in an even worse usability state than pygobject. Not to mention that it feels significantly slower.
Comment 5 Kyle Evans freebsd_committer 2020-10-16 13:16:33 UTC
Hey Diane,

chirp got removed this morning because we passed the expiration date, would you like to revive it with your python3 fix or should I?