Switch from Mk/bsd.ruby.mk to Mk/Uses/ruby.mk
Notable changes are.
- Mk/bsd.ruby.mk is moved to Mk/Uses/ruby.mk.
- USE_RUBY=yes is replaced with USES=ruby.
- USE_RUBY_EXTCONF is replaced with USES=ruby:extconf.
- USE_RUBY_RDOC is replaced with USES=ruby:rdoc.
- USE_RUBY_SETUP is replaces with USES=ruby:setup.
- RUBY_NO_BUILD_DEPENDS and RUBY_NO_RUN_DEPENDS are replaced with
USES=ruby:{build,none,run}.
- RUBY_REQUIRE isn't used anywhere, so removed.
- USES=gem now implies USES=ruby.
This is mainly the work of yasu@ at https://reviews.freebsd.org/D27863
I have just made some cosmetic changes and ran exp-run to test that the
tree is not in a BROKEN state.
Approved by: portmgr
Differential Revision: https://reviews.freebsd.org/D37925
Commit b7f05445c0 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)
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.
This commit implements such a proposal and moves one of the WWW: entries
of each pkg-descr file into the respective port's Makefile. A heuristic
attempts to identify the most relevant URL in case there is more than
one WWW: entry in some pkg-descr file. URLs that are not moved into the
Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr
files in order to preserve them.
There are 1256 ports that had no WWW: entries in pkg-descr files. These
ports will not be touched in this commit.
The portlint port has been adjusted to expect a WWW entry in each port
Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as
deprecated.
Approved by: portmgr (tcberner)
* 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
opt_VARS always upcases its argument, so the defined(_addflags)
check will never be true.
The _ADDFLAGS block overwrites the global CFLAGS and LDFLAGS which
is also suspicous and probably not quite right.
Reported by: portscan
Remove added to the upstream patch.
<ChangeLog>
================================================================================
Redis 6.0.12 Released Mon Mar 1 17:29:52 IST 2021
================================================================================
Upgrade urgency: LOW, fixes a compilation issue.
Bug fixes:
* Fix compilation error on non-glibc systems if jemalloc is not used (#8533)
</ChangeLog>
Integer overflow on 32-bit systems (CVE-2021-21309):
Redis 4.0 or newer uses a configurable limit for the maximum supported bulk
input size. By default, it is 512MB which is a safe value for all platforms.
If the limit is significantly increased, receiving a large request from a client
may trigger several integer overflow scenarios, which would result with buffer
overflow and heap corruption.
Various bugfixes.
<ChangeLog>
Upgrade urgency:CRITICAL if you use Streams with AOF ore replicas.
Otherwise the upgrade urgency is LOW.
This release has a speed improvement and a critical fix:
* FIX: XREADGROUP when fetching data in a blocking way, would not
emit the XCLAIM in the AOF file and to replicas. This means
that the last ID is not updated, and that restarting the server
will have the effect of reprocessing some entries.
* NEW: Clients blocked on the same key are now unblocked on
O(1) time. Backported from Redis 6.
</ChangeLog>
<ChangeLog>
Upgrade urgency HIGH: many issues fixed, some may have an impact.
Hi all, Redis 5.0.7 fixes a number of bugs, none is very critical, however
there are a few that may have an impact. It's a good idea to upgrade.
There are fixes in the area of replication from modules commands and
callbacks, AOF fsync (non critical issue), memory leaks (very rare and small),
streams beahvior (non critical), and a potential crash in commands
processing multiple keys at the same time that is there for years, and happens
very rarely, but is not impossible to trigger.
</ChangeLog>
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
<ChangeLog>
================================================================================
Redis 4.0.14 Released Mon Mar 18 17:22:10 CEST 2019
================================================================================
This release just backports a few fixes from Redis 5:
3c62ad19 HyperLogLog: handle wrong offset in the base case.
cc2b3a68 Fix hyperloglog corruption
e10c79d3 redis-check-aof: fix potential overflow.
6fa16f58 Fix mismatching keyspace notification classes
64311052 Fix zlexrangespec mem-leak in genericZrangebylexCommand
b0e86319 Make comment in #5911 stay inside 80 cols.
39ccce03 Replicas aren't allowed to run the replicaof command
================================================================================
Redis 4.0.13 Released Wed Feb 20 17:25:31 CEST 2019
================================================================================
This release just backports a few fixes from Redis 5:
60b2537f rewrite BRPOPLPUSH as RPOPLPUSH to propagate
afc4b36c Don't treat unsupported protocols as fatal errors
</ChangeLog>
<ChangeLog>
================================================================================
Redis 4.0.12 Released Tue Dec 11 18:06:12 CEST 2018
================================================================================
This backports the following Redis 5 fixes back into Redis 4.
Please check the Redis 5 changelog or see the full commit messages
for more information. Note that there are important fixes to the AOF
implementation so Redis 4.0.12 should be considered as a worthwhile
upgrade in production environments where AOF is used and there is the
idea of sticking with Redis 4 for some time.
b6cd3b3c asyncCloseClientOnOutputBufferLimitReached(): don't free fake clients.
e16402b0 Don't call sdscmp() with shared.maxstring or shared.minstring
49d9f411 Fix stringmatchlen() read past buffer bug.
97192e2d Merge pull request #5569 from maximebedard/backport-4497
1908aba7 add linkClient(): adds the client and caches the list node.
239b0857 networking: optimize unlinkClient() in freeClient()
54b17f98 When replica kills a pending RDB save during SYNC, log it.
b31c08db Move child termination to readSyncBulkPayload
21971ac8 Prevent RDB autosave from overwriting full resync results
3a91fcbc aof.c: improve indentation and change warning message.
e6f287d5 AOF: discard if we lost EXEC when loading aof
e0d4c66a Fix AOF comment to report the current behavior.
</ChangeLog>
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
<ChangeLog>
Upgrade urgency HIGH: not critical but very important bugs fixed.
Dear users, this is just a bugfix release of Redis 4. All new work
is now focused on Redis 5, however we backported a number of bug fixes here:
* The disconnection time between the master and slave was reset in an
incorrect place, sometimes a good slave will not be able to failover
because it claims it was disconnected for too much time from the master.
* A replication bug, rare to trigger but non impossible, is in Redis for
years. It was lately discovered at Redis Labs and fixed by Oran Agra.
It may cause disconnections, desynchronizations and other issues.
* RANDOMKEY may go in infinite loop on rare situations. Now fixed.
* EXISTS now works in a more consistent way on slaves.
* Sentinel: backport of an option to deny a potential security problem
when the SENTINEL command is used to configure an arbitrary script
to execute.
Many of these issues are there for a very long time, however upgrading
is a good idea.
</ChangeLog>
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
Update CONFLICTS.
<ChangeLog>
Redis 4.0.10 fixes a number of important issues:
* Important security issues related to the Lua scripting engine.
Please check https://github.com/antirez/redis/issues/5017
for more information.
* A bug with SCAN, SSCAN, HSCAN and ZSCAN, that may not return all the elements.
We also add a regression test that can trigger the issue often when present, and
may in theory be able to find unrelated regressions.
* A PSYNC2 bug is fixed: Redis should not expire keys when saving RDB files
because otherwise it is no longer possible to use such RDB file as a base
for partial resynchronization. It no longer represents the right state.
* Compatibility of AOF with RDB preamble when the RDB checksum is disabled.
* Sentinel bug that in some cases prevented Sentinel to detect that the master
was down immediately. A delay was added to the detection.
* Other minor issues.
</ChangeLog>