[Bug 195484] New: freebsd-update(8) fails to update 9.2-RELEASE to 10.1-RELEASE

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195484

            Bug ID: 195484
           Summary: freebsd-update(8) fails to update 9.2-RELEASE to
                    10.1-RELEASE
           Product: Base System
           Version: 9.2-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: fw at moov.de

I did the usual steps to upgrade a 9.2-RELEASE host to 10.1-RELEASE:

- freebsd-update upgrade -r 10.1-RELEASE
- freebsd-update install
- reboot
- freebsd-update install

Unfortunately it fails while trying to install the userland components:

    # freebsd-update install
    Installing updates…ln: ///usr/lib/private/libheimipcc.so: No such file or
directory
    install: ///usr/lib/private/libheimipcc.so.11: No such file or directory
    ln: ///usr/lib/private/libheimipcs.so: No such file or directory
    install: ///usr/lib/private/libheimipcs.so.11: No such file or directory
    ln: ///usr/lib/private/libldns.so: No such file or directory
    install: ///usr/lib/private/libldns.so.5: No such file or directory
    ln: ///usr/lib/private/libssh.so: No such file or directory
    install: ///usr/lib/private/libssh.so.5: No such file or directory
    ln: ///usr/lib/private/libucl.so: No such file or directory
    install: ///usr/lib/private/libucl.so.1: No such file or directory
    ln: ///usr/lib/private/libunbound.so: No such file or directory
    install: ///usr/lib/private/libunbound.so.5: No such file or directory
    ln: ///usr/lib/private/libyaml.so: No such file or directory
    install: ///usr/lib/private/libyaml.so.1: No such file or directory

freebsd-update(8) fails because it assumes that /usr/lib/private exists, while
it wasn't introduced until 9.3-RELEASE. As a result sshd(8) and pkg(8) will
stop working due to missing libraries.

This should be fixed to allow users to upgrade from 9.2-RELEASE to 10.x. The
EOL for 9.2 is set to 2014-12-31, so it's likely that an increasing number of
users will experience this issue.

As a sidenote freebsd-update(8) actually did exit with code 0, thus not
reporting an error. I would expect freebsd-update(8) to exit with non-zero exit
code if it fails to install a system library.

-- 
You are receiving this mail because:
You are the assignee for the bug.