Hello!

I have fedora25 running with kde. I use Yum extender to manage software installations and updates.
Since a few weeks, I am not able to update all the software installed. There is a conflit error when I try to update libidn2. The error is that some files from install of libidn2-2.0.0-1.fc25.686 conflit with files from package libidn2-2.0.16-1.fc25.x86_64


There are two versions installed:
libidn2 2.0.0-1.fc25 i686
libidn2 2.0.0-1.fc25 x86_64

The error is the same if I try to update one or the other. Is there a solution for this? As far as I understood these libs are dependencies of "dnf", so I cannot simply unninstall them.

Thank you!

People seem to think their ship will fall off the edge of the earth if they don't apply all available updates.
Is there any breakage in any other packages because libidn2-2.0.16-1 is not installed?

Obviously there is something installed that will cry if libidn2 2.0.0-1.fc25 is not installed, till that software requires version libidn2-2.0.16-1, there is no need to break things for the sake of having a blank list of available updates.

Thank you for your comment.
I am far away from being a linux or genneral computer expert. Nevertheless since ever I always eared that at least for security reasons we should have all software up to date. That was my main concern. But if in this case is not that important, so I will let be as it is and wait for something to happen...

Thank you again, and regards.

you DO know the difference between " i686" and " x86_64 "

i686 is 32 bit COMPATIBILITY seeing as there are no new 32 bit desktop or laptop CPU's
-- for running OLD 32 bit software
-- things like WINE for windows programs need the old 32 bit build

x86_64 the current 64 bit CPU's

the issue with MOST things in fedora's updates is installing CONFLICTING incompatible repos

please read the " dnf " man page and help

this command should post the repose that are installed and if they are on or off
so please post the out put of that
done as root , as is normal for that command

Hello!

Here is the output of the command:

#dnf repolist all
Last metadata expiration check: 23:54:27 ago on Wed Apr 26 20:59:44 2017.
repo id repo name status
*fedora Fedora 25 - x86_64 enabled: 51,669
fedora-cisco-openh264 Fedora 25 openh264 (From Cisco) - x86_64 disabled
fedora-cisco-openh264-debuginfo Fedora 25 openh264 (From Cisco) - x86_64 - Debug disabled
fedora-debuginfo Fedora 25 - x86_64 - Debug disabled
fedora-source Fedora 25 - Source disabled
google-earth google-earth enabled: 3
nielsenb-quakespasm Copr repo for quakespasm owned by nielsenb enabled: 2
*rpmfusion-free RPM Fusion for Fedora 25 - Free enabled: 541
rpmfusion-free-debuginfo RPM Fusion for Fedora 25 - Free - Debug disabled
rpmfusion-free-rawhide RPM Fusion for Fedora Rawhide - Free disabled
rpmfusion-free-rawhide-debuginfo RPM Fusion for Fedora Rawhide - Free - Debug disabled
rpmfusion-free-rawhide-source RPM Fusion for Fedora Rawhide - Free - Source disabled
rpmfusion-free-source RPM Fusion for Fedora 25 - Free - Source disabled
*rpmfusion-free-updates RPM Fusion for Fedora 25 - Free - Updates enabled: 185
rpmfusion-free-updates-debuginfo RPM Fusion for Fedora 25 - Free - Updates Debug disabled
rpmfusion-free-updates-source RPM Fusion for Fedora 25 - Free - Updates Source disabled
rpmfusion-free-updates-testing RPM Fusion for Fedora 25 - Free - Test Updates disabled
rpmfusion-free-updates-testing-debuginfo RPM Fusion for Fedora 25 - Free - Test Updates Debug disabled
rpmfusion-free-updates-testing-source RPM Fusion for Fedora 25 - Free - Test Updates Source disabled
*updates Fedora 25 - x86_64 - Updates enabled: 18,997
updates-debuginfo Fedora 25 - x86_64 - Updates - Debug disabled
updates-source Fedora 25 - Updates Source disabled
updates-testing Fedora 25 - x86_64 - Test Updates disabled
updates-testing-debuginfo Fedora 25 - x86_64 - Test Updates Debug disabled
updates-testing-source Fedora 25 - Test Updates Source disabled

Anyone can please make a sugestion? So far two buddies did it, but no conclusion... Am I the only one in the linux world with this problem, or is it normal to have these type of conflits in the linux world, and we just have to learn to live with it?

Thank you all.

when it dose not look like a repo issue

then most of the time for a arch error in yum or dnf or zypper

first see about removing the 32 bit rpm
-- BUT READ!!!!!!!!!! the output BEFORE you hit the "y" key
if only that or one or two other rpms want to be removed then agree

if half of the operating system wants to be removed -- type " n " for NO!!!

then once removed rerun the update
the " rpm clean all " clears the cache mostly not needed except when there are errors

1 members found this post helpful.

Hello John VV,

it is solved now. Thank you for your time!

:-)