From owner-freebsd-stable@freebsd.org Wed Aug 22 16:46:34 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7722F108EA57 for ; Wed, 22 Aug 2018 16:46:34 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F17507E0AE for ; Wed, 22 Aug 2018 16:46:33 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.106] (cpe-76-175-75-27.socal.res.rr.com [76.175.75.27]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 71bd45bf TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Wed, 22 Aug 2018 09:46:32 -0700 (PDT) Subject: Re: bad hash in repo To: freebsd-stable@freebsd.org References: From: Pete Wright Message-ID: <40cbc4e4-c0c8-e9f7-ba88-48dc226b032a@nomadlogic.org> Date: Wed, 22 Aug 2018 09:46:30 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2018 16:46:34 -0000 On 8/22/18 9:19 AM, Randy Bush wrote: >> seeing a lot of these >> >> Looking up update.FreeBSD.org mirrors... 2 mirrors found. >> Fetching metadata signature for 11.1-RELEASE from update4.freebsd.org... done. >> Fetching metadata index... done. >> Inspecting system... done. >> Preparing to download files... done. >> Fetching 2 patches.. done. >> Applying patches... done. >> Fetching 2 files... 104969ef03336523729ea1df2547267441a13cb040c778e971b74103e88dbc77 has incorrect hash. > these continue; like for a week. for multiple servers, all on the > global internet no filters other than samba etc. have you forced pulling down metadata from the pkg servers?  i have gotten into this state in the past and a "pkg update -f" would get me out of that scenario. -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA