Number of commits found: 19

databases/ip4r: Update to 2.4.1

This fixes the build with newer PostgreSQL versions.

Drop the IDXPATCH option.  The patch no longer applies.  Unfortunately
it was never upstreamed, its purpose is not clear, and the port no
longer has a maintainer to ask about this.

Changes:	https://github.com/RhodiumToad/ip4r/blob/2.4.1/README.ip4r
PR:		239514

Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.

PR:		238330

Return tobez@'s ports to the pool after his commit bit was safekept.

Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.

PR:		231590

Workaround the following problem on aarch64 by setting LLD_UNSAFE=yes:

  cc: error: invalid linker name in argument '-fuse-ld=bfd'

Neither emaste nor I can figure out exactly where the offending stanza is
coming in.  It will take someone with more knowledge of gmake debug flags,
and possibly the src build infrastructure, to figure it out.

While here, pet portlint.

Approved by:	portmgr (tier-2 blanket)

databases/ip4r: update 2.0 -> 2.2

- moved to github
- set LICENSE

PR:		219766
Changes:	https://github.com/RhodiumToad/ip4r
Submitted by:	Jov <amutu@amutu.com>
Approved by:	tobez (maintainer timeout)

databases/ip4r: patch to prefer ip4r indexes over seq_scan on large datasets

- add option to prefer ip4r indexes over seq_scan on large datasets

PR:		190104
Submitted by:	michelle@sorbs.net
Approved by:	maintainer (timeout)

Convert to USES=pgsql

While here:
databases/pg_reorg
- stagify

databases/iplike
- convert to USES=libtool
- strip binarie

databases/ip4r
- strip binaries

databases/postgresql-libpgeasy
- convert to USES=libtool
- strip binaries
- stagify

databases/postgresql-libpqxx
- convert to USES=libtool
- strip binaries

databases/postgresql-libpqxx3
- convert to USES=libtool
- strip binaries

Update to 2.0 and take over maintainership.

Add NO_STAGE all over the place in preparation for the staging support (cat:
databases)

- Update to 1.05

PR:             155272
Submitted by:   Ruslan Mahmatkhanov <cvs-src@yandex.ru>

Mark as broken on sparc64-6.

Maintainer has turned in his commit bit.

Hat:    portmgr

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)

Update to 1.03

Update to 1.01 for pgsql 8.2.x support

Change all bogus uses of BROKEN to IGNORE.  See CHANGES 20060705.

PR:             ports/92445
Hat:            portmgr

Set default pgsql version to 8.1.x, since the port doesn't work with
the packaging default of 7.4.x

IP4R is a contributed PostgreSQL module that embraces and extends the
existing 'inet' and 'cidr' built-in types, providing extra functionality
and simplicity to IPv4 address lookup within large-scale environments.

Number of commits found: 19

13 vulnerabilities affecting 78 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities

Last updated:
2019-12-06 20:23:44