| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Update devel/qt5-script* and www/qt5-webengine to 5.15.15-lts
Update devel/pyside2* and devel/shiboken2 to 5.15.10
Release note: https://code.qt.io/cgit/qt/qtreleasenotes.git/about/qt/5.15.10/release-note.md
PR: 273934
Exp-run by: antoine
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In mysql 5.7.34 binding a parameter to a 0-sized buffer triggers
an assert() -- previously this was DBG_ASSERT. This triggers
crashes in databases/akonadi in particular, which binds blobs of
size 0. This patch allows akonadi with the default mysql to
start (at all) again.
The patch file previously held a Qt4-era patch which had long
ago had a better patch applied upstream (the comment in the
patch refers to that). The old stuff has been removed, leaving
only the parameter-fix.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a major upgrade of the Qt libraries [1], [2].
* People that use upgrading mechanisms with incomplete dependency handling
(portmaster & Co) should make sure to manually remove the existing Qt
packages to guarantee a safe upgrade. Keep in mind, that Qt does not like if
you have an incomplete upgrade.
* This version of Qt drops support for OpenSSL 1.0 -- this means that there
won't be any binary packages for Qt5 provided by the FreeBSD package builders
for FreeBSD 11.x anymore -- and the same for *all* the ports depending on
net/qt5-network [3]. If you cannot upgrade to a more recent FreeBSD
version (12.x, 13.x), you will need to build Qt5 from ports while switching
to an SSL implementation from ports.
Big thanks are due for
* kai@ for updating webengine (also mikael@)
* Felix Palmen for providing LibreSSL support patches
* adridg@ and lbartoletti@ for helping me fix the fallout
[1] https://www.qt.io/blog/qt-5.15-released
[2] https://wiki.qt.io/New_Features_in_Qt_5.15
[3] https://www.freshports.org/net/qt5-network
PR: 247010
Exp-run by: antoine
Notes:
svn path=/head/; revision=541318
|
|
|
|
|
|
|
|
|
| |
Add a note to the patch for MariaDB-compatibility on how to do it
without ifdefs, which therefore would track changes in MariaDB
definitions (if it follows the MySQL change) automatically.
Notes:
svn path=/head/; revision=471403
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Recent MySQL code has deprecated the my_bool type, so r469165
added a check for that recent version. MariaDB pretends to be
MySQL, and has an even newer version, which nonetheless hasn't
taken over the drop-my_bool-type change. So my_bool still exists
there. Assume, for now, that MariaDB has my_bool regardless,
to fix incompatibilities reported after PR227813 was closed.
PR: 227813
Reported by: Jashank Jeremy
Notes:
svn path=/head/; revision=471301
|
|
against mysql >= 8.0.1.
From the mysql release notes [1]:
Incompatible Change: The my_bool type is no longer used in MySQL source code.
Any third-party code that used this type to represent C boolean variables should
use the bool or int C type instead.
Note
The change from my_bool to bool means that the mysql.h header file now requires
a C++ or C99 compiler to compile.
(Bug #25597667)
--
[1] https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-1.html
PR: 227813
Reported by: mikhail.rokhin@gmail.com
Notes:
svn path=/head/; revision=469165
|