doc: Updated math/volk to 2.4.0

(tnn)

volk: update to 2.4.0

pkgsrc: since the volk release tarball only provides the required cpu_features
library as a git submodule that has to be manually cloned, we instead depend on
devel/cpu_features from pkgsrc and patch the cmake files to accept the static
library as an external dependency.

Documentation
  Update README to be more verbose and to improve usefulness.
Compilers
  AppleClang: Treat AppleClang as Clang.
  Paired with the cpu_features introduction, this enables us to use architecture
    specific kernels on a broader set of platforms.
CMake
  Enable to not install volk_modtool.
  Remove "find_package_handle_standard_args" warning.
cpu_features
  Use cpu_features v0.6.0 as a private submodule to detect available CPU
  features.
  Fix incorrect feature detection for newer AVX versions.
  Circumvent platform specific feature detection.
  Enable more architecture specific kernels on more platforms.
Kernels
  Disable slow and broken SSE4.1 kernel in volk_32fc_x2_dot_prod_32fc
  Adjust min/max for 32f_s32f_convert_8i kernel
  Use INT8_* instead of CHAR_*

(tnn)

fix whitespace

(tnn)

cpu_features: pass -DBUILD_PIC=ON to cmake

(tnn)

Prefer openjdk11 to adoptopenjdk11-bin for NetBSD

(In the _PKG_JVMS.9 case)

(abs)

Updated net/syncthing to 1.12.0

(abs)

Updated net/syncthing to 1.12.0

Bugfixes:

  #5360: Dangling symlink prevents filesystem watcher on FreeBSD
  #6664: Panic due to internal folder context used on exported methods
  #7063: panic: runtime error: invalid memory address or nil pointer dereference
  #7077: GUI stuck with "id is not defined" error when trying to ignore non-existent folder
  #7098: File deletions are not being synced in newly shared folders

Enhancements:

  #6540: Config PATCH/PUT/DELETE API
  #7099: Add a html message to GUI when javascript is disabled
  #7108: Certificate for relaysrv with better naming

(abs)

binutils: don't use hard-coded -ldl in the gold test suite.

(fcambus)

doc: add devel/cpu_features

(tnn)

devel/cpu_features: import cpu_features-0.6.0

A cross-platform C library to retrieve CPU features
(such as available instructions) at runtime.

(tnn)

Updated devel/py-sortedcontainers, devel/py-intervaltree

(adam)

py-intervaltree: updated to 3.1.0

Version 3.1.0
- Dropped support for Python 3.4, added Python 3.8
- Add `__slots__` optimization in Node class, should give performance improvement
- Fixed:
  - Restore universal wheels
  - Bytes/str type incompatibility in setup.py
  - New version of distutils rejects version suffixes of `.postNN`, use `aNN` instead

(adam)

py-sortedcontainers: updated to 2.3.0

2.3.0:
Bugfixes
Make sort order stable when updating with large iterables.

(adam)

Updated textproc/py-elementpath, devel/py-restructuredtext_lint

(adam)

py-restructuredtext_lint: updated to 1.3.2

1.3.2 - Added "Other tools" section to README.

(adam)

py-elementpath: updated to 2.0.5

2.0.5:
* Increase the speed of path step selection on large trees
* More tests and small fixes to XSD builtin datatypes

(adam)

doc: Document several packages removals

Noticed via pkg-changes2html script.

(leot)

doc: Updated mail/qmail-run to 20201214

(schmonz)

Depend on qmail-acceptutils 20201214 for fixsmtpio(8) segfault fix.
Bump version.

(schmonz)

doc: Updated mail/qmail-acceptutils to 20201214

(schmonz)

Update to 20201214. From the changelog:

- fixsmtpio: Fix segfault by making sure eventq_get() returns a
  free()-able string.

(schmonz)

doc: Updated net/powerdns-recursor to 4.4.2

(otis)

net/powerdns-recursor: Update to 4.4.2

Changelog:
Released: 14th of December 2020

* Improvements:
  - UUID: Use the non-cryptographic variant of the boost::uuid.
  - Keep a cached, valid entry over a fresher Bogus one.
  - Ensure socket-dir matches runtime directory on old systemd
  - Move to several distinct Bogus states, for easier debugging.
  - Do not chase CNAME during qname minimization step 4.

* Bug Fixes:
  - Untangle the validation/resolving qnames and qtypes.
  - APL records: fix endianness problem.

(otis)

py-kitchen: Fix PLIST on older Python versions

(nia)

py-solo: Unbreak bulk builds.

(jperkin)

nudoku: Needs gettext m4 macros to build

(nia)

tty-clock: Add missing patch.

(nia)

(devel/ocaml-ppx_cold) Add ocaml-base as buildlink3.mk

(mef)

sane-airscan: Unbreak. Needs pkg-config to build properly.

(nia)

stone-stoup-sdl: Needs external copy of DejaVu to copy into place

(nia)

ncmpcpp: Needs getmouse in libcurses

(nia)

x11/tk: avoid x11 when building aqua

(dbj)

x11/tk: don't pull in pthreads when threads are disabled

(dbj)

Updated security/py-cryptography, security/py-cryptography_vectors

(adam)

py-cryptography py-cryptography_vectors: updated to 3.3.1

3.3.1:
* Re-added a legacy symbol causing problems for older ``pyOpenSSL`` users.

3.3:
* **BACKWARDS INCOMPATIBLE:** Support for Python 3.5 has been removed due to
  low usage and maintenance burden.
