Date: Tue, 08 Feb 2022 21:31:48 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 261791] devel/py-twisted: Update to 22.1.0 (includes a security update) Message-ID: <bug-261791-21822-W6Cv2Noa4u@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-261791-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-261791-21822@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=3D261791 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open CC| |ports-secteam@FreeBSD.org Keywords| |needs-qa Severity|Affects Some People |Affects Many People Flags| |merge-quarterly? Priority|--- |Normal --- Comment #2 from Kubilay Kocak <koobs@FreeBSD.org> --- Thank you for the report and patches. - Given this will need to be MFH'd, with alternative options being a backpo= rt to 21.x instead (for merging) updating head to 22.1.x, could you peruse the changelog between current port version and 22.1.0 looking for changes that might provide backward compat issues. In particular, of the main issues will be consuming ports that pin their twisted version specs to <22.1, or dont ping, but don't support later versi= ons for whatever reason. This class of issue will result in builds succeeding, = but with run time failures. An assessment of the version specs (in upstream sources that are used in ei= ther in setup.py or in external files like requirements files) for consuming por= ts to identify problematic ports will go a long way. --=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-261791-21822-W6Cv2Noa4u>