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

Version	EAPI	Keywords
19.5.3	8	~amd64 ~x86
19.5.2	8	~amd64 ~x86
19.5.1	8	~amd64 ~x86
19.5.0	8	~amd64 ~x86
19.4.5	8	~amd64 ~x86
19.4.4	8	~amd64 ~x86
19.4.3	8	~amd64 ~x86
19.4.2	8	~amd64 ~x86
19.4.1	8	~amd64 ~x86
19.4.0	8	~amd64 ~x86
19.3.7	8	~amd64 ~x86
19.3.6	8	~amd64 ~x86
19.3.5	8	~amd64 ~x86
19.3.4	8	~amd64 ~x86
19.3.3	8	~amd64 ~x86
19.3.2	8	~amd64 ~x86
19.3.1	8	~amd64 ~x86
19.3.0	8	~amd64 ~x86

Metadata

No metadata available.

Lint Warnings

[Warning] Ebuild 19.5.3 has a line exceeding 80 positions on line 43.
[Warning] Ebuild 19.5.3 has trailing whitespace on line 54.
[Warning] Ebuild 19.5.3 uses spaces for indentation on line 55.
[Warning] Ebuild 19.5.2 has a line exceeding 80 positions on line 43.
[Warning] Ebuild 19.5.2 has trailing whitespace on line 54.
[Warning] Ebuild 19.5.2 uses spaces for indentation on line 55.
[Warning] Ebuild 19.5.1 has a line exceeding 80 positions on line 43.
[Warning] Ebuild 19.5.1 has trailing whitespace on line 54.
[Warning] Ebuild 19.5.1 uses spaces for indentation on line 55.
[Warning] Ebuild 19.5.0 has a line exceeding 80 positions on line 43.
[Warning] Ebuild 19.5.0 has trailing whitespace on line 54.
[Warning] Ebuild 19.5.0 uses spaces for indentation on line 55.
[Warning] Ebuild 19.4.5 has a line exceeding 80 positions on line 43.
[Warning] Ebuild 19.4.5 has trailing whitespace on line 54.
[Warning] Ebuild 19.4.5 uses spaces for indentation on line 55.
[Warning] Ebuild 19.4.4 has a line exceeding 80 positions on line 43.
[Warning] Ebuild 19.4.4 has trailing whitespace on line 54.
[Warning] Ebuild 19.4.4 uses spaces for indentation on line 55.
[Warning] Ebuild 19.4.3 has a line exceeding 80 positions on line 43.
[Warning] Ebuild 19.4.3 has trailing whitespace on line 54.
[Warning] Ebuild 19.4.3 uses spaces for indentation on line 55.
[Warning] Ebuild 19.4.2 has a line exceeding 80 positions on line 43.
[Warning] Ebuild 19.4.2 has trailing whitespace on line 54.
[Warning] Ebuild 19.4.2 uses spaces for indentation on line 55.
[Warning] Ebuild 19.4.1 has a line exceeding 80 positions on line 43.
[Warning] Ebuild 19.4.1 has trailing whitespace on line 54.
[Warning] Ebuild 19.4.1 uses spaces for indentation on line 55.
[Warning] Ebuild 19.4.0 has a line exceeding 80 positions on line 43.
[Warning] Ebuild 19.4.0 has trailing whitespace on line 54.
[Warning] Ebuild 19.4.0 uses spaces for indentation on line 55.
[Warning] Ebuild 19.3.7 has a line exceeding 80 positions on line 43.
[Warning] Ebuild 19.3.7 has trailing whitespace on line 54.
[Warning] Ebuild 19.3.7 uses spaces for indentation on line 55.
[Warning] Ebuild 19.3.6 has a line exceeding 80 positions on line 43.
[Warning] Ebuild 19.3.6 has trailing whitespace on line 54.
[Warning] Ebuild 19.3.6 uses spaces for indentation on line 55.
[Warning] Ebuild 19.3.5 has a line exceeding 80 positions on line 43.
[Warning] Ebuild 19.3.5 has trailing whitespace on line 54.
[Warning] Ebuild 19.3.5 uses spaces for indentation on line 55.
[Warning] Ebuild 19.3.4 has a line exceeding 80 positions on line 43.
[Warning] Ebuild 19.3.4 has trailing whitespace on line 54.
[Warning] Ebuild 19.3.4 uses spaces for indentation on line 55.
[Warning] Ebuild 19.3.3 has a line exceeding 80 positions on line 43.
[Warning] Ebuild 19.3.3 has trailing whitespace on line 54.
[Warning] Ebuild 19.3.3 uses spaces for indentation on line 55.
[Warning] Ebuild 19.3.2 has a line exceeding 80 positions on line 43.
[Warning] Ebuild 19.3.2 has trailing whitespace on line 54.
[Warning] Ebuild 19.3.2 uses spaces for indentation on line 55.
[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.5.3 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
[Warning] Ebuild 19.5.2 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
[Warning] Ebuild 19.5.1 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
[Warning] Ebuild 19.5.0 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
[Warning] Ebuild 19.4.5 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
[Warning] Ebuild 19.4.4 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
[Warning] Ebuild 19.4.3 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
[Warning] Ebuild 19.4.2 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
[Warning] Ebuild 19.4.1 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
[Warning] Ebuild 19.4.0 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
[Warning] Ebuild 19.3.7 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
[Warning] Ebuild 19.3.6 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
[Warning] Ebuild 19.3.5 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
[Warning] Ebuild 19.3.4 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
[Warning] Ebuild 19.3.3 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
[Warning] Ebuild 19.3.2 calls 'systemd_dounit' conditionally based on a USE flag. Small files must be installed unconditionally (PG0301).
[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] USE flag 'systemd' in ebuild 19.5.3 is not documented in metadata.xml
[Warning] USE flag 'systemd' in ebuild 19.5.2 is not documented in metadata.xml
[Warning] USE flag 'systemd' in ebuild 19.5.1 is not documented in metadata.xml
[Warning] USE flag 'systemd' in ebuild 19.5.0 is not documented in metadata.xml
[Warning] USE flag 'systemd' in ebuild 19.4.5 is not documented in metadata.xml
[Warning] USE flag 'systemd' in ebuild 19.4.4 is not documented in metadata.xml
[Warning] USE flag 'systemd' in ebuild 19.4.3 is not documented in metadata.xml
[Warning] USE flag 'systemd' in ebuild 19.4.2 is not documented in metadata.xml
[Warning] USE flag 'systemd' in ebuild 19.4.1 is not documented in metadata.xml
[Warning] USE flag 'systemd' in ebuild 19.4.0 is not documented in metadata.xml
[Warning] USE flag 'systemd' in ebuild 19.3.7 is not documented in metadata.xml
[Warning] USE flag 'systemd' in ebuild 19.3.6 is not documented in metadata.xml
[Warning] USE flag 'systemd' in ebuild 19.3.5 is not documented in metadata.xml
[Warning] USE flag 'systemd' in ebuild 19.3.4 is not documented in metadata.xml
[Warning] USE flag 'systemd' in ebuild 19.3.3 is not documented in metadata.xml
[Warning] USE flag 'systemd' in ebuild 19.3.2 is not documented in metadata.xml
[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
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.
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.
[Notice] Package has only unstable keywords for arch(es): [ amd64, x86 ], all versions are unstable: [ 19.3.0, 19.3.1, 19.3.2, 19.3.3, 19.3.4, 19.3.5, 19.3.6, 19.3.7, 19.4.0, 19.4.1, 19.4.2, 19.4.3, 19.4.4, 19.4.5, 19.5.0, 19.5.1, 19.5.2, 19.5.3 ]
[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

Flag	Description	19.5.3	19.5.2	19.5.1	19.5.0	19.4.5	19.4.4	19.4.3	19.4.2	19.4.1	19.4.0	19.3.7	19.3.6	19.3.5	19.3.4	19.3.3	19.3.2	19.3.1	19.3.0
systemd	⚠️	✓	✓	✓	✓	✓	✓	✓	✓	✓	✓	✓	✓	✓	✓	✓	✓	✓	✓

Files

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

Manifest

Type	File	Size	Versions

Unmatched Entries

Type	File	Size
AUX	gitlab-pages.conf	771 bytes
AUX	gitlab-pages.confd	696 bytes
AUX	gitlab-pages.initd	429 bytes
AUX	gitlab-pages.service	425 bytes
EBUILD	gitlab-pages-19.3.0.ebuild	1495 bytes
EBUILD	gitlab-pages-19.3.1.ebuild	1495 bytes
EBUILD	gitlab-pages-19.3.2.ebuild	1495 bytes
EBUILD	gitlab-pages-19.3.3.ebuild	1495 bytes
EBUILD	gitlab-pages-19.3.4.ebuild	1495 bytes
EBUILD	gitlab-pages-19.3.5.ebuild	1495 bytes
EBUILD	gitlab-pages-19.3.6.ebuild	1495 bytes
EBUILD	gitlab-pages-19.3.7.ebuild	1495 bytes
EBUILD	gitlab-pages-19.4.0.ebuild	1495 bytes
EBUILD	gitlab-pages-19.4.1.ebuild	1495 bytes
EBUILD	gitlab-pages-19.4.2.ebuild	1495 bytes
EBUILD	gitlab-pages-19.4.3.ebuild	1495 bytes
EBUILD	gitlab-pages-19.4.4.ebuild	1495 bytes
EBUILD	gitlab-pages-19.4.5.ebuild	1495 bytes
EBUILD	gitlab-pages-19.5.0.ebuild	1495 bytes
EBUILD	gitlab-pages-19.5.1.ebuild	1495 bytes
EBUILD	gitlab-pages-19.5.2.ebuild	1495 bytes
EBUILD	gitlab-pages-19.5.3.ebuild	1495 bytes

www-apps/gitlab-pages (gitlab)