https://github.com/hashicorp/vagrant/releases
Also adds a one-line patch to vagrant's ssh_communicator to avoid a
flood of warnings from net-ssh (net-ssh changed a parameter's name).
PR: 222390
Approved by: joe(at)thrallingpenguin.com (maintainer)
This release includes proper support for egresses, meaning sandboxed
applications can now make outgoing network connections properly. In
addition to that, a new utility, flower_ls, can be used to extract a
list of registered servers. This is pretty useful for debugging.
Bump cloudabi-utils' revision to catch up with .proto changes.
Reviewed_by: koobs
Approved by: koobs (ports)
Differential_Revision: D12399
- Move ONLY_FOR_ARCHS into the right position of the Makefile.
- Omit a comment describing GCC_VERSION and SUFFIX.
- Do not quote constant strings compared with ${ARCH}. [1]
- Last, but not least the only functional change (and an important one):
Remove headers being created by GCC's fixincludes machinery from
the installation / packaging to avoid breakage when FreeBSD's headers
are changing afterwards. [2]
PR: 221905 [1], 222233 [2]
Submitted by: linimon [1]
behaviour and workflows of both Git and Darcs, but contrarily to those systems,
Pijul is based on a mathematically sound theory of patches.
Pijul was started out of frustration that no version control system was at the
same time fast and sound:
- Git has non-associative merges, which might lead to security problems.
Concretely, this means that the commits you merge might not be the same as
the ones you review and test.
- Handling of conflicts: Pijul has an explicit internal representation of
conflicts, a rock-solid theory of how they behave, and super-fast data
structures to handle them.
- Speed! The complexity of Pijul is low in all cases, whereas previous attempts
to build a mathematically sound distributed version control system had huge
worst-case complexities. The use of Rust additionally yields a blazingly fast
implementation.
WWW: https://pijul.org/
version of GCC has not been maintained upstream for nearly four-and-a-half
years and is not used anywhere in the tree.
Move ONLY_FOR_ARCHS to its appropriate place.
PR: 222373 [1]
Submitted by: Yasuhiro KIMURA <yasu@utahime.org> [1]
version of GCC (which is GCC 6 these days).
For most practical purposes USE_GCC=4.8+ is equivalent to USE_GCC=yes,
so GCC 5 for several months (and now GCC 6) have been used already since
2017-03-07 and revision 435594 -- if GCC is used at all, which is not the
default anyway.
- Fix in CegoBufferpool::writeCheckpoint, in case of an locking
exception ( lockBufferPool ), the pool must be released in any case.
For this the CegoLockManager::lockBufferPool and
CegoLockManager::unlockBufferPool have been modified in a way,
that lockBufferPool saves the current sema index ( _poolRangeLock )
which is later used for the unlocking call.
- Timeout parameter for bufferpool lock reduced to 60 seconds.
- Optimization in CegoBufferPool:bufferfix for minHashId calculation
in step 2, there was an unneeded locking operation for the
minhashId, which was already locked by the main loop
- Small format fix in CegoProcCreateStmt ( missing indent )
- Add header row out put for client raw mode ( attribute names )
- Fix in CegoQueryHelper::evalPredicate, for all predicate types,
the field array value has to be reset to 0, otherwise seg fault my
occur since invalid references might be used
Submitted by: Bjoern Lemke <lemke@lemke-it.com>
some commented (and thus disabled) logic around this on the way.
This brings the active lang/gcc* release-based ports in sync with
their respective lang/gcc*-devel twins.
PR: 221905 [1]
Submitted by: linimon [1]
Details:
- Use standard HAS_CONFIGURE instead of rolling our own
- Use blaslapack
- Regenerate patches with "make makepatch".
- Add LICENSE
- Fortran is used as linker but all the code is in C so use CFLAGS
instead of FFLAGS.
PR: 214963
Submitted by: pfg
Failed builds can occur when PORTSDIR is a symbolic link, or with
make -C /usr/ports/category/port/
PR: 221296
Reported by: yasu@utahime.org, rum1cro@yandex.ru
Reviewed by: bdrewery, sjg
Approved by: portmgr (bdrewery)
Differential Revision: https://reviews.freebsd.org/D11934
- Add HTTPS alternatives by request [1], deliberately keep corresponding HTTP
hosts for providing a variety of sources (not for integrity since this is
guaranteed by the distinfo checksums)
PR: 221725 [1]
Submitted by: xmj [1]
This package facilitates the creation and rendering of graph descriptions in the
DOT language of the Graphviz graph drawing software (repo) from Python.
Create a graph object, assemble the graph by adding nodes and edges, and
retrieve its DOT source code string. Save the source code to a file and render
it with the Graphviz installation of your system.
Use the view option/method to directly inspect the resulting (PDF, PNG, SVG,
etc.) file with its default application. Graphs can also be rendered and
displayed within Jupyter notebooks (a.k.a. IPython notebooks, example) as well
as the Jupyter Qt Console.
WWW: https://github.com/xflr6/graphviz
Already existed a port named graphics/py-graphviz, it was moved in
ports r408353 to graphics/py-pygraphviz because it was using an
incorrect name. More info in the commit log [1].
1 - https://svnweb.freebsd.org/ports?view=revision&revision=408353
PR: 222205
Submitted by: lbartoletti@tuxfamily.org
Reviewed by: koobs
Differential Revision: D12319
This plugin produces coverage reports. It supports centralised testing and
distributed testing in both load and each modes. It also supports coverage of
subprocesses.
All features offered by the coverage package should be available, either through
pytest-cov or through coverage's config file.
WWW: https://github.com/pytest-dev/pytest-cov
Reviewed by: koobs
Differential Revision: D12394
- Add arm64 support [1]
- Fix segfault on i386 [2]
- Switch to USES=compiler:c++14-lang for devel/chromium-gn because chromium
needs __builtin_add_overflow and friends to build.
Changelog: https://chromium.googlesource.com/chromium/src/+log/60.0.3112.113..61.0.3163.79?pretty=fuller&n=10000
PR: 220291 [1], 221266 [2]
Submitted by: Andrew [1]
Reported by: Patrick <doctorwhoguy@gmail.com> [2]
MFH: 2017Q3
