So I have this old i386 machine running NetBSD-9 on bare metal and I
decided to boot it up and try upgrading it with sysupgrade.

I did a "pkgin in sysupgrade", and then I noticed while fixing the
CACHEDIR setting to point to a place with space that sysupgrade would by
default try to upgrade to the latest netbsd-9 so I though I would try
that first:

# sysupgrade auto
sysupgrade: I: Starting auto-update with stages: fetch modules kernel sets 
etcupdate postinstall clean
sysupgrade: I: Downloading 
https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/i386/binary/sets/base.tgz
 into /usr/pkg/var/cache/sysupgrade
Trying [2a04:4e42:8b::262]:443 ...
ftp: Can't connect to `2a04:4e42:8b::262:443': No route to host
Trying 146.75.109.6:443 ...
Requesting 
https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/i386/binary/sets/base.tgz
Redirected to /pub/NetBSD-daily/netbsd-9/202408050500Z/i386/binary/sets/base.tgz
ftp: Can't lookup 
`/pub/NetBSD-daily/netbsd-9/202408050500Z/i386/binary/sets/base.tgz:ftp': No 
address associated with hostname
ftp: Can't connect or login to host 
`/pub/NetBSD-daily/netbsd-9/202408050500Z/i386/binary/sets/base.tgz:?'
sysupgrade: E: Failed to fetch 
https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/i386/binary/sets/base.tgz


Links (-gui) can follow the redirect, and presumably other web browsers
can as well, but ftp(1) (at least on netbsd-9) seems to fail.

So, is this an ftp(1) bug (or missing feature), or are the redirects on
nycdn.netbsd.org somehow broken?

Changing the RELEASEDIR to use an explicit ftp:// URL (i.e. with the
hostname chaged to nyftp.netbsd.org) works, but shouldn't the default
https:// URLs in the default sysupgrade.conf work too?  Especially since
sysupgrade doesn't also fetch the signature files and verify the
downloads (not that it would do much good unless there's a more secure
way to fetch the signatures!).

--
                                        Greg A. Woods <gwo...@acm.org>

Kelowna, BC     +1 250 762-7675           RoboHack <wo...@robohack.ca>
Planix, Inc. <wo...@planix.com>     Avoncote Farms <wo...@avoncote.ca>

Attachment: pgphDXj0tgeIK.pgp
Description: OpenPGP Digital Signature

Reply via email to