On 11/22/20 1:22 AM, Torge Riedel wrote:
I like to ask what to do with other packages when upgrading mailman. I noted, that after upgrading mailman, all requirements are fulfilled, but a lot updates are available:
(venv) mailman@basis2:~/core$ pip3 list --outdated Package Version Latest Type
aiosmtpd 1.2 1.2.2 sdist alembic 1.4.2 1.4.3 wheel atpublic 1.0 2.1.1 sdist dkimpy 1.0.4 1.0.5 sdist dnspython 1.16.0 2.0.0 wheel flufl.i18n 2.0.2 3.1.3 sdist flufl.lock 3.2 5.0.3 sdist idna 2.9 2.10 wheel importlib-metadata 1.6.1 2.0.0 wheel importlib-resources 2.0.1 3.3.0 wheel passlib 1.7.2 1.7.4 wheel PyMySQL 0.9.3 0.10.1 wheel requests 2.23.0 2.25.0 wheel SQLAlchemy 1.3.17 1.3.20 wheel urllib3 1.25.9 1.26.2 wheel zipp 3.1.0 3.4.0 wheel zope.component 4.6.1 4.6.2 wheel zope.event 4.4 4.5.0 wheel zope.interface 5.1.0 5.2.0 wheel
Should I update them (regularly) or may I break something in mailman?
In some cases and at some times, Mailman itself specifies a version <= something for a dependency. There have been issues where an upgraded dependency is not compatible with current Mailman.
You can look at the install_requires section of setup.py to see if there are any specific version requirements, but this is not fool proof. For example, flufl.lock 5.0 broke Mailman core (See https://gitlab.com/mailman/mailman/-/issues/754). This was fixed in core version 3.3.2.
Thus, If Mailman is working with the set of installed dependencies that you have and all of them satisfy >= requirements in setup.py, it's probably safest to leave them as is.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan