The release has fixes tracked by bug 691278. There are no known regressions. The /usr/bin/glsa-check executable is now installed by portage instead of gentoolkit (bug 463952), so this version or portage blocks <app-portage/gentoolkit-0.4.6, and both =app-portage/gentoolkit-0.4.6 and =sys-apps/portage-2.3.76 must be simultaneously stabilized (in the same push).
sparc stable
amd64 stable
ia64/ppc/ppc64 stable
x86 stable
s390 stable
So, when trying to perform an @world update, I get the following message related to this bug report: ``` [...] snip [...] [blocks B ] <app-portage/gentoolkit-0.4.6 ("<app-portage/gentoolkit-0.4.6" is blocking sys-apps/portage-2.3.76) [...] snip [...] ``` Since this bug has a status of CONFIRMED, I assume we can expect an ebuild update for gentoolkit, right? However, in the mean time, is there a nice "Gentoo-esque" way to ignore this particular Portage update for now, and continue updating other pending updates? (Sorry if this isn't place to ask)
(In reply to Guido Kroon from comment #6) > Since this bug has a status of CONFIRMED, I assume we can expect an ebuild > update for gentoolkit, right? Yes, maybe you just need to emerge --sync again. The keywords appear to be in sync right now: > $ grep KEYWORDS sys-apps/portage/portage-2.3.76.ebuild > KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ia64 ~m68k ~mips ppc ppc64 ~riscv s390 ~sh sparc x86 ~amd64-fbsd" > $ grep KEYWORDS app-portage/gentoolkit/gentoolkit-0.4.6.ebuild > KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ia64 ~m68k ~mips ppc ppc64 ~riscv s390 ~sh sparc x86 ~ppc-aix ~x64-cygwin ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
arm stable
alpha stable
arm64 stable
hppa stable