[Bug 291194] security/munge: update to 0.5.17

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291194

            Bug ID: 291194
           Summary: security/munge: update to 0.5.17
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: bofh@freebsd.org
          Reporter: rikka.goering@outlook.de
                CC: bofh@freebsd.org, rikka.goering@outlook.de
          Assignee: bofh@freebsd.org
             Flags: maintainer-feedback?(bofh@freebsd.org)
                CC:
             Flags: maintainer-feedback?(bofh@freebsd.org)
                CC: bofh@freebsd.org

Maintainer CC'd.

Port: security/munge
Current version in ports: 0.5.16
Upstream latest version: 0.5.17

Upstream released munge-0.5.17 on 2025-11-13:
  https://github.com/dun/munge/releases/tag/munge-0.5.17

The release notes mention, among other things:
 - new MUNGE_OPT_IGNORE_TTL and MUNGE_OPT_IGNORE_REPLAY options
 - new unmunge --ignore-ttl / --ignore-replay options
 - improved test suite behavior and diagnostics
 - various build / cross-compilation / portability fixes

The 0.5.17 release has been built and tested upstream on FreeBSD 14.3 and 13.5,
so it should be a straightforward update for the port.

On FreeBSD, security/munge is an important dependency for several HPC-related
ports, including:
 - sysutils/slurm-wlm
 - net/pmix
 - net/openmpi, net/openmpi4

I maintain sysutils/slurm-wlm and rely on security/munge as a core dependency
on FreeBSD, so I am very interested in keeping this part of the HPC stack
close to upstream. For people running modern Slurm-based clusters on FreeBSD,
keeping MUNGE closer to upstream is quite desirable.

If you would like, I can prepare and attach a full update patch (Makefile +
distinfo) and test it via poudriere.

Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.