Hi pinophyta,
So far I have had few colleagues report that it works. My best recommendation is to see if the 'appgatedriver.service' has been started properly. The appgate client and your user do not need to be able to manipulate TUN devices, it delegates to 'appgatedriver' which should be started by systemd.
Pinned Comments
garylinux666 commented on 2026-03-12 22:00 (UTC)
Quick guide for future maintainers (How to update this package)
Hi everyone! If I'm away and this package needs an update, here is a "for dummies" step-by-step guide to do it properly:
Clone the repo (if you haven't already): git clone ssh://aur@aur.archlinux.org/appgate-sdp.git
Update the PKGBUILD:
Change the pkgver variable to the new version (e.g., pkgver=6.5.5).
If the major/minor version changed (e.g., from 6.5 to 6.6), update the URL in the source array accordingly.
Update Checksums: Run updpkgsums.
This tool (part of pacman-contrib) reads the new URL in your PKGBUILD, downloads the file, calculates the new SHA256 hash, and automatically updates the sha256sums section in your PKGBUILD file. You don't need to copy-paste hashes manually.
Update Metadata: Run makepkg --printsrcinfo > .SRCINFO. IMPORTANT: AUR website reads this file, not the PKGBUILD. If you skip this, the website won't show the new version.
Test the build: Run makepkg -s to ensure the package compiles and the paths are still correct.
Commit and Push:
Bash git add PKGBUILD .SRCINFO git commit -m "Update to version X.Y.Z" git push origin master Note on services: Starting from version 6.5.x, the service name is appgatedriver.service. Always ensure the appgate-sdp.install file is included in the commit to notify users.