Hello Mark,
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).
Thank you
$ bin/update --help
Traceback (most recent call last):
File "bin/update", line 46, in <module>
import paths
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'.
-----Original Message-----
From: Mailman-Users [mailto:[email protected]] On
Behalf Of Mark Sapiro
Sent: Thursday, November 12, 2015 12:01 PM
To: [email protected]
Subject: Re: [Mailman-Users] Downgrade options/alternatives
On 11/12/15 10:14 AM, Montanez, Victor wrote:
>
> Hello,
>
> 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.
>
> Exiting.
>
> 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 <[email protected]> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list [email protected]
------------------------------------------------------
Mailman-Users mailing list [email protected]
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
