package postgis can't be purged if postgresql is not installed due to missing directory
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postgis (Debian) |
Fix Released
|
Unknown
|
|||
postgis (Ubuntu) |
Fix Released
|
Low
|
Jean-Baptiste Lallement | ||
Karmic |
Fix Released
|
Undecided
|
Jean-Baptiste Lallement |
Bug Description
:: DESCRIPTION ::
postgis can't be removed if postgresql is not installed due to missing "/usr/lib/
:: VERSION ::
postgis | 1.3.3-3 | intrepid/universe | source, amd64, i386
postgis | 1.3.3-3 | jaunty/universe | source, amd64, i386
postgis | 1.3.5-1 | karmic/universe | source, amd64, i386
postgis | 1.3.6-2 | lucid/universe | source, amd64, i386
:: TEST CASE ::
$ sudo apt-get install postgis
$ sudo apt-get remove --purge postgis
Removing postgis ...
Purging configuration files for postgis ...
find: `/usr/lib/
dpkg: error processing postgis (--purge):
subprocess post-removal script returned error exit status 1
:: WORKAROUND ::
$ sudo rm /var/lib/
$ sudo apt-get remove --purge postgis
=======
ProblemType: Package
Architecture: i386
Dependencies:
DistroRelease: Ubuntu 8.10
ErrorMessage: subprocess post-removal script returned error exit status 1
NonfreeKernelMo
Package: postgis None
SourcePackage: postgis
Title: package postgis None failed to install/upgrade: subprocess post-removal script returned error exit status 1
Uname: Linux 2.6.27-14-generic i686
Related branches
summary: |
- package postgis None failed to install/upgrade: subprocess post-removal - script returned error exit status 1 + package postgis can't be removed is postgresql is not installed due to + missing directory |
description: | updated |
summary: |
- package postgis can't be removed is postgresql is not installed due to + package postgis can't be purged if postgresql is not installed due to missing directory |
Changed in postgis (Debian): | |
status: | Unknown → Fix Released |
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.