From owner-freebsd-ports@FreeBSD.ORG Fri Jan 16 20:01:32 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2EB5910656E1 for ; Fri, 16 Jan 2009 20:01:32 +0000 (UTC) (envelope-from usgrishin@samaradom.ru) Received: from mx1.samaradom.ru (june.samaradom.ru [85.113.63.225]) by mx1.freebsd.org (Postfix) with ESMTP id D26638FC0C for ; Fri, 16 Jan 2009 20:01:31 +0000 (UTC) (envelope-from usgrishin@samaradom.ru) Received: from [10.62.116.37] (port=65262 helo=[192.168.0.15]) by mx1.samaradom.ru with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LNsou-00055t-JP for freebsd-ports@freebsd.org; Fri, 16 Jan 2009 21:49:24 +0400 Message-ID: <4970C86E.6050900@samaradom.ru> Date: Fri, 16 Jan 2009 21:48:30 +0400 From: Yuriy Grishin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081204 SeaMonkey/1.1.14 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Subject: [www/sams] why did commiter bump PORTREVISION ? Now it's broken. X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: uzgrishin@mail.ru List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2009 20:01:33 -0000 Hello I'm the maintainer of the port www/sams. In early of December 2008 the developer released new version of SAMS -- 1.0.4 I tried to take most of users comments and sent pr http://www.freebsd.org/cgi/query-pr.cgi?pr=129816 Few days afterwards miwi wrote that he couldn't extract my diff (may be because I had sent it using windows+seamonkey?) I upload files to my homepage and submitted follow-up. A few days later I saw that the port has been updated, BUT: 1) http://www.freebsd.org/cgi/query-pr.cgi?pr=129816 the pr is open (is it normal?) 2) commiter bumped PORTREVISION and it leads to port corruption because -------------------Makefile------------------- .... DISTNAME= ${PORTNAME}-${PORTVERSION} .... -------------------Makefile------------------- thus it searches sams-1.0.3 instead of sams-1.0.4 ==> hash check will fail Questions : 1.Should have I say in the pr that it was not only has been updated by me but also by the developer? 2.What should I do now?