Comments (2)
dun
commented on August 22, 2024
Hi Frank. Thanks for the changes.
The project specfile targets RHEL. The pragmatic reason for this choice is that's what we run in production, and distros will always use their own custom specfile. In practice, the systems on which I currently test the specfile include AlmaLinux 8+, CentOS 7+, CentOS Stream, the last several Fedora releases, and the RHEL versions we run in production. Those are similar enough that I've been able to do so with minimal changes.
In the past, I've tried having the specfile support openSUSE as well but had to contend with multiple %if-blocks between releases. The maintenance became too burdensome. But if I have time, I'll try to revisit this and see what would be involved in supporting openSUSE again (which I think should also work on SLES).
I just checked my vm systems and openSUSE 15.4 & 15.5 are both at munge-0.5.15. I don't have any SLES systems on which to test (and as such can't readily support it). Re: your changes, libzip5 and libzip-devel are not the same as bzip2-devel; on openSUSE, it's called libbz2-devel.
from munge.
wrussian
commented on August 22, 2024
Hi Chris,
Indeed the specfile in wriiten in excellent way. Only things I did was two zypper – queries and just the minor change in munge.spec. I happy if could make a very little contribution. Many thanks for keeping the munge project running!
SuSE SLES use different names than openSUSE for several RPMs.
At the moment I’m bit busy with our new cluster, but in ~4 weeks I check to change the spec with %if clauses to operate with SuSE.
From perspective the ticket can be closed. I’ll open a new referring to #134 when I upload a change request.
Cheers,
…-Frank
From: Chris Dunlap ***@***.***>
Sent: Thursday, 6 July 2023 01:41
To: dun/munge ***@***.***>
Cc: Heckes, Frank ***@***.***>; Author ***@***.***>
Subject: Re: [dun/munge] SuSE sles15.4: small correction for munge.spec (Issue #134)
Hi Frank. Thanks for the changes.
The project specfile targets RHEL. The pragmatic reason for this choice is that's what we run in production, and distros will always use their own custom specfile. In practice, the systems on which I currently test <https://github.com/dun/munge/blob/master/tests/1000-chaos-rpm.t> the specfile include AlmaLinux 8+, CentOS 7+, CentOS Stream, the last several Fedora releases, and the RHEL versions we run in production. Those are similar enough that I've been able to do so with minimal changes.
In the past <b0f993f> , I've tried having the specfile support openSUSE as well but had to contend with multiple %if-blocks between releases. The maintenance became too burdensome. But if I have time, I'll try to revisit this and see what would be involved in supporting openSUSE again (which I think should also work on SLES).
I just checked my vm systems and openSUSE 15.4 & 15.5 are both at munge-0.5.15. I don't have any SLES systems on which to test (and as such can't readily support it). Re: your changes, libzip5 and libzip-devel are not the same as bzip2-devel; on openSUSE, it's called libbz2-devel.
—
Reply to this email directly, view it on GitHub <#134 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/APDMBS3ZMMQL3TE4TGD73GTXOX3PZANCNFSM6AAAAAAZ4OMZ3Y> .
You are receiving this because you authored the thread.Message ID: ***@***.***>
from munge.
Related Issues (20)
- Error creating volatile directories on system startup when using LDAP as the user backend HOT 3
- Munge keeps crashing under supervisord in a container HOT 3
- Error: Invalid Credential HOT 4
- runstatedir causes error, it is not clear where run directory without it is. HOT 1
- munge.socket.2 not created HOT 3
- foreground logging with timestamps HOT 2
- munged: Info: Unauthorized credential for client UID=0 GID=0 inside docker container HOT 6
- question about UID + GID sync between multiple cluster HOT 2
- munged does not ignore SIGHUP when run in foreground HOT 4
- Failed to query password file entry for "user" HOT 2
- Munge Failed - Slurm HOT 2
- slurm: credential data mismatch error, munge 0.5.13 and 0.5.14 interoperability question HOT 3
- Keyfile is insecure: group-writable permissions without sticky bit set on "/etc HOT 1
- RHEL 9 HOT 1
- Location of munge.key HOT 3
- Unauthorized credential for client UID=0 GID=0 HOT 8
- Munge permission denied HOT 6
- package fails to install on ubuntu 22.04 HOT 1
- Lot of munged task HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from munge.