On 10/06/2017 09:24 AM, Patrick Dupre wrote:
When I try to install polymake, I get.
dnf install polymake
Repository mgeups has no mirror or baseurl set.
Last metadata expiration check: 1:41:29 ago on Fri 06 Oct 2017 04:34:53 PM CEST.
Error:
Problem: conflicting requests
- package polymake-3.1-3.fc26.i686 requires perl = 4:5.24.1, but none of the providers
can be installed
- package polymake-3.1-3.fc26.x86_64 requires perl = 4:5.24.1, but none of the
providers can be installed
- package perl-4:5.24.1-390.fc26.x86_64 requires perl-libs(x86-64) =
4:5.24.1-390.fc26, but none of the providers can be installed
- perl-libs-4:5.24.3-395.fc26.i686 has inferior architecture
- package perl-warnings-unused-0.06-1.fc26.x86_64 requires
perl(:MODULE_COMPAT_5.24.2), but none of the providers can be installed
- cannot install both perl-libs-4:5.24.1-390.fc26.x86_64 and
perl-libs-4:5.24.3-395.fc26.x86_64
- problem with installed package perl-warnings-unused-0.06-1.fc26.x86_64
- nothing provides perl = 4:5.24.2 needed by polymake-3.1-4.fc26.i686
- nothing provides perl = 4:5.24.2 needed by polymake-3.1-4.fc26.x86_64
(try to add '--allowerasing' to command line to replace conflicting packages or
'--skip-broken' to skip uninstallable packages)
And once again, you left out almost all the useful information. Just
paste the entire output of the dnf command.
If I make
dnf install polymake --allowerasing
it offers me to erase packages (Removing dependent packages) that I do not want to erase
(like my own perl packages)
and also to downgrade packages like:
vim-X11, vim-common, vim-enhanced, perl!!
You have installed perl packages that you have built yourself? That's
likely the problem. They could be blocking the upgrade of perl. I also
notice that the install is trying to install both 32-bit and 64-bit
versions of polymake. That is very strange assuming the command you
list at the top is actually what you entered. dnf should only try
installing the one for the base os architecture unless you already have
polymake installed in both version.
It is probably an issue with the updates-testing!!
Given that you left out all the info that would show that, it's
impossible to tell.