Grid Community Toolkit
# GCT packages for SLES and OpenSUSE #
According to the SUSE product support lifecycle ([1]) general support for SLES 12, 12 SP1 and 12 SP2 has already ended, so these repositories are disabled. If you are on LTSS ([2]) and still require packages for SLES 12 SP1 and 12 SP2 please let me know.
[1]: https://www.suse.com/lifecycle/
[2]: https://www.suse.com/de-de/products/long-term-service-pack-support/
****
> NOTICE1: Packages for SLES 11 (w/Service Pack 4 and Security Module (see [3] and [4] for details)) are not provided, (1) because of problems with the usable OpenSSL version in SLES 11 SP4 with Security Module, (2) unexpected difficulties with build dependency resolution not present in later SLES versions and (3) the amount of work needed to get this working just for SLES 11 whose general support will already end on 2019-03-31, so in less than half a year.
[3]: https://www.suse.com/c/introducing-the-suse-linux-enterprise-11-security-module/
[4]: https://www.suse.com/documentation/suse-best-practices/singlehtml/securitymodule/securitymodule.html
> NOTICE2: For SLES 12 (w/o Service Pack!) not all packages can be build, as a test case for the globus-gssapi-gsi build fails, most likely due to the used OpenSSL version of SLES 12. The test case works for SLES 12 SP1 and above.
> NOTICE3: The globus-xio-udt-driver build only works for OpenSUSE Leap 15.0, 15.1 and Tumbleweed, as the required (lib)udt-devel package is currently only available there and in the SUSE Package Hub (but only for AArch64! ([5])).
[5]: https://packagehub.suse.com/packages/udt/736905/
****
2019-02-26 Frank Scheiner
****
| Name | Changed |
|---|
Comments 11
2019-03-14
udtwith modified RPM spec file from OpenSUSE Leap 15.0 for SLES.aarch64andppc64ledon't havelibnice, so added path home:sbahling:Backports:SLE-15-Arch/SLE_15_Backports to SLE_15 repo definition.Hi, would you consider submitting these packages to openSUSE:Factory? I can help if you need any for specfile cleanups or so. Thanks!
@badsha400: In the short term only OpenSUSE Tumbleweed would benefit from such a change, right? But in the long-term could packages from openSUSE;Factory make it into the SLES and OpenSUSE Leap distributions, too?
I'd be absolutely interested, though my initial intention was to move these packages over to the "official" gridcf account after stabilization, getting them into the distributions would be even better and closer to the status in Fedora, EPEL and Debian.
Your help would be definitely appreciated. What needs to be done for a start?
Hi, Yes, only packages that are already in Factory make their way to Leap and SLE. So, this would be a first step. However, to get your package into openSUSE:Factory, you need to find a suitable devel project and submit your packages there first. I would suggest either science [1] or science:HPC [2]. Once your packages are reviewed and accepted into one of these projects, you may choose to submit to Factory at your convenience.
Since your packages are in working condition already, I would say they only need (mostly minor) cosmetic changes to get them in line with openSUSE packaging guidelines [3]. Typically, running
spec-cleaner file.specon a specfile will do most of the cleaning up for you.I think I'll get the cleaning up process started, so you will have some sr's from me to deal with over the weekend. Hope that is ok. Thanks a lot for your packages, btw.
[1] https://build.opensuse.org/project/show/science [2] https://build.opensuse.org/project/show/science:HPC [3] https://en.opensuse.org/openSUSE:Specfile_guidelines
@badsha400: Sure, awaiting your sr's.
Hi, sorry for the delay. But sr#697348 is the kind of changes I have in mind. Please feel to reject that sr if you disagree with anything. Thanks!
Hello.
I'm a maintainer of the GSI software in HPCI project, Japan.
We consider switching Globus Toolkit to GridCF edition, but a part of organizations joined to HPCI project uses SLES12 SP2 yet.
Could you enable SLES12 SP2's repository if possible?
Best regard.
Ok, I re-enabled it. There were a few issues to fix as available packages and behaviour seem to differ between SLES12 SP2 and SP3. For the latter the original spec files for globus-
net-managerandudtworked without modification, for SP2 they did not.What I don't know is, if the configured repo for SLES12 SP2 (
SUSE:SLE-12-SP2:GA/standard) includes the LTSS updates. So the organization in HPCI still using SLES12 SP2 should carefully check if the new GCT packages work like the old Globus Toolkit ones.In addition, feedback is always welcome, as I can't easily test with all SUSE distributions myself.
Thank you for re-enabling. We would like to contribute a fix if there are any problems.
Just checking: As LTSS for SLES 12 (SP2) ends end of March 2021, I would like to remove the builds for SLES 12 (SP2) afterwards (this will save me some work for GSI-OpenSSH) or do you still need these beyond that date?
2019-07-04
SLE_12_SP2for HPCISLE_15_SP1,openSUSE_Leap_15.1,openSUSE_Leap_15.1_ARMandopenSUSE_Leap_15.1_PowerPC