all: Bump after lang/go121 update

all: Bump after lang/go121 update

all: Bump after lang/go121 update

MFH:		2024Q2

all: Bump after lang/go121 update

MFH:		2024Q2

security/metasploit: update to 6.4.7

PR:		278720

security/metasploit: Fix crash at start

Fix crash at start due to issues with dependencies:

Could not find compatible versions

Because every version of sinatra depends on rack >= 3.0.0, < 4
  and every version of thin depends on rack >= 1, < 3,
  every version of sinatra is incompatible with thin >= 0.
And because every version of metasploit-framework depends on thin >= 0,
  every version of sinatra is incompatible with metasploit-framework >= 0.
So, because every version of metasploit-framework depends on sinatra >= 0
  and Gemfile depends on metasploit-framework >= 0,
  version solving has failed.

PR:		278534
Reported by:	d0wq92 <dimoj30024@picdv.com>

all: Bump after lang/go121 update

MFH:		2024Q2

lang/go: Change DEFAULT to 1.21

PR:		277776
Approved by:	portmgr (exp-run)

all: Bump PORTREVISION after lang/go* update

PR:		276530

security/metasploit: update to 6.3.50

security/metasploit: fix runtime

PR:		276006
MFH:		2024Q1

all: Bump PORTREVISION after lang/go* update

PR:		274405

all: Bump PORTREVISION after lang/go* update

all: Bump PORTREVISION after lang/go{119,120} update

all: Bump PORTREVISION after lang/go{119,120} update

all: Bump PORTREVISION after Go ports update

security/metasploit: fix dependencies

all: Bump PORTREVISION after lang/go{119,120} update

all: Bump PORTREVISION after GO_DEFAULT update.

Mk/**ruby.mk: Switch from USE_RUBY=yes to USES=ruby

Switch from Mk/bsd.ruby.mk to Mk/Uses/ruby.mk

Notable changes are.

- Mk/bsd.ruby.mk is moved to Mk/Uses/ruby.mk.
- USE_RUBY=yes is replaced with USES=ruby.
- USE_RUBY_EXTCONF is replaced with USES=ruby:extconf.
- USE_RUBY_RDOC is replaced with USES=ruby:rdoc.
- USE_RUBY_SETUP is replaces with USES=ruby:setup.
- RUBY_NO_BUILD_DEPENDS and RUBY_NO_RUN_DEPENDS are replaced with
  USES=ruby:{build,none,run}.
- RUBY_REQUIRE isn't used anywhere, so removed.
- USES=gem now implies USES=ruby.

This is mainly the work of yasu@ at https://reviews.freebsd.org/D27863

I have just made some cosmetic changes and ran exp-run to test that the
tree is not in a BROKEN state.

Approved by:	portmgr
Differential Revision:	https://reviews.freebsd.org/D37925

all: Bump PORTVERSION after lang/go{118,119} update

all: Bump PORTREVISION after lang/go{118,119} update

security/metasploit: Update to 6.2.23

ChangeLog:
https://github.com/rapid7/metasploit-framework/compare/6.1.24...6.2.23

PR:		266977
Reported by:	yonas.yanfa@gmail.com

all: Bump PORTREVISION after lang/go{118,119} update

all: Bump PORTREVISION after lang/go{118,119} update

Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

security/metasploit: fix dependencies and runtime

all: Bump PORTREVISION after Go update

Bump Go ports PORTREVISION after GO_DEFAULT and lang/go118 update.

security: remove 'Created by' lines

A big Thank You to the original contributors of these ports:

  *  <ports@c0decafe.net>
  *  Aaron Dalton <aaron@FreeBSD.org>
  *  Adam Weinberger <adamw@FreeBSD.org>
  *  Ade Lovett <ade@FreeBSD.org>
  *  Aldis Berjoza <aldis@bsdroot.lv>
  *  Alex Dupre <ale@FreeBSD.org>
  *  Alex Kapranoff <kappa@rambler-co.ru>
  *  Alex Samorukov <samm@freebsd.org>
  *  Alexander Botero-Lowry <alex@foxybanana.com>
  *  Alexander Kriventsov <avk@vl.ru>
  *  Alexander Leidinger <netchild@FreeBSD.org>

all: Bump PORTREVISION after lang/go{117,118} update

*/*: Bump port revisons after lang/go{117,118} update

*/*: Bump PORTREVISION after lang/go 1.18 update

security/metasploit: update to 6.1.24

ChangeLog: https://github.com/rapid7/metasploit-framework/tags

PR:	260959
Reported by:	mbeis@xs4all.nl
Approved by:	tanawts@gmail.com (maintainer, timeout)

security/metasploit: Update to 6.1.12

While I'm here,

* Switch to DISTVERSION
* Pet portclippy
* Re-format Makefile with portfmt

Changes:	https://github.com/rapid7/metasploit-framework/commits/6.1.12
PR:		259550
Approved by:	maintainer

security/metasploit: fix dependencies

security/metasploit: update to 6.1.6

PR:	258569

security/metasploit: Add CPE information

Approved by:	portmgr (blanket)

Remove # $FreeBSD$ from Makefiles.

Update to 6.0.23

Update to 6.0.0

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