From owner-freebsd-python@freebsd.org Sat Mar 7 04:35:33 2020 Return-Path: Delivered-To: freebsd-python@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D377C25B1AE for ; Sat, 7 Mar 2020 04:35:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 48ZBVs5GhPz4cqY for ; Sat, 7 Mar 2020 04:35:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id ADC4725B1AB; Sat, 7 Mar 2020 04:35:33 +0000 (UTC) Delivered-To: python@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AC55925B1AA for ; Sat, 7 Mar 2020 04:35:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48ZBVs3fwKz4cqV for ; Sat, 7 Mar 2020 04:35:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 748A83777 for ; Sat, 7 Mar 2020 04:35:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 0274ZXKw014370 for ; Sat, 7 Mar 2020 04:35:33 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 0274ZX6C014369 for python@FreeBSD.org; Sat, 7 Mar 2020 04:35:33 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: python@FreeBSD.org Subject: [Bug 237971] sysutils/py-salt: split port into -latest and -stable (2019.2 and 2018.3) Date: Sat, 07 Mar 2020 04:35:32 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: woodsb02@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-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-python@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Mar 2020 04:35:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237971 --- Comment #6 from Ben Woods --- Hi Christer, Now that phase 3 upstream support is now finished for 2018.3, can I ask what you would like to do with this bug? https://www.saltstack.com/product-support-lifecycle/ >From a user's point of view, its always nice if you can just keep doing "pkg upgrade", and not have to worry about versions. Am I correct in saying this patch would require the following manual steps from users to upgrade between versions? # pkg remove py37-salt20183 # pkg install py37-salt20192 Given salt masters and minions should generally be kept in sync, it might m= ake sense for salt to have separate packages in this case, and give the sysadmin fine-grained control over the salt versions being run (using the pkg comman= ds above). EXTRACT FROM UPSTREAM DOCUMENTATION - UPGRADE INSTRUCTIONS https://docs.saltstack.com/en/master/topics/installation/index.html#upgradi= ng-salt " Upgrading Salt When upgrading Salt, the master(s) should always be upgraded first. Backward compatibility for minions running newer versions of salt than their masters= is not guaranteed. Whenever possible, backward compatibility between new masters and old minio= ns will be preserved. Generally, the only exception to this policy is in case = of a security vulnerability. " --=20 You are receiving this mail because: You are on the CC list for the bug.=