This has been broken at runtime since the update to OpenLDAP 2.6.2.
ruby-ldap previously linked to libldap_r, but the OpenLDAP update removed
libldap_r, and the code compiled without linking to any ldap library,
breaking at runtime.
Update WANTLIB while here.
databases/xapian-bindings
databases/xapian-core
www/xapian-omega
OK sthen@ followed by quick databases/xapian-bindings/pkg/PLIST-python
tweak by me after the sphinx update PLIST regen
you can't move directly from 3.6 -> 4.4 (you can only move from one major version
to the next; 3.6->4.0, 4.0->4.2, 4.4->4.4) but you can use mongodump/mongorestore
from the mongo-tools package.
Tools for use with MongoDB:
- bsondump: display BSON files in a human-readable format
- mongoimport: Convert data from JSON, TSV or CSV and insert them
into a collection
- mongoexport: Write an existing collection to CSV or JSON format
- mongodump/mongorestore: Dump MongoDB backups to disk in .BSON format,
or restore them to a live database
- mongostat: Monitor live MongoDB servers, replica sets, or sharded clusters
- mongofiles: Read, write, delete, or update files in GridFS
- mongotop: Monitor read/write activity on a mongo server
- mongoreplay: Capture, observe, and replay traffic for MongoDB
- Use CFLAGS and CXXFLAGS instead of CMAKE_CXX_FLAGS and CMAKE_C_FLAGS.
- Use MODCMAKE_LDFLAGS instead of CMAKE_EXE_LINKER_FLAGS
- Fix broken builds with CMake 3.23
Update HOMEPAGE.
Add TESTFLAGS var for Tdbc-sqlite3 test control.
Upstream build improvements mean that now the Tdbc-sqlite3
tests can be run like normal Tcl TEA extension tests.
Update HOMEPAGE.
Add TESTFLAGS var for Tdbc-postgres test control.
Upstream build improvements mean that now the Tdbc-postgres
tests can be run like normal Tcl TEA extension tests.
Update HOMEPAGE.
Add TESTFLAGS var for Tdbc-mysql test control.
Upstream build improvements mean that now the Tdbc-mysql
tests can be run like normal Tcl TEA extension tests.
Add patch because MariaDb removed "MySQL" from error messages,
causing a test to fail.
Add cheap patch because mysql_get_client_version() since 10.6.2
returns the client version and no longer the server version,
breaking an assumption made by this software.
Add patch from upstream, fixing bug:
https://core.tcl-lang.org/tdbcmysql/info/9bf0e3e2e7.
This comment in the port Makefile was/is wrong:
"Skip test requiring isolation levels not provided by MariaDB"
All tests pass now.
Remove build lock to Tcl 8.5; not needed and
some people might want to build against 8.6.
Add recommended "-DSQLITE_DQS=0" build flag,
https://sqlite.org/quirks.html#dblquote.
- BDB/HDB are no longer supported in 2.5+, if you're using these you
need to move to MDB (MDB is supported in the 2.4.x version already in
ports).
*Before* upgrading use slapcat to dump your database to an ldif file.
(You should be doing this regularly anyway)
Update your database configuration to use mdb instead of bdb.
Note that if you are using the on-line configuration database (cn=config)
rather than slapd.conf it can be fiddly to change in an existing
configuration; you may prefer to regenerate the configuration too.
Reload your database from the ldif file using slapadd (or if you are
updating a read-only replica you can let syncrepl pick it up).
- The port has switched to a modular build. The most important backends
and overlays (in particular mdb and syncrepl) are still compiled into
slapd so in those cases you don't need to make any changes to adapt to
this. If using more exotic configuration then you may need to load
the relevant modules (for OLC see "olcModuleLoad", for slapd.conf see
"moduleload").
- Switch from BUILD_DEPENDS on groff (only soelim is used) to an awk
script.
Next commit will adjust other ports to cope.
IP4R is a PostgreSQL extension which supports 6 data types allowing
you to store IPv4 & IPv6 addresses in a PostgreSQL table:
ip4 - a single IPv4 address
ip4r - an arbitrary range of IPv4 addresses
ip6 - a single IPv6 address
ip6r - an arbitrary range of IPv6 addresses
ipaddress - a single IPv4 or IPv6 address
iprange - an arbitrary range of IPv4 or IPv6 addresses
While PostgreSQL already has builtin types 'inet' and 'cidr', the
authors of this module found that they had a number of requirements
that were not addressed by the builtin types.
Essentially a bugfix release. Biggest issue is :
BUGFIX: vmagent[2]: properly process passwords and secrets specified
in the file pointed by -promscrape.config command-line flag. All the
passwords and secrets were mistakenly replaced with <secret> string
in v1.77.0.
Changelog at https://github.com/VictoriaMetrics/VictoriaMetrics/releases/tag/v1.77.1
see https://sqlite.org/releaselog/3_38_3.html
"Fix a case of the query planner be overly aggressive with optimizing
automatic-index and Bloom-filter construction, using inappropriate ON
clause terms to restrict the size of the automatic-index or Bloom
filter, and resulting in missing rows in the output."
This fixes:
(CVE-2022-24736) An attacker attempting to load a specially crafted
Lua script can cause NULL pointer dereference which will result with
a crash of the redis-server process. This issue affects all versions
of Redis.
(CVE-2022-24735) By exploiting weaknesses in the Lua script
execution environment, an attacker with access to Redis can inject
Lua code that will execute with the (potentially higher) privileges
of another Redis user.
ok tb
the changelog list various bugfixes and improvements, but it also fixes
the error
/usr/local/share/lua/5.3/DBI.lua:31: attempt to call a nil value (field
'maxn'
when running the lua53 flavor (e.g. when using luadbi for prosody'
mod_storage_sql)
ok sthen@
or strongly suspected to support at least 8.0. (7.4 is currently on security
support only, and that finishes in November, so I intend to switch the "ports
default" version to 8.0).
some of these ports _may_ work with 8.0 already, some have pull requests or
support in newer upstream code (not always in a release), others definitely
need 7.4.
uses a different name or a subdirectory for the file.
Adjust some ports to use it: p5-DBI (different name), p5-Template (xs
subdirectory). There are others that could use this.
OK bluhm@
fix some #!/usr/bin/python3, add some optional runtime deps which are
small and used by the built-in filters for common file types, and switch
to qtwebengine for -gui on archs where it's available
remove the src/Makefile.in parallel build patch, those pieces have moved
to tools/Makefile.in but I'm unable to get it to fail with various -j values
so it seems likely the different directory introduces a sync point anyway
that is hard to patch for opaque structs in newer OpenSSL/LibreSSL.
While this port has been patched to _build_ against current postgresql
it hasn't been patched to _run_ with a newer version since 2018 (11.x)
so seems unlikely to really be used; this has no longer been maintained
upstream for even longer so I intend to remove the port soon.
A mariadb developer didn't like the fact that these structs need to be
allocated in OpenSSL 1.1 and added some insane hacks to work around
this. Adjust the code to cope with that the same way as it is done for
OpenSSL.
LibreSSL doesn't provide the means to override malloc and friends, so
the runtime check cannot be adapted. Use generous estimates for the
sizes for these structs instead.
With opaque EVP_CIPHER_CTX, EVP_CIPHER_CTX_buf_noconst() needs to be
provided by libcrypto, so disable this and a few other API redefinitions.
