Debian Known Issues

If you come across any unknown EPrints-specific issues please send a bug report to the eptech mailing list.

Known Issues

debian packages for version 3.3.13: Various problems related to subjects and divisions

Issue #291 has been resolved only after building debian packages for version 3.3.13.

This leads to problems with all operations reading tree structures from flat text files:

• bin/import_subjects produces essentially empty trees
• after creating a new repository with default divisions and subjects the divisions and subjects remain empty and more importantly, due to empty values most operations within the webinterface involving divisions or subjects yield an error, rendering the whole repository useless.

Solution: Manual edit

debian packages for version 3.3.13: links to /id/eprint/<NUMBER> yield 500 Internal Server Error

Solution: Manual edit

No Tools Available on Login

This occurs if you are using certain Firefox 3 versions on debian/ubuntu and you have your repository at http://localhost.

This is due to the fact that Firefox 3 won't let you store cookies for domains which don't have a domain. localhost.localdomain may work (untested) however the fix below encourages the use of example.org.

Basically it will work under most other browsers or you can do the following fix.

• Think of a domain for your repository and add this to your hosts file in /etc/hosts (here example.org) by doing the following as root.

 # vi /etc/hosts

Add the line

 127.0.0.1 example.org

• Then either create a new archive with example.org as its location

or

• Edit your archives 10_core.pl and change its location - as EPrints user

 vi archives/ARCHIVEID/cfg/cfg.d/10_core.pl

change the host line to your new host e.g.:

 $c->{host} = 'example.org';

Regenerate your apache config:

 bin/generate_apacheconf

As root restart your apache

 # apache2ctl graceful

Now you should be able to log in from the new url by pointing firefox at http://example.org

Wrong XML::LibXML Version

This affects mainly Ubuntu and older Debian distributions where the libxml package is too old. The package installer doesn't check the XML::LibXML version. Either install XML::LibXML 1.63 from cpan or disable it by setting enable_libxml to 0 in perl_lib/EPrints/SystemSettings.pm.

Installing 1.63 from cpan (as root):

# cpan XML::LibXML

Without either XML::LibXML or XML::GDOME, EPrints uses a bundled XML::DOM implementation that has much lower performance and poorer Unicode support. In future versions of EPrints only XML::LibXML will be supported. As this is widely available across the most commonly used Linux operating systems.

Note that you can build Debian packages from CPAN modules using dh-make-perl in order to keep track of those modules you've been building by yourself. Provided you've already configured your CPAN environment (that is, at least your proxies and servers), you can survive with:

dh-make-perl --install --notest --cpan XML::LibXML

DiskSpace.pm measuring disk usage (reiserFS)

Not supported in the default package install, to add support add the following to the array defined in $EPRINTS_HOME/perl_lib/Filesys/DiskSpace.pm

 1448756819 => "REISERFS_SUPER_MAGIC",    # 0x565A4653

Many thanks to José Miguel Parrella Romero for pointing this out.

Note that this was tested in a Debian GNU/Linux virtual private server running under Virtuozzo hypervision. Other filesystems, such as simfs, don't usually give any problems with DiskSpace.pm.

Debian 10+ (Buster, Bullseye, Bookworm etc.) does not allow unprivileged access to MySQL root user

This is also an issue with Ubuntu 20.04+, thus see advice at Installing EPrints on Debian/Ubuntu.

ImageMagick policy settings prevent PDF preview/thumbnail generation

This was identified as an issue with Debian 12 (Bookworm) but may also be an issue with earlier Debian version. ImageMagick has a policy which means it will not read PDF documents, which EPrints requires to generate preview and thumbnails of these PDFs. To fix this edit /etc/ImageMagick-6/policy.xml and change the line:

<policy domain="coder" rights="none" pattern="PDF" />

To:

<policy domain="coder" rights="read" pattern="PDF" />