===> The following configuration options are available for percona57-server-5.7.42.46:
FASTMTX=off: Replace mutexes with spinlocks
INNODBMEMCACHED=on: InnoDB Memcached plugin
OPENSSL=on: SSL/TLS support via OpenSSL
TOKUDB=off: TokuDB Engine (experimental)
===> Use 'make config' to modify these settings
Initial password for first time use of MySQL is saved in $HOME/.mysql_secret
ie. when you want to use "mysql -u root -p" first you should see password
in /root/.mysql_secret
If upgrading
Remember to run mysql_upgrade the first time you start the MySQL server
after an upgrade from an earlier version.
databases/percona57-server: Mark IGNORE_SSL
- Fails to build with OpenSSL 3.0.0 and later with
error: duplicate symbol: ossl_sa_ and as MySQL 5.7 did not get any
updates for OpenSSL 3.0.0 and later it is highly unlikely that Percona
will also get one.
- mark DEPRECATED as upstream will reach EOL on 2023-10-01
See:
https://www.percona.com/services/policies/percona-software-support-lifecycle
- Set EXPIRATION_DATE to 2023-10-01
- Fix a EOL space in pkg-plist
- Bump to show DEPRECATED message
Approved by: portmgr (blanket)
databases/percona57-*: update Percona MySQL to 5.7.41-44 release (+)
While here, introduce HAVE_TYPE_MY_BOOL variable alongside with typedef char
my_bool;
This unbreak devel/apr1 build with mysql integration enabled whule dafault is
set to percona
Release
notes: https://docs.percona.com/percona-server/5.7/release-notes/5.7.41-44.html
databases/and_others: Fix rc.d script comment
I found this typo while researching something else. It seems to have
propgated around the tree.
Approved by: blanket
Fix WWW in parent/child ports
Many of the WWW are overwritten later which means the wrong value
is used. This did not happen before where the children were either
a) just using the pkg-descr from the parents
b) or had their own separate pkg-descr with custom WWW
Use WWW?= in parents when the child's WWW is different.
Children that use the same WWW as the parent can just inherit it,
i.e., the child WWW can be removed.
Approved by: portmgr (implicit)
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
Fix CONFLICTS entries of multiple ports
There have been lots of missing CONFLICTS_INSTALL entries, either
because conflicting ports were added without updating existing ports,
due to name changes of generated packages, due to mis-understanding
the format and semantics of the conflicts entries, or just due to
typoes in package names.
This patch is the result of a comparison of all files contained in
the official packages with each other. This comparison was based on
packages built with default options and may therefore have missed
further conflicts with optionally installed files.
Where possible, version numbers in conflicts entries have been
generalized, some times taking advantage of the fact that a port
(Only the first 15 lines of the commit message are shown above )
*/*: Remove redundant '-*' from CONFLICTS definitions
The conflict checks compare the patterns first against the package
names without version (as reported by "pkg query "%n"), then - if
there was no match - agsinst the full package names including the
version (as reported by "pkg query "%n-%v").
Approved by: portmgr (blanket)
databases/percona57-{client, server}: update to 5.7.30-33 release
Bugs Fixed:
PS-6979: Modify the processing to call clean up functions to remove CREATE
USER statement from the processlist after the statement has completed (Upstream
#99200)
PS-6860: Merge innodb_buffer_pool_pages_LRU_flushed into
buf_get_total_stat()
PS-6811: Correct service failure of asserting ACL_PROXY_USER when
skip-name-resolve=1 and there is a Proxy user (Upstream #98908)
PS-6112: Correct Binlog_snapshot_gtid inconsistency when mysqldump was used
with -single-transaction.
PS-6945: Correct tokubackup plugin process exported API to allow large file
backups.
PS-6856: Correct binlogs corruptions in PS 5.7.28 and 5.7.29 (Upstream
#97531)
PS-6946: Correct tokubackup processing to free memory use from the address
and thread sanitizers
PS-5893: Add support for running multiple instances with systemD on Debian.
PS-5620: Modify Docker image to support supplying custom TLS certificates
PS-4573: Implement use of a single config file - mysqld.cnf file.
PS-7041: Correct Compilation error when -DWITH_EDITLINE=bundled is used
(Only the first 15 lines of the commit message are shown above )
databases/percona57-*: Fix build for i386
Make build-script assume that FreeBSD's Clang doesn't
have "atomic_*" functions builtin implemented on i386
While here, allow to build on DragonFly BSD and
drop "-fabi-version=2" from C/CXX flags
Reported by: pkg-fallout
MFH: 2020Q1
- Update Percona Server/Client to 5.7.28-31 release [1]
* When using skip-innodb_doublewrite in my.cnf, a parallel doublewrite buffer
is still created. Bugs fixed #3411.
* During a binlogging replication event, if the master crashes after
the multi-threaded slave has begun copying to the slave's relay log
and before the process has completed, a STOP SLAVE on the slave takes
longer than expected. Bug fixed #5824.
* If pam_krb5 is configured to allow the user to change their password,
and the password expired, the server crashed after receiving the new password.
Bug fixed #6023.
- Provide LibreSSL support [2]
- Take maintainership. feld@ didn't pet the ports for almost two years,
all updates was committed with maintainer timeout
PR: 242649
Submitted by: Igor Zabelin [1]. fluffy@ [2]
Approved by: maintainer (feld@, timeout >2 weeks)
databases/percona57-{server,client} update to 5.7.27-30 release
percona57-client:
- Install compat pkgconfig symlink as well as it done for libs
(many packages still search for mysqlclient.pc only)
percona57-server:
- Proper use system lz4/zstd libs for rocksdb engine
- Declare system libevent to use instead of bundled one
- Stop pollute libdata/pkgconfig dir with unneeded .pc file
- Unbreak build with DEFAULT_VERSIONS+=ssl=libressl
PR: 239347
Submitted by: fluffy [cleanups], Igor Zabelin [update]
Approved by: maintainer (timeout, >3 months)
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
Fix build on gcc-based architectures by removing the assumption that FreeBSD
must imply clang. While here, remove duplicate definition from USES.
PR: 234580
Submitted by: Piotr Kubaj
Approved by: portmgr (tier-2 blanket)
Move the BROKEN statement for powerpc64 to the server port only; the
client slave port builds.
Reported by: Piotr Kubaj
Approved by: portmgr (tier-2 blanket)
Change cmake default behaviour to outsource.
Ports that build out of source now simply can use "USES=cmake"
instead of "USES=cmake:outsource". Ports that fail to build
out of source now need to specify "USES=cmake:insource".
I tried to only set insource where explictely needed.
PR: 232038
Exp-run by: antoine
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
Install texinfo files (GNU info) into ${PREFIX}/share/info
After a discussion on the mailing list on moving manpages to
${PREFIX}/share/man for consistency with base where it is
installed in usr/share/man, it appeared the same should happen
to GNU info files which were installed under share in base and
not in ports.
Now texinfo is not in base on any of the supported version of FreeBSD
it is possible to proceed to this move and it is easier to do than
the manpage change.
Other benefit than consistency are less patching: all build tools but
cmake are expecting info files to be under share/info and cmake (patched here)
was having an exception for BSD so the patch makes FreeBSD case less
specific for them
Bump revision of all impacted ports
PR: 232907
exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D17816
databases/percona57-server: Adapt ${name}_limits to the new resource
limiting mechanics for services
Thanks to the recent change to rc.subr(8) it is no longer necessary to
define a resource limiting logic in service scripts. limits(1) is now run
by default and its configuration is handled via the "${name}_limits"
variable.
Unfortunately, there is a collision of variable names. The service scripts
are broken on FreeBSD version with that new change (>= 12.0).
The patch preserves the old behavior on the systems without the rc.subr(8)
modification.
PR: 227236
Reviewed by: krion
Approved by: krion (mentor), maintainer timeout
Differential Revision: https://reviews.freebsd.org/D17786
Bump PORTREVISION for ports depending on the canonical version of GCC
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.
This includes ports
- featuring USE_GCC=yes or USE_GCC=any,
- featuring USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and those
- with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.
PR: 222542
databases/percona57: Fix build with SASL
If SASL is detected at build time it assumes you want SASL and also
errors due to assuming we're Linux. This was already patched in our tree
for MySQL.
Also enable SASL support by default for the databases/percona57-client.
This is expected to be the default by upstream now.
Special thanks to mmokhi for figuring this out for us.
PR: 220865
MFH: 2018Q1
Bump PORTREVISION for ports depending on the canonical version of GCC
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++11-lang,
c++14-lang, c++0x, c11, or gcc-c++11-lib.
PR: 219275
MySQL ports: Extend CONFLICTS_INSTALL in conflicting ports.
databases/mysqlwsrep56-server has been present for some time and
databases/mysqlwsrep57-server has been added recently. Both ports
conflict with other MySQL server ports and this has been reflected
in databases/mysqlwsrep5[67]-server/Makefile but must also be
reflected in all conflicting ports' Makefiles as well.
The conflicting ports are:
databases/mariadb100-server
databases/mariadb101-server
databases/mariadb102-server
databases/mariadb55-server
databases/mysql55-server
databases/mysql56-server
(Only the first 15 lines of the commit message are shown above )
Make ninja opt-out in cmake.mk
Using ninja instead of make (1) can lead to significant speed ups while
building.
Therefore switch from having the ninja generator opt-in to having it opt-out.
Previously cmake-ports that wanted to use ninja could set
CMAKE_NINJA=yes
now, ports that do not work with ninja can set
cmake:<existing args>,noninja
Note, that needing this should be an exception and most often points to a broken
cmake of the port.
The ports using cmake were modified
* removed USES=gmake, if ninja is used
* removed MAKE_ARGS, if ninja is used
* added the cmake-argument noninja if necessary
PR: 219629
PR: 213331
Exp-run by: antoine
Reviewed by: rakuco
Differential Revision: https://reviews.freebsd.org/D10748
Bump PORTREVISIONs for ports depending on the canonical version of GCC and
lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using using Mk/bsd.octave.mk which in turn has USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
c++11-lang, c++0x, c11, or gcc-c++11-lib.
PR: 216707
Welcome Percona 5.7 ports to the tree
- client and server version 5.7.16-10
- pam-for-mysql: compatible with newer MySQL API (MySQL 5.7+)
Thanks to all who have worked on Percona, MariaDB, and MySQL ports. Your
tireless efforts have been instrumental in making this port happen.
Differential Revision: https://reviews.freebsd.org/D8785
