Get Gentoo!

sys-boot/gnu-efi

Package

Summary

Version Builds Tests QA
gnu-efi-3.0i
gnu-efi-3.0s
gnu-efi-3.0g
gnu-efi-3.0a-r1
gnu-efi-3.0u

Static analysis

Repoman

upstream.workaround sys-boot/gnu-efi/gnu-efi-3.0a-r1.ebuild: Upstream parallel compilation bug (ebuild calls emake -j1 on line: 31)
upstream.workaround sys-boot/gnu-efi/gnu-efi-3.0g.ebuild: Upstream parallel compilation bug (ebuild calls emake -j1 on line: 30)
upstream.workaround sys-boot/gnu-efi/gnu-efi-3.0i.ebuild: Upstream parallel compilation bug (ebuild calls emake -j1 on line: 36)
RDEPEND.implicit sys-boot/gnu-efi/gnu-efi-3.0a-r1.ebuild: RDEPEND is not explicitly assigned
RDEPEND.implicit sys-boot/gnu-efi/gnu-efi-3.0g.ebuild: RDEPEND is not explicitly assigned
RDEPEND.implicit sys-boot/gnu-efi/gnu-efi-3.0i.ebuild: RDEPEND is not explicitly assigned
repo.eapi.deprecated sys-boot/gnu-efi/gnu-efi-3.0a-r1.ebuild: 0
repo.eapi.deprecated sys-boot/gnu-efi/gnu-efi-3.0g.ebuild: 0
repo.eapi.deprecated sys-boot/gnu-efi/gnu-efi-3.0i.ebuild: 0

pkgcore-checks

  StaleUnstableKeyword: version 3.0g: no change in 1607 days for unstable keywords [ ~amd64, ~x86 ]
  StaleUnstableKeyword: version 3.0i: no change in 1377 days for unstable keywords [ ~amd64, ~x86 ]
  StaleUnstableKeyword: version 3.0u: no change in 82 days for unstable keywords [ ~amd64, ~ia64, ~x86 ]
  MissingChksum: version 3.0a-r1: file gnu-efi-3.0a.tar.gz is missing required chksums: sha512, whirlpool; has chksums: sha256, size
  MissingChksum: version 3.0g: file gnu-efi_3.0g.orig.tar.gz is missing required chksums: sha512, whirlpool; has chksums: sha256, size
  LaggingStableInfo: version 3.0i: stabled arches [ ia64 ], potentials [ ~amd64, ~x86 ]
  RedundantVersionWarning: version 3.0a-r1: slot(0) keywords are overshadowed by version '3.0s'
  RedundantVersionWarning: version 3.0g: slot(0) keywords are overshadowed by version '3.0s, 3.0i'
  RedundantVersionWarning: version 3.0i: slot(0) keywords are overshadowed by version '3.0s'

Sub-slot candidates

This lists all sub-slot candidates without regard to their appropriateness. Please check with the appropriate maintainer before implementing them. 

Nothing to report