Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <000701c1c073$51a319a0$6fc82486@medschool.dundee.ac.uk> Reply-To: "Fergus Daly" From: "Fergus Daly" To: Cc: Subject: Re: Updated: postgresql-7.2-2 Date: Thu, 28 Feb 2002 16:16:46 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 On his announcement of the updated postgresql-7.2.2, Jason Tishler wrote : >> WARNING WARNING WARNING WARNING WARNING >> Note that this distribution will *not* function correctly with Cygwin >> 1.3.9-1. If you want to use this distribution, then you *must* upgrade >> your Cygwin DLL to a recent snapshot (i.e., 2002-Feb-10 or later) >> or to the next release after 1.3.9-1 (when available). >> WARNING WARNING WARNING WARNING WARNING Now that the Cygwin DLL has advanced from 1.3.9-1 to 1.3.10-1 does this mean it's OK to reinstate postgresql-7.2.2? If it is, do we do it ourselves by an explicit intervention using setup.ini, or will setup.ini "see to it" for us (at some stage). This is not a nag (as in "1.3.9 -> 1.3.10 happened just now, so what's happening about postgresql, then?"), or it's not meant to be anyway : I ask because although I think I know how to manage this for myself, I really don't know whether I should. Fergus -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/