Comments
orion
I've piled onto https://bugzilla.redhat.com/show_bug.cgi?id=1815843
# dnf install python3-schema
Last metadata expiration check: 1 day, 13:59:14 ago on Fri 19 Feb 2021 08:09:15 AM MST.
Error:
Problem: conflicting requests
- nothing provides python3.6dist(contextlib2) >= 0.5.5 needed by python3-schema-0.7.3-1.el8.noarch
In file included from /builddir/build/BUILD/qgis-3.12.3/src/providers/grass/qgis.g.info.c:32:
/usr/lib64/grass78/include/grass/gis.h:28:10: fatal error: grass/config.h: No such file or directory
28 | #include <grass/config.h>
| ^~~~~~~~~~~~~~~~
WFM - Thanks!
Installs and seems to work. Thanks.
- nothing provides python-libcomps needed by koji-1.22.0-1.el8.noarch
WFM
Basic operations seem to work fine.
File "/usr/lib/python2.7/site-packages/epdb/init.py", line 30, in <module> from future import standard_library No module named future
looks like a missing requires. After installing python2-future it works
Error: Package: nut-client-2.7.4-1.el7.x86_64 (epel-testing)
Requires: systemd-udev
That's one of the reasons I removed that dep :)
Error: Package: borgbackup-1.1.11-2.el7.x86_64 (@epel-testing)
Requires: libb2.so.0()(64bit)
Removing: libb2-0.98-1.20171225git60ea749.el7.x86_64 (@epel)
libb2.so.0()(64bit)
Updated By: libb2-0.98.1-2.el7.x86_64 (epel-testing)
~libb2.so.1()(64bit)
New update - FEDORA-EPEL-2020-d06905e9a7
You need to actually enable the updates-testing-modular repo in order to test this update:
dnf --enablerepo=updates-testing-modular module install openmpi:3.1
The version of this update is 3.1.6-1.module_f32+8670+027d006d
Issue filed here: https://bugzilla.redhat.com/show_bug.cgi?id=1800226
I agree that dropping the old cron based update mechanism is not okay in EPEL7. It's not the same as having to have edit freshclam.conf - that was done once when clamav was first installed. This breaks running systems. Please re-add it.
If this update does not receive any negative karma it will get pushed to stable in 14 days, unless it receives 3 positive karma before that.
patience, young Jedi. -2 hasn't yet been pushed to testing.
I think I've found the issue - it appears that the sendmail actions now require definitions from the fail2ban-mail sub-package. I'll try to sort that out.
LGTM