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-yapf: updated to 0.31.0

0.31.0:
Added
- Renamed 'master' brannch to 'main'.
- Add 'BLANK_LINES_BETWEEN_TOP_LEVEL_IMPORTS_AND_VARIABLES' to support setting
  a custom number of blank lines between top-level imports and variable
  definitions.
- Ignore end of line `# copybara:` directives when checking line length.
- Look at the 'pyproject.toml' file to see if it contains style information for
  YAPF.
Changed
- Do not scan exlcuded directories. Prior versions would scan an exluded
  folder then exclude its contents on a file by file basis. Preventing the
  folder being scanned is faster.
Fixed
- Exclude directories on Windows.

Log message:
py-yapf: Sort PLIST

Log message:
py-yapf: add "-" to executable name before version, requested by adam

Ride import.

Log message:
devel/py-yapf: import py-yapf-0.30.0

Packaged for wip by nils@, nikita@, hauke@, rillig@

YAPF - Yet Another Python Formatter - is a python formatting
tool based based off of 'clang-format'.
In essence, the algorithm takes the code and reformats it to
the best formatting that conforms to the style guide, even if
the original code didn't violate the style guide.
The idea is also similar to the 'gofmt' tool for the Go
programming language: end all holy wars about formatting -
if the whole code base of a project is simply piped through
YAPF whenever modifications are made, the style remains consistent
throughout the project and there's no point arguing about style
in every code review.