[Mailman-Users] Downgrade options/alternatives
VxMr at pge.com
Thu Nov 12 16:28:49 EST 2015
Thank you for the information/confirmation. Knowing that the only thing left to do is to update the file on the last mailman version makes me feel more confident that all functional pieces were successfully rolled back. And that will make me feel better about upgrading soon.
I have checked the update script but I get some errors when trying to run the bin/update --force . I think this has to do with the import statements specified on the script. But I can say I do see the version I rolled back to through the web interface (which does appear to have rolled back successfully).
$ bin/update --help
Traceback (most recent call last):
File "bin/update", line 46, in <module>
ImportError: No module named paths
>Actually, you did do the downgrade. Only the final running of Mailman's
>bin/upgrade did not succeed. You can run it with the -f or --force
>option to make it succeed, but it won't do anything anyway except maybe
>update Mailman's data/last_mailman_version. See 'bin/upgrade --help'.
From: Mailman-Users [mailto:mailman-users-bounces+vxmr=pge.com at python.org] On Behalf Of Mark Sapiro
Sent: Thursday, November 12, 2015 12:01 PM
To: mailman-users at python.org
Subject: Re: [Mailman-Users] Downgrade options/alternatives
On 11/12/15 10:14 AM, Montanez, Victor wrote:
> I have done a successful upgrade from Mailman version 2.1.16 to 2.1.20 successfully. I am now testing the downgrade (In case some issue comes up and I have to rollback) and it seemed to have gone okay for the most part.
> At the of the end of the downgrade I get the following message(which I have googled around but no real alternative given).
> Downgrade detected, from version 0x20114f0 to version 0x20110f0
> This is probably not safe.
> make: *** [update] Error 1
> I understand is a downgrade, that is what I want to do. But it looks like "downgrading" isn't really supported in Mailman. What is a recommended alternative for having a way to go back to previous Mailman version?
Actually, you did do the downgrade. Only the final running of Mailman's
bin/upgrade did not succeed. You can run it with the -f or --force
option to make it succeed, but it won't do anything anyway except maybe
update Mailman's data/last_mailman_version. See 'bin/upgrade --help'.
Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users at python.org
More information about the Mailman-Users