PR stalled/timeout (was: ports/170632: devel/otrs: please update to current version)
Hi, would someone please takeover PR ports/170632? It's been open for 6 months now. The version in the ports collection is already 6 patchlevels behind the current version of OTRS. But it's not due to a lack of maintenance or contributions. Several people invested time, sent patches, posted build logs, wrote followups, but all work is lost, if no one actually commits the changes to the ports repository. Thank you for taking notice. Regards - Frank ___ 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: php5 and pgsql/sqlite
Hi, On Mon, Apr 02, 2012 at 06:22:54PM +0300, Daniel Braniss wrote: whenever extensions=pgsql.so or/and extensions=slqlite3.so is added php exits with error (Exit 1) [...] but when adding, for example extension=pgsql.so to /usr/local/etc/php/extensions.ini php exits with error I suspect it is related to the LINKTHR option being off. Please see http://lists.freebsd.org/pipermail/freebsd-ports/2011-June/068441.html http://lists.freebsd.org/pipermail/freebsd-ports/2011-June/068222.html for details on how to fix this issue. Bye - Frank ___ 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
Porting OpenVAS 5.0 (BETA) - Current state?
Hi, is anyone working on porting OpenVAS 5 to FreeBSD or has anyone tried to do it in the past? Any known problems, caveats or linuxisms? I've seen some posts about a year ago regarding OpenVAS 4, but it seems nothing has happended since then. I would like to continue work on OpenVAS if someone has started a port but didn't finished it yet. Thanks for your feedback. - Frank ___ 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
cciss_vol_status: cross-compiling on amd64 for i386 fails
Hi, I'm currently trying to compile sysutils/cciss_vol_status on my amd64 build server. Later I want to deploy it on my i386 servers. Unfortunately my attempt was not successfull... === Building for cciss_vol_status-1.09 make all-am cc -DHAVE_CONFIG_H -I. -pipe -MT cciss_vol_status.o -MD -MP -MF .deps/cciss_vol_status.Tpo -c -o cciss_vol_status.o cciss_vol_status.c cciss_vol_status.c:141:2: warning: #warning Since scsi/sg.h is not around, MSA1000 support will not be compiled. mv -f .deps/cciss_vol_status.Tpo .deps/cciss_vol_status.Po cc -pipe -o cciss_vol_status cciss_vol_status.o cciss_vol_status.o(.text+0x2d82): In function `msa1000_status': : undefined reference to `msa1000_passthru_ioctl' cciss_vol_status.o(.text+0x2e14): In function `msa1000_status': : undefined reference to `msa1000_logical_drive_status' cciss_vol_status.o(.text+0x3164): In function `cciss_logical_drive_status': : undefined reference to `find_scsi_device_node' *** Error code 1 Stop in /work/a/ports/sysutils/cciss_vol_status/work/cciss_vol_status-1.09. *** Error code 1 Stop in /work/a/ports/sysutils/cciss_vol_status/work/cciss_vol_status-1.09. *** Error code 1 The build is running inside tinderbox and I've set these env variables: export ARCH=i386 export MACHINE_ARCH=i386 export UNAME_m=i386 export UNAME_p=i386 Any idea? Thanks - Frank ___ 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: OPTIONS framework bug vs. SSL issues
On Mon, Aug 29, 2011 at 11:40:25AM +0200, Matthias Andree wrote: Euhm, while workable I don't like that approach. And I conclude that the way the OPTIONS system currently works has a serious shortcoming, in that it does not report changed defaults to the user. Basically in this situation (default changed) we'd need to: 1. present the options form again 2. mention to the user that the default has changed 3. let him choose. I don't think that this is the right way to go. You are forcing the user to rethink his past decision(s). Why would I want to do this? The user decided to go a specific path by initially choosing a specific set of OPTIONs. We *must* assume that the user had good reasons to do so. We should *not* assume the user has no idea what he's doing and needs to be guided. The latter would make make the update process just more complicated. To me the Ports System is mainly for expert users. Most of them will track changes and test (port/software) updates before installing this update on important systems. Bye - Frank ___ 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/mail/procmail Makefile
On Tue, Aug 30, 2011 at 01:11:52PM +0200, Kurt Jaeger wrote: - Can it use the 700+ lines long .procmailrc I have running in a criticial application or do I have to migrate that ? I would suggest to migrate to something new. While searching for a procmail replacement myself, I've even found a script to migrate procmail rules to SIEVE instructions: http://www.dovecot.org/tools/procmail2sieve.pl Bye - Frank ___ 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: php5-5.3.6_1 with Segmentation fault (amd64)
On Wed, Jun 29, 2011 at 09:33:12AM +0200, Alex Dupre wrote: Steven Hartland ha scritto: Rebuild with threads enabled, will likely fix all your problems. That's correct. Is this fix supposed to work with lang/php52 too? If so I'd go and submit a patch for it to add WITH_LINKTHR. Thanks - Frank ___ 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: php5-5.3.6_1 with Segmentation fault (amd64)
On Wed, Jun 29, 2011 at 11:40:59AM +0200, Alex Dupre wrote: Frank Wall ha scritto: Is this fix supposed to work with lang/php52 too? Of course, but you should update to a supported php release ;-) Submitted PR ports/158423. Let's see if it works for PHP 5.2. Actually I'm planning to update all servers to 5.3, but this is going to happen later this year. Bye - Frank ___ 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
portlint: FATAL: no in ..
Hi,
I'm trying to verify a newly created port and got this strange error
from `portlint` for the first time:
$ portlint -aNv
[...]
OK: WRKSRC seems to be ${WRKDIR}/.
OK: no NO_WRKSUBDIR, checking value of WRKSRC.
OK: checking RESTRICTED/NO_CDROM/NO_PACKAGE.
OK: checking NO_CONFIGURE/NO_PATCH.
OK: checking MAN[0-9LN].
OK: checking INFO.
OK: checking .
FATAL: no in ..
1 fatal error and 0 warnings found.
Could someone give me a hint on this? I don't get this error on
i386 machines, only on amd64. Maybe there's something broken somewhere.
$ pkg_info -xI portlint
portlint-2.13.1 A verifier for FreeBSD port directory
$ uname -a
FreeBSD server 7.1-RELEASE-p11 FreeBSD 7.1-RELEASE-p11 #0: Fri Feb 26 19:22:31
UTC 2010 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
amd64
Thanks
- Frank
___
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: portlint: FATAL: no in ..
On Thu, Nov 04, 2010 at 12:25:44PM +0100, René Ladan wrote: Which version of bsd.port.mk do you have on these machines? If you're using revision 1.652 or higher (MD5 checksumming removed), Got this version: $FreeBSD: ports/Mk/bsd.port.mk,v 1.653 2010/10/29 12:41:29 erwin Exp $ you'll need to manually upgrade portlint. Manually rebuilding portlint fixed it, thank you. I rebuilded it with portupgrade before, but obviously this did not help (though I don't understand why this did not fix it). Maybe the PORTREVISION of portlint should be bumped? Yes, I'd vote for it. Bye - Frank ___ 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: ClamAV 0.96.2 not working on FreeBSD 7.1
On Fri, Aug 27, 2010 at 02:48:15PM +0200, Frank Wall wrote: Maybe the ClamAV people will provide a fix for this issue. There is a patch [1] available from ClamAV. For me it solves the problem. I've created a PR [2] to get the fix committed to the ports tree soon. [1] http://git.clamav.net/gitweb?p=clamav-devel.git;a=commitdiff_plain;h=71ca3536c4e0ed6454315a7c3ad5950ba212fbe1 [2] http://www.freebsd.org/cgi/query-pr.cgi?pr=150243 Thanks - Frank ___ 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
ClamAV 0.96.2 not working on FreeBSD 7.1
Hi, I'm experiencing problems running ClamAV 0.96.2 on FreeBSD 7.1 (i386). The clamd will stop working immediately after startup. The process is still there, but unresponsive: # /usr/local/bin/clamdtop [...] Connecting to: /var/run/clamav/clamd.sock /var/run/clamav/clamd.sock: Resource temporarily unavailable I found that it works on FreeBSD 8.0 without any problems, so a change in version 0.96.2 possiblity broke compatiblity with older versions of FreeBSD. Version 0.96.1 runs without any problems on FreeBSD 7.1. Is anyone else seeing this problem? I am able to reproduce this on all my 7.1 boxes. FYI, I've opened a bug report at ClamAV: https://wwws.clamav.net/bugzilla/show_bug.cgi?id=2235 Thanks - Frank ___ 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: ClamAV 0.96.2 not working on FreeBSD 7.1
On Fri, Aug 27, 2010 at 01:20:23PM +0100, Paul Macdonald wrote: i had something similar and eventually found that disabling JIT Bytecode compiler option, returned it to being stable. This only happened on one of my boxes though so i figured it was 'me'. Thanks for the hint. Setting Bytecode to no does the trick. Now version 0.96.2 runs without any problems on FreeBSD 7.1. But I don't consider this a solution, it's a workaround to get things going again. Maybe the ClamAV people will provide a fix for this issue. Thanks - Frank ___ 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
PHP4 no longer compiles with www/apache20
Hi, I have updated www/apache20 to apache-2.0.63_15, but it seems that a recent change breaks compatiblity with PHP4. I got this error while trying to rebuild lang/php4: In file included from /usr/local/include/apache2/httpd.h:44, from /usr/local/include/apache2/util_filter.h:23, from /usr/ports/lang/php4/work/php-4.4.9/sapi/apache2handler/sapi_apache2.c:40: /usr/local/include/apache2/ap_regex.h:90: error: conflicting types for 'regoff_t' /usr/ports/lang/php4/work/php-4.4.9/regex/regex.h:17: error: previous declaration of 'regoff_t' was here *** Error code 1 Trying to restart Apache reveals a recent API change: # /usr/local/etc/rc.d/apache2 restart Performing sanity check on apache2 configuration: httpd: module /usr/ports/lang/php4/work/php-4.4.9/sapi/apache2handler/sapi_apache2.c is not compatible with this version of Apache (found 20020903, need 20050127). Please contact the vendor for the correct version. I assume the fix for mod_redirect introduces this new problem: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/146604 (MFC of http://svn.apache.org/viewvc?view=revisionrevision=153384) The system is really ancient, running 6.4-RELEASE with lot's of old stuff, but I cannot upgrade PHP nor Apache because of some compatiblity issues. Any hints/hacks? Regards Frank Wall ___ 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
