[Bug 988819] Re: [SRU] wrong path to libxml2.so.2 in mod_security - broken by multiarch enabled libraries
Steve Langasek
steve.langasek at canonical.com
Tue Jul 3 20:56:08 UTC 2012
I have serious misgivings about the particular approach taken here, in
SRU or otherwise. Why does mod-security.load need to hard-code
libxml2.so.2 *at all*? Isn't that why DSOs are dynamically linked to
their dependent libraries (which mod_security2.so is)? And why is
libxml2.so.2 being special-cased here, when mod_security2.so is also
linked against liblua5.1.so.0? Did anyone try to fix this by just
removing the LoadFile line completely? That would be a much safer fix
than SRUing the core of apache2, and would probably fix the problem that
this SRU seems to be stalled waiting for indeterminate regression
testing of "corner cases".
A naive test here of commenting out this 'LoadFile' line shows that the
apache config validates, and apache2-mpm-prefork starts without any
problems.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/988819
Title:
[SRU] wrong path to libxml2.so.2 in mod_security - broken by multiarch
enabled libraries
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/988819/+subscriptions
More information about the Ubuntu-server-bugs
mailing list