From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Dave Page <dpage(at)postgresql(dot)org> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Buildfarm member Narwhal: Python 2.5/8.1 |
Date: | 2007-04-17 13:43:34 |
Message-ID: | 4624CF06.4080906@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 latter by Tom but both
> only for 8.2+`- any reason this wasn't backported to 8.1? I couldn't
> find anything in the archives.
>
> http://www.pgbuildfarm.org/cgi-bin/show_stage_log.pl?nm=narwhal&dt=2007-04-17%20085153&stg=pl-install-check
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 immediately
before the library change.
(BTW, it is possible to include python only in certain branches in your
buildfarm client - examples are in the config file).
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2007-04-17 13:56:48 | Re: Buildfarm member Narwhal: Python 2.5/8.1 |
Previous Message | Marko Kreen | 2007-04-17 13:34:00 | Re: RESET command seems pretty disjointed now |