From owner-freebsd-questions@FreeBSD.ORG Thu Dec 17 22:10:12 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E9911065670 for ; Thu, 17 Dec 2009 22:10:12 +0000 (UTC) (envelope-from battdude@gmail.com) Received: from mail-pz0-f185.google.com (mail-pz0-f185.google.com [209.85.222.185]) by mx1.freebsd.org (Postfix) with ESMTP id 661348FC13 for ; Thu, 17 Dec 2009 22:10:12 +0000 (UTC) Received: by pzk15 with SMTP id 15so1705641pzk.3 for ; Thu, 17 Dec 2009 14:10:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=Uc2JosA72SzuTGBgWkHPNEMbaQkAXa+be6IJThwrVQ0=; b=BzzvDlOcu2lK3z7ImrP+8ItHl6iRnokhDZUVZX9GgXK99G6iwUjXhMHrot9vmesLMO nNPv6JIdCdSMWItP7qXJ8IrlmO2ANg9vGary1s7jieU8fu+4xuIg+8803EeAos6AAIHA jrexIk4OAKu5sgokDF/+fIjIsR3kjZF042u4M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=Rse+/CPMA2MXleQF/cJdVcbIQ/Zm/BmpOYwi2kIOhEQvs1AWdH+crGLmaO9f6VmZLi 91kuxLGNRNYaoCrAQ02c234IF728zhoasS5i3ofYIfVfaPU1X+GJdHonsydSRYbKMw9n WPNDMFxag//HVeAsHk8dCPR+cHUnJTBJHWDCc= MIME-Version: 1.0 Received: by 10.140.82.21 with SMTP id f21mr2150953rvb.51.1261087810940; Thu, 17 Dec 2009 14:10:10 -0800 (PST) In-Reply-To: <20091217052400.GC32037@lonesome.com> References: <7314e5020912161917s355d02c9l16c996043c753044@mail.gmail.com> <19241.45040.505925.616766@jerusalem.litteratus.org> <20091217052400.GC32037@lonesome.com> Date: Thu, 17 Dec 2009 12:10:10 -1000 Message-ID: <7314e5020912171410m172b95c9ke0ffde16ba23567c@mail.gmail.com> From: Kevin To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: portupgrade failure X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 22:10:12 -0000 On Wed, Dec 16, 2009 at 7:24 PM, Mark Linimon wrote: > On Wed, Dec 16, 2009 at 11:13:36PM -0500, Robert Huff wrote: >> The maintainer, ruby@, is aware of this; a check of the PR >> database shows multiple open PRs, none critical but many serious >> going back six months and more. > > As an aside, the Severity and Priority fields have been so often abused > as to have become meaningless. =A0Although I still try to groom the db > for "critical" ones, and thus try to get those some attention, I really > don't think the committers pay much attention. =A0(In general I think > those should be reserved for "data corruption" and "security".) > > The longer-term solution is to remove those as user-settable fields. > >> This hard to understand given portupgrade is the recommended upgrade >> tool. > > Once the individual who was working on it gave it up to the mailing > list, it became one of those "everyone is responsible so no one is > responsible" problems. =A0I don't have a recommended fix for this. > > Having said that, I have a ports tree as of a month ago and portupgrade > was working ok for me. =A0I don't have the cycles to go figure out where > it fails to be able to fix it, sorry. > > mcl Thanks to everyone for the tips. I downgraded to portupgrade-2.4.6_2,2, and am able to update my ports/packages again. I had seen others commenting on portupgrade being broken in the past, but the ruby errors made me wonder if it was actually a ruby problem.