Tracker bug. No talking please.
Just as a relevant remark, I don't want to *unneccessarily* touch toolchain ebuilds for this.
The old versions with EAPI=0 are phased out, but slowly.
Created attachment 578642 [details]
current list of EAPI=0 ebuilds (691)
Created attachment 585370 [details]
current list of EAPI=0 ebuilds (670)
Created attachment 591618 [details]
current list of EAPI=0 ebuilds (633)
Created attachment 592858 [details]
EAPI 0 packages, grouped by maintainer
Here's the updated list. I'm sorry for lack of sorting, something doesn't want to work ;-).
Created attachment 592860 [details]
EAPI 0 pacakges, grouped by maintainer (correct, this time)
Ok, I see that grouping was wrong too. Fixed the bug and now the output is neat.
Created attachment 595510 [details]
packages still needing update (143)
The bug has been closed via the following commit(s):
Author: Aaron Bauman <email@example.com>
AuthorDate: 2019-12-09 20:26:43 +0000
Commit: Aaron Bauman <firstname.lastname@example.org>
CommitDate: 2019-12-09 20:29:30 +0000
metadata/layout.conf: ban EAPI 0
Signed-off-by: Aaron Bauman <email@example.com>
metadata/layout.conf | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)