Date: Thu, 02 Mar 2017 17:03:45 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 217499] [patch] comms/chirp: Fix port after py-serial upgrade in r424787, formalize gtk dependency Message-ID: <bug-217499-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217499 Bug ID: 217499 Summary: [patch] comms/chirp: Fix port after py-serial upgrade in r424787, formalize gtk dependency Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: hamradio@FreeBSD.org Reporter: bsdports@kyle-evans.net Flags: maintainer-feedback?(hamradio@FreeBSD.org) Assignee: hamradio@FreeBSD.org Keywords: patch Created attachment 180442 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D180442&action= =3Dedit svn(1) diff of added patches to comms/chirp and gtk2 dependency added py-serial got updated in r424787 to a 3.* version, which chirp 0.4.1 is not compatible with because of a couple function =3D> property changes. Given t= hat upstream hasn't made a non-daily release since 0.4.1, I've backported the following two commits from upstream: http://chirp.danplanet.com/projects/chirp/repository/revisions/0758ce12bbae http://chirp.danplanet.com/projects/chirp/repository/revisions/d1bc2c917785 I did this fully acknowledging that comms/chirp could use an update to a ne= wer version, but unless we want to switch it to track daily- versions with an e= poch change then this is the next best thing. =3D) I've also formalized the dependency on py27-gtk2 and tested this patch with= my Baofeng UV-5RA. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217499-13>