Gentoo Packages

Search

Install

Install this package:

emerge -a www-apps/gitlab-pages

Package Information

Description:

GitLab Pages daemon used to serve static websites for GitLab users

Homepage:

https://gitlab.com/gitlab-org/gitlab-pages

License:

MIT

Versions

Metadata

No metadata available.

Lint Warnings

• [Warning] Ebuild 19.3.1 has a line exceeding 80 positions on line 43.
• [Warning] Ebuild 19.3.1 has trailing whitespace on line 54.
• [Warning] Ebuild 19.3.1 uses spaces for indentation on line 55.
• [Warning] Ebuild 19.3.0 has a line exceeding 80 positions on line 43.
• [Warning] Ebuild 19.3.0 has trailing whitespace on line 54.
• [Warning] Ebuild 19.3.0 uses spaces for indentation on line 55.
• [Warning] Ebuild 19.2.5 has a line exceeding 80 positions on line 43.
• [Warning] Ebuild 19.2.5 has trailing whitespace on line 54.
• [Warning] Ebuild 19.2.5 uses spaces for indentation on line 55.
• [Warning] Ebuild 19.2.4 has a line exceeding 80 positions on line 43.
• [Warning] Ebuild 19.2.4 has trailing whitespace on line 54.
• [Warning] Ebuild 19.2.4 uses spaces for indentation on line 55.
• [Warning] Ebuild 19.2.2 has a line exceeding 80 positions on line 43.
• [Warning] Ebuild 19.2.2 has trailing whitespace on line 54.
• [Warning] Ebuild 19.2.2 uses spaces for indentation on line 55.
• [Warning] Ebuild 19.2.1 has a line exceeding 80 positions on line 43.
• [Warning] Ebuild 19.2.1 has trailing whitespace on line 54.
• [Warning] Ebuild 19.2.1 uses spaces for indentation on line 55.
• [Warning] Ebuild 19.2.0 has a line exceeding 80 positions on line 43.
• [Warning] Ebuild 19.2.0 has trailing whitespace on line 54.
• [Warning] Ebuild 19.2.0 uses spaces for indentation on line 55.
• [Warning] Ebuild 19.1.7 has a line exceeding 80 positions on line 43.
• [Warning] Ebuild 19.1.7 has trailing whitespace on line 54.
• [Warning] Ebuild 19.1.7 uses spaces for indentation on line 55.
• [Warning] Ebuild 19.1.6 has a line exceeding 80 positions on line 43.
• [Warning] Ebuild 19.1.6 has trailing whitespace on line 54.
• [Warning] Ebuild 19.1.6 uses spaces for indentation on line 55.
• [Warning] Ebuild 19.1.4 has a line exceeding 80 positions on line 43.
• [Warning] Ebuild 19.1.4 has trailing whitespace on line 54.
• [Warning] Ebuild 19.1.4 uses spaces for indentation on line 55.
• [Warning] Ebuild 19.1.3 has a line exceeding 80 positions on line 43.
• [Warning] Ebuild 19.1.3 has trailing whitespace on line 54.
• [Warning] Ebuild 19.1.3 uses spaces for indentation on line 55.
• [Warning] Ebuild 19.1.2 has a line exceeding 80 positions on line 43.
• [Warning] Ebuild 19.1.2 has trailing whitespace on line 54.
• [Warning] Ebuild 19.1.2 uses spaces for indentation on line 55.
• [Warning] Ebuild 19.1.1 has a line exceeding 80 positions on line 43.
• [Warning] Ebuild 19.1.1 has trailing whitespace on line 54.
• [Warning] Ebuild 19.1.1 uses spaces for indentation on line 55.
• [Warning] Ebuild 19.1.0 has a line exceeding 80 positions on line 43.
• [Warning] Ebuild 19.1.0 has trailing whitespace on line 54.
• [Warning] Ebuild 19.1.0 uses spaces for indentation on line 55.
• [Warning] Ebuild 19.3.1 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
• [Warning] Ebuild 19.3.0 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
• [Warning] Ebuild 19.2.5 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
• [Warning] Ebuild 19.2.4 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
• [Warning] Ebuild 19.2.2 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
• [Warning] Ebuild 19.2.1 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
• [Warning] Ebuild 19.2.0 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
• [Warning] Ebuild 19.1.7 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
• [Warning] Ebuild 19.1.6 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
• [Warning] Ebuild 19.1.4 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
• [Warning] Ebuild 19.1.3 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
• [Warning] Ebuild 19.1.2 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
• [Warning] Ebuild 19.1.1 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
• [Warning] Ebuild 19.1.0 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
• [Warning] USE flag 'systemd' in ebuild 19.3.1 is not documented in metadata.xml
• [Warning] USE flag 'systemd' in ebuild 19.3.0 is not documented in metadata.xml
• [Warning] USE flag 'systemd' in ebuild 19.2.5 is not documented in metadata.xml
• [Warning] USE flag 'systemd' in ebuild 19.2.4 is not documented in metadata.xml
• [Warning] USE flag 'systemd' in ebuild 19.2.2 is not documented in metadata.xml
• [Warning] USE flag 'systemd' in ebuild 19.2.1 is not documented in metadata.xml
• [Warning] USE flag 'systemd' in ebuild 19.2.0 is not documented in metadata.xml
• [Warning] USE flag 'systemd' in ebuild 19.1.7 is not documented in metadata.xml
• [Warning] USE flag 'systemd' in ebuild 19.1.6 is not documented in metadata.xml
• [Warning] USE flag 'systemd' in ebuild 19.1.4 is not documented in metadata.xml
• [Warning] USE flag 'systemd' in ebuild 19.1.3 is not documented in metadata.xml
• [Warning] USE flag 'systemd' in ebuild 19.1.2 is not documented in metadata.xml
• [Warning] USE flag 'systemd' in ebuild 19.1.1 is not documented in metadata.xml
• [Warning] USE flag 'systemd' in ebuild 19.1.0 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.
• 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.
• 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] Repository is missing a repo-name in metadata/layout.conf or profiles/repo_name
• [Notice] Package has only unstable keywords for arch(es): [ amd64, x86 ], all versions are unstable: [ 19.1.0, 19.1.1, 19.1.2, 19.1.3, 19.1.4, 19.1.6, 19.1.7, 19.2.0, 19.2.1, 19.2.2, 19.2.4, 19.2.5, 19.3.0, 19.3.1 ]
• [Error] Invalid or missing metadata.xml: open www-apps/gitlab-pages/metadata.xml: file does not exist

USE Flags

Manage flags for this package: euse -i <flag> -p www-apps/gitlab-pages | euse -E <flag> -p www-apps/gitlab-pages | euse -D <flag> -p www-apps/gitlab-pages

Files

• gitlab-pages.conf
• gitlab-pages.confd
• gitlab-pages.initd
• gitlab-pages.service

Manifest