Date: Sat, 30 Mar 2019 20:04:53 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 234669] devel/upnp: Update to 1.8.4 Message-ID: <bug-234669-7788-oszmhOWmnv@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-234669-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-234669-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=3D234669 --- Comment #5 from Lorenzo Salvadore <phascolarctos@protonmail.ch> --- (In reply to Raphael Kubo da Costa from comment #4) Yes and no. It turned out that upnp-1.6.* and upnp-1.8.* are two distinct and incompati= ble branches of the project, both in development: this is similar to the python27/36 issue. Thus, - I've reverted original upnp to 1.6.25, applying to it the rest of the pat= ch. I tested the dependent ports with upnp built with default options and it worked; - I've created a new port named upnp18 to track the upnp-1.8.* development branch. I tested the build and it worked. However I have not submitted the patch for 1.6.25 nor the new upnp18 port y= et because I still have to solve the conflict between them: I think it is an e= asy fix and I hope to have it ready in a few days. --=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-234669-7788-oszmhOWmnv>