Number of commits found XX: 137 (showing only 100 on this page)

1 | 2  »  

Update to 5.0.90

Add a missing link

security/metasploit: Update rubygem-rex-exploitation dependency

While here, reorder some variables.

PR:	245047
Submitted by:	rl+fbsd@ciphron.de
Approved by:	tanawts@gmail.com(maintainer, timeout > 1 week)

Update to 5.0.79

Update to 5.0.64

Update to 5.0.54

Update to 5.0.47

Remove outdated RUBY_VER check

With hat:	ruby

Fix runtime after rubygem-sqlite3 upgrade

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 to 5.0.28

Update to 5.0.19

Change RUN_DEPENDS from rubygem-msgpack1 to rubygem-msgpack

- Bump PORTREVISION for dependency change

Update to 5.0.13

Update to 5.0.9

Update to 5.0.5

Update to 4.17.37

Update to 4.17.35

Update to 4.17.32

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

Update to 4.17.26

Update to 4.17.17

Update to 4.17.14

Update to 4.17.5

Metasploit database requires rubygem-pg version 0.2x

PR:		228722
Reported and tested by:	Marco Beishuizen
MFH:		2018Q3

Update to 4.16.63

Update to 4.16.60

Update to 4.16.57

Update to 4.16.51

Update to 4.16.49

Update to 4.16.45

Update to 4.16.43

Update to 4.16.41

Update to 4.16.36

Update to 4.16.32

Update to 4.16.28

Update to 4.16.26

Add a USES=python:env, that will not add a dependency on Python.

It has the same effect than setting PYTHON_NO_DEPENDS, but in a more
compact way.

Sponsored by:	Absolight

Update to 4.16.21

Update to 4.16.15

Update to 4.16.13

Update to 4.16.12

Update to 4.16.10

Update to 4.16.9

Update to 4.16.8

Update to 4.16.6

Update to 4.16.4

Update to 4.16.2

Update to 4.15.5

Update to 4.15.0

Update to 4.14.28

qa: add check for NO_ARCH

If NO_ARCH is set then check that no FreeBSD elf(5) files are in $STAGEDIR.
If an elf(5) file is bundles as part of the package, but is not meant to be
run directly (i.e. the elf(5) file is a payload, and not compiled) then
those files can be added to NO_ARCH_IGNORE to avoid the check from failing,

Changes to ports:
 - Ports that have NO_ARCH set, but actually compile files have had NO_ARCH
   removed.
 - Ports that have elf(5) payloads have had those files added to
   NO_ARCH_IGNORE.
 - R-cran ports that do not set USES=cran:compiles have NO_ARCH set,

PR:		218976
Reviewed by:	antoine, mat
Approved by:	portmgr

Update to 4.14.25

Update to 4.14.24

security/metasploit: Update to 4.14.22

PR:		219607
Approved by:	tanawts@gmail.com (maintainer)

Update to 4.14.21

Update to 4.14.16

Update to 4.14.9

Update to 4.14.2

Update to 4.13.24

Update to 4.13.19

Update to 4.13.16

Update to 4.13.15

Update to 4.13.12

Update to 4.13.6

Update to 4.13.1

Update to 4.13.0

Update to 4.12.41

Update to 4.12.39

Update to 4.12.35

Update to 4.12.34

Update to 4.12.31

Update to 4.12.29

Update to 4.12.28

Update to 4.12.26

Update to 4.12.23

Update to 4.12.22

Update to 4.12.16

Update to 4.12.15

Update to 4.12.12

PR:		210950

Update to 4.12.5

Update to 4.12.2

Update to 4.12.1

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

With hat:	portmgr
Sponsored by:	Absolight

- Add LICENSE

Approved by:	portmgr (blanket)

- Convert to new options target helper

Approved by:	portmgr (blanket)

- Fix shebangs

Approved by:	portmgr blanket

Adjust after rubygem-jsobfu update

Update security/metasploit to 4.11.2

Update ports in the remaining categories to not use GH_COMMIT.

With minor cleanups to make things simpler.

With hat:	portmgr
Sponsored by:	Absolight

Update USE_GITHUB so it does not require GH_COMMIT.

Using this new scheme allows only setting the _tag_ or _commit hash_ in
GH_TAGNAME and not having to know the hash for a tag.  This scheme will
download a tarball that has a different checksum than before due to a changed
directory name for extraction.

The following MASTER_SITES are provided to retain the old checksum and
directory structure (that require GH_COMMIT):
  GH -> GHL
  GITHUB -> GITHUB_LEGACY

Differential Revision:	https://reviews.freebsd.org/D748
Submitted by:	amdmi3
Reviewed by:	mat, swills, antoine, bdrewery
With hat:	portmgr

Update:
- metasploit to 4.11.1
- rubygem-metasploit-credential to 0.13.17
- rubygem-metasploit_data_models to 0.22.6
- rubygem-meterpreter_bins to 0.0.13
- rubygem-recog to 1.0.7

Update metasploit to 4.11.0

Remove dependency on rb-readline, it works fine without it

Update security/metasploit to 4.10.2
Add new ports needed by this version:
security/rubygem-metasploit-concern
security/rubygem-metasploit-credential
security/rubygem-metasploit-model
security/rubygem-meterpreter_bins
security/rubygem-recog

Unbreak metasploit at runtime by adding www/rubygem-rkelly-remix

- Update from 4.9.2 to 4.9.3

PR:		ports/190802
Submitted by:	tanawts@gmail.com

Update metasploit to 4.9.2 and rubygem-metasploit_data_models to 0.17.0

PR:		ports/189046
Approved by:	maintainer timeout (2 weeks)

Update to 4.8.2

PR:		ports/185253
Submitted by:	maintainer

- Update to 4.7.2
- Use option helpers
- Convert to STAGEDIR

PR:		ports/183099
Approved by:	maintainer timeout (2 weeks)

Number of commits found XX: 137 (showing only 100 on this page)

1 | 2  »  

14 vulnerabilities affecting 165 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities

Last updated:
2020-05-24 19:56:04