Gentoo Packages

Search

Install

Install this package:

emerge -a net-im/equibop

Package Information

Description:

Equibop is a fork of Vesktop.

Homepage:

https://github.com/Equicord/Equibop

License:

GPL-3

Versions

Metadata

No metadata available.

Lint Warnings

• [Error] Ebuild net-im/equibop/equibop-9999.ebuild attempts to create an absolute symlink using 'dosym /opt/equibop/linux-unpacked/equibop', which must be relative instead.
• [Error] Ebuild net-im/equibop/equibop-3.0.8.ebuild attempts to create an absolute symlink using 'dosym /opt/equibop/linux-unpacked/equibop', which must be relative instead.
• [Error] Ebuild net-im/equibop/equibop-2.1.7.ebuild attempts to create an absolute symlink using 'dosym /opt/equibop/linux-unpacked/equibop', which must be relative instead.
• [Error] Ebuild net-im/equibop/equibop-2.1.6.ebuild attempts to create an absolute symlink using 'dosym /opt/equibop/linux-unpacked/equibop', which must be relative instead.
• [Error] Ebuild net-im/equibop/equibop-2.1.5.ebuild attempts to create an absolute symlink using 'dosym /opt/equibop/linux-unpacked/equibop', which must be relative instead.
• [Error] Ebuild net-im/equibop/equibop-2.1.4.ebuild attempts to create an absolute symlink using 'dosym /opt/equibop/linux-unpacked/equibop', which must be relative instead.
• [Error] Ebuild net-im/equibop/equibop-2.1.3.ebuild attempts to create an absolute symlink using 'dosym /opt/equibop/linux-unpacked/equibop', which must be relative instead.
• Ebuild 9999 has a missing or malformed copyright/licensing header.
• Ebuild 3.0.8 has a missing or malformed copyright/licensing header.
• Ebuild 2.1.7 has a missing or malformed copyright/licensing header.
• Ebuild 2.1.6 has a missing or malformed copyright/licensing header.
• Ebuild 2.1.5 has a missing or malformed copyright/licensing header.
• Ebuild 2.1.4 has a missing or malformed copyright/licensing header.
• Ebuild 2.1.3 has a missing or malformed copyright/licensing header.
• [Notice] Ebuild 9999 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 3.0.8 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.1.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.1.6 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.1.5 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.1.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.1.3 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.1.7 has a line exceeding 80 positions on line 7.
• [Warning] Ebuild 2.1.6 has a line exceeding 80 positions on line 7.
• [Warning] Ebuild 2.1.5 has a line exceeding 80 positions on line 7.
• [Warning] Ebuild 2.1.4 has a line exceeding 80 positions on line 7.
• [Warning] Ebuild 2.1.3 has a line exceeding 80 positions on line 7.
• [Warning] Ebuild 2.1.3 has trailing whitespace on line 26.
• [Warning] Ebuild 2.1.3 has trailing whitespace on line 28.
• 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] Manifest entry for unused DIST file 'equibop-2.1.3.tar.gz'
• [Error] Manifest entry for unused DIST file 'equibop-2.1.4.tar.gz'
• [Error] Manifest entry for unused DIST file 'equibop-2.1.5.tar.gz'
• [Error] Manifest entry for unused DIST file 'equibop-2.1.6.tar.gz'
• [Error] Manifest entry for unused DIST file 'equibop-2.1.7.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.1.3, 2.1.4, 2.1.5, 2.1.6, 2.1.7, 3.0.8 ]
• [Error] Invalid or missing metadata.xml: open net-im/equibop/metadata.xml: file does not exist

Manifest