https://bugzilla.redhat.com/show_bug.cgi?id=1668968
Petr Pisar <ppisar(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmach(a)redhat.com,
| |mdomonko(a)redhat.com,
| |packaging-team-maint@redhat
| |.com,
| |sheltren(a)fedoraproject.org
Component|perl |yum
Assignee|jplesnik(a)redhat.com |packaging-team-maint@redhat
| |.com
Summary|failed to build transaction |yum-cron fails to solve
| |dependencies if a modular
| |repository is enabled
--- Comment #5 from Petr Pisar <ppisar(a)redhat.com> ---
I tried "dnf check" and no error. I install /usr/bin/yum and tried "yum
check"
and not error. Then wanted to examine /etc/cron.daily/0yum-daily.cron. My
system does not have it. I installed it to see what it does and it executes
/usr/sbin/yum-cron. I looked into /usr/sbin/yum-cron and saw a Python code that
uses YUM internals. I started /usr/sbin/yum-cron and I get the same error
messages as you posted.
The reason is yum-cron is an old piece of software based on YUM. Not on DNF.
YUM does not support modules at all. If I write YUM I mean the old YUM
technology that was obsoleted by DNF. Not /usr/bin/yum that's only wrapper
around DNF. YUM simply takes whatever highest package version-release it finds
and tries to install it. This assumption is not valid anymore since module
introduction.
I will reassign this issue to "yum" component where it belongs. However, I do
not believe it will be fixed any soon.
As a workaround disabling modular repositories should help you and make
yum-cron working again.
--
You are receiving this mail because:
You are on the CC list for the bug.