Search Criteria
Package Details: wstunnel 10.5.5-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/wstunnel.git (read-only, click to copy) |
|---|---|
| Package Base: | wstunnel |
| Description: | tunnel all your traffic over Websocket or HTTP2 |
| Upstream URL: | https://github.com/erebe/wstunnel |
| Licenses: | BSD-3-Clause |
| Conflicts: | haskell-wstunnel-bin, nodejs-wstunnel, wstunnel-bin |
| Provides: | wstunnel |
| Submitter: | alou-S |
| Maintainer: | shtrophic |
| Last Packager: | shtrophic |
| Votes: | 4 |
| Popularity: | 0.123386 |
| First Submitted: | 2024-02-07 11:13 (UTC) |
| Last Updated: | 2026-05-06 19:14 (UTC) |
Dependencies (4)
- gcc-libs (gcc-libs-gitAUR, gcc-libs-fast-optimizedAUR, gccrs-libs-gitAUR, gcc-libs-snapshotAUR)
- glibc (glibc-gitAUR, glibc-git-native-pgoAUR, glibc-eacAUR)
- git (git-gitAUR, git-glAUR, git-wd40AUR) (make)
- rust (rust-beta-binAUR, rustup-gitAUR, rust-gitAUR, rustup) (make)
Latest Comments
shtrophic commented on 2026-05-07 05:34 (UTC)
Works for me. You are free to skip check() with makepkg --nocheck.
gyscos commented on 2026-05-06 23:07 (UTC) (edited on 2026-05-07 00:00 (UTC) by gyscos)
Hi!
On the latest version (10.5.5-1) tests are failing:
It might depend on the environment since this does build on different systems.
It seems the check() step is a new addition?
gyscos commented on 2026-05-01 21:41 (UTC) (edited on 2026-05-02 01:12 (UTC) by gyscos)
Hi! I think the removal of the
!ltooption broke compilation for me:And plenty more such errors.
EDIT: Thanks for the quick fix! :)
gyscos commented on 2025-06-27 18:53 (UTC)
Hi! This package is still out of date. I understand it's easy to miss these notifications.
Any chance it could be updated? Thanks!
shtrophic commented on 2025-02-05 19:52 (UTC)
PKGBUILD needs to be updated with new hashes since the initial v10.1.9 was a pre-release and a new tarball is tagged as v10.1.9.
Erebe commented on 2024-08-18 10:19 (UTC)
You may want to update to v10.0.1 https://github.com/erebe/wstunnel/releases/tag/v10.0.1
v10.0.0 has been yanked due to a critical bug