Changes since 22.2.4:
Makefiles in wip/mk may use internal variables (starting with '_'), just
like their counterparts in main mk/.
Package versions containing letters are now parsed like in pkg_install.
Noteworthy changes in version 1.18.0 (2022-08-10)
-------------------------------------------------
* New keylist mode to force refresh via external methods. [T5951]
* The keylist operations now create an import result to report the
result of the locate keylist modes. [T5951]
* core: Return BAD_PASSPHRASE error code on symmetric decryption
failure. [T5939]
* cpp, qt: Do not export internal symbols anymore. [T5906]
* cpp, qt: Support revocation of own OpenPGP keys. [T5904]
* qt: The file name of (signed and) encrypted data can now be set. [T6056]
* cpp, qt: Support setting the primary user ID. [T5938]
* python: Fix segv(NULL) when inspecting contect after exeception. [T6060]
This works around a subtle bug in github.mk.
Long story short is GITHUB_PROJECT is used to infer WRKSRC when github.mk
is in use. In addition, GITHUB_PROJECT is inferred from DISTNAME when
not explicitly set by the package.
If one wants to reference WRKSRC in a BUILDLINK_TRANSFORM, that breaks
because cwrappers.mk is evaluated before bsd.fetch.mk and GITHUB_PROJECT
is not yet known at that point, leading to an invalid WRKSRC expansion.
compatible with upstream Bitwarden password manager clients.
It is well-suited for self-hosted deployment, where running the
official resource-heavy service might not be ideal.
pkgsrc changes:
* Add "USE_TOOLS+= pax" to plugins.mk.
* Add some note to MESSAGES.
* update DESCR.
1.6.0 (2022-07-28)
We proudly announce the release of the next major version 1.6 of Roundcube
webmail. With this milestone we cleaned up the codebase and bring full
support for PHP 8.1. The most noteworthy changes, as already announced with
the beta release, are:
* PHP 8.1 support
* Dropped support for PHP < 7.3
* Support responses (snippets) in HTML format
* Option to purge deleted mails older than 30, 60 or 90 days
* Unified and simplified services connection config options
* Removed the Classic and Larry skins from the release packages
* SQLite: Use foreign keys, require SQLite >= 3.6.19
See the full changelog in the release notes on the Github download page.
Breaking Changes to 1.5 and prior versions
The following config options have either been removed or renamed:
1. IMAP:
* renamed default_host to imap_host
* removed default_port option (non-standard port can be set via
imap_host)
* set "localhost:143" as a default for imap_host
2. SMTP:
* renamed smtp_server to smtp_host
* removed smtp_port option (non-standard port can be set via smtp_host)
* set "localhost:587" as a default for smtp_host
3. LDAP:
* removed port option from ldap_public array (non-standard port can be set
via host)
* removed use_tls option from ldap_public array (use tls:// prefix in host)
4. Managesieve:
* removed managesieve_port option (non-standard port can be set via
managesieve_host)
* removed managesieve_usetls option (set tls:// prefix to managesieve_host)
9.16.32 (2022-08-17)
Notes for BIND 9.16.32
Feature Changes
* The DNSSEC algorithms RSASHA1 and NSEC3RSASHA1 are now automatically
disabled on systems where they are disallowed by the security policy
(e.g. Red Hat Enterprise Linux 9). Primary zones using those algorithms
need to be migrated to new algorithms prior to running on these systems,
as graceful migration to different DNSSEC algorithms is not possible when
RSASHA1 is disallowed by the operating system. [GL #3469]
* Log messages related to fetch limiting have been improved to provide more
complete information. Specifically, the final counts of allowed and
spilled fetches are now logged before the counter object is destroyed.
[GL #3461]
Bug Fixes
* Non-dynamic zones that inherit dnssec-policy from the view or options
blocks were not marked as inline-signed and therefore never scheduled to
be re-signed. This has been fixed. [GL #3438]
* The old max-zone-ttl zone option was meant to be superseded by the
max-zone-ttl option in dnssec-policy; however, the latter option was not
fully effective. This has been corrected: zones no longer load if they
contain TTLs greater than the limit configured in dnssec-policy. For
zones with both the old max-zone-ttl option and dnssec-policy configured,
the old option is ignored, and a warning is generated. [GL #2918]
* rndc dumpdb -expired was fixed to include expired RRsets, even if
stale-cache-enable is set to no and the cache-cleaning time window has
passed. [GL #3462]
Changes:
1.6
---
* Code cleanups: unused code and refactored the code for reading read items
from a plain-text URL file list.
* Fix typos in the code and documentation.
* Improve clarity of some code comments.
* Add setsid example to the README.
