Hi!
Am 2011-03-15 um 10:16 schrieb Holger Levsen:
> On Montag, 14. März 2011, Claus Färber wrote:
>> When Apache 2.2 is not installed, typo3-dummy fails to install and,
>> which is more severe, to uninstall:
>
> Actually, failing to install+remove is more severe than failing to purge,
> though all of this is pretty bad. It just doesnt make the package completly
> unusable for everyone.
Unfortunately, it fails to install & uninstall, too:
$ sudo aptitude install typo3-dummy
The following NEW packages will be installed:
typo3-dummy
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/26.4 kB of archives. After unpacking 319 kB will be used.
Preconfiguring packages ...
Selecting previously deselected package typo3-dummy.
(Reading database ... 51379 files and directories currently installed.)
Unpacking typo3-dummy (from .../typo3-dummy_4.3.0-4.1_all.deb) ...
Setting up typo3-dummy (4.3.0-4.1) ...
dbconfig-common: writing config to /etc/dbconfig-common/typo3-dummy.conf
Creating config file /etc/dbconfig-common/typo3-dummy.conf with new version
Creating config file /etc/typo3-dummy/debian-db.php with new version
dbconfig-common: flushing administrative password
/var/lib/dpkg/info/typo3-dummy.postinst: 39: a2ensite: not found
dpkg: error processing typo3-dummy (--configure):
subprocess installed post-installation script returned error exit status 127
configured to not write apport reports
Errors were encountered while processing:
typo3-dummy
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up typo3-dummy (4.3.0-4.1) ...
dbconfig-common: writing config to /etc/dbconfig-common/typo3-dummy.conf
Replacing config file /etc/typo3-dummy/debian-db.php with new version
dbconfig-common: flushing administrative password
/var/lib/dpkg/info/typo3-dummy.postinst: 39: a2ensite: not found
dpkg: error processing typo3-dummy (--configure):
subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
typo3-dummy
$ sudo dpkg --remove typo3-dummy
(Reading database ... 51441 files and directories currently installed.)
Removing typo3-dummy ...
/var/lib/dpkg/info/typo3-dummy.postrm: 42: a2dissite: not found
dpkg: error processing typo3-dummy (--remove):
subprocess installed post-removal script returned error exit status 127
Errors were encountered while processing:
typo3-dummy
The problem is that a2ensite or a2dissite are called in the post-configure and
postrm scripts the even though the dependencies don't guarantee that these
programmes be present (and in postrm, it's not guaranteed even then).
Not even being able to remove the package that has failed to install is pretty
bad: You can't use aptitude any longer because it tries to install (or
uninstall) the package every time you want to add/remove other packages, often
failing the complete process.
>> (Please note that php5 depends on libapache2-mod-php5 |
>> libapache2-mod-php5filter | php5-cgi, only the first two options
>> depend on apache2.2-common.)
>
> Is this why you wrote typo3-dummy fails to install?
Somewhat. Without php5-cgi, apache2.2-common would have to be installed and
a2ensite/a2dissite would be available. However, you couldn't use typo3 with the
CGI version of PHP under Apache 2, then (not that anyone would want to do this).
Removing php5-cgi would be a quick fix, but a Depends: apache2.2-common would
be more appropriate.
Best Regards
Claus
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
