The gfal2 folks just released a version into EPEL that's incompatible with XRootD 4. We'll need to build a passthrough of gfal2-plugin-xrootd specifically for OSG 3.5. This could mean the currently released version, or perhaps an older version if the latest version is itself incompatible with XRootD 4
Yeah, our xcache Requires python-xrootd, which on el8 prefers the python3-xrootd from epel, which is part of the epel xrootd5 build.
In our el8 build of xrootd4, we have a python2-xrootd but not a python3-xrootd:
Per discussion with , i am untagging our xrootd builds from osg-3.5-el8-testing, since we are not planning to release those anyway, and it may be related to the python-xrootd conflicts with epel's xrootd in el8.
Per our discussion on Slack last night, we should not release gfal2-2.18.1-1.osg35.el8 as it’s not needed until we release XRootD 4 for EL8. could you please untag it from the prerelease/rolling/testing repos?
It's already untagged.
Perfect! Let’s make sure to note when we untag packages in relevant tickets in the future, though, to maintain the paper trail.
I did it late yesterday in preparation for today's release. I guess I didn't think about it because I don't get the pretty table. I will note untags in the future.