* **BACKWARDS INCOMPATIBLE:** The
  :class:`~cryptography.hazmat.primitives.ciphers.modes.GCM` and
  :class:`~cryptography.hazmat.primitives.ciphers.aead.AESGCM` now require
  64-bit to 1024-bit (8 byte to 128 byte) initialization vectors. This change
  is to conform with an upcoming OpenSSL release that will no longer support
  sizes outside this window.
* **BACKWARDS INCOMPATIBLE:** When deserializing asymmetric keys we now
  raise ``ValueError`` rather than ``UnsupportedAlgorithm`` when an
  unsupported cipher is used. This change is to conform with an upcoming
  OpenSSL release that will no longer distinguish between error types.
* **BACKWARDS INCOMPATIBLE:** We no longer allow loading of finite field
  Diffie-Hellman parameters of less than 512 bits in length. This change is to
  conform with an upcoming OpenSSL release that no longer supports smaller
  sizes. These keys were already wildly insecure and should not have been used
  in any application outside of testing.
* Updated Windows, macOS, and ``manylinux`` wheels to be compiled with
  OpenSSL 1.1.1i.
* Python 2 support is deprecated in ``cryptography``. This is the last release
  that will support Python 2.
* Added the
  :meth:`~cryptography.hazmat.primitives.asymmetric.rsa.RSAPublicKey.recover_data_from_signature`
  function to
  :class:`~cryptography.hazmat.primitives.asymmetric.rsa.RSAPublicKey`
  for recovering the signed data from an RSA signature.

(adam)

Updated net/py-zeroconf, devel/py-msgpack

(adam)

py-msgpack: updated to 1.0.1

1.0.1
Add Python 3.9 and linux/arm64 wheels.
Fixed Unpacker.tell() after read_bytes()
Fixed unpacking datetime before epoch on Windows
Fixed fallback Packer didn't check DateTime.tzinfo

(adam)

py-zeroconf: updated to 0.28.7

0.28.7
Fixed the IPv6 address rendering in the browser example
Fixed a crash happening when a service is added or removed during handle_response and improved exception handling

(adam)

security/py-google-auth, devel/py-wheel, devel/py-py, devel/py-test

(adam)

py-test: updated to 6.2.0

pytest 6.2.0 (2020-12-12)
=========================

Breaking Changes
----------------
- pytest now supports python3.6+ only.

Deprecations
------------
- Directly constructing/calling the following classes/functions is now deprecated:
  - ``_pytest.cacheprovider.Cache``
  - ``_pytest.cacheprovider.Cache.for_config()``
  - ``_pytest.cacheprovider.Cache.clear_cache()``
  - ``_pytest.cacheprovider.Cache.cache_dir_from_config()``
  - ``_pytest.capture.CaptureFixture``
  - ``_pytest.fixtures.FixtureRequest``
  - ``_pytest.fixtures.SubRequest``
  - ``_pytest.logging.LogCaptureFixture``
  - ``_pytest.pytester.Pytester``
  - ``_pytest.pytester.Testdir``
  - ``_pytest.recwarn.WarningsRecorder``
  - ``_pytest.recwarn.WarningsChecker``
  - ``_pytest.tmpdir.TempPathFactory``
  - ``_pytest.tmpdir.TempdirFactory``

  These have always been considered private, but now issue a deprecation warning, which may become a hard error in pytest 7.0.0.

- The ``--strict`` command-line option has been deprecated, use ``--strict-markers`` instead.

  We have plans to maybe in the future to reintroduce ``--strict`` and make it an encompassing flag for all strictness
  related options (``--strict-markers`` and ``--strict-config`` at the moment, more might be introduced in the future).

- The ``@pytest.yield_fixture`` decorator/function is now deprecated. Use :func:`pytest.fixture` instead.

  ``yield_fixture`` has been an alias for ``fixture`` for a very long time, so can be search/replaced safely.

Features
--------
- pytest now warns about unraisable exceptions and unhandled thread exceptions that occur in tests on Python>=3.8.
  See :ref:`unraisable` for more information.
- New :fixture:`pytester` fixture, which is identical to :fixture:`testdir` but its methods return :class:`pathlib.Path` when appropriate instead of ``py.path.local``.

  This is part of the movement to use :class:`pathlib.Path` objects internally, in order to remove the dependency to ``py`` in the future.

  Internally, the old :class:`Testdir <_pytest.pytester.Testdir>` is now a thin wrapper around :class:`Pytester <_pytest.pytester.Pytester>`, preserving the old interface.

- A new hook was added, `pytest_markeval_namespace` which should return a dictionary.
  This dictionary will be used to augment the "global" variables available to evaluate skipif/xfail/xpass markers.

  Pseudo example

  ``conftest.py``:

  .. code-block:: python

    def pytest_markeval_namespace():
        return {"color": "red"}

  ``test_func.py``:

  .. code-block:: python

    @pytest.mark.skipif("color == 'blue'", reason="Color is not red")
    def test_func():
        assert False

- It is now possible to construct a :class:`~pytest.MonkeyPatch` object directly as ``pytest.MonkeyPatch()``,
  in cases when the :fixture:`monkeypatch` fixture cannot be used. Previously some users imported it
  from the private `_pytest.monkeypatch.MonkeyPatch` namespace.

  Additionally, :meth:`MonkeyPatch.context <pytest.MonkeyPatch.context>` is now a classmethod,
  and can be used as ``with MonkeyPatch.context() as mp: ...``. This is the recommended way to use
  ``MonkeyPatch`` directly, since unlike the ``monkeypatch`` fixture, an instance created directly
  is not ``undo()``-ed automatically.

