Am 11.01.21 um 00:41 schrieb Samuel Sieb:
I have no problem with it on F33 or F32. I suspect the actual problem
is in one of those other packages that are mentioned. The dnf
messages are really hard to figure out, but it looks like there's a
long dependency chain possibly ending up with scala. Do you have any
blocking of modules?
Good Eyes .. There is an old scala.module entry of unkown origin, but
it's enabled:
[root@eve dnf]# ll modules.d
insgesamt 28
-rw-r--r--. 1 root root 51 27. Nov 2019 ant.module
-rw-r--r--. 1 root root 0 3. Jun 2020 eclipse.module.rpmmoved
-rw-r--r--. 1 root root 54 28. Nov 2019 gimp.module
-rw-r--r--. 1 root root 48 28. Nov 2019 libgit2.module
-rw-r--r--. 1 root root 54 27. Nov 2019 maven.module
-rw-r--r--. 1 root root 58 28. Nov 2019 meson.module
-rw-r--r--. 1 root root 58 28. Nov 2019 ninja.module
-rw-r--r--. 1 root root 55 27. Nov 2019 scala.module
[root@eve dnf]# cat modules.d/scala.module
[scala]
name=scala
stream=2.10
profiles=
state=enabled
- package scala-2.10.6-17.fc32.noarch is filtered out by modular
filtering
What happens if you add "--allowerasing" to the dnf command?
I renamed the scala.module and now it got installed.
best regards,
Marius Schwarz
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to 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/devel@lists.fedoraproject.org
