@mastaiza: Can you please try again. When I try to install them from the repo, I don't get the same error you saw. I'm guessing you downloaded the RPM and tried it directly?

$ sudo dnf install --enablerepo=updates-testing xiphos biblesync
Fedora 28 - x86_64 - Test Updates                                        2.0 MB/s |  16 MB     00:08    
Last metadata expiration check: 0:00:11 ago on Thu 17 May 2018 05:54:27 PM UTC.
Dependencies resolved.
 Package            Arch         Version                                     Repository             Size
 xiphos             x86_64       4.1.0-1.fc28                                updates-testing       5.2 M
Installing dependencies:
 biblesync          x86_64       1.2.0-1.fc28                                updates-testing        35 k
 clucene-core       x86_64         fedora                588 k
 gtkhtml3           x86_64       4.10.0-7.fc28                               fedora                826 k
 libgsf             x86_64       1.14.41-5.fc28                              fedora                246 k
 sword              x86_64       1.8.1-1.fc28                                fedora                729 k
 yelp               x86_64       2:3.28.1-1.fc28                             updates-testing       783 k
 yelp-libs          x86_64       2:3.28.1-1.fc28                             updates-testing       108 k
 yelp-xsl           noarch       3.28.0-1.fc28                               updates-testing       209 k

Transaction Summary
Install  9 Packages

Total download size: 8.7 M
Installed size: 22 M

mastaiza: What command did you run to get that result? Because that provide appears to be part of this update.

$ rpm -q --provides ~/Downloads/biblesync-1.2.0-1.fc28.x86_64.rpm
biblesync = 1.2.0-1.fc28
biblesync(x86-64) = 1.2.0-1.fc28

Getting the result you have would probably be toggled by just downloading the Xiphos RPM itself and trying to install it, but if you try to install both updates in the same command (or wait until they're pushed to testing and install them from the updates-testing repo), then that should work for you.

Well, my +1 was premature. I had originally given it +1 because the 2.12.1 version doesn't produce a python error about missing modules like the currently available 2.7 does. However, trying to execute something beyond a normal "molecule --help" now produces the following:

ERROR: Python version '3.6.5' not supported. Molecule only supports python version = 2.7.

@mcepl - Thanks for the catch. I've added Xiphos to the update.

This update has been unpushed.

Can you be more specific, please? In what way is this not EPEL packaging?

None of the types seemed to fit the description of what it actually should be called. So I just went with "security". I could easily change it to anything else that might be deemed a better fit.

This should be removed unpushed, as it can cause spurious successes against epel-testing repositories. Please do so.