Date: Fri, 12 Jun 2026 17:23:14 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 296007] lang/python314: update to 3.14.6 Message-ID: <bug-296007-21822-qMZvjjQTne@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-296007-21822@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=296007 --- Comment #4 from Matthias Andree <mandree@FreeBSD.org> --- You are guessing my motives. How does discussing ownership get the Python 3.14.6 security update out to users of the quarterly and latest ports trees? Now that you've claimed ownership, when can users expect the update for the FreeBSD trees and packages? In the interim, people can pull from https://gitlab.com/mandree/freebsd-ports/-/commits/main?ref_type=HEADS or https://github.com/mandree/freebsd-ports/commits/main/ - I also have the 2026Q2 update in place. On your local ports checkout, do either of these lines to get the upstream update first, then get my update, works for 2026Q2 and main: git pull ; git pull https://github.com/mandree/freebsd-ports.git `git rev-parse --abbrev-ref HEAD` git pull ; git pull https://gitlab.com/mandree/freebsd-ports.git `git rev-parse --abbrev-ref HEAD` Then rebuild from source. make -C lang/python314 clean all reinstall or portmaster python314. Remember to, afterwards, also rebuild and reinstall those from the following list that you have installed: py314-sqlite3, py314-gdbm and py314-tkinter -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-296007-21822-qMZvjjQTne>