Debian Patches
Status for django-mailman3/1.3.15-5
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-Fix-timezone-that-are-deprecated.patch | Fix timezone that are deprecated | Pierre-Elliott Bécue <peb@debian.org> | yes | 2023-11-13 | ||
| 0002-Fix-Remove-sociallogin.account-from-the-debug-print.patch | Fix: Remove sociallogin.account from the debug print. Since SocialLogin.account isn't a mandatory field, we can't make and assumption that it was filled in when it was created. Instead of checking everytie if the attribute exists, removing it form the debug print to restore compat with newer versions of django-allauth. |
Pierre-Elliott Bécue <peb@debian.org> | yes | 2024-10-20 | ||
| git_socialaccount_only.patch | commit 6f2bb068b2f0f60a25d87527b08b7cc074572c6f Expose SOCIALACCOUNT_ONLY in template context allauth 65+ introduces SOCIALACCOUNT_ONLY as a first-class setting. When True, allauth does not register the account_signup URL, so any {% url 'account_signup' %} in templates raises NoReverseMatch. Postorius and HyperKitty guard those links with {% if not SOCIALACCOUNT_ONLY %}, but SOCIALACCOUNT_ONLY is only available in allauth's own views — not in the broader template context. Inject it here with a False default so the guard works correctly on all pages regardless of whether allauth's context processors are active. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> diff --git a/django_mailman3/context_processors.py b/django_mailman3/context_processors.py index 471cb74..9c666a9 100644 |
Jordi Mallach <jordi@mallach.net> | no | 2026-05-08 | ||
| git_more_socialaccount_only_guards.patch | commit 87d0505d4bfc0ecab2aba7ba532be5f2c7645409 Guard account_email/change_password/reset_password links when SOCIALACCOUNT_ONLY=True allauth 65+ excludes a whole family of account_* URLs from its URL registry when SOCIALACCOUNT_ONLY=True, not just account_signup: account_email, account_change_password, account_reset_password, account_set_password, etc. are all omitted too. The previous fix (6f2bb068) only guarded account_signup links, mirroring Postorius and HyperKitty. It missed django-mailman3's own templates: * profile/base.html and profile/profile.html link to account_email and account_change_password unconditionally, so the user profile page raises NoReverseMatch on every load. * account/login.html links to account_reset_password unconditionally, which is worse since the login page is always reachable regardless of SOCIALACCOUNT_ONLY. Wrap all three in {% if not SOCIALACCOUNT_ONLY %}, same pattern as the existing account_signup guards. diff --git a/django_mailman3/templates/account/login.html b/django_mailman3/templates/account/login.html index d73d3d2..c7171ef 100644 |
Jordi Mallach <jordi@mallach.net> | yes | 2026-08-05 |