<tt><br /> In about a week I propose to have the buildfarm server start to reject results based on snapshots where the
newestfile is older than the time of the git migration a week ago. That means buildfarm owners need to upgrade to using
git.Many have already: see <a class="moz-txt-link-rfc2396E"
href="http://www.pgbuildfarm.org/cgi-bin/show_status.pl"><http://www.pgbuildfarm.org/cgi-bin/show_status.pl></a><br
/><br/> The move to git has been a long advertised change, and the software updates have been available for months.
Justto be clear, here are the steps involved in upgrading a buildfarm client:<br /><br /></tt><ul><li>install git on
yourmachine if it's not there already - latest version is best, but most moderately modern versions should do.<br
/><li>upgradeto the latest release of the buildfarm code (release 4.1) See <a class="moz-txt-link-rfc2396E"
href="http://pgfoundry.org/frs/?group_id=1000040"><http://pgfoundry.org/frs/?group_id=1000040></a><br/><li>remove
therepo copies in your buildroot ("rm -rf /path/to/buildroot/*/pgsql")<li>update the buildfarm.conf. At a minimum,
removethe settings for cvsmethod and cvsrepo and add setting "scm => 'git'". But you probably want a local git
mirrorrather than a separate clone for each branch. See <br /><a class="moz-txt-link-rfc2396E"
href="http://wiki.postgresql.org/wiki/PostgreSQL_Buildfarm_Howto"><http://wiki.postgresql.org/wiki/PostgreSQL_Buildfarm_Howto></a>
formore details<br /></ul> That's not exactly hard, on most platforms.<br /><br /> If you think you deserve a
dispensation,please ask me, but I really don't want the buildfarm server polluted with new builds of frozen code. That
doesn'thelp anyone - it's just useless noise.<br /><br /><br /> cheers<br /><br /> andrew<br />