[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 52 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-4a9fc09599 openjpeg2-2.3.1-10.el7 13 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-e30a25d6d0 chromium-88.0.4324.96-1.el7 11 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-4e3398c399 libssh-0.7.7-1.el7 11 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-c09d7045f3 seamonkey-2.53.6-1.el7 10 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-ba217a684f monitorix-3.13.1-1.el7 7 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-5ecfbfc6f6 pngcheck-2.4.0-7.el7 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-6eebad70ee SDL2-2.0.14-2.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing openelp-0.9.2-1.el7 Details about builds: openelp-0.9.2-1.el7 (FEDORA-EPEL-2021-380682c3f0) Open Source EchoLink Proxy Update Information: Update to OpenELP 0.9.2 ChangeLog: * Sun Feb 7 2021 Scott K Logan - 0.9.2-1 - Update to 0.9.2 (rhbz#1925917) References: [ 1 ] Bug #1925917 - openelp-0.9.2 is available https://bugzilla.redhat.com/show_bug.cgi?id=1925917 ___ 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
[EPEL-devel] Fedora EPEL 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing:
Age URL
12 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-b68969af8c
chromium-88.0.4324.96-1.el8
11 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-403074b7e0
seamonkey-2.53.6-1.el8
10 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-aadbebf090
monitorix-3.13.1-1.el8
6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-eca913b42e
pngcheck-2.4.0-7.el8
5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-69b5865b58
privoxy-3.0.31-1.el8
4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-5e4b80b9d8
zeromq-4.3.4-2.el8
4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-1917130359
czmq-4.2.1-2.el8
The following builds have been pushed to Fedora EPEL 8 updates-testing
NetworkManager-l2tp-1.8.6-5.el8
darktable-3.4.1-1.el8
openelp-0.9.2-1.el8
stress-ng-0.12.02-2.el8
Details about builds:
NetworkManager-l2tp-1.8.6-5.el8 (FEDORA-EPEL-2021-f8c96d653c)
NetworkManager VPN plugin for L2TP and L2TP/IPsec
Update Information:
Update to 1.8.6 release
ChangeLog:
* Sun Feb 7 2021 Douglas Kosovic - 1.8.6-5
- Correct EPEL8 conditional
* Sun Feb 7 2021 Douglas Kosovic - 1.8.6-4
- Sync with EPEL8
* Mon Jan 25 2021 Fedora Release Engineering -
1.8.6-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild
* Fri Jan 8 2021 Tomas Hrcka - 1.8.6-2
- rebuilt for new version of ppp
* Tue Nov 3 2020 Douglas Kosovic - 1.8.6-1
- Updated to 1.8.6 release
- Remove redundant libnm_glib conditionals
- explictly recommend libreswan >= 4.0 because of change in NSS DB location.
- AppData file now in %{_datadir}/metainfo/
- D-Bus policy file now in %{_datadir}/dbus-1/system.d/
* Mon Jul 27 2020 Fedora Release Engineering -
1.8.2-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
darktable-3.4.1-1.el8 (FEDORA-EPEL-2021-627a19325d)
Utility to organize and develop raw images
Update Information:
3.4.1 release
ChangeLog:
* Sat Feb 6 2021 Germano Massullo - 3.4.1-1
- 3.4.1 release
- removed 7428.patch and 7569.patch
* Tue Jan 26 2021 Fedora Release Engineering -
3.4.0-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild
openelp-0.9.2-1.el8 (FEDORA-EPEL-2021-371f06fb25)
Open Source EchoLink Proxy
Update Information:
Update to OpenELP 0.9.2
ChangeLog:
* Sun Feb 7 2021 Scott K Logan - 0.9.2-1
- Update to 0.9.2 (rhbz#1925917)
References:
[ 1 ] Bug #1925917 - openelp-0.9.2 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1925917
stress-ng-0.12.02-2.el8 (FEDORA-EPEL-2021-4860897f3e)
Stress test a computer system in various ways
Update Information:
Bump to 0.12.02
ChangeLog:
* Sun Feb 7 2021 Chris Brown - 0.12.02-1
- Bump to 0.12.02
* Wed Jan 27 2021 Fedora Release Engineering -
0.12.01-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild
References:
[ 1 ] Bug #1919034 - stress-ng-0.12.02 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1919034
___
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
[EPEL-devel] Re: Proposal: EPEL9 timeline
Overall this seems fine to me, a few nitpicks inline... On Fri, Feb 05, 2021 at 01:51:15PM -0800, Troy Dawson wrote: > This is a proposal. It's mainly writing down what I think most of us > agreed on at last weeks EPEL Steering Committee meeting. Feel free to > continue to discuss and/or have ideas. > I've been asked by a couple places what the plans were, so I'm writing it > here. > > Overall Plan: > - epel-next is an epel branch that is built against CentOS Stream. epel-next > only has the packages that would be incompatible with released RHEL > builds, or if an EPEL maintainer is updating a package that will only > be released to regular EPEL at the next RHEL release. > - We plan on creating epel9-next when CentOS 9 Stream has a public > repository. We plan on using the EPEL Packaging SIG to populate it > early with common packages, although any EPEL package maintainers can > add their packages whenever they want. This part I am unsure of. What are 'common packages' ? We should make sure and ask maintainers to branch and maintain packages they want for this, but I think it would be odd to just do it without them being in the loop. We never never 'mass branched' things in the past. EPEL isn't a specific set of packages, it's packages maintainers want to maintain. That said, if there's packages of interest where the maintainers are not interested in epel, the epel sig should definitely branch and maintain those. > - We plan on creating normal EPEL9 after the RHEL 9.0 GA release, just > like normal. No sooner. All epel9-next packages will be rebuilt on > EPEL9. They will not be "tagged over". This rebuild should be by whoever > built it in epel9-next. This I am also not a fan of. What if you make a epel9-next branch for something, but you don't (for whatever reason) want to put it in epel9? I think we should just open new epel9 branches at epel9 time and maintaienrs can branch and build them (again, if people don't care the epel packagers sig can do all the ones they manage right up front). > > Approximate Timelines: > - All of these timelines depend on (A) CentOS 9 Stream / RHEL9 actual dates > and (B) availability of EPEL volunteers. Please note, EPEL is > completely volunteers, and sometimes "day jobs" make EPEL timelines slip. > - epel9-next - July 2021 > -- CentOS 9 Stream should have a public repository in April 2021 > -- Should take about 3 months to setup > - epel9 - October 2022 > -- RHEL 9.0 should be released around May 2022 > -- Should take about 5 months to setup > -- Note: It takes longer because it has to deal with getting packages > from an internal RHEL repo and all the complications of doing that. > > EPEL Packaging SIG > - We hope to utilize the EPEL Packaging SIG as much as possible. > - This might be as simple as having them rebuild a epel9-next package > on epel9, or possibly maintaining a package when the Fedora packager > does not want to do EPEL. I think simple is better here. > - More details will be coming, but we hope the SIG will help get alot > of the most used EPEL packages into EPEL9 as soon as possible. Thanks for writing all this up! 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
[EPEL-devel] Xfce 4.16 on EPEL-8
Hi all, I have a COPR containing xfce 4.16 packages for EPEL-8 packages [0]. I would like to get some testing done using this COPR before getting into EPEL-8. Please email if and when you notice problems and I will try to fix it as soon as possible. As a reminder - xfce 4.16 will be available in F34. Thanks, Mukundan. [0] https://copr.fedorainfracloud.org/coprs/nonamedotc/xfce416-epel8/ -- GPG Key: E5C8BC67 OpenPGP_signature Description: OpenPGP digital 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
