From owner-freebsd-ports@FreeBSD.ORG Wed Nov 27 21:59:05 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 21622889 for ; Wed, 27 Nov 2013 21:59:05 +0000 (UTC) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 6648F2DF1 for ; Wed, 27 Nov 2013 21:58:47 +0000 (UTC) Received: (qmail 78552 invoked by uid 89); 27 Nov 2013 21:51:47 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@88.217.181.116) by mail.grem.de with ESMTPA; 27 Nov 2013 21:51:47 -0000 Date: Wed, 27 Nov 2013 22:51:47 +0100 From: Michael Gmelin To: "Helmut Schneider" Subject: Re: FreeBSD Port: py27-pytz-2013.8,1 Message-ID: <20131127225147.6a856316@bsd64.grem.de> In-Reply-To: References: <20131127181902.14b0bc64@bsd64.grem.de> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.18; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Nicola Vitale , freebsd-ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Nov 2013 21:59:05 -0000 On Wed, 27 Nov 2013 22:22:12 +0100 "Helmut Schneider" wrote: > From: Michael Gmelin > > > Does it work when NO_STAGE=yes? > > (e.g. NO_STAGE=yes portupgrade packagename) > > Yes, builds fine. What does that mean? Do I need to change something > or does the port? > I'm asking because I raised ports/184293 and would like to update it > accordingly. > > Thanks, Helmut > I had a similar issue on a 9.1 system using portmaster (NO_STAGE fixed it) last week, while portupgrade on a freshly installed system had no issues (no matter which packaging system pkgng/oldschool packages etc.). I can only speculate about the exact reasons, maybe it's related to the recent switch from py-distribute to py-setuptools in combination with staging support or only to upgrading from a specific version. I couldn't reproduce the problem, since I didn't keep the original package. Maybe it's not worthwhile chasing this one. In regards to your PR: I don't think this is related to py-boto specifically, but more to recent ports infrastructure changes, so I would suggest to close the PR and either open another one for the ports infrastructure (if you have enough details), keep trying to get attention on ports@ or simply forget about it ;) -- Michael Gmelin