Package Details: globalprotect-openconnect-git 2.4.0.r1.g0c9b8e6-1

Git Clone URL: https://aur.archlinux.org/globalprotect-openconnect-git.git (read-only, click to copy)
Package Base: globalprotect-openconnect-git
Description: A GUI for GlobalProtect VPN, based on OpenConnect, supports the SSO authentication method.
Upstream URL: https://github.com/yuezk/GlobalProtect-openconnect
Keywords: globalprotect openconnect saml vpn
Licenses: GPL3
Conflicts: globalprotect-openconnect
Provides: globalprotect-openconnect, gpauth, gpclient, gpgui, gpservice
Submitter: yuezk
Maintainer: yuezk
Last Packager: yuezk
Votes: 6
Popularity: 0.46
First Submitted: 2021-10-16 07:43 (UTC)
Last Updated: 2024-12-27 14:44 (UTC)

Latest Comments

1 2 3 4 Next › Last »

yuezk commented on 2024-12-27 15:00 (UTC)

@MarsSeed I’ve updated it to use the main branch.

That said, I understand that using a git tag may not align with the -git suffix, as tags are immutable once released. However, why must it be restricted to the main branch? What if the main branch serves as the release branch in my workflow?

In the end, isn’t this just a matter of branch naming? Functionally, there shouldn't be any difference when using the branch.

MarsSeed commented on 2024-12-27 14:41 (UTC)

@yuezk, this package is only valid for what its pkgname represents if you build it from the 'main' branch, but not when you use a stable release branch or a git tag as source.

Muflone commented on 2024-12-08 13:01 (UTC)

@MarsSeed thanks for pointing this, I missed the package from extra repository

the issue is now solved, as it sources from the git repo

Muflone commented on 2024-12-08 12:59 (UTC)

ok, now it seems fine (I've not tested it), therefore I'm canceling the pending deletion request

thanks yuezk for your prompt collaboration

MarsSeed commented on 2024-12-08 12:58 (UTC)

@Muflone, a stable globalprotect-openconnect build already exists in [extra] repo (albeit atm still on upstream's v1.4.9 from last year rather than on the current latest v2.x).

yuezk commented on 2024-12-08 12:52 (UTC)

@Muflone I prefer to use the —git package, so I changed the source to use the code from the main branch.

Muflone commented on 2024-12-08 11:09 (UTC)

@yuezk well done

now the issue is the package name:

this is called globalprotect-openconnect-git to indicate it will install the latest commit from the git repository, not a specific version.

this package instead uses a fixed version (2.3.9).

so please rename this package to globalprotect-openconnect (with no -git) to continue to use the fixed version like this package.

To accomplish this, simply recreate the package as globalprotect-openconnect and later file a merge request from globalprotect-openconnect-git to globalprotect-openconnect

yuezk commented on 2024-12-08 05:21 (UTC) (edited on 2024-12-08 06:22 (UTC) by yuezk)

@Muflone I have updated PKGBUILD to build the package from the source code.

Muflone commented on 2024-12-07 23:35 (UTC)

@yuezk this package name ends with -git to indicate this is a VCS package while it's not. Please switch to build from the git sources, using the main branch, or this package is a duplicate of globalprotect-openconnect

yuezk commented on 2024-11-02 10:41 (UTC)

@disastro This package downloads the pre-built binaries from the GitHub release because building it from the source is time-consuming.

If you like to build it from the source code, follow the instructions on GitHub.

1 2 3 4 Next › Last »