From owner-freebsd-questions@freebsd.org Thu May 5 17:31:51 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ED2B4B2E68C for ; Thu, 5 May 2016 17:31:51 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (jacobs.geeks.org [204.153.247.1]) (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 D3F2F19C9 for ; Thu, 5 May 2016 17:31:51 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (localhost [127.0.0.1]) by after-clamsmtpd.geeks.org (Postfix) with ESMTP id 78B73110236 for ; Thu, 5 May 2016 12:24:18 -0500 (CDT) Received: by mail.geeks.org (Postfix, from userid 1003) id 56F7B110235; Thu, 5 May 2016 12:24:18 -0500 (CDT) Date: Thu, 5 May 2016 12:24:18 -0500 From: Doug McIntyre To: freebsd-questions@freebsd.org Subject: Re: Freebsd-update not upgrading to 10.3-RELEASE-p2 Message-ID: <20160505172418.GA50983@geeks.org> References: <3742178.aKMkPuQEMT@curlew.lan> <966a21fb-7463-6001-0b5e-8f45863eb35e@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <966a21fb-7463-6001-0b5e-8f45863eb35e@freebsd.org> User-Agent: Mutt/1.6.0 (2016-04-01) X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2016 17:31:52 -0000 On Thu, May 05, 2016 at 01:19:55PM +0100, Matthew Seaman wrote: > On 05/05/16 12:42, Mike Clarke wrote: > > As advised in FreeBSD-SA-16:17.openssl I've just attempted to run freebsd- > > update but it tells me that no updates are needed. .. > Yes, this has been reported by many people in various different fora. > There is a problem with freebsd-update(8) and the latest SA and ENs. Hmm, nothing fixed yet, but to me, the update.freebsd.org site seems to have reverted back in time. Ie. I was able to do upgrades to 10.3-RELEASE-p1 over last weekend, but yet, the http://update.freebsd.org/10.3-RELEASE/amd64/latest.ssl lists 10.3-RELEASE-p0 as the latest.. :-( freebsd-update|amd64|10.3-RELEASE|0|8797efb5915e47a0a9bbcd69e1389d010a8041f8f1ca2c0dcfc0c4e4eca3fa8c|1525132800 Simularly, http://update.freebsd.org/10.2-RELEASE/amd64/latest.ssl is still stuck on 10.2-RELEASE-p15 freebsd-update|amd64|10.2-RELEASE|15|d0dab0d2567fd8b3a448781cf5486e2f0e2d46fb71adecdaf7f84a0e4d2dc95e|1483228800 And all mirrors of update?.freebsd.org are matching and identical as well. Something happened to update? Bad rollouts of 10.3-RELEASE-p2 and 10.2-RELEASE-p16?