[EPEL-devel] Fedora EPEL 7 updates-testing report
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.fedoraproject.org/updates/FEDORA-EPEL-2021-bd790583ee seamonkey-2.53.8-1.el7 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-4cfaa8ab63 djvulibre-3.5.25.3-24.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing python-regex-2021.7.6-1.el7 Details about builds: python-regex-2021.7.6-1.el7 (FEDORA-EPEL-2021-61d1701bfe) Alternative regular expression module, to replace re Update Information: Update python-regex to the latest release. ChangeLog: * Tue Jul 6 2021 Thomas Moschny - 2021.7.6-1 - Update to 2021.7.6. * Mon Jul 5 2021 Thomas Moschny - 2021.7.1-1 - Update to 2021.7.1. ___ 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] 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-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.fedoraproject.org/updates/FEDORA-EPEL-2021-d4c3bbff96 libolm-3.2.4-2.el8 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-15c5b7660c suricata-5.0.7-1.el8 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-ac096c00b0 libtpms-0.8.4-0.20210624gita594c4692a.el8.1 The following builds have been pushed to Fedora EPEL 8 updates-testing python-regex-2021.7.6-1.el8 Details about builds: python-regex-2021.7.6-1.el8 (FEDORA-EPEL-2021-7991bfb0de) Alternative regular expression module, to replace re Update Information: Update python-regex to the latest release. ChangeLog: * Tue Jul 6 2021 Thomas Moschny - 2021.7.6-1 - Update to 2021.7.6. * Mon Jul 5 2021 Thomas Moschny - 2021.7.1-1 - Update to 2021.7.1. * Thu Jun 3 2021 Python Maint - 2021.4.4-2 - Rebuilt for Python 3.10 ___ 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] libaom update issue
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, : tmprepo, verify, versionlock Loading support for Red Hat kernel ABI 0 packages excluded due to repository protections Resolving Dependencies --> Running transaction check ---> Package libaom.x86_64 0:1.0.0-8.20190810git9666276.el7 will be updated --> Processing Dependency: libaom.so.0()(64bit) for package: seamonkey-2.53.7-4.el7.x86_64 ---> Package libaom.x86_64 0:3.1.1-1.el7 will be an update --> Finished Dependency Resolution Error: Package: seamonkey-2.53.7-4.el7.x86_64 (@epel) Requires: libaom.so.0()(64bit) Removing: libaom-1.0.0-8.20190810git9666276.el7.x86_64 (@epel) libaom.so.0()(64bit) Updated By: libaom-3.1.1-1.el7.x86_64 (epel) ~libaom.so.3()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Any thoughts why this happened? It's unclear to me exactly what the issue is (note the .so bump from .0 to .3). No doubt I could likely remove both and install again, but just thought I'd inquire before changing anything. I only have a few systems this issue, so not a big deal. Thanks! ___ 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] [Fedocal] Reminder meeting : EPEL Steering Committee
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 #topic Intros #topic Old Business #topic EPEL-7 #topic EPEL-8 #topic EPEL-9 #topic Openfloor #endmeeting Source: https://calendar.fedoraproject.org//meeting/9854/ ___ 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: libaom update issue
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 yum --enablerepo=epel-testing update seamonkey libaom Troy On Tue, Jul 6, 2021 at 7:03 AM Chris Schanzle wrote: > 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, >: tmprepo, verify, versionlock > Loading support for Red Hat kernel ABI > 0 packages excluded due to repository protections > Resolving Dependencies > --> Running transaction check > ---> Package libaom.x86_64 0:1.0.0-8.20190810git9666276.el7 will be updated > --> Processing Dependency: libaom.so.0()(64bit) for package: > seamonkey-2.53.7-4.el7.x86_64 > ---> Package libaom.x86_64 0:3.1.1-1.el7 will be an update > --> Finished Dependency Resolution > Error: Package: seamonkey-2.53.7-4.el7.x86_64 (@epel) > Requires: libaom.so.0()(64bit) > Removing: libaom-1.0.0-8.20190810git9666276.el7.x86_64 (@epel) > libaom.so.0()(64bit) > Updated By: libaom-3.1.1-1.el7.x86_64 (epel) >~libaom.so.3()(64bit) > You could try using --skip-broken to work around the problem > You could try running: rpm -Va --nofiles --nodigest > > > Any thoughts why this happened? It's unclear to me exactly what the issue > is (note the .so bump from .0 to .3). No doubt I could likely remove both > and install again, but just thought I'd inquire before changing anything. > I only have a few systems this issue, so not a big deal. > > Thanks! > > ___ > 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 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
