From nobody@FreeBSD.org  Thu Apr  3 09:34:50 2014
Return-Path: <nobody@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 78539E32
	for <freebsd-gnats-submit@FreeBSD.org>; Thu,  3 Apr 2014 09:34:50 +0000 (UTC)
Received: from cgiserv.freebsd.org (cgiserv.freebsd.org [IPv6:2001:1900:2254:206a::50:4])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by mx1.freebsd.org (Postfix) with ESMTPS id 65923143
	for <freebsd-gnats-submit@FreeBSD.org>; Thu,  3 Apr 2014 09:34:50 +0000 (UTC)
Received: from cgiserv.freebsd.org ([127.0.1.6])
	by cgiserv.freebsd.org (8.14.8/8.14.8) with ESMTP id s339YoVf061661
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 3 Apr 2014 09:34:50 GMT
	(envelope-from nobody@cgiserv.freebsd.org)
Received: (from nobody@localhost)
	by cgiserv.freebsd.org (8.14.8/8.14.8/Submit) id s339YoYG061652;
	Thu, 3 Apr 2014 09:34:50 GMT
	(envelope-from nobody)
Message-Id: <201404030934.s339YoYG061652@cgiserv.freebsd.org>
Date: Thu, 3 Apr 2014 09:34:50 GMT
From: Jonas Blow <jonas.bulow@gmail.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: freebsd-update destroys installation
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         188220
>Category:       bin
>Synopsis:       freebsd-update(8) destroys installation
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    cperciva
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          update
>Submitter-Id:   current-users
>Arrival-Date:   Thu Apr 03 09:40:01 UTC 2014
>Closed-Date:    
>Last-Modified:  Wed Apr 23 08:10:00 UTC 2014
>Originator:     Jonas Blow
>Release:        10.0-RELEASE
>Organization:
>Environment:
FreeBSD jonasbu-netlab 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014     root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
>Description:
I have used freebsd-update to upgrade the system. After upgrade there are many mismatches with what is expected according to freebsd-update IDS.

# freebsd-update fetch install
Looking up update.FreeBSD.org mirrors... 5 mirrors found.
Fetching metadata signature for 10.0-RELEASE from update2.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

No updates needed to update system to 10.0-RELEASE-p0.
No updates are available to install.
Run '/usr/sbin/freebsd-update fetch' first.
# freebsd-update IDS | wc -l
39485

More or less every file has the wrong SHA256. 


>How-To-Repeat:
Use freebsd-update to upgrade the system to 10.0-RELEASE.
>Fix:
Reinstall from scratch.

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->cperciva 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Sun Apr 13 23:27:34 UTC 2014 
Responsible-Changed-Why:  
Over to maintainer. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=188220 

From: David Chisnall <theraven@FreeBSD.org>
To: bug-followup@FreeBSD.org, jonas.bulow@gmail.com
Cc:  
Subject: Re: bin/188220: freebsd-update(8) destroys installation
Date: Wed, 23 Apr 2014 09:05:01 +0100

 This has also been my experience.  Of the four machines that I've =
 updated from 9.x to 10.0 with freebsd-update, not one has ended up with =
 a working 10 configuration.    I thought one had done, but it turned out =
 that it only had a 10 kernel, but most of a 9.2 userland, which I only =
 discovered as a result of pkg installing the wrong version kernel =
 modules. =20
 
 I've recovered a couple by doing the env UNAME_r=3D trick and forcing =
 freebsd-update to run again, but this didn't work for two of them and =
 I've ended up having to untar the files from the distribution sets.
 
 Updating then to 10.0-RELEASE-p1 with freebsd-update then works fine, so =
 it's just something about the 9->10 transition (and, yes, I did remember =
 to do freebsd-update fetch / install / reboot first to make sure I had =
 the latest version of freebsd-update).
 
 Given that freebsd-update IDS can detect that it's failed to install =
 some of the files, it would be nice if it could then fix them, rather =
 than just giving you a long list of things that you have to fix =
 manually...
 
 David
 
>Unformatted:
