Your message dated Fri, 11 Aug 2006 14:53:32 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Works now
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: postgresql-common
Version: 58
Severity: normal
This problem started as I tried to maintain a mixed sarge/etch system. I
had postgresql-8.1 running well, but as it complained on every apt-get
upgrade, I decided to remove postgresql-8.1 to resolve the problem.
I had postgresql-common 55 installed, now attempting an upgrade to 58.
The problem appears as follows:
[EMAIL PROTECTED]:~> apt-get install postgresql-common postgresql-8.1
Reading package lists... Done
Building dependency tree... Done
postgresql-8.1 is already the newest version.
The following NEW packages will be installed:
postgresql-common
0 upgraded, 1 newly installed, 0 to remove and 9 not upgraded.
3 not fully installed or removed.
Need to get 0B/89.9kB of archives.
After unpacking 325kB of additional disk space will be used.
Preconfiguring packages ...
postgresql-common failed to preconfigure, with exit status 1
(Reading database ... 81797 files and directories currently installed.)
Unpacking postgresql-common (from .../postgresql-common_58_all.deb) ...
dpkg: error processing
/var/cache/apt/archives/postgresql-common_58_all.deb (--unpack):
subprocess pre-installation script returned error exit status 1
Errors were encountered while processing:
/var/cache/apt/archives/postgresql-common_58_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
In a long session on IRC with help from great many people I found that
it doesn't seem to unpack correctly, as only the postinst and list
control scripts can be found in /var/lib/dpkg/info.
There were naturally many suggestions that attempting to keep a mixed
system is a Bad Idea, but as I have limited bandwidth, I didn't want to
go for a complete dist-upgrade.
The apparent unpacking problems lead many to suggest that it was debconf
that was broken and needed upgrade, so I upgraded debconf, apt and quite
a few others, but it did not resolve the problem.
So, eventually, I did a dist-upgrade of the whole system over the night,
so the system is now fully etch. However, the problem persists.
Of course, I've tried all the usual suspects, full disk, removing,
reinstalling from scratch, unpacking control scripts with -e and moving
them to /var/lib/dpkg/info manually, but found no solution.
The system information below appears after my latest attempt to remove
everything that has to do with pg and reinstall.
So, I guess I've been doing some really wrong things here, but as I have
forced nothing, I wonder if it is a really bumpy upgrade path that has
not been discovered yet, thus this bug report.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27-2.4.27.2005-06-01.1-pooh
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages postgresql-common depends on:
ii adduser 3.95 Add and remove users and groups
ii debconf [debconf-2.0] 1.5.2 Debian configuration management sy
ii lsb-base 3.1-10 Linux Standard Base 3.1 init scrip
pn postgresql-client-common <none> (no description available)
ii procps 1:3.2.7-2 /proc file system utilities
ii ssl-cert 1.0.13 Simple debconf wrapper for openssl
postgresql-common recommends no packages.
--- End Message ---
--- Begin Message ---
So, the conclusion is that I borked the install by massaging too hard
when I installed pg 8.1. After purging the old database, it works.
--- End Message ---
