The problem still exist. Cannot upgrade apache2 in Edgy to apache2 in Feisty or Gutsy.
The hardware this server is running on is due to be upgraded in Sept. I have decided to run debian on our servers and ubuntu on our desktops. The apache2 upgrade problem is not to sole reason for this decision. The primary reason is debian's use of release aliases, ie "stable, testing, unstable, experimental". If you want to see how the upgrade failed please refer to my previous attached log file. Tim On 7/13/07, Soren Hansen <[EMAIL PROTECTED]> wrote: > The trouble is that the Order directive moved during the Apache 2.2 > development cycle. It used to live in mod_access, but now lives in > mod_authz_host. This is handled in Debian and hence Ubuntu by automatically > adding these modules when doing a fresh install or when upgrading from > anything below 2.2.3-3.1. > I've tested upgrades from 2.0 (Apache2 in Edgy) to 2.2 (Apache2 in Feisty) > and all works well. Did the upgrade perhaps fail for you the first time in > some way? > > -- > Apache2 Fails to install/start > https://bugs.launchpad.net/bugs/95162 > You received this bug notification because you are a direct subscriber > of the bug. > -- Apache2 Fails to install/start https://bugs.launchpad.net/bugs/95162 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
