Problem reports for ports-bugs at FreeBSD.org that need special attention
bugzilla-noreply at FreeBSD.org
bugzilla-noreply at FreeBSD.org
Sun Sep 16 21:00:09 UTC 2018
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.
Status | Bug Id | Description
------------+-----------+---------------------------------------------------
New | 227376 | net/rtg: fix runtime php errors / add new feature
Open | 207310 | deskutils/silence can't start - socket error
Open | 210626 | archivers/libarchive: Fails to build when archive
Open | 211108 | security/strongswan: Fix rc startup script for su
Open | 212149 | security/strongswan: Runtime failures with LibreS
Open | 213781 | sysutils/arcconf: Fails to run: Undefined symbol
Open | 216050 | x11/nvidia-driver: kernel module fails on vt() to
Open | 220308 | security/sssd Python 2 hangs calling pysss.getgro
Open | 220978 | mail/dcc-dccd: Mixes data and code, does not resp
Open | 221003 | sysutils/flexbackup: patch patch-flexbackup exten
Open | 221091 | security/ike: iked fails to run after FreeBSD 11.
Open | 221149 | mail/postfix-policyd-weight: rc script name issue
Open | 221268 | math/geogebra: 3D doesn't work
Open | 221297 | lang/go: Fix arm build
Open | 223486 | www/e2guardian: Fix certificate verification with
Open | 226722 | lang/opencoarrays: "make test" as root causes han
Open | 230496 | mail/nullmailer: Fails to build with Clang 6.0
Open | 230607 | devel/thrift: Remove -Werror compiler flag/argume
New | 228969 | [NEW PORT] deskutils/fasd: handy shell helper to
New | 229115 | [maintainer] sysutils/bbcp: silence pkg-fallout,
New | 231102 | [PATCH] devel/libe: update to release 0.11.0
New | 231103 | [PATCH] devel/busybee: update to release 0.7.0
New | 231156 | deskutils/py-vobject: Update to 0.9.6.1
23 problems total for which you should take action.
More information about the freebsd-ports-bugs
mailing list