Date: Thu, 13 Aug 2020 19:14:44 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 248525] news/sabnzbdplus: Update to 3.0.0 Message-ID: <bug-248525-7788-FylXjw492w@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-248525-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-248525-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D248525 colmconn@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |colmconn@gmail.com --- Comment #6 from colmconn@gmail.com --- Quick question, this patch moves notify2 from being an optional build time option to now being a requirement (i.e., to RUN_DEPENDS from OPTIONS_DEFINE where it was not enabled by default). This represents a change form the previous 2.3.9 package. What was the justification for this change? The version of cherrypy currently in ports (5.4.0) will cause sabnzb 3 to c= rash (see https://github.com/sabnzbd/sabnzbd/issues/1524). This was never an iss= ue before since SAB used to include cherrypy as part of its source. Since V3 t= his is no longer the case. I opened a bug against cherrypy https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D247597 for this reason = but it has elicited no response from the maintainer. It might be worth noting in t= he pkg-message that SAB may crash when changing the theme (e.g., Glitter - Def= ault to Glitter - Night) when it uses cherrypy-5.4.0 from ports and that the pro= blem lies not within SAB but in cherrypy. (I've got cherrypy 8.9.1 built locally= as a package and SAB works fine with it. --=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-248525-7788-FylXjw492w>