Hello list,
After upgrading a OpenBSD host running 6.5 to 6.6 using sysupgrade(8), I
received the email below.
It suggests that the upgrade has been aborted upon failure to upgrade
comp66.tgz. This set was not part of the initial installation.
Does this mean that the system is ‘half upgraded’? What steps are missing
because of the abort?
Cheers,
Heinrich
> On 28. Oct 2019, at 16:31, Charlie Root <r...@vpn.rebehn.net> wrote:
>
> Choose your keyboard layout ('?' or 'L' for list) [default] default
> Available disks are: sd0.
> Which disk is the root disk? ('?' for details) [sd0] sd0
> Checking root filesystem (fsck -fp /dev/sd0a)... OK.
> Mounting root filesystem (mount -o ro /dev/sd0a /mnt)... OK.
> Force checking of clean non-root filesystems? [no] no
> /dev/sd0a (331a03408374f07d.a) on /mnt type ffs (rw, local, wxallowed)
>
> Let's upgrade the sets!
> Location of sets? (cd0 disk http nfs or 'done') [http] disk
> Is the disk partition already mounted? [yes] yes
> Pathname to the sets? (or 'done') [6.6/amd64] /home/_sysupgrade/
>
> Select sets by entering a set name, a file name pattern or 'all'. De-select
> sets by prepending a '-', e.g.: '-game*'. Selected sets are labelled '[X]'.
> [X] bsd [X] comp66.tgz [X] xbase66.tgz [X] xserv66.tgz
> [X] bsd.rd [X] man66.tgz [X] xshare66.tgz
> [X] base66.tgz [X] game66.tgz [X] xfont66.tgz
> Set name(s)? (or 'abort' or 'done') [done] done
> Directory does not contain SHA256.sig. Continue without verification? [no] yes
> Installing bsd 100% |**************************| 18250 KB 00:00
>
> Installing bsd.rd 100% |**************************| 10058 KB 00:00
>
> Installing base66.tgz 100% |**************************| 236 MB 00:12
>
> Installing comp66.tgz 78% |******************** | 56832 KB 00:01
> ETAtar: Unable to remove directory ./usr/include/machine: Directory not empty
> Installing comp66.tgz 100% |**************************| 72109 KB 00:06
>
> Installation of comp66.tgz failed. Continue anyway? [no] no
