Arch Linux User Repository

Thank you for updating the package.

Yes master/minion connection errors are only related to 3007.5 and older. With newer versions it is fixed and compatibility is back again.

Thanks @cooldiver2 for the patch. Updated the package to use github sources for 3007.6. FYI Upgrade path from 3007.5 was smooth for me, no master/minion compatibility issues.

Packages from broadcom and github are the same. Cehcked via sah256sum. So I moved to github sources only. One place to get all the stuff for building.

Also updated to new version 3007.6.

From 82bf027419cb4774ca7378d3fc618e02d6a44b72 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Sven=20Rue=C3=9F?= <github@sven-ruess.de>
Date: Sat, 12 Jul 2025 08:47:16 +0200
Subject: [PATCH] Updated to version 3007.6 - Use only github for sources
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: Sven Rueß <github@sven-ruess.de>
---
 PKGBUILD | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/PKGBUILD b/PKGBUILD
index 996f93d..cab351d 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -13,7 +13,7 @@

 pkgname=salt-onedir
 provides=('salt')
-pkgver=3007.5
+pkgver=3007.6
 pkgrel=1
 pkgdesc="Central system and configuration manager (onedir installation +[${SALT_ADDITIONAL_PIP_PACKAGES}])"
 arch=('x86_64' 'aarch64')
@@ -28,17 +28,19 @@ backup=('etc/logrotate.d/salt'
         'etc/salt/master'
         'etc/salt/minion')

-source_x86_64=("https://packages.broadcom.com/artifactory/saltproject-generic/onedir/${pkgver}/salt-${pkgver}-onedir-linux-x86_64.tar.xz")
-sha256sums_x86_64=('d20759d2970ec8daeff7c9a5866cf874a08fdd65190f7c9b26d8e942204f7e8a')
+#source_x86_64=("https://packages.broadcom.com/artifactory/saltproject-generic/onedir/${pkgver}/salt-${pkgver}-onedir-linux-x86_64.tar.xz")
+source_x86_64=("https://github.com/saltstack/salt/releases/download/v${pkgver}/salt-${pkgver}-onedir-linux-x86_64.tar.xz")
+sha256sums_x86_64=('5d65442973b3db93b882dabb20d8c379950c68bd67c0aec5db8072d63eeaf5c7')

-source_aarch64=("https://packages.broadcom.com/artifactory/saltproject-generic/onedir/${pkgver}/salt-${pkgver}-onedir-linux-arm64.tar.xz")
-sha256sums_aarch64=('6bafdfbee798d160a2ef71a32f425082f3a6690b5e59a9dcdc922fb0de05a01e')
+#source_aarch64=("https://packages.broadcom.com/artifactory/saltproject-generic/onedir/${pkgver}/salt-${pkgver}-onedir-linux-arm64.tar.xz")
+source_aarch64=("https://github.com/saltstack/salt/releases/download/v${pkgver}/salt-${pkgver}-onedir-linux-arm64.tar.xz")
+sha256sums_aarch64=('61b3da8f7c49b55ff5ef0d02c7406fdad7af1644aa39bf7f626ad5a4297991fc')

 # The source tarball is downloaded because we need various files from pkg/common that are not included in the onedir tarball
 source=("https://github.com/saltstack/salt/releases/download/v${pkgver}/salt-${pkgver}.tar.gz"
         salt.logrotate
         0000-services.patch)
-sha256sums=('7f572e039059f1a597ba10a9bdc81dcc2375a49c49106581988f506039b3dda5'
+sha256sums=('176a8b97c43c50ed87df12279b3dd248bbb6ab48cd32b2de90f45234c7c4d094'
             'abecc3c1be124c4afffaaeb3ba32b60dfee8ba6dc32189edfa2ad154ecb7a215'
             '6eb7d8840c40da7070167d3c742e7337c45f80d639fb7ef72f196fcaa2843469')

-- 
2.50.1

Best regards Sven

Hell yeah. Thank you very much, I'll try it tonight.

@ipaqmaster Good news, turns out makepkg perfectly supports this situation! I added back aarch64 support with explicit per-arch sources. I cannot test the aarch64 build as I have no such environment currently available to me, so please let me know if it works as intended now :)

@ipaqmaster Apologies, yes this was an oversight from switching to the prebuilt version... With the manual build, it automatically built for whatever arch you were on.

Unfortunately, I currently don't think there's a good way to make this package build for the right arch automatically. I think the best option will be a dedicated salt-onedir-arm64 package that picks the arm64 prebuilt from broadcom. Let me look into this.

EDIT: FYI I removed aarch64 from this one now.

