Manually stopping of Apache was meant to help in debugging this - e.g. 
where/how does it fail?
Does it only fail, because Apache is not running and some dpkg-script does not 
handle it correctly?

IMHO the bug title is misleading: PHP5 does not cause breaking this - but 
apache2-common from edgy (according to bug #88210).
The PHP error then also results from a broken Apache setup, doesn't it?

-- 
PHP5 breaks apache update
https://launchpad.net/bugs/95325

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to