EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #07303

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

Re: [EP-tech] Upgrading from 3.0

Hi Gianluca,

A colleague of mine has tidied up the instructions I wrote from doing
several EPrints 3.3.12 to 3.4 upgrades and posted them at:

https://wiki.eprints.org/w/Upgrading_3.3.12%2B_to_3.4

The instructions are significantly reduced from what I first wrote, as
he removed references to issues specific to particular repositories I
have been upgrading.  I am sure this page will need to be expanded, as
there will be common issues that people will find whilst upgrading.
 However, hopefully this guide will give a great enough overview to
help people do a successful upgrade test run.  I do not think these
instructions are sufficiently well developed yet to use then to upgrade
a live repository without testing first, unless downtime is not an
issue.

Regards

David Newman

On Tue, 2018-05-08 at 14:29 +0200, Gianluca Sforna wrote:
> On Tue, May 8, 2018 at 11:21 AM, David R Newman <drn@ecs.soton.ac.uk>
> wrote:
> > 
> > Hi Gianluca,
> > 
> > Here are some wiki pages may be of use:
> > 
> > https://wiki.eprints.org/w/Upgrading_EPrints_3_versions (it says
> > deprecated but this is more to do with 3.0 and 3.1 being really
> > quite
> > old now)
> > 
> > https://wiki.eprints.org/w/Upgrading
> > 
> >      - https://wiki.eprints.org/w/Upgrading_from_3.1
> > 
> >      - https://wiki.eprints.org/w/Upgrading_from_3.2
> > 
> > I have been writing some instructions for 3.3 to 3.4 upgrades but
> > not
> > really ready to make publicly available yet, as they have a lot of
> > repository specific references.  I don't think you need to worry
> > about
> > upgrading to 3.4 immediately.  I suspect the majority of
> > repositories
> > will take a good few months if not a year or more before upgrading
> > to 3.4.
> Yeah, I noticed the 3.4 release but decided to stick with 3.3 because
> that seemed to be more mature, and I just needed something that would
> surely work with CentOS 7.
> In other words, upgrading is my initiative, client would rather be
> happy anyway with a straight rsync (provided it worked...) from the
> old server
> 
> I will examine the carefully the referenced pages. Thank you very
> much
> 
> G.
>