Difference between revisions of "Issues with Installing EPrints on Ubuntu 26.04"

From EPrints Documentation
Jump to: navigation, search
(Updated to explain the problem in more detail and link to GitHub)
(Updated info about XML library issue.)
Line 1: Line 1:
As of 9th May 2026, Ubuntu 26.04 is still under testing to determine if EPrints can be successfully installed and if so if there are any issues with doing this, which require a different approach from the general approach for installing EPrints on Debian/Ubuntu Linux.
+
As of 10th May 2026, Ubuntu 26.04 is still under testing to determine if EPrints can be successfully installed and if so if there are any issues with doing this, which require a different approach from the general approach for installing EPrints on Debian/Ubuntu Linux.
  
 
==== Current Issues ====
 
==== Current Issues ====
; XML library compatability problems : This will first occur at the point where you complete the credentials you want to use for your archive's database whilst you are running <code>bin/epadmin create pub</code>.  It will exhibit itself with the following error message or possibly one that relates to memory allocation (malloc) or free commands.  This is due to how EPrints make use of the <code>XML:LibXML</code> Perl library that ultimately use the C library <tt>libxml2</tt>.  As of 9th May 202 we have yet to diagnose why this is happening.  [https://github.com/eprints/eprints3.4/issues/509 This GitHub issue] first raised for what appears to be the same issue with FreeBSD 14.3 provides some more detail about this problem.
+
; XML library compatability problems : This will first occur at the point where you complete the credentials you want to use for your archive's database whilst you are running <code>bin/epadmin create pub</code>.  It will exhibit itself as either a segmentation fault or an error with the memory allocation (malloc) or free commands.  This is due to EPrints use of the <code>XML:LibXML</code> Perl library that ultimately uses the C library <tt>libxml2</tt>.  As of 10th May 2026, we have yet to defintively determine why this is happening.  [https://github.com/eprints/eprints3.4/issues/509 This GitHub issue] first raised for what appears to be the same issue with FreeBSD 14.3 provides some more detail about this problem.  It is likely this relates to [https://github.com/cpan-authors/XML-LibXML/issues/113 this XML::LibXML GitHub issue], so it may be a while before the libxml-libxml-perl package is updated but the XML::LibXML package on CPAN will likely be updated more promptly. Currently a possible working around of disabling "expand_entities" and "load_ext_dtd" options in the calls to <code>XML::LibXML->new</code> perl_lib/EPrints/XML/LibXML.pm on lines 69 and 73.  However, further testing is required to determine what impact this temporary mitigation may have on EPrints functionality.
  Segmentation fault        (core dumped) bin/epadmin create pub
 

Revision as of 12:08, 10 May 2026

As of 10th May 2026, Ubuntu 26.04 is still under testing to determine if EPrints can be successfully installed and if so if there are any issues with doing this, which require a different approach from the general approach for installing EPrints on Debian/Ubuntu Linux.

Current Issues

XML library compatability problems 
This will first occur at the point where you complete the credentials you want to use for your archive's database whilst you are running bin/epadmin create pub. It will exhibit itself as either a segmentation fault or an error with the memory allocation (malloc) or free commands. This is due to EPrints use of the XML:LibXML Perl library that ultimately uses the C library libxml2. As of 10th May 2026, we have yet to defintively determine why this is happening. This GitHub issue first raised for what appears to be the same issue with FreeBSD 14.3 provides some more detail about this problem. It is likely this relates to this XML::LibXML GitHub issue, so it may be a while before the libxml-libxml-perl package is updated but the XML::LibXML package on CPAN will likely be updated more promptly. Currently a possible working around of disabling "expand_entities" and "load_ext_dtd" options in the calls to XML::LibXML->new perl_lib/EPrints/XML/LibXML.pm on lines 69 and 73. However, further testing is required to determine what impact this temporary mitigation may have on EPrints functionality.