Source: unibilium
Version: 2.1.1-2
Severity: important
Tags: forky sid
Yesterday I uploaded a new ncurses patchlevel to experimental, and the
unibilium autopkgtest fails with ncurses-base 6.6+20260608-1, see [1]:
,----
| 41s # Parsing /usr/share/terminfo/x/xterm ...
| 41s not ok - db entry for xterm is too small to be valid
| 41s # Parsing /usr/share/terminfo/x/xterm-256color ...
| 41s not ok - db entry for xterm-256color is too small to be valid
`----
I have not looked at the details yet, but I suspect that the problem is
just the opposite of what the error message claims, namely that the
entries are too _large_ to be considered valid. The two terminfo
entries exceed the size of 4096 bytes, and libunibilium apparently has a
problem with that. Note that with the new format introduced in ncurses
6.1, compiled terminfo entries may be up to 32768 bytes.
,----
| $ stat -c '%s %n' /usr/share/terminfo/x/xterm{,-256color}
| 4156 /usr/share/terminfo/x/xterm
| 4242 /usr/share/terminfo/x/xterm-256color
`----
In forky (and older), the size of these two files is below the 4096
bytes boundary:
,----
| (forky)$ stat -c '%s %n' /usr/share/terminfo/x/xterm{,-256color}
| 3980 /usr/share/terminfo/x/xterm
| 4074 /usr/share/terminfo/x/xterm-256color
`----
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
1. https://ci.debian.net/packages/u/unibilium/unstable/arm64/71951602/
