From owner-freebsd-ports-bugs@FreeBSD.ORG Fri Jun 17 20:50:09 2011 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 436621065678 for ; Fri, 17 Jun 2011 20:50:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 20B7C8FC21 for ; Fri, 17 Jun 2011 20:50:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p5HKo7Jt021603 for ; Fri, 17 Jun 2011 20:50:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p5HKo7A8021602; Fri, 17 Jun 2011 20:50:07 GMT (envelope-from gnats) Resent-Date: Fri, 17 Jun 2011 20:50:07 GMT Resent-Message-Id: <201106172050.p5HKo7A8021602@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-ports-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Ruslan Mahmatkhanov Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32821106566C for ; Fri, 17 Jun 2011 20:46:05 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 22A208FC13 for ; Fri, 17 Jun 2011 20:46:05 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p5HKk45D083471 for ; Fri, 17 Jun 2011 20:46:04 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id p5HKk4Tr083470; Fri, 17 Jun 2011 20:46:04 GMT (envelope-from nobody) Message-Id: <201106172046.p5HKk4Tr083470@red.freebsd.org> Date: Fri, 17 Jun 2011 20:46:04 GMT From: Ruslan Mahmatkhanov To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: ports/157962: [MAINTAINER] devel/py-pyro: misc changes X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jun 2011 20:50:09 -0000 >Number: 157962 >Category: ports >Synopsis: [MAINTAINER] devel/py-pyro: misc changes >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: maintainer-update >Submitter-Id: current-users >Arrival-Date: Fri Jun 17 20:50:07 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Ruslan Mahmatkhanov >Release: 9.0-CURRENT >Organization: >Environment: 9.0-CURRENT i386 >Description: - use CHEESESHOP instead absolute download url - add LICENSE - minimal python version is 2.6 - add USE_DOS2UNIX - whitespace fixes in pkg-descr tinderbox buildlog (8.2-RELEASE): http://happy-nation.by.ru/ports/tb/py27-pyro-4.6_1.log >How-To-Repeat: >Fix: Patch attached with submission follows: diff -ruNa py-pyro.orig/Makefile py-pyro/Makefile --- py-pyro.orig/Makefile 2011-06-17 12:09:34.000000000 +0400 +++ py-pyro/Makefile 2011-06-18 00:33:35.000000000 +0400 @@ -7,15 +7,19 @@ PORTNAME= pyro PORTVERSION= 4.6 +PORTREVISION= 1 CATEGORIES= devel python -MASTER_SITES= http://pypi.python.org/packages/source/P/Pyro4/ +MASTER_SITES= CHEESESHOP PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX} DISTNAME= Pyro4-${PORTVERSION} MAINTAINER= cvs-src@yandex.ru COMMENT= Distributed Object Middleware for Python(IPC/RPC) -USE_PYTHON= 2.5+ +LICENSE= MIT + +USE_DOS2UNIX= yes +USE_PYTHON= 2.6+ USE_PYDISTUTILS= yes PYDISTUTILS_PKGNAME= Pyro4 diff -ruNa py-pyro.orig/pkg-descr py-pyro/pkg-descr --- py-pyro.orig/pkg-descr 2011-06-16 23:11:10.000000000 +0400 +++ py-pyro/pkg-descr 2011-06-18 00:32:10.000000000 +0400 @@ -8,8 +8,8 @@ socket programming details are taken care of, you just call a method on a remote object as if it were a local object! -Pyro provides an object-oriented form of RPC. You can use Pyro within a -single system but also use it for IPC. For those that are familiar with +Pyro provides an object-oriented form of RPC. You can use Pyro within a +single system but also use it for IPC. For those that are familiar with Java, Pyro resembles Java's Remote Method Invocation (RMI). It is less similar to CORBA - which is a system- and language independent Distributed Object Technology and has much more to offer than Pyro or >Release-Note: >Audit-Trail: >Unformatted: