Re: sysupgrade on aarch64

[Steve Rikli <sr%genyosha.net@localhost>]

On Tue, Nov 03, 2026 at 11:14:02AM -0800, Joel P. wrote:
> I just tried to use sysupgrade on my RPi3 (aarch64) with 11.0 and noticed
> RELEASEDIR also needs to be updated:
> 
>   RELEASEDIR="https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-$(uname -r |
> cut -d. -f1)/latest/$(uname -m)"
> 
> uname -m won't give "evbarm-aarch64" which is what I now see at:
>     https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-11/latest
> 
> This worked for me in sysupgrade.conf:
> 
> RELEASEDIR="https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-11/latest/evbarm-aarch64";

I did a similar thing for my rpi4:

  RELEASEDIR="https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-$(uname -r | cut -d. -f1)/latest/$(uname -m)-$(uname -p)"

I thought about trying to work on that problem as well in PR 59686 but
decided to just start with the sets filename compression suffix
mis-matches and see if it went anywhere.

Iirc sysupgrade.conf is basically sourced by sysupgrade, so
automatically making per-architecture adjustments like this to
RELEASEDIR after the initial setting might need to happen in the
sysupgrade script itself.

Fwiw I'm not sure if sysupgrade is still maintained; the Handbook
references it in examples and I've been using it successfully for a
while, so it seems useful.

Cheers,
sr.