1. Forum
  2. USENET
  3. muc.lists.freebsd.stable

  • [Bug 289769] libsys.so.7 not found when upgrading userland with legacy freebsd-update

    From bugzilla-noreply@bugzilla-noreply@freebsd.org to muc.lists.freebsd.stable on Sat Oct 18 22:44:28 2025
    From Newsgroup: muc.lists.freebsd.stable

    https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289769
    Craig Leres <leres@freebsd.org> changed:
    What |Removed |Added ----------------------------------------------------------------------------
    CC| |leres@freebsd.org
    --- Comment #16 from Craig Leres <leres@freebsd.org> ---
    I tried to go from 13.5 to 15.0-BETA2 and hit this. I don't see a recipe on how to recover so here's mine:
    # (I use csh)
    set path= ( /rescue $path )
    cd /tmp
    fetch https://download.freebsd.org/releases/amd64/15.0-BETA2/base.txz
    tar zxf ../base.txz lib/libsys.so.7
    mv -i lib/libsys.so.7 /lib
    freebsd-update install
    I *think* my problem was that the 13.5 version freebsd-update is missing the fix from this PR?
    --
    You are receiving this mail because:
    You are on the CC list for the bug.--
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From bugzilla-noreply@bugzilla-noreply@freebsd.org to muc.lists.freebsd.stable on Wed Dec 3 11:47:09 2025
    From Newsgroup: muc.lists.freebsd.stable

    https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289769
    ben@eskola.uk changed:
    What |Removed |Added ----------------------------------------------------------------------------
    CC| |ben@eskola.uk
    --- Comment #17 from ben@eskola.uk ---
    I seem to have also encountered this issue, upgrading from 14.3-RELEASE to 15.0-RELEASE, and fixed it following Craig Leres' instructions.
    --
    You are receiving this mail because:
    You are on the CC list for the bug.--
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From bugzilla-noreply@bugzilla-noreply@freebsd.org to muc.lists.freebsd.stable on Fri Dec 5 18:09:25 2025
    From Newsgroup: muc.lists.freebsd.stable

    https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289769
    Clay Ayers <thedaemon@thedaemons.space> changed:
    What |Removed |Added ----------------------------------------------------------------------------
    CC| |thedaemon@thedaemons.space
    --- Comment #18 from Clay Ayers <thedaemon@thedaemons.space> ---
    I can confirm I had the same issue on 14.3-RELEASE to 15.0-RELEASE on my server. Couldn't copy the files to /lib as I had no working su or sudo. Please advise.
    --
    You are receiving this mail because:
    You are on the CC list for the bug.--
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From bugzilla-noreply@bugzilla-noreply@freebsd.org to muc.lists.freebsd.stable on Sun Dec 7 14:12:58 2025
    From Newsgroup: muc.lists.freebsd.stable

    https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289769
    ykla <yklaxds@gmail.com> changed:
    What |Removed |Added ----------------------------------------------------------------------------
    CC| |yklaxds@gmail.com
    --- Comment #19 from ykla <yklaxds@gmail.com> ---
    This issue still occurs in the update from FreeBSD 14.3-RELEASE to 15.0.
    --
    You are receiving this mail because:
    You are on the CC list for the bug.--
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From bugzilla-noreply@bugzilla-noreply@freebsd.org to muc.lists.freebsd.stable on Wed Dec 10 08:22:46 2025
    From Newsgroup: muc.lists.freebsd.stable

    https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289769
    ivy@FreeBSD.org changed:
    What |Removed |Added ----------------------------------------------------------------------------
    CC| |ivy@FreeBSD.org
    --- Comment #20 from ivy@FreeBSD.org ---
    (In reply to ykla from comment #19)
    did you apply the freebsd-update errata (https://www.freebsd.org/security/advisories/FreeBSD-EN-25:18.freebsd-update.asc)
    before upgrading?
    --
    You are receiving this mail because:
    You are on the CC list for the bug.--
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From bugzilla-noreply@bugzilla-noreply@freebsd.org to muc.lists.freebsd.stable on Wed Dec 10 08:54:24 2025
    From Newsgroup: muc.lists.freebsd.stable

    https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289769
    Kurt Jaeger <pi@FreeBSD.org> changed:
    What |Removed |Added ----------------------------------------------------------------------------
    CC| |pi@FreeBSD.org
    --- Comment #21 from Kurt Jaeger <pi@FreeBSD.org> ---
    (In reply to Clay Ayers from comment #18)
    From my tests, the upgrade steps should be (from 14.3p6):
    freebsd-update -r 15.0-RELEASE upgrade
    freebsd-update install
    freebsd-update install
    shutdown -r now
    pkg update
    pkg upgrade
    freebsd-update install
    zpool upgrade ...
    Because 14.3p6 to 15.0, with only one install followed by a reboot leads to an unusable system, see above.
    --
    You are receiving this mail because:
    You are on the CC list for the bug.--
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2
  • From bugzilla-noreply@bugzilla-noreply@freebsd.org to muc.lists.freebsd.stable on Wed Dec 10 21:52:53 2025
    From Newsgroup: muc.lists.freebsd.stable

    https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289769
    --- Comment #22 from Graham Perrin <grahamperrin@gmail.com> ---
    This report is closed, please make a separate report for things such as documentation. Thank you.
    --
    You are receiving this mail because:
    You are on the CC list for the bug.--
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21a-Linux NewsLink 1.2