[Pgbuildfarm-members] release 2.12 of client code

Now available.

See http://pgfoundry.org/frs/?group_id=1000040

Changes:
. don't send log tar if the failure is from CVS stage - the files would be
from an earlier run.

. report changed files for forced run

. Add "use warnings"

. add NO_LOCALE flag for check target - still issues on postgres side ;-(

. add db logfile extract to stop/start logs

. minor bug fixes

. add update_personality.pl script

cheers

andrew

How much of this is just config file changes?

It would be easier for upgrades if there was a stock distribution config
that had good defaults that were then over-ridden by site-specific
settings as needed. That way, config changes wouldn't need to be
manually added to existing installs.

On Thu, Dec 29, 2005 at 12:31:49PM -0600, Andrew Dunstan wrote:
>
>
> Now available.
>
> See http://pgfoundry.org/frs/?group_id=1000040
>
>
> Changes:
> . don't send log tar if the failure is from CVS stage - the files would be
> from an earlier run.
>
> . report changed files for forced run
>
> . Add "use warnings"
>
> . add NO_LOCALE flag for check target - still issues on postgres side ;-(
>
> . add db logfile extract to stop/start logs
>
> . minor bug fixes
>
> . add update_personality.pl script
>
>
> cheers
>
> andrew
>
>
> _______________________________________________
> Pgbuildfarm-members mailing list
> Pgbuildfarm-members(at)pgfoundry(dot)org
> http://pgfoundry.org/mailman/listinfo/pgbuildfarm-members
>

--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

None of it. I try to avoid the need for config file upgrades where
possible. If it is needed, I will mention it in the release note. Maybe
I should also mention if a config file upgrade is not necessary.

cheers

andrew

Jim C. Nasby wrote:

>How much of this is just config file changes?
>
>It would be easier for upgrades if there was a stock distribution config
>that had good defaults that were then over-ridden by site-specific
>settings as needed. That way, config changes wouldn't need to be
>manually added to existing installs.
>
>On Thu, Dec 29, 2005 at 12:31:49PM -0600, Andrew Dunstan wrote:
>
>
>>Now available.
>>
>>See http://pgfoundry.org/frs/?group_id=1000040
>>
>>
>>Changes:
>>. don't send log tar if the failure is from CVS stage - the files would be
>>from an earlier run.
>>
>>. report changed files for forced run
>>
>>. Add "use warnings"
>>
>>. add NO_LOCALE flag for check target - still issues on postgres side ;-(
>>
>>. add db logfile extract to stop/start logs
>>
>>. minor bug fixes
>>
>>. add update_personality.pl script
>>
>>
>>cheers
>>
>>andrew
>>
>>
>>_______________________________________________
>>Pgbuildfarm-members mailing list
>>Pgbuildfarm-members(at)pgfoundry(dot)org
>>http://pgfoundry.org/mailman/listinfo/pgbuildfarm-members
>>
>>
>>
>
>
>