Remove expired ports:

2021-01-24 www/sogo4: Unmaintained, please migrate to a newer version of sogo
2021-01-24 www/sogo4-activesync: Unmaintained, please migrate to a newer version
of sogo
2021-01-27 security/py-rekall_lib: Unmaintained upstream
2021-01-27 devel/py-rekall-efilter: Unmaintained upstream
2021-01-27 security/py-rekall: Unmaintained upstream, use
security/py-volatility3 instead
2021-01-27 security/py-rekall-core: Unmaintained upstream
2021-01-27 www/kurly: Upstream is gone
2021-01-27 security/regripper: Upstream repo disappeared

Deprecate rekall ports

Update security/py-artifacts to 20200118

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

Update rekall to 1.7.2rc1-52

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

Attempt to unbreak ports depending on ipython

Update to 1.7.2rc1

Bump PORTREVISIONs of all users of math/mpc that we just updated to
version 1.1.0 (via revision 464079).

Explicitely pass ipython FLAVOR in a few ports

Convert Python ports to FLAVORS.

  Ports using USE_PYTHON=distutils are now flavored.  They will
  automatically get flavors (py27, py34, py35, py36) depending on what
  versions they support.

  There is also a USE_PYTHON=flavors for ports that do not use distutils
  but need FLAVORS to be set.  A USE_PYTHON=noflavors can be set if
  using distutils but flavors are not wanted.

  A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
  added to cope with Python ports that did not have the Python
  PKGNAMEPREFIX but are flavored.

  USES=python now also exports a PY_FLAVOR variable that contains the

Un-ignore after ipython upgrade

- Update py-rekall-core to 1.6.0
- Ignore py-rekall_gui: doesn't work with py-rekall-core 1.6.0 yet
- Ignore py-rekall: requires ipython 5.0.0

Cleanup no longer needed CHMOD usage after r424898.

PR:		213743
Submitted by:	mat
Exp-run by:	antoine
Sponsored by:	Absolight

Update py-rekall/py-rekall-core to 1.5.2

Update to 1.5.1

Update rekall to 1.5.0

Remove ${PORTSDIR}/ from dependencies, categories r, s, t, and u.

With hat:	portmgr
Sponsored by:	Absolight

- Update libsodium to 1.0.8
- Bump revisions of all dependant ports

PR:		206482
Submitted by:	lev, w.schwarzenfeld@aon.at

Update rekall to 1.4.1
It was split in 3 modules
- security/py-rekall-core : CORE component with command line interface
- security/py-rekall_gui : GUI with ipython and web interface
- security/py-rekall : "meta" module

- Fix shebangs

Approved by:	portmgr blanket
MFH:		2015Q2

Update to 1.3.2

Update to 1.3.1

Announce:	http://rekall-forensic.blogspot.ch/2015/04/announcing-rekall-release-131-dammastock.html

Update to 1.2.0

New port: security/py-rekall

The Rekall Framework is a completely open collection of tools, implemented in
Python under the GNU General Public License, for the extraction of digital
artifacts from volatile memory (RAM) samples. The extraction techniques are
performed completely independent of the system being investigated but offer
visibility into the runtime state of the system. The framework is intended to
introduce people to the techniques and complexities associated with extracting
digital artifacts from volatile memory samples and provide a platform for
further work into this exciting area of research.

WWW: http://www.rekall-forensic.com/