| Git Clone URL: | https://aur.archlinux.org/cisco-anyconnect.git (read-only, click to copy) |
|---|---|
| Package Base: | cisco-anyconnect |
| Description: | Cisco AnyConnect Secure Mobility Client |
| Upstream URL: | https://www.cisco.com/c/en/us/products/security/anyconnect-secure-mobility-client/index.html |
| Keywords: | anyconnect cisco vpn |
| Licenses: | custom |
| Submitter: | K900 |
| Maintainer: | Posi |
| Last Packager: | Posi |
| Votes: | 18 |
| Popularity: | 0.055420 |
| First Submitted: | 2019-03-28 09:19 (UTC) |
| Last Updated: | 2023-10-29 07:58 (UTC) |
The file:// thing is an unfortunate side effect of how AUR parses packages - I don't think there's a way to refer to a file that does not exist in the package source just by name.
@indianahorst: you need to obtain the file yourself and put it in the same directory as the PKGBUILD. Cisco doesn't provide direct download links.
@Xihu0208: what "app" are you opening exactly? vpnui? Is vpnagentd running?
Don't forget to call systemctl enable --now vpnagentd after build.
I already changed "file://${_filename}" to "${_filename}" in the PKGBUILD, but I still get this:
==> Retrieving sources... ==> ERROR: anyconnect-linux64-4.8.02042-core-vpn-webdeploy-k9.sh was not found in the build directory and is not a URL. :: Unable to build cisco-anyconnect - makepkg exited with code: 1
I had the same issue as @notizblock when I've recently needed to use a tarball instead of the script (needed to remove file:// from the source array).
Finally got my hands on all kinds of installers for 4.8.01090, including the new .pkg redistributable format that you get directly from cisco.com. The PKGBUILD is updated now, and a third new install method is supported.
At least for the tarball version, I had to replace "file://${_filename}" with "${_filename}" in the source array. Otherwise the tarball is not extracted by makepkg.
Would it be worth splitting this out into two packages? One for the installer, one for the tarball? That would at least allow you to update the PKGBUILD for just the installer (based on what I linked previously).
I still haven't managed to get my hands on a known-clean download of 4.8, so the update will take a bit longer :(
For 4.8.01090 (installer, don't have access to tarball), apart from updating pkgver and _filehash, just need to rename the manifesttool binary in package() to manifesttool_vpn.
Pinned Comments
labaman commented on 2023-02-28 17:14 (UTC)
Unfortunately, I don't have access to a version newer than 4.10.06079 yet. If there is someone who can help with the update package - please let me know - I'll add to the co-maintainers.
K900 commented on 2019-04-03 13:02 (UTC)
As the comment in the PKGBUILD says (you've read it, right? ;) ), Cisco does not provide public downloads for this, so you have to obtain the installer yourself either through your own Cisco account or through your company's.