From owner-freebsd-ports@FreeBSD.ORG Mon Jul 25 12:25:46 2011 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 1CC541065670 for ; Mon, 25 Jul 2011 12:25:46 +0000 (UTC) (envelope-from arved@FreeBSD.org) Received: from mail01.rise-w.com (iris.rise-s.com [88.116.105.226]) by mx1.freebsd.org (Postfix) with ESMTP id 8B41B8FC25 for ; Mon, 25 Jul 2011 12:25:45 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail01.rise-w.com (Postfix) with ESMTP id 2A34E40E09F; Mon, 25 Jul 2011 14:23:33 +0200 (CEST) Received: from [192.168.59.162] (chello080108063010.8.11.vie.surfer.at [80.108.63.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.rise-world.com (Postfix) with ESMTPSA id 3615040E056; Mon, 25 Jul 2011 14:23:28 +0200 (CEST) Message-ID: <4E2D60BC.50908@FreeBSD.org> Date: Mon, 25 Jul 2011 14:25:32 +0200 From: =?UTF-8?B?VGlsbWFuIEtlc2tpbsO2eg==?= User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Thunderbird/3.1.11 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: Time to mark portupgrade deprecated? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jul 2011 12:25:46 -0000 On 07/25/2011 04:20 AM, Eitan Adler wrote: > At this point noone is maintaining portupgrade any more and a large > number of PRs have been filed against it (see > http://www.freebsd.org/cgi/query-pr-summary.cgi?text=portupgrade). No > one has stepped up to do the work to fix these bugs so it is time to > officially drop it. > > I shortly went through the list. There are currently 22 PRs filed against portupgrade Of these: 4 are general problems of the ports collection/pkg_tools. (architecture-specific INDEX, Detecting of OPTIONs set, Overriding/removing files changed by the user etc.) 2 are documentation bugs 1 wishlist item 4 contain patches 1 i believed is already fixed, i set to feedback. So this leaves the following, which need someone (a maintainer?) to investigate/write a patch: 112818 ruby ports open non-criti medium current-us ports-mgmt/portupgrade -a fails with database error 127019 ruby ports open serious medium current-us ports-mgmt/portupgrade does not recognize fail conditions 127889 ruby ports open non-criti low current-us ports-mgmt/portupgrade detects spurious failures and skips ports unnecessarily 129930 ruby ports open serious high current-us ports-mgmt/portupgrade - portinstall tries to install dependencies twice 131111 ruby ports open serious medium current-us ports-mgmt/portupgrade-devel: completely removes package on installation error 140008 ruby ports open non-criti medium current-us ports-mgmt/portupgrade-devel chokes on bsdpan pkgs 147242 ruby ports open critical medium current-us ports-mgmt/portupgrade incorrectly remove old port when new one fails to compile 151662 ruby ports open non-criti low current-us ports-mgmt/portupgrade: upgrade of autoconf leaves old version 154210 ruby ports open serious medium current-us ports-mgmt/portupgrade 2.4.8_1,2: cross-thread violation on rb_gc() IMHO the situation is not that bad, that we need to DEPRECATE it.