From owner-freebsd-questions@FreeBSD.ORG Wed Sep 10 03:39:15 2014 Return-Path: Delivered-To: freebsd-questions@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 421789D8 for ; Wed, 10 Sep 2014 03:39:15 +0000 (UTC) Received: from empty1.ekahuna.com (empty1.ekahuna.com [198.144.200.196]) by mx1.freebsd.org (Postfix) with ESMTP id 18C96B6D for ; Wed, 10 Sep 2014 03:39:14 +0000 (UTC) Received: from [10.20.30.130] by empty1.ekahuna.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com for ; Tue, 9 Sep 2014 20:04:46 -0700 From: "Philip J. Koenig" Organization: The Electric Kahuna Organization To: freebsd-questions@freebsd.org Date: Tue, 09 Sep 2014 20:04:08 -0700 MIME-Version: 1.0 Subject: freebsd-update problems 9.x to 9.x Reply-to: pjklist2@ekahuna.com Priority: normal X-mailer: Pegasus Mail for Windows (4.63) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Message-ID: <20140910030446767.AAC240@empty1.ekahuna.com@[10.20.30.130]> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2014 03:39:15 -0000 [REPOST - sent 8/25 and no answers yet] I've extensively searched the list archives and cannot find an answer to this. I get the (apparently well-known) error below when trying to use the command "freebsd-update upgrade -r 9.3-RELEASE" on a box (actually VM) running 9.0-RELEASE (p7). > "The update metadata is correctly signed, but failed an integrity > check. Cowardly refusing to proceed any further." All the mentions I've seen of this issue pertain to either upgrading to 9.x from 8.x or earlier, or upgrading 9.x to 10.0. Even though I initially patched to the p7 level of 9.0-RELEASE before trying to do this upgrade (using freebsd-update actually, and it seemed to work fine for that), I still tried the often-suggested fix for the known issue of older versions of freebsd-update not recognizing "%" and "@" characters. The result was that there were no changes made to the freebsd-update script. (diff says it's identical to the existing file) Anything else I can try? Here's the sed command suggested/tried: sed -i '' -e 's/=_%@_/' /usr/sbin/freebsd-update TIA -- Philip J. Koenig pjklist@ekahuna.com Electric Kahuna Systems -- Computers & Communications for the New Millenium