From owner-freebsd-bugs@freebsd.org Mon Oct 9 15:03:09 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72180E32A85 for ; Mon, 9 Oct 2017 15:03:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F2C0072BC9 for ; Mon, 9 Oct 2017 15:03:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v99F38ch075366 for ; Mon, 9 Oct 2017 15:03:08 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 222880] freebsd-update should explain how to update ports after updating to a new release Date: Mon, 09 Oct 2017 15:03:08 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: allcoms@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Oct 2017 15:03:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222880 Bug ID: 222880 Summary: freebsd-update should explain how to update ports after updating to a new release Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: allcoms@gmail.com I have just finished upgrading my FreeBSD 11.0 to 11.1. This was the first = time I've ever upgraded from one FreeBSD release to another and thankfully it we= nt without any real problems apart from the fact that I had to search for documentation on how to update all of my installed ports because freebsd-up= date didn't tell me what I needed to do and neither did the official 11.1 upgrade instructions here: https://www.freebsd.org/releases/11.1R/installation.html#upgrade-binary Ideally, the user wouldn't need to search the web nor read any man pages (w= hich ones?) in order to fully update their system. After the second run of freebsd-update install it tells you to update third party software and remo= ve old libraries but without giving the user any hints beyond that. I could be more lucky than some in that I don't need any custom build optio= ns for any of the ports I use in FreeBSD so in my case it seems all I needed t= o do to fully update my system was to run: # pkg-static install -f pkg # pkg upgrade -f After the second run of `freebsd-update install`. In my case I didn't need = to run the first command as pkg was already up-to-date, but maybe this command should be recommended/run just in case? I think the updating of ports after upgrading to a new release should also = be covered in the Handbook for the sake of completeness: https://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html Maybe the process is a little more involved if users have customised port b= uild options? --=20 You are receiving this mail because: You are the assignee for the bug.=