This port hits segmentation faults right on startup (amd64, default/empty
`vm.malloc_conf'), both built with either `-fcommon' or fixes from FreeBSD.
No update since 2003.
Fails to build the now default "-fno-common".
OK gnezdo
tream at https://www.gnu.org/software/xhippo/ no longer provides
distfiles since at least 2019, FreeBSD also has marked the port as such;
the website says
The GNU xhippo has been decommissioned.
Fails to build the now default "-fno-common".
Other ports such as audio/mkplaylist do similar jobs, most media players
also have such functionality, e.g. VLC does.
OK danj
Starting the app shows a window but upon clicking "OK" it dies immediately.
It depends on old Python and GTK and already carries a local patch to cope
an old cURL update.
Upstream is dead, FreeBSD also marked the port for removal.
OK danj
The import of this tool in 2004 predates pf.conf(5)'s "af-to" which came
about in 2011.
Since that, there have been no port changes other than dusting things of
in the Makefile.
Upstream is dead, this port fails with "-fno-common" and I have a hard
time seeing how one would use a proxy daemon with their browser to do
address family translation these days.
OK danj
Upstream still ships the tarball, that's it, as per CVS log:
"primary distsite and homepage have gone away".
The only TCP port I've been able to detect (after producing traffing on a
variety of them) is SSH -- and that only worked after enabling IPv4.
Siphon does not seem to support/detect IPv6 at all and it's OS fingerprints
are extremely old; besides Gentoo we're the only ones still packaging it
according to https://repology.org/project/siphon/versions .
Fails with "-fno-common".
OK cwen
That's a NetBus 1.6 client... upstream's dead as in NXDOMAIN, we seem to be
the only folks still packaging it.
It has not changed in twenty years (surprise!) and basically only exists to
screw around with old old Windows boxes which... still run the server?
Fails with "-fno-common".
OK jsg
No release from upstream since 2004, no IPv6 support and the port now fails
to build with "-fno-common".
There's net/scapy in our tree which can do everything that nemesis does and
more.
OK bcallah
Our packaged 1.0 version seems to be the last one that can be fetched
from upstream, which is long dead; HOMEPAGE http://packit.sf.net points
to a generic corporate stub.
FreeBSD packages an "updated" version, see
https://github.com/resurrecting-open-source-projects/packit/blob/master/ChangeLog
which effectively is the old source could with all readily available
distribution patches from Debian, Gento, etc. applied on top; other than
that there's no development, the project README explicitly asks for help
from actual developers to keep such life support running.
Since noone could be bothered with updating our port since at least 2016,
I doubt there's much interest.
packit is a mixture of tcpdump(1) and scapy(1), it's synopsis uses every
letter (upper and lower) of the alphabet and IPv6 is not supported at all
(not even printing captured packets).
Basic tests showed no output when capturing on lo(4) devices.
tl;dr: There's little to no value in beating a dead horse.
OK solene
It fails to build with "-fno-common" and HOMEPAGE indicates that it's
no longer being worked on.
The website points at https://cronometer.com/ (website / mobile app) to be
used in the interim until upstream's NUT rewrite is done.
There is NUTsqlite on the sourceforge site's files section, not sure
but perhaps that is the rewrite talked about on the website. It is
written in Tcl/Tk. (thanks sthen)
OK sthen
Imported in 1998 and modified in 2009 to "fix Y2K bug" which means
"we may not distribute modified versions [due to its license]".
There has been no update and it now fails to build with "-fno-common".
The servers used by "getsts" and "gettle" to fetch satellite information
no longer exist.
FreeBSD removed it in 2011, "No more public distfiles". (thanks naddy)
OK naddy
Both are Python 2 only, collecting dust, their common upstream is dead
and py-vorbis is the only consumer of py-ogg.
Nothing in the tree uses either of them, not even as TEST_DEPENDS.
py-ogg now fails to build with "-fno-common".
OK sthen
It often aborts upon start due to "free(): recursive call",
does not support IPv6,
segfaults in vfscanf(3) due to "traceroute: sendto: No route to host" and
specifying a target only seems to work on the command line but not during
runtim in the window.
At runtime, it eventually aborts again.
tb even reported graphics related crashes in X11's iris driver when clicking
on the globe.
This port fails to build with "-fno-common".
No objections tb
OK sthen
Over half a year ago I dropped MAINTAINER on this port due to not using it
any longer. At that time it was already outdated. Noone spoke up to
update or even maintain it.
The new (unported) version 1.6.0 already suffers from TLS related build
failures, now there's another problem: it does not build with "-fcommon"
which will become a default compiler option in the tree.
If someone wants to fix both and get an up-to-date version running they
recover it from the attic.
OK tb
letsencrypt have already stopped allowing ACMEv1 for new domain
validations, and are now doing "brownouts" for all ACMEv1 access,
disabling it temporarily twice a month for increasing lengths of
time (6/24/48/72/120/168 hours) in the run up to disabling it
completely on June 1st.
"it was originally ported to 'fix' the qt5 bug with file dialogs when
running within gtk desktop environments, the default gtk3 file dialog
triggers a cpu 100% spin." -- landry
This issue still exists so DO NOT USE GTK3-style (which should not be the
default) for (py)-Qt applications.
Qt5 does not ship a qtconfig utility to configure fonts, icons or styles. You
can use the qt5ct package to do this job. Don't forget to set the environment
variable QT_QPA_PLATFORMTHEME=qt5ct so that the settings are picked up by Qt
applications
OK kmos, kn and landry
These ports are on the update path for py-sphinx so making them python3
only helps. Both jca and I built ports llvm with this update.
ok jca@, sebastia@ (maintainers of these ports)
First the package was broken due to too recent dependent packages, then it
was broken due to beeing too old itself.
Upstream dropped the GUI years ago, so remove it.
With daniel
x11/xfce4/xfce4-statusnotifier
orage was Gtk+2 only, saw no development since 4.12.
xfce4-statusnotifier features were merged to xfce4-panel systray plugin.