Garbage collect expired ports
2011-04-01 accessibility/linux-f8-atk: End of Life since Jan 7, 2009
2011-04-01 archivers/linux-f8-ucl: End of Life since Jan 7, 2009
2011-04-01 archivers/linux-f8-upx: End of Life since Jan 7, 2009
2011-04-01 audio/linux-f8-alsa-lib: End of Life since Jan 7, 2009
2011-04-01 audio/linux-f8-arts: End of Life since Jan 7, 2009
2011-04-01 audio/linux-f8-esound: End of Life since Jan 7, 2009
2011-04-01 audio/linux-f8-freealut: End of Life since Jan 7, 2009
2011-04-01 audio/linux-f8-libaudiofile: End of Life since Jan 7, 2009
2011-04-01 audio/linux-f8-libogg: End of Life since Jan 7, 2009
2011-04-01 audio/linux-f8-libvorbis: End of Life since Jan 7, 2009
2011-04-01 audio/linux-f8-mikmod: End of Life since Jan 7, 2009
2011-04-01 audio/linux-f8-nas-libs: End of Life since Jan 7, 2009
2011-04-01 audio/linux-f8-openal: End of Life since Jan 7, 2009
2011-04-01 audio/linux-f8-sdl_mixer: End of Life since Jan 7, 2009

- Get Rid MD5 support

Expire old versions of PostgreSQL @ 2011-04-02

PR:             ports/153312, ports/153313, ports/153314
Feature safe:   yes
Approved by:    portmgr

Fix @dirrmtry since it already filter stderr and return true

PR:             ports/153890
Submitted by:   az@
Approved by:    maintainer (timeout)
Feature safe:   yes

- Fix optional dependency on security/heimdal
- Bump PORTREVISION
PR:             ports/152029
Submitted by:   Joerg Pulz [Joerg.Pulz frm2.tum.de]
Approved by:    Ryan Steinmetz <rpsfa@rit.edu> (maintainer of net/freeradius*)
                girgen (maintainer of databases/postgresql*-server,
                        14 day timeout)

Update all PostgreSQL ports to latest versions.

Also, try to break the previous 1:1 relation between FreeBSD system and
PostgreSQL versions installed. Use different PREFIX:es to install
different versions on the same system.

PR: ports/132402, ports/145002, ports/146657

BROKEN should not be quoted.
No functional change.

Bounce PORTREVISION for gettext-related ports.  Have fun, ya'll.

Update all PostgreSQL ports to latest version.

Remove postgresql-contrib in favour for postgresqlNN-contrib.
This way we will get packages built, which is nice.

Security:       CVE-2010-1169
Security:       CVE-2010-1170

The PostgreSQL Project today released minor versions updating all active
branches of the PostgreSQL object-relational database system, including
versions 8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25, and 7.4.29. This release
fixes moderate-risk security issues with PL/perl and PL/tcl, as well as
a data corruption issue with standby databases.  Users of any of these
three features should update their PostgreSQL installations immediately.

Begin the process of deprecating sysutils/rc_subr by
s#. %%RC_SUBR%%#. /etc/rc.subr#

Fix a few "bad example" problems in the rc.d scripts that have been
propogated by copy and paste.

1. Primarily the "empty variable" default assignment, which is mostly
${name}_flags="", but fix a few others as well.
2. Where they are not already documented, add the existence of the _flags
(or other deleted empties) option to the comments, and in some cases add
comments from scratch.
3. Replace things that look like:
prefix=%%PREFIX%%
command=${prefix}/sbin/foo
to just use %%PREFIX%%. In many cases the $prefix variable is only used
once, and in some cases it is not used at all.
4. In a few cases remove ${name}_flags from command_args
5. Remove a long-stale comment about putting the port's rc.d script in
/etc/rc.d (which is no longer necessary).

No PORTREVISION bumps because all of these changes are noops.

Update PostgreSQL to latest versions.

The PostgreSQL Project today released minor versions updating all active
branches of the PostgreSQL object-relational database system, including
versions 8.3.7, 8.2.13, 8.1.17, 8.0.21 and 7.4.25. This release fixes a denial
of service issue with encoding conversion, and all users should update their
installations at the next reasonable opportunity.

There are 12 other minor fixes contained in these update releases, including
fixes for xpath() functions in version 8.3. See the release notes for full
details.

URL: http://www.postgresql.org/docs/8.3/static/release-8-3-7.html
URL: http://www.postgresql.org/docs/8.2/static/release-8-2-13.html
URL: http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-17
URL: http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-21
URL: http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-24

Update PostgreSQL to latest versions.

