On Sat, 13 Mar 2021 22:51:46 -0500, Mark Sapiro wrote:
On 3/13/21 7:08 PM, John Covici wrote:
On Sat, 13 Mar 2021 16:22:59 -0500, Abhilash Raj wrote:
My guess is that you updated the database (perhaps, by invoking the mailman command form 3.3.3) and then tried to start 3.3.2. In this case, Mailman comes up and sees a new revision for the database migration added from 3.3.3 but can’t find the same migration in its source (because it is 3.3.2).
That is sort of what happened, except in the opposite direction, it was from 3.3.3 to 3.3.2. My question is therefore, do I have to update this alembic_version when I upgrade mailman to a newer version? That is what I was getting at.
Abhilash's conjecture is that the error was due to a Mailman version accessing a database that had been previously accessed by a newer version so that the version_num in the alembic_version table didn't exist in mailman/database/alembic/versions/. This normally would not occur on an upgrade of Mailman, but if you went from a gentoo Mailman core to a version obtained by pip, it's possible that the gentoo Mailman had an alembic version that wasn't known to the pip Mailman even though the pip Mailman was newer.
OK, thanks.
-- Your life is like a penny. You're going to lose it. The question is: How do you spend it?
John Covici wb2una
covici@ccs.covici.com