Bug 247504 - sysutils/py-salt: Provide ports for all currently supported versions
Summary: sysutils/py-salt: Provide ports for all currently supported versions
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Kirill Ponomarev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-23 16:56 UTC by James TD Smith
Modified: 2022-08-08 06:09 UTC (History)
4 users (show)

See Also:


Attachments
Port for Salt 3000.x (15.05 KB, text/plain)
2020-06-24 15:30 UTC, James TD Smith
no flags Details
Port for Salt 3000.5 (15.05 KB, text/plain)
2020-11-03 18:23 UTC, James TD Smith
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description James TD Smith 2020-06-23 16:56:22 UTC
When the Salt port was updated to the 3000 branch, a port for the 2019.2 branch was also added to allow users who wanted to continue using it to do so. This was not done for the update to 3001, and I would like to keep using the 3000 branch for now.

According to the support schedule at https://www.saltstack.com/product-support-lifecycle/, 2019.2 will still get patches until the 30th of September 2020 and 3000 will be supported until 30th August 2021. Can we have ports for all the currently supported branches, or at least the latest and previous major releases so users can choose when to upgrade?
Comment 1 James TD Smith 2020-06-24 15:30:11 UTC
Created attachment 215908 [details]
Port for Salt 3000.x

Created a port for Salt 3000.x based on the existing ones. I also added a patch to get it to use cryptodome instead of the unmaintained py-crypto.
Comment 2 ari 2020-06-29 05:26:32 UTC
Possibly a duplicate of https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237971
Comment 3 James TD Smith 2020-11-03 18:23:05 UTC
Created attachment 219327 [details]
Port for Salt 3000.5

Updated port for the 3000.5 security update
Comment 4 Daniel Engberg freebsd_committer freebsd_triage 2022-08-08 06:04:39 UTC
We're at 3004.2 now so I guess we can close this issue?
Comment 5 Kirill Ponomarev freebsd_committer freebsd_triage 2022-08-08 06:09:02 UTC
yes, thanks dizzy@ for a ping