URL: http://www.postgresql.org/about/news.1055

The PostgreSQL Project today released
updates to all active branches of the
PostgreSQL object-relational database
system, including versions 8.3.6,
8.2.12, 8.1.16, 8.0.20 and 7.4.24. These
updates include two serious fixes, for
autovacuum crashes in version 8.1 and
GiST indexing data loss in 8.3, and
those two versions should be updated as
soon as possible.

Update PostgreSQL to latest versions.

http://www.postgresql.org/docs/current/static/release-8-3-5.html
http://www.postgresql.org/docs/current/static/release-8-2-11.html
http://www.postgresql.org/docs/current/static/release-8-1-15.html
http://www.postgresql.org/docs/current/static/release-8-0-19.html
http://www.postgresql.org/docs/current/static/release-7-4-23.html

Note that the GiST problem mentioned does not apply to users of
the FreeBSD port, since the previous version of PostgreSQL never
reached the ports tree, due to the freeze of the tree pending the
FreeBSD 7.1 update.

PR:     121848, 124713

Updates of the PostgreSQL ports

Updates for all maintained versions of PostgreSQL are available today:
8.3.3, 8.2.9, 8.1.13, 8.0.17 and 7.4.21.  These releases fix more than
two dozen minor issues reported and patched over the last few months.
All PostgreSQL users should plan to update at their earliest
convenience. People in affected time zones, in particular, should
upgrade as soon as possible.

Release Notes:
        http://www.postgresql.org/docs/8.3/static/release.html

Also, fix umask error in periodic script [1].

PR:             ports/124457 [1]
Submitted by:   Alexandre Perrin

Bump portrevision due to upgrade of devel/gettext.

The affected ports are the ones with gettext as a run-dependency
according to ports/INDEX-7 (5007 of them) and the ones with USE_GETTEXT
in Makefile (29 of them).

PR:             ports/124340
Submitted by:   edwin@
Approved by:    portmgr (pav)

- Remove USE_GETOPT_LONG which is a no-op since March 200

Fix bad distinfo sizes

Update all PostgreSQL ports to latest versions.

This includes a bunch of security fixes: CVE-2007-6067, CVE-2007-4772,
CVE-2007-6601, CVE-2007-6600 and CVE-2007-4769.

Security: http://www.postgresql.org/about/news.905

Migration from bison 1.x to 2.x

PR:             117086
Tested by:      -exp runs

Update PostgreSQL ports to the latest patch releases.

PR: ports/104075

- Accept --infodir argument in configure script so it won't fail when we
  set --mandir and --infodir in bsd.port.mk for GNU_CONFIGURE

PR:             ports/111470
Approved by:    portmgr
Tested by:      pointyhat exp run

- Welcome X.org 7.2 \o/.
- Set X11BASE to ${LOCALBASE} for recent ${OSVERSION}.
- Bump PORTREVISION for ports intalling files in ${X11BASE}.

Update PostgreSQL to 7.3.19, 7.4.17, 8.0.13, 8.1.9 and 8.2.4 respectively:

 The PostgreSQL Global Development Group has released updated versions
 for PostgreSQL 8.2 and all back versions to patch a privilege
 escalation exploit in SECURITY DEFINER functions.  All users of this
 feature are urged to update to the latest minor version and follow
 instructions on securing these functions as soon as possible.  This
 minor release also contains other fixes, so all users should plan to
 deploy it.

 Once you have updated, additional steps are required to secure your
 database against the exploit.  Please read the release notes at
 http://www.postgresql.org/docs/8.2/static/release.html and the
 TechDocs article at http://www.postgresql.org/docs/techdocs.77 on how
 to lock down your security definer functions, if you use them.

Update PostgreSQL with, amongst other things, a security fix:

  A vulnerability allows suppressing the normal checks that a SQL
  function returns the data type it's declared to do. These errors can
  easily be exploited to cause a backend crash, and in principle might
  be used to read database content that the user should not be able to
  access. [CVE-2007-0555]

The release includes a set of other fixes as well. Please see the
release information at
http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-16

Security: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0555

Add missing pg_id and bump PORTREVISION.

Reported by: Stefan Foulis

Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17.

Release notes:
http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17
http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15
http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10
http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6
http://www.postgresql.org/docs/8.2/static/release-8-2-1.html

