On Thu, Oct 26, 2023 at 4:27 PM Stephen J. Turnbull < turnbull.stephen.fw@u.tsukuba.ac.jp> wrote:
Odhiambo Washington writes:
This is the first time I am seeing this with MM3 so maybe it's something new in the latest releases?
IIRC you're one of the folks who creates a new venv and therefore gets upgrades of all prerequisite PyPI packages on upgrade. (Of course this is the recommended RightThing[tm].) If so, seems most likely that it's new in psycopg2.
I am not upgrading :-) This a completely new VM that has never seen MM3 before. A new Linux install of Debian12. I usually prefer testing first before implementing.
psycopg2 has been released 3 times since Aug 5, most recently Oct 3,
so it seems likely you've upgraded that package.
On this test machine, I have psycopg2-binary==2.8.6. The instructions on the documentation <https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mailm...> say:
pip install wheel mailman psycopg2-binary\<2.9
Try downgrading that package in the venv, to the version in the old
venv if you have that available.
There is no other venv on this host. It is not an upgrade, but a new install.
No log entry in any of the log files in /opt/mailman/mm/var/logs/.
Wouldn't expect them, since imports are early and the most likely relevant loggers (any that are in pyscopg2 itself) wouldn't be set up yet.
That makes sense.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]