It is interesting how it worked without this before... And how it works in Fedora with transaction-only triggers.
Probably libraries in /usr/lib64 are found always, even without runs of ldconfig, but libraries in non-standard directories like /lib64 now, after update to 2.36 and merging /usr, are not.
Let's build this package so that those who need it could install it.
nscd.socket does not exist in upstream any more, so do not install it
(I doubt it is useful).
Lua is not needed in scriptlets, use plain shell.
Do not own files from tmpfs /run (%%_rundir), it is useless.
```
DEBUG: strcoll_l.c:184:24: error: 'seq2.save_idx' may be used uninitialized in this function [-Werror=maybe-uninitialized]
DEBUG: 184 | len = weights[idx++];
DEBUG: | ~~~^~
```
glibc's upstream has git branches where important fixes are backported.
Let's use them instead of applying most of commits as patches.
Automate updates by script upd.sh.
Deleted strange patches without propper description.
glibc is a core component where we should avoid not properly audited and/or tested code.
Removed all Clear Linux patches, removed patches "from Fedora" which do not exist in fc37 and current rawhide.
We do not need to build glibc with clang, drop clang-related patches.
- caching of group and passwd does not make sense because sssd and winbind have their own caches, and NIS is not used nowadays
- caching to accelerate DNS resolution would be useful, but:
- systemd-resolved is used by default in rosa2019.1 and has its own cache
- but hosts cache is offed by default by eglibc-mandriva-nscd-no-host-cache.patch
So, nscd does not make sense. And causes troubles in different situations, e.g. in useradd --root <...> in Anaconda.
Support being a chroot on RHEL 8 (4.18), Ubuntu 18.04 (4.15) and LTS (4.14) kernel
For example, we have an aarch64 server with such kernel where it is problematic to upgrade it right now :(
Fixes: f1a767c "Support syscalls of kernel 5.4"
I have looked at https://sourceware.org/git/?p=glibc.git;a=history;f=sysdeps/unix/sysv/linux/syscall-names.list;h=HEAD;hb=HEAD
and it seems that we do not support quite a lot of syscalls
We loose ability to run in chroots/containers on CentOS 8, but it is probably not a big problem for us right now
(ROSA is not a populer distro for contaienrs unfortunately)
and, I think, it is better to support newer syscalls than try to support strange hosts of containers.
We do not support RHEL 7 hosts now (they have kernel 3.10, but we require 4.0+).
Both rosa2019.1 and RHEL 9 with a newer kernel will be released soon
Discussed with and approved by fedya@.
He also said that older kernels are not required on aarch64.
