Your message dated Mon, 15 Oct 2012 17:05:18 +0200 with message-id <[email protected]> and subject line Re: Bug#581889: posgresql-8.3: cannot purge after it has been removed has caused the Debian Bug report #581889, regarding posgresql-8.3: cannot purge after it has been removed to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 581889: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581889 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: postgresql-8.3 Version: postgresql-8.3: cannot purge after it has been removed Severity: important postgresql-8.3 was removed by incident of postgresql-8.4 being installed. sysvrc wants me to purge 8.3 so i can move to a dependency-based boot. however, "apitutude purge postgresql-8.3" renders this error message: Purging configuration files for postgresql-8.3 ... Dropping cluster main... Error: pid file is invalid, please manually kill the stale server process. Error: could not stop server, aborting dpkg: error processing postgresql-8.3 (--purge): subprocess installed post-removal script returned error exit status 1 Can you fix this in the package so future versions dont have this problem? I'm going to try to hack the prerm/postrm/whatever file so I can get this package off my system in the meantime. Thanks, Tyler -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages postgresql-8.3 depends on: ii libc6 2.10.2-8 Embedded GNU C Library: Shared lib ii libcomerr2 1.41.11-1 common error description library ii libgssapi-krb5-2 1.8.1+dfsg-2 MIT Kerberos runtime libraries - k ii libkrb5-3 1.8.1+dfsg-2 MIT Kerberos runtime libraries ii libldap-2.4-2 2.4.21-1 OpenLDAP libraries ii libpam0g 1.1.1-3 Pluggable Authentication Modules l ii libpq5 8.4.3-1 PostgreSQL C client library ii libssl0.9.8 0.9.8n-1 SSL shared libraries ii libxml2 2.7.7.dfsg-2 GNOME XML library ii locales 2.10.2-8 Embedded GNU C Library: National L pn postgresql-client-8.3 <none> (no description available) ii postgresql-common 107 PostgreSQL database-cluster manage ii ssl-cert 1.0.25 simple debconf wrapper for OpenSSL ii tzdata 2010j-1 time zone and daylight-saving time postgresql-8.3 recommends no packages. Versions of packages postgresql-8.3 suggests: ii pidentd [ident-server] 3.0.19.ds1-5 TCP/IP IDENT protocol server with
--- End Message ---
--- Begin Message ---Re: Tyler MacDonald 2010-05-17 <[email protected]> > Package: postgresql-8.3 > Version: postgresql-8.3: cannot purge after it has been removed > Severity: important > > > postgresql-8.3 was removed by incident of postgresql-8.4 being installed. > sysvrc wants me to purge 8.3 so i can move to a dependency-based boot. > however, "apitutude purge postgresql-8.3" renders this error message: > > Purging configuration files for postgresql-8.3 ... > Dropping cluster main... > Error: pid file is invalid, please manually kill the stale server process. > Error: could not stop server, aborting > dpkg: error processing postgresql-8.3 (--purge): > subprocess installed post-removal script returned error exit status 1 > > > Can you fix this in the package so future versions dont have this problem? > I'm going to try to hack the prerm/postrm/whatever file so I can get this > package off my system in the meantime. Hi Tyler, sorry for getting back to you so late on this. The package responsible for starting/stopping the servers is postgresql-common. There have been numerous fixes in that area lately, so I will assume the problem you are describing is fixed as well. Closing the bug now. Christoph -- [email protected] | http://www.df7cb.de/
--- End Message ---
