I don't know what the apt-get process does to undo what it had done up
to this point, but at this point, the new Mailman 2.1.9 had been
installed and all that was left to do was any necessary list data
migration. Since there aren't any data format changes between 2.1.9
and 2.1.11, it was essentially done.
If the installed package wasn't backed out, you can just manually run
Mailman's bin/update -f, but the real question is where did the 2.1.11
version come from and why doesn't apt-get know about it?
If I were you, I would look at Mailman's Mailman/Version.py file for
the version currently installed. If it is 2.1.11, then apt-get
reversed its changes, and what to do depends on whether you want to
leave 2.1.11 in place or overwrite it with 2.1.9. To leave it in
place, do nothing. You should be able to just start Mailman if it
isn't already running.
To overwrite 2.1.11 with 2.1.9, remove Mailman's
data/last_mailman_version file or edit its contents which are
apparently 0x2010bf0 to something like 0x20108f0 and then re-run the
apt-get.
On the other hand, if the version of Mailman's Mailman/Version.py file
is 2.1.9, then you have already over written the 2.1.11 version and
you can finish the process by stopping Mailman if it's running, then
run Mailman's
bin/update -f
and start Mailman.
okay that worked great - thanks Mark! :)
------------------------------------------------------
Mailman-Users mailing list [email protected]
http://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:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
