Judging by Vagrant's gemspec file, Vagrant requires rubygem-childprocess
version which is between 3.0.0 and 3.1.0 (expressed as ~> 3.0.0). Recently,
devel/ruby-gemprocess was updated to 4.0.0. It is necessary to switch to a
new port supporting version 3.0.*, which is devel/ruby-gemprocess3.
Approved by: portmgr blanket (runtime fix)
for the configure test to pass on FreeBSD right now (even with extra
ports available), so this simply makes this explicit and avoids a
warning from configure.
CMake Error in CMakeLists.txt:
Target "systemshock" requires the language dialect "CXX11" (with compiler
extensions), but CMake does not know the compile flags to use to enable it.
Approved by: portmgr (tier-2 blanket)
* Switch to Django 2.2 (current LTS release) because Django 1.11 is
End-of-Life.
* Introduce a DJANGO30 option to make use of the Django 3.0 port and set the
Python version accordingly for each option.
* Keep the DJANGO111 option for now as long as Django 1.11 is still present
in the Ports tree.
Django 1.11 is still required for www/py-django-mezzanine, www/seahub and
their dependencies. There's is work in progress by upstream to make these
ports compatible for Django 2.2+ .
PR: 245309
Submitted by: wen (via private e-mail, based on)
Reviewed by: sunpoet
Differential Revision: https://reviews.freebsd.org/D25495
CVE-2017-14160: Fix bounds check on very low sample rates.
CVE-2018-10392: Sanity check number of channels in setup.
These were committed upstream two years ago, but there has been no
release since.
Reported by: T.J. Townsend <tj@openbsd.org>
Security: 4200d5f5-b985-11ea-b08a-f8b156b6dcc8
After devel/zookeeper was upgraded to the latest version, this port no longer
builds. Last update from upstream was in 2015 so it appears Net::ZooKeeper
is no longer actively maintained.
- remove CONFLICTS with lang/python3 (DP)
- remove future CONFLICTS with blas/lapack (PR 247542)
- add a pkg-message for SAGE_ROOT / SAGE_LOCAL (DP)
- remove the check of R´s Makevars.site (DP)
see <https://trac.sagemath.org/ticket/29943>
- use math/e-antic from the ports tree
- make BROKEN on -CURRENT untill a solution is found / Python
Reported by: Dima Pasechnik <dimpase (at) gmail.com> (DP)
Changelog:
https://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html
among them are these two---and more bugfixes beyond not listed here:
* Security fix: if an SSH server accepted an offer of a public key
and then rejected the signature, PuTTY could access freed memory,
if the key had come from an SSH agent.
* Security feature: new config option to disable PuTTY's dynamic
host key preference policy, if you prefer to avoid giving away
to eavesdroppers which hosts you have stored keys for.
MFH: 2020Q2
Security: 6190c0cd-b945-11ea-9401-2dcf562daa69
Security: CVE-2020-14002
Security: FZI-2020-5
