Re: PostgreSQL 7.1 packages for potato
On Mon, Jul 02, 2001 at 04:15:14AM -0500, Donald R. Spoon wrote:
> Will Trillich wrote:
> >---snip---<
> > # apt-get -f install
> > Reading Package Lists... Done
> > Building Dependency Tree... Done
> > Correcting dependencies... Done
> > The following extra packages will be installed:
> > libpgsql2.1
> > The following packages will be REMOVED:
> > libpgsql2
> > The following NEW packages will be installed:
> > libpgsql2.1
> > 0 packages upgraded, 1 newly installed, 1 to remove and 1 not upgraded.
> > 7 packages not fully installed or removed.
> > Need to get 0B/180kB of archives. After unpacking 492kB will be used.
> > Do you want to continue? [Y/n]
> > (Reading database ... 46246 files and directories currently installed.)
> > Removing libpgsql2 ...
> > /var/lib/dpkg/info/libpgsql2.prerm: /etc/postgresql/postmaster.conf: No such file or directory
> > dpkg: error processing libpgsql2 (--remove):
> > subprocess pre-removal script returned error exit status 1
> > Errors were encountered while processing:
> > libpgsql2
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> >
> >
> >
> > what's the remedy for this? now, my postgresql seems down for the
> > count... :(
> >
>
> I ran into this exact same "won't-loop" tonight while moving from Potato
> ---> Testing using "apt-get dist-upgrade". After about a half hour of
> running around the loop and doing all the same stuff that you did, I
> fired up dselect and REMOVED the old postgresql packages from Potato
> completely including the python-pygresql package, then did another
> "apt-get update" and "atp-get dist-upgrade" and everything slid in quite
> smoothly...almost <g>. I had some problems with the X upgrade to 4.0.3
> (didn't install the fonts), and also it complained about some sort of
> ddd conflicts but those were separate issues. I dunno if you can just
> use the "apt-get remove postgresql" command or not...didn't think of it
> at the time. This was/is a somewhat MAJOR problem in doing an upgrade
> as this "loop" comes early in the upgrade and stalls out the process
> until you resolve it.
>
> Bottom line: Remove the OLD postgresql packages first (be sure to save
> any databases you have somewhere safe) then install the new packages &
> restore your database. Be sure to read the docs on migration of your
> old db to the 7.1 format. That is what worked here...(on July Fool's
> Day <g>).
i tried remove and purge and eradicate and zap and disintegrate
but it always failed (apt-get and dpkg and dselect) but when i
did the "touch /etc/postgresql/postmaster.conf" then everything
went smoothly thereafter.
but re-loading the database from 7.0.3 pg_dump into 7.1 psql was
a bit harrowing nonetheless -- lots more strict on various
features (foreign key for example)...
and now you can't "psql -l" to see the databases: you have to
specify a database even if you don't intend to do anything with
it: "psql -l template0" -- what's up with THAT?
--
DEBIAN NEWBIE TIP #25 from Will Trillich <will@serensoft.com>
:
Did you know you have MORE THAN ONE CONSOLE to use? There's six,
by default: try Control-Alt-F6 to see console six, Ctl-Alt-F3 for
console 3, and so forth. (If you don't use the X window display
system, you don't need to include the control key.) Each console
can have its own login, running its own jobs. Very handy!
Also see http://newbieDoc.sourceForge.net/ ...
Reply to: