Hrm, so now how do I set the severity in LP? This is critical.
If this wents from proposed to updates, we have a problem.
--
hardy-proposed (2.2.8-1ubuntu0.16) uninstallable
https://bugs.launchpad.net/bugs/583698
You received this bug notification because you are a member of Ubuntu
Server Team,
** Changed in: apache2 (Ubuntu)
Importance: Undecided = Critical
** Tags added: regression-proposed
--
hardy-proposed (2.2.8-1ubuntu0.16) uninstallable
https://bugs.launchpad.net/bugs/583698
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This regression does not appear to be specific to the version in hardy-
proposed.
--
hardy-proposed (2.2.8-1ubuntu0.16) uninstallable
https://bugs.launchpad.net/bugs/583698
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in
This affects specifically users who have statoverrides set for
/usr/sbin/apache2. This doesn't seem to be done by anything in the
current packaging; it could either be manual, or the relics of an old
script. Did you intentionally make /usr/sbin/apache2 non-executable?
The bug is that cut is
@Thorsten: Can you clarify the background with the history of this
machine:
Was this a fresh install of Hardy, where you already had Apache
installed (with -proposed enabled) and upgraded to *0.16 as part of your
normal upgrades?
Older install, upgraded from say dapper with -proposed already
@Dave: Old install of hardy (these are our desktop systems at work), which got
upgraded (as it is, daily).
My machine has proposed in sources.list as I’m the admin in charge of them.
@Colin: Yes, -x’ing apache was intentional, to have it installed/usable
but not enabled by default.
** Changed
@Thorsten: From the comments Colin has added, it seems that you would
have encountered this bug on *any* apache2 upgrade. I'm guessing that
/usr/bin/apache2 was set -x, and this is the first upgrade of apache2
since.
Colin has outlined a fix, and as this only causes an issue for a small
subset
