Both sqlparse and six are mentioned as dependencies, but are missing in
the ports RUN_DEPENDS.
The missing sqlparse dependencies causes (at least) devel/buildbot to
generate an error at run-time [1].
This change adds sqlparse and six to RUN_DEPENDS.
While I'm here:
- Add LICENSE_FILE
- Update RUN_DEPENDS version specs to match upstream files (NOOP)
- Enable "concurrent" Python version installation
- Add NO_ARCH (architecture independent)
PR: 215273 [1]
Reported by: Nikola Kolev <koue chaosophia net>
Approved by: portmgr (blanket)
MFH: 2016Q4
- Fix PLIST
- Bump PORTREVISION for package change
Note that postgresql-client was already brought in via USES=pgsql.
Therefore the equivalent WANT_PGSQL is "lib server".
Approved by: portmgr (blanket)
- Enable RASTER by default
- Fix PLIST
- Bump PORTREVISION for package change
====> Running Q/A tests (stage-qa)
Error: /usr/local/bin/pgsql2shp is linked to /usr/local/lib/libpq.so.5 from databases/postgresql96-client but it is not declared as a dependency
Warning: you need USES+=pgsql
2016-08-20 databases/py-sqlalchemy06: Upstream has declared this version EoL: please migrate to databases/py-sqlalchemy10
2016-05-02 print/py-reportlab2: no longer supported - use reportlab 3.x (py-reportlab) instead
2016-12-08 devel/py-itools: Depends on broken and expired py-reportlab2
2016-12-08 graphics/py-aafigure: Depends on broken and expired py-reportlab2
2016-12-08 converters/py-pisa: Deprecated upstream, depends on broken and expired py-reportlab2
memcached is a high-performance, distributed memory object caching
system, generic in nature, but intended for use in speeding up dynamic
web applications by alleviating database load.
This extension uses the libmemcached library to provide the API for
communicating with memcached servers.
WWW: http://pecl.php.net/package/memcached
PR: 208049
Submitted by: townwear@gmail.com
lang/gcc which have moved from GCC 4.8.5 to GCC 4.9.4 (at least under some
circumstances such as versions of FreeBSD or platforms), part II.
The first part covered ports with USE_GCC=yes, USE_GCC=any, or one of
gcc-c++11-lib, openmp, nestedfct, c++11-lib as well as c++14-lang,
c++11-lang, c++0x, c11 requested via USES=compiler.
This adds ports with USES=fortran and ports using Mk/bsd.octave.mk
which in turn has USES=fortran.
PR: 214965
Reported by: thierry
<ChangeLog>
Upgrade urgency LOW: This release mainly fixes a rare GEO API bug and a crash
related to the modules subsystem.
Redis 4.0.0-RC2 (version number 3.9.102) just fixes two bugs:
1. GEORADIUS could fail reporting items with very big radius lengths because
of a bug in the bounding box computation function. This was fixed and tests
with large radius sizes were added.
2. There was a crash in the modules subsystem that was not merged into RC1 for
an error, while it was already fixed into the "unstable" branch.
</ChangeLog>
<ChangeLog>
Upgrade urgency MODERATE: GEORADIUS, BITFIELD and Redis Cluster minor fixes.
This release mainly fixes three bugs:
1. A bug with BITFIELD that may cause the bitmap corruption when setting offsets
larger than the current string size.
2. A GEORADIUS bug that may happen when using very large radius lengths, in
the range of 10000km or alike, due to wrong bounding box calculation.
3. A bug with Redis Cluster which crashes when reading a nodes configuration
file with zero bytes at the end, which sometimes happens with certain ext4
configurations after a system crash.
</ChangeLog>
<ChangeLog>
Upgrade urgency LOW: This release only fixes a compilation issue due to the
missing -ldl at linking time.
zach shipko in commit 4736407:
BSDs don't have -ldl
1 file changed, 15 insertions(+), 5 deletions(-)
antirez in commit 9ada818:
Fix modules compilation when libc malloc is used.
1 file changed, 2 insertions(+), 2 deletions(-)
</ChangeLog>
- Fix in CegoFieldValue for fixed value handling.
In case of fixed value aggregations, the specified fixed dimension
should be kept. This has been done be analysing the value dimension
in the CegoFieldValue:add/sub/mu/div methods.
In CegoQueryHelper::prepareFieldValue, fixed values are checked now
for right dimension
Submitted by: Bjoern Lemke <lemke@lemke-it.com>
The only reason to use post-stage is because the port needs to do
"things" at a later time, like some plist manipulation.
While there, fold post-install in do-install targets when they are
defined.
PR: 214780
Submitted by: mat
Exp-run by: antoine
Sponsored by: Absolight
