freebsd-update failed from 10.1-RELEASE-p10 to p12 error messages showed: raycherng@fujitsu-freebsd </home/raycherng> sudo freebsd-update fetch Password: Looking up update.FreeBSD.org mirrors... none found. Fetching metadata signature for 10.1-RELEASE from update.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. The following files will be added as part of updating to 10.1-RELEASE-p12: /usr/src/contrib/file/magic/Magdir/kerberraycherng@fujitsu-freebsd </home/raycherng> uname -a FreeBSD fujitsu-freebsd 10.1-RELEASE-p10 FreeBSD 10.1-RELEASE-p10 #0: Wed May 13 06:54:13 UTC 2015 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 os /usr/src/contrib/file/magic/Magdir/meteorological /usr/src/contrib/file/magic/Magdir/qt /usr/src/crypto/openssl/util/mkbuildinf.pl raycherng@fujitsu-freebsd </home/raycherng> sudo freebsd-update install Installing updates...install: ///usr/src/contrib/file/magic/Magdir/kerberos: No such file or directory install: ///usr/src/contrib/file/magic/Magdir/meteorological: No such file or directory install: ///usr/src/contrib/file/magic/Magdir/qt: No such file or directory install: ///usr/src/crypto/openssl/util/mkbuildinf.pl: No such file or directory done. My FreeBSD version is raycherng@fujitsu-freebsd </home/raycherng> uname -a FreeBSD fujitsu-freebsd 10.1-RELEASE-p10 FreeBSD 10.1-RELEASE-p10 #0: Wed May 13 06:54:13 UTC 2015 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 Hardware : Fujitsu T2010 laptop
I'm having the same issue. Now stuck with 10.1-RELEASE-p10. This is a FreeBSD VM on CloudAtCost: uname -a FreeBSD daemon 10.1-RELEASE-p10 FreeBSD 10.1-RELEASE-p10 #0: Wed May 13 06:54:13 UTC 2015 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
After installing /usr/src, update was OK.
How to install /usr/src? So is it still a bug? Users usually don't have /usr/src installed...
(In reply to raycherng from comment #3) I used svn to update. I guess the svn version of src doesn't make any sense on 10.1-RELEASE... But anyways by installing src the problem was solved.
This was fixed in stable/10 as r284936.