Minor typo - the summary for the python2 subpackage says python3:
$ dnf search stomppy ============================= N/S Matched: stomppy ============================= python2-stomppy.noarch : Python stomp client for messaging for python3 python3-stomppy.noarch : Python stomp client for messaging for python3
This update changes the name of the binary package, and hence breaks dependencies in other packages that declare a dependency on it. There is an attempt at a provides for the old name, but unfortunately it is misspelled so it is not useful for backward compatibility with the old name (see rhbz #1435744). In order to fix the broken dependency in my package I adapted it to require the new name of the binary package, which stopped the complaints about the broken deps in F27. Now after the freeze is lifted for F26 my update for F26 was pushed to stable too, but now this update is not pushed yet and the new name is not available in F26 so now I got notifications of broken dependencies in F26.
Thank you for your detailed logs. I can see that on your system you do not have the CRLs installed. An absent CRL should mean "do not check" the CRL, and hence not be a source of an error. If I move the CRLs out of the way on my system I can reproduce the problem.
Looking at the code it looks like the 4.6.0 CRL checking code treats an absent CRL the same as an expired CRL and triggers error, which is a bug.
I have reported this upstream:
I can not reproduce this:
$ rpm -q xrootd-client xrootd-client-4.6.0-2.fc25.x86_64 $ xrdcp -f -d1 root://se1.accre.vanderbilt.edu//store/test/xrootd/T2_US_Vanderbilt//store/mc/SAM/GenericTTbar/GEN-SIM-RECO/CMSSW_5_3_1_START53_V5-v1/0013/CE4D66EB-5AAE-E111-96D6-003048D37524.root /dev/null [16MB/492.2MB][ 3%][=> ][2MB/s] [80MB/492.2MB][ 16%][========> ][6.667MB . . . [492.2MB/492.2MB][100%][==================================================][15.3 [492.2MB/492.2MB][100%][==================================================][14.92MB/s]
Can you provide more information?