CVE and update status of the FreeBSD ports tree4,526 unaddressed CVEs in 616 portsAll times are CET

Port details

comms/flcluster1.1.01

Management tool for accessing dxcluster nodes

Maintainer
hamradio@FreeBSD.org
Packages
flcluster 1.1.01
Upstream
up to date
CPE
none, CVEs only via VuXML
WWW
https://www.w1hkj.org/flcluster-help/
Links
cgit · VuXML

Unaddressed (0) · The CVE record lists this version as affected, no VuXML entry names the CVE

None. There is no CVE without a VuXML entry for this version.

VuXML only (0) · listed, port not fixed yet

None. pkg audit reports nothing for this version.

Fixed (0)

No VuXML entries for this package.

Commits (17)

Älven (alven) · 1.1.01
comms/flcluster: Update 1.0.4 => 1.1.01

Changelogs:
* https://sourceforge.net/p/fldigi/flcluster/ci/v1.1.01/tree/ChangeLog

* Fix upstream URI for WWW
* Use https:// URI scheme for WWW
* Add LICENSE_FILE
* Pet portclippy(1) and portfmt(1)
* Spellcheck pkg-descr

Approved by:	hamradio@ (alven@, yuri@)
Approved by:	yuri@ (Mentor)

Differential Revision: https://reviews.freebsd.org/D52897
4c5af10c63
Stefan Eßer (se) · 1.0.4_3
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)
fb16dfecae
Stefan Eßer (se) · 1.0.4_3
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.

This commit implements such a proposal and moves one of the WWW: entries
of each pkg-descr file into the respective port's Makefile. A heuristic
attempts to identify the most relevant URL in case there is more than
one WWW: entry in some pkg-descr file. URLs that are not moved into the
Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr
files in order to preserve them.

There are 1256 ports that had no WWW: entries in pkg-descr files. These
ports will not be touched in this commit.

The portlint port has been adjusted to expect a WWW entry in each port
Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as
deprecated.

Approved by:		portmgr (tcberner)
b7f05445c0
Dmitry Marakasov (amdmi3) · 1.0.4_3
*/*: fix trailing whitespace in pkg-descr's

Approved by:	portmgr blanket
7b4d1f0b36
Mathieu Arnold (mat) · 1.0.4_3
One more small cleanup, forgotten yesterday. Reported by:	lwhsu
cf118ccf87
Mathieu Arnold (mat) · 1.0.4_3
Remove # $FreeBSD$ from Makefiles.
305f148f48
Alexey Dokuchaev (danfe) · 1.0.4_3
Sanitize COMMENT per Section 5.6 of the FreeBSD Porter's Handbook (part 1).
907a4eb7ab
Niclas Zeising (zeising) · 1.0.4_3
Add USES=xorg USES=gl, ports categories c

Add USES=xorg, USES=gl and in a few cases USES=gnome to ports in categories
starting with 'c'.
c2e845d0c8
Gerald Pfeifer (gerald) · 1.0.4_3
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
ea8c8ec7da
Gerald Pfeifer (gerald) · 1.0.4_2
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
a9f015d155
Gerald Pfeifer (gerald) · 1.0.4_1
Bump PORTREVISION for ports depending on the canonical version of GCC in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which has now moved from GCC 6 to GCC 7 by default.

This includes ports
 - featuring USE_GCC=yes or USE_GCC=any,
 - featuring USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and those
 - with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
   c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.

PR:		222542
09f9633cb6
Diane Bruce (db) · 1.0.4
=Version 1.0.4=

2017-12-18  David Freese  <w1hkj@bellsouth.net>

        3fdf12c: Cluster stream
        d32b3d9: AR report

Reported by:	portscout
2ae3dd8688
Antoine Brodin (antoine) · 1.0.3
Cleanup LIB_DEPENDS on libpng
07faea058d
Diane Bruce (db) · 1.0.3
Move with upstream to sourceforge

=Version 1.0.3=

2017-10-14  David Freese  <w1hkj@bellsouth.net>

	0d1ba30: dxcc server list
76121f6b66
Diane Bruce (db) · 1.0.2
=Version 1.0.2=

2017-10-12  David Freese  <w1hkj@bellsouth.net>

	efe4c58: UI thread bug
	cc846da: FreeBSD reported bugs
	be720c4: Prog doc update

=Version 1.0.1=

	d46e018: Application icon
	926b7fd: Installation bugs
	43e4059: win mingw
	4a092db: doc update
	c9021c0: Code revision #2

=Version 1.0.0=

	c5373f2: Code Revision 1
	926ee8e: Initial flcluster repository
5cf392c1f3
Baptiste Daroussin (bapt) · 1.0.1
Mark as broken ports with no public distfiles
1493dd450d
Diane Bruce (db) · 1.0.1
flcluster is a stand alone dx cluster client that will also connect to fldigi and act as the dx cluster client for fldigi. Multiple instances of flcluster can simultaneously connect to fldigi, and fldigi's internal dx cluster client can also be connected at the same time.  Connectivity is via a socket interface, so flclient can reside on the same or a different computer on the LAN or WAN so long a

On line help is available <http://www.w1hkj.com/flcluster-help/>
fd5ad89442