On Sat, 13 Mar 2021 16:22:59 -0500, Abhilash Raj wrote:
On Mar 13, 2021, at 1:09 PM, John Covici <covici@ccs.covici.com> wrote:
On Sat, 13 Mar 2021 14:46:55 -0500, Mark Sapiro wrote:
On 3/13/21 11:14 AM, John Covici wrote:
Now one thing came up while trying to create the database, I got a traceback complaining about a revision error because gentoo had a slightly different version (3.3.2) instead of 3.3.3 using pip. When I upgrade mailman, am I going to have to do something to the database as well and why should the database have some kind of reference to the mailman version?
I don't know why this is an issue. You shouldn't need to do anything with the database when you upgrade. Please post the full traceback and error message.
Sorry I can't reproduce it, after dropping and recreating the database the error went away, but it was in alembic and it was talking about an invalid revision and gave a long hex string.
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.
-- 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