The server-side utilities of postgresql (initdb, initlocation,
ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now
installed by the respective postgresql*-server port (previously they
where installed with the client). If you update the client, you should
also update the server to make sure you are not left without the
server-side tools. Do something like:

    portupgrade postgresql-client postgresql-server

Update PostgreSQL to latest versions: 8.1.5, 8.0.9, 7.4.14 and 7.3.16.

Release notes:
8.1.5  http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-5
8.0.9  http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-9
7.4.14 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-14
7.3.16 http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-16

Change name of the rc script from '010.pgsql.sh' to 'postgresql'

Add optional hierachy patch added for 7.4 and 8.1 ports.

Chase heimdal libs update [reported by several]

For 8.1+ the port enables autovacuum in ~pgsql/postgresql.conf when
running initdb

Cleanup the ports, moving pkg-message-* to files/pkg-message-*.in and
files/pgsql.sh.tmpl to files/postgresql.in. [ports/97767]

PR: ports/97767, submitted by delphij@FreeBSD.org

There is no point in setting mode of rc.d file to be 554, set it to 555.
Otherwise there could be problems with the service not starting up in the
case when owner of the file has been changed.

Update all PostgreSQL to fix a security flaw

The PostgreSQL Global Development Group today released versions 8.1.4, 8.0.8,
7.4.13 and 7.3.15. This is an urgent update to close a security hole which
can permit a SQL injection attack on some applications running PostgreSQL.

Users are urged to apply the update as soon as reasonably possible. Since the
update affects client functionality, most driver projects will be updating
this week as well.

Because the security issue involved is complex, we have added a section in
Techdocs to explain it: http://www.postgresql.org/docs/techdocs.52. Please
read this first before applying the updates.

Also, fix rc_subr startup problems on FreeBSD-7.x.

Security:       http://www.postgresql.org/docs/techdocs.50
PR:             ports/95154

Remove the FreeBSD KEYWORD from all rc.d scripts where it appears.
We have not checked for this KEYWORD for a long time now, so this
is a complete noop, and thus no PORTREVISION bump. Removing it at
this point is mostly for pedantic reasons, and partly to avoid
perpetuating this anachronism by copy and paste to future scripts.

Security patch, update to version 7.4.12.

Security:       http://www.postgresql.org/docs/8.1/static/release-7-4-12.html

Add missing ) around SIZE statements.

eplace ugly "@unexec rmdir %D... 2>/dev/null || true" with @dirrmtry

Approved by:    krion@
PR:             ports/88711 (related)

Update postgresql with latest patch release.

A critical fix repairs an error in ReadBuffer that can cause data loss
due to overwriting recently-added pages.  This applies to the 8.1 and
8.0 branches on all platforms.

Note that this update might require a reindex of textual columns under
certain conditions; please see UPDATING.

Other fixes included are:
-- Character string locale comparison bug. This may require a REINDEX
    on text column indexes in some locales, such as Hungarian.
-- Prevent accidental changes of locale by plperl
-- Two fixes for Japanese encodings
-- Two fixes for COPY CSV
-- Fixes for functions returning RECORD
-- Fixes to autovacuum, dblink and pgcrypto

Handle a change in rc.subr. nowadays, "faststart" is used instead of
"start" when booting, since there's no need waste time checking for
running processes when the OS is starting up.

Bumping portrevision.

PR:             90884
Submitted by:   Victor Snezhko <snezhko@indorsoft.ru>

Update postgresql to 7.4.10

Submitted by:   Hirohisa Yamaguchi <umq@ueo.co.jp>
PR:             90445

Let postgresql (libpq.so) only link with the Kerberos implementations
installed from ports. The base heimdal distribution installs libraries
that have no depenency information. While this is quite correct, it
means that each library that links with libpq.so must also know if
libpq.so is linked with libkrb.so et al. Problem is, there's no good
way to get this information (pg_config has a --libs option starting at
version 8.1) and all ports using postgresql must be changed to make it
possible to link with a libpq.so that was configured to use the
Kerberos implementation installed in /usr by default. Hence, we
require one of the ports (heimdal or krb5) if postgresql is to be
linked with Kerberos. At least for now, until we can fix this in some
better way.

Also, if MIT Kerberos (security/krb5) is installed, users should
ideally remove the base heimdal installation so linkers will not pick
it up in preference to the krb5 libs (base heimdal has higher version
numbers than krb5 port).

PR: 80869, 88098, 85178

Upgrade to version 7.4.9

Migration to version 7.4.9

   A dump/restore is not required for those running 7.4.X. However, if you
   are upgrading from a version earlier than 7.4.8, see the release notes
   for 7.4.8.
     __________________________________________________________________

Changes

     * Fix error that allowed "VACUUM" to remove ctid chains too soon, and
       add more checking in code that follows ctid links
       This fixes a long-standing problem that could cause crashes in very
       rare circumstances.

