From owner-freebsd-python@FreeBSD.ORG Sun Sep 18 10:04:32 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 961AC16A41F; Sun, 18 Sep 2005 10:04:32 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id C166A43D45; Sun, 18 Sep 2005 10:04:31 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from ury.york.ac.uk (ury.york.ac.uk [144.32.108.81]) by mail-gw1.york.ac.uk (8.12.10/8.12.10) with ESMTP id j8IA4SKG026699; Sun, 18 Sep 2005 11:04:28 +0100 (BST) Received: from ury.york.ac.uk (localhost.york.ac.uk [127.0.0.1]) by ury.york.ac.uk (8.13.1/8.13.1) with ESMTP id j8IA4RZR087311; Sun, 18 Sep 2005 11:04:27 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from localhost (gavin@localhost) by ury.york.ac.uk (8.13.1/8.13.1/Submit) with ESMTP id j8IA4RdV087308; Sun, 18 Sep 2005 11:04:27 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: ury.york.ac.uk: gavin owned process doing -bs Date: Sun, 18 Sep 2005 11:04:27 +0100 (BST) From: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> X-X-Sender: gavin@ury.york.ac.uk To: python@freebsd.org Message-ID: <20050918101327.H86911@ury.york.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Cc: kris@freebsd.org Subject: Fixing port www/zope-cmfphoto 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: Sun, 18 Sep 2005 10:04:32 -0000 Hi, I'm looking into the build failures with www/zope-cmfphoto that have led to it being marked as broken and deprecated, scheduled for deletion on the 22nd Sept. I would appreciate it if it is not deleted just yet. This is my first attempt at understanding the ports build infrastructure. As far as I can tell from http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.5.2005051203/zope-cmfphoto-0.4.2.log the issue may be with the pointyhat ports build infrastructure. Despite zope-cmfphoto declaring it requires Python 2.3 (indirectly, via the USE_ZOPE=yes option), somehow RUN_DEPENDS is being populated with py24-imaging-1.1.5.tbz rather than py23-imaging-1.1.5.tbz - presumably this is being done by the pointyhat build scripts based soley on the fact that it is the newest/default version? Or is the issue the fact that a Python 2.3 version of py-imaging fails to install because a Python 2.4 version has been installed? The current port build infrastructure explicitely disallows this, so I'm not sure what can be done about it. Are the pointyhat build scripts available publically for me to try and figure out further what the issue is? The port builds and installs fine from source, and a package generated from that seems to be correct too. Thanks, Gavin From owner-freebsd-python@FreeBSD.ORG Sun Sep 18 10:48:37 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 7CC2016A41F for <python@freebsd.org>; Sun, 18 Sep 2005 10:48:37 +0000 (GMT) (envelope-from kaeru@pd.jaring.my) Received: from smtp105.mail.sc5.yahoo.com (smtp105.mail.sc5.yahoo.com [66.163.169.225]) by mx1.FreeBSD.org (Postfix) with SMTP id 2E33143D45 for <python@freebsd.org>; Sun, 18 Sep 2005 10:48:36 +0000 (GMT) (envelope-from kaeru@pd.jaring.my) Received: (qmail 9227 invoked from network); 18 Sep 2005 10:48:36 -0000 Received: from unknown (HELO ?192.168.1.49?) (khairil?yusof@219.95.135.243 with plain) by smtp105.mail.sc5.yahoo.com with SMTP; 18 Sep 2005 10:48:35 -0000 From: Khairil Yusof <kaeru@pd.jaring.my> To: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> In-Reply-To: <20050918101327.H86911@ury.york.ac.uk> References: <20050918101327.H86911@ury.york.ac.uk> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-s8xrl2Kc8LgqAN6lxYBg" Date: Sun, 18 Sep 2005 18:48:39 +0800 Message-Id: <1127040519.424.7.camel@wolverine> Mime-Version: 1.0 X-Mailer: Evolution 2.4.0 FreeBSD GNOME Team Port Cc: kris@freebsd.org, python@freebsd.org Subject: Re: Fixing port www/zope-cmfphoto 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: Sun, 18 Sep 2005 10:48:37 -0000 --=-s8xrl2Kc8LgqAN6lxYBg Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2005-09-18 at 11:04 +0100, Gavin Atkinson wrote: > Or is the issue the fact that a Python 2.3 version of py-imaging fails to= =20 > install because a Python 2.4 version has been installed? The current por= t=20 > build infrastructure explicitely disallows this, so I'm not sure what can= =20 > be done about it. Hi Gavin, I've just submitted a PR to disable package building and to mark it as not broken. This is a workaround that several other zope python affected ports have also implemented. If you are able to solve the root cause of this problem, it would be much appreciated by all. --=-s8xrl2Kc8LgqAN6lxYBg Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDLUYHDAqnLW/+/X8RAuvyAJ937Kg5d78Fg6tcR/z/of5eQN4odgCg/t3e GmC5QWaDOGocnCaSrzUiIqM= =A1cA -----END PGP SIGNATURE----- --=-s8xrl2Kc8LgqAN6lxYBg-- From owner-freebsd-python@FreeBSD.ORG Sun Sep 18 15:44:12 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 1EDCF16A41F; Sun, 18 Sep 2005 15:44:12 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80D1E43D58; Sun, 18 Sep 2005 15:44:07 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 687232D07; Sun, 18 Sep 2005 10:44:06 -0500 (CDT) Date: Sun, 18 Sep 2005 10:44:06 -0500 To: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> Message-ID: <20050918154406.GA5846@soaustin.net> References: <20050918101327.H86911@ury.york.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050918101327.H86911@ury.york.ac.uk> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: kris@freebsd.org, python@freebsd.org Subject: Re: Fixing port www/zope-cmfphoto 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: Sun, 18 Sep 2005 15:44:12 -0000 On Sun, Sep 18, 2005 at 11:04:27AM +0100, Gavin Atkinson wrote: > my first attempt at understanding the ports build infrastructure. Well, you've chosen a complex topic on which to dive into it :-) > Despite zope-cmfphoto declaring it requires Python 2.3 (indirectly, via > the USE_ZOPE=yes option), somehow RUN_DEPENDS is being populated with > py24-imaging-1.1.5.tbz rather than py23-imaging-1.1.5.tbz - presumably > this is being done by the pointyhat build scripts based soley on the fact > that it is the newest/default version? As best I can tell the pointyhat scripts use packages as prerequisites for every port that gets built. (Otherwise, the amount of time required for the builds would be vastly increased). My guess is that the default package of py-imaging maps to py24-imaging rather than py23-imaging. Let's see if that's correct .... Here is a graphical map of the dependencies as seen by a system that has Python 2.4 installed on it: http://portsmon.FreeBSD.org/portdependencytree.py?category=www&portname=zope-cmfphoto So www/zope-cmfphoto depends on lang/python23 and graphics/py-imaging; but graphics/py-imaging depends on lang/python (2.4), which would, when compiled in a clean system, indeed produce package py24-imaging, not py23-imaging. So this may be more a problem with the framework, not with pointyhat (e.g. the fact that you can only depend on a port, not a specific package of it). My guess would be that we need to mark these as NO_PACKAGE as a workaround until Zope can fix their code to not rely on 2.3, as some of these other ports have done. > Are the pointyhat build scripts available publically for me to try and > figure out further what the issue is? The port builds and installs fine > from source, and a package generated from that seems to be correct too. See http://www.freebsd.org/cgi/cvsweb.cgi/ports/Tools/portbuild/scripts/buildscript , but be warned that the scripts are very dense and will not quickly provide you any answers. mcl From owner-freebsd-python@FreeBSD.ORG Sun Sep 18 17:25:35 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 41D4A16A41F for <python@freebsd.org>; Sun, 18 Sep 2005 17:25:35 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id A292543D48 for <python@freebsd.org>; Sun, 18 Sep 2005 17:25:34 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from ury.york.ac.uk (ury.york.ac.uk [144.32.108.81]) by mail-gw1.york.ac.uk (8.12.10/8.12.10) with ESMTP id j8IHPVKG004399; Sun, 18 Sep 2005 18:25:31 +0100 (BST) Received: from ury.york.ac.uk (localhost.york.ac.uk [127.0.0.1]) by ury.york.ac.uk (8.13.1/8.13.1) with ESMTP id j8IHPVI9089716; Sun, 18 Sep 2005 18:25:31 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from localhost (gavin@localhost) by ury.york.ac.uk (8.13.1/8.13.1/Submit) with ESMTP id j8IHPUNd089713; Sun, 18 Sep 2005 18:25:31 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: ury.york.ac.uk: gavin owned process doing -bs Date: Sun, 18 Sep 2005 18:25:30 +0100 (BST) From: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> X-X-Sender: gavin@ury.york.ac.uk To: Khairil Yusof <kaeru@pd.jaring.my> In-Reply-To: <1127040519.424.7.camel@wolverine> Message-ID: <20050918182307.Q89636@ury.york.ac.uk> References: <20050918101327.H86911@ury.york.ac.uk> <1127040519.424.7.camel@wolverine> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Cc: python@freebsd.org Subject: Re: Fixing port www/zope-cmfphoto 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: Sun, 18 Sep 2005 17:25:35 -0000 On Sun, 18 Sep 2005, Khairil Yusof wrote: > On Sun, 2005-09-18 at 11:04 +0100, Gavin Atkinson wrote: > >> Or is the issue the fact that a Python 2.3 version of py-imaging fails to >> install because a Python 2.4 version has been installed? The current port >> build infrastructure explicitely disallows this, so I'm not sure what can >> be done about it. > > Hi Gavin, I've just submitted a PR to disable package building and to > mark it as not broken. Thanks! Gavin From owner-freebsd-python@FreeBSD.ORG Sun Sep 18 18:40:35 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 4D60B16A41F; Sun, 18 Sep 2005 18:40:35 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 946DC43D46; Sun, 18 Sep 2005 18:40:34 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from ury.york.ac.uk (ury.york.ac.uk [144.32.108.81]) by mail-gw1.york.ac.uk (8.12.10/8.12.10) with ESMTP id j8IIeWKG005488; Sun, 18 Sep 2005 19:40:32 +0100 (BST) Received: from ury.york.ac.uk (localhost.york.ac.uk [127.0.0.1]) by ury.york.ac.uk (8.13.1/8.13.1) with ESMTP id j8IIeTne090206; Sun, 18 Sep 2005 19:40:29 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from localhost (gavin@localhost) by ury.york.ac.uk (8.13.1/8.13.1/Submit) with ESMTP id j8IIeTrh090203; Sun, 18 Sep 2005 19:40:29 +0100 (BST) (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: ury.york.ac.uk: gavin owned process doing -bs Date: Sun, 18 Sep 2005 19:40:29 +0100 (BST) From: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> X-X-Sender: gavin@ury.york.ac.uk To: Mark Linimon <linimon@lonesome.com> In-Reply-To: <20050918154406.GA5846@soaustin.net> Message-ID: <20050918182556.G89636@ury.york.ac.uk> References: <20050918101327.H86911@ury.york.ac.uk> <20050918154406.GA5846@soaustin.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Cc: kris@freebsd.org, python@freebsd.org Subject: Re: Fixing port www/zope-cmfphoto 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: Sun, 18 Sep 2005 18:40:35 -0000 On Sun, 18 Sep 2005, Mark Linimon wrote: > On Sun, Sep 18, 2005 at 11:04:27AM +0100, Gavin Atkinson wrote: >> my first attempt at understanding the ports build infrastructure. > > Well, you've chosen a complex topic on which to dive into it :-) Often the best way to learn :) >> Despite zope-cmfphoto declaring it requires Python 2.3 (indirectly, via >> the USE_ZOPE=yes option), somehow RUN_DEPENDS is being populated with >> py24-imaging-1.1.5.tbz rather than py23-imaging-1.1.5.tbz - presumably >> this is being done by the pointyhat build scripts based soley on the fact >> that it is the newest/default version? > > As best I can tell the pointyhat scripts use packages as prerequisites > for every port that gets built. (Otherwise, the amount of time required > for the builds would be vastly increased). My guess is that the default > package of py-imaging maps to py24-imaging rather than py23-imaging. > Let's see if that's correct .... > > Here is a graphical map of the dependencies as seen by a system that has > Python 2.4 installed on it: > > http://portsmon.FreeBSD.org/portdependencytree.py?category=www&portname=zope-cmfphoto > > So www/zope-cmfphoto depends on lang/python23 and graphics/py-imaging; > but graphics/py-imaging depends on lang/python (2.4), which would, when > compiled in a clean system, indeed produce package py24-imaging, not > py23-imaging. > > So this may be more a problem with the framework, not with pointyhat > (e.g. the fact that you can only depend on a port, not a specific package > of it). I wonder if the way forward is to define a list of flags which are to be inherited by dependencies... For example, a similar issue will presumably also affect Perl ports, and possibly ports with USE_GCC version dependencies (eg if one port is compiled with one version and a dependency is compiled with another version of GCC, there is no guarantee the two can be linked together). > My guess would be that we need to mark these as NO_PACKAGE as a workaround > until Zope can fix their code to not rely on 2.3, as some of these other > ports have done. This has since been done. Once I understand the infrastructure a bit more, I might have a look to see if there is a solution to this issue, although I suspect it'll be beyond my abilities. Thanks, Gavin