Comments

116 Comments

The issue was fixed in elk-9.2.12-5.fc42

cd tests-libxc; ../tests/test-mpi.sh
Running test in directory test_001...
 Passed
Running test in directory test_002...
 Passed
Running test in directory test_003...
 Passed
Running test in directory test_004...
 Passed
Running test in directory test_005...
 Passed
Running test in directory test_006...
 Passed
1040.69user 5.89system 8:59.87elapsed 193%CPU (0avgtext+0avgdata 237660maxresident)k
16inputs+269152outputs (0major+427642minor)pagefaults 0swaps

thanks @marcindulak for pointing out the incomplete patch!

Looks like the side tag is no longer accessible to run the elk rebuild; I guess one must wait for these builds to hit rawhide to run the elk rebuild. It is should enough to relax the explicit version check.

I would contribute the patch upstream myself if they had an online repository...

ELK depending on libxc 6 has nothing to do with Libxc itself. Libxc 7 is fully API compatible with libxc 6.

I did notice the hard version check in the elk source code(!!!!!!) which I thought I had amended to also allow libxc version 7. Elk patch amended.

This update has been unpushed.

This update has been unpushed.

This update has been unpushed.

@axiomatic I can't reproduce it either, your document compiles just fine. Be sure to run

dnf --enablerepo=updates-testing update texlive*

Appears to work: I installed texlive-scheme-full and still have a working LaTeX.

BZ#2025720 Document fails to compile in Fedora 35
karma

This broke PySCF.

BZ#1912491 Please build SLURM in Fedora EPEL 7 and 8

This update has been unpushed.

Works

BZ#1908920 Update python-black to 20.8~b1 in Fedora 32 and 33
BZ#1895612 Internal compiler error on several architectures building OpenMolcas-20.10

This update has been unpushed.

This update has been unpushed.

Oh I didn't realize that. I was mislead since there's no qt5-devel metapackage....

karma

Doesn't segfault upon exit!

Thanks for the heads-up, I didn't remember that the el6 branch still used the obsolete way of handling dependencies.

Looks like the problem was at my end: I had a corrupted rpm database from my laptop running out of battery in the cleanup phase of a dnf update.

Sorry for the noise.