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 7.x/8.x/9.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: audio/teamspeak_client broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=teamspeak_client portname: chinese/big5con broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=big5con portname: chinese/hztty broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=hztty portname: databases/adstudio broken because: incomplete plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=adstudio portname: databases/grass broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=grass portname: databases/msql broken because: Broken on FreeBSD 9+ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=msql portname: databases/xapian-bindings10 broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=xapian-bindings10 portname: deskutils/simpleagenda broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=simpleagenda portname: devel/dsss broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=dsss portname: devel/fnccheck broken because: does not link build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.9.20121011194400/fnccheck-3.2.0.log (_Oct_21_00:37:47_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=fnccheck portname: devel/gauche-gaunit broken because: does not package build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=gauche-gaunit portname: devel/gcvs broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=gcvs portname: devel/linux-js broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linux-js portname: devel/linuxthreads broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linuxthreads portname: devel/lua-posix broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=lua-posix portname: devel/lua50-posix broken because: does not build build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.9.20120820204747/lua50-posix-5.0.log (_Apr__6_15:35:56_UTC_2012) overview:
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 7.x/8.x/9.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: accessibility/yasr broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibility&portname=yasr portname: audio/gdam broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gdam portname: audio/hydrogen broken because: does not install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=hydrogen portname: audio/sphinx3 broken because: does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20121001063541/sphinx3-0.7.log (_Sep_25_17:40:18_UTC_2012) http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.8.20120903060906/sphinx3-0.7.log (_Sep_10_18:56:45_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=sphinx3 portname: audio/teamspeak_client broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=teamspeak_client portname: benchmarks/polygraph31 broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=benchmarks&portname=polygraph31 portname: cad/brlcad broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=brlcad portname: cad/meshlab broken because: does not build build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.10.20120628171716/meshlab-1.2.3_2.log (_Jul_16_09:33:26_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=meshlab portname: cad/salome-gui broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=salome-gui portname: chinese/big5con broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=big5con portname: chinese/cxterm broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=cxterm portname: chinese/hztty broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=hztty portname: comms/hso-kmod broken because: does not build with USB2, please try comms/uhso-kmod instead build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=hso-kmod portname: comms/ib-kmod broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=ib-kmod portname: comms/uticom broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py
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: audio/linux-alsa-lib description:The Advanced Linux Sound Architecture libraries maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-alsa-lib portname: audio/linux-arts description:Audio system for the KDE integrated X11 desktop (Linux version) maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-arts portname: audio/linux-freealut description:A free implementation of OpenAL's ALUT standard (Linux version) maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-freealut portname: audio/linux-libmad description:Libmad library (part of MAD project) maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-libmad portname: audio/linux-libogg description:Ogg bitstream library (Linux version) maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-libogg portname: audio/linux-libvorbis description:Audio compression codec library (Linux version) maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-libvorbis portname: audio/linux-openal description:A 3D positional spatialized sound library (Linux version) maintainer: po...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-openal portname: devel/aifad description:Machine learning system maintainer: po...@freebsd.org deprecated because: No more public distfiles expiration date:2012-11-26 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=aifad portname: devel/libgetline description:A small, portable, and easy to use command line library maintainer: po...@freebsd.org deprecated because: Upstream disapear and distfile is no more available expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=libgetline portname: devel/looks description:The JGoodies Looks improve the appearance of your Java applications maintainer: po...@freebsd.org deprecated because: No more public distfiles expiration date:2012-10-20 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=looks portname: devel/ocaml-cfg description:Library for manipulation of context-free grammars maintainer: po...@freebsd.org deprecated because: No more public distfiles expiration date:2012-11-26 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=ocaml-cfg portname: devel/ocaml-lacaml description:OCaml interface to BLAS and LAPACK libraries maintainer:
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: lang/eperl forbidden because: Vulnerable since 2001-06-21, http://portaudit.freebsd.org/73efb1b7-07ec-11e2-a391-000c29033c32.html build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.20101015091133/eperl-2.2.14_3.log.bz2 (_Jul_31_06:17:35_UTC_2010) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=eperl portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ 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: web FreeBSD Ports Search is out of sync
On Sun, Dec 2, 2012 at 11:47 AM, Matthew Seaman wrote: > On 02/12/2012 09:32, Ion-Mihai Tetcu wrote: >>> If you're running 2.9 OPTIONSng should be handled correctly. It >>> > doesn't matter much: the exact format of the OPTIONS variables >>> > doesn't make much difference to building the INDEX, only detecting >>> > when they've been changed. > >> # pkg info p5-FreeBSD-Portindex >> p5-FreeBSD-Portindex-2.9 Incremental FreeBSD ports INDEX file >> generation >> >> So what exactly are you checking WRT option files? > > Basically, just the timestamp on the file. If it's newer than the last > time cache-update was run, then the corresponding port needs rechecking. > > Or if there is a new options file. The 'unknown options file' error > comes about by comparing the makefiles included from the ports with the > contents of the /var/db/ports directory. > > ... and thinking about it, after the benefit of sufficient coffee, it's > now clear to me that logic is incorrect: it can't distinguish between a > newly created options file and a leftover from a removed port. > > Does no harm, but won't work out that because there's a new options file > at least one port needs rechecking, or identify the port(s) to recheck. > I should fix that. > > Cheers, > > Matthew > Hi Matthew, With the latest 3.0 version of p5-FreeBSD-PortIndex I get an error at the end of portindex run: Accumulating dependency information: .[1000].[2000].[3000].[4000].[5000].[6000].[7000].[8000].[9000].[1].[11000].[12000].[13000].[14000].[15000].[16000].[17000].[18000].[19000].[2]Can't locate object method "accumulate_dependencies" via package "FreeBSD::Portindex::Category" at /usr/local/lib/perl5/site_perl/5.14.2/FreeBSD/Portindex/Tree.pm line 815. No INDEX file is generated. -Kimmo ___ 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: last.fm
* ajtiM [Thu, 6 Dec 2012 17:36:40 -0600]: > I got an email about last fm and a new version: > > "We're writing you to let you know that there will soon be a change to > Last.fm > radio that may affect you. Our stats show that you've listened to radio > through > an application that uses our old streaming protocol. On 1 December we will > deprecate this old protocol, so in some applications radio will no longer > work. > > If you would like to continue enjoying Last.fm Radio, consider upgrading to > a > new application or using http://www.last.fm/listen I have prepared a patch to update the port. Unfortunately i have not been able to test it yet. http://people.freebsd.org/~arved/stuff/patch.last.fm Please report back, if it works arved ___ 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: web FreeBSD Ports Search is out of sync
On 07/12/2012 11:09, Kimmo Paasiala wrote: > With the latest 3.0 version of p5-FreeBSD-PortIndex I get an error at > the end of portindex run: > > Accumulating dependency information: > .[1000].[2000].[3000].[4000].[5000].[6000].[7000].[8000].[9000].[1].[11000].[12000].[13000].[14000].[15000].[16000].[17000].[18000].[19000].[2]Can't > locate object method "accumulate_dependencies" via package > "FreeBSD::Portindex::Category" at > /usr/local/lib/perl5/site_perl/5.14.2/FreeBSD/Portindex/Tree.pm line > 815. > > No INDEX file is generated. > > -Kimmo > There was a problem with the www.p5-HTTP-Tiny port overnight (is fixed now) that was causing this sort of symptom. If you update to the latest ports and cache-init again, everything should work properly once more. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk ___ 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: last.fm
On 07.12.2012 12:25 (UTC+2), Tilman Keskinöz wrote: > * ajtiM [Thu, 6 Dec 2012 17:36:40 -0600]: > >> I got an email about last fm and a new version: >> >> "We're writing you to let you know that there will soon be a change to >> Last.fm >> radio that may affect you. Our stats show that you've listened to radio >> through >> an application that uses our old streaming protocol. On 1 December we will >> deprecate this old protocol, so in some applications radio will no longer >> work. >> >> If you would like to continue enjoying Last.fm Radio, consider upgrading to >> a >> new application or using http://www.last.fm/listen > > I have prepared a patch to update the port. > > Unfortunately i have not been able to test it yet. > > http://people.freebsd.org/~arved/stuff/patch.last.fm > > Please report back, if it works I tried your patch with recent CURRENT amd64 (clang) and it appied and built fine. As far as I can say now, it also plays fine. Thanks for the patch, Rainer > arved ___ 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 you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ devel/k8048 | 1.04| 2.03 +-+ sysutils/syslinux | 4.05| 5.00 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portsc...@portscout.freebsd.org Thanks. ___ 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: last.fm
On Friday 07 December 2012 08:37:46 Rainer Hurling wrote: > On 07.12.2012 12:25 (UTC+2), Tilman Keskinöz wrote: > > * ajtiM [Thu, 6 Dec 2012 17:36:40 -0600]: > >> I got an email about last fm and a new version: > >> > >> "We're writing you to let you know that there will soon be a change to > >> Last.fm radio that may affect you. Our stats show that you've listened > >> to radio through an application that uses our old streaming protocol. > >> On 1 December we will deprecate this old protocol, so in some > >> applications radio will no longer work. > >> > >> If you would like to continue enjoying Last.fm Radio, consider > >> upgrading to a > >> > >> new application or using http://www.last.fm/listen > > > > I have prepared a patch to update the port. > > > > Unfortunately i have not been able to test it yet. > > > > http://people.freebsd.org/~arved/stuff/patch.last.fm > > > > Please report back, if it works > > I tried your patch with recent CURRENT amd64 (clang) and it appied and > built fine. As far as I can say now, it also plays fine. > > Thanks for the patch, > Rainer > > > arved Thank you very much. It works on my system :) Mitja http://www.redbubble.com/people/lumiwa ___ 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"
