This update for ncurses fixes the following issue:
analyze_string()of progs/infocmp.c (bsc#1259924).{
"binaries": [
{
"libncurses5": "6.5.20250531-160000.3.1",
"libncurses6": "6.5.20250531-160000.3.1",
"ncurses-devel": "6.5.20250531-160000.3.1",
"ncurses-devel-static": "6.5.20250531-160000.3.1",
"ncurses-examples": "6.5.20250531-160000.3.1",
"ncurses-utils": "6.5.20250531-160000.3.1",
"tack": "1.11.20250503-160000.3.1",
"terminfo": "6.5.20250531-160000.3.1",
"terminfo-base": "6.5.20250531-160000.3.1",
"terminfo-iterm": "6.5.20250531-160000.3.1",
"terminfo-screen": "6.5.20250531-160000.3.1"
}
]
}
{
"binaries": [
{
"libncurses5": "6.5.20250531-160000.3.1",
"libncurses6": "6.5.20250531-160000.3.1",
"ncurses-devel": "6.5.20250531-160000.3.1",
"ncurses-devel-static": "6.5.20250531-160000.3.1",
"ncurses-examples": "6.5.20250531-160000.3.1",
"ncurses-utils": "6.5.20250531-160000.3.1",
"tack": "1.11.20250503-160000.3.1",
"terminfo": "6.5.20250531-160000.3.1",
"terminfo-base": "6.5.20250531-160000.3.1",
"terminfo-iterm": "6.5.20250531-160000.3.1",
"terminfo-screen": "6.5.20250531-160000.3.1"
}
]
}