Gentoo Packages

Search

Install

Install this package:

emerge -a net-vpn/globalprotect-openconnect

Package Information

Description:

GlobalProtect VPN GUI based on Openconnect with SAML auth mode support

Homepage:

https://github.com/yuezk/GlobalProtect-openconnect

License:

GPL-3

Versions

Metadata

No metadata available.

Lint Warnings

• Ebuild 2.3.9 has a missing or malformed copyright/licensing header.
• Ebuild 2.3.9 has a missing or malformed copyright/licensing header.
• Ebuild 2.3.7 has a missing or malformed copyright/licensing header.
• Ebuild 2.3.4 has a missing or malformed copyright/licensing header.
• Ebuild 2.3.2 has a missing or malformed copyright/licensing header.
• Ebuild 2.3.1 has a missing or malformed copyright/licensing header.
• [Notice] Ebuild 2.3.9 has an invalid header. It should start with a valid copyright line (e.g., '# Copyright YEARS MAIN-CONTRIBUTOR') and the GPLv2 distribution text followed by an empty line.
• [Notice] Ebuild 2.3.9 has an invalid header. It should start with a valid copyright line (e.g., '# Copyright YEARS MAIN-CONTRIBUTOR') and the GPLv2 distribution text followed by an empty line.
• [Notice] Ebuild 2.3.7 has an invalid header. It should start with a valid copyright line (e.g., '# Copyright YEARS MAIN-CONTRIBUTOR') and the GPLv2 distribution text followed by an empty line.
• [Notice] Ebuild 2.3.4 has an invalid header. It should start with a valid copyright line (e.g., '# Copyright YEARS MAIN-CONTRIBUTOR') and the GPLv2 distribution text followed by an empty line.
• [Notice] Ebuild 2.3.2 has an invalid header. It should start with a valid copyright line (e.g., '# Copyright YEARS MAIN-CONTRIBUTOR') and the GPLv2 distribution text followed by an empty line.
• [Notice] Ebuild 2.3.1 has an invalid header. It should start with a valid copyright line (e.g., '# Copyright YEARS MAIN-CONTRIBUTOR') and the GPLv2 distribution text followed by an empty line.
• [Warning] Ebuild 2.3.9 has a line exceeding 80 positions on line 14.
• [Warning] Ebuild 2.3.9 has a line exceeding 80 positions on line 16.
• [Warning] Ebuild 2.3.9 has a line exceeding 80 positions on line 11.
• [Warning] Ebuild 2.3.9 has a line exceeding 80 positions on line 13.
• [Warning] Ebuild 2.3.7 has a line exceeding 80 positions on line 11.
• [Warning] Ebuild 2.3.7 has a line exceeding 80 positions on line 13.
• [Warning] Ebuild 2.3.4 has a line exceeding 80 positions on line 11.
• [Warning] Ebuild 2.3.4 has a line exceeding 80 positions on line 13.
• [Warning] Ebuild 2.3.2 has a line exceeding 80 positions on line 11.
• [Warning] Ebuild 2.3.2 has a line exceeding 80 positions on line 13.
• [Warning] Ebuild 2.3.1 has a line exceeding 80 positions on line 11.
• [Warning] Ebuild 2.3.1 has a line exceeding 80 positions on line 13.
• [Warning] USE flag 'gnome' in ebuild 2.3.9 is not documented in metadata.xml
• [Warning] USE flag 'kde' in ebuild 2.3.9 is not documented in metadata.xml
• [Warning] USE flag 'gnome' in ebuild 2.3.9 is not documented in metadata.xml
• [Warning] USE flag 'kde' in ebuild 2.3.9 is not documented in metadata.xml
• [Warning] USE flag 'gnome' in ebuild 2.3.7 is not documented in metadata.xml
• [Warning] USE flag 'kde' in ebuild 2.3.7 is not documented in metadata.xml
• [Warning] USE flag 'gnome' in ebuild 2.3.4 is not documented in metadata.xml
• [Warning] USE flag 'kde' in ebuild 2.3.4 is not documented in metadata.xml
• [Warning] USE flag 'gnome' in ebuild 2.3.2 is not documented in metadata.xml
• [Warning] USE flag 'kde' in ebuild 2.3.2 is not documented in metadata.xml
• [Warning] USE flag 'gnome' in ebuild 2.3.1 is not documented in metadata.xml
• [Warning] USE flag 'kde' in ebuild 2.3.1 is not documented in metadata.xml
• Bypassing the network sandbox using `RESTRICT="network-sandbox"` violates Gentoo's core packaging policies. Ebuilds must support offline and reproducible builds, meaning all assets must be fetched via `SRC_URI` during the fetch phase and verified using Manifest checksums. To resolve this, you should package the required dependencies (e.g., node modules, cargo crates) into a tarball, host it, reference it in `SRC_URI` and perform an offline installation.
• Bypassing the network sandbox using `RESTRICT="network-sandbox"` violates Gentoo's core packaging policies. Ebuilds must support offline and reproducible builds, meaning all assets must be fetched via `SRC_URI` during the fetch phase and verified using Manifest checksums. To resolve this, you should package the required dependencies (e.g., node modules, cargo crates) into a tarball, host it, reference it in `SRC_URI` and perform an offline installation.
• Bypassing the network sandbox using `RESTRICT="network-sandbox"` violates Gentoo's core packaging policies. Ebuilds must support offline and reproducible builds, meaning all assets must be fetched via `SRC_URI` during the fetch phase and verified using Manifest checksums. To resolve this, you should package the required dependencies (e.g., node modules, cargo crates) into a tarball, host it, reference it in `SRC_URI` and perform an offline installation.
• Bypassing the network sandbox using `RESTRICT="network-sandbox"` violates Gentoo's core packaging policies. Ebuilds must support offline and reproducible builds, meaning all assets must be fetched via `SRC_URI` during the fetch phase and verified using Manifest checksums. To resolve this, you should package the required dependencies (e.g., node modules, cargo crates) into a tarball, host it, reference it in `SRC_URI` and perform an offline installation.
• Bypassing the network sandbox using `RESTRICT="network-sandbox"` violates Gentoo's core packaging policies. Ebuilds must support offline and reproducible builds, meaning all assets must be fetched via `SRC_URI` during the fetch phase and verified using Manifest checksums. To resolve this, you should package the required dependencies (e.g., node modules, cargo crates) into a tarball, host it, reference it in `SRC_URI` and perform an offline installation.
• Bypassing the network sandbox using `RESTRICT="network-sandbox"` violates Gentoo's core packaging policies. Ebuilds must support offline and reproducible builds, meaning all assets must be fetched via `SRC_URI` during the fetch phase and verified using Manifest checksums. To resolve this, you should package the required dependencies (e.g., node modules, cargo crates) into a tarball, host it, reference it in `SRC_URI` and perform an offline installation.
• [Error] Manifest entry for unused DIST file 'globalprotect-openconnect-2.3.1.tar.gz'
• [Error] Manifest entry for unused DIST file 'globalprotect-openconnect-2.3.2.tar.gz'
• [Error] Manifest entry for unused DIST file 'globalprotect-openconnect-2.3.4.tar.gz'
• [Error] Manifest entry for unused DIST file 'globalprotect-openconnect-2.3.7.tar.gz'
• [Error] Manifest entry for unused DIST file 'globalprotect-openconnect-2.3.9.tar.gz'
• [Error] Repository is missing a repo-name in metadata/layout.conf or profiles/repo_name
• [Notice] Package has only unstable keywords for arch(es): [ amd64 ], all versions are unstable: [ 2.3.1, 2.3.2, 2.3.4, 2.3.7, 2.3.9, 2.3.9 ]
• [Error] Invalid or missing metadata.xml: open net-vpn/globalprotect-openconnect/metadata.xml: file does not exist

USE Flags

Manage flags for this package: euse -i <flag> -p net-vpn/globalprotect-openconnect | euse -E <flag> -p net-vpn/globalprotect-openconnect | euse -D <flag> -p net-vpn/globalprotect-openconnect

Manifest