Improvements
------------
- Added an ``__str__`` implementation to the :class:`~pytest.pytester.LineMatcher` class which is returned from ``pytester.run_pytest().stdout`` and similar. It returns the entire output, like the existing ``str()`` method.
- Verbose mode now shows the reason that a test was skipped in the test's terminal line after the "SKIPPED", "XFAIL" or "XPASS".
- The types of builtin pytest fixtures are now exported so they may be used in type annotations of test functions.
  The newly-exported types are:
  - ``pytest.FixtureRequest`` for the :fixture:`request` fixture.
  - ``pytest.Cache`` for the :fixture:`cache` fixture.
  - ``pytest.CaptureFixture[str]`` for the :fixture:`capfd` and :fixture:`capsys` fixtures.
  - ``pytest.CaptureFixture[bytes]`` for the :fixture:`capfdbinary` and :fixture:`capsysbinary` fixtures.
  - ``pytest.LogCaptureFixture`` for the :fixture:`caplog` fixture.
  - ``pytest.Pytester`` for the :fixture:`pytester` fixture.
  - ``pytest.Testdir`` for the :fixture:`testdir` fixture.
  - ``pytest.TempdirFactory`` for the :fixture:`tmpdir_factory` fixture.
  - ``pytest.TempPathFactory`` for the :fixture:`tmp_path_factory` fixture.
  - ``pytest.MonkeyPatch`` for the :fixture:`monkeypatch` fixture.
  - ``pytest.WarningsRecorder`` for the :fixture:`recwarn` fixture.

  Constructing them is not supported (except for `MonkeyPatch`); they are only meant for use in type annotations.
  Doing so will emit a deprecation warning, and may become a hard-error in pytest 7.0.

  Subclassing them is also not supported. This is not currently enforced at runtime, but is detected by type-checkers such as mypy.

- When a comparison between :func:`namedtuple <collections.namedtuple>` instances of the same type fails, pytest now shows the differing field names (possibly nested) instead of their indexes.
- :meth:`Node.warn <_pytest.nodes.Node.warn>` now permits any subclass of :class:`Warning`, not just :class:`PytestWarning <pytest.PytestWarning>`.
- Improved reporting when using ``--collected-only``. It will now show the number of collected tests in the summary stats.
- Use strict equality comparison for non-numeric types in :func:`pytest.approx` instead of
  raising :class:`TypeError`.

  This was the undocumented behavior before 3.7, but is now officially a supported feature.

- New ``--sw-skip`` argument which is a shorthand for ``--stepwise-skip``.
- Added ``'node_modules'`` to default value for :confval:`norecursedirs`.
- :meth:`doClassCleanups <unittest.TestCase.doClassCleanups>` (introduced in :mod:`unittest` in Python and 3.8) is now called appropriately.

Bug Fixes
---------
- Fixed quadratic behavior and improved performance of collection of items using autouse fixtures and xunit fixtures.
- Fixed an issue where some files in packages are getting lost from ``--lf`` even though they contain tests that failed. Regressed in pytest 5.4.0.
-  Directories created by by :fixture:`tmp_path` and :fixture:`tmpdir` are now considered stale after 3 days without modification (previous value was 3 hours) to avoid deleting directories still in use in long running test suites.
-  Fixed a crash or hang in :meth:`pytester.spawn <_pytest.pytester.Pytester.spawn>` when the :mod:`readline` module is involved.
- Fixed handling of recursive symlinks when collecting tests.
- Fixed symlinked directories not being followed during collection. Regressed in pytest 6.1.0.
- Fixed only one doctest being collected when using ``pytest --doctest-modules path/to/an/__init__.py``.

Improved Documentation
----------------------
- Add more information and use cases about skipping doctests.
- Classes which should not be inherited from are now marked ``final class`` in the API reference.
- ``_pytest.config.argparsing.Parser.addini()`` accepts explicit ``None`` and ``"string"``.
- In pull request section, ask to commit after editing changelog and authors file.

Trivial/Internal Changes
------------------------
- The ``attrs`` dependency requirement is now >=19.2.0 instead of >=17.4.0.
- `.pyc` files created by pytest's assertion rewriting now conform to the newer PEP-552 format on Python>=3.7.
  (These files are internal and only interpreted by pytest itself.)

(adam)

py-py: updated to 1.10.0

1.10.0 (2020-12-12)
===================
- Fix a regular expression DoS vulnerability in the py.path.svnwc SVN blame functionality (CVE-2020-29651)
- Update vendored apipkg: 1.4 => 1.5
- Update vendored iniconfig: 1.0.0 => 1.1.1

(adam)

py-wheel: updated to 0.36.2

0.36.2
- Updated vendored ``packaging`` library to v20.8
- Fixed wheel sdist missing ``LICENSE.txt``
- Don't use default ``macos/arm64`` deployment target in calculating the
  platform tag for fat binaries

(adam)

py-google-auth: updated to 1.24.0

1.24.0

Features
add Python 3.9 support, drop Python 3.5 support

Bug Fixes
avoid losing the original '_include_email' parameter in impersonated credentials

Documentation
fix typo in import

(adam)

Updated devel/py-ipykernel, www/py-uvicorn, www/py-django-cors-headers, textproc/py-humanize

