From owner-freebsd-apache@FreeBSD.ORG Sun Oct 5 10:50:41 2014 Return-Path: Delivered-To: apache@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2D44A611 for ; Sun, 5 Oct 2014 10:50:41 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 14AE56E3 for ; Sun, 5 Oct 2014 10:50:41 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s95AoeQW031317 for ; Sun, 5 Oct 2014 10:50:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: apache@FreeBSD.org Subject: [Bug 193538] [patch] www/mod_amazon_proxy allow build agains apache24 Date: Sun, 05 Oct 2014 10:50:41 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports Tree X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: tota@FreeBSD.org X-Bugzilla-Status: Issue Resolved X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: tota@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Oct 2014 10:50:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193538 TAKATSU Tomonari changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Triage |Issue Resolved Resolution|--- |FIXED --- Comment #2 from TAKATSU Tomonari --- I've never noticed this PR. I fixed it at r368643. Thanks, -- You are receiving this mail because: You are on the CC list for the bug. From owner-freebsd-apache@FreeBSD.ORG Tue Oct 7 08:28:02 2014 Return-Path: Delivered-To: apache@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EE1118D2 for ; Tue, 7 Oct 2014 08:28:02 +0000 (UTC) Received: from portsmon.freebsd.org (portsmon.freebsd.org [IPv6:2001:1900:2254:206a::50:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C4ADEA93 for ; Tue, 7 Oct 2014 08:28:02 +0000 (UTC) Received: from portsmon.freebsd.org ([127.0.1.104]) by portsmon.freebsd.org (8.14.9/8.14.9) with ESMTP id s978S2Yi057131 for ; Tue, 7 Oct 2014 08:28:02 GMT (envelope-from linimon@FreeBSD.org) Date: Tue, 7 Oct 2014 08:28:02 GMT Message-Id: <201410070828.s978S2Yi057131@portsmon.freebsd.org> From: linimon@FreeBSD.org To: apache@freebsd.org Reply-To: portmgr-feedback@FreeBSD.org Subject: FreeBSD ports that you maintain which are currently marked broken X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Oct 2014 08:28:03 -0000 Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 7.x/8.x/9.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: www/mod_auth_cookie_mysql2 broken because: build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=mod_auth_cookie_mysql2 portname: www/mod_auth_external2 broken because: build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=mod_auth_external2 If these errors are ones that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Every effort has been made to make sure that these error reports really do correspond to a port that you maintain. However, due to the fact that this is an automated process, it may indeed generate false matches. If one of these errors fits that description, please forward this email to the author of this software, Mark Linimon , so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. From owner-freebsd-apache@FreeBSD.ORG Wed Oct 8 07:47:18 2014 Return-Path: Delivered-To: freebsd-apache@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C0AF6331 for ; Wed, 8 Oct 2014 07:47:18 +0000 (UTC) Received: from mx.ds9.org.za (ds9.org.za [IPv6:2a02:2770:11:0:21a:4aff:fe9c:8c91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 817CC75D for ; Wed, 8 Oct 2014 07:47:17 +0000 (UTC) Received: from ds9.org.za (localhost [127.0.0.1]) by mx.ds9.org.za (Postfix) with ESMTP id 83C85174561 for ; Wed, 8 Oct 2014 09:47:14 +0200 (SAST) Received: from mx.ds9.org.za ([127.0.0.1]) by ds9.org.za (ds9.org.za [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rb2Aw8D2f7lv for ; Wed, 8 Oct 2014 09:47:12 +0200 (SAST) Received: from damar.ru.ac.za (damar.ru.ac.za [IPv6:2001:4200:1010:1058:8e89:a5ff:fe85:6458]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.ds9.org.za (Postfix) with ESMTPSA id 6AF431744C9 for ; Wed, 8 Oct 2014 09:47:12 +0200 (SAST) From: David =?ISO-8859-1?Q?Sieb=F6rger?= To: freebsd-apache@freebsd.org Subject: USE_APACHE range broken? Date: Wed, 08 Oct 2014 09:47:08 +0200 Message-ID: <1494790.xaIYzRiInq@damar.ru.ac.za> User-Agent: KMail/4.12.5 (FreeBSD/10.0-RELEASE-p9; KDE/4.12.5; amd64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Oct 2014 07:47:18 -0000 Mk/bsd.apache.mk says that one can specify a range of Apache versions: # USE_APACHE=3D 22-24 # specify [min]-[max] range So far as I can see, security/shibboleth2-sp is the only port using tha= t=20 functionality. However, it doesn't seem to work properly, specifically= when=20 I'm using Poudriere to build packages and still prefer Apache 2.2. I've specified Apache 2.2 in make.conf: $ cat /etc/make.conf DEFAULT_VERSIONS+=3Dapache=3D2.2 And that does what I expect in other ports: $ grep USE_APACHE /usr/ports/lang/php5/Makefile USE_APACHE=3D 22+ $ make -C /usr/ports/www/mod_php5 -V APACHE_VERSION 22 But it doesn't do what I expect in Shibboleth: $ grep USE_APACHE /usr/ports/security/shibboleth2-sp/Makefile USE_APACHE=3D 22-24 $ make -C /usr/ports/security/shibboleth2-sp -V APACHE_VERSION 24 If I already have Apache 2.2 installed, then it works as I'd expect: $ sudo pkg install -qy apache22 =3D=3D=3D> Creating users and/or groups. Using existing group 'www'. Using existing user 'www'. $ make -C /usr/ports/security/shibboleth2-sp -V APACHE_VERSION 22 ... but that doesn't help in Poudriere, which installs Apache 2.4 as a=20= dependency before building Shibboleth. Should the range functionality be fixed, or should shibboleth2-sp simpl= y use=20 USE_APACHE=3D22+ instead? --=20 David Sieb=F6rger drs@sieborger.nom.za From owner-freebsd-apache@FreeBSD.ORG Thu Oct 9 14:22:47 2014 Return-Path: Delivered-To: apache@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2EA539FA for ; Thu, 9 Oct 2014 14:22:47 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 15C4E3E3 for ; Thu, 9 Oct 2014 14:22:47 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s99EMkb3007615 for ; Thu, 9 Oct 2014 14:22:46 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: apache@FreeBSD.org Subject: [Bug 187561] devel/subversion: bogus "No route to host" caused by www/serf Date: Thu, 09 Oct 2014 14:22:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports Tree X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: beastie@tardisi.com X-Bugzilla-Status: In Discussion X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: apache@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Oct 2014 14:22:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187561 --- Comment #6 from Lawrence Chen --- At the present time, things are working for me due to two possible reasons. I had first got things working again, by rebuilding 'devel/apr1' with IPV6 turned off. As I recall, a number of services failed to start during a reboot due to the lack of '::1'. The second reason is I later installed ports bind on my home network, with the FILTER_AAAA option enabled. And, made use of that. Since I didn't have this problem at work, because this option is used on the DNS servers there. At work, IPV6 has been outlawed (and actively being blocked) on our network, and other users were impacted by applications (such as chrome) that preferred IPV6 over IPV4. Though I usually launch 'www/chromium' with the '--disable-ipv6' option ;) Though someday I might get around to doing IPV6 on my home network... -- You are receiving this mail because: You are the assignee for the bug.