Log message:
py-test-benchmark: updated to 4.0.0

4.0.0 (2022-10-26)
------------------
* Dropped support for legacy Pythons (2.7, 3.6 or older).
* Switched CI to GitHub Actions.
* Removed dependency on the ``py`` library (that was not properly specified as a \ 
dependency anyway).
* Fix skipping test in `test_utils.py` if appropriate VCS not available. Also \ 
fix typo.
* Added support for pytest 7.2.0 by using ``pytest.hookimpl`` and \ 
``pytest.hookspec`` to configure hooks.
* Now no save is attempted if ``--benchmark-disable`` is used.

Log message:
python: egg.mk: add USE_PKG_RESOURCES flag

This flag should be set for packages that import pkg_resources
and thus need setuptools after the build step.

Set this flag for packages that need it and bump PKGREVISION.

Log message:
*: bump PKGREVISION for egg.mk users

They now have a tool dependency on py-setuptools instead of a DEPENDS

Log message:
archivers: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

Could not be committed due to merge conflict:
devel/py-traitlets/distinfo

The following distfiles were unfetchable (note: some may be only fetched
conditionally):

./devel/pvs/distinfo pvs-3.2-solaris.tgz
./devel/eclipse/distinfo eclipse-sourceBuild-srcIncluded-3.0.1.zip

Log message:
devel: Remove SHA1 hashes for distfiles

Log message:
py-test-benchmark: updated to 3.4.1

3.4.1 (2021-04-17)
------------------
* Republished with updated changelog.

  I intended to publish a ``3.3.0`` release but I messed it up because \ 
bumpversion doesn't work well with pre-commit
  apparently... thus ``3.4.0`` was set in by accident.

3.4.0 (2021-04-17)
------------------
* Disable progress indication unless ``--benchmark-verbose`` is used.
* Added Python 3.9, dropped Python 3.5.
* Changed the "cpu" data in the json output to include everything that \ 
cpuinfo outputs, for better or worse as cpuinfo 6.0 changed some
  fields. Users should now ensure they are an adequate cpuinfo package installed.
  **MAY BE BACKWARDS INCOMPATIBLE**
* Changed behavior of ``--benchmark-skip`` and ``--benchmark-only`` to apply \ 
early in the collection phase.
  This means skipped tests won't make pytest run fixtures for said tests \ 
unnecessarily, but unfortunately this also means
  the skipping behavior will be applied to any tests that requires a \ 
"benchmark" fixture, regardless if it would come from pytest-benchmark
  or not.
  **MAY BE BACKWARDS INCOMPATIBLE**
* Added ``--benchmark-quiet`` - option to disable reporting and other \ 
information output.
* Squelched unnecessary warning when ``--benchmark-disable`` and save options \ 
are used.
* ``PerformanceRegression`` exception no longer inherits ``pytest.UsageError`` \ 
(apparently a *final* class).

Log message:
py-test-benchmark: Unbreak bulk builds.

Log message:
devel/py-test-benchmark: import py-test-benchmark-3.2.3

A pytest fixture for benchmarking code. It will group the tests
into rounds that are calibrated to the chosen timer.