From owner-freebsd-bugs@freebsd.org Sat Mar 24 14:26:30 2018 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 240FDF4E422 for ; Sat, 24 Mar 2018 14:26:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AD5826ED59 for ; Sat, 24 Mar 2018 14:26:29 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id F29D924781 for ; Sat, 24 Mar 2018 14:26:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w2OEQSO9022747 for ; Sat, 24 Mar 2018 14:26:28 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2OEQSQq022746 for freebsd-bugs@FreeBSD.org; Sat, 24 Mar 2018 14:26:28 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 226893] freebsd-update supporting explicit patch-level for fetch+upgrade Date: Sat, 24 Mar 2018 14:26:29 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed 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 Many People X-Bugzilla-Who: 482254ac@razorfever.net 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: Message-ID: In-Reply-To: References: 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.25 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 14:26:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226893 --- Comment #1 from Derek <482254ac@razorfever.net> --- It was expressed that "it would be nice if" we could list the available pat= ch levels, for example, and by extension if we can specify that patch level by number, instead of existing tag hash. 1. Without updates to the freebsd-update server portion, the only way that I can see this being feasible is to download all the available tags for a release, and then pull down their manifests and see if there's a file that = can be downloaded (e.g. whatever freebsd-version is sourcing), and parsed. I f= eel like this is needlessly onerous. 2. A different method, would be in addition to latest.ssl, we also support all.ssl, which is the concatenation of all of the latest.ssl released for a particular release/architecture. This will require changes to the freebsd-update server portion, and will need support added retroactively for previous supported releases. It would be trivial to modify to the freebsd-update client to support this file instead (or in addition to). 3. A third, most hacky, option is just to specify the tag hash on the comma= nd line, and put the onus on the user to research the tag they wish to install. There's likely other approaches, but I'm partial to #2. --=20 You are receiving this mail because: You are the assignee for the bug.=