From: Tim Brody <tdb2 AT ecs.soton.ac.uk>
Date: Tue, 16 Mar 2010 15:32:04 +0000
| Threading: | ↑ [EP-tech] Repository Upgrade Problem from mawest2 AT bsu.edu • This Message |
In bin/epadmin it looks like this:
sub upgrade_3_1_0_to_3_1_1
{
my( $repoid, $db ) = AT _;
my $repo = EPrints::Repository->new( $repoid );
update_datasets( $repo, $db );
}
Should be:
sub upgrade_3_1_0_to_3_1_1
{
my( $repoid, $db ) = AT _;
my $repo = &repository( $repoid );
update_datasets( $repo, $db );
}
On Tue, 2010-03-16 at 10:50 -0400, West, Mark Andrew wrote:
> Greetings,
>
> I am transferring a copy of my university repository to a demonstration ↵
server. The production server runs EPrints 3.0 on Windows 2003. The demo ↵
server runs EPrints 3.2 on Fedora 12. The transfer has been going fairly ↵
smoothly up to the point where it is time to upgrade the repository schema to ↵
3.2.
>
> sh-4.0$ bin/epadmin upgrade bsuirep
>
> ...
>
> Upgrading 3.1.0 to 3.1.1
> No repository named 'EPrints::Repository=HASH(0xaa9bb6c)' found in ↵
/opt/eprints3/archives.
>
> This 'no repository' message is blocking further attempts to finish the ↵
transfer. What exactly am I looking at?
>
> --------------------------------------------------------
> Andy West
> Microcomputer/Systems/Network Analyst v: 765 285-8032
> Ball State University e: mawest2/at/bsu/dot/edu
> Muncie, IN 47306 w: mawest2.iweb.bsu.edu
> --------------------------------------------------------------
> Ball State University Libraries
> A destination for research, learning and friends.
>
>
> *** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
> *** Archive: http://www.eprints.org/tech.php/
> *** EPrints community wiki: http://wiki.eprints.org/
*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/