Log message:
py-django-registration: updated to 5.1.0

Version 5.1.0

* Adopted "DjangoVer" versioning.

* Supported Django versions are now 4.2, 5.0, and 5.1.

* Supported Python versions are now 3.9, 3.10, 3.11, 3.12, and 3.13.

* The base :class:`~django_registration.forms.RegistrationForm` has been
  completely rewritten, though in a backwards-compatible way. It is no longer a
  subclass of Django's ``UserCreationForm``, which means it is far more
  flexible with respect to custom user models (and for many cases, no longer
  requires a custom form subclass just to handle a custom user model).

* :class:`~django_registration.views.ActivationView` has also been rewritten,
  and with it parts of :ref:`the built-in activation-based workflow
  <activation-workflow>`. The primary change here is that ``ActivationView``
  now only attempts to activate the user account on an HTTP ``POST`` request
  (previously it would do so on ``GET``, which was increasingly unsafe due to
  email clients auto-following links). This is backwards-incompatible: the
  activation view now displays a form on ``GET``, and the templates involved
  have changed. See :ref:`the template documentation <default-templates>` for
  details of the required templates.

Log message:
py-*: remove unused tool dependency

py-setuptools includes the py-wheel functionality nowadays

Log message:
py-django-registration: updated to 3.4

3.4
Unknown changes

Log message:
*: switch django users to py-django3

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

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

Log message:
www: Replace RMD160 checksums with BLAKE2s checksums

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

Not committed (merge conflicts):
www/nghttp2/distinfo

Unfetchable distfiles (almost certainly fetched conditionally...):
./www/nginx-devel/distinfo array-var-nginx-module-0.05.tar.gz
./www/nginx-devel/distinfo echo-nginx-module-0.62.tar.gz
./www/nginx-devel/distinfo encrypted-session-nginx-module-0.08.tar.gz
./www/nginx-devel/distinfo form-input-nginx-module-0.12.tar.gz
./www/nginx-devel/distinfo headers-more-nginx-module-0.33.tar.gz
./www/nginx-devel/distinfo lua-nginx-module-0.10.19.tar.gz
./www/nginx-devel/distinfo naxsi-1.3.tar.gz
./www/nginx-devel/distinfo nginx-dav-ext-module-3.0.0.tar.gz
./www/nginx-devel/distinfo nginx-rtmp-module-1.2.2.tar.gz
./www/nginx-devel/distinfo nginx_http_push_module-1.2.10.tar.gz
./www/nginx-devel/distinfo ngx_cache_purge-2.5.1.tar.gz
./www/nginx-devel/distinfo ngx_devel_kit-0.3.1.tar.gz
./www/nginx-devel/distinfo ngx_http_geoip2_module-3.3.tar.gz
./www/nginx-devel/distinfo njs-0.5.0.tar.gz
./www/nginx-devel/distinfo set-misc-nginx-module-0.32.tar.gz
./www/nginx/distinfo array-var-nginx-module-0.05.tar.gz
./www/nginx/distinfo echo-nginx-module-0.62.tar.gz
./www/nginx/distinfo encrypted-session-nginx-module-0.08.tar.gz
./www/nginx/distinfo form-input-nginx-module-0.12.tar.gz
./www/nginx/distinfo headers-more-nginx-module-0.33.tar.gz
./www/nginx/distinfo lua-nginx-module-0.10.19.tar.gz
./www/nginx/distinfo naxsi-1.3.tar.gz
./www/nginx/distinfo nginx-dav-ext-module-3.0.0.tar.gz
./www/nginx/distinfo nginx-rtmp-module-1.2.2.tar.gz
./www/nginx/distinfo nginx_http_push_module-1.2.10.tar.gz
./www/nginx/distinfo ngx_cache_purge-2.5.1.tar.gz
./www/nginx/distinfo ngx_devel_kit-0.3.1.tar.gz
./www/nginx/distinfo ngx_http_geoip2_module-3.3.tar.gz
./www/nginx/distinfo njs-0.5.0.tar.gz
./www/nginx/distinfo set-misc-nginx-module-0.32.tar.gz

Log message:
www: Remove SHA1 hashes for distfiles

Log message:
py-django-registration: typo in DESCR

Log message:
py-django-registration: updated to 2.4.1

2.4.1:
Bug fixes.

Log message:
py-django-registration: updated to 2.3

In django-registration 2.3, the new validators \ 
:func:`~registration.validators.validate_confusables` and \ 
:func:`~registration.validators.validate_confusables_email` were added, and are \ 
applied by default to the username field and email field, respectively, of \ 
registration forms. This may cause some usernames which previously were accepted \ 
to no longer be accepted, but like the reserved-name validator this change was \ 
made because its security benefits significantly outweigh the edge cases in \ 
which it might disallow an otherwise-acceptable username or email address. If \ 
for some reason you need to allow registration with usernames or email addresses \ 
containing potentially dangerous use of Unicode, you can subclass the \ 
registration form and remove these validators, though doing so is not \ 
recommended.