- Change the :target in SQLite dependency to `build' so that files which
are copied during `pre-configure' stage would be generated;
- Don't explicitly list supported Lua versions in the COMMENT and define
options after other declarative knobs and before targets;
- Switch to the new upstream distfile (version remained the same) as the
previous one is no longer fetchable. Looking at the changes, they
span the period from 2018-07-01 to 2021-09-07 and look legit. Also,
the test suite had been amended; it would be hooked in another commit.
PR: 259991
ChangeLog: https://www.sqlite.org/releaselog/3_39_0.html
* Add (long overdue) support for RIGHT and FULL OUTER JOIN.
* Add new binary comparison operators IS NOT DISTINCT FROM and IS DISTINCT FROM
that are equivalent to IS and IS NOT, respective, for compatibility with
PostgreSQL and SQL standards.
* Add a new return code (value "3") from the sqlite3_vtab_distinct() interface
that indicates a query that has both DISTINCT and ORDER BY clauses.
* Added the sqlite3_db_name() interface.
* The unix os interface resolves all symbolic links in database filenames to
create a canonical name for the database before the file is opened.
* Defer materializing views until the materialization is actually needed, thus
avoiding unnecessary work if the materialization turns out to never be used.
* The HAVING clause of a SELECT statement is now allowed on any aggregate
query, even queries that do not have a GROUP BY clause.
* Many microoptimizations collectively reduce CPU cycles by about 2.3%.
PR: 264974
Reported by: pavelivolkov@gmail.com (maintainer)
- update patch-collection diff to be at the highest patch-level
- update patch-collection diff to be against 5.15.5 instead of 5.15.2
- update devel/qt5-script to 5.15.10
- libressl support by Felix Palmen <felix@palmen-it.de>
PR: 264944
Exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D35619
2022-06-30 databases/pgpool-II-36: Upstream support ended use databases/pgpool-II-43
2022-06-30 ftp/multiget: Last release in 2007, doesn't support https, depends on deprecated wxgtk28 and dead upstream. Please consider using net/uget
2022-06-30 devel/electron13: EOLed upstream, switch to newer version
2022-06-30 ftp/puf: Last release in 2006, doesn't support https and upstream is dead. Please consider using www/aria2
2022-06-30 security/gss: Abandonware, last release in 2014 and no development since
2022-06-30 security/shishi: Abandonware, last release in 2013 and no development since
2022-06-30 ftp/urlgfe
2022-06-30 www/nspluginwrapper: Abandonware, last release in 2011 and upstream is dead. NPAPI plugins are now obsolete and depends on deprecated library GTK 2
2022-06-30 devel/govendor: Use Go modules
2022-06-30 devel/racer: Racer is not actively developped now. Please consider using newer software such as devel/rust-analyzer.
2022-06-30 net-mgmt/unifi6: No longer maintained by upstream
2022-06-30 devel/dep: Use Go modules
2022-06-30 databases/libgda5-bdb: Depends on deprecated databases/db5
2022-06-30 emulators/qemu5: Use emulators/qemu6 or emulators/qemu
2022-06-30 deskutils/bitcollider: bitzi.com is no longer available, closed down in 2013
2022-06-30 converters/htx: XHTML is considered obsolete in favor of HTML5
2022-06-30 www/getleft: Abandonware last updated on 2008
2022-06-30 ftp/wxdfast: Last release in 2009, doesn't support https, depends on deprecated wxgtk28 and dead upstream. Please consider using net/uget
2022-06-30 databases/percona56-server: EOL since February 2021
2022-06-30 databases/percona56-client: EOL since February 2021
2022-06-30 databases/mysql55-server: Upstream support ended on December 2018
2022-06-30 databases/mysql55-client: Upstream support ended on December 2018
pgagroal is a high-performance protocol-native connection pool for
PostgreSQL. Which features High performance, Connection pool, Limit
connections for users and databases, Prefill support, Remove idle
connections, Connection validation, Enable / disable database access,
Graceful / fast shutdown, Prometheus support, Grafana 8 dashboard,
Remote management, Authentication query support, Failover support,
Transport Layer Security (TLS) v1.2+ support, Daemon support, User
vault, Lightweight connection pooler for PostgreSQL.
WWW: https://agroal.github.io/pgagroal/
Sponsored by: Bounce Experts
Required for gitlab-ce 15.1.
Changelog:
https://github.com/pganalyze/pg_query/blob/main/CHANGELOG.md
2.1.3 2022-01-28
Track tables in EXCEPT and INTERSECT queries (#239)
Get filter_columns working with UNION/EXCEPT/INTERSECT (#240)
Update google-protobuf to address CVE scanner complaints
Note that none of the CVEs apply to pg_query, but this avoids unnecessary errors when the google-protobuf dependency is pulled in
ChangeLog: https://github.com/mongodb/mongo/releases/tag/r5.0.9
* Remove limits on number of LDAP connections per host
* Detect namespace changes when refreshing Collection after yielding
* Sharding an empty collection releases the critical section too early
* Mongos fails to attach RetryableWrite Error Label For Command Interrupted
In _parseCommand
* Fix search near returning wrong key/value sometimes when key doesn't exist
PR: 264341
Reported by: ulassayginim@gmail.com
MFH: 2022Q2 (many bugfixes)
This release fixes an issue with all versions of PostgreSQL 14 that can
lead to silent corruption of indexes.
Since the release of PostgreSQL 14.0, there existed an issue with CREATE
INDEX CONCURRENTLY and REINDEX CONCURRENTLY that could cause silent data
corruption in indexes. This issue is fixed in the upcoming PostgreSQL
14.4 release.
If you ran either of these commands on any version of PostgreSQL 14
prior to 14.4, you may have experienced silent data corruption. You can
use the pg_amcheck command with the --heapallindexed flag to detect this
issue with B-tree indexes.
If you need an immediate remediation for this issue before the
PostgreSQL 14.4 release, you can run CREATE INDEX or REINDEX without
CONCURRENTLY. You can also run the reindexdb command and use the --jobs
flag for added parallelism, but do not use the --concurrently flag.
Once PostgreSQL 14.4 is released, you can safely use CREATE INDEX
CONCURRENTLY and REINDEX CONCURRENTLY to manage your indexes, as well as
the --concurrently flag on reindexdb.
URL: https://www.postgresql.org/message-id/165473835807.573551.1512237163040609764%40wrigleys.postgresql.org
- Replaced Chain("") with Chain() for several. This was motivated by
an observed bug for check constraint xml import, where a comparision
between Chain() and Chain("") returned false
- Fix in CegoFunction::evalFieldValue for case REPLACE. If replace
string is null, then empty string is replaced instead of "null"
string.
Author: Björn Lemke <lemke@lemke-it.com>
Please DO NOT use this version in production, it is an early test
version.
port-committers@ please DO NOT mark your ports IGNORE_WITH_PHP=82. A
build is running to check all php ports with php82 and will be
committed in batch tomorrow.
Sponsored by: Bounce Experts
Over 120 individual programs plus dozens of programmer libraries and
feature plugins are released simultaneously as part of KDE Gear.
Today they all get new bugfix source releases with updated translations, including:
* ark: Support ‘7zip’ as well as ‘p7zip’.
* konsole: Fix scroll position jumps regression.
* okular: Fix crash while undoing with the menu on an empty
annotation.
Distro and app store packagers should update their application packages.
Full Changelog: https://kde.org/announcements/changelogs/gear/22.04.2/
The JDBC team has released version 42.3.6 to fix a regression introduced
in 42.3.2
This fixes "cursor <unnamed portal 1> does not exist" when using
ResultSet.setFetchSize from CallableStatement, fixed in 42.3.5
(see PG #2377)
Release notes: https://jdbc.postgresql.org/documentation/changelog.html#version_42.3.6
- FreeTDS fails to connect with MsSQL after the latest updates of
OpenSSL specially after the release of 13.1 SNAPSHOTS including
13.1-RELEASE and more specifically when openssl turned into 1.1.1l
See the following for more details:
https://github.com/FreeTDS/freetds/issues/458
- After the upgrade to version 1.3.9 FreeTDS fails to upgrade when using
ports tree. [1]
PR: 261967 263641 [1]
Reported by: jsc@ntu.edu.tw eugen [1]
- Rename autoconf 2.13 port directory, package, and command all to
autoconf2.13 just like ports like perl and python.
- Let USES=autoreconf run gtkdocize if necessary.
- Rewrite autoconf-wrapper and rename it autoconf-switch to reflect
better what it does.
- Delete patch-bison. It has been reverted upstream.
- Add a patch to let autoreconf set the AUTOCONF environment variable
so subprocesses like automake use the correct version.
- Make building of info files optional.
- Address portlint, portclippy, portfmt issues in devel/autoconf*.
PR: 259556, 263970
The rc script was converted to use a SUB_LIST variable, but I failed to
introduce the variable correctly in the Makefile. [1]
The plist for postgresql15-server was incorrect. Fixed this as well.
PR: 264097 [1]
Changelog:
Welcome to the release of phpMyAdmin version 5.2.0. This release contains many new features and quite a few bug fixes. We are simultaneously releasing phpMyAdmin 5.1.4, which is the last release of the 5.1 line and is mostly intended to help downstream packaging teams. Most users should migrate to 5.2.0.
Most notably, these releases resolve a networking error when exporting a file (https://github.com/phpmyadmin/phpmyadmin/issues/17445).
Some other highlights of 5.2.0 include:
Removed support for Microsoft Internet Explorer
Requires PHP 7.2 or newer
Requires the openssl PHP extension
Improved handling of system CA bundle and cacert.pem, falling back to Mozilla CA if needed
Replace "master/slave" terms with "primary/replica"
Add "NOT LIKE %...%" operator to Table search
Add support for the Mroonga engine
Add support for account locking
Several fixes and improvements to the SQL parser library
Sponsored by: Netzkommune GmbH
Thursday, 12 May 2022. Over 120 individual programs plus dozens of
programmer libraries and feature plugins are released simultaneously as
part of KDE Gear.
Today they all get new bugfix source releases with updated translations,
including:
* dolphin: The terminal panel will keep in sync with quick folder
changes now
* kate: Fix crash on session restore
* kalendar: Fix ’next week’ button in the week’s view
The full changelog can be found at
https://kde.org/announcements/changelogs/gear/22.04.1/
The PostgreSQL Global Development Group has released an update to all
supported versions of PostgreSQL, including 14.3, 13.7, 12.11, 11.16,
and 10.21. This release fixes over 50 bugs reported over the last three
months. This release closes one security vulnerability and fixes over 50
bugs reported over the last three months.
We encourage you to install this update at your earliest possible
convenience.
If you have any GiST indexes on columns using the ltree data type, you
will need to reindex them after upgrading.
For the full list of changes, please review the release notes.
It also fixes a security issue, CVE-2022-1552:
Autovacuum, REINDEX, and others omit "security restricted operation" sandbox.
Versions Affected: 10 - 14. The security team typically does not test
unsupported versions, but this problem is quite old.
Autovacuum, REINDEX, CREATE INDEX, REFRESH MATERIALIZED VIEW, CLUSTER,
and pg_amcheck made incomplete efforts to operate safely when a
privileged user is maintaining another user's objects. Those commands
activated relevant protections too late or not at all. An attacker
having permission to create non-temp objects in at least one schema
could execute arbitrary SQL functions under a superuser identity.
While promptly updating PostgreSQL is the best remediation for most
users, a user unable to do that can work around the vulnerability by
disabling autovacuum, not manually running the above commands, and not
restoring from output of the pg_dump command. Performance may degrade
quickly under this workaround. VACUUM is safe, and all commands are fine
when a trusted user owns the target object.
Security: 157ce083-d145-11ec-ab9b-6cc21735f730
Release notes: https://www.postgresql.org/docs/release/
According to the upstream document
https://www.oracle.com/us/support/library/lifetime-support-technology-069183.pdf
MySQL 5.5 has reached it's Extended Support on December 2018. Under
sustaining support there is no New updates, fixes, security alerts, data
fixes, and critical patch updates. Hence we are setting it to EXPIRE
before 2022Q3.
PR: 263762
Approved by: ale (maintainer)
Bugs Fixed
InnoDB: A failure occurred when attempting to purge undo records for a table with an instantly added column. (Bug #33924532)
InnoDB: High-priority transactions were not permitted to stop waiting when interrupted or to timeout while waiting for a lock, preventing deadlocks from being resolved. In cases where the blocking transaction is also high-priority, high-priority transactions are now permitted to stop waiting when interrupted or timeout when exceeding the lock wait timeout period. If a blocking transaction is not high-priority, high-priority transactions wait for the blocking transaction to release its locks. (Bug #33856332)
InnoDB: The AIO synchronization queue used on Windows was removed. The synchronous file I/O read-write function (SyncFileIO::execute) was revised to handle files opened for both normal and overlapped I/O, as it does on Linux. (Bug #33840645)
InnoDB: Table version metadata was not reset after truncating all partitions of a table with an instantly added column. (Bug #33822729)
InnoDB: The srv_error_monitor_thread() function, which prints warnings about semaphore waits, failed to handle a long semaphore wait as expected. To address this issue, a blocking call was moved to a more appropriate location. Related monitor thread code was simplified and improved, and missing shutdown signals were added for several server threads.
Enabling and disabling of the standard monitor by InnoDB is now performed independently of the user-settable innodb_status_output variable. This change addresses an issue in which the monitor was enabled by InnoDB in a particular scenario but not set back to its previous value. Thanks to Yuhui Wang for the contribution. (Bug #33789526, Bug #93878)
InnoDB: Valgrind testing identified an off-by-one error in rec_convert_dtuple_to_rec_old() in the InnoDB sources. (Bug #33784672)
InnoDB: The UNIV_DEBUG variant of the mem_heap_alloc() function in the InnoDB sources was modified to improve Valgrind error detection. (Bug #33783709)
InnoDB: A fast shutdown did not wait for all active I/O operations to finish before closing all files. (Bug #33768584)
InnoDB: A Clang warning reported an incorrectly placed @return command. (Bug #33734011)
InnoDB: Values of the new record locks array (m_prebuilt->new_rec_locks[]) were not properly synchronized when switching between partitions, causing an assertion failure due to locks being freed or not freed as expected. (Bug #33724166)
InnoDB: A race condition in the function that updates the double write buffer when a write request is completed caused a long semaphore wait error. (Bug #33712370)
InnoDB: A function wrongly assumed that changing a record in an indexed column always requires creating a new record in the secondary index, resulting in an lock-related assertion failure. To address this and other similar cases, the lock_rec_convert_impl_to_expl() function that converts an implicit record lock to an explicit record lock is now used only when an implicit record lock is actually held. (Bug #33657235)
InnoDB: A number of Doxygen issues in the InnoDB sources were addressed. (Bug #33603036)
InnoDB: A missing null pointer check for an index instance caused a failure. (Bug #33600109)
Full (and long) relnotes: https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-29.html
Sponsored by: Netzkommune GmbH
Mostly just typos and assigning PORTREVISION multiple times.
This commit doesn't fix up PORTREVISION between master-slave
ports where the master port often overwrites PORTREVISION from
the slaves which means the slaves don't actually get bumped.
These probably just need PORTREVISION?= but care must be taken
to not decrease the package versions of all the master-slave
packages and to actually bump PORTREVISION as intended. For the
record the currently visible broken master ports are:
databases/libgda5
emulators/virtualbox-ose
emulators/virtualbox-ose-legacy
graphics/atril
multimedia/mlt7
textproc/uim
But all master ports should be looked at here and get an explicit
PORTREVISION?= where it's currently missing to prevent this.
Reported by: portscan
After lang/ruby26 is removed the value of it is same with all
supported ruby versions. So ports need not use it to specify full
patch of rdoc executable.
PR: 263386
Approved by: maintainer timeout
compiling bdb.c
In file included from bdb.c:1:
In file included from ./bdb.h:1:
/usr/local/include/db5/db.h:2725:5: warning: 'DB_DBM_HSEARCH' is not defined, evaluates to 0 [-Wundef]
#if DB_DBM_HSEARCH != 0
^
/usr/local/include/db5/db.h:3081:5: warning: 'DB_DBM_HSEARCH' is not defined, evaluates to 0 [-Wundef]
#if DB_DBM_HSEARCH != 0
^
/usr/local/include/db5/db.h:3102:5: warning: 'DB_DBM_HSEARCH' is not defined, evaluates to 0 [-Wundef]
#if DB_DBM_HSEARCH != 0
^
bdb.c:168:15: error: implicit declaration of function 'rb_tainted_str_new2' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
version = rb_tainted_str_new2(db_version(&major, &minor, &patch));
^
bdb.c:672:5: warning: 'HAVE_CONST_BDB_TXN_COMMIT' is not defined, evaluates to 0 [-Wundef]
#if HAVE_CONST_BDB_TXN_COMMIT
^
bdb.c:960:18: error: implicit declaration of function 'rb_tainted_str_new' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
bdb_errstr = rb_tainted_str_new(0, 0);
^
bdb.c:960:18: note: did you mean 'rb_tainted_str_new2'?
bdb.c:168:15: note: 'rb_tainted_str_new2' declared here
version = rb_tainted_str_new2(db_version(&major, &minor, &patch));
^
4 warnings and 2 errors generated.
*** Error code 1
Stop.
While I'm here,
* Pet portlint and portclippy.
* Tidy up Makefile with portfmt.
PR: 263360
Approved by: maintainer timeout
Mark BROKEN if any of external lua library options are enabled.
Upstream add new APIs to bundled lua library and use them in source
code of redis. This makes it impossible to compile and link redis with
external lua libraries. According to the commit message of upstream
repository they took the code of new API from the repository of
lua. It means linking with external lua libraries may get possible
again if they are updated. So mark BROKEN rather than remove these
options.
Changes: b8eb2a7...02080f2
Security: cc42db1c-c65f-11ec-ad96-0800270512f4
Bugs Fixed
InnoDB: A missing null pointer check for an index instance caused a failure. (Bug #33600109)
InnoDB: Purge threads processed undo records of an encrypted table for which the tablespace was not loaded, causing a failure. (Bug #32586721)
InnoDB: Incorrect AUTO_INCREMENT values were generated when the maximum integer column value was exceeded. The error was due to the maximum column value not being considered. The previous valid AUTO_INCREMENT value should have been returned in this case, causing a duplicate key error. (Bug #87926, Bug #26906787)
Partitioning: In some cases, establishing a connection to MySQL server could fail if the .ibd file for a partition was missing. (Bug #33459653)
Statements that cannot be parsed (due, for example, to syntax errors) are no longer written to the slow query log. (Bug #33732907)
It was not possible to revoke the DROP privilege on the Performance Schema. (Bug #33578113)
A page cleaner thread timed out as it waited for an exclusive lock on an index page held by a full-text index creation operation on a large table. (Bug #33101844)
A memory leak occurred if mysqldump was used on more than one table with the --order-by-primary option. The memory allocated for sorting each table’s rows is now freed after every table, rather than only once. (Bug #30042589, Bug #96178)
mysqld_safe log message textual errors were corrected. Thanks to Bin Wang at China Mobile for the contribution. (Bug #106590, Bug #33903639)
Full Changelog: https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-38.html
Sponsored by: Netzkommune GmbH
p5-DBD-Sybase compilation fails with obscure build error
when building system has previous version of freetds installed.
Let's print friendly message instead noting needed freetds version.
* Mark BROKEN if any of external lua library options are
enabled. Upstream add new APIs to bundled lua library and use them
in source code of redis. This makes it impossible to compile and
link redis with external lua libraries. According to the commit
message of upstream repository they took the code of new API from
the repository of lua. It means linking with external lua libraries
may get possible again if they are updated. So mark BROKEN rather
than remove these options.
* Update CONFLICTS of databases/redis*.
* Switch to DISTVERSION.
* Pet portlint and portclippy.
* Tidy up Makefile with portfmt.
ChangeLog: https://github.com/redis/redis/releases/tag/7.0.0
Security: cc42db1c-c65f-11ec-ad96-0800270512f4
* Mark BROKEN if any of external lua library options are
enabled. Upstream add new APIs to bundled lua library and use them
in source code of redis. This makes it impossible to compile and
link redis with external lua libraries. According to the commit
message of upstream repository they took the code of new API from
the repository of lua. It means linking with external lua libraries
may get possible again if they are updated. So mark BROKEN rather
than remove these options.
* Switch to DISTVERSION.
* Pet portlint and portclippy.
* Tidy up Makefile with portfmt.
ChangeLog: https://github.com/redis/redis/releases/tag/6.2.7
Security: cc42db1c-c65f-11ec-ad96-0800270512f4
DBIx::Tracer is easy tracer for DBI. You can trace a SQL queries without
modifying configuration in your application.
You can insert snippets using DBIx::Tracer, and profile it.
WWW: https://metacpan.org/dist/DBIx-Tracer