(adam)

py-humanize: updated to 3.2.0

3.2.0:

Added
Internationalise intcomma and add fr_FR

Changed
Apply setup-py-upgrade
Test Python 3.9 final on Travis CI

Fixed
Fix grammar mistake in the Dutch translations

(adam)

py-django-cors-headers: updated to 3.6.0

3.6.0:
Drop Python 3.5 support.
Support Python 3.9.

(adam)

py-uvicorn: updated to 0.13.1

0.13.1

Fixed

Prevent exceptions when the ASGI application rejects a connection during the WebSocket handshake, when running on both --ws wsproto or --ws websockets.
Ensure connection scope doesn't leak in logs when using JSON log formatters.

(adam)

py-ipykernel: updated to 5.4.2

5.4.2
- Revert "Fix stop_on_error_timeout blocking other messages in queue".

5.4.1
- Invalid syntax in ipykernel/log.py.

(adam)

Updated devel/R-testthat to 3.0.0

(mef)

(graphics/ocaml-cairo) Add ocaml-dune-configurator as buildlink3.mk

(mef)

(devel/R-testthat) Updated 2.3.2 to 3.0.0

# testthat 3.0.0

## 3rd edition

testhat 3.0.0 brings with it a 3rd edition that makes a number of breaking
changes in order to clean up the interface and help you use our latest
recommendations. To opt-in to the 3rd edition for your package, set
`Config/testthat/edition: 3` in your `DESCRIPTION` or use `local_edition(3)` in
individual tests. You can retrieve the active edition with `edition_get()`.
Learn more in `vignette("third-edition")`.

* `context()` is deprecated.

* `expect_identical()` and `expect_equal()` use `waldo::compare()` to
  compare actual and expected results. This mostly yields much more
  informative output when the actual and expected values are different,
  but while writing it uncovered some bugs in the existing comparison
  code.

