any problem going from 9.x (don't laugh) to 11 directly?

[Doug Hardie]

I can't find the original email, but here is what I did find via google:

10.0-RELEASE is no longer supported, which means you didn't get the important FreeBSD-EN-16:09.freebsd-update errata fix for freebsd-update.
You'll have to patch freebsd-update manually. Open up /usr/sbin/freebsd-update, and in the function fetch_metadata_sanity(), you'll see this:
# Check that the first four fields make sense.
    if gunzip -c < files/$1.gz |
        grep -qvE "^[a-z]+\|[0-9a-z]+\|${P}+\|[fdL-]\|"; then
            fetch_metadata_bogus ""
            return 1
    fi

Add a hyphen at the end of [0-9a-z] like so:
        grep -qvE "^[a-z]+\|[0-9a-z-]+\|${P}+\|[fdL-]\|"; then

Save, and now it should work.
	• permalink
	• embed
	• save
	• parent

[–]ddp 2 points 1 year ago 
Unfortunately that didn't resolve it; same failure.
    # Check that the first four fields make sense.                                              
    if gunzip -c < files/$1.gz |
        grep -qvE "^[a-z]+\|[0-9a-z-]+\|${P}+\|[fdL-]\|"; then
            fetch_metadata_bogus ""
            return 1
    fi

	• permalink
	• embed
	• save
	• parent

[–]DaemonWithin 2 points 1 year ago* 
It's definitely failing within fetch_metadata_sanity() somewhere. 
Does /var/db/freebsd-update/sanitycheck.tmp exist when freebsd-update exits? If so, post its contents. If not, then it's failing at the point you quoted. (Incidentally, bspatch isn't executed yet, so the problem isn't connected to your truncating bspatch.)
Also, post your /usr/sbin/freebsd-update to pastebin or something. I'll compare it with my later version.
	• permalink
	• embed
	• save
	• parent

[–]ddp 2 points 1 year ago* 
I don't have a sanitycheck.tmp there.
http://pastebin.com/A1MGqr3L
	• permalink
	• embed
	• save
	• parent

[–]DaemonWithin 4 points 1 year ago* 
I think I've found the problem.
In the same function, fetch_metadata_sanity(), add a comma to this:
P="[-+./:=%@_[~[:alnum:]]"

like so:
P="[-+./:=,%@_[~[:alnum:]]"

The comma doesn't exist before 10.2, explaining why some people are having luck upgrading to 10.3 first. If that's what the problem is, then I'd say an errata needs to be released for the still-supported 10.1 and 9.3.



There are two patches there.  The second may be all that you need.  I just don't recall if I used the first one also.  There is a Bug report:  Bug 211398 that has the original patch that I used.  Note, that the line numbers were not exactly the same for any of my systems.  

-- Doug