aboutsummaryrefslogtreecommitdiff
path: root/databases
Commit message (Collapse)AuthorAgeFilesLines
* databases/lmdb: Fix static library installation.Xin LI2022-05-132-11/+17
| | | | | | | | | INSTALL_LIB will strip symbols, and should not be used for static libraries. PR: ports/263884 Reported by: yuri MFH: 2022Q2
* databases/adodb5: update to 5.22.2 maintenance releaseDima Panov2022-05-122-4/+4
| | | | Cahngelog: https://github.com/ADOdb/ADOdb/blob/v5.22.2/docs/changelog.md
* databases/postgresql??-server: update to latest versionPalle Girgensohn2022-05-1215-30/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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/
* databases/sqlite3: Update to 3.38.2Pavel Volkov2022-05-122-9/+10
| | | | | | | ChangeLog: https://www.sqlite.org/releaselog/3_38_3.html PR: 263718 Reported by: pavelivolkov@gmail.com (maintainer)
* databases/R-cran-RSQLite.extfuns: mark as deprecatedSteven Kreuzer2022-05-111-2/+7
| | | | | Mark port as depreciated as it has been merged with RSQLite. Schedule the port to be removed at the end of this month
* databases/pointcloud: Update to 1.2.2Loïc Bartoletti2022-05-113-15/+12
| | | | | Changes: - https://github.com/pgpointcloud/pointcloud/blob/v1.2.2/NEWS#L1-L14
* databases/neo4j: Update to 4.2.16Wen Heping2022-05-118-153/+147
| | | | | | | Take maintainership PR: 263555 Reported by: wen@ Approved by: maintainer(timeout, > 14 days)
* databases/rubygem-arel-helpers: update to 2.14.0Antoine Brodin2022-05-102-5/+4
|
* databases/geoserver-mysql-plugin: Add CPE informationBernhard Froehlich2022-05-101-1/+3
| | | | Approved by: portmgr (blanket)
* graphics/poppler: bump portrevision of consumersTobias C. Berner2022-05-091-1/+1
|
* databases/rubygem-bdb1: fix runtime error with ruby 3.0: Undefined symbol ↵Dirk Meyer2022-05-093-6/+79
| | | | "rb_secure"
* databases/phppgadmin: fix for PHP8Dirk Meyer2022-05-093-1/+26
| | | | PR: 263759
* databases/mroonga: Update version 12.02=>12.03Muhammad Moinur Rahman2022-05-072-4/+4
| | | | Relnotes: https://mroonga.org/en/blog/2022/05/06/mroonga-12.03.html
* databases/mysql-connector-java: Update to 8.0.29Richard Gallamore2022-05-072-4/+4
| | | | Changes: https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/news-8-0-29.html
* databases/py-whisper: update to version 1.1.8Steven Kreuzer2022-05-072-5/+4
|
* databases/R-cran-sqldf: update to version 0.4-11Steven Kreuzer2022-05-073-18/+18
| | | | | | Changes: * modifications for RSQLite 2.0.0 * read.csv.sql now accepts https and ftps
* databases/R-cran-RSQLite: update to version 2.2.14Steven Kreuzer2022-05-072-6/+13
| | | | | Changes: * Upgrade bundled SQLite to version 3.38.5
* databases/redisjson: update to 2.0.8Sergey A. Osokin2022-05-072-74/+70
|
* databases/py-python-sql: Update to 1.4.0Wen Heping2022-05-072-4/+4
|
* databses/unixODBC: Update to 2.3.11Bernard Spil2022-05-053-5/+7
|
* databases/mysql55-server: Mark DEPRECATEDMuhammad Moinur Rahman2022-05-041-0/+3
| | | | | | | | | | | | 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)
* databases/py-mysql-connector-python: Update version 8.0.28=>8.0.29Muhammad Moinur Rahman2022-05-032-5/+4
| | | | | Relnotes: https://github.com/mysql/mysql-connector-python/releases/tag/8.0.29
* databases/mysql80-server: Mark als BROKEN on i386 after ↵Jochen Neumeister2022-05-031-0/+2
| | | | | | | | | | | | 10d211b655d85e31bf9b8e27d234f526cfd1e49b cd /wrkdirs/usr/ports/databases/mysql80-server/work/.build/plugin/x/protocol/plugin && /usr/local/bin/protoc --plugin=protoc-gen-yplg=/wrkdirs/usr/ports/databases/mysql80-server/work/.build/runtime_output_directory/xprotocol_plugin --yplg_out /wrkdirs/usr/ports/databases/mysql80-server/work/.build/plugin/x/generated -I /usr/local/include -I /wrkdirs/usr/ports/databases/mysql80-server/work/mysql-8.0.29/plugin/x/protocol/protobuf /wrkdirs/usr/ports/databases/mysql80-server/work/mysql-8.0.29/plugin/x/protocol/protobuf/mysqlx_connection.proto /wrkdirs/usr/ports/databases/mysql80-server/work/mysql-8.0.29/plugin/x/protocol/protobuf/mysqlx_crud.proto /wrkdirs/usr/ports/databases/mysql80-server/work/mysql-8.0.29/plugin/x/protocol/protobuf/mysqlx_cursor.proto /wrkdirs/usr/ports/databases/mysql80-server/work/mysql-8.0.29/plugin/x/protocol/protobuf/mysqlx_datatypes.proto /wrkdirs/usr/ports/databases/mysql80-server/work/mysql-8.0.29/plugin/x/protocol/protobuf/mysqlx_expect.proto /wrkdirs/usr/ports/databases/mysql80-server/work/mysql-8.0.29/plugin/x/protocol/protobuf/mysqlx_expr.proto /wrkdirs/usr/ports/databases/mysql80-server/work/mysql-8.0.29/plugin/x/protocol/protobuf/mysqlx_notice.proto /wrkdirs/usr/ports/databases/mysql80-server/work/mysql-8.0.29/plugin/x/protocol/protobuf/mysqlx_prepare.proto /wrkdirs/usr/ports/databases/mysql80-server/work/mysql-8.0.29/plugin/x/protocol/protobuf/mysqlx.proto /wrkdirs/usr/ports/databases/mysql80-server/work/mysql-8.0.29/plugin/x/protocol/protobuf/mysqlx_resultset.proto /wrkdirs/usr/ports/databases/mysql80-server/work/mysql-8.0.29/plugin/x/protocol/protobuf/mysqlx_session.proto /wrkdirs/usr/ports/databases/mysql80-server/work/mysql-8.0.29/plugin/x/protocol/protobuf/mysqlx_sql.proto --yplg_out: protoc-gen-yplg: Plugin killed by signal 11. *** Error code 1 A solution is being worked on Sponsored by: Netzkommune GmbH
* databases/mysql80-{client, server}: Update to latest release 8.0.29Jochen Neumeister2022-05-035-17/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* databases/py-python-swiftclient: update to 3.13.1Mikolaj Golub2022-05-032-4/+4
|
* lang/rust: Relink ports after the Rust 1.60.0 updateTobias Kortkamp2022-05-033-3/+3
|
* *: Fix up PORTREVISIONTobias Kortkamp2022-05-031-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | 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
* Mk/bsd.ruby.mk: Remove RUBY_RDOCYasuhiro Kimura2022-05-022-12/+2
| | | | | | | | | 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
* databases/ruby-bdb: Mark BROKEN_RUBY32Yasuhiro Kimura2022-05-021-24/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* grimreaper: return zeising's ports to the pool after safekeeping his ports bit.Rene Ladan2022-05-021-1/+1
|
* databases/redis62: Fix CPE information after repocopyBernhard Froehlich2022-05-021-0/+1
| | | | Approved by: portmgr (blanket)
* databases/ejdb: new port had been added (+)Alexey Dokuchaev2022-05-017-0/+125
| | | | | | | Embeddable JSON database engine C library which supports simple XPath-like query language (JQL). WWW: https://ejdb.org/
* databases/redis-devel: Update to latest snapshotYasuhiro Kimura2022-05-012-5/+8
| | | | | | | | | | | | | | 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: https://github.com/redis/redis/compare/b8eb2a7...02080f2 Security: cc42db1c-c65f-11ec-ad96-0800270512f4
* databases/rubygem-activerecord70: Update to 7.0.2.4Po-Chuan Hsieh2022-04-302-4/+4
| | | | Changes: https://github.com/rails/rails/releases
* databases/rubygem-activemodel70: Update to 7.0.2.4Po-Chuan Hsieh2022-04-302-4/+4
| | | | Changes: https://github.com/rails/rails/releases
* databases/rubygem-activerecord61: Update to 6.1.5.1Po-Chuan Hsieh2022-04-302-4/+4
| | | | Changes: https://github.com/rails/rails/releases
* databases/rubygem-activemodel61: Update to 6.1.5.1Po-Chuan Hsieh2022-04-302-4/+4
| | | | Changes: https://github.com/rails/rails/releases
* databases/rubygem-activerecord60: Update to 6.0.4.8Po-Chuan Hsieh2022-04-302-4/+4
| | | | Changes: https://github.com/rails/rails/releases
* databases/rubygem-activemodel60: Update to 6.0.4.8Po-Chuan Hsieh2022-04-302-4/+4
| | | | Changes: https://github.com/rails/rails/releases
* databases/rubygem-activerecord52: Update to 5.2.7.1Po-Chuan Hsieh2022-04-302-4/+4
| | | | Changes: https://github.com/rails/rails/releases
* databases/rubygem-activemodel52: Update to 5.2.7.1Po-Chuan Hsieh2022-04-302-4/+4
| | | | Changes: https://github.com/rails/rails/releases
* databases/py-tiledb: Update to 0.14.2Po-Chuan Hsieh2022-04-303-7/+7
| | | | Changes: https://github.com/TileDB-Inc/TileDB-Py/releases
* databases/py-tarantool: Update to 0.8.0Po-Chuan Hsieh2022-04-302-4/+4
| | | | Changes: https://github.com/tarantool/tarantool-python/releases
* databases/py-sqlalchemy14: Update to 1.4.36Po-Chuan Hsieh2022-04-303-4/+6
| | | | Changes: https://docs.sqlalchemy.org/en/14/changelog/changelog_14.html
* databases/py-psycopg-pool: Update to 3.1.1Po-Chuan Hsieh2022-04-302-5/+5
| | | | Changes: https://github.com/psycopg/psycopg/blob/master/docs/news_pool.rst
* databases/py-psycopg-c: Update to 3.0.12Po-Chuan Hsieh2022-04-302-4/+4
| | | | Changes: https://github.com/psycopg/psycopg/blob/master/docs/news.rst
* databases/py-psycopg: Update to 3.0.12Po-Chuan Hsieh2022-04-302-4/+4
| | | | Changes: https://github.com/psycopg/psycopg/blob/master/docs/news.rst
* databases/tiledb: Update to 2.8.2Po-Chuan Hsieh2022-04-302-4/+4
| | | | Changes: https://github.com/TileDB-Inc/TileDB/releases
* databases/mysql57-*: Update ti 5.7.38Jochen Neumeister2022-04-303-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | 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
* databases/pg_activity: update to 2.3.1Palle Girgensohn2022-04-292-4/+4
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-08 13:56:37 +0000