From owner-freebsd-python@FreeBSD.ORG Mon Sep 12 16:21:38 2005 Return-Path: <owner-freebsd-python@FreeBSD.ORG> X-Original-To: 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 32F7016A41F; Mon, 12 Sep 2005 16:21:38 +0000 (GMT) (envelope-from x@vex.net) Received: from smaug.vex.net (smaug.vex.net [66.96.28.243]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0E1443D45; Mon, 12 Sep 2005 16:21:37 +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 51D2F25F69; Mon, 12 Sep 2005 12:21:35 -0400 (EDT) Received: by bee.xxvii.x (Postfix, from userid 1000) id 7B6E11CC1A; Mon, 12 Sep 2005 12:21:40 -0400 (EDT) From: Tim Middleton <x@vex.net> Organization: xxvii.net To: linimon@freebsd.org, python@freebsd.org Date: Mon, 12 Sep 2005 12:21:35 -0400 User-Agent: KMail/1.8.2 References: <20050910083032.2C49022987@mail.droso.net> In-Reply-To: <20050910083032.2C49022987@mail.droso.net> X-GPG-Fingerprint: F59D 8A8C A8E1 23B5 407D DD30 9069 D1B3 6416 FFB6 X-Whee: Yes, Please. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200509121221.39030.x@vex.net> Cc: Subject: Re: FreeBSD ports that you maintain which are currently marked broken X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list 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: Mon, 12 Sep 2005 16:21:38 -0000 On Saturday 10 September 2005 04:30, you wrote: > portname: www/zope-parsedxml > broken because: Broken dependency > build errors: > http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.4.2005072423/zope-parsedxml-1.4.log (Aug 21 17:56:44 GMT 2005) overview: > http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=zope-parsedxml Hello Mark... This has been going on for a long, long time now. )-: I was really hoping Zope 2.8 would have found its way into ports by now, which eliminates the Python 2.3 dependency the current Zope port has, thus rendering this context obsolete. But even with things as they are, I can not reproduce the dependency error the above report is reporting... It seems there's something in the environment of, or methods used by, your build/test system which is forcing the python 2.4 build of py-xml. Most of this time I've been thinking it must be something in my environment which avoids the error you are getting above, but could not identify what it was. Recently however, I thought to try building zope-parsedxml on fairly clean new FreeBSD 5.3 box I was given to upgrade. I updated the ports tree. Python 2.4 was already installed on the box, but not much else. THere's nothing special in make.conf (just the usual PERL_VER stuff). So i remove the BROKEN tag from zope-parsedxml/Makefile ... type "make install" ... and everything builds and installs perfectly (python 2.3, zope 2.7.7, py23-xml, and then zope-parsedxml). There is actually a second problem indicated by the log above, and that is that apparently py24-xml-0.8.4 and py23-xml-0.8.4 are not being allowed to co-exist at the same time (the py23-xml-0.8.4 build is not allowed to install because an "old version" [py24-xml-0.8.4] is found already installed). There's no technical reason these shouldn't be able to both be installed as they install to different python library directories, and anyhow py24-xml-0.8.4 is not an older version of py23-xml-0.8.4.... Maybe implications of this is the problem? However, back my main problem, the USE_ZOPE directive in my Makefile should be (and apparently is, on a regular, clean system!) setting the python version to 2.3. The only thing I can think of is that your build process is building the dependencies independently?... and thus is losing the PYTHON_VERSION=python2.3 environment which is set in bsd.python.mk. I believe this is an innocent port about to be executed here. (-: -- Tim Middleton | Vex.Net | He is no Quaker, for he hath got a Perriwig x@veX.net | VexTech.ca | on. [OED] From owner-freebsd-python@FreeBSD.ORG Mon Sep 12 16:37:15 2005 Return-Path: <owner-freebsd-python@FreeBSD.ORG> X-Original-To: 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 3B36B16A41F for <python@freebsd.org>; Mon, 12 Sep 2005 16:37:15 +0000 (GMT) (envelope-from x@vex.net) Received: from smaug.vex.net (smaug.vex.net [66.96.28.243]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3EB743D45 for <python@freebsd.org>; Mon, 12 Sep 2005 16:37:14 +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 B883D26073 for <python@freebsd.org>; Mon, 12 Sep 2005 12:37:12 -0400 (EDT) Received: by bee.xxvii.x (Postfix, from userid 1000) id 2809D1CC2F; Mon, 12 Sep 2005 12:37:18 -0400 (EDT) From: Tim Middleton <x@vex.net> Organization: xxvii.net To: python@freebsd.org Date: Mon, 12 Sep 2005 12:37:16 -0400 User-Agent: KMail/1.8.2 References: <8828e1ad05072503136d2a1260@mail.gmail.com> In-Reply-To: <8828e1ad05072503136d2a1260@mail.gmail.com> X-GPG-Fingerprint: F59D 8A8C A8E1 23B5 407D DD30 9069 D1B3 6416 FFB6 X-Whee: Yes, Please. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200509121237.17549.x@vex.net> Cc: Subject: Re: BROKEN Zope products ports X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list 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: Mon, 12 Sep 2005 16:37:15 -0000 On Monday 25 July 2005 06:13, Filippo Natali wrote to ports@freebsd.org: > package building process, so I'm asking if skipping the package build > adding NO_PACKAGE to these ports is a suitable workaround. Hmm, I should have poked my head in here before my last reply to linimon@freebsd.org (copied here)... I now see also that indeed some zope ports have been updated with NO_PACKAGE... I guess I'll do the same... it seems a bit of a sad solution though... oh well. -- Tim Middleton | Vex.Net | But the trouble was that my hysterical fit x@veX.net | VexTech.ca | could not go on for ever. --Dost (NFTU)