Debian Upgrading
This page applies to Moin users who have installed their wiki originally by using debian packages. Before going through this, maybe you'd like to see the more general HelpOnUpdating, to understand the general protocol.
moin 1.2.x
moin_1.2.4-1_all.deb is the last 1.2.x series deb package, and upgrading any earlier 1.2.x versions of moin via debian package to this one seems to work just fine.
moin 1.2.x deb to 1.3.x upstream sources via arch
The debian package name for GNU Arch is tla and you can fetch the archive that way if you like, after which all ordinary directions for installing MoinMoin and continuing to upgrade it will apply.
- Backup your stuff first
- your moin code
your wiki's data directory - if you have multiple wiki, make a seperate tarball each.
- your theme stuff, especially if you've done customizations - themes are very different now.
Get the moin upstream package (see MoinMoinDownload)
It is possible to tell the debian system that you do have moin, in a way that will not allow it to be overrun by the debian packaging system later, however since other packages do not currently depend on moin you do not need to do this.
moin 1.2.x deb to 1.3 via debian package
1.3.4-1 package upgrade gets you a non-working wiki, because your data is unharmed, but still in 1.2.x format and cannot be served by current moin.
For everyone whose package name moin upgraded on its own, this might be why you are here; the maintainer provided /usr/share/docs/moin/README.migration.bz but did not have debconf warn you of the transition.
A bug was filed. See /Debian13FiascoLog for the discussion in irc that led to this filing.
As of 1.3.4-3, the name moin no longer upgrades standing 1.2.x installations, and the new package is being split into multiple packages to save space for people who don't need internationalized wikis. The moin developers do not know, at this time, if the extra packages provide automatic migration in debconf yet, and it is entirely likely that they do not. See below about completing the migration, if that is still a problem and you have chosen to upgrade.
The reason for the split was to support multiple versions of Python. Non-english stuff may be split off at some point, but is not done currently. I'd really want the separation automated as mentioned loong ago at JonasSmedegaard -- -- JonasSmedegaard 2005-05-04 20:12:33
That just leaves us how to help you with completing the upgrade, or returning to your previous package.
|
Choose only one direction, downgrade or upgrade! |
![/!\](/moin_static19/modernized/img/alert.png "/!\"){kind=small}
Sudden Death / Resurrection: Downgrading to 1.2.4-1
Debian keeps its downloaded deb files in /var/cache/apt/archives/ -- if you still have your moin_1.2.4-1_all.deb package there, excellent. Otherwise, retrieve a fresh copy of it from the debian snapshots archive: http://snapshot.debian.net/archive/2004/10/30/debian/pool/main/m/moin/
Now, issue the command: dpkg -i --force-downgrade moin_1.2.4-1_all.deb
Your moin should be fully operational.
In for a Dime, In for a Dollar / Completing The Migration: Upgrading to 1.3.4
We have a set of migration scripts, which you must apply to your wiki's data/ directory. These are stored in the place where your moin code sits, /usr/lib/python2.3/MoinMoin/scripts/migration
Because they expect to work on a directory named data within their current directory, it would be best to create a special migrations directory, and copy the set of scripts into there, plus cp -a your data tree from the wiki you want to migrate. Each script must be run only once, from 1 up to the highest numbered 12_to_13_mig script that is present. An extra copy of the data tree is made for each change.
Yes, we know it's a bit space consuming, we were being hypercareful during the version transition. If you want to know more exactly what to expect in terms of directory size during each step, there are some notes in MoinMoinBugs/MigrationIssues. Rule of thumb, it'll take about N+1 times the space, (where N is how many scripts) unless you are getting rid of the intermediate directories along the way.
We have had several people transition smoothly and report no data lost. Please feel free to add comments.
For massive wiki farms this will be time consuming, and has to be done one wiki at a time. Also, you must access the data with only the correct version of the wiki software after it is transitioned. It doesn't take very long per - maybe 20 or 30 minutes - but you don't want to get people's data trees mixed up.
WORTH CHECKING: the config file format has more things in it now. See the example templates under /usr/share/moin/config
All settled in? Enjoy your much faster and spam-defending moin!
-- Heather Stern, 13 Apr 2005 4:16 pm PDT
Issues remaining
Debian package 1.3.4-2 is rarely found; its release period was very short.
Debian package 1.3.4-3 has been reconfigured and split into several parts, as noted above. We are still receiving occasional reports of people having trouble with transition - python 2.4's variant may have the wrong migration scripts. If you think you have the wrong ones, try these, they worked fine on a wiki dataset under debian's 1.2.4 package:
1.3.4-2 is broken - attempts at using the python 2.4 variant causes a mix of 2.3 and 2.4. Why would you ever want that broken package? -- -- JonasSmedegaard 2005-05-04 20:12:33
Please read the Debian Bug Tracking System (bugs.debian.org, bugs on packages containing the word moin) and be willing to tell us exactly which moin version you have when you pop into MoinMoinChat - we will help in any way that we can, but some bugs might not be ours.
Also feel free to file bugreports against the package in Debian if you believe errors to belong there. Writing about it here (without notifying me about the existence of this page!) sure won't help improve the package :-P -- -- JonasSmedegaard 2005-05-04 20:12:33