[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-96ee75b9fe chromium-121.0.6167.160-1.el7 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-4a6bba707d libmodsecurity-3.0.12-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing netdata-1.44.3-1.el7 rpki-client-8.9-1.el7 stb-0-0.41.20240213gitae721c5.el7 Details about builds: netdata-1.44.3-1.el7 (FEDORA-EPEL-2024-8fd5ec2725) Real-time performance monitoring Update Information: Update from upstream Update from upstream ChangeLog: * Mon Feb 12 2024 Didier Fabert 1.44.3-1 - Update from upstream * Thu Feb 8 2024 Didier Fabert 1.44.2-1 - Update from upstream * Thu Jan 25 2024 Fedora Release Engineering - 1.44.1-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild * Sun Jan 21 2024 Fedora Release Engineering - 1.44.1-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild References: [ 1 ] Bug #2263063 - netdata-1.44.2 is available https://bugzilla.redhat.com/show_bug.cgi?id=2263063 rpki-client-8.9-1.el7 (FEDORA-EPEL-2024-92b39d4109) OpenBSD RPKI validator to support BGP Origin Validation Update Information: rpki-client 8.9 The handling of manifests fetched via rsync or RRDP was reworked to fully conform to RFC 9286. The issuance date and manifest number of the purported new manifest file must have been increased, otherwise the cached version is used. As a consequence of the above changes, some warnings for .mft files were reworded. The notion of a stale manifest is no longer used. The following counters will be removed in rpki-client 9.0: The stalemanifest counter in JSON output. The "stale" state for manifest objects in Open Metrics output. A race condition between closing an idle connection and scheduling a new request on it could trigger an assert in rare circumstances. The evaluation time specified with -P now also applies to trust anchor certificates. Check that the entire CMS eContent was consumed. Previously, trailing data would be silently discarded on deserialization of products. In file mode do not consider overclaiming intermediate CA certificates as invalid. A warning is still issued. Print the revocation time of certificates in file mode. Be more careful when converting OpenSSL numeric identifiers (NIDs) to strings. ChangeLog: * Tue Feb 13 2024 Robert Scheck 8.9-1 - Upgrade to 8.9 (#2264085) * Fri Jan 26 2024 Fedora Release Engineering - 8.8-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild * Mon Jan 22 2024 Fedora Release Engineering - 8.8-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild References: [ 1 ] Bug #2264085 - rpki-client-8.9 is available https://bugzilla.redhat.com/show_bug.cgi?id=2264085 stb-0-0.41.20240213gitae721c5.el7 (FEDORA-EPEL-2024-dc7641d7b3) Single-file public domain libraries for C/C++ Update Information: Update to 0^20240213gitae721c5 stb_image-devel is updated to 2.29, with various bugfixes and enhancements stb_image_resize2-devel is updated to 2.06: fix for 2 pixel to 1 pixel resizes with wrap; fix for output callback; fix for rare AVX bug, shadowed symbol; ASAN and TSAN warnings fixed, minor tweaks; and fix for identical width/height 3x or more down-scaling undersampling a single row on rare resize ratios (about 1%) ChangeLog: * Tue Feb 13 2024 Benjamin A. Beasley - 0-0.41.20240213gitae721c5 - Update to 0^20240213gitae721c5 - stb_image_resize2-devel is updated to 2.06 * Tue Feb 13 2024 Benjamin A. Beasley - 0-0.40.20240208gitb7cf124 - Update to 0^20240208gitb7cf124 - stb_image-devel is updated to 2.29 - stb_image_resize2-devel is updated to 2.05 -- ___ epel-devel mailing list --
[EPEL-devel] Incompatible Upgrade of singularity-ce in EPEL 7 / 8 / 9
After approval in the last EPEL meeting [1], I have submitted an incompatible upgrade of singularity-ce to testing for EPEL 7, 8 & 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-cbd86d2020 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-f299fbc570 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-05e20edbbf These updates upgrade singularity-ce from v3.11.5 to v4.1.1. The following incompatibilities should be noted by users: 1) Some functionality previously provided by the `singularity remote` command is split into new `singularity registry` and `singularity keyserver` commands. 2) The `singularity remote add` command now sets a newly added remote as the default (unless suppressed). Previously the user had to set the default remote manually. 3) The deprecated and unmaintained `—vm` flag to start singularity inside a Virtual Machine has been removed. 4) Bind mounts are now performed in the order in which they are specified. Previously, image based bind mounts were performed before others. 5) Current working directory on the host is now created in the container, restoring a behaviour from Singularity <3.6.0 unless suppressed. 6) If the current directory paths on the container and host contains symlinks to different locations, the current working directory is not mounted. Changes 1,2,3 are expected to have minimal impact, and 4,5,6 are likely to be considered bug fixes by many users. No changes are required to existing configuration files for this update. A complete description of changes and additions between v3.11 and v4.1.1 is available in the upstream documentation at https://sylabs.io/docs/ In the absence of any issues, the updates will be pushed to stable after a one week testing period has passed, with a follow-up notification here. Cheers, David Trudgian [1] https://pagure.io/epel/issue/265#comment-894790 -- ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[EPEL-devel] [Fedocal] Reminder meeting : EPEL Steering Committee
Dear all, You are kindly invited to the meeting: EPEL Steering Committee on 2024-02-14 from 18:00:00 to 19:00:00 UTC At fedora-meet...@chat.fedoraproject.org The meeting will be about: https://chat.fedoraproject.org/#/room/#meeting:fedoraproject.org This is the weekly EPEL Steering Committee Meeting. A general agenda is the following: #topic aloha #topic EPEL Issues https://pagure.io/epel/issues * https://pagure.io/epel/issues?tags=meeting=Open #topic Old Business (if needed) #topic General Issues / Open Floor Source: https://calendar.fedoraproject.org//meeting/10727/ -- ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
