Date: Mon, 22 Aug 2016 01:01:52 +0200 From: Rainer Duffner <rainer@ultra-secure.de> To: Doug Hardie <doug@mail.sermon-archive.info> Cc: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: FreeBSD 10.1 can't upgrade to FreeBSD 11-RC1 via freebsd-update Message-ID: <B5747320-4FB3-4F20-84D4-AEED6AD491A9@ultra-secure.de> In-Reply-To: <6EB5F84D-E392-4742-BB4D-5A78393F4A24@mail.sermon-archive.info> References: <504FE992-890D-4335-BFD5-5F538FBC6459@ultra-secure.de> <6EB5F84D-E392-4742-BB4D-5A78393F4A24@mail.sermon-archive.info>
next in thread | previous in thread | raw e-mail | index | archive | help
> Am 20.08.2016 um 22:34 schrieb Doug Hardie <doug@mail.sermon-archive.info>:
>
>
>> On 20 August 2016, at 11:50, Rainer Duffner <rainer@ultra-secure.de> wrote:
>>
>> FreeBSD 10.3 works.
>>
>> FreeBSD 10.1 complains about a failed integrity check etc (which the EN was supposed to fix, I assume)
>>
>>
>> I did run freebsd-update to update to the latest patch-level and freebsd-version said, I was on p37.
>
> I encountered the same issue with 9.x. The following patch was sent to me:
>
> --- Comment #5 from Xin LI <delphij@FreeBSD.org> ---
> (In reply to bc979 from comment #4)
>
> Can you try applying this? (r279901)
>
> Index: head/usr.sbin/freebsd-update/freebsd-update.sh
> ===================================================================
> --- head/usr.sbin/freebsd-update/freebsd-update.sh (revision 279900)
> +++ head/usr.sbin/freebsd-update/freebsd-update.sh (revision 279901)
> @@ -1231,7 +1231,7 @@ fetch_metadata_sanity () {
> # Some aliases to save space later: ${P} is a character which can
> # appear in a path; ${M} is the four numeric metadata fields; and
> # ${H} is a sha256 hash.
> - P="[-+./:=%@_[~[:alnum:]]"
> + P="[-+./:=,%@_[~[:alnum:]]"
> M="[0-9]+\|[0-9]+\|[0-9]+\|[0-9]+"
> H="[0-9a-f]{64}"
>
> --
>
> However, it doesn't actually go in 9.x. The line numbers are very close. Use the comment to find the proper line. For me it was less than 10 lines before 1231. I don't keep the source so I just updated /usr/sbin/freebsd-update directly. The patch worked.
>
It seems to work, yes.
I think this should be fixed before 11.0-RELEASE becomes available.
Rainer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B5747320-4FB3-4F20-84D4-AEED6AD491A9>