New buildfarm member Narwhal is failing the PL regression tests for
Python on REL8_1_STABLE. This appears to be because it's running Python
2.5 (the causes being a deprecated module - whrandom - and some changed
messages).
The former problem was fixed by Peter, and the latter by Tom but both
On 4/17/07, Dave Page [EMAIL PROTECTED] wrote:
New buildfarm member Narwhal is failing the PL regression tests for
Python on REL8_1_STABLE. This appears to be because it's running Python
2.5 (the causes being a deprecated module - whrandom - and some changed
messages).
I also suggest
Tom Lane wrote:
Dave Page [EMAIL PROTECTED] writes:
Andrew Dunstan wrote:
The question in my mind is this: how much do we back-patch to cover new
and incompatible releases of software we depend on?
I guess that depends on the invasiveness - in this case it's a couple of
simple updates to
Dave Page [EMAIL PROTECTED] writes:
Andrew Dunstan wrote:
The question in my mind is this: how much do we back-patch to cover new
and incompatible releases of software we depend on?
I guess that depends on the invasiveness - in this case it's a couple of
simple updates to the regression
Dave Page wrote:
New buildfarm member Narwhal is failing the PL regression tests for
Python on REL8_1_STABLE. This appears to be because it's running
Python 2.5 (the causes being a deprecated module - whrandom - and some
changed messages).
The former problem was fixed by Peter, and the
Andrew Dunstan wrote:
The question in my mind is this: how much do we back-patch to cover new
and incompatible releases of software we depend on? Python 2.5 was
released on 19 Sept 2006, long after Postgres 8.1. I guess you could
make a case to say that we should back-patch to the release