[Bug 271673] lang/python312: New port, update to 3.12.8
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271673 --- Comment #58 from Baptiste Daroussin --- vishwin: is adding this version to the tree, with no possibility to enable it via as default python in collision with the part you are working on ? if no then we should proceed with the addition of the 3.12 version and only block adding the python.mk bits until your work has hit the tree Another question is: where is you work located, and what is missing, my understanding from the discussion, is that some UPDATING/CHANGES bits are missing but, the work is ok pending some exp-run am I right in my understanding, if yes, just to the exp-run, and push your changes if suitable, documentation on UPDATING/CHANGES can be done in a second step or even by someone else. also if you work it public someone should be able to give a hand and write those bits while the exp-run is running. -- You are receiving this mail because: You are the assignee for the bug.
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/pyt...@freebsd.org.html Port| Current version | New version +-+ www/py-django50 | 5.0.13 | 5.0.14 +-+ www/py-django51 | 5.1.7 | 5.1.8 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout!
[Bug 274671] lang/python313: New port, 3.13.2 release
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274671 --- Comment #13 from p5b2ea8...@t-online.de --- What exactly prevents the committing of lang/python3.13 as a new port. I do see Wen's attachments but not an initial commit for creating the port. I do need to understand the criteria/policy if any for porting new Python releases. We had python 3.10.0.beta4, 3.10.0rc1, 3.10.0rc2 as ports but do fail to provide actual Python releases for 3.12 and 3.12. What's going on here please? What is the point of failure? I do NOT criticize Wen here, as he is doing a great job by providing port-upgrades for Python in typically less than 5 days. And he is the one providing upgrade attachments. But there is an issue for getting the first (3.x.0 versions) releases in a reasonable timely manner as a port. And yes, upgrading Python default versions looked also more like than anything else. But this is another story and still needs to be improved. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 274671] lang/python313: New port, 3.13.2 release
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274671 Kurt Jaeger changed: What|Removed |Added Severity|Affects Only Me |Affects Many People -- You are receiving this mail because: You are the assignee for the bug.
[Bug 271673] lang/python312: New port, update to 3.12.8
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271673 Kurt Jaeger changed: What|Removed |Added Severity|Affects Only Me |Affects Many People -- You are receiving this mail because: You are the assignee for the bug.