* `expect_error()`, `expect_warning()`, `expect_message()`, and
  `expect_condition()` now all use the same underlying logic: they
  capture the first condition that matches `class`/`regexp` and
  allow anything else to bubble up (#998/#1052). They also warn if
  there are unexpected arguments that are never used.

* The `all` argument to `expect_message()` and `expect_warning()` is now
  deprecated. It was never a particularly good idea or well documented,
  and is now superseded by the new condition capturing behaviour.

* `expect_equivalent()`, `expect_reference()`, `expect_is()` and
  `expect_that()` are deprecated.

* Messages are no longer automatically silenced. Either use
  `suppressMessages()` to hide unimportant messages, or
  `expect_messsage()` to catch important messages (#1095).

* `setup()` and `teardown()` are deprecated in favour of test fixtures.
  See `vignette("test-fixtures")` for more details.

* `expect_known_output()`, `expect_known_value()`, `expect_known_hash()`,
  and `expect_equal_to_reference()` are all deprecated in favour of
  `expect_snapshot_output()` and `expect_snapshot_value()`.

* `test_that()` now sets a number of options and env vars to make output as
  reproducible as possible (#1044). Many of these options were previously
  set in various places (in `devtools::test()`, `test_dir()`, `test_file()`,
  or `verify_output()`) but they have now been centralised. You can use in
  your own code, or when debugging tests interactively with
  `local_test_context()`.

* `with_mock()` and `local_mock()` are deprecated; please use the mockr
  or mockery packages instead (#1099).

## Snapshot testing

New family of snapshot expectations (`expect_snapshot()`, `expect_snapshot_output()`, `expect_snapshot_error()`, and `expect_snapshot_value()`) provide "snapshot" tests, where the expected results are stored in separate files in `test/testthat/_snaps`. They're useful whenever it's painful to store expected results directly in the test files.

`expect_snapshot_file()` along with `snapshot_review()` help snapshot
more complex data, with initial support for text files, images, and data frames (#1050).

See `vignette("snapshotting")` for more details.

## Reporters

* `CheckReporter` (used inside R CMD check) now prints out all problems
  (i.e. errors, failures, warnings and skips; and not just the first 10),
  lists skips types, and records problems in machine readable format in
  `tests/testthat-problems.rds` (#1075).

* New `CompactProgressReporter` tweaks the output of `ProgressReporter` for
  use with a single file, as in `devtools::test_file()`. You can pick a
  different default by setting `testthat.default_compact_reporter` to
  the name of a reporter.

* `ProgressReporter` (the default reporter) now keeps the stack traces of
  an errors that happen before the before test, making problems substantially
  easier to track down (#1004). It checks if you've exceeded the maximum number
  of failures (from option `testthat.progress.max_fails`) after each
  expectation, rather than at the end of each file (#967). It also gains
  new random praise options that use emoji, and lists skipped tests by type
  (#1028).

* `StopReporter` adds random praise emoji when a single test passes (#1094).
  It has more refined display of failures, now using the same style
  as `CompactProgressReporter` and `ProgressReporter`.

* `SummaryReporter` now records file start, not just context start. This
  makes it more compatible with modern style which does not use `context()`
  (#1089).

* All reporters now use exactly the same format when reporting the location
  of an expectation.

* Warnings now include a backtrace, making it easier to figure
  out where they came from.

* Catch C++ tests now provide detailed results for each test.
  To upgrade existing code, re-run `testthat::use_catch()` (#1008).

## Fixures

* New `vignette("test-fixtures")` describes test fixtures; i.e. how to
  temporarily and cleanly change global state in order to test parts of
  your code that otherwise would be hard to run (#1042). `setup()` and
  `teardown()` are superseded in favour of test fixtures.

* New `teardown_env()` for use with `withr::defer()`. This allows you to
  run code after all other tests have been run.

## Skips

* New `vignette("skipping")` gives more general information on skipping
  tests, include some basics on testing skipping helpers (#1060).

* `ProgressReporter()` and `CheckReporter()` list the number of skipped tests
  by reason at the end of the reporter. This makes it easier to check that
  you're not skipping the wrong tests, particularly on CI services (#1028).

## Test running

* `test_that()` no longer triggers an error when run outside of tests;
  instead it produces a more informative summary of all failures, errors,
  warnings, and skips that occurred inside the test.

* `test_that()` now errors if `desc` is not a string (#1161).

* `test_file()` now runs helper, setup, and teardown code, and has the
  same arguments as `test_dir()` (#968). Long deprecated `encoding` argument
  has been removed.

* `test_dir()` now defaults `stop_on_failure` to `TRUE` for consistency with
  other `test_` functions. The `wrap` argument has been deprecated; it's not
  clear that it should ever have been exposed.

* New `test_local()` tests a local source package directory. It's equivalent
  to `devtools::test()` but doesn't require devtools and all its dependencies
  to be installed (#1030).

## Minor improvements and bug fixes

* testthat no longer supports tests stored in `inst/tests`. This has been
  deprecated since testthat 0.11.0 (released in 2015). `test_package()`
  (previously used for running tests in R CMD check) will fail silently
  if no tests are found to avoid breaking old packages on CRAN (#1149).

* `capture_output()` and `verify_output()` use a new `testthat_print()`
  generic. This allows you to control the printed representation of your
  object specifically for tests (i.e. if your usual print method shows
  data that varies in a way that you don't care about for tests) (#1056).

* `context_start_file()` is now exported for external reporters (#983, #1082).
  It now only strips first instance of prefix/suffix (#1041, @stufield).

* `expect_error()` no longer encourages you to use `class`. This advice
  one type of fragility at the expense of creating a different type (#1013).

* `expect_known_failure()` has been removed. As far as I can tell it was
  only ever used by testthat, and is rather fragile.

* `expect_true()`, `expect_false()`, and `expect_null()` now use waldo to
  produce more informative failures.

* `verify_output()` no longer always fails if output contains a carriage
  return character ("\r") (#1048). It uses the `pdf()` device instead of
  `png()` soit work on systems without X11 (#1011). And it uses
  `waldo::compare()` to give more informative failures.

(mef)

Updated devel/R-rprojroot to 2.0.2
Added devel/R-waldo version 0.2.3
Added devel/R-diffobj version 0.3.2
Added devel/R-brio version 1.1.0
Added www/R-diffviewer version 0.1.0
Updated sysutils/R-ps to 1.5.0

(mef)

(sysutils/R-ps) Updated 1.3.0 to 1.5.0

# ps 1.5.0

* New function `ps_shared_libs()` to list the loaded shared libraries
  of a process, on Windows.

* New function `ps_shared_lib_users()` to list all processes that
  loaded a certain shared library, on Windows.

* New function `ps_descent()` to query the ancestry of a process.

# ps 1.4.0

* ps is now under the MIT license.

* Process functions now default to the calling R process. So e.g. you can
  write simply `ps_connections()` to list all network connections of the
  current process, instead of `ps_connections(ps_handle())`.

* New `ps_get_nice()` and `ps_set_nice()` functions to get and set the
  priority of a process (#89).

* New `ps_system_memory()` and `ps_system_swap()` functions, to
  return information about system memory and swap usage.

* New `ps_disk_partitions()` and `ps_disk_usage()` functions, they
  return information about file systems, similarly to the `mount` and
  `df` Unix commands.

* New `ps_tty_size()` function to query the size of the terminal.

* Fixed an issue in `CLeanupReporter()` that triggered random failures
  on macOS.

# ps 1.3.4

* `ps_cpu_count()` now reports the correct number on Windows, even if
  the package binary was built on a Windows version with a different
  API (#77).

# ps 1.3.3

* New function `errno()` returns a table of `errno.h` error codes and
  their description.

* ps now compiles again on Solaris.

# ps 1.3.2

* ps now compiles again on unsupported platforms like Solaris.

# ps 1.3.1

* Fixed an installation problem on some Windows versions, where the
  output of `cmd /c ver` looks different (#69).

(mef)

www/R-diffviewer: import R-diffviewer-0.1.0

A HTML widget that shows differences between files (text, images, and
data frames).

(mef)

devel/R-brio: import R-brio-1.1.0

Functions to handle basic input output, these functions always read
and write UTF-8 (8-bit Unicode Transformation Format) files and
provide more explicit control over line endings.

(mef)

devel/R-diffobj: import R-diffobj-0.3.2

Generate a colorized diff of two R objects for an intuitive
visualization of their differences.

(mef)

devel/R-waldo: import R-waldo-0.2.3

Compare complex R objects and reveal the key differences.  Designed
particularly for use in testing packages where being able to quickly
isolate key differences makes understanding test failures much easier.

(mef)

(devel/rprojroot) Updated 1.3.2 to 2.0.2

# rprojroot 2.0.2 (2020-11-15)

## Features
- In `find_root_file()`, if the first path component is already an
  absolute path, the path is returned unchanged without referring to
  the root. This allows using both root-relative and absolute paths in
  `here::here()`. Mixing root-relative and absolute paths in the same
  call returns an error (#59).

- `find_root_file()` propagates `NA` values in path components. Using
  tidyverse recycling rules for path components of length different
  from one (#66).

- `has_file()` and `has_file_pattern()` gain `fixed` argument (#75).
- New `is_drake_project` criterion (#34).
- Add `subdir` argument to `make_fix_file()` (#33, @BarkleyBG).
- Update documentation for version control criteria (#35, @uribo).

## Breaking changes

- `Has_file()` and `has_dir()` now throw an error if the `filepath`
  argument is an absolute path (#74).

- `has_basename()` replaces `has_dirname()` to avoid confusion (#63).

- `as_root_criterion()` and `is_root_criterion()` replace `as.` and
  `is.`, respectively. The latter are soft-deprecated.

- `thisfile()` and related functions are soft-deprecated, now
  available in the whereami package (#43).

## Bug fixes

- The `is_dirname()` criterion no longer considers sibling directories (#44).

## Internal

- Use testthat 3e (#70).
- The backports package is no longer imported (#68).
- Re-license as MIT (#50).
- Move checks to GitHub Actions (#52).

- Availability of suggested packages knitr and rmarkdown, and pandoc,
  is now checked before running the corresponding tests.

(mef)

ham/gnuradio: add 38 to PYTHON_VERSIONS_ACCEPTED

(dbj)

mail/fetchmail: fix build on Darwin with gssapi or kerberos options

Darwin doesn't install include files in ${KRB5BASE}
(They are in the SDK instead)
therefore let fetchmail use krb5-config to determine how to
link against kerberos

(dbj)

cross/mingw-*-bin: fix INSTALLATION_DIRS

(dbj)

cross/mingw-binutils: take upstream fix to avoid BASH_LINENO

https://sourceware.org/bugzilla/show_bug.cgi?id=5652

(dbj)

show-all: explain how to show the values of tricky variables

In most cases, the output of "bmake show-all" is reliable, but in a few
edge cases there may still be surprises.

(rillig)

doc: Updated devel/R-magrittr to 2.0.1

(mef)

(devel/R-magrittr) Updated 1.5 to 2.0.1  make test fails at PDF

# magrittr 2.0.1

* Fixed issue caused by objects with certain names being present in
  the calling environment (#233).

* Fixed regression in `freduce()` with long lists (kcf-jackson/sketch#5).

# magrittr 2.0.0

## Fast and lean implementation of the pipe

The pipe has been rewritten in C with the following goals in mind:

- Minimal performance cost.
- Minimal impact on backtraces.
- No impact on reference counts.

As part of this rewrite we have changed the behaviour of the pipe to
make it closer to the implementation that will likely be included in a
future version of R. The pipe now evaluates piped expressions lazily (#120).
The main consequence of this change is that warnings and errors can
now be handled by trailing pipe calls:

```r
stop("foo") %>% try()
warning("bar") %>% suppressWarnings()
```

## Breaking changes

The pipe rewrite should generally not affect your code. We have
checked magrittr on 2800 CRAN packages and found only a dozen of
failures. The development version of magrittr has been advertised on
social media for a 3 months trial period, and no major issues were
reported. However, there are some corner cases that might require
updating your code. Below is a report of the backward
incompatibilities we found in real code to help you transition, should
you find an issue in your code.

### Behaviour of `return()` in a pipeline

In previous versions of magrittr, the behaviour of `return()` within
pipe expressions was undefined. Should it return from the current pipe
expression, from the whole pipeline, or from the enclosing function?
The behaviour that makes the most sense is to return from the
enclosing function. However, we can't make this work easily with the
new implementation, and so calling `return()` is now an error.

```r
my_function <- function(x) {
  x %>% {
    if (.) return("true")
    "false"
  }
}

my_function(TRUE)
#> Error: no function to return from, jumping to top level
```

In magrittr 1.5, `return()` used to return from the current pipe
expression. You can rewrite this to the equivalent:

```r
my_function <- function(x) {
  x %>% {
    if (.) {
      "true"
    } else {
      "false"
    }
  }
}

my_function(TRUE)
#> [1] "true"
```

For backward-compatibility we have special-cased trailing `return()`
calls as this is a common occurrence in packages:

```r
1 %>% identity() %>% return()
```

Note however that this only returns from the pipeline, not the
enclosing function (which is the historical behaviour):

```r
my_function <- function() {
  "value" %>% identity() %>% return()
  "wrong value"
}

my_function()
#> [1] "wrong value"
```

It is generally best to avoid using `return()` in a pipeline, even if
trailing.

### Failures caused by laziness

With the new lazy model for the evaluation of pipe expressions,
earlier parts of a pipeline are not yet evaluated when the last pipe
expression is called. They only get evaluated when the last function
actually uses the piped arguments:

```r
ignore <- function(x) "return value"
stop("never called") %>% ignore()
#> [1] "return value"
```

This should generally not cause problems. However we found some
functions with special behaviour, written under the assumption that
earlier parts of the pipeline were already evaluated and had already
produced side effects. This is generally incorrect behaviour because
that means that these functions do not work properly when called
with the nested form, e.g. `f(g(1))` instead of `1 %>% g() %>% f()`.

The solution to fix this is to call `force()` on the inputs to force
evaluation, and only then check for side effects:

```r
my_function <- function(data) {
  force(data)
  peek_side_effect()
}
```

Another issue caused by laziness is that if any function in a pipeline
returns invisibly, than the whole pipeline returns invisibly as well.

```r
1 %>% identity() %>% invisible()
1 %>% invisible() %>% identity()
1 %>% identity() %>% invisible() %>% identity()
```

This is consistent with the equivalent nested code. This behaviour can
be worked around in two ways. You can force visibility by wrapping the
pipeline in parentheses:

```r
my_function <- function(x) {
  (x %>% invisible() %>% identity())
}
```

Or by assigning the result to a variable and return it:

```r
my_function <- function(x) {
  out <- x %>% invisible() %>% identity()
  out
}
```

### Incorrect call stack introspection

The magrittr expressions are no longer evaluated in frames that can be
inspected by `sys.frames()` or `sys.parent()`. Using these functions
for implementing actual functionality (as opposed as debugging tools)
is likely to produce bugs. Instead, you should generally use
`parent.frame()` which works even when R code is called from
non-inspectable frames. This happens with e.g. `do.call()` and the new
C implementation of magrittr.

### Incorrect assumptions about magrittr internals

Some packages were depending on how magrittr was internally
structured. Robust code should only use the documented and exported
API of other packages.

## Bug fixes

* Can now use the placeholder `.` with the splicing operator `!!!`
  from rlang (#191).

* Piped arguments are now persistent. They can be evaluated after the
  pipeline has returned, which fixes subtle issues with function
  factories (#159, #195).

(mef)

doc: Updated devel/R-clipr to 0.7.1

(mef)

(devel/R-clipr) Updated 0.7.0 to 0.7.1

## clipr 0.7.1
- Call xsel with the `--output` flag, which prevents RStudio from
  hanging when calling clipr functions on a system running certain
  Linux window managers. Thank you to @cgillespie and @kevinushey for
  identifying the bug and the solution, and to @hannahcgunderman for
  help in testing.

(mef)

doc: Updated devel/R-cliapp to 0.1.1

(mef)

(devel/R-cliapp) Updated 0.1.0 to 0.1.1

# 0.1.1
* cliapp is superseded, and we focus on the cli package now.

* Fix a potential error when text is outputted without an
  enclosing container.

(mef)

doc: Updated devel/R-callr to 3.5.1

(mef)

(devel/R-callr) Updated 3.4.4 to 3.5.1 (make test fails at PDF creation)

# callr 3.5.1

* `callr::r_session` now handles large messages from the subprocess
  well (#168).

# callr 3.5.0

* callr can now pass the environment of the function to the subprocess,
  optionally. This makes it easier to call an internal function of a
  package in a subprocess. See the `package` argument of `r()`, `r_bg()`,
  `r_session$run()`, etc. (#147).

(mef)

doc: Updated sysutils/R-processx to 3.4.5

(mef)

(sysutils/R-processx) Updated 3.4.1 to 3.4.5

# processx 3.4.5

* New options in `pty_options` to set the initial size of the pseudo
  terminal.

* Reading the standard output or error now does not crash occasionally
  when a `\n` character is at the beginning of the input buffer (#281).

# processx 3.4.4

* processx now works correctly for non-ASCII commands and arguments passed
  in the native encoding, on Windows (#261, #262, #263, #264).

* Providing multiple environment variables now works on windows (#267).

# processx 3.4.3

* The supervisor (activated with `supervise = TRUE`) does not crash
  on the Windows Subsystem on Linux (WSL) now (#222).

* Fix ABI compatibility for pre and post R 4.0.1 versions. Now CRAN
  builds (with R 4.0.2 and later 4.0.x) work well on R 4.0.0.

* Now processx can run commands on UNC paths specified with
  forward slashes: `//hostname/...` UNC paths with the usual
  back-slashes were always fine (#249).

* The `$as_ps_handle()` method works now better; previously it
  sometimes created an invalid `ps::ps_handle` object, if the system
  clock has changed (#258).

# processx 3.4.2

* `run()` now does a better job with displaying the spinner on terminals
  that buffer the output (#223).

* Error messages are now fully printed after an error. In non-interactive
  sessions, the stack trace is printed as well.

* Further improved error messages. Errors from C code now include the
  name of the C function, and errors that belong to a process include the
  system command (#197).

* processx does not crash now if the process receives a SIGPIPE signal when
  trying to write to a pipe, of which the other end has already exited.

* processx now to works better with fork clusters from the parallel
  package. See 'Mixing processx and the parallel base R package' in the
  README file (#236).

* processx now does no block SIGCHLD by default in the subprocess,
  blocking potentially causes zombie sub-subprocesses (#240).

* The `process$wait()` method now does not leak file descriptors on
  Unix when interrupted (#141).

(mef)

doc/TODO: add some

+ ImageMagick-7.0.10.48, autoconf-2.70, enchant2-2.2.14,
  gstreamer1-1.18.2, mono6-6.12.0.107, p11-kit-0.23.22, php-8.0,
  poppler-20.12.1, py-chardet-4.0.0, py-hypothesis-5.43.3,
  py-packaging-20.8, qt6-6.0, readline-8.1, spdlog-1.8.2,
  xscreensaver-5.45.

(wiz)

platform/Linux: always prefer native pthread/libdl

(nia)

doc: Updated devel/golangci-lint to 1.33.0

(bsiegert)

New package, golangci-lint.

golangci-lint is a fast runner for Go linters. It runs linters in parallel,
uses caching, supports yaml config, has integrations with all major IDE and has
dozens of linters included.

(bsiegert)

doc: Added net/hdl-dump version 20200727

(nia)

Add net/hdl-dump.

Contributed by embr@liclac.eu in a private email, thx!

hdl_dump is a tool for installing games and homebrew software in HDLoader
format onto a PlayStation 2's hard drive, either over the network or by
directly attaching it to your machine.

(nia)

doc: Added converters/cue2pops version 20180104

(nia)

Add converters/cue2pops.

Contributed in a private email by embr@liclac.eu, thx!

cue2pops is a tool for converting PlayStation 1 backups in .CUE/.BIN format to
.VCD, the format supported by the PlayStation 2's POPS emulator.

The original cue2pops is Windows-only, this is the cue2pops-linux fork.

(nia)

binutils: remove apparently unneeded patch for libiberty.

Built a package with and without the patch on NetBSD and couldn't notice
any difference. Package also builds without issue on Linux and OpenBSD.

(fcambus)

x11/gtksourceview2: remove configure option --disable-build-tests

It is no longer known.  The ChangeLog files don't contain an entry about
its removal.

(rillig)

(security/ocaml-ssl) Add devel/ocaml-dune-configurator as buildlink3.mk

(mef)

(devel/ocaml-lwt) Add devel/ocaml-dune-configurator as buildlink3.mk

(mef)

(devel/ocaml-ppxlib) Add missing devel/ocaml-sexplib0 as buildlink3.mk

(mef)

doc: Updated pkgtools/pkgin to 20.12.0

(jperkin)

pkgin: Update to 20.12.0.

## Version 20.12.0 (2020-12-13)

* Return correct MACHINE_ARCH when using $arch in repositories.conf.

(jperkin)

doc: Updated security/py-solo to 0.0.26

(riastradh)

security/py-solo: Import solo-python 0.0.26

Tool and Python library for managing SoloKeys

(riastradh)

security/py-fido2: Improve NetBSD patch.

- Simplify byte-munging with ctypes.
- Expose the product and vendor strings, not just numbers.
- Expose the serial number too.

(riastradh)

doc: Updated devel/p5-Test-BDD-Cucumber to 0.74

(schmonz)

Update to 0.74. From the changelog:

- Fixed: failure exit code from 'pherkin' does not work
- Synchronized translations with upstream i18n data

(schmonz)

doc: Updated geography/qgis to 3.10.12

(gdt)

qgis: Update to 3.10.12

This is a micro release; upstream changes are minor improvements and
bugfixes.

Packaging changes is one new translation file.

(gdt)

note update of bacula and friends to 9.6.7

(jnemeth)

bacula: update to 9.6.7

====== ReleaseNotes =====
03Dec20
- Restore custom permission of symlink on FreeBSD and MacOS
- Fix #2582 bextract is broken for sparse gzip and compressed streams
- Fix org#2567 device capabilities overwritten
- baculum: Update script version
- Fix org#2573 About Syntax error in granting privileges script with
MySQL if --with-db-password parameter is used
- Fix org#2471 About deleted files are listed as being present in an
accurate backup by various sample queries
- Fix org#2571 About errors in es_AR.po file
- Fix org#2568 About compilation issue on gcc10
- Fix org#2584 About inconsitancies in the make_mysql_tables script
- baculum: Fix English text noticed by Peter McDonald
- baculum: Update Russian translations
- baculum: Update Portuguese translations
- baculum: Implement graphical status storage
- baculum: Add gauge.js library
- baculum: Add json output option to show storages and show single storage
  endpoints
- baculum: Add path field to restore wizard to narrow down search file
results to specific path - idea proposed by Wanderlei Huttel
- baculum: Add path parameter to job files API endpoint
- baculum: Fix #2565 status icon overlaps action buttons in API wizard
- baculum: Add Sergey Zhidkov to AUTHORS
- baculum: Add Russian translations
- baculum: Fix access to job resources if no job assigned to user
- baculum: Update Portuguese translations
- baculum: Ajax queue improvement in framework
- baculum: Fix renaming config resources
- baculum: Add graphs to job view page
- baculum: Fix using offset in job file list query with MySQL catalog
database
- baculum: Show more detailed job file list - idea proposed by
Wanderlei Huttel
- baculum: Rework job file list API endpoint
- baculum: Add searching jobs by filename in restore wizard - idea
proposed by Wanderlei Huttel
- baculum: Add job files API endpoint
- Add code to retry a MySQL query after a deadlock
- baculum: Update Portuguese translations
- baculum: Add default days and limit values to status schedules API
endpoint
- baculum: Fix displaying multitextbox and multicombobox directive controls
- baculum: Fix date filter on status schedule page
- baculum: Fix #2570 fileset excludes settings with PHP 7.4
- baculum: Rework job file list API endpoint
- baculum: Add searching jobs by filename in restore wizard - idea
proposed by Wanderlei Huttel
- baculum: Add job files API endpoint
- Add code to retry a MySQL query after a deadlock
- baculum: Update Portuguese translations
- baculum: Add default days and limit values to status schedules API
endpoint
- baculum: Fix displaying multitextbox and multicombobox directive controls
- baculum: Fix date filter on status schedule page
- baculum: Fix #2570 fileset excludes settings with PHP 7.4
- baculum: New features and improvements to multi-user interface and
restricted access

(jnemeth)

doc: Updated net/gallery-dl to 1.16.0

(leot)