Package: postgresql-common
Version: 71
Severity: serious

I tried to remove postgresql:
enterprise:~# env LANG=C aptitude purge postgresql-8.1
Reading package lists... Done
Building dependency tree... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
Building tag database... Done
The following packages are unused and will be REMOVED:
  postgresql-client-8.1 postgresql-client-common postgresql-common
The following packages will be REMOVED:
  postgresql-8.1{p}
0 packages upgraded, 0 newly installed, 4 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 17.2MB will be freed.
Do you want to continue? [Y/n/?]
Writing extended state information... Done
(Reading database ... 209457 files and directories currently installed.)
Removing postgresql-8.1 ...
Stopping PostgreSQL 8.1 database server: main* Insecure directory in 
$ENV{PATH} while running with -T switch at /usr/bin/pg_ctlcluster line 352.
Insecure directory in $ENV{PATH} while running with -T switch 
at /usr/bin/pg_ctlcluster line 360.
(does not shutdown gracefully, now stopping immediately)
 failed!
invoke-rc.d: initscript postgresql-8.1, action "stop" failed.
dpkg: error processing postgresql-8.1 (--purge):
 subprocess pre-removal script returned error exit status 1
Starting PostgreSQL 8.1 database server: main* Insecure directory in 
$ENV{PATH} while running with -T switch at /usr/bin/pg_ctlcluster line 52.
 failed!
invoke-rc.d: initscript postgresql-8.1, action "start" failed.
dpkg: error while cleaning up:
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 postgresql-8.1
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:

changing the switch -T in the first line of  pg_ctlcluster  an in 
pg_dropcluster to -t allows me to purge the package.

Regards,
Quim


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to