[EPEL-devel] Fedora EPEL 7 updates-testing report

2021-07-06 Thread updates
The following Fedora EPEL 7 Security updates need testing: Age URL 40 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-1f259a45ef openjpeg2-2.3.1-11.el7 12 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-1ad14f84b0 ansible-2.9.23-1.el7 6 https://bodhi.fedoraprojec

[EPEL-devel] Fedora EPEL 8 updates-testing report

2021-07-06 Thread updates
The following Fedora EPEL 8 Security updates need testing: Age URL 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-f77315a931 seamonkey-2.53.8-1.el8 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-3eb74527f8 chromium-91.0.4472.114-1.el8 5 https://bodhi.fedo

[EPEL-devel] libaom update issue

2021-07-06 Thread Chris Schanzle
Hi, I'm getting a yum update failure with seamonkey 2.53.7-4 which requires libaom (src rpm=aom), which doesn't have a clean update path: # yum update seamonkey libaom Loaded plugins: aliases, changelog, kabi, langpacks, post-transaction-actions, priorities, protectbase, ps, remove-with-leaves

[EPEL-devel] [Fedocal] Reminder meeting : EPEL Steering Committee

2021-07-06 Thread tdawson
Dear all, You are kindly invited to the meeting: EPEL Steering Committee on 2021-07-07 from 16:00:00 to 17:00:00 US/Eastern At fedora-meet...@irc.libera.net The meeting will be about: This is the weekly EPEL Steering Committee Meeting. A general agenda is the following: #meetingname EPEL

[EPEL-devel] Re: libaom update issue

2021-07-06 Thread Troy Dawson
Looks like the seamonkey you want is still in epel7-testing. There was an aom update, and it made it through testing, so it's currently in epel7. There was also a seamonkey update, to pull in the updated aom. But it's still in epel7-testing. For now, the easiest thing to do is enable epel-testing