Closed fscheiner closed 2 years ago
Not sure anyone would still be interested in the myproxy-oauth. In principle https://github.com/ncsa/OA4MP is what's supported, but it still could be nice if it's not too difficult to get to work.
What's the difference between myproxy-oauth and OA4MP anyhow?
Not sure anyone would still be interested in the myproxy-oauth. In principle https://github.com/ncsa/OA4MP is what's supported, but it still could be nice if it's not too difficult to get to work.
What's the difference between myproxy-oauth and OA4MP anyhow?
See #200 let's just remove the myproxy-oauth code and close #200.
Ok, I agree and I'll look into that and come up with another PR.
- "globus-xio-udt-driver" can't be built (also for SRPM) on CentOS Stream 9 and Rocky Linux 9 because "libnice(-devel)" is not (yet) available for these OSes, so (S)RPMs are not built for *9 OS versions, too. Mattias has already opened a bug about branching and building libnice in EPEL 9.
Now buildable in EPEL 9. The RHEL 9.1 release added some missing dependencies needed to build the missing dependencies in EPEL.
globus-xio-udt-driver package update for EPEL 9: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-cd6c9c9c8b
Thanks for getting this going Mattias (@ellert), I saw it in the morning and will make the required changes.
This PR implements the following changes:
no.4 unveiled the following issues:
~"globus-xio-udt-driver" can't be built (also for SRPM) on CentOS Stream 9 and Rocky Linux 9 because "libnice(-devel)" is not (yet) available for these OSes, so (S)RPMs are not built for *9 OS versions, too. Mattias has already opened a bug about branching and building libnice in EPEL 9.~
=> Bug 2033520 is solved and libnice is now in EPEL 9 (see https://github.com/gridcf/gct/pull/199#issuecomment-1320932059)
~"myproxy-oauth" can't be built on CentOS Stream 8 and Rocky Linux 8 and upwards as it depends on Python 2.x based dependencies not available for the respective OSes, so neither source tarballs nor (S)RPMs are built for 8 and 9 OS versions. There is also no "myproxy-oauth" package in EPEL or Fedora AFAICS. So this part of the GCT could be (1) dropped when switching from CentOS 7 to an *8 version of the OS as main build target or (2) needs to be ported to Python 3 if kept.~
=> myproxy-oauth is gone with #201 merged.
"globus-scheduler-event-generator" depends on LSB (Linux Standard Base) if available (see https://github.com/gridcf/gct/blob/switchover-to-new-src-repo/gram/jobmanager/scheduler_event_generator/source/configure.ac#L59..#L77 for details) but per default does not actually depend on LSB, so for *9 OS versions which are missing "redhat-lsb-core" the LSB dependency can be safely ignored. The dependency comes from an init script version that uses LSB init functions. The "globus-scheduler-event-generator-progs" package in EPEL and Fedora use a non-LSB init script or a systemd unit file w/o LSB dependency.