sys-boot/grub-static

Static analysis

Repoman

repo.eapi.deprecated sys-boot/grub-static/grub-static-0.96-r1.ebuild: 0
repo.eapi.deprecated sys-boot/grub-static/grub-static-0.97.ebuild: 0
repo.eapi.deprecated sys-boot/grub-static/grub-static-0.97-r6.ebuild: 0
repo.eapi.deprecated sys-boot/grub-static/grub-static-0.97-r9.ebuild: 0
repo.eapi.deprecated sys-boot/grub-static/grub-static-0.97-r10.ebuild: 0
repo.eapi.deprecated sys-boot/grub-static/grub-static-0.97-r12.ebuild: 0

pkgcore-checks

  StaleUnstableKeyword: version 0.96-r1: no change in 683 days for unstable keywords [ ~x86 ]
  StaleUnstableKeyword: version 0.97: no change in 683 days for unstable keywords [ ~x86 ]
  StaleUnstableKeyword: version 0.97-r6: no change in 683 days for unstable keywords [ ~x86 ]
  StaleUnstableKeyword: version 0.97-r10: no change in 683 days for unstable keywords [ ~x86 ]
  StaleUnstableKeyword: version 0.97-r12: no change in 666 days for unstable keywords [ ~x86 ]
  MissingChksum: version 0.96-r1: file grub-static-0.96.tar.bz2 is missing required chksums: sha512, whirlpool; has chksums: sha256, size
  MissingChksum: version 0.97: file grub-static-0.97.tar.bz2 is missing required chksums: sha512, whirlpool; has chksums: sha256, size
  MissingChksum: version 0.97-r6: file grub-static-0.97-r6.tar.bz2 is missing required chksums: sha512, whirlpool; has chksums: sha256, size
  LaggingStableInfo: version 0.97-r12: stabled arches [ amd64 ], potentials [ ~x86 ]
  RedundantVersionWarning: version 0.96-r1: slot(0) keywords are overshadowed by version '0.97-r12, 0.97-r10, 0.97-r9, 0.97-r6, 0.97'
  RedundantVersionWarning: version 0.97: slot(0) keywords are overshadowed by version '0.97-r12, 0.97-r10, 0.97-r9, 0.97-r6'
  RedundantVersionWarning: version 0.97-r6: slot(0) keywords are overshadowed by version '0.97-r12, 0.97-r10, 0.97-r9'
  RedundantVersionWarning: version 0.97-r10: slot(0) keywords are overshadowed by version '0.97-r12'

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