On Tue, 29 Dec 2020 19:00:30 +0200, Kostas Sfakiotakis wrote:
[root@Orion ~]# dnf repoquery --whatrequires libcpuid
Last metadata expiration check: 0:52:55 ago on Tue 29 Dec 2020 06:01:13
PM EET.
cpu-x-0:4.0.1-5.fc33.x86_64
i-nex-0:7.6.1-4.fc33.x86_64
i-nex-0:7.6.1-6.fc33.x86_64
libcpuid-devel-0:0.4.1-3.fc33.i686
libcpuid-devel-0:0.4.1-3.fc33.x86_64
libcpuid-devel-0:0.5.0-1.fc33.i686
libcpuid-devel-0:0.5.0-1.fc33.x86_64
The only package from the above that i was using was cpu-x ( deleted it
since ) , i am not using i-nex , so by deleting the cpu-x package i was
indeed getting rid off the
problem you mentioned with libcpuid . That's what i was trying to say .
You had written "[...] and then reinstall or abandon the cpu-x package
for the moment [...]", which prompted me to point out that reinstalling
the package would not fix anything, since it would not fix the dependency
breakage.
Of course, if you don't need cpu-x at all, you can keep it removed.
Reinstalling is what would not fix anything with regard to the libcpuid
test update breakage.