[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

upgrading postgres on unstable

Time to admit the sorry truth ... at the time that I switched from RH to
Debian several years ago, my Debian install's version of postgres was
older than the version I'd compiled on RH, and consequently I had to
install from source to get postgres 7.0 functionality.

I um ... *blush* ... well, I haven't upgraded postgres since.  It's
still chugging along happily ... it's just very old =P

I'm finally attempting to bring myself into the 21st century through
apt-get.  It runs me through some config options, recognizes that I have
an old install and offers to upgrade it, and then says this:

home:/var/lib/dpkg/info# apt-get install postgresql
Reading Package Lists... Done
Building Dependency Tree... Done
Suggested packages:
  libpgperl libpgtcl postgresql-dev python-pygresql python-psycopg python-popy
  python-pgsql pgdocs ecpg
The following NEW packages will be installed:
0 upgraded, 1 newly installed, 0 to remove and 29 not upgraded.
1 not fully installed or removed.
Need to get 0B/3010kB of archives.
After unpacking 7512kB of additional disk space will be used.
Preconfiguring packages ...
(Reading database ... 76051 files and directories currently installed.)
Unpacking postgresql (from .../postgresql_7.3.4-6_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/postgresql_7.3.4-6_i386.deb 
 subprocess pre-installation script returned error exit status 20
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)

So here's my question.  How do I figure out what "exit status 20" means?
I d/l'd the source and grepped around in preinst.in, but I couldn't
figure it out.

Secondarily, is there a place that debian stores the currently-used
install files so that I don't have to download the whole source package
just to find them?  It seems like /var/lib/dpkg/info only has this sort
of thing for fully-installed packages.

Unless you need to share ultra-sensitive super-spy stuff with me, please
don't email me directly.  I will most likely see your post before I read
your mail, anyway.

Reply to: