Bug 182574 - freebsd-update(8) can not update custom release with custom kernels
Summary: freebsd-update(8) can not update custom release with custom kernels
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 9.2-STABLE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-02 15:00 UTC by Anes Mukhametov
Modified: 2023-03-03 00:08 UTC (History)
2 users (show)

See Also:


Attachments
freebsd-update.sh.diff (514 bytes, patch)
2013-10-02 15:00 UTC, Anes Mukhametov
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Anes Mukhametov 2013-10-02 15:00:00 UTC
        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.
Comment 1 Glen Barber freebsd_committer freebsd_triage 2013-10-02 15:03:08 UTC
Responsible Changed
From-To: freebsd-bugs->cperciva

Over to maintainer.
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:45:08 UTC
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.
Comment 3 Colin Percival freebsd_committer freebsd_triage 2019-03-12 22:59:54 UTC
Drop freebsd-update PRs which were assigned to me.  I'm not working on this code any more.