Re: wrap alpha4 tomorrow ~9am Eastern (was: Alpha4 release blockers)

On Tue, Mar 8, 2011 at 12:00 PM, Robert Haas <robertmhaas@gmail.com> wrote:

Going once, going twice...

I'll go ahead and do this, barring objections or some other volunteer.

developer.postgresql.org apparently hates me. After waiting an
insanely long time to copy over the exported tarball to that machine,
I tried to follow the instructions at
http://wiki.postgresql.org/wiki/Alpha_release_process but of course it
didn't work:

$ src/tools/version_stamp.pl alpha4
Stamped these files with version number 9.1alpha4:
configure.in
doc/bug.template
src/include/pg_config.h.win32
src/interfaces/libpq/libpq.rc.in
src/port/win32ver.rc
Don't forget to run autoconf 2.63 before committing.
$ autoconf --version
autoconf (GNU Autoconf) 2.62
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later
<http://gnu.org/licenses/old-licenses/gpl-2.0.html&gt;
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David J. MacKenzie and Akim Demaille.
$ autoconf
configure.in:22: error: Autoconf version 2.63 is required.
Untested combinations of 'autoconf' and PostgreSQL versions are not
recommended. You can remove the check from 'configure.in' but it is then
your responsibility whether the result works or not.
configure.in:22: the top level
autom4te-2.62: /usr/local/bin/gm4 failed with exit status: 1

As Magnus pointed out to me on IM, there must be a usable version of
autoconf on this machine somewhere if it's doing the nightly snapshot
builds, but beats me where it is. Help?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Due to backbranch packaging, and having to support several different
versions of autoconf as a results, its a bit more confusing ...

'k, normally it would be in /usr/local/bin:

developer# ls -lt autoconf-*
-r-xr-xr-x 1 root wheel 14657 Aug 13 2009 autoconf-2.62
-r-xr-xr-x 1 root wheel 13420 Aug 26 2007 autoconf-2.61
-r-xr-xr-x 1 root wheel 5009 Aug 16 2007 autoconf-2.13
-r-xr-xr-x 1 root wheel 7674 Aug 16 2007 autoconf-2.59
-r-xr-xr-x 1 root wheel 6196 Aug 16 2007 autoconf-2.53

But, since they seem to have 'skipped' 2.63 in FreeBSD for some reason
(current version in ports is 2.68), 2.63 had to be manually installed
seperately from ports:

developer# /root/bin/autoconf --version
autoconf (GNU Autoconf) 2.63
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later
<http://gnu.org/licenses/old-licenses/gpl-2.0.html&gt;
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David J. MacKenzie and Akim Demaille.

Sorry for the confusion on that ...

On Wed, 9 Mar 2011, Robert Haas wrote:

On Tue, Mar 8, 2011 at 12:00 PM, Robert Haas <robertmhaas@gmail.com> wrote:

Going once, going twice...

I'll go ahead and do this, barring objections or some other volunteer.

developer.postgresql.org apparently hates me. After waiting an
insanely long time to copy over the exported tarball to that machine,
I tried to follow the instructions at
http://wiki.postgresql.org/wiki/Alpha_release_process but of course it
didn't work:

$ src/tools/version_stamp.pl alpha4
Stamped these files with version number 9.1alpha4:
configure.in
doc/bug.template
src/include/pg_config.h.win32
src/interfaces/libpq/libpq.rc.in
src/port/win32ver.rc
Don't forget to run autoconf 2.63 before committing.
$ autoconf --version
autoconf (GNU Autoconf) 2.62
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later
<http://gnu.org/licenses/old-licenses/gpl-2.0.html&gt;
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David J. MacKenzie and Akim Demaille.
$ autoconf
configure.in:22: error: Autoconf version 2.63 is required.
Untested combinations of 'autoconf' and PostgreSQL versions are not
recommended. You can remove the check from 'configure.in' but it is then
your responsibility whether the result works or not.
configure.in:22: the top level
autom4te-2.62: /usr/local/bin/gm4 failed with exit status: 1

As Magnus pointed out to me on IM, there must be a usable version of
autoconf on this machine somewhere if it's doing the nightly snapshot
builds, but beats me where it is. Help?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

----
Marc G. Fournier Hub.Org Hosting Solutions S.A.
scrappy@hub.org http://www.hub.org

Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org

On ons, 2011-03-09 at 10:12 -0500, Robert Haas wrote:

developer.postgresql.org apparently hates me. After waiting an
insanely long time to copy over the exported tarball to that machine,

I run the export on d.p.o.

As Magnus pointed out to me on IM, there must be a usable version of
autoconf on this machine somewhere if it's doing the nightly snapshot
builds, but beats me where it is. Help?

The snapshot doesn't need autoconf, but there is an installation in
~petere/sw/ac263/ that you can use.

