Update php-xdebug to 2.9.5.
php-xdebug 2.9.5 (2020-04-25)
Fixed bugs:
- Fixed issue #1772: Crash with exception thrown inside a destructor
- Fixed issue #1775: Segfault when another extension compiles a PHP file
during RINIT
- Fixed issue #1779: Nested multi-line built-in function in namespace are
not covered
Update postfix to 3.5.1.
3.5.0 (2020-03-16)
Postfix stable release 3.5.0 is available. Support has ended for
legacy release Postfix 3.1.
The main changes are below. See the RELEASE_NOTES file for further details.
* Support for the haproxy v2 protocol. The Postfix implementation
supports TCP over IPv4 and IPv6, as well as non-proxied
connections; the latter are typically used for heartbeat tests.
* Support to force-expire email messages. This introduces new
postsuper(1) command-line options to request expiration, and
additional information in mailq(1) or postqueue(1) output.
* The Postfix SMTP and LMTP client support a list of nexthop
destinations separated by comma or whitespace. These destinations
will be tried in the specified order. Examples:
/etc/postfix/main.cf:
relayhost = foo.example, bar.example
default_transport = smtp:foo.example, bar.example
Incompatible changes:
* Logging: Postfix daemon processes now log the from= and to=
addresses in external (quoted) form in non-debug logging (info,
warning, etc.). This means that when an address localpart
contains spaces or other special characters, the localpart will
be quoted, for example:
from=<"name with spaces"@example.com>
Specify "info_log_address_format = internal" for backwards compatibility.
* Postfix now normalizes IP addresses received with XCLIENT,
XFORWARD, or with the HaProxy protocol, for consistency with
direct connections to Postfix. This may change the appearance
of logging, and the way that check_client_access will match
subnets of an IPv6 address.
3.5.1 (2020-04-20)
Postfix versions 3.5.1, 3.4.11, 3.3.9, 3.2.14:
* Bitrot workaround for broken builds after an incompatible change
in GCC 10.
* Bitrot workaround for broken DANE/DNSSEC support after an
incompatible change in GLIBC 2.31. This change avoids the need
for new options in /etc/resolv.conf.
Update drupal8 to 8.7.12.
Release notes
Maintenance and security release of the Drupal 8 series.
This release fixes security vulnerabilities. Sites are urged to upgrade
immediately after reading the notes below and the security announcement:
* Drupal core - Moderately critical - Third-party library - SA-CORE-2020-001
No other fixes are included.
Which release do I choose? Security coverage information
* Sites on 8.7.x will receive security coverage until June 3, 2020 (when
Drupal 8.9.0 is scheduled for release).
* Versions of Drupal 8 prior to 8.7.x are end-of-life and do not receive
security coverage.
Important update information
No changes have been made to the .htaccess, web.config, robots.txt or
default settings.php files in this release, so upgrading custom versions of
those files is not necessary if your site is already on the previous
release.
Fix roundcube-plugin-password.
* Patch for roundcube-plugin-password had not been applied accidently.
* More changes were required to make it work on *BSD system.
Bump PKGREVISION.
Update ruby-sequel to 5.31.0.
=== 5.31.0 (2020-04-01)
* Fix alter_table drop_constraint :primary_key option on SQLite for non-integer primary keys (jeremyevans)
* Add skip_saving_columns plugin, which supports columns to skip when saving, and skips generated columns by default (joeosburn, jeremyevans) (#1681, #1682)
* Add support for creating partitioned tables in PostgreSQL 10+ using :partition_by and :partition_of options (jeremyevans)
* Dump generated columns as generated columns when using the schema_dumper with :same_db option on PostgreSQL 12+ (jeremyevans) (#1680)
* Ignore defaults for generated columns by default when using the schema dumper (jeremyevans) (#1680)
* Include generated columns in schema on SQLite 3.31+ (jeremyevans)
* Add :generated schema entry on PostgreSQL 12+ and SQLite 3.31+ for whether the columns is generated (jeremyevans)
* Add association_lazy_eager_option plugin for supporting :eager option for association method (jeremyevans)
* Add forbid_lazy_load plugin for forbidding lazy loading of associations, to help find N+1 issues (jeremyevans)
Update ruby-activeldap to 6.0.1.
## 6.0.1: 2020-04-21 {#release-6-0-1}
### Improvements
* Dropped support for Ruby 2.4.
* Stopped using paged results when we need only one entry.
[GitHub#173][Patch by Kevin McCormack]
### Thanks
* Kevin McCormack
## 6.0.0: 2020-04-16 {#release-6-0-0}
### Improvements
* Removed needless `rubyforge_project` from `.gemspec`.
[GitHub#167][Patch by Olle Jonsson]
* Added support for reusing parent configuration for omitted
configuration items when creating a connection per class or DN.
* jndi: Added support for processing DN that includes backslash.
* jndi: Added a CI job for JRuby 9.
[GitHub#170][Patch by Kevin McCormack]
* jndi: Added support for paged search.
[GitHub#171][Patch by Kevin McCormack]
* Added support for Active Model 6.
* `search`: Added `:used_paged_results` and `:page_size` options.
### Thanks
* Olle Jonsson
* Kevin McCormack
LXQt is a free desktop environment with comparatively low resource
requirements. This makes it especially suitable for resource-constrained
personal computers such as netbooks or system-on-a-chip machines.
(Packaged in wip by pin@, additional changes by myself.)
Place the panel settings configuration file where the rest of LXQt (as
configured in pkgsrc presently) expects it to be, so fallbacks work if
a user doesn't already have a custom configuration defined. (Ride
previous commits of LXQt earlier today; this doesn't merit a recursive
dependency bump.)
Place the desktop settings configuration file where the rest of LXQt
(as configured in pkgsrc presently) expects it to be, so fallbacks
work if a user doesn't already have a custom configuration defined.
This does not affect standalone use of this application, only its
functionality that provides the desktop background for LXQt. (Ride
previous commits of LXQt earlier today; this doesn't merit a recursive
dependency bump.)
One is via "${JAVA_BINPREFIX}-java", and one is via
"${PKG_JAVA_HOME}/bin/java".
The "${JAVA_BINPREFIX}-java" way relies on an appropriately named
executable being present in the built-in JRE if you are using the
built-in - something with a "-java" suffix. That just doesn't exist
in either the MacOS Oracle JRE install or the JDK install. So switch
to "${PKG_JAVA_HOME}/bin/java" instead, which works (but does require
careful quoting to allow for spaces under MacOS).
Bump PKGREVISION.
goldmark is a Markdown parser written in Go. It is compliant with
CommonMark 0.29. Its features include:
- Standards-compliant. goldmark is fully compliant with the latest
CommonMark specification.
- Extensible. Do you want to add a @username mention syntax to
Markdown? You can easily do so in goldmark. You can add your AST
nodes, parsers for block-level elements, parsers for inline-level
elements, transformers for paragraphs, transformers for the whole
AST structure, and renderers.
- Performance. goldmark's performance is on par with that of cmark,
the CommonMark reference implementation written in C.
- Robust. goldmark is tested with go-fuzz, a fuzz testing tool.
- Built-in extensions. goldmark ships with common extensions like
tables, strikethrough, task lists, and definition lists.
- Depends only on standard libraries.
