From owner-freebsd-python@FreeBSD.ORG Fri Oct 13 07:52:16 2006 Return-Path: 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 8EF0816A407 for ; Fri, 13 Oct 2006 07:52:16 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4FA243D55 for ; Fri, 13 Oct 2006 07:52:12 +0000 (GMT) (envelope-from avg@icyb.net.ua) Received: from [212.40.38.87] (oddity-e.topspin.kiev.ua [212.40.38.87]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA12135 for ; Fri, 13 Oct 2006 10:52:10 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <452F45A9.3020203@icyb.net.ua> Date: Fri, 13 Oct 2006 10:52:09 +0300 From: Andriy Gapon User-Agent: Thunderbird 1.5.0.7 (X11/20060915) MIME-Version: 1.0 To: python@FreeBSD.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: [Fwd: python 2.5 upgrade: error in devel/py-sip] X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2006 07:52:16 -0000 Forwarding this here to get more attention. There was a number of similar reports about failures in py-sip on ports@. -------- Original Message -------- Subject: python 2.5 upgrade: error in devel/py-sip Date: Wed, 11 Oct 2006 21:49:26 +0300 From: Andriy Gapon To: freebsd-ports@freebsd.org devel/py-sip port failed to get upgraded to python 2.5 using standard procedure. This port is used by py-qt which is used by some python GUI applications. The reason for the failure is changes in object.h, struct PyHeapTypeObject: fields type and name were renamed in 2.5 to ht_type and ht_name correspondingly. I was able to get the port updated and working [tested] by simply blanket replacing occurrences of "super.type" and "super.name" with "super.ht_type" and "super.ht_name". Thus the port probably needs to have a python-version-specific patch. P.S. the port doesn't seem to have a maintainer. -- Andriy Gapon -- Andriy Gapon