openSUSE-Leap-16.0-4 moderate SUSE SLFO 1.2 This update for cloud-regionsrv-client fixes the following issues: Update version to 10.5.2 (bsc#1247539) + When an instance fails verification server side the default credentials were left behind requireing manual intervantion prior to the next registration attempt. + Fix issue triggered when using instance-billing-flavor-check due to IP address handling as object rather than string introduced 10.5.0 cloud-regionsrv-client-10.5.2-160000.3.1.noarch.rpm cloud-regionsrv-client-10.5.2-160000.3.1.src.rpm cloud-regionsrv-client-generic-config-1.0.0-160000.3.1.noarch.rpm cloud-regionsrv-client-license-watcher-1.0.0-160000.3.1.noarch.rpm cloud-regionsrv-client-plugin-azure-2.0.0-160000.3.1.noarch.rpm cloud-regionsrv-client-plugin-ec2-1.0.5-160000.3.1.noarch.rpm cloud-regionsrv-client-plugin-gce-1.0.0-160000.3.1.noarch.rpm openSUSE-Leap-16.0-3 moderate SUSE SLFO 1.2 This update for python-instance-billing-flavor-check fixes the following issues: - Build fix for SLE 16 and later (bsc#1250110) python-instance-billing-flavor-check-1.0.1-160000.3.1.aarch64.rpm python-instance-billing-flavor-check-1.0.1-160000.3.1.src.rpm openSUSE-Leap-16.0-3 moderate SUSE SLFO 1.2 This update for python-instance-billing-flavor-check fixes the following issues: - Build fix for SLE 16 and later (bsc#1250110) python-instance-billing-flavor-check-1.0.1-160000.3.1.ppc64le.rpm python-instance-billing-flavor-check-1.0.1-160000.3.1.src.rpm openSUSE-Leap-16.0-3 moderate SUSE SLFO 1.2 This update for python-instance-billing-flavor-check fixes the following issues: - Build fix for SLE 16 and later (bsc#1250110) python-instance-billing-flavor-check-1.0.1-160000.3.1.s390x.rpm python-instance-billing-flavor-check-1.0.1-160000.3.1.src.rpm openSUSE-Leap-16.0-3 moderate SUSE SLFO 1.2 This update for python-instance-billing-flavor-check fixes the following issues: - Build fix for SLE 16 and later (bsc#1250110) python-instance-billing-flavor-check-1.0.1-160000.3.1.src.rpm python-instance-billing-flavor-check-1.0.1-160000.3.1.x86_64.rpm openSUSE-Leap-16.0-2 moderate SUSE SLFO 1.2 This update for flake-pilot fixes the following issues: Update version to 3.1.22. - Fixes to use flakes as normal user Running a flake is a container based instance provisioning and startup. Some part of this process requires root permissions for example mounting the container instance store for the provisioning step. This commit fixes the required calls to be properly managed by sudo. - seed from entropy - Fix assignment of random sequence number We should use a seed for the sequence as described in https://rust-random.github.io/book/guide-seeding.html#a-simple-number In addition the logic when a random sequence number should be used was wrong and needed a fix regarding resume and attach type flakes which must not use a random sequence - Pass --init option for resume type flakes In resume mode a sleep command is used to keep the container open. However, without the --init option there is no signal handling available. This commit fixes it - Revert "kill prior remove when using %remove flag" This reverts commit 06c7d4aa71f74865dfecba399fd08cc2fde2e1f2. no hard killing needed with the event loop entrypoint - Fixed CVE-2025-55159 slab: incorrect bounds check Update to slab 0.4.11 to fix the mentioned CVE. This Fixes bsc#1248004 - Apply clippy fixes - Create sequence number for the same invocation If a flake which is not a resume or attach flake is called twice with the same invocation arguments an error message is displayed to give this invocation a new name via the @NAME runtime option. This commit makes this more comfortable and automatically assigns a random sequence number for the call if no @NAME is given. - kill prior remove when using %remove flag In case the container instance should be removed via the %remove flag, send a kill first, followed by a force remove. The reason for this is because we use a never ending sleep command as entry point for resume type containers. If they should be removed the standard signal send on podman rm will not stop the sleep and after a period of 10 seconds podman sends a kill signal itself. We can speedup this process as we know the entry point command and send the kill signal first followed by the remove which saves us some wait time spent in podman otherwise. - Fix clippy hints variables can be used directly in the format! string - Prune old images after load Make sure no <none> image references stay in the registry flake-pilot-3.1.22-160000.1.1.aarch64.rpm flake-pilot-3.1.22-160000.1.1.src.rpm flake-pilot-debuginfo-3.1.22-160000.1.1.aarch64.rpm flake-pilot-firecracker-3.1.22-160000.1.1.aarch64.rpm flake-pilot-firecracker-debuginfo-3.1.22-160000.1.1.aarch64.rpm flake-pilot-firecracker-dracut-netstart-3.1.22-160000.1.1.noarch.rpm flake-pilot-firecracker-guestvm-tools-3.1.22-160000.1.1.aarch64.rpm flake-pilot-firecracker-guestvm-tools-debuginfo-3.1.22-160000.1.1.aarch64.rpm flake-pilot-podman-3.1.22-160000.1.1.aarch64.rpm openSUSE-Leap-16.0-2 moderate SUSE SLFO 1.2 This update for flake-pilot fixes the following issues: Update version to 3.1.22. - Fixes to use flakes as normal user Running a flake is a container based instance provisioning and startup. Some part of this process requires root permissions for example mounting the container instance store for the provisioning step. This commit fixes the required calls to be properly managed by sudo. - seed from entropy - Fix assignment of random sequence number We should use a seed for the sequence as described in https://rust-random.github.io/book/guide-seeding.html#a-simple-number In addition the logic when a random sequence number should be used was wrong and needed a fix regarding resume and attach type flakes which must not use a random sequence - Pass --init option for resume type flakes In resume mode a sleep command is used to keep the container open. However, without the --init option there is no signal handling available. This commit fixes it - Revert "kill prior remove when using %remove flag" This reverts commit 06c7d4aa71f74865dfecba399fd08cc2fde2e1f2. no hard killing needed with the event loop entrypoint - Fixed CVE-2025-55159 slab: incorrect bounds check Update to slab 0.4.11 to fix the mentioned CVE. This Fixes bsc#1248004 - Apply clippy fixes - Create sequence number for the same invocation If a flake which is not a resume or attach flake is called twice with the same invocation arguments an error message is displayed to give this invocation a new name via the @NAME runtime option. This commit makes this more comfortable and automatically assigns a random sequence number for the call if no @NAME is given. - kill prior remove when using %remove flag In case the container instance should be removed via the %remove flag, send a kill first, followed by a force remove. The reason for this is because we use a never ending sleep command as entry point for resume type containers. If they should be removed the standard signal send on podman rm will not stop the sleep and after a period of 10 seconds podman sends a kill signal itself. We can speedup this process as we know the entry point command and send the kill signal first followed by the remove which saves us some wait time spent in podman otherwise. - Fix clippy hints variables can be used directly in the format! string - Prune old images after load Make sure no <none> image references stay in the registry flake-pilot-3.1.22-160000.1.1.ppc64le.rpm flake-pilot-3.1.22-160000.1.1.src.rpm flake-pilot-firecracker-3.1.22-160000.1.1.ppc64le.rpm flake-pilot-firecracker-dracut-netstart-3.1.22-160000.1.1.noarch.rpm flake-pilot-firecracker-guestvm-tools-3.1.22-160000.1.1.ppc64le.rpm flake-pilot-podman-3.1.22-160000.1.1.ppc64le.rpm openSUSE-Leap-16.0-2 moderate SUSE SLFO 1.2 This update for flake-pilot fixes the following issues: Update version to 3.1.22. - Fixes to use flakes as normal user Running a flake is a container based instance provisioning and startup. Some part of this process requires root permissions for example mounting the container instance store for the provisioning step. This commit fixes the required calls to be properly managed by sudo. - seed from entropy - Fix assignment of random sequence number We should use a seed for the sequence as described in https://rust-random.github.io/book/guide-seeding.html#a-simple-number In addition the logic when a random sequence number should be used was wrong and needed a fix regarding resume and attach type flakes which must not use a random sequence - Pass --init option for resume type flakes In resume mode a sleep command is used to keep the container open. However, without the --init option there is no signal handling available. This commit fixes it - Revert "kill prior remove when using %remove flag" This reverts commit 06c7d4aa71f74865dfecba399fd08cc2fde2e1f2. no hard killing needed with the event loop entrypoint - Fixed CVE-2025-55159 slab: incorrect bounds check Update to slab 0.4.11 to fix the mentioned CVE. This Fixes bsc#1248004 - Apply clippy fixes - Create sequence number for the same invocation If a flake which is not a resume or attach flake is called twice with the same invocation arguments an error message is displayed to give this invocation a new name via the @NAME runtime option. This commit makes this more comfortable and automatically assigns a random sequence number for the call if no @NAME is given. - kill prior remove when using %remove flag In case the container instance should be removed via the %remove flag, send a kill first, followed by a force remove. The reason for this is because we use a never ending sleep command as entry point for resume type containers. If they should be removed the standard signal send on podman rm will not stop the sleep and after a period of 10 seconds podman sends a kill signal itself. We can speedup this process as we know the entry point command and send the kill signal first followed by the remove which saves us some wait time spent in podman otherwise. - Fix clippy hints variables can be used directly in the format! string - Prune old images after load Make sure no <none> image references stay in the registry flake-pilot-3.1.22-160000.1.1.s390x.rpm flake-pilot-3.1.22-160000.1.1.src.rpm flake-pilot-debuginfo-3.1.22-160000.1.1.s390x.rpm flake-pilot-firecracker-3.1.22-160000.1.1.s390x.rpm flake-pilot-firecracker-debuginfo-3.1.22-160000.1.1.s390x.rpm flake-pilot-firecracker-dracut-netstart-3.1.22-160000.1.1.noarch.rpm flake-pilot-firecracker-guestvm-tools-3.1.22-160000.1.1.s390x.rpm flake-pilot-firecracker-guestvm-tools-debuginfo-3.1.22-160000.1.1.s390x.rpm flake-pilot-podman-3.1.22-160000.1.1.s390x.rpm openSUSE-Leap-16.0-2 moderate SUSE SLFO 1.2 This update for flake-pilot fixes the following issues: Update version to 3.1.22. - Fixes to use flakes as normal user Running a flake is a container based instance provisioning and startup. Some part of this process requires root permissions for example mounting the container instance store for the provisioning step. This commit fixes the required calls to be properly managed by sudo. - seed from entropy - Fix assignment of random sequence number We should use a seed for the sequence as described in https://rust-random.github.io/book/guide-seeding.html#a-simple-number In addition the logic when a random sequence number should be used was wrong and needed a fix regarding resume and attach type flakes which must not use a random sequence - Pass --init option for resume type flakes In resume mode a sleep command is used to keep the container open. However, without the --init option there is no signal handling available. This commit fixes it - Revert "kill prior remove when using %remove flag" This reverts commit 06c7d4aa71f74865dfecba399fd08cc2fde2e1f2. no hard killing needed with the event loop entrypoint - Fixed CVE-2025-55159 slab: incorrect bounds check Update to slab 0.4.11 to fix the mentioned CVE. This Fixes bsc#1248004 - Apply clippy fixes - Create sequence number for the same invocation If a flake which is not a resume or attach flake is called twice with the same invocation arguments an error message is displayed to give this invocation a new name via the @NAME runtime option. This commit makes this more comfortable and automatically assigns a random sequence number for the call if no @NAME is given. - kill prior remove when using %remove flag In case the container instance should be removed via the %remove flag, send a kill first, followed by a force remove. The reason for this is because we use a never ending sleep command as entry point for resume type containers. If they should be removed the standard signal send on podman rm will not stop the sleep and after a period of 10 seconds podman sends a kill signal itself. We can speedup this process as we know the entry point command and send the kill signal first followed by the remove which saves us some wait time spent in podman otherwise. - Fix clippy hints variables can be used directly in the format! string - Prune old images after load Make sure no <none> image references stay in the registry flake-pilot-3.1.22-160000.1.1.src.rpm flake-pilot-3.1.22-160000.1.1.x86_64.rpm flake-pilot-debuginfo-3.1.22-160000.1.1.x86_64.rpm flake-pilot-firecracker-3.1.22-160000.1.1.x86_64.rpm flake-pilot-firecracker-debuginfo-3.1.22-160000.1.1.x86_64.rpm flake-pilot-firecracker-dracut-netstart-3.1.22-160000.1.1.noarch.rpm flake-pilot-firecracker-guestvm-tools-3.1.22-160000.1.1.x86_64.rpm flake-pilot-firecracker-guestvm-tools-debuginfo-3.1.22-160000.1.1.x86_64.rpm flake-pilot-podman-3.1.22-160000.1.1.x86_64.rpm openSUSE-Leap-16.0-packagehub-1 critical openSUSE Backports SLE-16.0 This update for chromium fixes the following issues: Chromium 141.0.7390.76: * Do not send URLs as AIM input. This is to resolve a privacy concern, around passing urls to AI Mode. Chromium 141.0.7390.65 (boo#1251334): * CVE-2025-11458: Heap buffer overflow in Sync * CVE-2025-11460: Use after free in Storage * CVE-2025-11211: Out of bounds read in WebCodecs Chromium 141.0.7390.54 (stable released 2025-09-30) (boo#1250780) * CVE-2025-11205: Heap buffer overflow in WebGPU * CVE-2025-11206: Heap buffer overflow in Video * CVE-2025-11207: Side-channel information leakage in Storage * CVE-2025-11208: Inappropriate implementation in Media * CVE-2025-11209: Inappropriate implementation in Omnibox * CVE-2025-11210: Side-channel information leakage in Tab * CVE-2025-11211: Out of bounds read in Media * CVE-2025-11212: Inappropriate implementation in Media * CVE-2025-11213: Inappropriate implementation in Omnibox * CVE-2025-11215: Off by one error in V8 * CVE-2025-11216: Inappropriate implementation in Storage * CVE-2025-11219: Use after free in V8 * Various fixes from internal audits, fuzzing and other initiatives Chromium 141.0.7390.37 (beta released 2025-09-24) Chromium 140.0.7339.207 (boo#1250472) * CVE-2025-10890: Side-channel information leakage in V8 * CVE-2025-10891: Integer overflow in V8 * CVE-2025-10892: Integer overflow in V8 chromedriver-141.0.7390.76-bp160.1.1.aarch64.rpm chromium-141.0.7390.76-bp160.1.1.aarch64.rpm chromium-141.0.7390.76-bp160.1.1.nosrc.rpm openSUSE-Leap-16.0-packagehub-1 critical openSUSE Backports SLE-16.0 This update for chromium fixes the following issues: Chromium 141.0.7390.76: * Do not send URLs as AIM input. This is to resolve a privacy concern, around passing urls to AI Mode. Chromium 141.0.7390.65 (boo#1251334): * CVE-2025-11458: Heap buffer overflow in Sync * CVE-2025-11460: Use after free in Storage * CVE-2025-11211: Out of bounds read in WebCodecs Chromium 141.0.7390.54 (stable released 2025-09-30) (boo#1250780) * CVE-2025-11205: Heap buffer overflow in WebGPU * CVE-2025-11206: Heap buffer overflow in Video * CVE-2025-11207: Side-channel information leakage in Storage * CVE-2025-11208: Inappropriate implementation in Media * CVE-2025-11209: Inappropriate implementation in Omnibox * CVE-2025-11210: Side-channel information leakage in Tab * CVE-2025-11211: Out of bounds read in Media * CVE-2025-11212: Inappropriate implementation in Media * CVE-2025-11213: Inappropriate implementation in Omnibox * CVE-2025-11215: Off by one error in V8 * CVE-2025-11216: Inappropriate implementation in Storage * CVE-2025-11219: Use after free in V8 * Various fixes from internal audits, fuzzing and other initiatives Chromium 141.0.7390.37 (beta released 2025-09-24) Chromium 140.0.7339.207 (boo#1250472) * CVE-2025-10890: Side-channel information leakage in V8 * CVE-2025-10891: Integer overflow in V8 * CVE-2025-10892: Integer overflow in V8 chromedriver-141.0.7390.76-bp160.1.1.ppc64le.rpm chromium-141.0.7390.76-bp160.1.1.nosrc.rpm chromium-141.0.7390.76-bp160.1.1.ppc64le.rpm openSUSE-Leap-16.0-packagehub-1 critical openSUSE Backports SLE-16.0 This update for chromium fixes the following issues: Chromium 141.0.7390.76: * Do not send URLs as AIM input. This is to resolve a privacy concern, around passing urls to AI Mode. Chromium 141.0.7390.65 (boo#1251334): * CVE-2025-11458: Heap buffer overflow in Sync * CVE-2025-11460: Use after free in Storage * CVE-2025-11211: Out of bounds read in WebCodecs Chromium 141.0.7390.54 (stable released 2025-09-30) (boo#1250780) * CVE-2025-11205: Heap buffer overflow in WebGPU * CVE-2025-11206: Heap buffer overflow in Video * CVE-2025-11207: Side-channel information leakage in Storage * CVE-2025-11208: Inappropriate implementation in Media * CVE-2025-11209: Inappropriate implementation in Omnibox * CVE-2025-11210: Side-channel information leakage in Tab * CVE-2025-11211: Out of bounds read in Media * CVE-2025-11212: Inappropriate implementation in Media * CVE-2025-11213: Inappropriate implementation in Omnibox * CVE-2025-11215: Off by one error in V8 * CVE-2025-11216: Inappropriate implementation in Storage * CVE-2025-11219: Use after free in V8 * Various fixes from internal audits, fuzzing and other initiatives Chromium 141.0.7390.37 (beta released 2025-09-24) Chromium 140.0.7339.207 (boo#1250472) * CVE-2025-10890: Side-channel information leakage in V8 * CVE-2025-10891: Integer overflow in V8 * CVE-2025-10892: Integer overflow in V8 chromedriver-141.0.7390.76-bp160.1.1.x86_64.rpm chromium-141.0.7390.76-bp160.1.1.nosrc.rpm chromium-141.0.7390.76-bp160.1.1.x86_64.rpm openSUSE-Leap-16.0-packagehub-3 moderate openSUSE Backports SLE-16.0 This update for chromium fixes the following issues: Chromium 141.0.7390.107: * CVE-2025-11756: Use after free in Safe Browsing (boo#1252013) chromedriver-141.0.7390.107-bp160.1.1.aarch64.rpm chromium-141.0.7390.107-bp160.1.1.aarch64.rpm chromium-141.0.7390.107-bp160.1.1.nosrc.rpm openSUSE-Leap-16.0-packagehub-3 moderate openSUSE Backports SLE-16.0 This update for chromium fixes the following issues: Chromium 141.0.7390.107: * CVE-2025-11756: Use after free in Safe Browsing (boo#1252013) chromedriver-141.0.7390.107-bp160.1.1.ppc64le.rpm chromium-141.0.7390.107-bp160.1.1.nosrc.rpm chromium-141.0.7390.107-bp160.1.1.ppc64le.rpm openSUSE-Leap-16.0-packagehub-3 moderate openSUSE Backports SLE-16.0 This update for chromium fixes the following issues: Chromium 141.0.7390.107: * CVE-2025-11756: Use after free in Safe Browsing (boo#1252013) chromedriver-141.0.7390.107-bp160.1.1.x86_64.rpm chromium-141.0.7390.107-bp160.1.1.nosrc.rpm chromium-141.0.7390.107-bp160.1.1.x86_64.rpm openSUSE-Leap-16.0-packagehub-4 moderate openSUSE Backports SLE-16.0 This update for opi fixes the following issues: - Version 5.8.8 * Fix adding openh264 repo on leap 16.0 This update for opi fixes the following issues: - Version 5.8.7 * Fix ocenaudio url * Add LocalSend plugin * Run all tests in verbose mode * Print written repo files in verbose mode * Increase timeouts in test/06_install_non_interactive.py * Remove DNF references from README.md This update for opi fixes the following issues: - Version 5.8.5 * add librewolf plugin (#205) * Install .NET 9 * Add verbose mode * Change the order of the process in the github module * Add rustdesk plugin This update for opi fixes the following issues: - Version 5.8.4 * Use arm64 rpm for libation on aarch64 This update for opi fixes the following issues: - Version 5.8.3 * Install dependencies rpm-build and squashfs at runtime if needed * Drop DNF support This update for opi fixes the following issues: - Version 5.8.2 * Warn about adding staging repos * Gracefully handle zypper exit code 106 (repos without cache present) This update for opi fixes the following issues: - Version 5.8.1 * Fix SyntaxWarning: invalid escape sequence '\s' This update for opi fixes the following issues: - Version 5.8.0 * Add mullvad-brower This update for opi fixes the following issues: - Version 5.7.0 * Add leap-only plugin to install zellij from github release * Don't use subprocess.run user kwarg on 15.6 * Fix tests: Use helloworld-opi-tests instead of zfs * Perform search despite locked rpmdb * Simplify backend code This update for opi fixes the following issues: - Use no macros in url in .spec for packtrack This update for opi fixes the following issues: - Version 5.6.0 * Add plugin to install vagrant from hashicorp repo This update for opi fixes the following issues: - Version 5.5.0 * Update opi/plugins/collabora.py * add collabora office desktop * Omit unsupported cli args on leap in 99_install_opi.py * Switch to PEP517 install * Fix 09_install_with_multi_repos_in_single_file_non_interactive.py * Fix 07_install_multiple.py on tumbleweed * Fix test suite on tumbleweed * Update available apps in opi - README.md This update for opi fixes the following issues: - Version 5.4.0 * Show key ID when importing or deleting package signing keys * Add option to install google-chrome-canary This update for opi fixes the following issues: - Version 5.3.0 * Fix tests for new zypper version * fix doblue slash in packman repo url * Add Plugin to install Libation opi-5.8.8-bp160.1.1.noarch.rpm opi-5.8.8-bp160.1.1.src.rpm openSUSE-Leap-16.0-packagehub-5 moderate openSUSE Backports SLE-16.0 This update for virtme fixes the following issues: - Update to 1.38: * Fix the infamous Stale file handle (ESTALE) errors with virtiofsd * Fix for systemctl daemon-reload when systemd support is enabled * Fix for a kernel symlink issue affecting openSUSE/SLE * README/docs improvements * Various coding style cleanups virtme-1.38-bp160.1.1.noarch.rpm virtme-1.38-bp160.1.1.src.rpm openSUSE-Leap-16.0-packagehub-6 moderate openSUSE Backports SLE-16.0 This update for lutris fixes the following issues: - Move selinux dependency - Fix gaming under selinux (bsc#1206292) - Fix wrong placement of lang_package macro in spec file - Update to 0.5.19: * Fix Proton integration bugs so Proton-fixes are applied * Do not offer DXVK, VKD3D, D3D Extras or DDXVK-NVAPI on Proton versions; Proton will handle these. * The "Enable Esync" and "Enable Fsync" settings are now passed on to Proton * DXVK's integrated D8VK will be enabled in Proton * Emulator BIOS file location (used by libretro) may be set in Preferences * Obtain the release year from GOG and Itch.io. * MAME Machine setting uses a searchable entry for its enourmous list * Support for importing Commodore 64 ROMs - Add BuildRequires apparmor-abstractions, apparmor-rpm-macros for Leap, fix for build error: directories not owned by a package: /etc/apparmor.d - update to 0.5.18: * Lutris downloads the latest GE-Proton build for Wine if any Wine version is installed * Use dark theme by default * Display cover-art rather than banners by default * Add 'Uncategorized' view to sidebar * Preference options that do not work on Wayland will be hidden when on Wayland * Game searches can now use fancy tags like 'installed:yes' or 'source:gog', with explanatory tool-tip * A new filter button on the search box can build many of these fancy tags for you * Runner searches can use 'installed:yes' as well, but no other fancy searches or anything * Updated the Flathub and Amazon source to new APIs, restoring integration * Itch.io source integration will load a collection named 'Lutris' if present * GOG and Itch.io sources can now offer Linux and Windows installers for the same game * Added support for the 'foot' terminal * Support for DirectX 8 in DXVK v2.4 * Support for Ayatana Application Indicators * Additional options for Ruffle runner * Updated download links for the Atari800 and MicroM8 runners * No longer re-download cached installation files even when some are missing * Lutris log is included in the 'System' tab of the Preferences window * Improved error reporting, with the Lutris log included in the error details * Add AppArmor profile for Ubuntu versions >= 23.10 * Add Duckstation runner lutris-0.5.19-bp160.1.1.noarch.rpm lutris-0.5.19-bp160.1.1.src.rpm lutris-apparmor-0.5.19-bp160.1.1.noarch.rpm lutris-lang-0.5.19-bp160.1.1.noarch.rpm openSUSE-Leap-16.0-packagehub-8 moderate openSUSE Backports SLE-16.0 This update for chromium fixes the following issues: Chromium 141.0.7390.122: * CVE-2025-12036: Inappropriate implementation in V8 (boo#1252402) chromedriver-141.0.7390.122-bp160.1.1.aarch64.rpm chromium-141.0.7390.122-bp160.1.1.aarch64.rpm chromium-141.0.7390.122-bp160.1.1.nosrc.rpm openSUSE-Leap-16.0-packagehub-8 moderate openSUSE Backports SLE-16.0 This update for chromium fixes the following issues: Chromium 141.0.7390.122: * CVE-2025-12036: Inappropriate implementation in V8 (boo#1252402) chromedriver-141.0.7390.122-bp160.1.1.ppc64le.rpm chromium-141.0.7390.122-bp160.1.1.nosrc.rpm chromium-141.0.7390.122-bp160.1.1.ppc64le.rpm openSUSE-Leap-16.0-packagehub-8 moderate openSUSE Backports SLE-16.0 This update for chromium fixes the following issues: Chromium 141.0.7390.122: * CVE-2025-12036: Inappropriate implementation in V8 (boo#1252402) chromedriver-141.0.7390.122-bp160.1.1.x86_64.rpm chromium-141.0.7390.122-bp160.1.1.nosrc.rpm chromium-141.0.7390.122-bp160.1.1.x86_64.rpm openSUSE-Leap-16.0-packagehub-7 important openSUSE Backports SLE-16.0 This update for warewulf4 fixes the following issues: Changes in warewulf4: - Update to version 4.6.4: * v4.6.4 release updates * Convert disk booleans from wwbool to *bool which allows bools in disk to be set to false via command line (bsc#1248768) * Update NetworkManager Overlay * Disable ipv4 in NetworkManager if no address or route is specified * fix(wwctl): Create overlay edit tempfile in tmpdir * Add default for systemd name for warewulf in warewulf.conf * Atomic overlay file application in wwclient * Simpler names for overlay methods * Fix warewulfd api behavior when deleting distribution overlay - Update to version 4.6.3: * v4.6.3 release * IPv6 iPXE support * Fix a syntax error in the RPM specfile * Fix a race condition in wwctl overlay edit * Fixed handling of comma-separated mount options in `fstab` and `ignition` overlays * Move reexec.Init() to beginning of wwctl * Add documentation for using tmpfs to distribute across numa nodes * added warewuld configure option * Fix wwctl upgrade nodes to handle kernel argument lists (bsc#1227686 bsc#1227465) * Address copilot review from #1945 * Refactor wwapi tests for proper isolation * Bugfix: cloning a site overlay when parent dir does not exist * Clone to a site overlay when adding files in wwapi * Consolidated createOverlayFile and updateOverlayFile to addOverlayFile * Support for creating and updating overlay file in wwapi * Only return overlay files that refer to a path within the overlay * add overlay file deletion support * DELETE /api/overlays/{id}?force=true can delete overlays in use * Restore idempotency of PUT /api/nodes/{id} * Simplify overlay mtime api and add tests * add node overlay buildtime * Improved netplan support * Rebuild overlays for discovered nodes * Restrict userdocs from building during pr when not modified * Update to v4.6.2 GitHub release notes warewulf4-4.6.4-bp160.1.1.aarch64.rpm warewulf4-4.6.4-bp160.1.1.src.rpm warewulf4-debuginfo-4.6.4-bp160.1.1.aarch64.rpm warewulf4-dracut-4.6.4-bp160.1.1.noarch.rpm warewulf4-man-4.6.4-bp160.1.1.noarch.rpm warewulf4-overlay-4.6.4-bp160.1.1.aarch64.rpm warewulf4-overlay-debuginfo-4.6.4-bp160.1.1.aarch64.rpm warewulf4-overlay-rke2-4.6.4-bp160.1.1.noarch.rpm warewulf4-overlay-slurm-4.6.4-bp160.1.1.noarch.rpm warewulf4-reference-doc-4.6.4-bp160.1.1.noarch.rpm openSUSE-Leap-16.0-packagehub-7 important openSUSE Backports SLE-16.0 This update for warewulf4 fixes the following issues: Changes in warewulf4: - Update to version 4.6.4: * v4.6.4 release updates * Convert disk booleans from wwbool to *bool which allows bools in disk to be set to false via command line (bsc#1248768) * Update NetworkManager Overlay * Disable ipv4 in NetworkManager if no address or route is specified * fix(wwctl): Create overlay edit tempfile in tmpdir * Add default for systemd name for warewulf in warewulf.conf * Atomic overlay file application in wwclient * Simpler names for overlay methods * Fix warewulfd api behavior when deleting distribution overlay - Update to version 4.6.3: * v4.6.3 release * IPv6 iPXE support * Fix a syntax error in the RPM specfile * Fix a race condition in wwctl overlay edit * Fixed handling of comma-separated mount options in `fstab` and `ignition` overlays * Move reexec.Init() to beginning of wwctl * Add documentation for using tmpfs to distribute across numa nodes * added warewuld configure option * Fix wwctl upgrade nodes to handle kernel argument lists (bsc#1227686 bsc#1227465) * Address copilot review from #1945 * Refactor wwapi tests for proper isolation * Bugfix: cloning a site overlay when parent dir does not exist * Clone to a site overlay when adding files in wwapi * Consolidated createOverlayFile and updateOverlayFile to addOverlayFile * Support for creating and updating overlay file in wwapi * Only return overlay files that refer to a path within the overlay * add overlay file deletion support * DELETE /api/overlays/{id}?force=true can delete overlays in use * Restore idempotency of PUT /api/nodes/{id} * Simplify overlay mtime api and add tests * add node overlay buildtime * Improved netplan support * Rebuild overlays for discovered nodes * Restrict userdocs from building during pr when not modified * Update to v4.6.2 GitHub release notes warewulf4-4.6.4-bp160.1.1.src.rpm warewulf4-4.6.4-bp160.1.1.x86_64.rpm warewulf4-debuginfo-4.6.4-bp160.1.1.x86_64.rpm warewulf4-dracut-4.6.4-bp160.1.1.noarch.rpm warewulf4-man-4.6.4-bp160.1.1.noarch.rpm warewulf4-overlay-4.6.4-bp160.1.1.x86_64.rpm warewulf4-overlay-debuginfo-4.6.4-bp160.1.1.x86_64.rpm warewulf4-overlay-rke2-4.6.4-bp160.1.1.noarch.rpm warewulf4-overlay-slurm-4.6.4-bp160.1.1.noarch.rpm warewulf4-reference-doc-4.6.4-bp160.1.1.noarch.rpm openSUSE-Leap-16.0-packagehub-9 moderate openSUSE Backports SLE-16.0 This update ships fprintd 1.94.4 to openSUSE Leap 16.0 and SLES Package Hub 16.0 fprintd-1.94.4-bp160.1.1.aarch64.rpm fprintd-1.94.4-bp160.1.1.src.rpm fprintd-debuginfo-1.94.4-bp160.1.1.aarch64.rpm fprintd-debugsource-1.94.4-bp160.1.1.aarch64.rpm fprintd-devel-1.94.4-bp160.1.1.noarch.rpm fprintd-doc-1.94.4-bp160.1.1.noarch.rpm fprintd-lang-1.94.4-bp160.1.1.noarch.rpm fprintd-pam-1.94.4-bp160.1.1.aarch64.rpm fprintd-pam-debuginfo-1.94.4-bp160.1.1.aarch64.rpm openSUSE-Leap-16.0-packagehub-9 moderate openSUSE Backports SLE-16.0 This update ships fprintd 1.94.4 to openSUSE Leap 16.0 and SLES Package Hub 16.0 fprintd-1.94.4-bp160.1.1.ppc64le.rpm fprintd-1.94.4-bp160.1.1.src.rpm fprintd-debuginfo-1.94.4-bp160.1.1.ppc64le.rpm fprintd-debugsource-1.94.4-bp160.1.1.ppc64le.rpm fprintd-devel-1.94.4-bp160.1.1.noarch.rpm fprintd-doc-1.94.4-bp160.1.1.noarch.rpm fprintd-lang-1.94.4-bp160.1.1.noarch.rpm fprintd-pam-1.94.4-bp160.1.1.ppc64le.rpm fprintd-pam-debuginfo-1.94.4-bp160.1.1.ppc64le.rpm openSUSE-Leap-16.0-packagehub-9 moderate openSUSE Backports SLE-16.0 This update ships fprintd 1.94.4 to openSUSE Leap 16.0 and SLES Package Hub 16.0 fprintd-1.94.4-bp160.1.1.src.rpm fprintd-1.94.4-bp160.1.1.x86_64.rpm fprintd-debuginfo-1.94.4-bp160.1.1.x86_64.rpm fprintd-debugsource-1.94.4-bp160.1.1.x86_64.rpm fprintd-devel-1.94.4-bp160.1.1.noarch.rpm fprintd-doc-1.94.4-bp160.1.1.noarch.rpm fprintd-lang-1.94.4-bp160.1.1.noarch.rpm fprintd-pam-1.94.4-bp160.1.1.x86_64.rpm fprintd-pam-debuginfo-1.94.4-bp160.1.1.x86_64.rpm