Log message:
devel/py-dialog2: removed; use py-dialog instead

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:
*: Convert broken sourceforge HOMEPAGEs back to http

Log message:
py-dialog{2}: updated to 3.5.1

Main changes in version 3.5.1

The main changes in version 3.5.1 are:

The default used when the PATH environment variable is unset is now \ 
"/bin:/usr/bin" instead of ":/bin:/usr/bin". This is \ 
relevant when the dialog argument of the Dialog constructor contains no slash \ 
(/), which is the case by default. The benefit of this change is that in such a \ 
situation (PATH unset and dialog argument containing no slash), the dialog-like \ 
program will not be searched in the current directory anymore (unless of course \ 
the current directory is /bin or /usr/bin). This is a much safer behavior; \ 
fortunately, the risky behavior only ever existed on bogus setups where the PATH \ 
environment variable is unset.

Note that in this respect, we have been following what the GNU C Library (glibc) \ 
does for its execvp() function—the corresponding change in glibc happened in \ 
version 2.24, released in 2016.

When a Dialog instance is created, it now immediately stores the result of \ 
calling os.path.realpath() on the specified executable (which is searched using \ 
the PATH if the dialog argument passed to the constructor contains no \ 
slash—cf. documentation of the Dialog constructor). This way, a \ 
pythondialog-based program can change its current directory after creating a \ 
Dialog instance without fearing that this might cause subsequent Dialog method \ 
calls to fail or to invoke an executable from a different directory \ 
(additionally, os.path.realpath() resolves symbolic links).

The Python 2 backport of pythondialog has been released for this version and \ 
should be on par with pythondialog 3.5.1 (this is why version 3.5.0 of the \ 
backport has been skipped). The packaging of the backport has been switched from \ 
distutils to setuptools too, just as was done in pythondialog 3.5.0 (see below). \ 
As a consequence, it is now available in wheel format. However, as said above, \ 
Python 2 is deprecated and the Python 2 backport of pythondialog is not \ 
supported anymore. Don't expect any further updates to it.

Main changes in version 3.5.0

The main change in version 3.5.0 is:

pythondialog's packaging has been switched from distutils to setuptools (this is \ 
the modern way, see the Python Packaging User Guide). Thanks to this change, \ 
pythondialog is now available in wheel format. The normal installation method \ 
using pip didn't change (see the INSTALL file for details).

The Python 2 backport of pythondialog has not been released for this version \ 
(version 3.5.1 will be the last one).

Log message:
all: migrate several HOMEPAGEs to https

pkglint --only "https instead of http" -r -F

With manual adjustments afterwards since pkglint 19.4.4 fixed a few
indentations in unrelated lines.

This mainly affects projects hosted at SourceForce, as well as
freedesktop.org, CTAN and GNU.

Log message:
devel/py-*: align variable assignments

pkglint -Wall -F --only aligned --only indent -r

No manual corrections.

Log message:
Changed PYTHON_VERSIONS_INCOMPATIBLE to PYTHON_VERSIONS_ACCEPTED; needed for \ 
future Python 3.8