From owner-freebsd-apache@FreeBSD.ORG Sun Dec 18 10:58:24 2005 Return-Path: X-Original-To: apache@freebsd.org Delivered-To: freebsd-apache@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5976716A41F for ; Sun, 18 Dec 2005 10:58:24 +0000 (GMT) (envelope-from kuku@www.kukulies.org) Received: from www.kukulies.org (www.kukulies.org [213.146.112.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FF1743D77 for ; Sun, 18 Dec 2005 10:58:18 +0000 (GMT) (envelope-from kuku@www.kukulies.org) Received: from www.kukulies.org (localhost [127.0.0.1]) by www.kukulies.org (8.13.3/8.12.10) with ESMTP id jBIAwE9n027914 for ; Sun, 18 Dec 2005 11:58:15 +0100 (CET) (envelope-from kuku@www.kukulies.org) Received: (from kuku@localhost) by www.kukulies.org (8.13.3/8.12.10/Submit) id jBIAwEkq027913 for apache@freebsd.org; Sun, 18 Dec 2005 11:58:14 +0100 (CET) (envelope-from kuku) Date: Sun, 18 Dec 2005 11:58:14 +0100 (CET) From: Christoph Kukulies Message-Id: <200512181058.jBIAwEkq027913@www.kukulies.org> To: apache@freebsd.org Cc: Subject: apache2 proxy modules disabled? X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Dec 2005 10:58:24 -0000 I'm trying to get apache/tomcat/opencms working under FreeBSD and I find that apache2 dows not enable all modules (proxy e.g.) by default. Is there an option to build apache2 with everything? -- Chris Christoph P. U. Kukulies kuku_at_kukulies.org From owner-freebsd-apache@FreeBSD.ORG Mon Dec 19 00:52:56 2005 Return-Path: X-Original-To: apache@freebsd.org Delivered-To: freebsd-apache@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B292616A41F for ; Mon, 19 Dec 2005 00:52:56 +0000 (GMT) (envelope-from mv@roq.com) Received: from vault.mel.jumbuck.com (ppp166-27.static.internode.on.net [150.101.166.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 352F943D46 for ; Mon, 19 Dec 2005 00:52:55 +0000 (GMT) (envelope-from mv@roq.com) Received: from vault.mel.jumbuck.com (localhost [127.0.0.1]) by vault.mel.jumbuck.com (Postfix) with ESMTP id 9D43A8A00D; Mon, 19 Dec 2005 11:52:54 +1100 (EST) Received: from [192.168.46.52] (unknown [192.168.46.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by vault.mel.jumbuck.com (Postfix) with ESMTP id 819CF8A00A; Mon, 19 Dec 2005 11:52:54 +1100 (EST) Message-ID: <43A60466.3000206@roq.com> Date: Mon, 19 Dec 2005 11:52:54 +1100 From: Michael Vince User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20051208 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christoph Kukulies References: <200512181058.jBIAwEkq027913@www.kukulies.org> In-Reply-To: <200512181058.jBIAwEkq027913@www.kukulies.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: apache@freebsd.org Subject: Re: apache2 proxy modules disabled? X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2005 00:52:56 -0000 There are lots of ways to do this, for example. portupgrade -N -m 'WITH_MPM=worker -DWITH_PROXY_MODULES -DWITH_EXPERIMENTAL_MODULES' /usr/ports/www/apache20 Cheers, Mike Christoph Kukulies wrote: >I'm trying to get apache/tomcat/opencms working under FreeBSD >and I find that apache2 dows not enable all modules (proxy e.g.) >by default. > >Is there an option to build apache2 with everything? > >-- >Chris Christoph P. U. Kukulies kuku_at_kukulies.org >_______________________________________________ >freebsd-apache@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-apache >To unsubscribe, send any mail to "freebsd-apache-unsubscribe@freebsd.org" > > From owner-freebsd-apache@FreeBSD.ORG Mon Dec 19 11:00:52 2005 Return-Path: X-Original-To: apache@freebsd.org Delivered-To: freebsd-apache@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99B2D16A41F for ; Mon, 19 Dec 2005 11:00:52 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B52643D67 for ; Mon, 19 Dec 2005 11:00:50 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBJB0nZt010270 for ; Mon, 19 Dec 2005 11:00:49 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBJB0me7010262 for apache@freebsd.org; Mon, 19 Dec 2005 11:00:48 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 19 Dec 2005 11:00:48 GMT Message-Id: <200512191100.jBJB0me7010262@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: apache@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2005 11:00:52 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2005/11/20] ports/89308 apache [patch] www/mod_accounting crash on reque 1 problem total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/12/09] ports/74907 apache [PATCH] www/mod_perl: cleanups o [2005/05/18] ports/81183 apache apache13-modperl can not compile with por o [2005/12/05] ports/89972 apache portupgrade apache+ssl fails on dependenc 3 problems total. From owner-freebsd-apache@FreeBSD.ORG Wed Dec 21 10:00:41 2005 Return-Path: X-Original-To: apache@freebsd.org Delivered-To: freebsd-apache@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C37316A420 for ; Wed, 21 Dec 2005 10:00:41 +0000 (GMT) (envelope-from fenner+portsurvey@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA0D443D6B for ; Wed, 21 Dec 2005 10:00:29 +0000 (GMT) (envelope-from fenner+portsurvey@FreeBSD.org) Received: from freefall.freebsd.org (fenner@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id jBLA0PGS083220 for ; Wed, 21 Dec 2005 10:00:25 GMT (envelope-from fenner+portsurvey@freefall.freebsd.org) Received: (from fenner@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id jBLA0PGm083219; Wed, 21 Dec 2005 10:00:25 GMT (envelope-from fenner+portsurvey) Date: Wed, 21 Dec 2005 10:00:25 GMT Message-Id: <200512211000.jBLA0PGm083219@freefall.freebsd.org> From: fenner@freebsd.org (Bill "distfiles" Fenner) To: apache@freebsd.org Cc: Subject: FreeBSD ports: 5 unfetchable distfiles: www/mod_accesscookie, www/mod_injection, www/mod_v2h, www/mod_vdbh, www/mod_webapp X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ports@freebsd.org List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Dec 2005 10:00:41 -0000 Dear apache@freebsd.org, You are listed as the FreeBSD port maintainer for 5 ports whose distfiles are not fetchable from their MASTER_SITES. Could you please visit http://people.freebsd.org/~fenner/portsurvey/apache@freebsd.org.html and correct the problems listed there? The individual ports with problems are www/mod_accesscookie,www/mod_injection,www/mod_v2h,www/mod_vdbh,www/mod_webapp. If you have already corrected the problems and submitted a PR, please accept my thanks and apologies for the delay in getting the fixes into the tree. This reminder is created automatically and does not (yet) have a way to know if a PR fixing the problem has been submitted. Please do *NOT* send your response to me directly; I do not necessarily have time to commit your fix; please instead submit a PR via 'send-pr' so it doesn't get lost. Problems are usually of two types: 1. The software package has been upgraded and the version in the port has been removed. The best solution to this problem is to upgrade the port to the most current version of the software package. If you are a FreeBSD committer, then you can just upgrade the port directly. If not, you should create the updated port on your own machine, test it (and maybe even run "portlint" on it), and then use "send-pr" to submit a "diff -uNr old-port updated-port". If you added or deleted any files, please make an explicit note of it. 2. The mirror site being used no longer contains the software package in question, or no longer exists. Solutions include: a) If there are other mirror sites, just remove the bad site from the list. (Make sure that what appears to be a bad site isn't actually a problem of type 1, upgrade) b) If the README or other support files in the software documentation mention where to get the software package, use one of those sites. c) Use a search engine to find another place to get the original DISTFILES. Make sure that you don't pick a FreeBSD distfiles mirror -- if you can't find any other places where the file exists, it can be a LOCAL_PORT or you can simply comment out the MASTER_SITES= line, with a comment explaining why. Once you have a solution, use "send-pr" to submit a "diff -u" of the Makefile. Note that this isn't an urgent issue, as people who try to build the port now will just fall back to the FreeBSD distfiles mirror. Please just put it on your list to do and get to it when you have time. These messages will continue to arrive twice a month until the fix is committed, as a reminder. Thanks, Bill "distfiles" Fenner.