openSUSE has issued an advisory on April 19:
The issue is fixed upstream in 3.1.2.
Mageia 7 and Mageia 8 are also affected.
Fixed upstream in 3.1.2Whiteboard:
neoclust has already done the update, so assigning this to you.
Removing Mageia 7 from whiteboard due to EOL:
MGA8TOO, MGA7TOO =>
cauldron is with version 3.2
version 3.2 pushed in mga8:
Fixed upstream in 3.1.2 =>
Sorry, the following pakage cannot be selected:
- python3-django-registration-3.2-1.mga8.noarch (beause of unfulfilled python3.8dist(django)[< 3])
Confirmed that here. Adding feedback marker.
It seems that rpmbuild has difficulty to manage versionning requires from python:
urpmq --requires --media Testing python3-django-registration
where in Python setup.py says:
Actually, django is in 3.2
Thus, I suggest to patch the setup.py in this way:
Yes, rpmbuild doesn't parse those things correctly. We have patches for that in a lot of packages.
A new build:
MGA8-64 Plasma on Lenovo B50 in Dutch
No installation issues.
No previous updates and both
# urpmq --whatrequires python3-django-registration
# urpmq --whatrequires-recursive python3-django-registration
return nothing, so OK on clean install as with other developer's stuff.
An update for this issue has been pushed to the Mageia Updates repository.