From owner-freebsd-stable@freebsd.org Sat Sep 1 17:09:49 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 86D71FF5158 for ; Sat, 1 Sep 2018 17:09:49 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3B75E73C70 for ; Sat, 1 Sep 2018 17:09:49 +0000 (UTC) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from ) id 1fw9P9-0006bY-HP; Sat, 01 Sep 2018 17:09:47 +0000 Date: Sat, 01 Sep 2018 10:09:46 -0700 Message-ID: From: Randy Bush To: Pete Wright Cc: freebsd-stable@freebsd.org Subject: Re: bad hash in repo In-Reply-To: References: <40cbc4e4-c0c8-e9f7-ba88-48dc226b032a@nomadlogic.org> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 Mule/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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: Sat, 01 Sep 2018 17:09:49 -0000 >>>> seeing a lot of these >>>>=20 >>>> 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... 104969ef03336523729ea1df2547267441a13cb040c778e971= b74103e88dbc77 has incorrect hash. >>> these continue; like for a week. for multiple servers, all on the >>> global internet no filters other than samba etc. >>=20 >> have you forced pulling down metadata from the pkg servers?=A0 i have >> gotten into this state in the past and a "pkg update -f" would get me >> out of that scenario. >=20 > # pkg update -f > Updating FreeBSD repository catalogue... > Fetching meta.txz: 100% 944 B 0.9kB/s 00:01 =20 > Fetching packagesite.txz: 100% 6 MiB 2.2MB/s 00:03 =20 > Processing entries: 100% > FreeBSD repository update completed. 32029 packages processed. > All repositories are up to date. > # freebsd-update fetch > Looking up update.FreeBSD.org mirrors... 2 mirrors found. > Fetching metadata signature for 11.1-RELEASE from update5.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... 104969ef03336523729ea1df2547267441a13cb040c778e971b74= 103e88dbc77 has incorrect hash. this is now over two weeks. still multiple systems on public net, v4 and dual stack. randy