graphics/openexr: graphics/ilmbase: v2.5.4 update
"Patch release with various bug/sanitizer/security fixes, primarily related to
reading corrupted input files."
<https://github.com/AcademySoftwareFoundation/openexr/releases/tag/v2.5.4>
Cherry-pick upstream commit for GCC 11 compatibility:
<a40a6151c4>
Since this changes the patchlevel of the solibs, bump PORTREVISION of dependent
ports just to be sure.
(graphics/py-openshadinglanguage is unaltered and .includes the revision bump
from .../openshadinglanguage.)
graphics/openexr: really commit v2.5.4 update.
Unfortunately, this was missed with the ilmbase update, and
causes yet another PORTREVISION bump on all dependent ports.
repeating ilmbase's commit log here:
"Patch release with various bug/sanitizer/security fixes, primarily related to
reading corrupted input files."
<https://github.com/AcademySoftwareFoundation/openexr/releases/tag/v2.5.4>
Cherry-pick upstream commit for GCC 11 compatibility:
<a40a6151c4>
Since this changes the patchlevel of the solibs, bump PORTREVISION of dependent
ports just to be sure.
(graphics/py-openshadinglanguage is unaltered and .includes the revision bump
from .../openshadinglanguage.)
Reported by: VVD (IRC, #bsdports)
graphics/openexr, ilmbase: security update to v2.5.5
https://github.com/AcademySoftwareFoundation/openexr/releases/tag/v2.5.5
"Specific OSS-fuzz issues include:
OSS-fuzz #30291 Timeout in openexr_exrcheck_fuzzer
OSS-fuzz #29106 Heap-buffer-overflow in Imf_2_5::FastHufDecoder::decode
OSS-fuzz #28971 Undefined-shift in Imf_2_5::cachePadding
OSS-fuzz #29829 Integer-overflow in Imf_2_5::DwaCompressor::initializeBuffers
OSS-fuzz #30121 Out-of-memory in openexr_exrcheck_fuzzer"
Bump PORTREVISION of ports that directly depend on openexr and/or ilmbase.
Security: 98044aba-6d72-11eb-aed7-1b1b8a70cc8b
cad/graywolf: Update 0.1.6-3 -> 0.1.6-4
cad/graywolf: Backport PR that makes graywolf run through tests
Submitted by: GH PR submitted by Kevin Zheng <kevinz5000@gmail.com>
the package is still 4.7. as a proof, SHA256 in distinfo is identical.
confusingly, the version in "About" says "master", not 4.8 nor 4.7.
this PR should be reopened. (Tomoyuki Sakura)
Apparently I forgot to remove a line causing the wrong cura version
to be claimed as an update to 4.8
I think I have it right this time. Apologies I should have noticed.
I'll take the pointyhat and go sit in the corner.
PR: ports/251236
Submitted by: sko@rostwald.de
Reported by: trombik1973@gmail.com
Since r558913 Python 3.8 incorporates BPO-42604 [1] which changed the
shared libs naming scheme. This means "EXT_SUFFIX" is now derived from
SOABI and yields with Python 3.8 to ".cpython-38.so" instead of ".so".
The affected ports strip the libaries in the "post-install" target via
hardcoded path(s) and the build fails at the end because the new extension
is not expected at this place.
Remedy the issue by adding wildcards to these paths. This should also
prepare the ports for future Python releases, which will use the new shared
libs naming scheme.
[1] https://bugs.python.org/issue42604
PR: 252057
Reported by: John Kennedy
Reviewed by: fluffy, koobs
Approved by: koobs (python)
- Add some dependencies which might be detected by Find_Package but not registered;
- Bump PORTREVISION of consumers.
PR: 250833
Submitted by: /me
Approved by: tcberner@ (KDE / maintainer) + exp-run
This commit combines several updates.
- Update Qt to 5.12.2
- Update PyQt to 5.15.1
- Since PySide 5.15.1 is broken with Qt 5.15.2, so PySide and Shiboken are also updated to 5.15.2.
- Update sip to 5.4.0
SIP is a collection of tools to create Python bindings for C and C++ libraries and used by PyQt and wxPython. There are some changes with sip5 [1]:
- python 3.5+ is required
- sip drops support of old deprecated methods as sipdistutils & cie.
- this version breaks also PyQt5 extension ABI. SIP files will be installed in ${PYTHON_SITELIBDIR}/PyQt${_PYQT_VERSION}/bindings
- some ports will use the new pyqtbuilder package with the pyproject.toml setup. Instead if the project have a setup.py, you should use sip-build to build it.
- if a port needs sip, it should also needs pysip. BTW, py-qt5-core requires pysip, so that should be enough for PyQt packages.
List of ports impacted by this change. Most of the patches have been integrated or are in the process of being integrated upstream:
- devel/libsavitar
- graphics/py-python-poppler-qt5
- net-im/scudcloud
- net/libarcus
- print/py-frescobaldi
- science/py-veusz
- graphics/qgis and graphics/qgis-ltr
- deskutils/calibre
A special note regarding calibre. New versions require sip>=5, we update it to the latest version (thanks to madpilot@)
science/scidavis will remove the PyQt binding soon and there is no patch planned, so we remove the python option (ok makc@)
While here, convert some ports to USE_PYQT (cad/cura, cad/uranium, devel/eric6, ...)
Thanks to tcberner and adridg!
[1] https://www.riverbankcomputing.com/static/Docs/sip/
PR: 250853
Exp-run by: antoine
0.11 failed to produce dxf files which could be imported into AutoCAD.
This bugfix release improves DXF importing from 10% to about 90%.
Found out via: repology.org
This implies:
- french /aster builds fine with clang, but it seg-faults: switched to Gcc
- ASTK is upgraded to 2019.0-1
- math/mumps is upgraded to 5.1.2-aster7
- TFEL/MFront is now required, but when the compilers of tfel and aster are
different, it cannot be linked
. recopopy science/tfel to science/tfel-edf and depends on science/tfel-edf
. science/tfel-edf is built by Gcc, from the sources included in Aster's
tarball
. register the conflicts
Sync up with cura and cura-engine
fixes to Uranium
Tooltip areas should not steal mouse events
This prevents us from using the tooltip area in a pop-up where the Z
coordinates are not a good solution.
Round coordinates when sampling pixel for selection ray
Pixel coordinates must be integer for the Python bindings of Qt.
In Cura version 4.7 a bug regarding slowdowns in circular perimeters was
introduced (or at list gets triggered much more easily than in earlier
versions):
https://github.com/Ultimaker/Cura/issues/8321
This issue makes v4.7.x hardly usable.
Sticking to v4.5 has become quite "tricky" to say the least, due to
the massive python-induced dependency hell and lots of dependencies
being too new and/or incompatible for the 4.5 version.
Version 4.8 has been released on November 10 that fixes this glitch in
the simplification algorithm. The issue is still open, but is considered
to be solved with 4.8 and changed default settings for Maximum resolution
and Maximum Deviation.
From the Changelog of 4.8:
Fixed under-simplification (blobs, zits) on some printer models. An oversight
in 4.6.x resulted in an oversimplification (smoothing) of models.
The attempted fix in 4.7.x overcompensated, which gave difficulty
(zits, blobs) for some printer models when the resulting gcode became
too intricate. This is now fixed, though some profiles might need
to be updated, since they where made against 4.6.x, and therefore may
rely on the over-simplification.
PR: ports/251236
Submitted by: Sebastian <sko@rostwald.de>
