Re: sysupgrade

[Julio Merino <julio%meroh.net@localhost>]

On Sun, May 21, 2017 at 7:39 PM, Johnny C. Lam <jlam%netbsd.org@localhost> wrote:
> On Sun, May 21, 2017 at 05:04:19PM -0500, Jason Bacon wrote:
>> Is sysutils/sysupgrade still supported?  It looks like the package hasn't
>> been upgraded in a few years, although it's recommended here:
>>
>>     https://www.netbsd.org/docs/guide/en/chap-upgrading.html
>
> Yes, it should still work.

Yup, it does work. I use it routinely.

>> Trying to run this:
>>
>>     sysupgrade auto 'ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-7.1/amd64'
>>
>> Ends in this:
>>
>>     sysupgrade: E: Failed to fetch ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-7.1/amd64/binary/kernel/netbsd-AUTOUPDATE.gz
>
> It looks like sysupgrade tried to automatically discover your kernel
> config name, and determined it to be "AUTOUPDATE".  Is that correct?
> You can run "config -x | head -1" to see.  You can explicitly set
> the kernel to use as part of the auto-update with:
>
>         sysupgrade -o KERNEL=GENERIC auto <releasedir>

I wonder what should sysupgrade do when it detects a custom kernel
that is not available in the given repository. Fail as it does now?
Ignore the kernel upgrade? Or maybe the user should be the one
explicitly saying "UPDATE_KERNEL=no" or something similar when they
have explicitly compiled their own kernel, because sysupgrade cannot
deal with this.

-- 
Julio Merino -- http://julio.meroh.net/