SUSE-CU-2024:1518-1: Recommended update of bci/bci-init
sle-container-updates at lists.suse.com
sle-container-updates at lists.suse.com
Tue Apr 16 07:13:04 UTC 2024
SUSE Container Update Advisory: bci/bci-init
-----------------------------------------------------------------
Container Advisory ID : SUSE-CU-2024:1518-1
Container Tags : bci/bci-init:15.6 , bci/bci-init:15.6.7.33
Container Release : 7.33
Severity : moderate
Type : recommended
References : 1210959 1214934 1217450 1217667 1218492 1219031 1219520 1220724
1221239
-----------------------------------------------------------------
The container bci/bci-init was updated. The following patches have been included in this update:
-----------------------------------------------------------------
Advisory ID: SUSE-RU-2024:1253-1
Released: Fri Apr 12 08:15:18 2024
Summary: Recommended update for gcc13
Type: recommended
Severity: moderate
References: 1210959,1214934,1217450,1217667,1218492,1219031,1219520,1220724,1221239
This update for gcc13 fixes the following issues:
- Fix unwinding for JIT code. [bsc#1221239]
- Revert libgccjit dependency change. [bsc#1220724]
- Remove crypt and crypt_r interceptors. The crypt API change in SLE15 SP3
breaks them. [bsc#1219520]
- Add support for -fmin-function-alignment. [bsc#1214934]
- Use %{_target_cpu} to determine host and build.
- Fix for building TVM. [bsc#1218492]
- Add cross-X-newlib-devel requires to newlib cross compilers.
[bsc#1219031]
- Package m2rte.so plugin in the gcc13-m2 sub-package rather than in gcc13-devel. [bsc#1210959]
- Require libstdc++6-devel-gcc13 from gcc13-m2 as m2 programs are linked against libstdc++6.
- Fixed building mariadb on i686. [bsc#1217667]
- Avoid update-alternatives dependency for accelerator crosses.
- Package tool links to llvm in cross-amdgcn-gcc13 rather than in
cross-amdgcn-newlib13-devel since that also has the dependence.
- Depend on llvmVER instead of llvm with VER equal to
%product_libs_llvm_ver where available and adjust tool discovery
accordingly. This should also properly trigger re-builds when
the patchlevel version of llvmVER changes, possibly changing
the binary names we link to. [bsc#1217450]
The following package changes have been done:
- glibc-2.38-150600.9.2 updated
- libgcrypt20-1.10.3-150600.1.17 updated
- libgcc_s1-13.2.1+git8285-150000.1.9.1 updated
- libstdc++6-13.2.1+git8285-150000.1.9.1 updated
- libopenssl3-3.1.4-150600.2.17 updated
- libsystemd0-254.10-150600.1.1 updated
- libopenssl-3-fips-provider-3.1.4-150600.2.17 updated
- sles-release-15.6-150600.32.2 updated
- systemd-254.10-150600.1.1 updated
- container:sles15-image-15.0.0-46.2.6 updated
More information about the sle-container-updates
mailing list