[Bug 257073] www/mitmproxy fails to build because py-asgiref was upgraded to 3.4.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257073 Kubilay Kocak changed: What|Removed |Added Severity|Affects Some People |Affects Many People Keywords||regression Flags||maintainer-feedback?(wen@Fr ||eeBSD.org) Status|New |Open CC||python@FreeBSD.org, ||w...@freebsd.org --- Comment #1 from Kubilay Kocak --- ^Triage: Request feedback from committer of asgiref update mitmproxy port correctly declares a pinned max version [1] [1] py38-asgiref>=3.2.10<3.4 : www/py-asgiref@py38 -- You are receiving this mail because: You are on the CC list for the bug.
[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 Kubilay Kocak changed: What|Removed |Added See Also||https://github.com/lief-pro ||ject/LIEF/issues/575 Flags||maintainer-feedback?(ports@ ||nicandneal.net) Keywords||feature, needs-patch, ||needs-qa Status|New |Open CC||d...@freebsd.org, ||po...@nicandneal.net, ||python@FreeBSD.org Summary|[NEW PORT]: devel/py-lief - |[NEW PORT]: devel/py-lief: |parse, modify and abstract |Parse, modify and abstract |ELF, PE and MachO formats. |ELF, PE and MachO formats. --- Comment #1 from Kubilay Kocak --- Review items: - Add python to CATEGORIES - Use MASTER=SITES=CHEESESHOP (PyPI) unless there is a compelling case not to - Match COMMENT to upstream setup.py:description (Library to instrument executable formats), or suggest upstream improve their description. - Use USE_PYTHON=autoplist unless there is a compelling case not to. pkg-plist not requires after this change - Use USE_PYTHON=concurrent for Python packages which install files into common (non python version specific) locations. THis port does (LOCALBASE/bin/*) - Remove do-build: target, shouldn't be necessary with USE_PYTHON=distutils - Strip shared library in a post-install: target See also: https://github.com/lief-project/LIEF/issues/575 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 256272] sysutils/py-scandir: Fails to stage on Python 3.9: error: redefinition of 'PyStructSequence_UnnamedField' with a different type: 'char *' vs 'const char *const' (breaks www/py-graphite-we
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256272 Kubilay Kocak changed: What|Removed |Added Flags||merge-quarterly- Assignee|ports-b...@freebsd.org |sunp...@freebsd.org Resolution|--- |FIXED Status|Open|Closed --- Comment #7 from Kubilay Kocak --- ^Triage: Assign to committer that resolved and close -- 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 +-+ devel/mercurial | 5.5 | 5.8.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!
Ports with version numbers going backwards: devel/p5-MooseX-SetOnce, devel/p...
** The following ports have a version number that sorts before a previous one ** For many package tools to work correctly, it is of utmost importance that version numbers of a port form a monotonic increasing sequence over time. Refer to the FreeBSD Porter's Handbook, 'Package Naming Conventions' for more information. Tools that won't work include pkg_version, portupgrade and portaudit. A common error is an accidental deletion of PORTEPOCH. Please fix any errors as soon as possible. The ports tree was updated at Fri Jul 9 2021 12:30:00 UTC. - *devel/p5-MooseX-SetOnce* : p5-MooseX-SetOnce-0.201 < p5-MooseX-SetOnce-0.22_1 - *devel/py-pytest* : py38-pytest-4.6.11 < py38-pytest-6.2.4 - *devel/py-pytest-flask* : py38-pytest-flask-0.15.1 < py38-pytest-flask-1.2.0 - *devel/py-pytest-translations* : py38-pytest-translations-2.0.0 < py38-pytest-translations-3.1.0 - *devel/py-pytest-xdist* : py38-pytest-xdist-1.32.0 < py38-pytest-xdist-2.3.0
[Bug 257073] www/mitmproxy fails to build because py-asgiref was upgraded to 3.4.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257073 --- Comment #2 from Wen Heping --- (In reply to Kubilay Kocak from comment #1) Upstream changed the asgiref depends to: asgiref>=3.2.10<3.4 shall we update RUN_DEPENDS as it ? wen -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 257073] www/mitmproxy fails to build because py-asgiref was upgraded to 3.4.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257073 --- Comment #3 from Wen Heping --- (In reply to Kubilay Kocak from comment #1) Sorry, upstream changed the asgiref depends to: asgiref>=3.2.10<3.5 shall we update RUN_DEPENDS as it ? wen -- You are receiving this mail because: You are on the CC list for the bug.
[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 --- Comment #2 from Neal Nelson --- (In reply to Kubilay Kocak from comment #1) - I assume that python is a virtual category? This does not bode well for my other port submissions, which are also python and also not tagged as such. - I chose github as this is where the project is based. Is it a policy to use pypi if available even though there may be more up to date version available elsewhere? If so, see above comment about not boding well. - That's a better comment (yours, not mine). It's not shown on github. - Alas autoplist does not work, for the very reason of the github issue you linked: the autoplist is incorrectly generated. It works fine as submitted. - I'm not exactly sure what the ramifications of USE_PYTHON=concurrent are, but without autoplist it may do nothing. - Sorry for the do-build. This was copied over from a port that needed it. - Strip added. -- You are receiving this mail because: You are on the CC list for the bug.
