Comments

94 Comments

What is wrong here? I have this update received via stable-updates not via testing-updates.

I'm not entirely sure. If you look at the history here, it was supposedly pushed automatically, but then it was ejected, whatever this means (devel thread about ejected updates, ticket). So I've just pushed it manually.

BZ#2030870 valgrind: Please handle the rseq system call

I'm surprised that -24 fixed the OpenJDK build because I didn't fix wcscmp.

BZ#2007807 tzdata-2021b is available

This update reportedly breaks Steam, see bug #2005142.

BZ#1661510 glibc: Adjust to rpm's find-debuginfo.sh changes, to keep stripping binaries [Fedora]
BZ#1886295 glibc: ldconfig debuginfo file conflict between i686 and x86_64
BZ#1905611 glibc: Do not remove debugging information from ld.so
BZ#1932590 CVE-2021-27645 glibc: Use-after-free in addgetnetgrentX function in netgroupcache.c [fedora-all]
BZ#1901445 beaker-28.1 is available
BZ#1918649 beaker: GSSAPI interface uses base64.encodestring removed in Python 3.9
karma

Upstream test case for CVE-2019-25013 no longer segfaults. System still boots and core functionality is available.

BZ#1913056 CVE-2019-25013 glibc: buffer over-read in iconv when processing invalid multi-byte input sequences in the EUC-KR encoding [fedora-all]
BZ#1779399 .gnu.build.attributes problems causing FTBFS on f30, f31
BZ#1779399 .gnu.build.attributes problems causing FTBFS on f30, f31
BZ#1767937 strip:testprog[.gnu.build.attributes]: corrupt GNU build attribute note: wrong note type: bad value