I had this a while ago. Copied the missing file from another system. Didn’t find the root cause.
Freebsd-update could be improved on resilience for inconsistent systems I 
assume.

Regards,
Ronald.

Van: void <v...@f-m.fm>
Datum: 24 december 2024 01:41
Aan: freebsd-sta...@freebsd.org
Onderwerp: freebsd-update errors 13.3-p11 => 13.4-p2



Hello,

On upgrading 13.3-p11 to 13.4-p2 (amd64) the following is displayed after the 
kernel parts finish installing, before the first reboot:

# /usr/sbin/freebsd-update install
src component not installed, skipped
Installing updates...ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or 
directory
ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or directory
ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or directory
ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or directory
ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or directory
ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or directory
ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or directory
ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or directory
ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or directory
ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or directory
ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or directory
ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or directory
ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or directory
ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or directory
ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or directory
ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or directory
ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or directory
ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or directory
ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or directory
ln: ///usr/share/man/man3/atf-sh-api.3.gz: No such file or directory

Restarting sshd after upgrade
(etc)

The upgrade proceeds normally other than this.
--




Reply via email to