On Wed, Mar 9, 2011 at 10:35 AM, Peter Eisentraut <peter_e@gmx.net> wrote:

On ons, 2011-03-09 at 10:12 -0500, Robert Haas wrote:

developer.postgresql.org apparently hates me.  After waiting an
insanely long time to copy over the exported tarball to that machine,

I run the export on d.p.o.

I can see why, but I didn't have a git clone on that machine.

As Magnus pointed out to me on IM, there must be a usable version of
autoconf on this machine somewhere if it's doing the nightly snapshot
builds, but beats me where it is.  Help?

The snapshot doesn't need autoconf, but there is an installation in
~petere/sw/ac263/ that you can use.

OK, thanks. Running make distcheck now.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

On Wed, Mar 9, 2011 at 10:43 AM, Robert Haas <robertmhaas@gmail.com> wrote:

On Wed, Mar 9, 2011 at 10:35 AM, Peter Eisentraut <peter_e@gmx.net> wrote:

On ons, 2011-03-09 at 10:12 -0500, Robert Haas wrote:

developer.postgresql.org apparently hates me.  After waiting an
insanely long time to copy over the exported tarball to that machine,

I run the export on d.p.o.

I can see why, but I didn't have a git clone on that machine.

As Magnus pointed out to me on IM, there must be a usable version of
autoconf on this machine somewhere if it's doing the nightly snapshot
builds, but beats me where it is.  Help?

The snapshot doesn't need autoconf, but there is an installation in
~petere/sw/ac263/ that you can use.

OK, thanks.  Running make distcheck now.

And done.

Files now up at:

http://developer.postgresql.org/~rhaas/

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Robert Haas <robertmhaas@gmail.com> wrote:

Files now up at:

http://developer.postgresql.org/~rhaas/

As an initial sanity test I downloaded the bz2 version and its md5
file. The md5sum checked out and this all ran as expected:

tar -xjf postgresql-9.1alpha4.tar.bz2
cd postgresql-9.1alpha4/
./configure --prefix=/usr/local/pgsql-9.1alpha4 \
--enable-debug \
--enable-cassert \
--enable-depend
make world
make check-world
pushd src/test/isolation/ ; make check ; popd

-Kevin

On Wed, Mar 9, 2011 at 12:30 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:

Robert Haas <robertmhaas@gmail.com> wrote:

Files now up at:

http://developer.postgresql.org/~rhaas/

As an initial sanity test I downloaded the bz2 version and its md5
file.  The md5sum checked out and this all ran as expected:

tar -xjf postgresql-9.1alpha4.tar.bz2
cd postgresql-9.1alpha4/
./configure --prefix=/usr/local/pgsql-9.1alpha4 \
           --enable-debug \
           --enable-cassert \
           --enable-depend
make world
make check-world
pushd src/test/isolation/ ; make check ; popd

Thanks. I copied the files to ~ftp/pub/source/9.1alpha4 on
developer.postgresql.org also, along side the existing 9.1alpha{1,2,3}
directories, but I'm fuzzy on how it all gets pushed out to wwwmaster
and the mirror network.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

On Wed, Mar 9, 2011 at 18:53, Robert Haas <robertmhaas@gmail.com> wrote:

On Wed, Mar 9, 2011 at 12:30 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:

Robert Haas <robertmhaas@gmail.com> wrote:

Files now up at:

http://developer.postgresql.org/~rhaas/

As an initial sanity test I downloaded the bz2 version and its md5
file.  The md5sum checked out and this all ran as expected:

tar -xjf postgresql-9.1alpha4.tar.bz2
cd postgresql-9.1alpha4/
./configure --prefix=/usr/local/pgsql-9.1alpha4 \
           --enable-debug \
           --enable-cassert \
           --enable-depend
make world
make check-world
pushd src/test/isolation/ ; make check ; popd

Thanks.  I copied the files to ~ftp/pub/source/9.1alpha4 on
developer.postgresql.org also, along side the existing 9.1alpha{1,2,3}
directories, but I'm fuzzy on how it all gets pushed out to wwwmaster
and the mirror network.

Time will take care of that for you. You just have a coffee and wait...

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

On Wed, Mar 9, 2011 at 12:56 PM, Magnus Hagander <magnus@hagander.net> wrote:

Time will take care of that for you. You just have a coffee and wait...

Time seems to have done the trick (though my coffee would be getting
cold by now). I now see it at:

http://www.postgresql.org/ftp/source/v9.1alpha4/

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Robert,

Should I write the announcement for this, or do you want to?

--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com

On Wed, Mar 9, 2011 at 11:04 PM, Josh Berkus <josh@agliodbs.com> wrote:

Should I write the announcement for this, or do you want to?

For alpha4? I'd be happy for you to do it, but it's a bit out of date
now. I was thinking to bundle alpha5 on Monday; maybe we should just
wait and announce that one.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company