FreeBSD Port: phpbb-3.0.5
Hello, I want to install phpBB on my SRV. I see the 3.0.6 is just released on 17 november. Do you know when you upgrade the port ? Regards, David KINER ___ 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
rc.d scripts and REQUIRE part
Hello, I am trying to understand how to customize rc.d scripts to get the right startup sequence for all daemons. Seems we have (my case havp, but it is also the same problem for example monit) : /usr/local/etc/rc.d/havp : # PROVIDE: havp # REQUIRE: DAEMON cleanvar # BEFORE: LOGIN But in my configuration, I need ... clamd to be started before havp. I have no garantee that clamd is started before havp. Is there any hint (I had a look in handbook, but didn't find yet) a way to add some REQUIRE stuff for a rc script inside, for example /etc/rc.conf ? Thanks, Xavier -- Association KAZAR - http://kazar.net/ Non profit hosting for anybody ___ 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: rc.d scripts and REQUIRE part
On Fri, 20 Nov 2009 11:38:58 +0100 Xavier Beaudouin k...@oav.net replied: Hello, I am trying to understand how to customize rc.d scripts to get the right startup sequence for all daemons. Seems we have (my case havp, but it is also the same problem for example monit) : /usr/local/etc/rc.d/havp : # PROVIDE: havp # REQUIRE: DAEMON cleanvar # BEFORE: LOGIN But in my configuration, I need ... clamd to be started before havp. Change to: # REQUIRE: DAEMON cleanvar clamd You also might try in the '/usr/local/etc/rc.d/clamav-clamd' file adding: # BEFORE: havp Do not remove any entries all ready listed there. I think the first method would be your best solution however. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | If life gives you lemons, make lemonade. ___ 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 Port: oracle8-client-0.2.0_1
Is it possible some how install this PHP extension (PHP5-OCI8) with oracle_client on FBSD 7.2 AMD64? === oracle8-client-0.2.0_1 is only for i386, while you are running amd64. *** Error code 1 Stop in /usr/ports/databases/oracle8-client. *** Error code 1 I undestand that it's not supported on 64bit FBSD...but in real life is it possible somehow to get work? Maybe through linux_base emulator etc? ___ 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: rc.d scripts and REQUIRE part
On Fri, Nov 20, 2009 at 11:38:58AM +0100, Xavier Beaudouin wrote: ... I am trying to understand how to customize rc.d scripts to get the right startup sequence for all daemons. ... But in my configuration, I need ... clamd to be started before havp. I have no garantee that clamd is started before havp. Is there any hint (I had a look in handbook, but didn't find yet) a way to add some REQUIRE stuff for a rc script inside, for example /etc/rc.conf ? See [man pages] rc.d(8) and rcorder(8). Use rcorder to see what the order will be. Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgp4ZkZKgb1wi.pgp Description: PGP signature
Re: FreeBSD Port: oracle8-client-0.2.0_1
On Fri, 20 Nov 2009 13:52:39 +0200 Noisex noi...@apollo.lv wrote: Is it possible some how install this PHP extension (PHP5-OCI8) with oracle_client on FBSD 7.2 AMD64? === oracle8-client-0.2.0_1 is only for i386, while you are running amd64. *** Error code 1 Stop in /usr/ports/databases/oracle8-client. *** Error code 1 I undestand that it's not supported on 64bit FBSD...but in real life is it possible somehow to get work? Maybe through linux_base emulator etc? Considering that this port is two years old and support for running 32 bit binaries with AMD64 has greatly improved since then it may just work. It probably depends on which version of FreeBSD you're using. Just comment out the ONLY_FOR_ARCHS line and see what happens. --- Gary Jennejohn ___ 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: rc.d scripts and REQUIRE part
On Fri, 20 Nov 2009 11:38:58 +0100 Xavier Beaudouin k...@oav.net wrote: Hello, I am trying to understand how to customize rc.d scripts to get the right startup sequence for all daemons. Seems we have (my case havp, but it is also the same problem for example monit) : /usr/local/etc/rc.d/havp : # PROVIDE: havp # REQUIRE: DAEMON cleanvar # BEFORE: LOGIN But in my configuration, I need ... clamd to be started before havp. I have no garantee that clamd is started before havp. Is there any hint (I had a look in handbook, but didn't find yet) a way to add some REQUIRE stuff for a rc script inside, for example /etc/rc.conf ? I would suggest that you don't modify any scripts because you will have to maintain them. I'd create some dummy scripts in /usr/local/etc to provide the ordering e.g. #!/bin/sh # # PROVIDE: PREHAVP # REQUIRE: clamd # BEFORE: havp ___ 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: open64 fbsd port?
On Fri, Nov 20, 2009 at 04:47:41PM +, Anton Shterenlikht wrote: Is there a fbsd port of open64 (http://www.open64.net/), or any branched project? In particular there is a mention of ORC (http://ipf-orc.sourceforge.net/) specifically for ia64, but the pages are very out of date. And then there's something called Aurora, which seems to be the same as ORC (http://sourceforge.net/projects/ipf-orc/), but also *very* out of date. And also there is OpenUH, primarilily for ia64, but linux: OpenUH Source code, IA-64, Red Hat Enterprise Linux AS release 3 and gcc 3.x openuh-alpha.src.tar.gz 90.2 MB and Path64 (http://www.path64.com/) I understand no fbsd ports for these compilers exist yet? -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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
open64 fbsd port?
Is there a fbsd port of open64 (http://www.open64.net/), or any branched project? In particular there is a mention of ORC (http://ipf-orc.sourceforge.net/) specifically for ia64, but the pages are very out of date. And then there's something called Aurora, which seems to be the same as ORC (http://sourceforge.net/projects/ipf-orc/), but also *very* out of date. I'm confused many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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: open64 fbsd port?
On Nov 20, 2009, at 8:47 AM, Anton Shterenlikht wrote: Is there a fbsd port of open64 (http://www.open64.net/), or any branched project? Not at this time. In particular there is a mention of ORC (http://ipf-orc.sourceforge.net/) specifically for ia64, but the pages are very out of date. open64 includes ORC. I believe ORC is EOL. And then there's something called Aurora, which seems to be the same as ORC (http://sourceforge.net/projects/ipf-orc/), but also *very* out of date. They probably renamed the project. It does look like the same thing. FYI, -- Marcel Moolenaar xcl...@mac.com ___ 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: open64 fbsd port?
On Nov 20, 2009, at 9:01 AM, Anton Shterenlikht wrote: On Fri, Nov 20, 2009 at 04:47:41PM +, Anton Shterenlikht wrote: Is there a fbsd port of open64 (http://www.open64.net/), or any branched project? In particular there is a mention of ORC (http://ipf-orc.sourceforge.net/) specifically for ia64, but the pages are very out of date. And then there's something called Aurora, which seems to be the same as ORC (http://sourceforge.net/projects/ipf-orc/), but also *very* out of date. And also there is OpenUH, primarilily for ia64, but linux: OpenUHSource code, IA-64, Red Hat Enterprise Linux AS release 3 and gcc 3.x openuh-alpha.src.tar.gz 90.2 MB Looks like a branch off of Open64. and Path64 (http://www.path64.com/) I don't believe Path64 has an ia64 backend (it's optimized for amd64), but that may be pulled from Open64. I think Path64 may be a better investment than Open64 (for FreeBSD), if the project is more open... I understand no fbsd ports for these compilers exist yet? Correct. -- Marcel Moolenaar xcl...@mac.com ___ 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
Update claws-mail
Claws Mail 3.7.3 was released on 09 October 2009. Usually when claws-mail is updated, the new version appears in the ports tree within a week. I was just wondering why there is an extended delay in releasing this new version? -- Jerry ges...@yahoo.com |=== |=== |=== |=== | Support your right to bare arms! A message from the National Short-Sleeved Shirt Association ___ 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: Update claws-mail
Jerry, There is PR to update of claws-mail. See: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/139467 It will be committed soon. Thanks, Sylvio Cesar. 2009/11/20 Jerry ges...@yahoo.com: Claws Mail 3.7.3 was released on 09 October 2009. Usually when claws-mail is updated, the new version appears in the ports tree within a week. I was just wondering why there is an extended delay in releasing this new version? -- Jerry ges...@yahoo.com |=== |=== |=== |=== | Support your right to bare arms! A message from the National Short-Sleeved Shirt Association ___ 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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Update claws-mail
Hi-- On Nov 20, 2009, at 1:07 PM, Sylvio Cesar wrote: There is PR to update of claws-mail. See: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/139467 It will be committed soon. It's quite useful for people to try the patches for updates that they are interested in, and report back whether the update works well for them. Especially if the ports tree is in a freeze or slush period (ie, say for 8.0 release), portmgr folks like to see independent confirmation that changes work as expected... Regards, -- -Chuck ___ 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: cvs commit: ports/net/pptpclient Makefile
The Restless Daemon identified a PLIST error while trying to build: pptpclient-1.7.2_4 maintained by po...@freebsd.org Makefile ident: $FreeBSD: ports/net/pptpclient/Makefile,v 1.24 2009/11/20 21:49:25 lippe Exp $ Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/pptpclient-1.7.2_4.log : risk to the system. FreeBSD makes no guarantee about the security of ports included in the Ports Collection. Please type 'make deinstall' to deinstall the port if this is a concern. For more information, and contact details about the security status of this software, see the following webpage: http://pptpclient.sourceforge.net/ phase 7: make package === Building package for pptpclient-1.7.2_4 tar: sbin/pptpsetup: Cannot stat: No such file or directory tar: etc/pptpclient/ppp.conf: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 Creating package /tmp/packages/All/pptpclient-1.7.2_4.tbz Registering depends: perl-5.8.9_3. Creating bzip'd tar ball in '/tmp/packages/All/pptpclient-1.7.2_4.tbz' *** Error code 1 Stop in /a/ports/net/pptpclient. Deleting pptpclient-1.7.2_4 pkg_delete: file '/usr/local/sbin/pptpsetup' doesn't exist pkg_delete: file '/usr/local/etc/pptpclient/ppp.conf' doesn't exist pkg_delete: file '/usr/local/etc/pptpclient' doesn't exist pkg_delete: unable to completely remove directory '/usr/local/etc/pptpclient' pkg_delete: couldn't entirely delete package (perhaps the packing list is incorrectly specified?) === Checking filesystem state Deleting perl-5.8.9_3 Removing stale symlinks from /usr/bin... Removing /usr/bin/perl Removing /usr/bin/perl5 Done. Cleaning up /etc/make.conf... Done. Cleaning up /etc/manpath.config... Done. === Checking filesystem state after all packages deleted build of /usr/ports/net/pptpclient ended at Fri Nov 20 21:54:24 UTC 2009 PortsMon page for the port: http://portsmon.freebsd.org/portoverview.py?category=netportname=pptpclient The build which triggered this BotMail was done under tinderbox-devel-3.2_5; dsversion: 3.2 on RELENG_7 on amd64, kern.smp.cpus: 1 with tinderd_flags=-nullfs -plistcheck -onceonly and ccache support, with the official up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- QAT - your friendly neighborhood Daemon, preparing a heck of an error trapping system: - HMC and EOI? - Halt, Melt and Catch fire or Execute Operator Immediately. ___ 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: rc.d scripts and REQUIRE part
RW wrote: On Fri, 20 Nov 2009 11:38:58 +0100 Xavier Beaudouin k...@oav.net wrote: Hello, I am trying to understand how to customize rc.d scripts to get the right startup sequence for all daemons. Seems we have (my case havp, but it is also the same problem for example monit) : /usr/local/etc/rc.d/havp : # PROVIDE: havp # REQUIRE: DAEMON cleanvar # BEFORE: LOGIN But in my configuration, I need ... clamd to be started before havp. I have no garantee that clamd is started before havp. Is there any hint (I had a look in handbook, but didn't find yet) a way to add some REQUIRE stuff for a rc script inside, for example /etc/rc.conf ? To answer this question directly, no. I would suggest that you don't modify any scripts because you will have to maintain them. I'd create some dummy scripts in /usr/local/etc to provide the ordering e.g. #!/bin/sh # # PROVIDE: PREHAVP # REQUIRE: clamd # BEFORE: havp I think we're in a great stage of rc.d adoption when a user is able to provide another user the exactly correct answer. :) One tiny correction, you would want to put this dummy script in /usr/local/etc/rc.d/. Also make sure that it's set executable (chmod 755). The name of the script won't matter, but it's generally a good idea to make the name of the file match what's in the PROVIDE line to make debugging easier. hth, Doug -- Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ 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: audio/ccaudio broken because: Does not build with libtool 2.2. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=ccaudio portname: audio/py-libmpdclient broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/py26-libmpdclient-0.10.0.log (_Aug_23_08:38:53_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=py-libmpdclient portname: chinese/gbk2uni broken because: does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=gbk2uni portname: chinese/iiimf-le-xcin broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/zh-iiimf-le-xcin-0.1.7_5.log (_Aug_23_08:39:47_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=iiimf-le-xcin portname: devel/ace+tao broken because: Does not compile on FreeBSD = 7.0 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=ace%2Btao portname: devel/adabindx broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=adabindx portname: devel/agide broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=agide portname: devel/asis broken because: Does not build after gpl 2009 update to lang/gnat build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=asis portname: devel/callgrind broken because: does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=callgrind 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=develportname=fampp portname: devel/florist broken because: Does not build after gpl 2009 update to lang/gnat build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=florist portname: devel/p5-ORBit broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=p5-ORBit portname: editors/xml2rfc-xxe broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=editorsportname=xml2rfc-xxe portname: emulators/snes9express broken because: Does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=snes9express portname: graphics/gephex broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/gephex-0.4.4_1.log
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: audio/ccaudio broken because: Does not build with libtool 2.2. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=ccaudio portname: audio/dino broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=dino portname: audio/ecamegapedal broken because: does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.8.20091115185923/ecamegapedal-0.4.4_4.log (_Nov_15_19:50:27_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=ecamegapedal portname: audio/ecawave broken because: does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20091113082031/ecawave-0.6.1_5.log (_Nov_15_03:02:38_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=ecawave portname: audio/emu10kx broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=emu10kx portname: audio/gmpc-mserver broken because: fails to build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=gmpc-mserver portname: audio/py-libmpdclient broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/py26-libmpdclient-0.10.0.log (_Aug_23_08:38:53_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=py-libmpdclient portname: biology/dotter broken because: checksum mismatch build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.20091113232800/dotter-20021204.log (_Nov_14_20:15:45_UTC_2009) http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/dotter-20021204.log (_Aug_17_05:33:45_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=biologyportname=dotter portname: cad/alliance broken because: does not compile build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=cadportname=alliance portname: chinese/gbk2uni broken because: does not fetch build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=gbk2uni portname: chinese/iiimf-le-xcin broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/zh-iiimf-le-xcin-0.1.7_5.log (_Aug_23_08:39:47_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=chineseportname=iiimf-le-xcin portname: comms/hcfmdm broken because: Does not compile at 7.x or higher build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=commsportname=hcfmdm portname: converters/mimelib broken because: Does not compile with GCC 4.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=convertersportname=mimelib portname: databases/erserver broken because: Does not
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: devel/callgrind description:Valgrind skin for cache simulation and call tracing maintainer: po...@freebsd.org status: BROKEN deprecated because: Included in devel/valgrind expiration date:2009-10-30 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=callgrind portname: lang/gcl description:GNU Common Lisp maintainer: po...@freebsd.org status: BROKEN deprecated because: fails to build on FreeBSD 7.x expiration date:2010-01-12 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=langportname=gcl portname: net-mgmt/net-snmp4 description:An extendable SNMP implementation maintainer: po...@freebsd.org deprecated because: Use net-mgmt/net-snmp port instead expiration date:2009-07-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmtportname=net-snmp4 portname: net-mgmt/p5-SNMP description:A perl5 module for interfacing with the CMU SNMP library maintainer: po...@freebsd.org deprecated because: Perl SNMP module is now a part of net-mgmt/net-snmp expiration date:2009-08-15 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmtportname=p5-SNMP portname: www/jakarta-tomcat4 description:Open-source Java web server by Apache, stable 4.0.x branch maintainer: po...@freebsd.org deprecated because: www/jakarta-tomcat5 is recommended instead for new installations expiration date:2009-01-12 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=jakarta-tomcat4 portname: www/jakarta-tomcat5 description:Open-source Java web server by Apache, 5.0.x branch maintainer: po...@freebsd.org deprecated because: Old version, consider using www/tomcat55 or www/tomcat6 instead expiration date:2009-01-12 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=jakarta-tomcat5 portname: www/mod_auth_mysql41_ap2 description:MySQL 4.1 and Apache 2 port of mod_auth_mysql maintainer: po...@freebsd.org status: IGNORE deprecated because: distfile no longer fetchable expiration date:2009-10-17 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=mod_auth_mysql41_ap2 portname: x11-toolkits/gtkscintilla description:A wrapper for the Scintilla editing component maintainer: po...@freebsd.org status: BROKEN deprecated because: no longer under development, last release in 2002 expiration date:2009-10-13 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/gtkscintilla-0.8.2_6.log (_Aug_16_11:57:48_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=gtkscintilla portname: x11-toolkits/p5-Gnome description:The main Gnome module of Gtk-Perl maintainer: po...@freebsd.org status: BROKEN deprecated because: Has been broken for more than 6 months expiration date:2008-09-19 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=p5-Gnome portname: x11-toolkits/py-gtkscintilla description:A Python bindings for gtkscintilla library maintainer: po...@freebsd.org status: BROKEN deprecated because: no longer under development, last release in 2002 expiration date:2009-10-13 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=py-gtkscintilla portname: x11-toolkits/xclasses description:C++ layout library for X maintainer: po...@freebsd.org deprecated because: Version branch long since retired expiration date:2007-10-28 build errors: none. overview:
FreeBSD 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: audio/squeezecenter description:Slim Devices audio streaming server maintainer: bro...@freebsd.org deprecated because: Replaced by audio/squeezeboxcenter expiration date:2009-11-30 build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.20091113102251/squeezecenter-7.3.3.log (_Nov_14_00:03:36_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=squeezecenter portname: audio/squeezecenter-dynamicplaylist description:SqueezeCenter plugin to create dynamic playlists maintainer: t...@freebsd.org deprecated because: Replaced by audio/squeezeboxserver-dynamicplaylist expiration date:2009-11-30 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=squeezecenter-dynamicplaylist portname: audio/squeezecenter-lazysearch description:SqueezeCenter plugin for performing lazy searches maintainer: t...@freebsd.org deprecated because: Replaced by audio/squeezeboxserver-lazysearch expiration date:2009-11-30 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=squeezecenter-lazysearch portname: audio/squeezecenter-sqlplaylist description:SqueezeCenter plugin to create playlists based on SQL queries maintainer: t...@freebsd.org deprecated because: Replaced by audio/squeezeboxserver-sqlplaylist expiration date:2009-11-30 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=squeezecenter-sqlplaylist portname: audio/squeezecenter-superdatetime description:SqueezeCenter plugin to display weather conditions and forecasts maintainer: t...@freebsd.org deprecated because: Replaced by audio/squeezeboxserver-superdatetime expiration date:2009-11-30 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=squeezecenter-superdatetime portname: audio/squeezecenter-trackstat description:SqueezeCenter plugin to store ratings and statistics about songs maintainer: t...@freebsd.org deprecated because: Replaced by audio/squeezeboxserver-trackstat expiration date:2009-11-30 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=squeezecenter-trackstat portname: devel/callgrind description:Valgrind skin for cache simulation and call tracing maintainer: po...@freebsd.org status: BROKEN deprecated because: Included in devel/valgrind expiration date:2009-10-30 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=callgrind portname: devel/gdb53 description:Source level debugger - GNU GDB 5.3 maintainer: obr...@freebsd.org status: BROKEN deprecated because: has been broken for 3 months expiration date:2010-01-18 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/gdb-5.3_1,1.log (_Aug_17_05:35:15_UTC_2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=gdb53 portname: lang/gcl description:GNU Common Lisp maintainer: po...@freebsd.org status: BROKEN deprecated because: fails to build on FreeBSD 7.x expiration date:2010-01-12 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=langportname=gcl portname: mail/squirrelmail-devel description:A webmail system which accesses mail over IMAP (Development version) maintainer: tabtho...@freebsd.org deprecated because: use mail/squirrelmail expiration date:2010-01-06 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mailportname=squirrelmail-devel portname: math/scilab description:A free Matlab clone by INRIA ENPC maintainer: utis...@googlemail.com deprecated because:
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=databasesportname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=miscportname=compat3x portname: www/firefox forbidden because: too many security issues http://www.vuxml.org/freebsd/922d2398-9e2d-11de-a998-0030843d3802.html http://www.vuxml.org/freebsd/49e8f2ee-8147-11de-a994-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=firefox portname: www/linux-firefox-devel forbidden because: Security issues http://www.vuxml.org/freebsd/f29fea8f-b19f-11dd-a55e-00163e16.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-firefox-devel portname: www/neon26 forbidden because: see CVE-2009-2474 please use neon28 or neon29 instead build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=neon26 ___ 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
