Date: Mon, 10 Oct 2016 08:04:58 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-stable@freebsd.org Subject: Re: Failing to upgrade from 10.1-RELEASE to 10.3-STABLE Message-ID: <a791313f-63eb-9358-4874-402a92ccfef1@FreeBSD.org> In-Reply-To: <d1813e22-b8bc-57c7-9691-1f6d8023d95d@m5p.com> References: <5942b107-349b-4a97-7f26-e24ea09079bb@m5p.com> <20161009195746.GC4560@home.opsec.eu> <d1813e22-b8bc-57c7-9691-1f6d8023d95d@m5p.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --qXQtVv2HgJlCiKIMBw8m0RcEn7PIUptLn Content-Type: multipart/mixed; boundary="g6GvrfaF0uUcTSJwPBT1oF8tR7I6IwuEh"; protected-headers="v1" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-stable@freebsd.org Message-ID: <a791313f-63eb-9358-4874-402a92ccfef1@FreeBSD.org> Subject: Re: Failing to upgrade from 10.1-RELEASE to 10.3-STABLE References: <5942b107-349b-4a97-7f26-e24ea09079bb@m5p.com> <20161009195746.GC4560@home.opsec.eu> <d1813e22-b8bc-57c7-9691-1f6d8023d95d@m5p.com> In-Reply-To: <d1813e22-b8bc-57c7-9691-1f6d8023d95d@m5p.com> --g6GvrfaF0uUcTSJwPBT1oF8tR7I6IwuEh Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 09/10/2016 23:56, George Mitchell wrote: > On 10/09/16 15:57, Kurt Jaeger wrote: >> Hi! >> >>> What am I doing wrong? (I get the same failure attempting to upgrade= >>> to 10.1-RELEASE and 10.2-RELEASE.) -- George >> >> Ah, one thing: >> >> Please do update to the latest 10.1-REL patch level, first. >> > After upgrading to the latest 10.1-RELEASE: >=20 > I can update to 10.3-RELEASE, and that will probably do for now. > Should it have worked to update from 10.1-RELEASE to 10.3-STABLE > directly? If I decide to upgrade from 10.3-RELEASE to 10.3-STABLE > later on, should I expect that to work? -- George Most of the time you should be able to upgrade from any patch level of release to the latest on any supported release branch using freebsd-update(8). However there have been a number of occasions where changes to freebsd-update itself cause that not to work. This is one of those occasions. As you've discovered, the answer is to update to the latest patch level of the branch you're already on, which will pull in the necessary fixes to freebsd-update(8), and then you can upgrade to a more recent branch. As other people have noted, you can't use freebsd-update(8) to get to 10.3-STABLE -- for that, you need to build the OS from source. Cheers, Matthew --g6GvrfaF0uUcTSJwPBT1oF8tR7I6IwuEh-- --qXQtVv2HgJlCiKIMBw8m0RcEn7PIUptLn Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJX+z2bXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkAThl0P/10Qb5cRO5wBGzdsQNvGI8W8 mT+DFuZ5xbIC0NSk55fxJar3UPhxjKo1w7mcbCvYSjKX2YuWWxwfjXMThoAkYPGO OKNcpZ1fd9T4r8MUsq1EQjMolGMTa4KK/SfI52ESdXW1oYXOleT9NeGG0wQJU7Qg ddAjazc5i1Fneukhp9P7n78XZK/ZoWjdjvInXCGJ+QqUow4lPRd9tIIhmyhXsiNB Un+a32WOKv7J18tIlVlDw2mUaBkPzKiUhZKo/R9qAfJ+bTFRGVxZ3HE00YB9OwRr d8k6SdQue63fgYyV9tcYpWSvN4odajwOF9mq91YhfxIAGYEgyIAqpVS1TSj1c7aH kHzKpuj5BDj71saBqG09yCKh9DqEJi0mujEMYuB9AaGkzT6mqmmNx31TlJ35arBe u9BYF+dax+H3r1RgcxQzj0wbHgF2RC+DS+mjHs260j/nxEbPruTEqtH6vUJLieeh 7LQ1+zkV8ugS7eiq4mrNnT2KAKmX3tRCyy8ZrWiC/P19EMPTbyDhBYwbmTnlKQKR ZsP/6ScViY/PUI4TR62MyeweMifZDRLITYUmNhuQSmdcDIqQutV3tHNzJlAzzUL+ BvYG9OD2P6tKlp9ZNIX9YMpg/sQJ4OSkqNNdKPsNDgJ/LOP9E6DBWEwwgv9jtCUa rBvhWr2UkfoJXM2TgIpp =Us2H -----END PGP SIGNATURE----- --qXQtVv2HgJlCiKIMBw8m0RcEn7PIUptLn--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a791313f-63eb-9358-4874-402a92ccfef1>