something wrong with LICENSEs
Hi, CCd eadler@ as he did last commit. When I'm trying update x11/xbitmaps x11/xtrans and other xorg-related(?) ports I got: ===> License not correctly defined: for unknown licenses, defining LICENSE_PERMS is mandatory (otherwise use a known LICENSE) with DISABLE_LICENSES all works fine, sure. Not so long ago was a great practice - 'freeze' for ports tree, but it was abandoned, so sad. Eitan, does x11/xbitmaps (for example) build fine for you? -- wbr, tiger ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: something wrong with LICENSEs
Sergey V. Dyatko wrote on 20.09.2011 11:06: Hi, CCd eadler@ as he did last commit. When I'm trying update x11/xbitmaps x11/xtrans and other xorg-related(?) ports I got: ===> License not correctly defined: for unknown licenses, defining LICENSE_PERMS is mandatory (otherwise use a known LICENSE) with DISABLE_LICENSES all works fine, sure. Not so long ago was a great practice - 'freeze' for ports tree, but it was abandoned, so sad. Eitan, does x11/xbitmaps (for example) build fine for you? There is no "x11" in Mk/bsd.licenses.db.mk -- Regards, Ruslan Tinderboxing kills... the drives. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: something wrong with LICENSEs
On Tue, 20 Sep 2011 11:42:17 +0400 Ruslan Mahmatkhanov wrote: > Sergey V. Dyatko wrote on 20.09.2011 11:06: > > Hi, > > > > CCd eadler@ as he did last commit. > > > > When I'm trying update x11/xbitmaps x11/xtrans and other > > xorg-related(?) ports I got: > > > > ===> License not correctly defined: for unknown licenses, defining > > LICENSE_PERMS is mandatory (otherwise use a known LICENSE) > > > > with DISABLE_LICENSES all works fine, sure. > > > > Not so long ago was a great practice - 'freeze' for ports tree, but > > it was abandoned, so sad. > > > > Eitan, does x11/xbitmaps (for example) build fine for you? > > > > There is no "x11" in Mk/bsd.licenses.db.mk > Exactly. thats why Eitan, does x11/xbitmaps (for example) build fine for you? -- wbr, tiger ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: something wrong with LICENSEs
On Tue, Sep 20, 2011 at 11:13:38AM +0300, Sergey V. Dyatko wrote: > On Tue, 20 Sep 2011 11:42:17 +0400 > Ruslan Mahmatkhanov wrote: > > > Sergey V. Dyatko wrote on 20.09.2011 11:06: > > > Hi, > > > > > > CCd eadler@ as he did last commit. > > > > > > When I'm trying update x11/xbitmaps x11/xtrans and other > > > xorg-related(?) ports I got: > > > > > > ===> License not correctly defined: for unknown licenses, defining > > > LICENSE_PERMS is mandatory (otherwise use a known LICENSE) > > > > > > with DISABLE_LICENSES all works fine, sure. > > > > > > Not so long ago was a great practice - 'freeze' for ports tree, but > > > it was abandoned, so sad. > > > > > > Eitan, does x11/xbitmaps (for example) build fine for you? > > > > > > > There is no "x11" in Mk/bsd.licenses.db.mk > > > > Exactly. thats why > > Eitan, does x11/xbitmaps (for example) build fine for you? > This is fixed now, regards, Bapt pgpOCtqW5OMu7.pgp Description: PGP signature
Re: Circular dependency in devel/doxygen?
> Hey everyone, I maintain devel/doxygen (sorry I didn't add my 2 cents > earlier, I've been a bit busy) and was looking at this particular thread. I > know someone filed a PR regarding the circular dependency, stating that it > might be best to split apart doxygen so one port builds just the program and > another port build just the documentation. I am not sure if that is the > best thing to do or not. I've been wanting to push out an update to doxygen > but this has been a stopping block for me. > Naram Qashat It seems strange to me that doxygen would have audio dependencies, or is doxygen supposed to work with a speech synthesizer? What dependencies would doxygen documentation have? Anything circular? I see abiword and abiword-docs are split in two separate ports. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
problem with port x11/xbitmaps in Current and 7.4 stable.
Checked UPDATING and there isn't any mention. I get: x11/xbitmaps # make ===> Vulnerability check disabled, database not found ===> License not correctly defined: for unknown licenses, defining LICENSE_PERMS is mandatory (otherwise use a known LICENSE) *** Error code 1 Stop in /usr/ports/x11/xbitmaps. Not a big deal, I've not seen that message before, that I rememver anyway. ed ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: problem with port x11/xbitmaps in Current and 7.4 stable.
On 20 Sep 2011 13:10, "Edwin L. Culp W." wrote: > > Checked UPDATING and there isn't any mention. I get: > > x11/xbitmaps # make > ===> Vulnerability check disabled, database not found > ===> License not correctly defined: for unknown licenses, defining > LICENSE_PERMS is mandatory (otherwise use a known LICENSE) > *** Error code 1 > > Stop in /usr/ports/x11/xbitmaps. > > Not a big deal, I've not seen that message before, that I rememver anyway. > Please csup and try again. Has a nice ring, doesn't it ;) Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: something wrong with LICENSEs
On Sep 20, 2011, at 4:23 AM, Baptiste Daroussin wrote: > On Tue, Sep 20, 2011 at 11:13:38AM +0300, Sergey V. Dyatko wrote: >> On Tue, 20 Sep 2011 11:42:17 +0400 >> Ruslan Mahmatkhanov wrote: >> >>> Sergey V. Dyatko wrote on 20.09.2011 11:06: Hi, CCd eadler@ as he did last commit. When I'm trying update x11/xbitmaps x11/xtrans and other xorg-related(?) ports I got: ===> License not correctly defined: for unknown licenses, defining LICENSE_PERMS is mandatory (otherwise use a known LICENSE) with DISABLE_LICENSES all works fine, sure. Not so long ago was a great practice - 'freeze' for ports tree, but it was abandoned, so sad. Eitan, does x11/xbitmaps (for example) build fine for you? >>> >>> There is no "x11" in Mk/bsd.licenses.db.mk >>> >> >> Exactly. thats why >> >> Eitan, does x11/xbitmaps (for example) build fine for you? >> > > This is fixed now, This was my fault and oversight; I am sorry. I know that will not allay some of your collective ire, so please direct all hatemail to me. -- Sahil Tandon___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: something wrong with LICENSEs
Sahil Tandon wrote on 20.09.2011 16:41: On Sep 20, 2011, at 4:23 AM, Baptiste Daroussin wrote: On Tue, Sep 20, 2011 at 11:13:38AM +0300, Sergey V. Dyatko wrote: On Tue, 20 Sep 2011 11:42:17 +0400 Ruslan Mahmatkhanov wrote: Sergey V. Dyatko wrote on 20.09.2011 11:06: Hi, CCd eadler@ as he did last commit. When I'm trying update x11/xbitmaps x11/xtrans and other xorg-related(?) ports I got: ===>License not correctly defined: for unknown licenses, defining LICENSE_PERMS is mandatory (otherwise use a known LICENSE) with DISABLE_LICENSES all works fine, sure. Not so long ago was a great practice - 'freeze' for ports tree, but it was abandoned, so sad. Eitan, does x11/xbitmaps (for example) build fine for you? There is no "x11" in Mk/bsd.licenses.db.mk Exactly. thats why Eitan, does x11/xbitmaps (for example) build fine for you? This is fixed now, This was my fault and oversight; I am sorry. I know that will not allay some of your collective ire, so please direct all hatemail to me. -- Sahil Tandon Hi, Sahil :) Maybe you prefer to commit http://bugs.freebsd.org/160434 as an punishment for that :)? It's new license adding, and Wen have some connection problem right now. -- Regards, Ruslan Tinderboxing kills... the drives. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: problem with port x11/xbitmaps in Current and 7.4 stable.
On Tue, Sep 20, 2011 at 7:13 AM, Chris Rees wrote: > > On 20 Sep 2011 13:10, "Edwin L. Culp W." wrote: >> >> Checked UPDATING and there isn't any mention. I get: >> >> x11/xbitmaps # make >> ===> Vulnerability check disabled, database not found >> ===> License not correctly defined: for unknown licenses, defining >> LICENSE_PERMS is mandatory (otherwise use a known LICENSE) >> *** Error code 1 >> >> Stop in /usr/ports/x11/xbitmaps. >> >> Not a big deal, I've not seen that message before, that I rememver anyway. >> > > Please csup and try again. > > Has a nice ring, doesn't it ;) > > Chris :) Thanks, Chris. I've got a daily csup crontab. Should be ok in the morning. ed ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD unmaintained ports which are currently marked broken
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 6.x/7.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: archivers/bzip broken because: unfetchable; use archivers/bzip2 instead build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=bzip portname: audio/fmit broken because: does not configure build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.9.20110902155823/fmit-0.99.2.log (_Sep__8_01:25:02_UTC_2011) http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.8.20110718073617/fmit-0.97.7_6.log (_Jul_31_06:20:01_UTC_2011) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=fmit portname: audio/linux-shoutcast broken because: unfetchable; website rearranged build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-shoutcast portname: audio/shoutcast broken because: unfetchable; website rearranged build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=shoutcast portname: chinese/scim-chewing broken because: does not configure build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=scim-chewing portname: databases/kpogre broken because: does not compile build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20110914141638/kpogre-1.8.2_3.log (_Sep_17_09:27:37_UTC_2011) overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=kpogre portname: databases/xbase broken because: Does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=xbase portname: deskutils/gemcal broken because: Does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=gemcal portname: deskutils/mhc broken because: Does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=mhc portname: deskutils/org-mode.el6 broken because: Does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=org-mode.el6 portname: devel/erlang-thrift broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=erlang-thrift portname: devel/fampp broken because: FAM system mismatch: gamin is installed, while desired FAM system is fam build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=fampp portname: devel/gccxml broken because: does not compile build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.9.20110902155823/gccxml-0.6.0.log (_Sep__7_21:41:48_UTC_2011) overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=gccxml portname: devel/gcvs broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=gcvs portname:
FreeBSD ports which are currently marked broken
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 6.x/7.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: archivers/bzip broken because: unfetchable; use archivers/bzip2 instead build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=bzip portname: archivers/dact broken because: needs to be upgraded to lzo2 according to ports/156954 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=dact portname: audio/aacplusenc broken because: unfetchable build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20110920160718/aacplusenc-0.17.1.log (_Jul__8_13:10:29_UTC_2011) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=aacplusenc portname: audio/aureal-kmod broken because: doesn't build on RELENG_8 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=aureal-kmod portname: audio/fmit broken because: does not configure build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.9.20110902155823/fmit-0.99.2.log (_Sep__8_01:25:02_UTC_2011) http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.8.20110718073617/fmit-0.97.7_6.log (_Jul_31_06:20:01_UTC_2011) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=fmit portname: audio/gstreamer-plugins-flite broken because: Doesn't work due to link problem in audio/flite build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gstreamer-plugins-flite portname: audio/linux-shoutcast broken because: unfetchable; website rearranged build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-shoutcast portname: audio/rubyripper broken because: does not package build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.9.20110907072101/rubyripper-0.6.0_1.log (_Sep__4_07:26:45_UTC_2011) http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20110908204544/rubyripper-0.6.0_1.log (_Sep__9_22:14:56_UTC_2011) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=rubyripper portname: audio/shoutcast broken because: unfetchable; website rearranged build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=shoutcast portname: benchmarks/polygraph broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=benchmarks&portname=polygraph portname: benchmarks/polygraph31 broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=benchmarks&portname=polygraph31 portname: chinese/scim-chewing broken because: does not configure build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=scim-chewing portname: chinese/tin broken because: does not patch build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.8.20110718073617/zh-tin-1.9.6_3.log (_Jul_31_07:41:03_UTC_2011) overview:
FreeBSD unmaintained ports which are currently scheduled for deletion
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: archivers/bsdar description:BSD-licensed replacement of the ar utility maintainer: po...@freebsd.org status: IGNORE deprecated because: part of the base system expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=bsdar portname: archivers/bzip description:A block-sorting file compressor maintainer: po...@freebsd.org status: BROKEN deprecated because: unfetchable; use archivers/bzip2 instead expiration date:2011-10-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=bzip portname: astro/gkrellsun description:A Gkrellm-Plugin that displays the local sun rise and sun set times maintainer: po...@freebsd.org deprecated because: Abandonware expiration date:2011-09-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=astro&portname=gkrellsun portname: astro/xrmap description:Map portions of the earth from a given longitude/latitude maintainer: po...@freebsd.org deprecated because: No more distfiles expiration date:2011-09-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=astro&portname=xrmap portname: audio/gkrellmss description:A plugin for GKrellM with a VU meter showing left/right channel audio maintainer: po...@freebsd.org deprecated because: Abandonware expiration date:2011-09-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gkrellmss portname: audio/gnapster description:GNOME client for the online mp3 community called napster maintainer: po...@freebsd.org deprecated because: Abandonware expiration date:2011-09-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gnapster portname: audio/linux-shoutcast description:Nullsoft's streaming audio server (Linux binary port) maintainer: po...@freebsd.org status: BROKEN deprecated because: unfetchable; website rearranged expiration date:2011-10-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-shoutcast portname: audio/midimountain description:MIDI sequencer maintainer: po...@freebsd.org deprecated because: Abandonware expiration date:2011-09-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=midimountain portname: audio/orpheus description:Light-weight console UI audio player application maintainer: po...@freebsd.org deprecated because: Contains problem with autotools, security CVE-2005-3863. Use audio/cmus instead expiration date:2011-10-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=orpheus portname: audio/shoutcast description:Nullsoft's streaming audio server (binary port) maintainer: po...@freebsd.org status: BROKEN deprecated because: unfetchable; website rearranged expiration date:2011-10-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=shoutcast portname: audio/xmms-sid description:XMMS input plugin to play SID files maintainer: po...@freebsd.org deprecated because: Relies on audio/libsidplay, which is deprecated expiration date:2011-09-30 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=xmms-sid portname: chinese/auto-cn-l10n description:The automatic localization for Simplified Chinese zh_CN.eucCN locale maintainer: po...@freebsd.org deprecated because: No more public distfiles expiration date:
FreeBSD unmaintained ports which are currently marked forbidden
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as "forbidden" in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: math/mupad forbidden because: Relies on xpm, vulnerable since 2004-09-15, http://portaudit.freebsd.org/ef253f8b-0727-11d9-b45d-000c41e2cdad.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=math&portname=mupad portname: net-p2p/torrentflux forbidden because: Vulnerable since 2006-10-07, http://portaudit.freebsd.org/72f21372-55e4-11db-a5ae-00508d6a62df.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-p2p&portname=torrentflux portname: net/tptest forbidden because: Vulnerable since 2009-12-17, http://portaudit.freebsd.org/5486669e-ea9f-11de-bd9c-00215c6a37bb.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=tptest portname: security/cfs forbidden because: Buffer overflows allow remote attackers to cause DoS / execute arbitrary code build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=cfs portname: security/pgp6 forbidden because: Vulnerable since 2005-07-31, http://portaudit.freebsd.org/8375a73f-01bf-11da-bc08-0001020eed82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=pgp6 portname: www/plone forbidden because: Vulnerable since 2011-02-10, http://portaudit.freebsd.org/7c492ea2-3566-11e0-8e81-0022190034c0.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=plone portname: www/rt36 forbidden because: Vulnerable since 2009-12-09, http://portaudit.freebsd.org/714c1406-e4cf-11de-883a-003048590f9e.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=rt36 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as "forbidden" in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: math/mupad forbidden because: Relies on xpm, vulnerable since 2004-09-15, http://portaudit.freebsd.org/ef253f8b-0727-11d9-b45d-000c41e2cdad.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=math&portname=mupad portname: net-p2p/torrentflux forbidden because: Vulnerable since 2006-10-07, http://portaudit.freebsd.org/72f21372-55e4-11db-a5ae-00508d6a62df.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-p2p&portname=torrentflux portname: net/tptest forbidden because: Vulnerable since 2009-12-17, http://portaudit.freebsd.org/5486669e-ea9f-11de-bd9c-00215c6a37bb.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=tptest portname: security/cfs forbidden because: Buffer overflows allow remote attackers to cause DoS / execute arbitrary code build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=cfs portname: security/pgp6 forbidden because: Vulnerable since 2005-07-31, http://portaudit.freebsd.org/8375a73f-01bf-11da-bc08-0001020eed82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=pgp6 portname: www/plone forbidden because: Vulnerable since 2011-02-10, http://portaudit.freebsd.org/7c492ea2-3566-11e0-8e81-0022190034c0.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=plone portname: www/pyblosxom forbidden because: Vulnerable since 2009-02-11 http://portaudit.freebsd.org/b07f3254-f83a-11dd-85a4-ea653f0746ab.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=pyblosxom portname: www/rt36 forbidden because: Vulnerable since 2009-12-09, http://portaudit.freebsd.org/714c1406-e4cf-11de-883a-003048590f9e.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=rt36 portname: www/seamonkey2 forbidden because: several security vulnerabilities build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=seamonkey2 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
