[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-242bfc4463 cacti-1.2.19-1.el8 cacti-spine-1.2.19-1.el8 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-f89c59b568 botan2-2.12.1-4.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing NetworkManager-strongswan-1.5.2-1.el8 dkms-3.0.0-1.el8 python-resultsdb_api-2.1.4-1.el8 Details about builds: NetworkManager-strongswan-1.5.2-1.el8 (FEDORA-EPEL-2021-6cb990c547) NetworkManager strongSwan IPSec VPN plug-in Update Information: NetworkManager user interface for strongswan configuration. - note: It does not work well on SELinux in enforcing mode, if certificates are stored in home. Visit [bug](https://bugzilla.redhat.com/show_bug.cgi?id=1662050) for details. ChangeLog: dkms-3.0.0-1.el8 (FEDORA-EPEL-2021-bdd50a8079) Dynamic Kernel Module Support Framework Update Information: Update to 3.0.0, major cleanup and refactor. Solves the issues of kernel modules disappearing if *both* an updated DKMS module package and a new kernel are in the same YUM/DNF transaction. ChangeLog: * Mon Nov 8 2021 Simone Caronni - 3.0.0-1 - Update to 3.0.0. * Sat Oct 30 2021 Simone Caronni - 2.8.8-1 - Update to 2.8.8. * Fri Oct 1 2021 Simone Caronni - 2.8.7-1 - Update to 2.8.7. References: [ 1 ] Bug #2018763 - dkms-2.8.8 is available https://bugzilla.redhat.com/show_bug.cgi?id=2018763 python-resultsdb_api-2.1.4-1.el8 (FEDORA-EPEL-2021-40fd5acf2f) Interface api to ResultsDB Update Information: - add auth class with basic http auth support ChangeLog: ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] ansible 2.9.x EOL - 2022-05-23
Greetings. Upstream ansible has announced that they intend to EOL ansible 2.9.x on May 23rd, 2022. I intend to likewise retire the epel7 and epel8 ansible-2.9.x packages at that time. See the upstream announcement at: https://groups.google.com/g/ansible-devel/c/rx-fnf1L5e8/m/r0_UumLMBgAJ ansible-core will be available in centos stream 8/9 and rhel8/9 soon. The ansible upstream distribution (ansible-core + many many collections) will be available for Fedora soon ( https://fedoraproject.org/wiki/Changes/Ansible5 ). Once that packaging work is done we will see about also adding it to epel8/9. Users using EL7 for a control host should look at moving to EL8 before ansible 2.9 goes EOL. Thanks, kevin signature.asc Description: PGP signature ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] fluidsynth-2.1.8-4.el7 available for EPEL7
Hello! fluidsynth-2.1.8-4.el7 is now in stable for EPEL7. Best Regards Christoph ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] IRC Announcement
Since its beginnings, the Fedora Project has used the freenode IRC network for our project communications. Due to a variety of recent changes to that network, the Fedora Project is moving our IRC communications to Libera.Chat. If you are a current IRC user, please go and register your nick(s) on Libera.Chat ( https://libera.chat/guides/registration#registering ) and rejoin the #fedora related channels you wish to. You can take this opportunity to choose a new secure password and make sure you are connecting via SSL. There is good documentation about choosing an IRC client at https://libera.chat/guides/clients If you are a Matrix user, we ask for your patience as we get bridges setup on the new network. If you were joined to rooms via the generic freenode bridge, you will need to leave them and rejoin the fedora rooms in matrix (which will be plumbed with the Libera channels) As of 2021-05-28 our official IRC presence is on irc.libera.chat. Many Fedora channels have moved over and are ready on Libera.Chat. However, less-used channels have not be automatically setup. If you need a specific #fedora-* IRC channel setup, please file a ticket at http://pagure.io/irc requesting the channel. New channels should have the same name as they did on freenode. For example: #fedora, #fedora-admin, #fedora-devel, and #fedora-join. If you would like a fedora IRC ‘cloak’ you can request it at: https://fedoraproject.org/wiki/LiberaCloaks (an IRC cloak obfuscates your client host address and shows ‘fedora’ instead). Please note that cloaks are not foolproof, there are ways for people to still get your IP, but they do make it more difficult for people to obtain your IP. Also, look for upcoming exciting announcements around Fedora’s Matrix presence. nb ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: Plan for EPEL-9
On Mon, Nov 8, 2021 at 3:31 AM Neal Gompa wrote: > On Mon, Nov 8, 2021 at 2:18 AM Remi Collet > wrote: > > > > As both RHEL-9 Beta and CentOS 9 Stream are available, > > what are the plan for EPEL-9 ? > > > > > > I really this should be available ASAP to be > > available to our users at GA time. > > EPEL 9 Next for CentOS Stream 9 is blocked on the migration of our > s390x systems to z15[1], because currently all s390x builds fail[2]. > Once that's taken care of, we'll launch EPEL 9 Next. > > [1]: https://pagure.io/fedora-infrastructure/issue/10302 > [2]: https://pagure.io/releng/issue/10360 > > Our current goal to have epel9-next completely available for maintainers/developers is December 1st. Basically one month after RHEL 9 beta was released. We are hoping to have it available earlier, but as Neal pointed out, we've got a (known) blocker with the build platform. And it's possible that once that get's fixed there might be something else we weren't expecting. So, December 1st is our goal. When it is available, we will announce it on as many channels as we can. Troy ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: Plan for EPEL-9
On Mon, Nov 8, 2021 at 2:18 AM Remi Collet wrote: > > As both RHEL-9 Beta and CentOS 9 Stream are available, > what are the plan for EPEL-9 ? > > > I really this should be available ASAP to be > available to our users at GA time. EPEL 9 Next for CentOS Stream 9 is blocked on the migration of our s390x systems to z15[1], because currently all s390x builds fail[2]. Once that's taken care of, we'll launch EPEL 9 Next. [1]: https://pagure.io/fedora-infrastructure/issue/10302 [2]: https://pagure.io/releng/issue/10360 -- 真実はいつも一つ！/ Always, there's only one truth! ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
