Bug 182574
| Summary: | freebsd-update(8) can not update custom release with custom kernels | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | Anes Mukhametov <anes> | ||||
| Component: | bin | Assignee: | freebsd-bugs (Nobody) <bugs> | ||||
| Status: | Open --- | ||||||
| Severity: | Affects Only Me | CC: | cperciva, emaste | ||||
| Priority: | Normal | ||||||
| Version: | 9.2-STABLE | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| See Also: | https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=131598 | ||||||
| Attachments: |
|
||||||
Responsible Changed From-To: freebsd-bugs->cperciva Over to maintainer. batch change: For bugs that match the following - Status Is In progress AND - Untouched since 2018-01-01. AND - Affects Base System OR Documentation DO: Reset to open status. Note: I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed. Drop freebsd-update PRs which were assigned to me. I'm not working on this code any more. |
I use custom FreeBSD releases which include more than one custom kernel. In my case I can't update with freebsd-update, it fails with fetch_metadata_bogus. The reason is custom kernel path /boot/kernel.CUSTOMKERNEL is invalid for freebsd-update. Attached patch fixes this behaviour. How-To-Repeat: Build your own release with more than one kernel (GENERIC+XENHVM for example). Set up freebsd-update server and try to update.