Comment 17 for bug 1863116

I have to update the verification status for focal.
I re-did everything from scratch and it worked now.
(Did it twice, just to be sure - there was either a problem in the git tree I used or s/t went wrong while I transferred the data to a s390x test system or a racy situation ...)

I can now confirm that 'updateconfigs' works on a focal master-next tree on a non-amd64 system (s390x was used):

$ fakeroot debian/rules updateconfigs
dh_testdir;
/bin/bash -e debian/scripts/misc/kernelconfig updateconfigs
WARNING: x86_64-linux-gnu-gcc not installed
Running splitconfig.pl for amd64
...
Creating stub configs ...
  processing config.common.arm64 ... done.
  processing config.common.amd64 ... done.
  processing config.common.armhf ... done.
  processing config.common.s390x ... done.
  processing config.common.i386 ... done.
  processing config.common.ppc64el ... done.

Running config-check for all configurations ...

check-config: /tmp/tmp.IkFhf0NTgn/CONFIGS/s390x-config.flavour.generic: loading config
check-config: /home/ubuntu/focal-master-next/debian.master/config/annotations loading annotations
check-config: 133/133 checks passed -- exit 0

WARNING: configuration operation applied only to a subset of architectures (skipped amd64 i386 armhf arm64 ppc64el)

rm -rf build
$

A subsequent kernel build completed fine.

(same output an behavior than with groovy)

Adjusting tag accordingly ...