Update PostgreSQL to latest versions.  For details on the fixes,
please see the HISTORY file included in the Release, but a summary
consists of:

      * Change encoding function signature to prevent misuse
      * Change "contrib/tsearch2" to avoid unsafe use of INTERNAL function
        results
      * Repair race condition between relation extension and VACUUM
        This could theoretically have caused loss of a page's worth of
        freshly-inserted data, although the scenario seems of very low
        probability. There are no known cases of it having caused more than
        an Assert failure.

Security:       http://www.postgresql.org/about/news.315

Modify 8.0's startup script to simulate a full login (su -l) [1]. Also
add support to select login class for running postgresql [2].

The new startup script, using rc.subr, is now installed for all
versions of postgresql. Bump portrevisions, since startup script is
modified.

PR:             78630 [1]
Submitted by:   Vivek Khera [1]
Submitted by:   Brian B. [2]
Approved by:    seanc (implicit)

Fixing problems with the recent security patch: When bison was not
installed, the patched gram.y file would not be used and the security
patch would be a no-op. Also, I've had reports of compilation errors
related to bison.

Since checking for the correct version of bison is hard and error
prone, I'm doing what the postgresql distribution does - patching the
yacc:ed .c file to get rid of the building dependency.

Bumping portrevision of -server.

Pointy hat to:  me
Noticed by:     Mike Harding and others
Security:      
http://www.vuxml.org/freebsd/6b4b0b3f-8127-11d9-a9e7-0001020eed82.html
Approved by:    seanc (implicit)

Fix security alert using a patch from PostgreSQL's CVS repository:

  Prevent overrunning a heap-allocated buffer if more than 1024
  parameters to a refcursor declaration are specified. This is a
  minimally-invasive fix for the buffer overrun.

Define LATEST_LINK to avoid package name clashes between the different
branches of PostgreSQL. [1] (Since postgresql-tcltk is hardwired to
branch 7.4, keep its LATEST_LINK to a generic value.)

Set UNIQUENAME and let it be the same for server & client, so each
branch's ports will share the same options file. This adds some no-op
knobs to the -client port, but IMO it is better this way.

Add space inside paranthesis in OSVERSION conditional to work around

Update JDBC support to version 8.0 (build 310).

The PostgreSQL JDBC project has been decoupled from the server
distribution, and is now hosted at http://jdbc.postgresql.org/.

Approved by:    ade (mentor)

Let pkg-message reflect the renaming of the startup script.

Submitted by: Nick Pavlica <linicks at gmail dot com>
Approved by: ade (mentor)

local/java/classes is part of mtree, so don't remove when
deinstalling.

Approved by: ade (mentor)

In order to address a potential security hole recently identified with
the "LOAD" option, the PostgreSQL Global Development Group is
announcing the release of new versions of PostgreSQL.

Update to 7.3.9, 7.4.7 & 8.0.1.

Take the opportunity to reset PORTREVISION of slave ports.

Back out name change of startup script. The new script uses rc.subr(8),
and as such also uses rcorder(8). But, rcorder does not exist in FreeBSD
4.x. Hence rename the script it back to the top of the directory
list. [1]

The periodic script should of course be executable. [2]

[1] Noted by Niels Chr. Bank-Pedersen <ncbp at bank-pedersen dot dk>
[2] Noted by Fritz Heinrichmeyer <fritz.heinrichmeyer at fernuni-hagen dot de>

Split the postgresql ports into a server and a client part. The
following knobs can be used by ports depending on PostgreSQL:

# USE_PGSQL     - Add PostgreSQL client dependency.
#                 If no version is given (by the maintainer via the port or
#                 by the user via defined variable), try to find the
#                 currently installed version.  Fall back to default if
#                 necessary (PostgreSQL-7.4 = 74).
# DEFAULT_PGSQL_VER
#               - PostgreSQL default version. Can be overridden within a port.
#                 Default: 74.
# WANT_PGSQL_VER
#               - Maintainer can set an arbitrary version of PostgreSQL by
#                 using it.
# BROKEN_WITH_PGSQL

PR ports/75344 - This needs testing and an probably experimental
build, so it will not be out the door before the ports freeze.
Meanwhile, modify BROKEN text to something more informative.

Approved by: ade (mentor)

Add myself as committer, and use my @FreeBSD.org address.

Approved by: ade (mentor)

Another step along the road to the postgresql new world order.

Note that none of these ports are (yet) hooked into the tree,
and will not compile unless you set a specific environmental
variable.  This should be warning enough to leave well alone
for now :)

Submitted by:   maintainer