Re: PHP question
On Wed, 2009-01-14 at 15:26 -0500, Albert Thiel wrote: I am trying to figure out how to get a working Apache 2.x server with PHP in a safe configuration (or as safe as possible based upon all the vulns). I do not need a database. What version and options is my best bet. I have tried on my own but losing it. Nothing I have tried works. This is the wrong list of general PHP setup instructions. PHP4 is dead. PHP5 is nearing beta1 of 5.3. Use 5.2.9 in the mean time. # cd /usr/ports/lang/php5 make config make install Modify your apache22 httpd.conf accordingly to activate the module. There are thousands of sites that explain the proces. Security with PHP involves writing code well, both in your application, and in the PHP engine -- as well as responsible administration: locking out insecure features in php.ini ~BAS signature.asc Description: This is a digitally signed message part
Re: FreeBSD Port: php5-5.2.7
On Sun, 2008-12-07 at 20:25 +0100, Albert Gabàs | Astabis wrote: Dear Ale, I have updated the PHP to 5.2.7 version, and now some code give me the next error: Looks like 5.2.7 got off'd anyway. 5.2.8 pushed. They must be working with the MySQL folks on release engineering... ~BAS signature.asc Description: This is a digitally signed message part
Re: [phing] Updated FreeBSD Phing Port
As we near the 9 month anniversary of this, [er [EMAIL PROTECTED], I recommend that we commit the new version of this port. ~BAS On Fri, 2008-05-30 at 17:11 -0400, Brian A. Seklecki wrote: All: Normally I would say that this PR may be approaching the point where we override the maintainer -- the problem is that I haven't received any feedback from anyone other than my development team. ~BAS On Mon, 2008-04-07 at 11:32 -0400, Brian A. Seklecki wrote: The associated PRs are: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/122450 http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/121791 My draft version of the rewrite is at: http://people.collaborativefusion.com/~seklecki/phing-2.3.0-CFI1.tar I would note that there is a 20-line count diff of the file-contents listing -- someone should dig through it to validate that some files massive list of files has not been added since I originally composed the PLIST back in late October of 2007? I just never filed PR for some reason. Feedback appreciated -- be sure to CC: [EMAIL PROTECTED] with title e: ports/122450: devel/php5-phing redesign TIA, ~BAS On Fri, 2008-04-04 at 12:43 -0400, Brian A. Seklecki wrote: I remember now why I never filed the PR -- the whole thing is fucked. I realized that after I tried to conver the FreeBSD port from a simple do-install: target to use ${PORTSDIR}/devel/pear/bsd.pear.mk: Here are the two big issues that I require guidance with: 1) FreeBSD Ports PEAR subsystem designates pear package contents as either: $TESTS $SCRIPTFILES $SQLS $EXAMPLES $DOCS or $FILES Not the most ambiguous designations ever, but close. Pear packages use categories: script, php, data, doc Could anyone comment on the mappings? 2) The PEAR port is installing a script in $PREFIX/bin/phing as a bourne shell script wrapper around $PREFIX/share/pear/phing.php script /usr/local/bin/phing $ ident /usr/local/bin/phing /usr/local/bin/phing: $Id: pear-phing 123 2006-09-14 20:19:08Z mrook $ Where as we are running some sed(1) statements on: ${WRKSRC}/bin/phing the installing it as ${PREFIX}/bin/phing However, i think some of these post-extract: targets are legacy because one substrpl is: s|/opt/phing|${PREFIX}/lib/php/phing| But: $ grep -i opt \ [../obj]/devel/php5-phing-work/work/phing-2.3.0/bin/phing.php // Set any INI options for PHP No such instances of this string exist any more in phing.php or phing in 2.3.0x I'm filing the PR now and I'll let everyone else fight over the proper solution. ~BAS On Fri, 2008-04-04 at 11:46 -0400, Brian A. Seklecki wrote: On Fri, 2008-04-04 at 11:27 -0400, Brian A. Seklecki wrote: Michiel et. al.: Some of my developers are telling me that they are having some trouble using the stable v2.3.0 in FreeBSD ports. Oh yea, my day is done for: [EMAIL PROTECTED]:/home/seklecki$ wc -l phing_port.txt phing_pear.txt 272 phing_port 301 phing_pear 573 total I have a vague recollection, maybe 6 months ago, converting the FreeBSD port to use the PEAR-framework so that it is properly registered -- spending 18 hours sorting out PLIST differences. What happened? Maybe I forgot to file PR? ~BAS I'm digging for details now -- but I may be related to the path in which the PEAR package installs files v.s. the Port. Any insight into this before I burn my day down? ~BAS On Sun, 7 Oct 2007, Michiel Rook wrote: Hi Brian, We should endeavor to update this to something recent. We'll try this from here and forward results on. That'd be great! The latest release is 2.3.0RC1 - we're hoping to release 2.3.0 soon(ish). regards, Michiel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ Guilty? Yeah. But he knows it. I mean, you're guilty. You just don't know it. So who's really in jail? ~Maynard James Keenan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org
Re: net-snmp5.4.x unusable, PR times out, what should I do next?
On Fri, 2008-05-23 at 13:17 +0200, Helmut Schneider wrote: Hi, I don't blame anyone, I'm sure all of the maintainers have a lot of things to. Rather I would like to know what I should do/can do next. As I'm using If it makes you feel any better, we can get it to segfault with SIGHUP at the top of the hour. (Although we realized that we don't need to HUP it from newsyslog since we're using syslog(3)) OpenBSD's snmpd(8) has HOST-RESOURCES, UCD-MIB, PF-MIB (well, Sensors), and DISKIO-MIB support, supposedly. ~BAS IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [phing] Updated FreeBSD Phing Port
All: Normally I would say that this PR may be approaching the point where we override the maintainer -- the problem is that I haven't received any feedback from anyone other than my development team. ~BAS On Mon, 2008-04-07 at 11:32 -0400, Brian A. Seklecki wrote: The associated PRs are: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/122450 http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/121791 My draft version of the rewrite is at: http://people.collaborativefusion.com/~seklecki/phing-2.3.0-CFI1.tar I would note that there is a 20-line count diff of the file-contents listing -- someone should dig through it to validate that some files massive list of files has not been added since I originally composed the PLIST back in late October of 2007? I just never filed PR for some reason. Feedback appreciated -- be sure to CC: [EMAIL PROTECTED] with title e: ports/122450: devel/php5-phing redesign TIA, ~BAS On Fri, 2008-04-04 at 12:43 -0400, Brian A. Seklecki wrote: I remember now why I never filed the PR -- the whole thing is fucked. I realized that after I tried to conver the FreeBSD port from a simple do-install: target to use ${PORTSDIR}/devel/pear/bsd.pear.mk: Here are the two big issues that I require guidance with: 1) FreeBSD Ports PEAR subsystem designates pear package contents as either: $TESTS $SCRIPTFILES $SQLS $EXAMPLES $DOCS or $FILES Not the most ambiguous designations ever, but close. Pear packages use categories: script, php, data, doc Could anyone comment on the mappings? 2) The PEAR port is installing a script in $PREFIX/bin/phing as a bourne shell script wrapper around $PREFIX/share/pear/phing.php script /usr/local/bin/phing $ ident /usr/local/bin/phing /usr/local/bin/phing: $Id: pear-phing 123 2006-09-14 20:19:08Z mrook $ Where as we are running some sed(1) statements on: ${WRKSRC}/bin/phing the installing it as ${PREFIX}/bin/phing However, i think some of these post-extract: targets are legacy because one substrpl is: s|/opt/phing|${PREFIX}/lib/php/phing| But: $ grep -i opt \ [../obj]/devel/php5-phing-work/work/phing-2.3.0/bin/phing.php // Set any INI options for PHP No such instances of this string exist any more in phing.php or phing in 2.3.0x I'm filing the PR now and I'll let everyone else fight over the proper solution. ~BAS On Fri, 2008-04-04 at 11:46 -0400, Brian A. Seklecki wrote: On Fri, 2008-04-04 at 11:27 -0400, Brian A. Seklecki wrote: Michiel et. al.: Some of my developers are telling me that they are having some trouble using the stable v2.3.0 in FreeBSD ports. Oh yea, my day is done for: [EMAIL PROTECTED]:/home/seklecki$ wc -l phing_port.txt phing_pear.txt 272 phing_port 301 phing_pear 573 total I have a vague recollection, maybe 6 months ago, converting the FreeBSD port to use the PEAR-framework so that it is properly registered -- spending 18 hours sorting out PLIST differences. What happened? Maybe I forgot to file PR? ~BAS I'm digging for details now -- but I may be related to the path in which the PEAR package installs files v.s. the Port. Any insight into this before I burn my day down? ~BAS On Sun, 7 Oct 2007, Michiel Rook wrote: Hi Brian, We should endeavor to update this to something recent. We'll try this from here and forward results on. That'd be great! The latest release is 2.3.0RC1 - we're hoping to release 2.3.0 soon(ish). regards, Michiel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ Guilty? Yeah. But he knows it. I mean, you're guilty. You just don't know it. So who's really in jail? ~Maynard James Keenan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports Request: OpenNMS
On Fri, 2008-04-11 at 09:34 -0400, Paul Pathiakis wrote: Hi, This is another request for someone to port OpenNMS to a FreeBSD port. www.opennms.org http://www.opennms.org/ This is a work of art that is well worthwhile beyond Tivoli and HP-Openview. Oh come on now! You've just never had the pleasure (cut 50/50 with agonizing pain) of NetCool Omninbus! ~BAS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: net-mgmt/nagios-devel is 2 versions behind..
On Mon, 2007-11-26 at 15:13 -0500, Chris Haulmark wrote: On Mon, Nov 26, 2007 at 12:00:33PM -0500, Chris Haulmark wrote: Currently it is nagios-devel 3.0.b5. Can someone please update it to nagios-devel 3.0.b7. Plus there was a crazy threading issue with B7. I'll submit details in a second. ~BAS We have Portsfreeze, if you want a patch feel free to try the following: http://miwi.homeunix.com/nagios-devel.diff Appreciate it! - - Martin - -- +---+---+ | PGP: 0x05682353 | Jabber : miwi(at)BSDCrew.de | | ICQ: 169139903 | Mail : miwi(at)FreeBSD.org | +---+---+ | Mess with the Best, Die like the Rest! | +---+---+ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHSv0vFwpycAVoI1MRAjQLAJ4+ERXVNUfnl6qnvFX503cgnDA6GACgjSDh MuQlytcjbfDcvhgoILKzIAU= =c2pA -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
bsd.pear.mk and EXTRACT_SUFX=.tgz
Is it safe to assume that 99% of PEAR packages, distributed either via web or PEAR channels have a .tgz suffix, thus justifying: EXTRACT_SUFX= .tgz As a global override? Why is PHING the exception? Is there are a gzip'd tarball dist? Your search - phing-2.3.0.tgz - did not match any documents. ~BAS $ ls /usr/ports/distfiles/PEAR/ total 1164 drwxr-xr-x 2 root wheel 512 Nov 6 09:53 ./ drwxr-xr-x 16 root wheel7680 Oct 31 16:35 ../ -rw-r--r-- 1 root wheel9506 Jun 22 21:25 Benchmark-1.2.7.tgz -rw-r--r-- 1 root wheel4593 Nov 14 2005 HTTP-1.4.0.tgz -rw-r--r-- 1 root wheel6396 Jun 11 2004 HTTP_Client-1.0.0.tgz -rw-r--r-- 1 root wheel 38479 May 14 02:46 Log-1.9.11.tgz -rw-r--r-- 1 root wheel4404 Jan 26 2005 MIME_Type-1.0.0.tgz -rw-r--r-- 1 root wheel5441 May 4 2007 Net_Socket-1.0.8.tgz -rw-r--r-- 1 root wheel6303 Jun 28 10:58 Net_URL-1.0.15.tgz -rw-r--r-- 1 root wheel 43190 Dec 27 2005 PHPUnit2-2.3.4.tgz -rw-r--r-- 1 root wheel 69948 Jun 29 11:10 SOAP-0.11.0.tgz -rw-r--r-- 1 root wheel 15753 Feb 5 2006 Text_Diff-0.2.1.tgz -rw-r--r-- 1 root wheel 13476 Dec 1 2006 XML_Parser-1.2.8.tgz -rw-r--r-- 1 root wheel 932889 Nov 4 09:44 phing-2.3.0.zip ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Updated FreeBSD Port - Phing 2.3.0 [Fwd: bsd.pear.mk and EXTRACT_SUFX=.tgz]
Never mind, there's a source .zip file separate from the pear channel package at http://pear.phing.info/get/phing-$VER.tgz Updated FreeBSD ports port: http://people.collaborativefusion.com/~seklecki/phing_230_fbsd_p.tar Utilizes the bsd.pear.mk infrastructure and the CATEGORY=phing hack to ensure ${LOCALBASE}/usr/share/phing is docroot for all FILES={..}. [EMAIL PROTECTED]:/export/ports/devel/php5-phing$ portlint FATAL: Makefile: no ports collection makefile for line in comment FATAL: Makefile: no Whom line in comment section. FATAL: Makefile: no Date created line in comment section. WARN: Makefile: only one MASTER_SITE configured. Consider adding .. WARN: Makefile: BUILD_DEPENDS has to appear earlier. WARN: Makefile: RUN_DEPENDS has to appear earlier. 3 fatal errors and 3 warnings found. $ pkg_info -L pear-phing-2.3.0 | wc -l 289 [EMAIL PROTECTED]:/tmp$ phing -V Unknown argument: -Vphing [options] [target [target2 [target3] ...]] Options: -h -help print this message -l -list list available targets in this project -v -versionprint the version information and exit -q -quiet be extra quiet -verbose be extra verbose -debug print debugging information -logfile fileuse given file for log -logger classnamethe class which is to perform logging -f -buildfile file use given buildfile -Dproperty=value use value for given property -find file search for buildfile towards the root of the filesystem and use it Report bugs to [EMAIL PROTECTED] [EMAIL PROTECTED]:/tmp$ phing -v Phing version 2.3.0 $ pear list -a Installed packages, channel pear.phing.info: Package Version State phing 2.3.0 stable $ pkg_info -L pear-phing-2.3.0 Information for pear-phing-2.3.0: Files: /usr/local/share/pear/phing/etc/log.xsl /usr/local/share/pear/phing/etc/phpunit2-noframes.xsl /usr/local/share/pear/phing/etc/phpunit2-frames.xsl /usr/local/share/pear/phing/etc/coverage-frames.xsl /usr/local/share/pear/phing/etc/str.replace.function.xsl /usr/local/share/pear/phing/etc/VERSION.TXT /usr/local/share/pear/phing/bin/pear-phing.bat /usr/local/share/pear/phing/bin/pear-phing /usr/local/share/pear/phing/bin/phing.php /usr/local/share/pear/phing/CHANGELOG /usr/local/share/pear/phing/TODO /usr/local/share/pear/phing/CREDITS /usr/local/share/pear/phing/README /usr/local/share/pear/phing/IntrospectionHelper.php /usr/local/share/pear/phing/ProjectComponent.php /usr/local/share/pear/phing/BuildLogger.php /usr/local/share/pear/phing/TaskContainer.php /usr/local/share/pear/phing/BuildEvent.php /usr/local/share/pear/phing/Task.php /usr/local/share/pear/phing/TaskAdapter.php /usr/local/share/pear/phing/Phing.php /usr/local/share/pear/phing/RuntimeConfigurable.php /usr/local/share/pear/phing/BuildListener.php /usr/local/share/pear/phing/Project.php /usr/local/share/pear/phing/UnknownElement.php /usr/local/share/pear/phing/BuildException.php /usr/local/share/pear/phing/Target.php /usr/local/share/pear/phing/util/regexp/RegexpEngine.php /usr/local/share/pear/phing/util/regexp/Regexp.php /usr/local/share/pear/phing/util/regexp/PregEngine.php /usr/local/share/pear/phing/util/SourceFileScanner.php /usr/local/share/pear/phing/util/ExtendedFileStream.php /usr/local/share/pear/phing/util/DirectoryScanner.php /usr/local/share/pear/phing/util/LogWriter.php /usr/local/share/pear/phing/util/FileUtils.php /usr/local/share/pear/phing/util/StringHelper.php /usr/local/share/pear/phing/util/PathTokenizer.php /usr/local/share/pear/phing/filters/util/IniFileTokenReader.php /usr/local/share/pear/phing/filters/util/ChainReaderHelper.php /usr/local/share/pear/phing/filters/LineContainsRegexp.php /usr/local/share/pear/phing/filters/ChainableReader.php /usr/local/share/pear/phing/filters/ExpandProperties.php /usr/local/share/pear/phing/filters/TailFilter.php /usr/local/share/pear/phing/filters/ReplaceTokens.php /usr/local/share/pear/phing/filters/XsltFilter.php /usr/local/share/pear/phing/filters/StripLineBreaks.php /usr/local/share/pear/phing/filters/StripLineComments.php /usr/local/share/pear/phing/filters/TranslateGettext.php /usr/local/share/pear/phing/filters/BaseFilterReader.php /usr/local/share/pear/phing/filters/HeadFilter.php /usr/local/share/pear/phing/filters/TabToSpaces.php /usr/local/share/pear/phing/filters/TidyFilter.php /usr/local/share/pear/phing/filters/StripPhpComments.php /usr/local/share/pear/phing/filters/XincludeFilter.php /usr/local/share/pear/phing/filters/ReplaceRegexp.php /usr/local/share/pear/phing/filters/BaseParamFilterReader.php /usr/local/share/pear/phing/filters/LineContains.php /usr/local/share/pear/phing/filters/PrefixLines.php /usr/local/share/pear/phing/filters/StripWhitespace.php /usr/local/share/pear/phing/mappers/IdentityMapper.php /usr/local/share/pear/phing/mappers/RegexpMapper.php
Re: FreeBSD Port for Testing_Selenium Client PEAR Binding
misc/117872 opened to track new package submission. ~BAS On Fri, 12 Oct 2007, Brian A. Seklecki wrote: Makefile unambiguously stolen from ports/devel/pear-PHPUnit3: http://people.collaborativefusion.com/~seklecki/pear-Testing_Selenium_bas.tar For use in ports/devel/pear-Testing_Selenium/ ~BAS $ pear list-files Testing_Selenium Installed Files For Testing_Selenium Type Install Path doc /usr/local/share/doc/pear/Testing_Selenium/examples/example.php php /usr/local/share/pear/Testing/Selenium/Exception.php test /usr/local/share/pear/tests/Testing_Selenium/tests/html/bug8893.html test /usr/local/share/pear/tests/Testing_Selenium/tests/html/bug9119.html test /usr/local/share/pear/tests/Testing_Selenium/tests/html/bug9189.html test /usr/local/share/pear/tests/Testing_Selenium/tests/AllTests.php test /usr/local/share/pear/tests/Testing_Selenium/tests/BugTest.php test /usr/local/share/pear/tests/Testing_Selenium/tests/GoogleTest.php test /usr/local/share/pear/tests/Testing_Selenium/tests/SeleniumTest.php doc /usr/local/share/doc/pear/Testing_Selenium/ChangeLog doc /usr/local/share/doc/pear/Testing_Selenium/README php /usr/local/share/pear/Testing/Selenium.php doc /usr/local/share/doc/pear/Testing_Selenium/TODO v.s.: $ pkg_info -L pear-Testing_Selenium-0.3.2 Information for pear-Testing_Selenium-0.3.2: Files: /usr/local/share/pear/Selenium/Exception.php /usr/local/share/pear/ChangeLog /usr/local/share/pear/Selenium.php /usr/local/share/pear/README /usr/local/share/pear/TODO /usr/local/share/pear/tests/Testing_Selenium/html/bug8893.html /usr/local/share/pear/tests/Testing_Selenium/html/bug9119.html /usr/local/share/pear/tests/Testing_Selenium/html/bug9189.html /usr/local/share/pear/tests/Testing_Selenium/AllTests.php /usr/local/share/pear/tests/Testing_Selenium/BugTest.php /usr/local/share/pear/tests/Testing_Selenium/GoogleTest.php /usr/local/share/pear/tests/Testing_Selenium/SeleniumTest.php /usr/local/share/examples/pear/Testing_Selenium/example.php l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ Guilty? Yeah. But he knows it. I mean, you're guilty. You just don't know it. So who's really in jail? ~Maynard James Keenan l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ Guilty? Yeah. But he knows it. I mean, you're guilty. You just don't know it. So who's really in jail? ~Maynard James Keenan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
3.1.x Port update for FreeBSD
The FBSD port is deadly out of date: # $FreeBSD: ports/devel/pear-PHPUnit3/Makefile,v 1.20 2007/06/26 08:09:31 pav Exp $ # PORTNAME= PHPUnit PORTVERSION=3.0.6 PORTREVISION= 1 It's 3.0.6 PL1. I'm attempting to update it to 3.1.9 now. I noticed the port is flagged as broken: BROKEN= Does not fetch This is because: MASTER_SITES= http://pear.phpunit.de/get/ Is set, but MASTER_SITES gets set back to pear.php.net later using: .include ${PORTSDIR}/devel/pear/bsd.pear.mk l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ Guilty? Yeah. But he knows it. I mean, you're guilty. You just don't know it. So who's really in jail? ~Maynard James Keenan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [phpunit-user] 3.1.x Port update for FreeBSD
On Fri, 12 Oct 2007, Sebastian Bergmann wrote: Brian A. Seklecki wrote: This is because: MASTER_SITES= http://pear.phpunit.de/get/ Is set, but MASTER_SITES gets set back to pear.php.net later using: Updated (w/ massive manual file list intervention): http://people.collaborativefusion.com/~seklecki/pear-PHPUnit3-3.1.9_bas.tar Looks good from here (except for that MASTER_SITES cheap hack). God speed. ~BAS .include ${PORTSDIR}/devel/pear/bsd.pear.mk The correct base url would be http://pear.phpunit.de/get/. -- Sebastian Bergmann http://sebastian-bergmann.de/ GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69 l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ Guilty? Yeah. But he knows it. I mean, you're guilty. You just don't know it. So who's really in jail? ~Maynard James Keenan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port for Testing_Selenium Client PEAR Binding
Makefile unambiguously stolen from ports/devel/pear-PHPUnit3: http://people.collaborativefusion.com/~seklecki/pear-Testing_Selenium_bas.tar For use in ports/devel/pear-Testing_Selenium/ ~BAS $ pear list-files Testing_Selenium Installed Files For Testing_Selenium Type Install Path doc /usr/local/share/doc/pear/Testing_Selenium/examples/example.php php /usr/local/share/pear/Testing/Selenium/Exception.php test /usr/local/share/pear/tests/Testing_Selenium/tests/html/bug8893.html test /usr/local/share/pear/tests/Testing_Selenium/tests/html/bug9119.html test /usr/local/share/pear/tests/Testing_Selenium/tests/html/bug9189.html test /usr/local/share/pear/tests/Testing_Selenium/tests/AllTests.php test /usr/local/share/pear/tests/Testing_Selenium/tests/BugTest.php test /usr/local/share/pear/tests/Testing_Selenium/tests/GoogleTest.php test /usr/local/share/pear/tests/Testing_Selenium/tests/SeleniumTest.php doc /usr/local/share/doc/pear/Testing_Selenium/ChangeLog doc /usr/local/share/doc/pear/Testing_Selenium/README php /usr/local/share/pear/Testing/Selenium.php doc /usr/local/share/doc/pear/Testing_Selenium/TODO v.s.: $ pkg_info -L pear-Testing_Selenium-0.3.2 Information for pear-Testing_Selenium-0.3.2: Files: /usr/local/share/pear/Selenium/Exception.php /usr/local/share/pear/ChangeLog /usr/local/share/pear/Selenium.php /usr/local/share/pear/README /usr/local/share/pear/TODO /usr/local/share/pear/tests/Testing_Selenium/html/bug8893.html /usr/local/share/pear/tests/Testing_Selenium/html/bug9119.html /usr/local/share/pear/tests/Testing_Selenium/html/bug9189.html /usr/local/share/pear/tests/Testing_Selenium/AllTests.php /usr/local/share/pear/tests/Testing_Selenium/BugTest.php /usr/local/share/pear/tests/Testing_Selenium/GoogleTest.php /usr/local/share/pear/tests/Testing_Selenium/SeleniumTest.php /usr/local/share/examples/pear/Testing_Selenium/example.php l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ Guilty? Yeah. But he knows it. I mean, you're guilty. You just don't know it. So who's really in jail? ~Maynard James Keenan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Updated FreeBSD Phing Port
All: FBSD Ports has an old copy from late `06 before phing.info / phing.tigris.org apparently: $ ident /usr/local/bin/phing /usr/local/bin/phing: $Id: pear-phing 123 2006-09-14 20:19:08Z mrook PORTNAME= phing PORTVERSION=2.1.1 However, one of my developers seems to have a 2.3.x-BETA/RC version running on 6.2-p7 just fine (php 5.2.1/pear 1.6.2) $ phing -version Phing version 2.3.0beta1 We should endeavor to update this to something recent. We'll try this from here and forward results on. l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ Guilty? Yeah. But he knows it. I mean, you're guilty. You just don't know it. So who's really in jail? ~Maynard James Keenan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: php5 does not buid
On Tue, 2007-10-02 at 18:23 +0200, Alexander Konovalenko wrote: Hello, I got an error while building php5: make clean build === Cleaning for php5-5.2.4_1 === Vulnerability check disabled, database not found === Found saved configuration for php5-5.2.4_1 === Extracting for php5-5.2.4_1 = MD5 Checksum OK for php-5.2.4.tar.bz2. = SHA256 Checksum OK for php-5.2.4.tar.bz2. === Patching for php5-5.2.4_1 === Applying FreeBSD patches for php5-5.2.4_1 === php5-5.2.4_1 depends on file: /usr/local/sbin/apxs - found === php5-5.2.4_1 depends on file: /usr/local/bin/autoconf-2.61 - found === php5-5.2.4_1 depends on executable: pkg-config - found === php5-5.2.4_1 depends on shared library: xml2.5 - found What does config.log look like? /var/db/ports/php5/options ? php5/Makefiles was touched two weeks ago for 5.2.4 and then two days ago for autotools-related changes: Revision 1.121: download - view: text, markup, annotated - select for diffs Sun Sep 30 04:47:00 2007 UTC (2 days, 11 hours ago) by linimon Branches: MAIN CVS tags: HEAD Diff to: previous 1.120: preferred, colored Changes since revision 1.120: +2 -2 lines Switch autoconf dependencies from 2.53 or 2.59 to 2.61. PR: ports/116639 Submitted by: aDe === Configuring for php5-5.2.4_1 configure.in:152: warning: AC_PROG_LEX invoked multiple times ../../lib/autoconf/programs.m4:779: AC_DECL_YYTEXT is expanded from... aclocal.m4:2080: PHP_PROG_LEX is expanded from... configure.in:152: the top level === Building for php5-5.2.4_1 make: cannot open Makefile. *** Error code 2 Stop in /usr/ports/lang/php5. *** Error code 1 Stop in /usr/ports/lang/php5. Is there any work around? I tried php4 but got the same error. I need to build php5 module for Apache22. uname -a FreeBSD myhost 6.2-STABLE FreeBSD 6.2-STABLE #2: Mon Oct 1 12:35:16 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP-DEVELOPER i386 /Alexander Konovalenko +46-8-5537-8142 (office) +46-7-3752-2116 http://daemon.nanophys.kth.se/~kono Royal Institute of Technology (KTH) Nanostructure Physics Department, Albanova Roslagstullsbacken 21 10691 Stockholm Sweden ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Keeping /dev/dsp in digital out mode?
Perhaps there is a sysctl for the drive you use that enables upsampling/resampling on-demand? I seem to remember on NetBSD. ~BAS On Wed, 2007-06-27 at 08:12 +1000, Stephen Hocking wrote: Hi, All of my systems are connected to a home theatre amp via an analogue connection except for one, which used an optical connection. Unsuprisingly, the digital connection sounds better (less noise etc). Has anyone experimented with keeping the output in digital mode all the time? I guess that some things would have to be resampled (I'm thinking of some games that only use 22KHz output etc, and some cards will only output digital at 48KHz). Any ideas? Stephen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports apache22 stupid quitestion.
You might set it in make.conf(5), but apache22 doesn't seem to use /var/db/ports/apache22/options. In either case, regardless, you'd still be replicating a file across all of the systems that you wish to remain homogeneous. ~BAS On Mon, 2007-04-23 at 18:33 +0300, Anton - Valqk wrote: because I build it with_mpm=worker and when I do -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Bacula-devel] Bacula version 2.2.x for Solaris, FreeBSD, and Windows
[cross-posting to freebsd-ports@ where hopefully we'll get some attention] FYI: The Bacula project is requesting additional voluntary development involvement by the FreeBSD community. A senior technical liaison who can dedicate time to staying abreast of development efforts in Bacula. Perhaps an organization using Bacula in their corporate infrastructure can volunteer developer time. ~BAS On Sun, 2007-04-15 at 11:24 +0200, Kern Sibbald wrote: Hello, As I have previously emailed several times over the last 6 months or so, I no longer build Bacula on Solaris and FreeBSD, and other than testing the Win32 client, I am running no regression tests on Win32, Solaris and FreeBSD. The Bacula community must step forward and organize systematically running regression testing, but so far this has not happened (this is quite disappointing). I have just completed significant modifications to the Volume reservation code in the Storage daemon (now in the SVN). There will undoubtedly be some fine tuning before it ships. However, I suspect that the code now makes recursive mutex calls, which work perfectly well on Linux, but they cause a failure on FreeBSD (this is permitted by the standard), which means that it is quite possible that the current SVN code will fail on FreeBSD. For Solaris, I am unsure. This email is a *BIG* urgent warning that unless the Bacula Solaris and FreeBSD users pull together and organize regression testing, you may find that version 2.2.x will not work on your platform, and it may be difficult to correct problems after production release in a timely fashion since once released, it is not possible to make any significant changes to mutex usage without destabilizing the code. Now is the time to test and bring any problems to my attention. I am ready to help you get the regression tests working and to fix mutex usage so that it works on your platform during the current development cycle. Best regards, Kern PS: I will be out of town from this afternoon until late Tuesday. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Bacula-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/bacula-devel -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
syslog-ng2 conf path default changed; pkg-plist out of date
Okay...who broke this: The path in the binary to the default config file has changed but the pkg-list hasn't and aside from the 2.0.2 patch level bump I dont see where else it came from: [EMAIL PROTECTED] ~]$ strings /usr/local/sbin/syslog-ng |egrep \.conf -f fname, --cfgfile=fnameSet config file name, default=/usr/local/etc/syslog-ng.conf /usr/local/etc/syslog-ng.conf [EMAIL PROTECTED] /usr/local/cf]$ sudo bash -x /usr/local/etc/rc.d/syslog-ng restart [...snip...] ++ /usr/local/sbin/syslog-ng -p /var/run/syslog.pid Error opening configuration file; filename='/usr/local/etc/syslog-ng.conf', error='No such file or directory (2)' The work-around for the mean time is: syslog_ng_flags=-f /usr/local/etc/syslog-ng/syslog-ng.conf I need to see a CVS changelog of certain files, but Balavid doesn't have a cvsweb, viewvc, etc. or public CVS archive? l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ ...from back in the heady days when helpdesk meant nothing, diskquota meant everything, and lives could be bought and sold for a couple of pages of laser printout - and frequently were. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
[Fwd: Re: ports/111462: syslog-ng2 default configuration file path]
ports/111462 filed. Have a great evening all* -- $ diff -u 2.0.0/syslog-ng.spec.bb 2.0.2/syslog-ng.spec.bb |grep -i conf -./configure --prefix=/ --mandir=/usr/share/man --infodir=/usr/share/info \ - --sysconfdir=/etc +./configure --prefix=%{prefix} --mandir=%{_mandir} \ + --infodir=%{prefix}/share/info + --sysconfdir=/etc/syslog-ng -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ---BeginMessage--- Thank you very much for your problem report. It has the internal identification `ports/111462'. The individual assigned to look at your report is: freebsd-ports-bugs. You can access the state of your problem report at any time via this link: http://www.freebsd.org/cgi/query-pr.cgi?pr=111462 Category: ports Responsible:freebsd-ports-bugs Synopsis: syslog-ng2 default configuration file path Arrival-Date: Tue Apr 10 22:40:01 GMT 2007 ---End Message--- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: subject=FreeBSD 6.1 gettext-0.16.1 portupgrade problems
On Sat, 2007-03-31 at 06:41 -0700, Dino Vliet wrote: ** Could not clean up temporary directory: Directory not empty - /var/tmp/portupgradeRtIfghsG Are you maybe not running this as root? Show is the full output of the command you ran. You'll need to make a judgment call on the packages that failed -- do you need them, etc. You may be better of pkg_delete'ing them and starting from scratch. ~BAS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: $snmpd_flush_cache for Net-SNMP ports/net-mgmt/net-snmp/files/snmpd.sh.in
Pending 5.4 now I assume? OpenBSD is about to commit a 5.4 version to their ports/ tree. ~BAS On Sat, 2006-11-04 at 18:53 +0900, Jun Kuriyama wrote: At Fri, 03 Nov 2006 23:18:11 -0500, Brian A. Seklecki wrote: FYI to SNMP hackers. Objections to this patch? No problem from me. I'm preparing for 5.3.1 upgrade in my local. This will bump shlib version, so I'll do it after 6.2R with your patch. -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [syslog-ng] sysutils/syslog-ng/files/syslong-ng.sh.in patch
* of alcohol. :} Betsy was a Himalayan Mountain Goat, and I'm the Sherpa. ~BAS Ahh. That explains the jpeg of you and the llamas. :) -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: $snmpd_flush_cache for Net-SNMP ports/net-mgmt/net-snmp/files/snmpd.sh.in
I filed PR: ports/106036 Feel free to close when the 5.3.x update rolls out to the public I know that the Net-SNMP people have been bugging me to to test new patches on FreeBSD and NetBSD, but I'm so stretched for time as it is that I barely have time to submit little PRs like this. ~BAS On Sat, 2006-11-04 at 18:53 +0900, Jun Kuriyama wrote: At Fri, 03 Nov 2006 23:18:11 -0500, Brian A. Seklecki wrote: FYI to SNMP hackers. Objections to this patch? No problem from me. I'm preparing for 5.3.1 upgrade in my local. This will bump shlib version, so I'll do it after 6.2R with your patch. -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [syslog-ng] sysutils/syslog-ng/files/syslong-ng.sh.in patch
Yep. I sent about 75 messages the other night well under the influence of a *LOT* of alcohol. :} ~BAS On Sun, 2006-11-05 at 23:37 -0500, [EMAIL PROTECTED] wrote: On Fri, 03 Nov 2006 21:31:59 EST, Brian A. Seklecki said: +syslog_ng_purgeklog=${syslog_ng_purgeklig-NO} klig? Typo? -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
sysutils/syslog-ng/files/syslong-ng.sh.in patch
This is a nice little patch we use to purge out /dev/klog after /etc/rc.d/dmesg and before /usr/local/etc/rc.d/syslog-ng.sh. It's useful for shops that translate user.info facility/priority syslog messages into SMS/E-Mail via a log{} mechanism (i.e., hardware error messages from the kernel, like some flunky in the NOC plugging a keyboard into your system). It lets you avoid 200 lines of boot messages in log(9) making their way into your log{} mechanism or into your pager. We want to feed it upstream because we think others will find it useful. ~BAS $ diff -u /usr/ports/sysutils/syslog-ng/files/syslog-ng.sh.in syslog-ng.sh.in --- /usr/ports/sysutils/syslog-ng/files/syslog-ng.sh.in Wed Mar 29 16:20:19 2006 +++ syslog-ng.sh.in Fri Nov 3 20:32:59 2006 @@ -14,6 +14,8 @@ #syslog_ng_enable=YES # +syslog_ng_purgeklog=${syslog_ng_purgeklig-NO} + . %%RC_SUBR%% name=syslog_ng @@ -23,6 +25,11 @@ required_files=%%PREFIX%%/etc/syslog-ng/syslog-ng.conf pidfile=/var/run/syslog.pid extra_commands=reload + +if checkyesno syslog_ng_purgeklog; then +start_precmd=echo \Purging klog(9)\ sysctl -w kern.msgbuf_clear=1 $start_precmd; +fi + stop_postcmd=stop_postcmd load_rc_config $name l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ ...from back in the heady days when helpdesk meant nothing, diskquota meant everything, and lives could be bought and sold for a couple of pages of laser printout - and frequently were. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
$snmpd_flush_cache for Net-SNMP ports/net-mgmt/net-snmp/files/snmpd.sh.in
FYI to SNMP hackers. Objections to this patch? -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. ---BeginMessage--- Good call on the $snmpd_pidfile= Another useful flag would be an optional pre_start() to blow away the Exec cache (which lingers after the process dies without documentation) Basically if you're writing a lot of your own passthrough OIDs and one of them fails to exec, a simple restart of SNMP should be enough to flush out: +start_precmd=snmpd_precmd +snmpd_precmd () { + if checkyesno snmpd_flush_cache; then + rm -rvf /var/net-snmp/.snmp-exec-cache fi ~BAS -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. ---End Message--- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [syslog-ng] building 2.0 on freebsd
You should try to work closely with the FreeBSD port maintainer for sysutils/syslog-ng to integrate 2.x into a Port. Unless there is a liscencing restriction I don't know preventing a enw sysutils/syslog-ng2/ port, we're still at 1.6.11 in Ports. Since there is no declared port maintainer right now, look at the CVS log for those who've been commiting fixes to the Makefile: [..in no particular order...] mnag@ linimon@ garga@ sem@ erwin@ novel@ pav@ demon@ ijliao@ will@ olgeni@ steve@ pat@ edwin@ ~BAS l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ ...from back in the heady days when helpdesk meant nothing, diskquota meant everything, and lives could be bought and sold for a couple of pages of laser printout - and frequently were. On Oct 12, 2006, at 5:24 PM, Vivek Khera wrote: What do I need to install to get eventlib on this system? i guess i searched not hard enough... i finally found it. never mind :-( ___ syslog-ng maillist - [EMAIL PROTECTED] https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]