I built this in an aarch64 environment and it seems to have resulted in a package that has x86_64 binaries inside. This package claims to support aarch64 and qemu-aarch64-static was used for an aarch64 environment. The build took a lot longer than x86_64. But somehow I have a package file with x86_64 python binaries inside.

I think the ${source} variable explicitly grabs an x86_64 build of salt-onedir.

For humans, how want to build it by themselves:

From 0ab8630ef0a7321679aada17eb9243d34af67e2d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Sven=20Rue=C3=9F?= <github@sven-ruess.de>
Date: Wed, 9 Jul 2025 08:09:22 +0200
Subject: [PATCH] Updated to 3007.5 - Fix dependency issue - Fix bash
 completion - Updated relenv to 0.19.3 - Updated python to 3.10.17
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: Sven Rueß <github@sven-ruess.de>
---
 PKGBUILD | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/PKGBUILD b/PKGBUILD
index 3f0afd2..6698625 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -25,8 +25,8 @@

 pkgname=salt-onedir
 provides=('salt')
-pkgver=3007.1
-pkgrel=5
+pkgver=3007.5
+pkgrel=1
 pkgdesc="Central system and configuration manager (onedir installation +[${SALT_ADDITIONAL_PIP_PACKAGES}])"
 arch=('x86_64' 'aarch64')
 url='http://saltstack.org/'
@@ -42,7 +42,7 @@ backup=('etc/logrotate.d/salt'
 source=("https://github.com/saltstack/salt/releases/download/v${pkgver}/salt-${pkgver}.tar.gz"
         salt.logrotate
         0000-services.patch)
-sha256sums=('b933ac4cb3e4b1118b46dada55c9cc6bdc6f0f94b4c92877aec44b25c6a28c9a'
+sha256sums=('7f572e039059f1a597ba10a9bdc81dcc2375a49c49106581988f506039b3dda5'
             'abecc3c1be124c4afffaaeb3ba32b60dfee8ba6dc32189edfa2ad154ecb7a215'
             '7619465e571469e5a08cd507d3d49e0e003256d79a1ada61971edecad0149ea8')

@@ -66,10 +66,10 @@ build() {
   # not included in the package!
   virtualenv -p python3 "${venvdir}"
   source "${venvdir}"/bin/activate
-  pip install relenv==0.18.0
+  pip install relenv==0.19.3
   # fetch the relenv distribution
   # this unfortunately writes to ${HOME}/.local/relenv/build
-  relenv fetch --python=3.10.15
+  relenv fetch --python=3.10.17
   # create the relenv environment into which we will install Salt
   relenv create "${onedir}"
   deactivate
@@ -85,7 +85,7 @@ build() {
     USE_STATIC_REQUIREMENTS=1
   fi
   USE_STATIC_REQUIREMENTS=${USE_STATIC_REQUIREMENTS} \
-    "${onedir}"/bin/pip3 install "${srcdir}/salt-${pkgver}"
+    "${onedir}"/bin/pip3 install -r "${srcdir}/salt-${pkgver}/requirements/base.txt" "${srcdir}/salt-${pkgver}"

   # Add additional python deps for Salt
   if [[ -n ${SALT_ADDITIONAL_PIP_PACKAGES} ]]; then
@@ -130,7 +130,7 @@ package() {
   done

   # completions
-  install -v -Dm644 pkg/common/salt.bash "$pkgdir/usr/share/bash-completion/completions/salt"
+  install -v -Dm644 pkg/rpm/salt.bash "$pkgdir/usr/share/bash-completion/completions/salt"
   install -v -Dm644 pkg/common/salt.zsh "$pkgdir/usr/share/zsh/site-functions/_salt"
   install -v -Dm644 -t "$pkgdir/usr/share/fish/vendor_completions.d" pkg/common/fish-completions/*
 }
-- 
2.50.1

Issue with dependency from salt is fixed and will used latest versions of relenv and python.

Best regards Sven

Updated to salt 3007.5. I finally switched to using the prebuilt onedir tarball as per @wzyboy suggestion from months ago. Unfortunately, the manual relenv build process was very fragile, and I had too many issues getting it to work for 3007.5. I believe that using the upstream tarball is in any case the most sensible solution.

The SALT_ADDITIONAL_PIP_PACKAGES env var is still supported by the PKGBUILD.

Note that the location of the salt executables moved from /opt/salt/bin to /opt/salt. The upstream tarball is built that way, and I decided not to manually retain the previous layout.

Hi, @sven thanks for the patch. I had been on vacation and will push the update very soon. Sorry for the delay.