On 2026/07/01 17:21, Daniel Dickman wrote: > Here's 15 new ports needed in order to update mail/mailman from version > 2.1.39 which uses Python 2 to version 3.3.10 which uses Python 3.
mailman2 and mailman3 need to be installed in parallel to manage the migration. when I read your earlier mail "porting mailman 2 to 3" I thought you were talking about porting it to python 3... (there is also https://github.com/jaredmauch/mailman2-python3 which while still labelled 'alpha' is very active). mailman2 and mailman3 are not really comparable anyway, mailman3 is a very different beast and most list admins seem to move to other software (mlmmj etc) rather than to mailman3. also it really seems intended to run in a venv. I'm a bit concerned about keeping all of those moving parts synchronized otherwise... > ok to import these new deps? > > devel/py-zopehookable > devel/py-zopei18nmessageid > devel/py-zopeschema > devel/py-zopeconfiguration > devel/py-atpublic > devel/py-flufl.bounce > devel/py-flufl.i18n > devel/py-flufl.lock > devel/py-lazr.delegates > devel/py-lazr.config > devel/py-publicsuffix2 > mail/py-authheaders > mail/py-aiosmtpd > mail/py-standard-nntplib > www/py-falcon >
