< snip >
That is a fallacy. As soon as cpu-x would be installed again, the problem would return, since nothing has changed, and as long as the incompatible test update of libcpuid remains available, you cannot update that package since it would break dependencies. The way forward would be to either rebuild cpu-x and offer it as an update, or to withdraw the incompatible libcpuid package from the updates-testing repo.
Well i guess i can look for the source code of cpu-x and try build it from source . As for withdrawing the incompatible libcpuid package from the updates-testing repo , well i don't have the slightest clue on how that can be achieved .
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/users@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/users@xxxxxxxxxxxxxxxxxxxxxxx
