Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 5 May 2016 09:09:20 -0700
From:      Nick Rogers <ncrogers@gmail.com>
To:        FreeBSD STABLE <freebsd-stable@freebsd.org>
Subject:   10.1-RELEASE-p33 update does not exist?
Message-ID:  <CAKOb=YbMfMOOOeujLeM6V8oERLbij3GT%2Bod0ogPRNfkHV5Xraw@mail.gmail.com>

next in thread | raw e-mail | index | archive | help
Hello,

I am not sure if this is the appropriate place to inquire about this, but I
am unable to update my 10.1-RELEASE machines to the latest releng branch
(10.1-RELEASE-p33) with the latest FreeBSD-SA-16:17.openssl advisory.

Here's what happens when I try freebsd-update.

# freebsd-version -ku
10.1-RELEASE-p31
10.1-RELEASE-p32
# uname -v
FreeBSD 10.1-RELEASE-p31 #0: Wed Mar 16 18:39:20 UTC 2016
root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
# freebsdupdatec
# freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 4 mirrors found.
Fetching metadata signature for 10.1-RELEASE from update6.freebsd.org...
done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.

The following files are affected by updates, but no changes have
been downloaded because the files have been modified locally:
/etc/mtree/BSD.usr.dist
/var/db/etcupdate/current/etc/mtree/BSD.usr.dist
/var/db/etcupdate/current/etc/ntp.conf
/var/db/mergemaster.mtree

No updates needed to update system to 10.1-RELEASE-p32.

There seems to be some discussion that is perhaps related to this issue in
this bug:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209147

Thanks.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKOb=YbMfMOOOeujLeM6V8oERLbij3GT%2Bod0ogPRNfkHV5Xraw>