Date: Mon, 25 Jul 2011 14:25:32 +0200 From: =?UTF-8?B?VGlsbWFuIEtlc2tpbsO2eg==?= <arved@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: Time to mark portupgrade deprecated? Message-ID: <4E2D60BC.50908@FreeBSD.org> In-Reply-To: <CAF6rxg=TfxbKJwbcm6_c8P7m6%2B-pzvB9SpwKB99%2BLDe4OM%2BeLA@mail.gmail.com> References: <CAF6rxg=TfxbKJwbcm6_c8P7m6%2B-pzvB9SpwKB99%2BLDe4OM%2BeLA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E2D60BC.50908>