This bug was fixed in the package modsecurity-apache - 2.6.3-1ubuntu0.2
---
modsecurity-apache (2.6.3-1ubuntu0.2) precise-proposed; urgency=low
* debian/mod-security.load: revert previous change, since an alternate
solution has been agreed in the bug.
*
This bug was fixed in the package mod-proxy-html - 3.0.1-1ubuntu0.1
---
mod-proxy-html (3.0.1-1ubuntu0.1) precise-proposed; urgency=low
* debian/rules: explicitly link against libxml2.so, so that it gets
declared as a dependency. This will allow apache to load the module
libapache2-modsecurity now installs fine.
--
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
libapache2-mod-proxy-html also installs fine.
** Tags removed: verification-needed
** Tags added: verification-done
--
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:
The tests above were done without the updated apache2 from -proposed as
this one was the previous fix and was now pulled out of -proposed.
Marking verification-done.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
Hello Christoph_vW, or anyone else affected,
Accepted modsecurity-apache into precise-proposed. The package will
build now and be available at http://launchpad.net/ubuntu/+source
/modsecurity-apache/2.6.3-1ubuntu0.2 in a few hours, and then in the
-proposed repository.
Please help us by testing
** Branch linked: lp:~ubuntu-branches/ubuntu/precise/mod-proxy-html
/precise-proposed
--
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
Removing the LoadFile /usr/lib/libxml2.so.2 line from /etc/apache2
/mods-available/mod_security2.so works fixes the immediate problem and
apache does load OK and serves the root page after this. So this fix is
a candidate for a simple SRU to Precise.
However, I am concerned to make sure that
jamespage rbasak, I think that the test case can be technical
jamespage so for example I think its sufficient to say - yes we can restart
apache OK with it installed and we can see that this library has been loaded by
using lsof or suchlike
Based on this, my test case for SRU verification will
Marked bug task for apache2 as 'Invalid' as this is being fix in just
the modules.
** Changed in: mod-proxy-html (Ubuntu Precise)
Milestone: None = ubuntu-12.04.1
** Changed in: mod-proxy-html (Ubuntu Precise)
Assignee: (unassigned) = Robie Basak (racb)
** Changed in: mod-proxy-html
** Changed in: mod-proxy-html (Ubuntu Precise)
Status: Confirmed = In Progress
** Changed in: apache2 (Ubuntu Precise)
Assignee: Robie Basak (racb) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in
** Description changed:
[Impact]
- The libapache2-modsecurity package does not work out of the box (but a
- workaround is available).
+ The libapache2-modsecurity and libapache2-mod-proxy-html packages does
+ not work out of the box (but workarounds are available).
[Test Case]
-
Robie - both MP's looked good - uploaded.
--
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
Since the fix in -proposed is in doubt, I've marked the bug
verification-failed. We can remove the package from precise-proposed if
need be. Otherwise, upload whatever fix is appropriate to proposed.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this
The SRU I proposed just backports the fix that Debian have applied. If
we want to do something else in Quantal, then we'd be deviating from
Debian on this. Is this worth doing?
Of course, the SRU can be done differently. If commenting out LoadFile
works, then perhaps that's all we need to do for
There are two schools of thought here. Some people prefer linking to the
libraries directly (the saner approach for a Linux distribution) and
some people prefer to load depending libraries with LoadFile (to make it
easier to avoid loading to different versions of the same library in the
same
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
** Also affects: mod-proxy-html (Ubuntu)
Importance: Undecided
Status: New
--
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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mod-proxy-html (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mod-proxy-html (Ubuntu Precise)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
** Changed in: mod-proxy-html (Ubuntu)
Status: Confirmed = Fix Released
--
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
sudo apt-get install apache2 libapache2-modsecurity
[]
Setting up apache2.2-common (2.2.22-1ubuntu1.1) ...
Enabling site default.
Enabling module alias.
Enabling module autoindex.
Enabling module dir.
Enabling module env.
Enabling module mime.
Enabling module negotiation.
Enabling module
The specific issue this fix resolves tested OK - but as Clint states
this probably needs more thorough testing before acceptance into
-updates.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
I'm a little concerned about how deep inside the core of Apache this
change is. I think its probably, as you say, a corner case if it causes
somebody issues, but we should make sure it actually works as we think
it does by testing some of those corner cases.
** Changed in: apache2 (Ubuntu
** Branch linked: lp:ubuntu/precise-proposed/modsecurity-apache
** Branch linked: lp:ubuntu/precise-proposed/apache2
--
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:
** Changed in: apache2 (Ubuntu Precise)
Status: Triaged = In Progress
** Changed in: modsecurity-apache (Ubuntu Precise)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
** Summary changed:
- wrong path to libxml2.so.2 in mod_security
+ [SRU] wrong path to libxml2.so.2 in mod_security - broken by multiarch
enabled libraries
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
27 matches
Mail list logo
