| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
databases/redis: security fix
Revisions pulled up:
- databases/redis/Makefile 1.56
---
Module Name: pkgsrc
Committed By: wiz
Date: Mon Aug 3 10:38:45 UTC 2020
Modified Files:
pkgsrc/databases/redis: Makefile
Log Message:
redis: fix CVE-2016-2121
The configuration file was installed mode 644, but could contain passwords.
Bump PKGREVISION.
|
|
databases/ldb: dependent update
Revisions pulled up:
- databases/ldb/Makefile 1.17
- databases/ldb/distinfo 1.9
---
Module Name: pkgsrc
Committed By: adam
Date: Mon Jul 6 14:29:42 UTC 2020
Modified Files:
pkgsrc/databases/ldb: Makefile distinfo
Log Message:
ldb: updated to 2.1.4
2.1.4:
Unknown changes
|
|
|
|
Instead:
1. Package makefiles including their own options.mk
2. Packages say "SUBST_CLASSES+=djberrno" to get the hack, if needed
3. Packages adjust SUBST_FILES.djberrno, if needed
Should fix bulk build failures due to multiple inclusions of options.mk
and/or incorrect definitions of DJB_ERRNO_HACK.
Approved during the freeze by wiz@.
|
|
Changelog picked from https://notabug.org/guile-sqlite3/guile-sqlite3/releases
0.1.2:
Allow sqlite-finalize to be called twice on the same statement.
0.1.1:
sqlite-finalize: Reset statement when called on cached statement.
Fix memory management of retrieved blob values.
|
|
There has been one package only for a long time, so don't explain
which it is.
|
|
Packaging changes: depend on protobuf-c and json-c
PostGIS 3.0.1
2020/02/20
* Breaking Changes *
- #4637 svn number replaced by git hash in version output
(Sandro Santilli, Regina Obe, Bas Couwenberg)
* New Features *
- #4617, Add configure switch `--without-phony-revision` (Raúl Marín)
Use to prevent postgis_revision.h from rebuilding
(when building from tar ball) and building in a gitted folder.
* Bug Fixes and Enhancements *
[many, see NEWS]
PostGIS 3.0.0
2019/10/20
This version requires PostgreSQL 9.5+-12 and GEOS >= 3.6+
Additional features enabled if you are running Proj6+, PostgreSQL 12
and GEOS 3.8.0
* Breaking Changes *
- #4267, Bump minimum GEOS version to 3.6 (Regina Obe, Darafei Praliaskouski)
- #3888, Raster support now available as a separate extension
(Sandro Santilli)
- #3807, Extension library files no longer include the minor version.
Use New configure switch --with-library-minor-version
if you need the old behavior (Regina Obe)
- #4230, ND box operators (overlaps, contains, within, equals) now
don't look on dimensions that aren't present in both operands.
Please REINDEX your ND indexes after upgrade. (Darafei Praliaskouski)
- #4229, Dropped support for PostgreSQL < 9.5. (Darafei Praliaskouski)
- #4260, liblwgeom headers are not installed anymore.
If your project depends on them available, please use
librttopo instead. (Darafei Praliaskouski)
- #4258, Remove SFCGAL support for ST_Area, ST_Distance, ST_Intersection,
ST_Difference, ST_Union, ST_Intersects, ST_3DIntersects, ST_3DDistance
and postgis.backend switch (Darafei Praliaskouski)
- #4267, Enable Proj 6 deprecated APIs (Darafei Praliaskouski, Raúl Marín)
- #4268, Bump minimum SFCGAL version to 1.3.1 (Darafei Praliaskouski)
- #4331, ST_3DMakeBox now returns error instead of a miniscule box (Regina Obe)
- #4342, Removed "versioned" variants of ST_AsGeoJSON and ST_AsKML (Paul Ramsey)
- #4356, ST_Accum removed. Use array_agg instead. (Darafei Praliaskouski)
- #4414, Include version number in address_standardizer lib (Raúl Marín)
- #4334, Fix upgrade issues related to renamed function parameters (Raúl Marín)
- #4442, raster2pgsql now skips NODATA tiles. Use -k option if you still want
them in database for some reason. (Darafei Praliaskouski)
- #4433, 32-bit hash fix (requires reindexing hash(geometry) indexes) (Raúl Marín)
- #3383, Sorting now uses Hilbert curve and Postgres Abbreviated Compare.
You need to REINDEX your btree indexes if you had them.
(Darafei Praliaskouski)
* New Features *
- #2902, postgis_geos_noop (Sandro Santilli)
- #4128, ST_AsMVT support for Feature ID (Stepan Kuzmin)
- #4230, SP-GiST and GiST support for ND box operators overlaps, contains,
within, equals (Esteban Zimányi and Arthur Lesuisse from Université
Libre de Bruxelles (ULB), Darafei Praliaskouski)
- #4171, ST_3DLineInterpolatePoint (Julien Cabieces, Vincent Mora)
- #4311, Introduce WAGYU to validate MVT polygons. This option requires a C++11
compiler and will use CXXFLAGS (not CFLAGS). Add `--without-wagyu`
to disable this option and keep the behaviour from 2.5 (Raúl Marín)
- #1833, ST_AsGeoJSON(row) generates full GeoJSON Features (Joe Conway)
- #3687, Casts json(geometry) and jsonb(geometry) for implicit GeoJSON
generation (Paul Ramsey)
- #4198, Add ST_ConstrainedDelaunayTriangles SFCGAL function (Darafei
Praliaskouski)
* Enhancements *
- #4322, Support for Proj 6+ API, bringing more accurate datum transforms
and support for WKT projections
[many more; see NEWS]
|
|
2.19.1:
[BUGFIX] TSDB: Fix m-map file truncation leading to unsequential files.
|
|
3.32.3:
Various minor bug fixes
|
|
Release 3.3.0:
Highlights:
* ``LDAPError`` now contains additional fields, such as ctrls, result, msgid
* ``passwd_s`` can now extract the newly generated password
* LDAP connections can now be made from a file descriptor
This release is tested on Python 3.8, and the beta of Python 3.9.
The following undocumented functions are deprecated and scheduled for removal:
- ``ldap.cidict.strlist_intersection``
- ``ldap.cidict.strlist_minus``
- ``ldap.cidict.strlist_union``
Modules/
* Ensure ReconnectLDAPObject is not left in an inconsistent state after
a reconnection timeout
* Syncrepl now correctly parses SyncInfoMessage when the message is a syncIdSet
* Release GIL around global get/set option call
* Do not leak serverctrls in result functions
* Don't overallocate memory in attrs_from_List()
* Fix thread support check for Python 3
* With OpenLDAP 2.4.48, use the new header openldap.h
Lib/
* Fix some edge cases regarding quoting in the schema tokenizer
* Fix escaping a single space in ldap.escape_dn_chars
* Fix string formatting in ldap.compare_ext_s
* Prefer iterating dict instead of calling dict.keys()
Doc/
* Clarify the relationship between initialize() and LDAPObject()
* Improve documentation of TLS options
* Update FAQ to include Samba AD-DC error message
"Operation unavailable without authentication"
* Fix several incorrect examples and demos
(but note that these are not yet tested)
* Update Debian installation instructions for Debian Buster
* Typo fixes in docs and docstrings
Test/
* Test and document error cases in ldap.compare_s
* Test if reconnection is done after connection loss
* Make test certificates valid for the far future
* Use slapd -Tt instead of slaptest
Infrastructure:
* Mark the LICENCE file as a license for setuptools
* Use "unittest discover" rather than "setup.py test" to run tests
|
|
Update Ruby on Rails to 6.0.3.2.
www/ruby-actionpack60 is the really updated package and other packages
have no change except version.
CHANGELOG of www/ruby-actionpack60 is here:
## Rails 6.0.3.2 (June 17, 2020) ##
* [CVE-2020-8185] Only allow ActionableErrors if
show_detailed_exceptions is enabled
|
|
|
|
0.37.8:
Unknown changes
|
|
|
|
While here hook a working log4j properties file to silence startup with
all the "Missing classes" errors
Changelog:
Bug Fixes (2)
SOLR-14411: Fix Admin UI collection/core drop-downs placeholder text. Comple
tes work started in SOLR-14359
(janhoy)
SOLR-14471: Fix bug in shards.preference behavior, base replica selection st
rategy not applied to the last group of equivalent replicas.
(Michael Gibney via Tomas Fernandez Lobbe)
|
|
0.16.13
Default install of tortoise-orm now installs with no C-dependencies, if you want to use the C accelerators, please do a pip install tortoise-orm[accel] instead.
Added <instance>.clone() method that will create a cloned instance in memory. To persist it you still need to call .save()
.clone() will raise a ParamsError if tortoise can’t generate a primary key. In that case do a .clone(pk=<newval>)
If manually setting the primary key value to None and the primary key can be automatically generated, this will create a new record. We however still recommend the .clone() method instead.
.save() can be forced to do a create by setting force_create=True
.save() can be forced to do an update by setting force_update=True
Setting update_fields for a .save() operation will strongly prefer to do an update if possible
|
|
Redis 6.0.5
Upgrade urgency MODERATE: several bugs with moderate impact are fixed here.
The most important issues are listed here:
* Fix handling of speical chars in ACL LOAD.
* Make Redis Cluster more robust about operation errors that may lead
to two clusters to mix together.
* Revert the sendfile() implementation of RDB transfer. It causes some delay.
* Fix TLS certificate loading for chained certificates.
* Fix AOF rewirting of KEEPTTL SET option.
* Fix MULTI/EXEC behavior during -BUSY script errors.
|
|
4.2.7:
mongos crashes due to client disconnecting when signing keys being refreshed
The mongos routing for scatter/gather ops can have unbounded latency
Shutdown command with force:true should ignore all stepdown errors
Ability to specify sync source read preference in initial sync
|
|
2.19.0:
[FEATURE] TSDB: Memory-map full chunks of Head (in-memory) block from disk. This reduces memory footprint and makes restarts faster.
[ENHANCEMENT] Discovery: Added discovery support for Triton global zones.
[ENHANCEMENT] Increased alert resend delay to be more tolerant towards failures.
[ENHANCEMENT] Remote Read: Added prometheus_remote_storage_remote_read_queries_total counter to count total number of remote read queries.
[ENHANCEMEMT] Added time range parameters for label names and label values API.
[ENHANCEMENT] TSDB: Reduced contention in isolation for high load.
[BUGFIX] PromQL: Eliminated collision while checking for duplicate labels.
[BUGFIX] React UI: Don't null out data when clicking on the current tab.
[BUGFIX] PromQL: Correctly track number of samples for a query.
[BUGFIX] PromQL: Return NaN when histogram buckets have 0 observations.
[BUGFIX] TSDB: Fix incorrect query results when using Prometheus with remote reads configured
|
|
3.32.2-r1
Added constants:
SQLITE_IOERR_DATA, SQLITE_CORRUPT_INDEX, SQLITE_BUSY_TIMEOUT, SQLITE_FCNTL_CKPT_START, SQLITE_FCNTL_RESERVE_BYTES
|
|
|
|
Apache Solr is an open source enterprise search server based on the Apache
Lucene Java search library, with XML/HTTP and JSON APIs, hit highlighting,
faceted search, caching, replication, and a web administration interface.
|
|
changes unknown
|
|
3.5.3:
* Restore try/except clauses to __del__ methods. These will be removed
in 4.0 when more explicit resource management if enforced.
* Update the master_address when Sentinels promote a new master.
* Update SentinelConnectionPool to not forcefully disconnect other in-use
connections which can negatively affect threaded applications.
|
|
Update ruby-sequel to 5.33.0.
=== 5.33.0 (2020-06-01)
* Support custom join types on a per-association basis when using eager_graph/association_join (jeremyevans)
* Support primary_key with type: :smallserial on PostgreSQL (j-a-m-l) (#1698)
* Add Database#current_timestamp_utc accessor on SQLite to keep CURRENT_* in UTC instead of converting to localtime (jeremyevans)
|
|
|
|
3.32.2:
Fix a long-standing bug in the byte-code engine that can cause a COMMIT command report as success when in fact it failed to commit.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It had previously been yes, therefore this is the default value.
|
|
|
|
|
|
|
|
|
|
|
|
Redis 6.0.4
===========
Upgrade urgency CRITICAL: this release fixes a severe replication bug.
Redis 6.0.4 fixes a critical replication bug caused by a new feature introduced
in Redis 6. The feature, called "meaningful offset" and strongly wanted by
myself (antirez) was an improvement that avoided that masters were no longer
able, during a failover where they were demoted to replicas, to partially
synchronize with the new master. In short the feature was able to avoid full
synchronizations with RDB. How did it work? By trimming the replication backlog
of the final "PING" commands the master was sending in the replication channel:
this way the replication offset would no longer go "after" the one of the
promoted replica, allowing the master to just continue in the same replication
history, receiving only a small data difference.
However after the introduction of the feature we (the Redis core team) quickly
understood there was something wrong: the apparently harmless feature had
many bugs, and the last bug we discovered, after a joined effort of multiple
people, we were not even able to fully understand after fixing it. Enough was
enough, we decided that the complexity cost of this feature was too high.
So Redis 6.0.4 removes the feature entirely, and fixes the data corruption that
it was able to cause.
However there are two facts to take in mind.
Fact 1: Setups using chained replication, that means that certain replicas
are replicating from other replicas, up to Redis 6.0.3 can experience data
corruption. For chained replication we mean that:
+--------+ +---------+ +-------------+
| master |--------->| replica |-------->| sub-replica |
+--------+ +---------+ +-------------+
People using chained replication SHOULD UPGRADE ASAP away from Redis 6.0.0,
6.0.1, 6.0.2 or 6.0.3 to Redis 6.0.4.
To be clear, people NOT using this setup, but having just replicas attached
directly to the master, SHOUDL NOT BE in danger of any problem. But we
are no longer confident on 6.0.x replication implementation complexities
so we suggest to upgrade to 6.0.4 to everybody using an older 6.0.3 release.
We just so far didn't find any bug that affects Redis 6.0.3 that does not
involve chained replication.
People starting with Redis 6.0.4 are fine. People with Redis 5 are fine.
People upgrading from Redis 5 to Redis 6.0.4 are fine.
TLDR: The problem is with users of 6.0.0, 6.0.1, 6.0.2, 6.0.3.
Fact 2: Upgrading from Redis 6.0.x to Redis 6.0.4, IF AND ONLY IF you
use chained replication, requires some extra care:
1. Once you attach your new Redis 6.0.4 instance as a replica of the current
Redis 6.0.x master, you should wait for the first full synchronization,
then you should promote it right away, if your setup involves chained
replication. Don't give it the time to do a new partial synchronization
in the case the link between the master and the replica will break in
the mean time.
2. As an additional care, you may want to set the replication ping period
to a very large value (for instance 1000000) using the following command:
CONFIG SET repl-ping-replica-period 1000000
Note that if you do "1" with care, "2" is not needed.
However if you do it, make sure to later restore it to its default:
CONFIG SET repl-ping-replica-period 10
So this is the main change in Redis 6. Later we'll find a different way in
order to achieve what we wanted to achieve with the Meaningful Offset feature,
but without the same complexity.
Other changes in this release:
* PSYNC2 tests improved.
* Fix a rare active defrag edge case bug leading to stagnation
* Fix Redis 6 asserting at startup in 32 bit systems.
* Redis 6 32 bit is now added back to our testing environments.
* Fix server crash for STRALGO command,
* Implement sendfile for RDB transfer.
* TLS fixes.
* Make replication more resistant by disconnecting the master if we
detect a protocol error. Basically we no longer accept inline protocol
from the master.
* Other improvements in the tests.
|
|
|
|
0.37.7:
Bug fixes
|
|
2.18.1:
[BUGFIX] TSDB: Fixed snapshot API.
2.18.0:
[CHANGE] Federation: Only use local TSDB for federation (ignore remote read).
[CHANGE] Rules: rule_evaluations_total and rule_evaluation_failures_total have a rule_group label now.
[FEATURE] Tracing: Added experimental Jaeger support
[ENHANCEMENT] TSDB: Significantly reduce WAL size kept around after a block cut.
[ENHANCEMENT] Discovery: Add architecture meta label for EC2.
[BUGFIX] UI: Fixed wrong MinTime reported by /status.
[BUGFIX] React UI: Fixed multiselect legend on OSX.
[BUGFIX] Remote Write: Fixed blocked resharding edge case.
[BUGFIX] Remote Write: Fixed remote write not updating on relabel configs change.
|
|
Changes in version 3.32.1:
Fix two long-standing bugs that allow malicious SQL statements to crash the process that is running SQLite. These bugs were announced by a third-party approximately 24 hours after the 3.32.0 release but are not specific to the 3.32.0 release.
Other minor compiler-warning fixes and whatnot.
|
|
|
|
|
|
|
|
|
