Difference between revisions of "Upgrading EPrints 3 versions"
| Line 1: | Line 1: | ||
EPrints developer Christopher Gutteridge gives the following instructions: | EPrints developer Christopher Gutteridge gives the following instructions: | ||
| − | Upgrading 3.0. | + | == Upgrading 3.0.x to 3.0.y == |
| + | |||
| + | This is very easy - just run <tt>configure</tt> with the | ||
<tt>--prefix</tt> set to the location of the current repo (you may also need to set the --with-user and --with-group options). Then run install.pl to upgrade the software. Then run | <tt>--prefix</tt> set to the location of the current repo (you may also need to set the --with-user and --with-group options). Then run install.pl to upgrade the software. Then run | ||
epadmin upgrade REPOID | epadmin upgrade REPOID | ||
| − | + | For each repository to update the database. Normally minor updates would not update the db at all. In this case all it does is add an SQL index to make things go faster. Restart the webserver in indexer after an upgrade. (or better, shut them off before you start to upgrade) | |
(lightly edited from [http://www.eprints.org/tech.php/6598.html], 2007-04-13 to eprints-tech) | (lightly edited from [http://www.eprints.org/tech.php/6598.html], 2007-04-13 to eprints-tech) | ||
| + | |||
| + | == Upgrading 3.0.x to 3.1.x == | ||
| + | |||
| + | This is not yet widely tested, so at your own risk. Initial notes on 3.1.0-beta-2. | ||
| + | * epadmin upgrade reports lots of SQL errors, but these don't cause any problems (and will be suppressed by -rc-1) | ||
| + | * large repositories can take a significant chunk of time to run epadmin upgrade (many minutes) | ||
| + | * "Views" get a little screwed up as the new configuration options are slightly altered. | ||
| + | * [[New Features in EPrints 3.1]] has a list of suggested configuration changes. | ||
Revision as of 15:16, 7 April 2008
EPrints developer Christopher Gutteridge gives the following instructions:
Upgrading 3.0.x to 3.0.y
This is very easy - just run configure with the --prefix set to the location of the current repo (you may also need to set the --with-user and --with-group options). Then run install.pl to upgrade the software. Then run
epadmin upgrade REPOID
For each repository to update the database. Normally minor updates would not update the db at all. In this case all it does is add an SQL index to make things go faster. Restart the webserver in indexer after an upgrade. (or better, shut them off before you start to upgrade)
(lightly edited from [1], 2007-04-13 to eprints-tech)
Upgrading 3.0.x to 3.1.x
This is not yet widely tested, so at your own risk. Initial notes on 3.1.0-beta-2.
- epadmin upgrade reports lots of SQL errors, but these don't cause any problems (and will be suppressed by -rc-1)
- large repositories can take a significant chunk of time to run epadmin upgrade (many minutes)
- "Views" get a little screwed up as the new configuration options are slightly altered.
- New Features in EPrints 3.1 has a list of suggested configuration changes.
