Mail delivery failed: returning message to sender
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to all of its recipients. The
following address(es) failed:
absurd@localhost:
generated |/usr/bin/procmail -Y -f -
The following text was generated during the delivery attempt:
------ |/usr/bin/procmail -Y -f - ------
do_ypcall: clnt_call: RPC: Remote system error
------ This is a copy of the message, including all the headers. ------
Return-path: <debian-devel@lists.debian.org>
Received: from localhost [127.0.0.1] (absurd)
by renfield.nib15.intra with esmtp (Exim 2.05 #1 (Debian))
id 12tyQl-0007gT-01; Mon, 22 May 2000 22:04:03 +0200
Received: from pophost.fh-worms.de
by fetchmail-4.6.4 POP3
for <absurd/localhost> (single-drop); Mon, 22 May 2000 22:04:03 CEST
Received: from villon.Fh-Worms.DE (villon.fh-worms.de [143.93.160.9])
by swemmel.Fh-Worms.DE (8.9.3/8.9.3) with ESMTP id KAA15661
for <inf222@swemmel.fh-worms.de>; Mon, 22 May 2000 10:35:36 +0200 (MET DST)
Received: from master.debian.org (mail@master.debian.org [216.234.231.5])
by villon.Fh-Worms.DE (8.9.3/8.9.3) with ESMTP id KAA06460
for <inf222@fh-worms.de>; Mon, 22 May 2000 10:35:35 +0200 (MET DST)
Received: from murphy.debian.org [216.234.231.6]
by master.debian.org with smtp (Exim 3.12 #2 (Debian))
id 12tngT-000252-00; Mon, 22 May 2000 03:35:33 -0500
Received: (qmail 27730 invoked by uid 38); 22 May 2000 08:35:31 -0000
X-Envelope-Sender: cech@atrey.karlin.mff.cuni.cz
Received: (qmail 27696 invoked from network); 22 May 2000 08:35:30 -0000
Received: from atrey.karlin.mff.cuni.cz (root@195.113.31.123)
by murphy.debian.org with SMTP; 22 May 2000 08:35:30 -0000
Received: (from cech@localhost)
by atrey.karlin.mff.cuni.cz (8.8.8/8.8.8) id KAA10731;
Mon, 22 May 2000 10:35:24 +0200
Date: Mon, 22 May 2000 10:35:24 +0200
From: Petr Cech <cech@atrey.karlin.mff.cuni.cz>
To: Oliver Elphick <olly@lfix.co.uk>
Cc: debian-devel@lists.debian.org
Subject: Re: PostgreSQL upgrade from slink - proposed solution
Message-ID: <[🔎] 20000522103524.B9843@atrey.karlin.mff.cuni.cz>
Mail-Followup-To: Oliver Elphick <olly@lfix.co.uk>,
debian-devel@lists.debian.org
References: <[🔎] 200005210626.e4L6QsJ16495@linda.lfix.co.uk>
Mime-Version: 1.0
Content-Disposition: inline
User-Agent: Mutt/1.1.11i
In-Reply-To: <[🔎] 200005210626.e4L6QsJ16495@linda.lfix.co.uk>; from olly@lfix.co.uk on Sun, May 21, 2000 at 07:26:53AM +0100
Resent-Message-ID: <KBTMRC.A.GxG.TFPK5@murphy>
Resent-From: debian-devel@lists.debian.org
X-Mailing-List: <debian-devel@lists.debian.org> archive/latest/60804
X-Loop: debian-devel@lists.debian.org
Precedence: list
Resent-Sender: debian-devel-request@lists.debian.org
Resent-Date: Mon, 22 May 2000 03:35:33 -0500
Content-Type: text/plain; charset=us-ascii
X-UIDL: 7b3e6c458757069a31720b4f533452c5
Resent-Bcc:
On Sun, May 21, 2000 at 07:26:53AM +0100 , Oliver Elphick wrote:
> Summary of the problem: postgresql needs to use the binaries of the previous
> release to make a dump of the database, if the old database version is built
> by an earlier release. However, those binaries are no longer available
> by the time postgresql knows they are needed, because apt is likely to
> delete the old package before installing the new one. 6.5.3-18 and later
> handle this by saving the binaries in their prerm. However slink does not
-19 preinst could handle that. When preinst is run, the old binaries are still
there, sou you can save them to /usr/lib/postgresql/??/6.3 .
> have this feature, and it is too late to introduce it. This is likely
> to lead to upgrade problems from slink to potato.
yes, but upgrading a database is usually done by someone who understands it
> Proposed solution: postgresql must depend on a package that contains only
> the old binaries. These will have to be collected for each architecture
> and the package will contain uuencoded versions. This package will
eww
> be called postgresql-slink. In view of library changes from slink to
> potato, I will probably have to build this on a potato system from 6.3.2
> source; alternatively, it will have dependencies on the slink library
> versions (is that feasible?).
yes, but you still have problems. that there will be installed newer glibc and
libpgsql2, no?
> The postinst of postgresql will look for binaries presaved by the old
> package. If it does not find them, it will look for a uuencoded version
> from postgresql-slink. If it doesn't find those, it will try to use ones
postgres should be static then, it depends on quite a few libraries
> copied by the preinst.
>
> This expedient will be used only for slink to potato upgrading.
> postgresql 6.5.3-19 will depend on postgresql-slink. postgresql 7.0-final-1
> and later will not.
>
> Comments please.
save in preinst of postgresql, libpgsql2
Petr Cech
--
Debian GNU/Linux maintainer - www.debian.{org,cz}
cech@atrey.karlin.mff.cuni.cz
<sgore> We Are Debian. You Will Be Packaged. Media Opinion Is Irrelevant.
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: