From owner-freebsd-python@FreeBSD.ORG Sat Feb 12 00:32:48 2005 Return-Path: <owner-freebsd-python@FreeBSD.ORG> Delivered-To: freebsd-python@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DAE716A4CE for <python@freebsd.org>; Sat, 12 Feb 2005 00:32:48 +0000 (GMT) Received: from smaug.vex.net (smaug.vex.net [66.96.28.243]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EB6C43D31 for <python@freebsd.org>; Sat, 12 Feb 2005 00:32:48 +0000 (GMT) (envelope-from x@vex.net) Received: from bee.xxvii.x (H140.C18.B96.tor.eicat.ca [66.96.18.140]) by smaug.vex.net (Postfix) with ESMTP id 20C0F2546B for <python@freebsd.org>; Fri, 11 Feb 2005 19:32:47 -0500 (EST) Received: by bee.xxvii.x (Postfix, from userid 1000) id E73CA11486; Fri, 11 Feb 2005 19:32:45 -0500 (EST) From: Tim Middleton <x@vex.net> Organization: xxvii.net To: python@freebsd.org Date: Fri, 11 Feb 2005 19:32:44 -0500 User-Agent: KMail/1.7.2 X-Whee: Yes, Please. MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200502111932.45111.x@vex.net> Subject: broken dependency zope ports X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: python@freebsd.org List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>, <mailto:freebsd-python-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-python> List-Post: <mailto:freebsd-python@freebsd.org> List-Help: <mailto:freebsd-python-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-python>, <mailto:freebsd-python-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 12 Feb 2005 00:32:48 -0000 A small bunch of zope ports were marked broken today with the message "broken dependency". One of them is mine, and I don't see any broken dependencies. I'm suspecting this might have something to do with the python versus python23 thing which zope is inflicting on us... i noticed that all of the ports marked broken have other non-zope python module dependencies. Could the build process be getting confused between python versions? Just wondering if anyone deeper into the mysterious ways of the ports has any insights... -- Tim Middleton | Vex.Net | There are a thousand hacking at the branches x@veX.net | VexTech.ca | of evil [but who] at the root. --Thoreau (W)