[Bug 257041] [NEW PORT]: devel/py-lief: Parse, modify and abstract ELF, PE and MachO formats
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257041 Neal Nelson changed: What|Removed |Added Flags|maintainer-feedback?(ports@ | |nicandneal.net) | --- Comment #14 from Neal Nelson --- Given that ports seems to be suffering lots of incompatible requirements for conflicting ports at the moment (tbb, onetbb, various opencasecade versions, etc.), maybe a port containing it's own dependencies isn't such a bad thing, as long as it doesn't pollute any other ports. Or to put it another way, I have no idea how to go about removing *some* of the third-party files, which we have in ports, but not others, which we do not. I can see part of the CMakeLists.txt that deals with third-party, but not being a CMake user I could only have a stab at trying to remove the dependencies. -- You are receiving this mail because: You are on the CC list 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-bjoern | 3.1.0 | 3.2.1 +-+ 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!
maintainer-feedback requested: [Bug 261974] lang/python311: add --enable-lto
Bugzilla Automation has asked freebsd-python (Nobody) for maintainer-feedback: Bug 261974: lang/python311: add --enable-lto https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261974 --- Description --- Off for riscv64 and powerpc64. configure.ac checks $CC, so we need to set it to clang if $CC == cc. LD takes around 300MB for linking so it should be ok to enable it even for 32 bit architectures. This patch should also be merged to older Python. At least 3.10 and 3.9 should build with LTO. It would be nice if it's done before 3.9 is made the default.
[Bug 261974] lang/python311: add --enable-lto
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261974 Bug ID: 261974 Summary: lang/python311: add --enable-lto Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: python@FreeBSD.org Reporter: pku...@freebsd.org Flags: maintainer-feedback?(python@FreeBSD.org) Assignee: python@FreeBSD.org Off for riscv64 and powerpc64. configure.ac checks $CC, so we need to set it to clang if $CC == cc. LD takes around 300MB for linking so it should be ok to enable it even for 32 bit architectures. This patch should also be merged to older Python. At least 3.10 and 3.9 should build with LTO. It would be nice if it's done before 3.9 is made the default. -- You are receiving this mail because: You are the assignee for the bug.
maintainer-approval requested: [Bug 261974] lang/python311: add --enable-lto : [Attachment 231841] patch
Piotr Kubaj has asked freebsd-python (Nobody) for maintainer-approval: Bug 261974: lang/python311: add --enable-lto https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261974 Attachment 231841: patch https://bugs.freebsd.org/bugzilla/attachment.cgi?id=231841&action=edit --- Comment #1 from Piotr Kubaj --- Created attachment 231841 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=231841&action=edit patch
[Bug 261974] lang/python311: add --enable-lto
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261974 Piotr Kubaj changed: What|Removed |Added CC||python@FreeBSD.org Attachment #231841||maintainer-approval?(python Flags||@FreeBSD.org) --- Comment #1 from Piotr Kubaj --- Created attachment 231841 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=231841&action=edit patch -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[Bug 261313] [META] Deprecate/Expire Django 2.2 and switch to Django 3.2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261313 Bug 261313 depends on bug 261918, which changed state. Bug 261918 Summary: www/py-django-appconf: Update to 1.0.5 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261918 What|Removed |Added Status|Open|Closed Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 261868] devel/py-aws-sam-translator: Allow build with Python 3.9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261868 Thierry Thomas changed: What|Removed |Added Resolution|--- |FIXED Status|Open|Closed Flags|maintainer-feedback?(nork@n |maintainer-feedback+, |inth-nine.com), |merge-quarterly- |merge-quarterly?| --- Comment #2 from Thierry Thomas --- Committed, thanks for the approval! -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 261703] Mk/bsd.default-versions.mk: Switch default Python version to 3.9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261703 Bug 261703 depends on bug 261868, which changed state. Bug 261868 Summary: devel/py-aws-sam-translator: Allow build with Python 3.9 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261868 What|Removed |Added Status|Open|Closed Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[Bug 261868] devel/py-aws-sam-translator: Allow build with Python 3.9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261868 --- Comment #3 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=3e024fcf393694f14fe70c52f06d0b459071d67d commit 3e024fcf393694f14fe70c52f06d0b459071d67d Author: Thierry Thomas AuthorDate: 2022-02-15 18:33:35 + Commit: Thierry Thomas CommitDate: 2022-02-15 18:39:12 + devel/py-aws-sam-translator: allow build with Python 3.9 According to official site, it's said that python 3.9 is not officially supported, but antoine@ noticed that it’s fine. PR: 261868 Approved by:Norikatsu Shigemura (maintainer) devel/py-aws-sam-translator/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 256995] textproc/py-pygments: Update to 2.11.2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256995 --- Comment #14 from Thierry Thomas --- (In reply to Yuri Victorovich from comment #10) It seems that Pygments-2.11.2 introduced a regression revealed by openage. Then I suggest that we start by updating textproc/py-pygments to 2.9.0 as proposed with my initial patch: everything is clear with it. In a second time, we could submit an another PR to upgrade it to the next version. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 256995] textproc/py-pygments: Update to 2.11.2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256995 --- Comment #15 from Yuri Victorovich --- (In reply to Thierry Thomas from comment #14) I agree. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 256995] textproc/py-pygments: Update to 2.9.0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256995 Thierry Thomas changed: What|Removed |Added Flags|maintainer-feedback-|maintainer-feedback+ URL|https://github.com/pygments |https://github.com/pygments |/pygments/releases/tag/2.11 |/pygments/releases/tag/2.9. |.2 |0 Summary|textproc/py-pygments: |textproc/py-pygments: |Update to 2.11.2|Update to 2.9.0 --- Comment #16 from Thierry Thomas --- (In reply to Yuri Victorovich from comment #15) OK, thanks. Then Antoine, could you please launch an exp-run? (it should be the latest one!) -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 256995] textproc/py-pygments: Update to 2.9.0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256995 Thierry Thomas changed: What|Removed |Added Attachment #231195|0 |1 is obsolete|| --- Comment #17 from Thierry Thomas --- Created attachment 231844 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=231844&action=edit Upgrade to 2.9.0 Resubmit the previous patch. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 261974] lang/python311: add --enable-lto
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261974 Kubilay Kocak changed: What|Removed |Added Status|New |Open --- Comment #2 from Kubilay Kocak --- I have a WIP for python ports to LTO, PGO, et al (PIE, etc), and more broadly prefer to handle this at the framework level than at an individual ports/software build level. Most build systems that provide pie/lto/etc features are relatively flaky and produce inconsistent results -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Bug 261974] lang/python311: add --enable-lto
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261974 Kubilay Kocak changed: What|Removed |Added Blocks||258536 --- Comment #3 from Kubilay Kocak --- @Piotr Let's touch base and solve this by making some progress at the higher level, I've made significant progress for establishing a baseline configuration for large swathes of the ports tree for LTO Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258536 [Bug 258536] Mk/bsd.lto.mk: Add Link-Time Optimization (LTO) support -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Bug 261974] lang/python311: add --enable-lto
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261974 --- Comment #4 from Piotr Kubaj --- I saw your site at https://wiki.freebsd.org/KubilayKocak/Ports/LinkTimeOptimization. However, until the toolchain issues are resolved, I'd prefer to enable LTO only for individual ports. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
