package gosa 2.5.19-2 failed to install/upgrade: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 1 zurück

[Jürgen Schroll]

Binary package hint: gosa

I can't purge or remove gosa

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: gosa 2.5.19-2
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: nvidia
AptOrdering: gosa: Remove
Architecture: amd64
Date: Tue May 4 18:38:16 2010
ErrorMessage: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 1 zurück
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
PackageArchitecture: all
SourcePackage: gosa
Title: package gosa 2.5.19-2 failed to install/upgrade: Unterprozess installiertes post-removal-Skript gab den Fehlerwert 1 zurück

[Niall Creech (sevenmachines-deactivatedaccount)]

in /var/lib/dpkg/info/gosa.postrm:

 for srv in apache apache-ssl; do
                dpkg -s $srv 2>&1 | grep -q "^Status:.*not-installed"
                if [ $? -eq 1 ]; then
                        servers="$srv $servers"
                fi
        done

looks like dpkg -s $srv 2>&1 | grep -q "^Status:.*not-installed" no longer works as expected since these packages are deprecated theres no info available and this causes the script to exit

i'm guessing its trying to find a way to remove the gosa.conf scripts from server configs in /etc but this wouldnt remove /etc/apache2/conf.d/gosa.conf anyway

since gosa now depends on apache2 it might be ok just to remove the above lines and just attempt to remove the config

if [ -e /etc/apache2/conf.d/gosa.conf ]; then
    rm /etc/apache2/conf.d/gosa.conf
fi

[Michael Vogt (mvo)]

During a automatic intall/remove of the package the following problems were found from the package auto-install-tester on current lucid:
(Reading database ... 417291 files and directories currently installed.)
Removing gosa ...
dpkg: error processing gosa (--remove):
 subprocess installed post-removal script returned error exit status 1

[Stefano Travelli (stefano-travelli)]

Fix from comment #2 worked for me, but I also had to comment the following line near the end of gosa.postrm:

# Restart servers
# /usr/share/wwwconfig-common/restart.sh <--- Comment this as this command doesn't exist.