The failure, I think, it because of the newline patch we got for psql yesterday. I am seeking a diff from pgcrypto to fix it. My openssl is too old.
--------------------------------------------------------------------------- Dave Page wrote: > > > > -----Original Message----- > > From: Marko Kreen [mailto:[EMAIL PROTECTED] > > Sent: 10 February 2006 15:07 > > To: Dave Page > > Cc: pgsql-hackers@postgresql.org > > Subject: Re: [HACKERS] FW: PGBuildfarm member snake Branch > > HEAD Status changed from OK to ContribCheck failure > > > > On 2/10/06, Dave Page <dpage@vale-housing.co.uk> wrote: > > > Something broke snake again :-(. Looks like tsearch2 > > through the haze of > > > my Lemsip... I hate winter :-( > > > > AFAIR the reason for different length of psql's '----' header lines > > was database encoding being UNICODE not SQL_ASCII. Can this > > be the case > > there? > > Oh, didn't spot those (barely functioning at all today though!). > > No-one has even logged into Snake for a week or more though, so I would > still suspect a source change as the culprit. > > Regards, Dave. > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
