Skip to content

New package: awsvpnclient-5.4.0 - #61700

Open
H4ndrycx wants to merge 1 commit into
void-linux:masterfrom
H4ndrycx:awsvpnclient
Open

New package: awsvpnclient-5.4.0#61700
H4ndrycx wants to merge 1 commit into
void-linux:masterfrom
H4ndrycx:awsvpnclient

Conversation

@H4ndrycx

Copy link
Copy Markdown
Contributor

Testing the changes

  • I tested the changes in this PR: YES

New package

Local build testing

  • I built this PR locally for my native architecture, (x86_64-glibc)
  • Installed the package, started the runit service, launched the GUI, and connected a VPN (DNS via the resolvectl shim)

AWS VPN Client from the upstream GTK .deb (nonfree, restricted=yes).

Notes from getting it running on Void (void-base, x86_64, glibc 2.41, kernel 6.18):

Upstream only publishes awsvpnclient_amd64.deb, so this is x86_64 only. Cross builds don't apply.

The .deb expects systemd. Void uses runit, so files/awsvpnclient/run starts ACVC.GTK.Service. The GUI does not connect without that daemon.

configure-dns calls resolvectl (systemd-resolved), which Void does not have. Patching that script failed with OvpnResourcesChecksumValidationFailed. The shim lives in /usr/libexec/awsvpnclient, and the run script prepends that dir to PATH so the lookup works without touching the checksummed file. libexec keeps it out of /usr/bin.

The .desktop Exec line ships as AWS\sVPN\sClient, which breaks on Void. patches/awsvpnclient.desktop.patch fixes the path.

Connect hit UnableToEnforceFipsException until fipsmodule.cnf was generated with the bundled musl OpenSSL/fips.so. The INSTALL hook does that after install.

@tranzystorekk tranzystorekk added the new-package This PR adds a new package label Jul 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new-package This PR adds a new package

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants