Search Criteria
Package Details: amneziawg-linux 1.0.20241112-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/amneziawg-linux.git (read-only, click to copy) |
---|---|
Package Base: | amneziawg-linux |
Description: | AmneziaWG is a contemporary version of the popular VPN protocol, WireGuard. |
Upstream URL: | https://github.com/amnezia-vpn/amneziawg-linux-kernel-module |
Licenses: | GPLv2 |
Provides: | AMNEZIAWG-MODULE |
Submitter: | VVL |
Maintainer: | VVL |
Last Packager: | VVL |
Votes: | 5 |
Popularity: | 0.54 |
First Submitted: | 2024-09-30 22:01 (UTC) |
Last Updated: | 2024-12-09 10:57 (UTC) |
Latest Comments
1 2 Next › Last »
distrayer commented on 2025-02-11 16:28 (UTC)
If after updating amneziawg-linux awg-quick doesn't use this kernel module, you need to rebuild amneziawg-tools and amneziawg-go (idk which of them explicitly causes this problem)
VVL commented on 2024-12-09 10:57 (UTC)
I've removed hard depend on version of linux package. You may try to build it now.
AlexWayfer commented on 2024-12-08 12:50 (UTC)
VVL commented on 2024-11-20 13:07 (UTC)
I double-checked everything and was able to reproduce the error. For some unknown reason, all package managers working with AUR determine the dependencies of the pkg{} block before building, and not during packaging, as intended in this PKGBUILD. This causes some inconvenience - a hard link to the linux version is needed for correct updating of the kernel in the future - you will also need to update the amneziawg-linux package, otherwise the kernel will be updated and the module will stop working. I don't know how to solve this problem yet, I will try different options.
VVS commented on 2024-11-19 13:23 (UTC)
No packages amneziawg-linux, linux-headers, linux in cache.
VVL commented on 2024-11-18 19:05 (UTC)
Can you clear your yay cache (build directory)?
VVS commented on 2024-11-18 18:23 (UTC)
@VVL, same issue:
VVL commented on 2024-11-18 07:34 (UTC)
I've added another logic of dependencies in PKGBUILD - please check it working correctly.
VVS commented on 2024-11-14 20:13 (UTC)
itsTomHarper +1 Same error. Bur I'm use 6.6.54...
1 2 Next › Last »