Hi, On 05.01.2013 18:05, Jonas Smedegaard wrote: > Severity: serious > Justification: Policy 7.2 I doubt this applies in your case. But anyway, let's not discuss about bug severities. > Setting up apache2.2-common (2.2.22-12) ... > sh: 1: .: Can't open /etc/apache2/envvars > Could not read /etc/apache2/envvars > dpkg: error processing apache2.2-common (--configure): > subprocess installed post-installation script returned error exit status 2 Could you provide a full output and what exactly you did? At very least you are probably not using the multistrap default setup which does not include Apache for obvious reasons. > Seems that error comes from a2ensite call, so I suspect the cause might > be some dependency of that script has not yet been configured. a2ensite does not call a shell to read /etc/apache2/envvars. Your output makes me suspect this is rather coming from the init script which is invoked from postinst. What makes you think a2ensite is the problem? That makes this error really strange because envvars comes from the same package and is installed through dpkg, not a maintainer script, i.e. long before the init script is called. > Perhaps apache2.2-common must pre-depend (not depend) on perl, to ensure > perl is fully configured before used. In fact, a2enmod (almost) works already with perl-base installed, which is an essential package. I say almost, because it does not include File::Basename which we use. If perl was the problem, it would fail out there. > The installation was done using multistrap which postpones more postinst > scripts than debootstrap and debian-installer. Perhaps multistrap should be fixed then. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D
Attachment:
signature.asc
Description: OpenPGP digital signature