Date: Sun, 13 Nov 2022 23:54:57 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 260440] devel/py-Jinja2: Update to 3.0.3 Message-ID: <bug-260440-21822-NpCifJNmRW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-260440-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-260440-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=3D260440 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|maintainer-feedback?(nivit@ | |FreeBSD.org) | --- Comment #4 from Kubilay Kocak <koobs@FreeBSD.org> --- @Yuri This sphinx update caused a regression. This port is maintained by python@, nivit@ just happened to be assigned to nivit@.=20 The correct/better course of action would have been a reset of assignee to python@ (as it wasn't on our radar). It was an assignee timeout, not a maintainer timeout. Not withstanding, comment 1 detailed what was necessary to progress, which wasn't ack'd. The missing bulk / consumer build test would have picked up the regression. Further, this update was for 3.0.3 (which wouldn't have broken the build) The commit updating to 3.1 should have gone through a cycle on this issue, including updating the summary to match. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260440-21822-NpCifJNmRW>