[Pkg-zsh-devel] zsh FTBFS under Salsa CI's reprotest: 'KEY_EVENT' undeclared / blhc CI check disabled / bullseye freeze: zsh is considered a key package

[Daniel Shahaf]

Axel Beckert wrote on Mon, 12 Oct 2020 15:45 +00:00:
> 1. zsh FTBFS inside reprotest on Salsa CI:
> https://salsa.debian.org/debian/zsh/-/jobs/1012123#L2931
> 
> Relevant lines:
> 
> gcc -c -I. -I../../Src -I../../../Src -I../../../Src/Zle 
> -I../../../Src/Modules -Wdate-time -D_FORTIFY_SOURCE=2  -DHAVE_CONFIG_H 
> -DMODULE -g -O2 
> -fdebug-prefix-map=/tmp/reprotest.1y9OUh/const_build_path/const_build_path=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -g -fPIC -o curses..o ../../../Src/Modules/curses.c
> In file included from ../../../Src/Modules/curses.c:210:
> ./curses_keys.h:93:15: error: ‘KEY_EVENT’ undeclared here (not in a 
> function); did you mean ‘KEY_RESET’?
>    93 |     {"EVENT", KEY_EVENT},
>       |               ^~~~~~~~~
>       |               KEY_RESET
> make[5]: *** [Makefile:240: curses..o] Error 1
> 
> Anyone an idea why? Because if I run "reprotest --variations=-kernel
> ." locally in my checked out source of zsh, it passes without issues.
> 
> (If I omit the "--variations=-kernel", it will FTBFS, but with
> "unshare" failing with "No space left on device" despite I have no
> idea on which device that happens. But since there are quite some
> issues known to reprotest calling unshare in both its README as well
> as in the bug reports against reprotest, I do not expect this to be a
> zsh issue.)
> 
> So I just declared that reprotest failures on Salsa CI are acceptable
> (for now). See
> https://salsa.debian.org/salsa-ci-team/pipeline#allow-reprotest-to-fail
> 
> Will push the according commit soon.

Looks just like the issue fixed upstream in zsh-5.8-251-gc6a851636.

Cheers,

Daniel