https://bugzilla.redhat.com/show_bug.cgi?id=1668215
--- Comment #5 from Jie Kang <jkang(a)redhat.com> ---
(In reply to Severin Gehwolf from comment #4)
(In reply to Mattias Ellert from comment #3)
> The module version of jmc is declared "default", i.e. unless you actively
> disable the module version this is the version you get. I have not chosen
> the activate this module, it is what you get by default.
Do you have the 'jmc' module installed, though? Output of this, please:
$ rpm -qa | grep module_2663
What does this command return for you?
$ rpm -q javamail
> I understand that if you choose to activate some module some things might
> break. This is the reason for having modules in the first place.
>
> But no module declared "default" should be allowed to break anything. A
> module declared "default" seamlessly replace normal rpms from the base
and
> updates repositories and must be drop in replacements for those. Otherwise
> they must not be declared default.
OK. I'm still trying to replicate what you are seeing, though. What are the
precise steps to reproduce this? Please provide steps in terms of dnf
commands. So far I was unable to :-(
I think if you have ever enabled or disabled the module, you can't return to
the 'default' state. In a completely fresh F29 VM I can see that if I 'sudo
dnf
install axiom', the javamail dependency is resolved from the jmc module and
there is a conflict.
I have submitted PRs to drop the default stream for jmc @
https://pagure.io/releng/fedora-module-defaults/pull-request/47
https://pagure.io/releng/fedora-module-defaults/pull-request/48
This issue should no longer occur once these propagate to the system.
--
You are receiving this mail because:
You are on the CC list for the bug.