On 1/4/23 13:54, Dan Caballero wrote:

I'm attempting this upgrade in my test environment which is a Docker container with Python 3.9.10 virtual environment. I was able to upgrade all the Python requirements but when I run mailman-web migrate I get an error. It seems related to the mailman-web package. See output below.

"(mailmanve) mailman@1d0e3a230c94:/var/www/mailman-www$ mailman-web migrate Traceback (most recent call last): File "/opt/mailmanve/bin/mailman-web", line 33, in <module> sys.exit(load_entry_point('mailman-web==0.0.6', 'console_scripts', 'mailman-web')()) File "/opt/mailmanve/lib/python3.9/site-packages/mailman_web/manage.py", line 37, in main execute_from_command_line(sys.argv) File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line utility.execute() File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/__init__.py", line 440, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/base.py", line 402, in run_from_argv self.execute(*args, **cmd_options) File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/base.py", line 448, in execute output = self.handle(*args, **options) File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/base.py", line 96, in wrapped res = handle_func(*args, **kwargs) File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/commands/migrate.py", line 97, in handle self.check(databases=[database]) File "/opt/mailmanve/lib/python3.9/site-packages/django/core/management/base.py", line 475, in check all_issues = checks.run_checks( File "/opt/mailmanve/lib/python3.9/site-packages/django/core/checks/registry.py", line 88, in run_checks new_errors = check(app_configs=app_configs, databases=databases) File "/opt/mailmanve/lib/python3.9/site-packages/django/core/checks/urls.py", line 14, in check_url_config return check_resolver(resolver) File "/opt/mailmanve/lib/python3.9/site-packages/django/core/checks/urls.py", line 24, in check_resolver return check_method() File "/opt/mailmanve/lib/python3.9/site-packages/django/urls/resolvers.py", line 494, in check for pattern in self.url_patterns: File "/opt/mailmanve/lib/python3.9/site-packages/django/utils/functional.py", line 57, in __get__ res = instance.__dict__[self.name] = self.func(instance) File "/opt/mailmanve/lib/python3.9/site-packages/django/urls/resolvers.py", line 715, in url_patterns patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module) File "/opt/mailmanve/lib/python3.9/site-packages/django/utils/functional.py", line 57, in __get__ res = instance.__dict__[self.name] = self.func(instance) File "/opt/mailmanve/lib/python3.9/site-packages/django/urls/resolvers.py", line 708, in urlconf_module return import_module(self.urlconf_name) File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1030, in _gcd_import File "<frozen importlib._bootstrap>", line 1007, in _find_and_load File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 680, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 850, in exec_module File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed File "/var/www/mailman-www/urls.py", line 20, in <module> from django.conf.urls import include, url ImportError: cannot import name 'url' from 'django.conf.urls' (/opt/mailmanve/lib/python3.9/site-packages/django/conf/urls/__init__.py)"

In Django 3.1 django.conf.urls.url was a deprecated alias to django.urls.re_path and in Django 4.0 it was removed. See, e.g. https://docs.djangoproject.com/en/3.2/ref/urls/ and https://docs.djangoproject.com/en/4.0/ref/urls/.

However, the above Traceback doesn't identify which module contains the

from django.conf.urls import include, url

import. If I look through our sources, I only find this import in mailman-suite/mailman-suite_project/urls.py as an example.

You need to look at your urls.py files. Try something like

grep -r 'from django.conf.urls import include, url' /opt/mailmanve/lib/python3.9/site-packages/

to find which module contains that import.

-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Thanks Mark. The migration completes after I updated the curls.py file.

I do see some warnings...

"WARNINGS: django_mailman3.MailDomain: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. django_mailman3.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the DjangoMailman3Config.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Attachment: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Email: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Favorite: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.LastView: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.MailingList: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Profile: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tag: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Tagging: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Thread: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.ThreadCategory: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. hyperkitty.Vote: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the HyperKittyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. postorius.EmailTemplate: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the PostoriusConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'."

Dears,

I like to know and discuss ideas to get the update process more stable!

Today I updated core and web of mailman3 and ran into all the issues you can have:

• Dependencies are not updated properly
• In case you use "--force-reinstall" Django gets also updated in web and you need to update the urls.py file accordingly
• Enhancement of settings file required (DEFAULT_AUTO_FIELD = ...)

Finally I got it working, but there is always the fear for breaking something on update.

I know it is open source and no one gets paid for the work. But I think there is space for improvement here.

Kind regards Torge

Am 04.01.23 um 10:59 schrieb Abhilash Raj:

Hello Everyone,

Happy new year!

I am pleased to announce several new releases for GNU Mailman project.

1. Mailman Core 3.3.8 1
2. Postorius 1.3.8 2
3. Hyperkitty 1.3.7 3
4. Mailmanclient 3.3.5 4
5. Django-mailman3 1.3.9 5
6. Mailman-hyperkitty 1.2.1 6

All the releases are published to PyPI and you can find links to all the PyPI projects:

   https://docs.mailman3.org/en/latest/

A full list of change logs are available below:

Finally, the minimum Python version required is 3.7, and all the components now support Python 3.7 to 3.11.

Thanks to all the contributors for making this release possible!

If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available here: https://docs.mailman3.org/en/latest/

Installation documentation is available at

    https://docs.mailman3.org/en/latest/install/install.html

and if you are upgrading an existing virtualenv install you can refer

    https://docs.mailman3.org/en/latest/upgrade-3.2.html

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...

This message sent to torgeriedel@gmx.de

On 2/12/23 06:16, Torge Riedel wrote:

Today I updated core and web of mailman3 and ran into all the issues you can have:

• Dependencies are not updated properly

This depends on your pip version. With recent pip you need to specify --upgrade-strategy eager along with --upgrade to upgrade dependencies. This is a bit less aggressive than --force-reinstall.

-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

I finally got around to doing this upgrade. I followed the instructions at:

https://docs.mailman3.org/en/latest/upgrade-3.2.html

Everything seemed to go fine but, mailman3 failed to start because “_BindParamClause” could not be found in sqlalchemy.sql.expression. It looks like alembic-1.6.2 is not completely compatible with SQLAlchemy-2.0.6. I fixed the problem by hacking sqla_compat.py in alembic-1.6.2, but should Mailman start requiring a newer version of alembic?

On Jan 4, 2023, at 4:59 AM, Abhilash Raj maxking@asynchronous.in wrote:

Hello Everyone,

Happy new year!

I am pleased to announce several new releases for GNU Mailman project.

1. Mailman Core 3.3.8 1
2. Postorius 1.3.8 2
3. Hyperkitty 1.3.7 3
4. Mailmanclient 3.3.5 4
5. Django-mailman3 1.3.9 5
6. Mailman-hyperkitty 1.2.1 6

All the releases are published to PyPI and you can find links to all the PyPI projects:

https://docs.mailman3.org/en/latest/

A full list of change logs are available below:

Finally, the minimum Python version required is 3.7, and all the components now support Python 3.7 to 3.11.

Thanks to all the contributors for making this release possible!

If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available here: https://docs.mailman3.org/en/latest/

Installation documentation is available at

https://docs.mailman3.org/en/latest/install/install.html

and if you are upgrading an existing virtualenv install you can refer

https://docs.mailman3.org/en/latest/upgrade-3.2.html

-- thanks, Abhilash Raj (maxking)

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...

This message sent to mm3@steele.com

Mailman's content filtering has removed the following MIME parts from this message.

Content-Type: image/vnd.microsoft.icon Name: favicon.ico

Replaced multipart/alternative part with first alternative.