Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
apache2 : Depends: apache2-mpm-worker (= 2.2.22-13) but it is not going to be installed or
apache2-mpm-prefork (= 2.2.22-13) but it is not going to be installed or
apache2-mpm-event (= 2.2.22-13) but it is not going to be installed or
apache2-mpm-itk (= 2.2.22-13) but it is not going to be installed
Depends: apache2.2-common (= 2.2.22-13) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
apache2 : Depends: apache2-mpm-worker (= 2.2.22-13) but it is not going to be installed or
apache2-mpm-prefork (= 2.2.22-13) but it is not going to be installed or
apache2-mpm-event (= 2.2.22-13) but it is not going to be installed or
apache2-mpm-itk (= 2.2.22-13) but it is not going to be installed
Depends: apache2.2-common (= 2.2.22-13) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
at my vps it takes up to 2 hours. it depends on the hoster.
i hope so, if you watch out for errors during the ipc-setup it should install all needed packages. When you look along the board you can see, that nobody have errors like you.
And most of the users use a virgin debian-system.