From owner-freebsd-ports-bugs@FreeBSD.ORG Wed Sep 22 20:10:05 2010 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 57875106564A for ; Wed, 22 Sep 2010 20:10:05 +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 474288FC1F for ; Wed, 22 Sep 2010 20:10:05 +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 o8MKA4Uj042659 for ; Wed, 22 Sep 2010 20:10:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o8MKA46X042656; Wed, 22 Sep 2010 20:10:04 GMT (envelope-from gnats) Date: Wed, 22 Sep 2010 20:10:04 GMT Message-Id: <201009222010.o8MKA46X042656@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Peter Schuller Cc: Subject: Re: ports/150728: [PATCH] sysutils/duplicity-devel: update to 0.6.10 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Peter Schuller List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 20:10:05 -0000 The following reply was made to PR ports/150728; it has been noted by GNATS. From: Peter Schuller To: bug-followup@freebsd.org Cc: freebsd@beardz.net Subject: Re: ports/150728: [PATCH] sysutils/duplicity-devel: update to 0.6.10 Date: Wed, 22 Sep 2010 22:08:20 +0200 Tested, I approve. Thanks for the patch, and apologies for the delay in reviewing. To committer: there is a (by now, long) standing issue that 0.6 is no longer '-devel' and should be moved to sysutils/duplicity. The old version should presumably be retained as sysutils/duplicity05 (considering backwards compatibility need is great in this case). What is the appropriate procedure for arranging a switch-a-roo as a non-committer? Does one submit a separate repo copy request with additional instructions on e.g. suggested UPDATING message, etc? -- / Peter Schuller