Installing EPrints on RHEL/Fedora/CentOS
- RedHat Enterprise/CentOS 7 (earlier versions may work)
Add the rpm.eprints.org repository key:
... the rpm.eprints.org EPrints repository:
... on RHEL 5.x only the rpm.eprints.org RHEL updates repository:
... on RHEL 6.x only install antiword if installing EPrints 3.2.x or earlier (from 3.3 onwards only used to as a Word -> PDF converter so not strictly necessary):
rpm -ivh http://rpm.eprints.org/RHEL/5/i386/antiword-0.37-1.i386.rpm # or for 64 bit: rpm -ivh http://rpm.eprints.org/RHEL/5/x86_64/antiword-0.37-1.x86_64.rpm
Upgrade your XML libraries:
yum upgrade libxml2 libxslt perl-XML-LibXML perl-XML-LibXSLT
Install EPrints 3:
yum install eprints # 3.3.x and later yum install eprints3 # 3.2.x
Other sources for dependencies
The following RPM repositories may be useful for finding other dependencies required by EPrints that aren't part of the core RHEL system.
http://fedoraproject.org/wiki/EPEL - Fedora Extras for RHEL.
http://pkgs.repoforge.org/rpmforge-release/ - RPMforge, which covers a very large range of Perl modules plus others.
If you're using SELinux on your server you will need to give Apache read/write access to the documents directory for all repositories you create and the eprints var folder (indexer log, ticker files):
chcon -R -h -t httpd_sys_script_rw_t /usr/share/eprints/archives/[repoid]/documents/ chcon -R -h -t httpd_sys_script_rw_t /usr/share/eprints/var/
you may also need to tell SELinux to allow apache to talk on the network (maybe only if your database is on a separate server
setsebool -P httpd_can_network_connect=1
Failed to parse XML file
When installing EPrints on RHEL6 (may apply to other versions), If you get the error:
Failed to parse XML file: /usr/share/eprints/lib/lang/en/phrases/system.xml: Entity: line 396: parser error : Entity 'nbsp' not defined age or title page. If there are more...
sed -i 's/ / /g' /usr/share/eprints/lib/lang/en/phrases/system.xml
then navigate to the root of your EPrints install (/opt/eprints or /usr/share/eprints) and run
bin/generate_views *repository_id* bin/epadmin reload *repository_id*
Upgrade from previous 3.3
After a upgrading from previous 3.3, your existing repository's database may need updating.
bin/epadmin update [arcid]