Hide Forgot
It is impossible to install CP2K in Fedora 28 using DNF. Is this a mass rebuild problem? # dnf install dnf install cp2k* Erro: Problema 1: conflicting requests - nothing provides libxsmm.so.1()(64bit) needed by cp2k-5.1-3.fc28.x86_64 Problema 2: conflicting requests - nothing provides libxsmm.so.1()(64bit) needed by cp2k-mpich-5.1-3.fc28.x86_64 Problema 3: conflicting requests - nothing provides libxsmm.so.1()(64bit) needed by cp2k-openmpi-5.1-3.fc28.x86_64 [root@localhost x86_64] # dnf whatprovides */libxsmm.so.1 libxsmm-1.8.3-1.fc28.x86_64 : Small dense or sparse matrix multiplications and convolutions for x86_64 Repo : @System Resultado a partir de: Nome de arquivo : /usr/lib64/libxsmm.so.1 libxsmm-1.8.3-1.fc28.x86_64 : Small dense or sparse matrix multiplications and convolutions for x86_64 Repo : fedora Resultado a partir de: Nome de arquivo : /usr/lib64/libxsmm.so.1 But libxsmm-1.8.3-1.fc28.x86_64 is already installed
Related: #1577494 #1577495 #1577496
Ops. Sorry. Related: https://bugzilla.redhat.com/show_bug.cgi?id=1577494 https://bugzilla.redhat.com/show_bug.cgi?id=1577495 https://bugzilla.redhat.com/show_bug.cgi?id=1577496
cp2k-5.1-4.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-b80b8f943f
cp2k-5.1-4.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-b80b8f943f
The accidental soname change for libxsmm is reverted in builds currently in testing, which I'll push to stable as soon as possible. Apologies for not noticing the upstream issue which caused it,
libxsmm-1.8.3-2.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-b60d813a5c
libxsmm-1.8.3-2.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.