From owner-freebsd-stable@FreeBSD.ORG Fri Feb 21 22:09:43 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 04644D49; Fri, 21 Feb 2014 22:09:43 +0000 (UTC) Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B278C1259; Fri, 21 Feb 2014 22:09:42 +0000 (UTC) Received: by mail-pd0-f169.google.com with SMTP id v10so3858954pde.14 for ; Fri, 21 Feb 2014 14:09:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=N+ZI+Nhh0iRA9FgEw5ud/q0cY2YCHF+3pg3nUUqpZBo=; b=CIf1bTgL/N6QDtcyFsP4J3oLIObVFo3dc00gCvyHKWGjRTimtehJdBl/SiG35/NSPT cBo5lH1a+Jd1S394vPkfK1scyyuPLQMFqClko4Ge4XB5pOHm6FNH8Cbxw6ZhFVMG5dIW cHuYgUHtKJD0XmLPpiq+nLgcDRCXWUrREknE984FnvNElC+rEcF3hIjkjl/XUu9xXVtH hZ4a2PMVDsxgrJHw8AmiZDcBNiG6tUmkocyR6D3bPjrNYf+G6XpEb20CrZ4EGTkdMrw+ 14wHhY6RpRiLil/CDFwboD2UITuzJx0EsKGVruiRB/HGTf63//aAyOVame9LeTRbsw3s W1rQ== X-Received: by 10.68.221.42 with SMTP id qb10mr11561926pbc.65.1393020581682; Fri, 21 Feb 2014 14:09:41 -0800 (PST) Received: from [192.168.1.7] (ppp59-167-128-11.static.internode.on.net. [59.167.128.11]) by mx.google.com with ESMTPSA id ei4sm24670552pbb.42.2014.02.21.14.09.38 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Feb 2014 14:09:41 -0800 (PST) Message-ID: <5307CE99.1050605@FreeBSD.org> Date: Sat, 22 Feb 2014 09:09:29 +1100 From: Kubilay Kocak User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Thunderbird/27.0 MIME-Version: 1.0 To: Dewey Hylton , gahr@FreeBSD.org Subject: Re: lang/expect -- update coming References: <1134405947.26568.1392997901552.JavaMail.root@mail> In-Reply-To: <1134405947.26568.1392997901552.JavaMail.root@mail> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 22 Feb 2014 00:15:19 +0000 Cc: freebsd-stable@FreeBSD.org, romain garbage , Martin Wilke , jmohacsi@bsd.hu, pdagog@gmail.com, freebsd-current@FreeBSD.org, freebsd-ports@FreeBSD.org, wrighrc@gmail.com X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: koobs@FreeBSD.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Feb 2014 22:09:43 -0000 On 22/02/2014 2:51 AM, Dewey Hylton wrote: >> From: "Pietro Cerutti" >> To: freebsd-ports@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-current@FreeBSD.org >> Cc: jmohacsi@bsd.hu, "Martin Wilke" , wrighrc@gmail.com, freenx@deweyonline.com, pdagog@gmail.com, >> "romain garbage" >> Sent: Friday, February 21, 2014 10:38:24 AM >> Subject: Re: lang/expect -- update coming >> >> On 2014-Feb-21, 15:38, Pietro Cerutti wrote: >>> All, >>> >>> I'm planning to commit an update to bring lang/expect up to the >>> latest >>> 5.45 version. At the same time, I'm going to kill >>> lang/expect-devel, >>> which would otherwise be left lagging behind at 5.44. >>> >>> The following ports use either expect or -devel (maintainers CC'd). >>> >>> devel/pecl-expect >>> net-mgmt/rancid >>> net-mgmt/rancid-devel >> >> Turns out my regexp-foo sucked this time.. Here's a more complete >> list. >> Thanks koobs@ for noticing. >> >> devel/pecl-expect >> misc/dejagnu >> misc/sshbuddy >> net/freenx >> net-mgmt/netmagis-topo >> et-mgmt/rancid >> net-mgmt/rancid-devel >> security/belier > > i'm no longer maintaining the freenx/nxserver ports. they are so outdated at this point they should probably be killed off as well, but i have no idea who might still be using them. While the MAINTAINER line references your email, you do, even if not for version updates. As maintainer, you have a couple of PR options up your sleeve: - Reset maintainer, so someone else can pick them up - Set EXPIRE with reason and an appropriate lead time to removal The above can also serve to communicate to users-come-would-be-maintainers that they might need attention and provide the impetus to jump in and have a go :) Koobs