Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 5 May 2016 13:19:55 +0100
From:      Matthew Seaman <matthew@FreeBSD.org>
To:        freebsd-questions@freebsd.org
Subject:   Re: Freebsd-update not upgrading to 10.3-RELEASE-p2
Message-ID:  <966a21fb-7463-6001-0b5e-8f45863eb35e@freebsd.org>
In-Reply-To: <3742178.aKMkPuQEMT@curlew.lan>
References:  <3742178.aKMkPuQEMT@curlew.lan>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--46kR88outv0QObEGW7fSTGW4RuqTdTP04
Content-Type: multipart/mixed; boundary="hx5cao1p1N4p6lQJ0EcRX9jEBiS8bIQxS"
From: Matthew Seaman <matthew@freebsd.org>
To: freebsd-questions@freebsd.org
Message-ID: <966a21fb-7463-6001-0b5e-8f45863eb35e@freebsd.org>
Subject: Re: Freebsd-update not upgrading to 10.3-RELEASE-p2
References: <3742178.aKMkPuQEMT@curlew.lan>
In-Reply-To: <3742178.aKMkPuQEMT@curlew.lan>

--hx5cao1p1N4p6lQJ0EcRX9jEBiS8bIQxS
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 05/05/16 12:42, Mike Clarke wrote:
> As advised in FreeBSD-SA-16:17.openssl I've just attempted to run freeb=
sd-
> update but it tells me that no updates are needed.
>=20
> This is the first time I've run freebsd-update since I upgraded to 10.3=
 on 30th=20
> April.
>=20
> The most recent revision shown in /usr/src/UPDATING is 20160329: 10.3-R=
ELEASE=20
> so I would have expected freebsd-update to have taken me up to 10.3-REL=
EASE-p2=20
> r299066.
>=20
> curlew:/home/mike% uname -a
> FreeBSD curlew.lan 10.3-RELEASE FreeBSD 10.3-RELEASE #0 r297264: Fri Ma=
r 25=20
> 02:10:02 UTC 2016    =20
> root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
> curlew:/home/mike% freebsd-version -ku
> 10.3-RELEASE
> 10.3-RELEASE-p1

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.

You can be sure this has been bought to the attention of the responsible
people, or will have been by the end of the day.  People are looking
into the problem right now, but we may need to wait on some others in
California, where it is currently the small hours and they are almost
certainly asleep.

	Cheers,

	Matthew




--hx5cao1p1N4p6lQJ0EcRX9jEBiS8bIQxS--

--46kR88outv0QObEGW7fSTGW4RuqTdTP04
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXKzprAAoJEABRPxDgqeTnrZgQALI2KqpHEehFwKltrDmgvbB5
J5h123BWDpqJKrptOCCBD7NcqC3GfwwnGWLnCmZ2CVz3BpkE2FaSxV2cF6bqGyvq
R6eBmTa9l5XbCneW8HoaCCfVXEKuEp8hmKjpCDRPiT1+W2ZYXvx9iGKcQaBnOyex
ruZuhBLKJh0FfOvXEcAnRwzjSsyIJUYLdHxw0vWLxT3oGh5UMtqMRmzlH1x55dYc
W/6IyZ6aJtJFy3ePVdAy3ZjSH4rz8N1q5jRDTVySUw7rxKp7m5d6yc9EBOWNsi3a
VVR9p5mj73PbIOXXYut4hfJ0TybMvBrl86Xn7BHKOv0lwq4ld1sasjUKI3FdT4BT
4pT4fT6Yo7e2k0kmosFdgdfYQ3UU5G+e/TTNpq44BEvRc+m+2GuKxGW8N0a29+Cd
Lgj9kY/UNq1ua5GabWeSp8r8YlfBpwLZATvdMP/mrx40yTZaj6QQPEDoA5ciufMW
ahoCR6vhpA9sMB3g2JX5AjdNRiwerWH1OpZ6931Ki+wt0MUfnmVRziCaH9LhCOIG
aIyRu2PiSiTkyhTLSU85b7LTzKDuFyYBQCAB9e581gVMoy3UImEGUfOMW42+IQkx
eXzizdr5ZWs/jkJMjvC3XJVWi17wGTkq/ZWAGKWOcddTG6o5uovtQ0vH78qR+Sm8
Nqf4bsD50u3g/FBAEyce
=LHz+
-----END PGP SIGNATURE-----

--46kR88outv0QObEGW7fSTGW4RuqTdTP04--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?966a21fb-7463-6001-0b5e-8f45863eb35e>